]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
41e964a625f848c307f4d0007c401276e0f70157
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>https://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>OpenSnitch in Debian ready for prime time</title>
11 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</guid>
13 <pubDate>Sat, 13 May 2023 12:10:00 +0200</pubDate>
14 <description>&lt;p&gt;A bit delayed,
15 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
16 application firewall OpenSnitch&lt;/a&gt; package in Debian now got the
17 latest fixes ready for Debian Bookworm. Because it depend on a
18 package missing on some architectures, the autopkgtest check of the
19 testing migration script did not understand that the tests were
20 actually working, so the migration was delayed. A bug in the package
21 dependencies is also fixed, so those installing the firewall package
22 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
23 installed by default. I am very grateful to Gustavo Iñiguez Goya for
24 his work on getting the package ready for Debian Bookworm.&lt;/p&gt;
25
26 &lt;p&gt;Armed with this package I have discovered some surprising
27 connections from programs I believed were able to work completly
28 offline, and it has already proven its worth, at least to me. If you
29 too want to get more familiar with the kind of programs using
30 Internett connections on your machine, I recommend testing &lt;tt&gt;apt
31 install opensnitch&lt;/tt&gt; in Bookworm and see what you think.&lt;/p&gt;
32
33 &lt;p&gt;The package is still not able to build its eBPF module within
34 Debian. Not sure how much work it would be to get it working, but
35 suspect some kernel related packages need to be extended with more
36 header files to get it working.&lt;/p&gt;
37
38 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
39 activities, please send Bitcoin donations to my address
40 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
41 </description>
42 </item>
43
44 <item>
45 <title>Speech to text, she APTly whispered, how hard can it be?</title>
46 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</link>
47 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</guid>
48 <pubDate>Sun, 23 Apr 2023 09:40:00 +0200</pubDate>
49 <description>&lt;p&gt;While visiting a convention during Easter, it occurred to me that
50 it would be great if I could have a digital Dictaphone with
51 transcribing capabilities, providing me with texts to cut-n-paste into
52 stuff I need to write. The background is that long drives often bring
53 up the urge to write on texts I am working on, which of course is out
54 of the question while driving. With the release of
55 &lt;a href=&quot;https://github.com/openai/whisper/&quot;&gt;OpenAI Whisper&lt;/a&gt;, this
56 seem to be within reach with Free Software, so I decided to give it a
57 go. OpenAI Whisper is a Linux based neural network system to read in
58 audio files and provide text representation of the speech in that
59 audio recording. It handle multiple languages and according to its
60 creators even can translate into a different language than the spoken
61 one. I have not tested the latter feature. It can either use the CPU
62 or a GPU with CUDA support. As far as I can tell, CUDA in practice
63 limit that feature to NVidia graphics cards. I have few of those, as
64 they do not work great with free software drivers, and have not tested
65 the GPU option. While looking into the matter, I did discover some
66 work to provide CUDA support on non-NVidia GPUs, and some work with
67 the library used by Whisper to port it to other GPUs, but have not
68 spent much time looking into GPU support yet. I&#39;ve so far used an old
69 X220 laptop as my test machine, and only transcribed using its
70 CPU.&lt;/p&gt;
71
72 &lt;p&gt;As it from a privacy standpoint is unthinkable to use computers
73 under control of someone else (aka a &quot;cloud&quot; service) to transcribe
74 ones thoughts and personal notes, I want to run the transcribing
75 system locally on my own computers. The only sensible approach to me
76 is to make the effort I put into this available for any Linux user and
77 to upload the needed packages into Debian. Looking at Debian Bookworm, I
78 discovered that only three packages were missing,
79 &lt;a href=&quot;https://bugs.debian.org/1034307&quot;&gt;tiktoken&lt;/a&gt;,
80 &lt;a href=&quot;https://bugs.debian.org/1034144&quot;&gt;triton&lt;/a&gt;, and
81 &lt;a href=&quot;https://bugs.debian.org/1034091&quot;&gt;openai-whisper&lt;/a&gt;. For a while
82 I also believed
83 &lt;a href=&quot;https://bugs.debian.org/1034286&quot;&gt;ffmpeg-python&lt;/a&gt; was
84 needed, but as its
85 &lt;a href=&quot;https://github.com/kkroening/ffmpeg-python/issues/760&quot;&gt;upstream
86 seem to have vanished&lt;/a&gt; I found it safer
87 &lt;a href=&quot;https://github.com/openai/whisper/pull/1242&quot;&gt;to rewrite
88 whisper&lt;/a&gt; to stop depending on in than to introduce ffmpeg-python
89 into Debian. I decided to place these packages under the umbrella of
90 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team&quot;&gt;the Debian Deep
91 Learning Team&lt;/a&gt;, which seem like the best team to look after such
92 packages. Discussing the topic within the group also made me aware
93 that the triton package was already a future dependency of newer
94 versions of the torch package being planned, and would be needed after
95 Bookworm is released.&lt;/p&gt;
96
97 &lt;p&gt;All required code packages have been now waiting in
98 &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the Debian NEW
99 queue&lt;/a&gt; since Wednesday, heading for Debian Experimental until
100 Bookworm is released. An unsolved issue is how to handle the neural
101 network models used by Whisper. The default behaviour of Whisper is
102 to require Internet connectivity and download the model requested to
103 &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt; on first invocation. This obviously would
104 fail &lt;a href=&quot;https://people.debian.org/~bap/dfsg-faq.html&quot;&gt;the
105 deserted island test of free software&lt;/a&gt; as the Debian packages would
106 be unusable for someone stranded with only the Debian archive and solar
107 powered computer on a deserted island.&lt;/p&gt;
108
109 &lt;p&gt;Because of this, I would love to include the models in the Debian
110 mirror system. This is problematic, as the models are very large
111 files, which would put a heavy strain on the Debian mirror
112 infrastructure around the globe. The strain would be even higher if
113 the models change often, which luckily as far as I can tell they do
114 not. The small model, which according to its creator is most useful
115 for English and in my experience is not doing a great job there
116 either, is 462 MiB (deb is 414 MiB). The medium model, which to me
117 seem to handle English speech fairly well is 1.5 GiB (deb is 1.3 GiB)
118 and the large model is 2.9 GiB (deb is 2.6 GiB). I would assume
119 everyone with enough resources would prefer to use the large model for
120 highest quality. I believe the models themselves would have to go
121 into the non-free part of the Debian archive, as they are not really
122 including any useful source code for updating the models. The
123 &quot;source&quot;, aka the model training set, according to the creators
124 consist of &quot;680,000 hours of multilingual and multitask supervised
125 data collected from the web&quot;, which to me reads material with both
126 unknown copyright terms, unavailable to the general public. In other
127 words, the source is not available according to the Debian Free
128 Software Guidelines and the model should be considered non-free.&lt;/p&gt;
129
130 &lt;p&gt;I asked the Debian FTP masters for advice regarding uploading a
131 model package on their IRC channel, and based on the feedback there it
132 is still unclear to me if such package would be accepted into the
133 archive. In any case I wrote build rules for a
134 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team/openai-whisper-model&quot;&gt;OpenAI
135 Whisper model package&lt;/a&gt; and
136 &lt;a href=&quot;https://github.com/openai/whisper/pull/1257&quot;&gt;modified the
137 Whisper code base&lt;/a&gt; to prefer shared files under &lt;tt&gt;/usr/&lt;/tt&gt; and
138 &lt;tt&gt;/var/&lt;/tt&gt; over user specific files in &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt;
139 to be able to use these model packages, to prepare for such
140 possibility. One solution might be to include only one of the models
141 (small or medium, I guess) in the Debian archive, and ask people to
142 download the others from the Internet. Not quite sure what to do
143 here, and advice is most welcome (use the debian-ai mailing list).&lt;/p&gt;
144
145 &lt;p&gt;To make it easier to test the new packages while I wait for them to
146 clear the NEW queue, I created an APT source targeting bookworm. I
147 selected Bookworm instead of Bullseye, even though I know the latter
148 would reach more users, is that some of the required dependencies are
149 missing from Bullseye and I during this phase of testing did not want
150 to backport a lot of packages just to get up and running.&lt;/p&gt;
151
152 &lt;p&gt;Here is a recipe to run as user root if you want to test OpenAI
153 Whisper using Debian packages on your Debian Bookworm installation,
154 first adding the APT repository GPG key to the list of trusted keys,
155 then setting up the APT repository and finally installing the packages
156 and one of the models:&lt;/p&gt;
157
158 &lt;p&gt;&lt;pre&gt;
159 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
160 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
161 mkdir -p /etc/apt/sources.list.d
162 cat &gt; /etc/apt/sources.list.d/pere-whisper.list &amp;lt;&amp;lt;EOF
163 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
164 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
165 EOF
166 apt update
167 apt install openai-whisper
168 &lt;/pre&gt;&lt;/p&gt;
169
170 &lt;p&gt;The package work for me, but have not yet been tested on any other
171 computer than my own. With it, I have been able to (badly) transcribe
172 a 2 minute 40 second Norwegian audio clip to test using the small
173 model. This took 11 minutes and around 2.2 GiB of RAM. Transcribing
174 the same file with the medium model gave a accurate text in 77 minutes
175 using around 5.2 GiB of RAM. My test machine had too little memory to
176 test the large model, which I believe require 11 GiB of RAM. In
177 short, this now work for me using Debian packages, and I hope it will
178 for you and everyone else once the packages enter Debian.&lt;/p&gt;
179
180 &lt;p&gt;Now I can start on the audio recording part of this project.&lt;/p&gt;
181
182 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
183 activities, please send Bitcoin donations to my address
184 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
185 </description>
186 </item>
187
188 <item>
189 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software</title>
190 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</link>
191 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</guid>
192 <pubDate>Fri, 7 Apr 2023 23:10:00 +0200</pubDate>
193 <description>&lt;p&gt;Today I finally found time to track down a useful radio frequency
194 scanner for my software defined radio. Just for fun I tried to locate
195 the radios used in the areas, and a good start would be to scan all
196 the frequencies to see what is in use. I&#39;ve tried to find a useful
197 program earlier, but ran out of time before I managed to find a useful
198 tool. This time I was more successful, and after a few false leads I
199 found a description of
200 &lt;a href=&quot;https://www.kali.org/tools/rtlsdr-scanner/&quot;&gt;rtlsdr-scanner
201 over at the Kali site&lt;/a&gt;, and was able to track down
202 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git&quot;&gt;the
203 Kali package git repository&lt;/a&gt; to build a deb package for the
204 scanner. Sadly the package is missing from the Debian project itself,
205 at least in Debian Bullseye. Two runtime dependencies,
206 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-visvis.git&quot;&gt;python-visvis&lt;/a&gt;
207 and
208 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-rtlsdr.git&quot;&gt;python-rtlsdr&lt;/a&gt;
209 had to be built and installed separately. Luckily &#39;&lt;tt&gt;gbp
210 buildpackage&lt;/tt&gt;&#39; handled them just fine and no further packages had
211 to be manually built. The end result worked out of the box after
212 installation.&lt;/p&gt;
213
214 &lt;p&gt;My initial scans for FM channels worked just fine, so I knew the
215 scanner was functioning. But when I tried to scan every frequency
216 from 100 to 1000 MHz, the program stopped unexpectedly near the
217 completion. After some debugging I discovered USB software radio I
218 used rejected frequencies above 948 MHz, triggering a unreported
219 exception breaking the scan. Changing the scan to end at 957 worked
220 better. I similarly found the lower limit to be around 15, and ended
221 up with the following full scan:&lt;/p&gt;
222
223 &lt;p&gt;&lt;a href=&quot;https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png&quot;&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png&quot; width=&quot;100%&quot;&gt;&lt;/a&gt;&lt;/p&gt;
224
225 &lt;p&gt;Saving the scan did not work, but exporting it as a CSV file worked
226 just fine. I ended up with around 477k CVS lines with dB level for
227 the given frequency.&lt;/p&gt;
228
229 &lt;p&gt;The save failure seem to be a missing UTF-8 encoding issue in the
230 python code. Will see if I can find time to send a patch
231 &lt;a href=&quot;https://github.com/CdeMills/RTLSDR-Scanner/&quot;&gt;upstream&lt;/a&gt;
232 later to fix this exception:&lt;/p&gt;
233
234 &lt;pre&gt;
235 Traceback (most recent call last):
236 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
237 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
238 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
239 handle.write(json.dumps(data, indent=4))
240 TypeError: a bytes-like object is required, not &#39;str&#39;
241 Traceback (most recent call last):
242 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
243 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
244 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
245 handle.write(json.dumps(data, indent=4))
246 TypeError: a bytes-like object is required, not &#39;str&#39;
247 &lt;/pre&gt;
248
249 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
250 activities, please send Bitcoin donations to my address
251 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
252 </description>
253 </item>
254
255 <item>
256 <title>OpenSnitch available in Debian Sid and Bookworm</title>
257 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</link>
258 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</guid>
259 <pubDate>Sat, 25 Feb 2023 20:30:00 +0100</pubDate>
260 <description>&lt;p&gt;Thanks to the efforts of the OpenSnitch lead developer Gustavo
261 Iñiguez Goya allowing me to sponsor the upload,
262 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
263 application firewall OpenSnitch&lt;/a&gt; is now available in Debian
264 Testing, soon to become the next stable release of Debian.&lt;/p&gt;
265
266 &lt;p&gt;This is a package which set up a network firewall on one or more
267 machines, which is controlled by a graphical user interface that will
268 ask the user if a program should be allowed to connect to the local
269 network or the Internet. If some background daemon is trying to dial
270 home, it can be blocked from doing so with a simple mouse click, or by
271 default simply by not doing anything when the GUI question dialog pop
272 up. A list of all programs discovered using the network is provided
273 in the GUI, giving the user an overview of how the machine(s) programs
274 use the network.&lt;/p&gt;
275
276 &lt;p&gt;OpenSnitch was uploaded for NEW processing about a month ago, and I
277 had little hope of it getting accepted and shaping up in time for the
278 package freeze, but the Debian ftpmasters proved to be amazingly quick
279 at checking out the package and it was accepted into the archive about
280 week after the first upload. It is now team maintained under the Go
281 language team umbrella. A few fixes to the default setup is only in
282 Sid, and should migrate to Testing/Bookworm in a week.&lt;/p&gt;
283
284 &lt;p&gt;During testing I ran into an
285 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/813&quot;&gt;issue
286 with Minecraft server broadcasts disappearing&lt;/a&gt;, which was quickly
287 resolved by the developer with a patch and a proposed configuration
288 change. I&#39;ve been told this was caused by the Debian packages default
289 use if /proc/ information to track down kernel status, instead of the
290 newer eBPF module that can be used. The reason is simply that
291 upstream and I have failed to find a way to build the eBPF modules for
292 OpenSnitch without a complete configured Linux kernel source tree,
293 which as far as we can tell is unavailable as a build dependency in
294 Debian. We tried unsuccessfully so far to use the kernel-headers
295 package. It would be great if someone could provide some clues how to
296 build eBPF modules on build daemons in Debian, possibly without the full
297 kernel source.&lt;/p&gt;
298
299 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
300 activities, please send Bitcoin donations to my address
301 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
302 </description>
303 </item>
304
305 <item>
306 <title>Is the desktop recommending your program for opening its files?</title>
307 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</link>
308 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</guid>
309 <pubDate>Sun, 29 Jan 2023 11:00:00 +0100</pubDate>
310 <description>&lt;p&gt;Linux desktop systems
311 &lt;a href=&quot;https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html&quot;&gt;have
312 standardized&lt;/a&gt; how programs present themselves to the desktop
313 system. If a package include a .desktop file in
314 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
315 environments will pick up the file and use its content to generate the
316 menu of available programs in the system. A lesser known fact is that
317 a package can also explain to the desktop system how to recognize the
318 files created by the program in question, and use it to open these
319 files on request, for example via a GUI file browser.&lt;/p&gt;
320
321 &lt;p&gt;A while back I ran into a package that did not tell the desktop
322 system how to recognize its files and was not used to open its files
323 in the file browser and fixed it. In the process I wrote a simple
324 debian/tests/ script to ensure the setup keep working. It might be
325 useful for other packages too, to ensure any future version of the
326 package keep handling its own files.&lt;/p&gt;
327
328 &lt;p&gt;For this to work the file format need a useful MIME type that can
329 be used to identify the format. If the file format do not yet have a
330 MIME type, it should define one and preferably also
331 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;register
332 it with IANA&lt;/a&gt; to ensure the MIME type string is reserved.&lt;/p&gt;
333
334 &lt;p&gt;The script uses the &lt;tt&gt;xdg-mime&lt;/tt&gt; program from xdg-utils to
335 query the database of standardized package information and ensure it
336 return sensible values. It also need the location of an example file
337 for xdg-mime to guess the format of.&lt;/p&gt;
338
339 &lt;pre&gt;
340 #!/bin/sh
341 #
342 # Author: Petter Reinholdtsen
343 # License: GPL v2 or later at your choice.
344 #
345 # Validate the MIME setup, making sure motor types have
346 # application/vnd.openmotor+yaml associated with them and is connected
347 # to the openmotor desktop file.
348
349 retval=0
350
351 mimetype=&quot;application/vnd.openmotor+yaml&quot;
352 testfile=&quot;test/data/real/o3100/motor.ric&quot;
353 mydesktopfile=&quot;openmotor.desktop&quot;
354
355 filemime=&quot;$(xdg-mime query filetype &quot;$testfile&quot;)&quot;
356
357 if [ &quot;$mimetype&quot; != &quot;$filemime&quot; ] ; then
358 retval=1
359 echo &quot;error: xdg-mime claim motor file MIME type is $filemine, not $mimetype&quot;
360 else
361 echo &quot;success: xdg-mime report correct mime type $mimetype for motor file&quot;
362 fi
363
364 desktop=$(xdg-mime query default &quot;$mimetype&quot;)
365
366 if [ &quot;$mydesktopfile&quot; != &quot;$desktop&quot; ]; then
367 retval=1
368 echo &quot;error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile&quot;
369 else
370 echo &quot;success: xdg-mime agree motor file should be handled by $mydesktopfile&quot;
371 fi
372
373 exit $retval
374 &lt;/pre&gt;
375
376 &lt;p&gt;It is a simple way to ensure your users are not very surprised when
377 they try to open one of your file formats in their file browser.&lt;/p&gt;
378
379 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
380 activities, please send Bitcoin donations to my address
381 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
382 </description>
383 </item>
384
385 <item>
386 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive</title>
387 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</link>
388 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</guid>
389 <pubDate>Sun, 22 Jan 2023 23:55:00 +0100</pubDate>
390 <description>&lt;p&gt;While reading a
391 &lt;a href=&quot;https://sneak.berlin/20230115/macos-scans-your-local-files-now/&quot;&gt;blog
392 post claiming MacOS X recently started scanning local files and
393 reporting information about them to Apple&lt;/a&gt;, even on a machine where
394 all such callback features had been disabled, I came across a
395 description of the Little Snitch application for MacOS X. It seemed
396 like a very nice tool to have in the tool box, and I decided to see if
397 something similar was available for Linux.&lt;/p&gt;
398
399 &lt;p&gt;It did not take long to find
400 &lt;a href=&quot;https://github.com/evilsocket/opensnitch&quot;&gt;the OpenSnitch
401 package&lt;/a&gt;, which has been in development since 2017, and now is in
402 version 1.5.0. It has had a
403 &lt;a href=&quot;https://bugs.debian.org/909567&quot;&gt;request for Debian
404 packaging&lt;/a&gt; since 2018, but no-one completed the job so far. Just
405 for fun, I decided to see if I could help, and I was very happy to
406 discover that
407 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/304&quot;&gt;upstream
408 want a Debian package too&lt;/a&gt;.&lt;/p&gt;
409
410 &lt;p&gt;After struggling a bit with getting the program to run, figuring
411 out building Go programs (and a little failed detour to look at eBPF
412 builds too - help needed), I am very happy to report that I am
413 sponsoring upstream to maintain the package in Debian, and it has
414 since this morning been waiting in NEW for the ftpmasters to have a
415 look. Perhaps it can get into the archive in time for the Bookworm
416 release?&lt;/p&gt;
417
418 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
419 activities, please send Bitcoin donations to my address
420 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
421 </description>
422 </item>
423
424 <item>
425 <title>LinuxCNC MQTT publisher component</title>
426 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</link>
427 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</guid>
428 <pubDate>Sun, 8 Jan 2023 19:30:00 +0100</pubDate>
429 <description>&lt;p&gt;I watched &lt;a href=&quot;https://yewtu.be/watch?v=jmKUV3aNLjk&quot;&gt;a 2015
430 video from Andreas Schiffler&lt;/a&gt; the other day, where he set up
431 &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;LinuxCNC&lt;/a&gt; to send status
432 information to the MQTT broker IBM Bluemix. As I also use MQTT for
433 graphing, it occured to me that a generic MQTT LinuxCNC component
434 would be useful and I set out to implement it. Today I got the first
435 draft limping along and submitted as
436 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/2253&quot;&gt;a patch to the
437 LinuxCNC project&lt;/a&gt;.&lt;/p&gt;
438
439 &lt;p&gt;The simple part was setting up the MQTT publishing code in Python.
440 I already have set up other parts submitting data to my Mosquito MQTT
441 broker, so I could reuse that code. Writing a LinuxCNC component in
442 Python as new to me, but using existing examples in the code
443 repository and the extensive documentation, this was fairly straight
444 forward. The hardest part was creating a automated test for the
445 component to ensure it was working. Testing it in a simulated
446 LinuxCNC machine proved very useful, as I discovered features I needed
447 that I had not thought of yet, and adjusted the code quite a bit to
448 make it easier to test without a operational MQTT broker
449 available.&lt;/p&gt;
450
451 &lt;p&gt;The draft is ready and working, but I am unsure which LinuxCNC HAL
452 pins I should collect and publish by default (in other words, the
453 default set of information pieces published), and how to get the
454 machine name from the LinuxCNC INI file. The latter is a minor
455 detail, but I expect it would be useful in a setup with several
456 machines available. I am hoping for feedback from the experienced
457 LinuxCNC developers and users, to make the component even better
458 before it can go into the mainland LinuxCNC code base.&lt;/p&gt;
459
460 &lt;p&gt;Since I started on the MQTT component, I came across
461 &lt;a href=&quot;https://yewtu.be/watch?v=Bqa2grG0XtA&quot;&gt;another video from Kent
462 VanderVelden&lt;/a&gt; where he combine LinuxCNC with a set of screen glasses
463 controlled by a Raspberry Pi, and it occured to me that it would
464 be useful for such use cases if LinuxCNC also provided a REST API for
465 querying its status. I hope to start on such component once the MQTT
466 component is working well.&lt;/p&gt;
467
468 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
469 activities, please send Bitcoin donations to my address
470 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
471 </description>
472 </item>
473
474 <item>
475 <title>ONVIF IP camera management tool finally in Debian</title>
476 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</link>
477 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</guid>
478 <pubDate>Sat, 24 Dec 2022 08:00:00 +0100</pubDate>
479 <description>&lt;p&gt;Merry Christmas to you all. Here is a small gift to all those with
480 IP cameras following the &lt;a href=&quot;https://www.onvif.org/&quot;&gt;ONVIF
481 specification&lt;/a&gt;. There is finally a nice command line and GUI tool
482 in Debian to manage ONVIF IP cameras. After working with upstream for
483 a few months and sponsoring the upload, I am very happy to report that
484 the &lt;a href=&quot;https://tracker.debian.org/libonvif&quot;&gt;libonvif package&lt;/a&gt;
485 entered Debian Sid last night.&lt;/p&gt;
486
487 &lt;p&gt;The package provide a C library to communicate with such cameras, a
488 command line tool to locate and update settings of (like password) the
489 cameras and a GUI tool to configure and control the units as well as
490 preview the video from the camera. Libonvif is available on Both
491 Linux and Windows and the GUI tool uses the Qt library. The main
492 competitors are non-free software, while libonvif is GNU GPL licensed.
493 I am very glad Debian users in the future can control their cameras
494 using a free software system provided by Debian. But the ONVIF world
495 is full of slightly broken firmware, where the cameras pretend to
496 follow the ONVIF specification but fail to set some configuration
497 values or refuse to provide video to more than one recipient at the
498 time, and the onvif project is quite young and might take a while
499 before it completely work with your camera. Upstream seem eager to
500 improve the library, so handling any broken camera might be just &lt;a
501 href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;a bug report away&lt;/a&gt;.&lt;/p&gt;
502
503 &lt;p&gt;The package just cleared NEW, and need a new source only upload
504 before it can enter testing. This will happen in the next few
505 days.&lt;/p&gt;
506
507 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
508 activities, please send Bitcoin donations to my address
509 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
510 </description>
511 </item>
512
513 <item>
514 <title>Managing and using ONVIF IP cameras with Linux</title>
515 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</link>
516 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</guid>
517 <pubDate>Wed, 19 Oct 2022 12:30:00 +0200</pubDate>
518 <description>&lt;p&gt;Recently I have been looking at how to control and collect data
519 from a handful IP cameras using Linux. I both wanted to change their
520 settings and to make their imagery available via a free software
521 service under my control. Here is a summary of the tools I found.&lt;/p&gt;
522
523 &lt;p&gt;First I had to identify the cameras and their protocols. As far as
524 I could tell, they were using some SOAP looking protocol and their
525 internal web server seem to only work with Microsoft Internet Explorer
526 with some proprietary binary plugin, which in these days of course is
527 a security disaster and also made it impossible for me to use the
528 camera web interface. Luckily I discovered that the SOAP looking
529 protocol is actually following &lt;a href=&quot;https://www.onvif.org/&quot;&gt;the
530 ONVIF specification&lt;/a&gt;, which seem to be supported by a lot of IP
531 cameras these days.&lt;/p&gt;
532
533 &lt;p&gt;Once the protocol was identified, I was able to find what appear to
534 be the most popular way to configure ONVIF cameras, the free software
535 Windows tool named
536 &lt;a href=&quot;https://sourceforge.net/projects/onvifdm/&quot;&gt;ONVIF Device
537 Manager&lt;/a&gt;. Lacking any other options at the time, I tried
538 unsuccessfully to get it running using Wine, but was missing a dotnet
539 40 library and I found no way around it to run it on Linux.&lt;/p&gt;
540
541 &lt;p&gt;The next tool I found to configure the cameras were a non-free Linux Qt
542 client &lt;a href=&quot;https://www.lingodigit.com/onvif_nvcdemo.html&quot;&gt;ONVIF
543 Device Tool&lt;/a&gt;. I did not like its terms of use, so did not spend
544 much time on it.&lt;/p&gt;
545
546 &lt;p&gt;To collect the video and make it available in a web interface, I
547 found the Zoneminder tool in Debian. A recent version was able to
548 automatically detect and configure ONVIF devices, so I could use it to
549 set up motion detection in and collection of the camera output. I had
550 initial problems getting the ONVIF autodetection to work, as both
551 Firefox and Chromium &lt;a href=&quot;https://bugs.debian.org/1001188&quot;&gt;refused
552 the inter-tab communication&lt;/a&gt; being used by the Zoneminder web
553 pages, but managed to get konqueror to work. Apparently the &quot;Enhanced
554 Tracking Protection&quot; in Firefox cause the problem. I ended up
555 upgrading to the Bookworm edition of Zoneminder in the process to try
556 to fix the issue, and believe the problem might be solved now.&lt;/p&gt;
557
558 &lt;p&gt;In the process I came across the nice Linux GUI tool
559 &lt;a href=&quot;https://gitlab.com/caspermeijn/onvifviewer/&quot;&gt;ONVIF Viewer&lt;/a&gt;
560 allowing me to preview the camera output and validate the login
561 passwords required. Sadly its author has grown tired of maintaining
562 the software, so it might not see any future updates. Which is sad,
563 as the viewer is sightly unstable and the picture tend to lock up.
564 Note, this lockup might be due to limitations in the cameras and not
565 the viewer implementation. I suspect the camera is only able to
566 provide pictures to one client at the time, and the Zoneminder feed
567 might interfere with the GUI viewer. I have
568 &lt;a href=&quot;https://bugs.debian.org/1000820&quot;&gt;asked for the tool to be
569 included in Debian&lt;/a&gt;.&lt;/p&gt;
570
571 &lt;p&gt;Finally, I found what appear to be very nice Linux free software
572 replacement for the Windows tool, named
573 &lt;a href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;libonvif&lt;/a&gt;. It
574 provide a C library to talk to ONVIF devices as well as a command line
575 and GUI tool using the library. Using the GUI tool I was able to change
576 the admin passwords and update other settings of the cameras. I have
577 &lt;a href=&quot;https://bugs.debian.org/1021980&quot;&gt;asked for the package to be
578 included in Debian&lt;/a&gt;.&lt;/p&gt;
579
580 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
581 activities, please send Bitcoin donations to my address
582 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
583
584 &lt;p&gt;&lt;strong&gt;Update 2022-10-20&lt;/strong&gt;: Since my initial publication of
585 this text, I got several suggestions for more free software Linux
586 tools. There is &lt;a href=&quot;https://github.com/quatanium/python-onvif&quot;&gt;a
587 ONVIF python library&lt;/a&gt; (already
588 &lt;a href=&quot;https://bugs.debian.org/824240&quot;&gt;requested into Debian&lt;/a&gt;) and
589 &lt;a href=&quot;https://github.com/FalkTannhaeuser/python-onvif-zeep&quot;&gt;a python 3
590 fork&lt;/a&gt; using a different SOAP dependency. There is also
591 &lt;a href=&quot;https://www.home-assistant.io/integrations/onvif/&quot;&gt;support for
592 ONVIF in Home Assistant&lt;/a&gt;, and there is an alternative to Zoneminder
593 called &lt;a href=&quot;https://www.shinobi.video/&quot;&gt;Shinobi&lt;/a&gt;. The latter
594 two are not included in Debian either. I have not tested any of these
595 so far.&lt;/p&gt;
596 </description>
597 </item>
598
599 <item>
600 <title>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
601 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
602 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
603 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
604 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
605
606 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
607
608 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
609 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
610 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
611 english text is updated, and it is time to start working on the
612 translations. Around 37 percent of the strings have been updated, one
613 way or another, and the translations starting from a complete Debian Buster
614 edition now need to bring their translation up from 63% to 100%. The
615 complete book is licensed using a Creative Commons license, and has
616 been published in several languages over the years. The translations
617 are done by volunteers to bring Linux in their native tongue. The
618 last time I checked, it complete text was available in English,
619 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
620 In addition, work has been started for Arabic (Morocco), Catalan,
621 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
622 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
623 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
624
625 &lt;p&gt;The translation is conducted on
626 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
627 hosted weblate project page&lt;/a&gt;. Prospective translators are
628 recommeded to subscribe to
629 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
630 translators mailing list&lt;/a&gt; and should also check out
631 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
632 contributors&lt;/a&gt;.&lt;/p&gt;
633
634 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
635 have just started. Your contribution is most welcome.&lt;/p&gt;
636
637 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
638 activities, please send Bitcoin donations to my address
639 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
640 </description>
641 </item>
642
643 <item>
644 <title>Automatic LinuxCNC servo PID tuning?</title>
645 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
646 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
647 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
648 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
649 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
650 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
651 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
652 that control such mathematical machinery that a PID controller is. It
653 proved to be a lot harder than I hoped, and I still have not succeeded
654 in getting the Z PID controller to successfully defy gravity, nor X
655 and Y to move accurately and reliably. But while climbing up this
656 rather steep learning curve, I discovered that some motor control
657 systems are able to tune their PID controllers. I got the impression
658 from the documentation that LinuxCNC were not. This proved to be not
659 true.&lt;/p&gt;
660
661 &lt;p&gt;The LinuxCNC
662 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
663 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
664 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
665 &lt;tt&gt;bias&lt;/tt&gt;, &lt;tt&gt;FF0&lt;/tt&gt;, &lt;tt&gt;FF1&lt;/tt&gt;, &lt;tt&gt;FF2&lt;/tt&gt; and
666 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
667 state, and all of these need to have a sensible value for the
668 controller to behave properly. Note, there are even more values
669 involved, theser are just the most important ones. In my case I need
670 the X, Y and Z axes to follow the requested path with little error.
671 This has proved quite a challenge for someone who have never tuned a
672 PID controller before, but there is at least some help to be found.
673
674 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
675 at_pid claiming to have auto tuning capabilities. Sadly it had been
676 neglected since 2011, and could not be used as a plug in replacement
677 for the default pid component. One would have to rewriting the
678 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
679 to quickly test auto tuning to see if it did a better job than me at
680 figuring out good P, I and D values to use.&lt;/p&gt;
681
682 &lt;p&gt;I decided to have a look if the situation could be improved. This
683 involved trying to understand the code and history of the pid and
684 at_pid components. Apparently they had a common ancestor, as code
685 structure, comments and variable names were quite close to each other.
686 Sadly this was not reflected in the git history, making it hard to
687 figure out what really happened. My guess is that the author of
688 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c&quot;&gt;at_pid.c&lt;/a&gt;
689 took a version of
690 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
691 rewrote it to follow the structure he wished pid.c to have, then added
692 support for auto tuning and finally got it included into the LinuxCNC
693 repository. The restructuring and lack of early history made it
694 harder to figure out which part of the code were relevant to the auto
695 tuning, and which part of the code needed to be updated to work the
696 same way as the current pid.c implementation. I started by trying to
697 isolate relevant changes in pid.c, and applying them to at_pid.c. My
698 aim was to make sure the at_pid component could replace the pid
699 component with a simple change in the HAL setup loadrt line, without
700 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
701 hours following this approach, I had learned quite a lot about the
702 code structure of both components, while concluding I was heading down
703 the wrong rabbit hole, and should get back to the surface and find a
704 different path.&lt;/p&gt;
705
706 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
707 related part of the original at_pid.c, and instead isolate and lift
708 the auto tuning part of the code and inject it into a copy of pid.c.
709 This ensured compatibility with the current pid component, while
710 adding auto tuning as a run time option. To make it easier to identify
711 the relevant parts in the future, I wrapped all the auto tuning code
712 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
713 pid component by default, as that part of the code is identical. The
714 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
715 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
716
717 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
718 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
719 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
720 back, and see what the auto tuning code will do. I do not know the
721 mathematical foundation of the at_pid algorithm, but from observation
722 I can tell that the algorithm will, when enabled, produce a square
723 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
724 of the PID controller. This can be seen using the HAL Scope provided
725 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
726 to the motor controller, which in turn is translated into motor speed.
727 So at_pid will ask the motor to move the axis back and forth. The
728 number of cycles in the pattern is controlled by the
729 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
730 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
731 change the direction of a physical object instantly (as in going
732 directly from a positive voltage to the equivalent negative voltage)
733 do not change velocity instantly, and it take some time for the object
734 to slow down and move in the opposite direction. This result in a
735 more smooth movement wave form, as the axis in question were vibrating
736 back and forth. When the axis reached the target speed in the
737 opposing direction, the auto tuner change direction again. After
738 several of these changes, the average time delay between the &#39;peaks&#39;
739 and &#39;valleys&#39; of this movement graph is then used to calculate
740 proposed values for Pgain, Igain and Dgain, and insert them into the
741 HAL model to use by the pid controller. The auto tuned settings are
742 not great, but htye work a lot better than the values I had been able
743 to cook up on my own, at least for the horizontal X and Y axis. But I
744 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
745 controllers error out if the voltage change too quickly. I&#39;ve been
746 less lucky with the Z axis, which is moving a heavy object up and
747 down, and seem to confuse the algorithm. The Z axis movement became a
748 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
749 gravitational drag, but I will have to work a lot more on the Z axis
750 PID values.&lt;/p&gt;
751
752 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
753 tuning. Lets say the HAL configuration in question load the PID
754 component for X, Y and Z like this:&lt;/p&gt;
755
756 &lt;blockquote&gt;&lt;pre&gt;
757 loadrt pid names=pid.x,pid.y,pid.z
758 &lt;/pre&gt;&lt;/blockquote&gt;
759
760 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
761 look like this:&lt;/p&gt;
762
763 &lt;blockquote&gt;&lt;pre&gt;
764 loadrt at_pid names=pid.x,pid.y,pid.z
765 &lt;/pre&gt;&lt;/blockquote&gt;
766
767 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
768 components are referenced by name. If the component had used count=3
769 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
770
771 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
772 range, to make sure it do not hit anything when it start moving back
773 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
774 output range. I used 0.1 as my initial value. Next, assign 1 to the
775 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
776 part and feed 0 to the output pin, which in my case initially caused a
777 lot of drift. In my case it proved to be a good idea with X and Y to
778 tune the motor driver to make sure 0 voltage stopped the motor
779 rotation. On the other hand, for the Z axis this proved to be a bad
780 idea, so it will depend on your setup. It might help to set the
781 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
782 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
783 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
784 your axis will vibrate for a few seconds and when it is done, new
785 values for Pgain, Igain and Dgain will be active. To test them,
786 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
787 machine to suddenly jerk as it bring the axis back to its commanded
788 position, which it might have drifted away from during tuning. To
789 summarize with some halcmd lines:&lt;/p&gt;
790
791 &lt;blockquote&gt;&lt;pre&gt;
792 setp pid.x.tune-effort 0.1
793 setp pid.x.tune-mode 1
794 setp pid.x.tune-start 1
795 # wait for the tuning to complete
796 setp pid.x.tune-mode 0
797 &lt;/pre&gt;&lt;/blockquote&gt;
798
799 &lt;p&gt;After doing this task quite a few times while trying to figure out
800 how to properly tune the PID controllers on the machine in, I decided
801 to figure out if this process could be automated, and wrote a script
802 to do the entire tuning process from power on. The end result will
803 ensure the machine is powered on and ready to run, home all axis if it
804 is not already done, check that the extra tuning pins are available,
805 move the axis to its mid point, run the auto tuning and re-enable the
806 pid controller when it is done. It can be run several times. Check
807 out the
808 &lt;a href=&quot;https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner&quot;&gt;run-auto-pid-tuner&lt;/a&gt;
809 script on github if you want to learn how it is done.&lt;/p&gt;
810
811 &lt;p&gt;My hope is that this little adventure can inspire someone who know
812 more about motor PID controller tuning can implement even better
813 algorithms for automatic PID tuning in LinuxCNC, making life easier
814 for both me and all the others that want to use LinuxCNC but lack the
815 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
816
817 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
818 activities, please send Bitcoin donations to my address
819 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
820 </description>
821 </item>
822
823 <item>
824 <title>LinuxCNC translators life just got a bit easier</title>
825 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
826 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
827 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
828 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
829 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
830 proposed to change the documentation build system make life easier for
831 translators. The original system consisted of independently written
832 documentation files for each language, with no automated way to track
833 changes done in other translations and no help for the translators to
834 know how much was left to translated. By using
835 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
836 files from the English documentation, this can be improved. A small
837 team of LinuxCNC contributors got together and today our labour
838 finally payed off. Since a few hours ago, it is now possible to
839 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
840 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
841
842 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
843 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
844
845 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
846 activities, please send Bitcoin donations to my address
847 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
848 </description>
849 </item>
850
851 <item>
852 <title>geteltorito make CD firmware upgrades a breeze</title>
853 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
854 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
855 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
856 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
857 located the firmware download page from Lenovo (which annoyingly do
858 not allow access via Tor, forcing me to hand them more personal
859 information that I would like). The
860 &lt;a href=&quot;https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso&amp;SearchType=Customer search&amp;searchLocation=Masthead&quot;&gt;download
861 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
862 when all I got available is a USB memory stick. I tried booting the
863 ISO as a USB stick, but this did not work. But genisoimage came to
864 the rescue.&lt;/p&gt;
865
866 &lt;P&gt;The geteltorito program in
867 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
868 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
869 USB stick using a simple command line recipe, which I then can write
870 to the most recently inserted USB stick:&lt;/p&gt;
871
872 &lt;blockquote&gt;&lt;pre&gt;
873 geteltorito -o usbstick.img lenovo-firmware.iso
874 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
875 &lt;/pre&gt;&lt;/blockquote&gt;
876
877 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
878 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
879 </description>
880 </item>
881
882 <item>
883 <title>Run your industrial metal working machine using Debian?</title>
884 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
885 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
886 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
887 <description>&lt;p&gt;After many months of hard work by the good people involved in
888 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
889 system was accepted Sunday
890 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
891 Once it was available from Debian, I was surprised to discover from
892 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
893 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
894 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
895 be a good place to check out, but sadly is not working when visiting
896 via Tor.&lt;/p&gt;
897
898 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
899 Wikipedia quote is in place?&lt;/p&gt;
900
901 &lt;blockquote&gt;
902 &quot;LinuxCNC is a software system for numerical control of
903 machines such as milling machines, lathes, plasma cutters, routers,
904 cutting machines, robots and hexapods. It can control up to 9 axes or
905 joints of a CNC machine using G-code (RS-274NGC) as input. It has
906 several GUIs suited to specific kinds of usage (touch screen,
907 interactive development).&quot;
908 &lt;/blockquote&gt;
909
910 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
911 page indicate that it can only work with hard real time kernel
912 features, it can also work with the user space soft real time features
913 provided by the Debian kernel.
914 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
915 available from Github. The last few months I&#39;ve been involved in the
916 translation setup for the program and documentation. Translators are
917 most welcome to
918 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
919 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
920
921 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
922 activities, please send Bitcoin donations to my address
923 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
924 </description>
925 </item>
926
927 <item>
928 <title>Debian still an excellent choice for Lego builders</title>
929 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
930 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
931 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
932 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
933 the packages under the team umbrella has been updated to fix
934 packaging, lintian issues and BTS reports. In addition, a new and
935 inspiring team member appeared on both the
936 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
937 Team mailing list&lt;/a&gt; and
938 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
939 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
940 Mindstorms programming, check out the
941 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
942 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
943
944 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
945 even the first one in more than ten years, and old upstreams was
946 released with new ones. There are still a lot of work left, and the
947 team welcome more members to help us make sure Debian is the Linux
948 distribution of choice for Lego builders. If you want to contribute,
949 join us in the IRC channel and become part of
950 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
951 Salsa&lt;/a&gt;.&lt;/p&gt;
952
953 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
954 activities, please send Bitcoin donations to my address
955 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
956 </description>
957 </item>
958
959 <item>
960 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
961 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
962 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
963 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
964 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
965 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
966 I am not sure which one of these are completely proof read, but the
967 complete book is available in these languages:
968
969 &lt;ul&gt;
970
971 &lt;li&gt;English&lt;/li&gt;
972 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
973 &lt;li&gt;German&lt;/li&gt;
974 &lt;li&gt;Indonesian&lt;/li&gt;
975 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
976 &lt;li&gt;Spanish&lt;/li&gt;
977
978 &lt;/ul&gt;
979
980 &lt;p&gt;This is the list of languages more than 70% complete, in other
981 words with not too much left to do:&lt;/p&gt;
982
983 &lt;ul&gt;
984
985 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
986 &lt;li&gt;French - 79%&lt;/li&gt;
987 &lt;li&gt;Italian - 79%&lt;/li&gt;
988 &lt;li&gt;Japanese - 77%&lt;/li&gt;
989 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
990 &lt;li&gt;Persian - 71%&lt;/li&gt;
991
992 &lt;/ul&gt;
993
994 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
995
996 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
997
998 &lt;ul&gt;
999
1000 &lt;li&gt;Russian - 63%&lt;/li&gt;
1001 &lt;li&gt;Swedish - 53%&lt;/li&gt;
1002 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
1003 &lt;li&gt;Catalan - 45%&lt;/li&gt;
1004
1005 &lt;/ul&gt;
1006
1007 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
1008
1009 &lt;ul&gt;
1010
1011 &lt;li&gt;Dutch - 26%&lt;/li&gt;
1012 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
1013 &lt;li&gt;Polish - 23%&lt;/li&gt;
1014 &lt;li&gt;Czech - 22%&lt;/li&gt;
1015 &lt;li&gt;Turkish - 18%&lt;/li&gt;
1016
1017 &lt;/ul&gt;
1018
1019 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
1020
1021 &lt;ul&gt;
1022
1023 &lt;li&gt;Korean - 4%&lt;/li&gt;
1024 &lt;li&gt;Croatian - 2%&lt;/li&gt;
1025 &lt;li&gt;Greek - 2%&lt;/li&gt;
1026 &lt;li&gt;Danish - 1%&lt;/li&gt;
1027 &lt;li&gt;Romanian - 1%&lt;/li&gt;
1028
1029 &lt;/ul&gt;
1030
1031 &lt;p&gt;If you want to help provide a Debian instruction book in your own
1032 language, visit
1033 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
1034 to contribute to the translations.&lt;/p&gt;
1035
1036 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1037 activities, please send Bitcoin donations to my address
1038 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1039 </description>
1040 </item>
1041
1042 <item>
1043 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
1044 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
1045 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
1046 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
1047 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
1048 others, the decentralized communication platform
1049 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
1050 (earlier known as Ring), managed to get
1051 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
1052 into Debian Testing. Several of its dependencies has caused build and
1053 propagation problems, which all seem to be solved now.&lt;/p&gt;
1054
1055 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
1056 bittorrent is decentralized, I first of all like how it is not
1057 connected to external IDs like phone numbers. This allow me to set up
1058 computers to send me notifications using Jami without having to find
1059 get a phone number for each computer. Automatic notification via Jami
1060 is also made trivial thanks to the provided client side API (as a DBus
1061 service). Here is my bourne shell script demonstrating how to let any
1062 system send a message to any Jami address. It will create a new
1063 identity before sending the message, if no Jami identity exist
1064 already:&lt;/p&gt;
1065
1066 &lt;p&gt;&lt;pre&gt;
1067 #!/bin/sh
1068 #
1069 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
1070 #
1071 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
1072 # missing.
1073 #
1074 # License: GPL v2 or later at your choice
1075 # Author: Petter Reinholdtsen
1076
1077
1078 if [ -z &quot;$HOME&quot; ] ; then
1079 echo &quot;error: missing \$HOME, required for dbus to work&quot;
1080 exit 1
1081 fi
1082
1083 # First, get dbus running if not already running
1084 DBUSLAUNCH=/usr/bin/dbus-launch
1085 PIDFILE=/run/asterisk/dbus-session.pid
1086 if [ -e $PIDFILE ] ; then
1087 . $PIDFILE
1088 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
1089 unset DBUS_SESSION_BUS_ADDRESS
1090 fi
1091 fi
1092 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
1093 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
1094 dbus-daemon --session --address=&quot;$DBUS_SESSION_BUS_ADDRESS&quot; --nofork --nopidfile --syslog-only &lt; /dev/null &gt; /dev/null 2&gt;&amp;1 3&gt;&amp;1 &amp;
1095 DBUS_SESSION_BUS_PID=$!
1096 (
1097 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1098 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
1099 echo export DBUS_SESSION_BUS_ADDRESS
1100 ) &gt; $PIDFILE
1101 . $PIDFILE
1102 fi &amp;
1103
1104 dringop() {
1105 part=&quot;$1&quot;; shift
1106 op=&quot;$1&quot;; shift
1107 dbus-send --session \
1108 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1109 }
1110
1111 dringopreply() {
1112 part=&quot;$1&quot;; shift
1113 op=&quot;$1&quot;; shift
1114 dbus-send --session --print-reply \
1115 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1116 }
1117
1118 firstaccount() {
1119 dringopreply ConfigurationManager getAccountList | \
1120 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
1121 }
1122
1123 account=$(firstaccount)
1124
1125 if [ -z &quot;$account&quot; ] ; then
1126 echo &quot;Missing local account, trying to create it&quot;
1127 dringop ConfigurationManager addAccount \
1128 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
1129 account=$(firstaccount)
1130 if [ -z &quot;$account&quot; ] ; then
1131 echo &quot;unable to create local account&quot;
1132 exit 1
1133 fi
1134 fi
1135
1136 # Not using dringopreply to ensure $2 can contain spaces
1137 dbus-send --print-reply --session \
1138 --dest=cx.ring.Ring \
1139 /cx/ring/Ring/ConfigurationManager \
1140 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1141 string:&quot;$account&quot; string:&quot;$1&quot; \
1142 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
1143 &lt;/pre&gt;&lt;/p&gt;
1144
1145 &lt;p&gt;If you want to check it out yourself, visit the
1146 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
1147 more, and install the latest Jami client from Debian Unstable or
1148 Testing.&lt;/p&gt;
1149
1150 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1151 activities, please send Bitcoin donations to my address
1152 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1153 </description>
1154 </item>
1155
1156 <item>
1157 <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
1158 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1159 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1160 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
1161 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
1162
1163 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
1164 became the first translation published on paper of the new Buster
1165 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1166 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
1167 some days ago, and it looked good, so now the book is approved for
1168 general distribution. This updated paperback edition &lt;a
1169 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
1170 lulu.com&lt;/a&gt;. The book is also available for download in electronic
1171 form as PDF, EPUB and Mobipocket, and can also be
1172 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
1173
1174 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
1175 which concludes several months of work by several volunteers. The
1176 number of Linux related books published in Norwegian are few, and I
1177 really hope this one will gain many readers, as it is packed with deep
1178 knowledge on Linux and the Debian ecosystem. The book will be
1179 available for various Internet book stores like Amazon and Barnes &amp;
1180 Noble soon, but I recommend buying
1181 &quot;&lt;a href=&quot;https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-9j7qwq.html&quot;&gt;Håndbok
1182 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
1183
1184 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1185 activities, please send Bitcoin donations to my address
1186 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1187 </description>
1188 </item>
1189
1190 <item>
1191 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
1192 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
1193 <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>
1194 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
1195 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
1196 of the Norwegian translation for
1197 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1198 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
1199 reading, I consider the proof reading complete enough for us to move
1200 to the next step, and have asked for the print version to be prepared
1201 and sent of to the print on demand service lulu.com. While it is
1202 still not to late if you find any incorrect translations on
1203 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1204 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
1205 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
1206 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
1207
1208 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
1209 with links available from the web site for the book linked to above.
1210 I hope a lot of readers find it useful.&lt;/p&gt;
1211
1212 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1213 activities, please send Bitcoin donations to my address
1214 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1215 </description>
1216 </item>
1217
1218 <item>
1219 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
1220 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1221 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1222 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
1223 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
1224 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1225 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
1226 new and updated version based on Buster is getting ready. Work on the
1227 updated Norwegian Bokmål edition has been going on for a few months
1228 now, and yesterday, we reached the first mile stone, with 100% of the
1229 texts being translated. A lot of proof reading remains, of course,
1230 but a major step towards a new edition has been taken.&lt;/p&gt;
1231
1232 &lt;p&gt;The book is translated by volunteers, and we would love to get some
1233 help with the proof reading. The translation uses
1234 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1235 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
1236 submit improvements and suggestions. There is also a proof readers
1237 PDF available on request, get in touch if you want to help out that
1238 way.&lt;/p&gt;
1239
1240 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1241 activities, please send Bitcoin donations to my address
1242 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1243 </description>
1244 </item>
1245
1246 <item>
1247 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
1248 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
1249 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
1250 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
1251 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
1252 User Group&lt;/a&gt;, I have the pleasure of receiving the
1253 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
1254 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
1255 several times a year. I rarely have time to read all the articles,
1256 but try to at least skim through them all as there is a lot of nice
1257 knowledge passed on there. I even carry the latest issue with me most
1258 of the time to try to get through all the articles when I have a few
1259 spare minutes.&lt;/p&gt;
1260
1261 &lt;p&gt;The other day I came across a nice article titled
1262 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
1263 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
1264 marvellous idea I hope can make it all the way into the POSIX standard.
1265 The idea is as simple as it is powerful. By introducing a new
1266 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1267 handle setting up TLS connections, one both make it trivial to add TLS
1268 support to any program currently using the POSIX socket API, and gain
1269 system wide control over certificates, TLS versions and encryption
1270 systems used. Instead of doing this:&lt;/p&gt;
1271
1272 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1273 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1274 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1275
1276 &lt;p&gt;the program code would be doing this:&lt;p&gt;
1277
1278 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1279 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1280 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1281
1282 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
1283 would normally modify only 5-10 lines in the code, which is amazing
1284 when compared to using for example the OpenSSL API.&lt;/p&gt;
1285
1286 &lt;p&gt;The project has set up the
1287 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
1288 web site to spread the idea, and the code for a kernel module and the
1289 associated system daemon is available from two github repositories:
1290 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
1291 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
1292 Unfortunately there is no explicit license information with the code,
1293 so its copyright status is unclear. A
1294 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
1295 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
1296
1297 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
1298 understand why it is an advantage to implement this as a kernel module
1299 and system wide service daemon, but can not help to think that it
1300 would be a lot easier to get projects to move to this way of setting
1301 up TLS if it was done with a user space approach where programs
1302 wanting to use this API approach could just link with a wrapper
1303 library.&lt;/p&gt;
1304
1305 &lt;p&gt;I recommend you check out this simple and powerful approach to more
1306 secure network connections. :)&lt;/p&gt;
1307
1308 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1309 activities, please send Bitcoin donations to my address
1310 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1311 </description>
1312 </item>
1313
1314 <item>
1315 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
1316 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
1317 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
1318 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
1319 <description>&lt;p&gt;Half a year ago,
1320 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
1321 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
1322 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
1323 handle both messages, audio and video. It uses distributed hash
1324 tables instead of central infrastructure to connect its users to each
1325 other, which in my book is a plus. I mentioned briefly that it could
1326 also work as a SIP client, which came in handy when the higher
1327 educational sector in Norway started to promote Zoom as its video
1328 conferencing solution. I am reluctant to use the official Zoom client
1329 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
1330 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
1331 to check the security) and benchmark it, and thus prefer to connect to
1332 Zoom meetings with free software clients.&lt;/p&gt;
1333
1334 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
1335 password set on the room. The Jami daemon leak memory like crazy
1336 (approximately 1 GiB a minute) when I am connected to the video
1337 conference, so I had to restart the client every 7-10 minutes, which
1338 is not great. I tried to get other SIP Linux clients to work
1339 without success, so I decided I would have to live with this wart
1340 until someone managed to fix the leak in the dring code base. But
1341 another problem showed up once the rooms were password protected. I
1342 could not get my dial tone signaling through from Jami to Zoom, and
1343 dial tone signaling is used to enter the password when connecting to
1344 Zoom. I tried a lot of different permutations with my Jami and
1345 Asterisk setup to try to figure out why the signaling did not get
1346 through, only to finally discover that the fundamental problem seem to
1347 be that Zoom is simply not able to receive dial tone signaling when
1348 connecting via SIP. There seem to be nothing wrong with the Jami and
1349 Asterisk end, it is simply broken in the Zoom end. I got help from a
1350 very skilled VoIP engineer figuring out this last part. And being a
1351 very skilled engineer, he was also able to locate a solution for me.
1352 Or to be exact, a workaround that solve my initial problem of
1353 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
1354
1355 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
1356 trick is already
1357 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
1358 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
1359 password. What is most surprising about this is that the
1360 automatically generated email from Zoom with instructions on how to
1361 connect via SIP do not mention this. The SIP address to use normally
1362 consist of the room ID (a number), an @ character and the IP address
1363 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1364 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
1365 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
1366 can both enter password, control the layout (full screen, active
1367 presence and gallery) and specify the host key to start the meeting.
1368 The full SIP address entered into Jami to provide the password will
1369 then look like this (all using made up numbers):&lt;/p&gt;
1370
1371 &lt;p&gt;&lt;blockquote&gt;
1372 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
1373 &lt;/blockquote&gt;&lt;/p&gt;
1374
1375 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
1376 recommend this setup to others. :)&lt;/p&gt;
1377
1378 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1379 activities, please send Bitcoin donations to my address
1380 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1381 </description>
1382 </item>
1383
1384 <item>
1385 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
1386 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
1387 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
1388 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
1389 <description>&lt;p&gt;The curiosity got the better of me when
1390 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
1391 reported&lt;/a&gt; that New Jersey was desperately looking for
1392 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
1393 and a few days later it was reported that
1394 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
1395 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
1396
1397 &lt;p&gt;I thus decided to have a look at free software alternatives to
1398 learn COBOL, and had the pleasure to find
1399 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
1400 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
1401 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
1402 transforming COBOL code to C or C++ before giving it to GCC or Visual
1403 Studio to build binaries.&lt;/p&gt;
1404
1405 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
1406 quick response, and also was happy to see a new Debian maintainer
1407 taking over when the original one recently asked to be replaced. A
1408 new Debian upload was done as recently as yesterday.&lt;/p&gt;
1409
1410 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
1411 introduction and make and run simple COBOL programs. It was fun to
1412 learn a new programming language. If you want to test for yourself,
1413 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
1414 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
1415
1416 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
1417 standard compliant it is, but it claim to pass most tests from COBOL
1418 test suite, which sound good to me. It is nice to know it is possible
1419 to learn COBOL using software without any usage restrictions, and I am
1420 very happy such nice free software project as this is available. If
1421 you as me is curious about COBOL, check it out.&lt;/p&gt;
1422
1423 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1424 activities, please send Bitcoin donations to my address
1425 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1426 </description>
1427 </item>
1428
1429 <item>
1430 <title>Jami/Ring, finally functioning peer to peer communication client</title>
1431 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
1432 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
1433 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
1434 <description>&lt;p&gt;Some years ago, in 2016, I
1435 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
1436 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
1437 It would provide messaging without any central server coordinating the
1438 system and without requiring all users to register a phone number or
1439 own a mobile phone. Back then, I could not get it to work, and put it
1440 aside until it had seen more development. A few days ago I decided to
1441 give it another try, and am happy to report that this time I am able
1442 to not only send and receive messages, but also place audio and video
1443 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
1444
1445 &lt;p&gt;The Ring system changed name earlier this year to
1446 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
1447 tried doing web search for &#39;ring&#39; when I discovered it for the first
1448 time, and can only applaud this change as it is impossible to find
1449 something called Ring among the noise of other uses of that word. Now
1450 you can search for &#39;jami&#39; and this client and
1451 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
1452 least on duckduckgo.&lt;/p&gt;
1453
1454 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
1455 calls, and try to send them directly between the communicating parties
1456 if possible. If this proves impossible (for example if both ends are
1457 behind NAT), it will use a central SIP TURN server maintained by the
1458 Jami project. Jami can also be a normal SIP client. If the SIP
1459 server is unencrypted, the audio and video calls will also be
1460 unencrypted. This is as far as I know the only case where Jami will
1461 do anything without encryption.&lt;/p&gt;
1462
1463 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
1464 Android, iOS, and Android TV. It is included in Debian already. Jami
1465 also work for those using F-Droid without any Google connections,
1466 while Signal do not.
1467 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
1468 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
1469 distributed hash table (DHT) system (similar to BitTorrent) running
1470 over UDP. On one of the networks I use, I discovered Jami failed to
1471 work. I tracked this down to the fact that incoming UDP packages
1472 going to ports 1-49999 were blocked, and the DHT would pick a random
1473 port and end up in the low range most of the time. After talking to
1474 the developers, I solved this by enabling the dhtproxy in the
1475 settings, thus using TCP to talk to a central DHT proxy instead of
1476
1477 peering directly with others. I&#39;ve been told the developers are
1478 working on allowing DHT to use TCP to avoid this problem. I also ran
1479 into a problem when trying to talk to the version of Ring included in
1480 Debian Stable (Stretch). Apparently the protocol changed between
1481 beta2 and the current version, making these clients incompatible.
1482 Hopefully the protocol will not be made incompatible in the
1483 future.&lt;/p&gt;
1484
1485 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
1486 came across another communication platform I have not tested yet. The
1487 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
1488 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
1489 become the topic of a future blog post.&lt;/p&gt;
1490
1491 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1492 activities, please send Bitcoin donations to my address
1493 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1494 </description>
1495 </item>
1496
1497 <item>
1498 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
1499 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
1500 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
1501 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
1502 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
1503 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
1504 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
1505 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1506 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1507 nye versjonen kom på nyåret, og ble
1508 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
1509 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
1510 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1511 måtte justeres, men ikke noe alvorlig. Har oppdatert
1512 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
1513 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
1514
1515 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1516 å spille for oss som liker slikt. :)&lt;/p&gt;
1517
1518 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1519 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1520 til min adresse
1521 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
1522 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1523 </description>
1524 </item>
1525
1526 <item>
1527 <title>Debian now got everything you need to program Micro:bit</title>
1528 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
1529 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
1530 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
1531 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
1532 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
1533 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
1534 thanks to the hard work of Nick Morrott and the Debian python
1535 packaging team. The micro:bit project recommend the mu-editor to
1536 program the microcomputer, as this editor will take care of all the
1537 machinery required to injekt/flash micropython alongside the program
1538 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
1539
1540 &lt;p&gt;There are three main pieces involved. The first to enter Debian
1541 was
1542 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
1543 which was accepted into the archive 2019-01-12. The next one was
1544 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
1545 showed up 2019-01-13. The final and hardest part to to into the
1546 archive was
1547 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
1548 which needed to get its build system and dependencies into Debian
1549 before it was accepted 2019-01-20. The last one is already in Debian
1550 Unstable and should enter Debian Testing / Buster in three days. This
1551 all allow any user of the micro:bit to get going by simply running
1552 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
1553 Buster is released as stable, all the users of Debian stable will be
1554 catered for.&lt;/p&gt;
1555
1556 &lt;p&gt;As a minor final touch, I added rules to
1557 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
1558 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
1559 package. This make sure any user of the isenkram desktop daemon will
1560 get a popup suggesting to install mu-editor then the USB cable from
1561 the micro:bit is inserted for the first time.&lt;/p&gt;
1562
1563 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
1564
1565 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1566 activities, please send Bitcoin donations to my address
1567 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1568 </description>
1569 </item>
1570
1571 <item>
1572 <title>Learn to program with Minetest on Debian</title>
1573 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
1574 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
1575 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
1576 <description>&lt;p&gt;A fun way to learn how to program
1577 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
1578 instructions in the book
1579 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
1580 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
1581 who like to play with Minecraft. The book uses a Python library to
1582 talk to a TCP/IP socket with an API accepting build instructions and
1583 providing information about the current players in a Minecraft world.
1584 The TCP/IP API was first created for the Minecraft implementation for
1585 Raspberry Pi, and has since been ported to some server versions of
1586 Minecraft. The book contain recipes for those using Windows, MacOSX
1587 and Raspian. But a little known fact is that you can follow the same
1588 recipes using the free software construction game
1589 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1590
1591 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1592 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1593 use the Python programs coded to talk to Minecraft with Minetest too.
1594 I
1595 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1596 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1597 FTP masters NEW queue, learning to program Python with Minetest on
1598 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1599 maintained as part of the Debian Games team, and
1600 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1601 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1602 Salsa.&lt;/p&gt;
1603
1604 &lt;p&gt;You will most likely need to install several of the Minetest
1605 modules in Debian for the examples included with the library to work
1606 well, as there are several blocks used by the example scripts that are
1607 provided via modules in Minetest. Without the required blocks, a
1608 simple stone block is used instead. My initial testing with a analog
1609 clock did not get gold arms as instructed in the python library, but
1610 instead used stone arms.&lt;/p&gt;
1611
1612 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1613 Minecraft, but were unable to find any working recipes. The
1614 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1615 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1616 working with a standalone Minecraft server setup. Are there any
1617 options to use with the normal desktop version?&lt;/p&gt;
1618
1619 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1620 activities, please send Bitcoin donations to my address
1621 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1622 </description>
1623 </item>
1624
1625 <item>
1626 <title>Time for an official MIME type for patches?</title>
1627 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1628 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1629 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1630 <description>&lt;p&gt;As part of my involvement in
1631 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1632 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1633 emails into a test instance of the archive to see how well this would
1634 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1635 notmuch email database&lt;/a&gt;, all public emails sent to me via
1636 @lists.debian.org, giving me a set of around 216 000 emails to import.
1637 In the process, I had a look at the various attachments included in
1638 these emails, to figure out what to do with attachments, and noticed
1639 that one of the most common attachment formats do not have
1640 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1641 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1642 diff, ie the input for patch, is on the top 10 list of formats
1643 included in these emails. At the moment people seem to use either
1644 text/x-patch or text/x-diff, but neither is officially registered. It
1645 would be better if one official MIME type were registered and used
1646 everywhere.&lt;/p&gt;
1647
1648 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1649 up the topic on
1650 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1651 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1652 which MIME type to use as the official for patch files, or involved in
1653 making software using a MIME type for patches, perhaps you would like
1654 to join the discussion?&lt;/p&gt;
1655
1656 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1657 activities, please send Bitcoin donations to my address
1658 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1659 </description>
1660 </item>
1661
1662 <item>
1663 <title>Automatic Google Drive sync using grive in Debian</title>
1664 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1665 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1666 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1667 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1668 rescue the remains, I helped set up automatic sync with Google Drive.
1669 I did not find any sensible Debian package handling this
1670 automatically, so I rebuild the grive2 source from
1671 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1672 task and added a autostart desktop entry and a small shell script to
1673 run in the background while the user is logged in to do the sync.
1674 Here is a sketch of the setup for future reference.&lt;/p&gt;
1675
1676 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1677 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1678 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1679 to start the sync when the user log in:&lt;/p&gt;
1680
1681 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1682 [Desktop Entry]
1683 Name=Google drive autosync
1684 Type=Application
1685 Exec=/home/user/bin/grive-sync
1686 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1687
1688 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1689 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1690
1691 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1692 #!/bin/sh
1693 set -e
1694 cd ~/
1695 cleanup() {
1696 if [ &quot;$syncpid&quot; ] ; then
1697 kill $syncpid
1698 fi
1699 }
1700 trap cleanup EXIT INT QUIT
1701 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1702 syncpdi=$!
1703 while true; do
1704 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1705 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1706 exit 1
1707 fi
1708 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1709 /usr/lib/grive/grive-sync.sh sync googledrive
1710 fi
1711 sleep 300
1712 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
1713 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1714
1715 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
1716 GNU GPL v2 licensed (or any later version, at your leisure), but I
1717 doubt this code is possible to claim copyright on.&lt;/p&gt;
1718
1719 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1720 activities, please send Bitcoin donations to my address
1721 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1722 </description>
1723 </item>
1724
1725 <item>
1726 <title>Using the Kodi API to play Youtube videos</title>
1727 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
1728 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
1729 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
1730 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
1731 tell it to play a youtube URL I received in a chat, without having to
1732 insert search terms using the on-screen keyboard. After searching the
1733 web for API access to the Youtube plugin and testing a bit, I managed
1734 to find a recipe that worked. If you got a kodi instance with its API
1735 available from http://kodihost/jsonrpc, you can try the following to
1736 have check out a nice cover band.&lt;/p&gt;
1737
1738 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
1739 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
1740 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
1741 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
1742 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1743
1744 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
1745 first argument. It can now handle direct video links, youtube links
1746 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
1747 Chromecast. :)&lt;/p&gt;
1748
1749 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1750 activities, please send Bitcoin donations to my address
1751 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1752 </description>
1753 </item>
1754
1755 <item>
1756 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
1757 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
1758 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
1759 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
1760 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
1761 with my family using a self hosted solution, as it is unacceptable to
1762 place images from my personal life under the control of strangers
1763 working for data hoarders like Google or Dropbox. The last few days I
1764 have drafted an approach that might work out, and I would like to
1765 share it with you. I would like to publish images on a server under
1766 my control, and point some Internet connected display units using some
1767 free and open standard to the images I published. As my primary
1768 language is not limited to ASCII, I need to store metadata using
1769 UTF-8. Many years ago, I hoped to find a digital photo frame capable
1770 of reading a RSS feed with image references (aka using the
1771 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
1772 of such frames. In the end I gave up that approach.&lt;/p&gt;
1773
1774 &lt;p&gt;Some months ago, I discovered that
1775 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
1776 read images from a RSS feed, and used it to set up a screen saver on
1777 my home info screen, showing images from the Daily images feed from
1778 NASA. This proved to work well. More recently I discovered that
1779 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
1780 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
1781 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
1782 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
1783 screen saver capable of reading a RSS feed with images and news. For
1784 fun, I used it this summer to test Kodi on my parents TV by hooking up
1785 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1786 screen saver showing selected pictures from my selection.&lt;/p&gt;
1787
1788 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
1789 a RSS feed for the Kodi instance. I adjusted my &lt;a
1790 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
1791 /var/www/html/privatepictures/, wrote a small Perl script to extract
1792 title and description metadata from the photo files and generate the
1793 RSS file. I ended up using Perl instead of python, as the
1794 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1795 tags I ended up using, while python3-exif did not. The relevant EXIF
1796 tags only support ASCII, so I had to find better alternatives. XMP
1797 seem to have the support I need.&lt;/p&gt;
1798
1799 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
1800 use tags that can be easily added/updated using normal free software
1801 photo managing software. I ended up using the tags set using this
1802 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
1803
1804 &lt;blockquote&gt;&lt;pre&gt;
1805 exiftool -headline=&#39;The RSS image title&#39; \
1806 -description=&#39;The RSS image description.&#39; \
1807 -subject+=for-family photo.jpeg
1808 &lt;/pre&gt;&lt;/blockquote&gt;
1809
1810 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
1811 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
1812 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
1813 shared with my family. Images with this keyword set are located and
1814 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
1815
1816 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
1817 suggestions.&lt;/p&gt;
1818
1819 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1820 activities, please send Bitcoin donations to my address
1821 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1822 </description>
1823 </item>
1824
1825 <item>
1826 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
1827 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
1828 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
1829 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
1830 <description>&lt;p&gt;Last night, I wrote
1831 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
1832 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
1833 During the day I received valuable feedback, and thanks to the
1834 suggestions I have been able to rewrite the recipe into a much simpler
1835 approach requiring no setup at all. It is a single script that take
1836 care of it all.&lt;/p&gt;
1837
1838 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
1839 desktop and stream it to Kodi. This fixed the video quality issue I
1840 saw initially. It further removes the need to add a m3u file on the
1841 Kodi machine, as it instead connects to
1842 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
1843 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
1844 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1845 the script below, run it with the DNS name or IP address of the kodi
1846 server to stream to as the only argument, and watch your screen show
1847 up on the Kodi screen. Note, it depend on multicast on the local
1848 network, so if you need to stream outside the local network, the
1849 script must be modified. Also note, I have no idea if audio work, as
1850 I only care about the picture part.&lt;/p&gt;
1851
1852 &lt;blockquote&gt;&lt;pre&gt;
1853 #!/bin/sh
1854 #
1855 # Stream the Linux desktop view to Kodi. See
1856 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1857 # for backgorund information.
1858
1859 # Make sure the stream is stopped in Kodi and the gstreamer process is
1860 # killed if something go wrong (for example if curl is unable to find the
1861 # kodi server). Do the same when interrupting this script.
1862 kodicmd() {
1863 host=&quot;$1&quot;
1864 cmd=&quot;$2&quot;
1865 params=&quot;$3&quot;
1866 curl --silent --header &#39;Content-Type: application/json&#39; \
1867 --data-binary &quot;{ \&quot;id\&quot;: 1, \&quot;jsonrpc\&quot;: \&quot;2.0\&quot;, \&quot;method\&quot;: \&quot;$cmd\&quot;, \&quot;params\&quot;: $params }&quot; \
1868 &quot;http://$host/jsonrpc&quot;
1869 }
1870 cleanup() {
1871 if [ -n &quot;$kodihost&quot; ] ; then
1872 # Stop the playing when we end
1873 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
1874 jq .result[].playerid)
1875 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
1876 fi
1877 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
1878 kill &quot;$gstpid&quot;
1879 fi
1880 }
1881 trap cleanup EXIT INT
1882
1883 if [ -n &quot;$1&quot; ]; then
1884 kodihost=$1
1885 shift
1886 else
1887 kodihost=kodi.local
1888 fi
1889
1890 mcast=239.255.0.1
1891 mcastport=1234
1892 mcastttl=1
1893
1894 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
1895 cut -d&quot; &quot; -f2|head -1)
1896 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1897 videoconvert ! queue2 ! \
1898 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1899 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1900 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1901 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
1902 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1903 &gt; /dev/null 2&gt;&amp;1 &amp;
1904 gstpid=$!
1905
1906 # Give stream a second to get going
1907 sleep 1
1908
1909 # Ask kodi to start streaming using its JSON-RPC API
1910 kodicmd &quot;$kodihost&quot; Player.Open \
1911 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
1912
1913 # wait for gst to end
1914 wait &quot;$gstpid&quot;
1915 &lt;/pre&gt;&lt;/blockquote&gt;
1916
1917 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
1918
1919 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1920 activities, please send Bitcoin donations to my address
1921 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1922 </description>
1923 </item>
1924
1925 <item>
1926 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
1927 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
1928 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
1929 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
1930 <description>&lt;p&gt;PS: See
1931 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
1932 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
1933
1934 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
1935 my projector connected to Kodi. I sadly had to admit that I had no
1936 idea, as it was a task I never had tried. Since then, I have been
1937 looking for a way to do so, preferable without much extra software to
1938 install on either side. Today I found a way that seem to kind of
1939 work. Not great, but it is a start.&lt;/p&gt;
1940
1941 &lt;p&gt;I had a look at several approaches, for example
1942 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
1943 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
1944 local storage enough to store the stream locally. This is not going
1945 to work well for me, lacking enough free space, and it would
1946 impossible for my friend to get working.&lt;/p&gt;
1947
1948 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
1949 video stream that Kodi could play. Preferably using
1950 broadcast/multicast, to avoid having to change any setup on the Kodi
1951 side when starting such stream. Unfortunately, the only recipe I
1952 could find using multicast used the rtp protocol, and this protocol
1953 seem to not be supported by Kodi.&lt;/p&gt;
1954
1955 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
1956 have to specify the IP address of the streaming machine in both the
1957 sending command and the file on the Kodi server. But it is showing my
1958 desktop, and thus allow us to have a shared look on the big screen at
1959 the programs I work on.&lt;/p&gt;
1960
1961 &lt;p&gt;I did not spend much time investigating codeces. I combined the
1962 rtp and rtsp recipes from
1963 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
1964 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
1965 this working on the desktop/streaming end.&lt;/p&gt;
1966
1967 &lt;blockquote&gt;&lt;pre&gt;
1968 vlc screen:// --sout \
1969 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}&#39;
1970 &lt;/pre&gt;&lt;/blockquote&gt;
1971
1972 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
1973 same IP address:&lt;/p&gt;
1974
1975 &lt;blockquote&gt;&lt;pre&gt;
1976 echo rtsp://192.168.11.4:8080/test.sdp \
1977 &gt; /storage/videos/screenstream.m3u
1978 &lt;/pre&gt;&lt;/blockquote&gt;
1979
1980 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
1981 as I can tell the IP must be hardcoded for this to work. In other
1982 words, if someone elses machine is going to do the steaming, you have
1983 to update screenstream.m3u on the Kodi machine and adjust the vlc
1984 recipe. To get started, locate the file in Kodi and select the m3u
1985 file while the VLC stream is running. The desktop then show up in my
1986 big screen. :)&lt;/p&gt;
1987
1988 &lt;p&gt;When using the same technique to stream a video file with audio,
1989 the audio quality is really bad. No idea if the problem is package
1990 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1991 enough to tell.&lt;/p&gt;
1992
1993 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
1994 succestions and reminded me about an important step. The &quot;screen:&quot;
1995 input source is only available once the vlc-plugin-access-extra
1996 package is installed on Debian. Without it, you will see this error
1997 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
1998 for details.&quot; He further found that it is possible to drop some parts
1999 of the VLC command line to reduce the amount of hardcoded information.
2000 It is also useful to consider using cvlc to avoid having the VLC
2001 window in the desktop view. In sum, this give us this command line on
2002 the source end
2003
2004 &lt;blockquote&gt;&lt;pre&gt;
2005 cvlc screen:// --sout \
2006 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
2007 &lt;/pre&gt;&lt;/blockquote&gt;
2008
2009 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2010
2011 &lt;blockquote&gt;&lt;pre&gt;
2012 echo rtsp://192.168.11.4:8080/ \
2013 &gt; /storage/videos/screenstream.m3u
2014 &lt;/pre&gt;&lt;/blockquote&gt;
2015
2016 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
2017 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
2018 audio quality, so I guess the issue is in the input or transcoding
2019 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
2020 parameters to use more bandwidth, but it did not make a
2021 difference.&lt;/p&gt;
2022
2023 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
2024 gstreamer instead of VLC, and this proved to work great! He also
2025 provided me with the trick to get Kodi to use a multicast stream as
2026 its source. By using this monstrous oneliner, I can stream my desktop
2027 with good video quality in reasonable framerate to the 239.255.0.1
2028 multicast address on port 1234:
2029
2030 &lt;blockquote&gt;&lt;pre&gt;
2031 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
2032 videoconvert ! queue2 ! \
2033 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
2034 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
2035 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
2036 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
2037 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
2038 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
2039 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2040 &lt;/pre&gt;&lt;/blockquote&gt;
2041
2042 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2043
2044 &lt;blockquote&gt;&lt;pre&gt;
2045 echo udp://@239.255.0.1:1234 \
2046 &gt; /storage/videos/screenstream.m3u
2047 &lt;/pre&gt;&lt;/blockquote&gt;
2048
2049 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
2050 pick the one you need. This approach will of course lead to trouble
2051 if more than one source uses the same multicast port and address.
2052 Note the ttl-mc=1 setting, which limit the multicast packages to the
2053 local network. If the value is increased, your screen will be
2054 broadcasted further, one network &quot;hop&quot; for each increase (read up on
2055 multicast to learn more. :)!&lt;/p&gt;
2056
2057 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
2058 could use this VLC command to stream to the same multicast address.
2059 The image quality is way better than the rtsp approach, but gstreamer
2060 seem to be doing a better job.&lt;/p&gt;
2061
2062 &lt;blockquote&gt;&lt;pre&gt;
2063 cvlc screen:// --sout &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}&#39;
2064 &lt;/pre&gt;&lt;/blockquote&gt;
2065
2066 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2067 activities, please send Bitcoin donations to my address
2068 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2069 </description>
2070 </item>
2071
2072 <item>
2073 <title>What is the most supported MIME type in Debian in 2018?</title>
2074 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
2075 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
2076 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
2077 <description>&lt;p&gt;Five years ago,
2078 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
2079 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
2080 analysing the desktop files in all packages in the archive. Since
2081 then, the DEP-11 AppStream system has been put into production, making
2082 the task a lot easier. This made me want to repeat the measurement,
2083 to see how much things changed. Here are the new numbers, for
2084 unstable only this time:
2085
2086 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2087
2088 &lt;pre&gt;
2089 count MIME type
2090 ----- -----------------------
2091 56 image/jpeg
2092 55 image/png
2093 49 image/tiff
2094 48 image/gif
2095 39 image/bmp
2096 38 text/plain
2097 37 audio/mpeg
2098 34 application/ogg
2099 33 audio/x-flac
2100 32 audio/x-mp3
2101 30 audio/x-wav
2102 30 audio/x-vorbis+ogg
2103 29 image/x-portable-pixmap
2104 27 inode/directory
2105 27 image/x-portable-bitmap
2106 27 audio/x-mpeg
2107 26 application/x-ogg
2108 25 audio/x-mpegurl
2109 25 audio/ogg
2110 24 text/html
2111 &lt;/pre&gt;
2112
2113 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
2114 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
2115 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
2116
2117 &lt;p&gt;It is interesting to see how image formats have passed text/plain
2118 as the most announced supported MIME type. These days, thanks to the
2119 AppStream system, if you run into a file format you do not know, and
2120 want to figure out which packages support the format, you can find the
2121 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
2122 look up all packages announcing support for this format in their
2123 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
2124 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
2125 me, want to know which packages support inode/directory, you can get a
2126 list like this:&lt;/p&gt;
2127
2128 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2129 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2130 Package: anjuta
2131 Package: audacious
2132 Package: baobab
2133 Package: cervisia
2134 Package: chirp
2135 Package: dolphin
2136 Package: doublecmd-common
2137 Package: easytag
2138 Package: enlightenment
2139 Package: ephoto
2140 Package: filelight
2141 Package: gwenview
2142 Package: k4dirstat
2143 Package: kaffeine
2144 Package: kdesvn
2145 Package: kid3
2146 Package: kid3-qt
2147 Package: nautilus
2148 Package: nemo
2149 Package: pcmanfm
2150 Package: pcmanfm-qt
2151 Package: qweborf
2152 Package: ranger
2153 Package: sirikali
2154 Package: spacefm
2155 Package: spacefm
2156 Package: vifm
2157 %
2158 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2159
2160 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
2161 format is not yet supported by any package in Debian:&lt;/p&gt;
2162
2163 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2164 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2165 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
2166 %
2167 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2168
2169 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
2170 format:&lt;/p&gt;
2171
2172 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2173 % appstreamcli what-provides mimetype application/sla|grep Package
2174 Package: cura
2175 Package: meshlab
2176 Package: printrun
2177 %
2178 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2179
2180 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
2181
2182 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2183 activities, please send Bitcoin donations to my address
2184 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2185 </description>
2186 </item>
2187
2188 <item>
2189 <title>Debian APT upgrade without enough free space on the disk...</title>
2190 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
2191 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
2192 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
2193 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2194 for a while, and when I need to update it there is not enough free
2195 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
2196 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
2197 upgrade only some of the packages in one batch, until the amount of
2198 packages to download fall below the amount of free space available.
2199 Today, I had about 500 packages to upgrade, and after a while I got
2200 tired of trying to install chunks of packages manually. I concluded
2201 that I did not have the spare hours required to complete the task, and
2202 decided to see if I could automate it. I came up with this small
2203 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
2204
2205 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2206 #!/bin/sh
2207 #
2208 # Upgrade packages when the disk is too full to upgrade every
2209 # upgradable package in one lump. Fetching packages to upgrade using
2210 # apt, and then installing using dpkg, to avoid changing the package
2211 # flag for manual/automatic.
2212
2213 set -e
2214
2215 ignore() {
2216 if [ &quot;$1&quot; ]; then
2217 grep -v &quot;$1&quot;
2218 else
2219 cat
2220 fi
2221 }
2222
2223 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
2224 echo &quot;Upgrading $p&quot;
2225 apt clean
2226 apt install --download-only -y $p
2227 for f in /var/cache/apt/archives/*.deb; do
2228 if [ -e &quot;$f&quot; ]; then
2229 dpkg -i /var/cache/apt/archives/*.deb
2230 break
2231 fi
2232 done
2233 done
2234 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2235
2236 &lt;p&gt;The script will extract the list of packages to upgrade, try to
2237 download the packages needed to upgrade one package, install the
2238 downloaded packages using dpkg. The idea is to upgrade packages
2239 without changing the APT mark for the package (ie the one recording of
2240 the package was manually requested or pulled in as a dependency). To
2241 use it, simply run it as root from the command line. If it fail, try
2242 &#39;apt install -f&#39; to clean up the mess and run the script again. This
2243 might happen if the new packages conflict with one of the old
2244 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
2245
2246 &lt;p&gt;It take one option, a package to ignore in the list of packages to
2247 upgrade. The option to ignore a package is there to be able to skip
2248 the packages that are simply too large to unpack. Today this was
2249 &#39;ghc&#39;, but I have run into other large packages causing similar
2250 problems earlier (like TeX).&lt;/p&gt;
2251
2252 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
2253 alternative ways to handle this. The &quot;unattended-upgrades
2254 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
2255 each package to upgrade, and then upgrade them in order, smallest set
2256 first. It might be a better option than my above mentioned script.
2257 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
2258 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
2259
2260 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2261 activities, please send Bitcoin donations to my address
2262 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2263 </description>
2264 </item>
2265
2266 <item>
2267 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
2268 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
2269 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
2270 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
2271 <description>&lt;p&gt;A new version of the
2272 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
2273 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
2274 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2275 useful. It was uploaded the last few days, and the last update will
2276 enter testing tomorrow. See the
2277 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
2278 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
2279 was announced 6 days ago. We will try to get it into Debian as
2280 well.&lt;/p&gt;
2281
2282 &lt;p&gt;More information related to 3D printing is available on the
2283 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
2284 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
2285 in Debian.&lt;/p&gt;
2286
2287 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2288 activities, please send Bitcoin donations to my address
2289 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2290 </description>
2291 </item>
2292
2293 <item>
2294 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
2295 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
2296 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
2297 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
2298 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
2299 that the nice and user friendly 3D printer slicer software Cura just
2300 entered Debian Unstable. It consist of five packages,
2301 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
2302 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
2303 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
2304 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
2305 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
2306 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
2307 two, uranium and cura, entered Unstable yesterday. This should make
2308 it easier for Debian users to print on at least the Ultimaker class of
2309 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
2310 make life easier for at least me. :)&lt;/p&gt;
2311
2312 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
2313 happy to assist him in sponsoring the packages. With the introduction
2314 of Cura, Debian is up to three 3D printer slicers at your service,
2315 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
2316 printer, give it a go. :)&lt;/p&gt;
2317
2318 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
2319 team, flocking together on the
2320 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
2321 mailing list and the
2322 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
2323 IRC channel.&lt;/p&gt;
2324
2325 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
2326 version 3.0.3 and then update the entire set of packages to version
2327 3.1.0 which showed up the last few days.&lt;/p&gt;
2328 </description>
2329 </item>
2330
2331 <item>
2332 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
2333 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
2334 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
2335 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
2336 <description>&lt;p&gt;At my nearby maker space,
2337 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
2338 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
2339 on Windows and MacOS X than Linux, because the software involved had
2340 to be manually compiled and set up on Linux while premade packages
2341 worked out of the box on Windows and MacOS X. I found this annoying,
2342 as the software involved,
2343 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
2344 and should be trivial to get up and running on Linux if someone took
2345 the time to package it for the relevant distributions. I even found
2346 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
2347 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
2348 never resulted in the software showing up in Debian. So a few days
2349 ago I offered my help to try to improve the situation.&lt;/p&gt;
2350
2351 &lt;p&gt;Now I am very happy to see that all the packages required by a
2352 working Cura in Debian are uploaded into Debian and waiting in the NEW
2353 queue for the ftpmasters to have a look. You can track the progress
2354 on
2355 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
2356 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
2357
2358 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
2359 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
2360 queue&lt;/a&gt; while we work up updating the packages to the latest
2361 upstream version.&lt;/p&gt;
2362
2363 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
2364 to use and was unable to configure correctly for Ultimaker 2+ in the
2365 short time I spent on it, are already in Debian. If you are looking
2366 for 3D printer &quot;slicers&quot; and want something already available in
2367 Debian, check out
2368 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
2369 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
2370 The latter is a fork of the former.&lt;/p&gt;
2371
2372 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2373 activities, please send Bitcoin donations to my address
2374 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2375 </description>
2376 </item>
2377
2378 <item>
2379 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
2380 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
2381 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
2382 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
2383 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
2384 mobile cell towers. And this radio chatter is available for anyone
2385 with a radio receiver capable of receiving them. Details about the
2386 mobile phones with very good accuracy is of course collected by the
2387 phone companies, but this is not the topic of this blog post. The
2388 mobile phone radio chatter make it possible to figure out when a cell
2389 phone is nearby, as it include the SIM card ID (IMSI). By paying
2390 attention over time, one can see when a phone arrive and when it leave
2391 an area. I believe it would be nice to make this information more
2392 available to the general public, to make more people aware of how
2393 their phones are announcing their whereabouts to anyone that care to
2394 listen.&lt;/p&gt;
2395
2396 &lt;p&gt;I am very happy to report that we managed to get something
2397 visualizing this information up and running for
2398 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
2399 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2400 library. The solution is based on the
2401 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
2402 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
2403 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
2404 Sone from the Computer Science department of the University of
2405 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
2406 IMSIs) as dots in a web browser graph, with lines to the dot
2407 representing mobile base station it is talking to. It was working in
2408 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
2409
2410 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
2411 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2412 connected and visualize the visible cell phone towers using an
2413 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
2414 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
2415 grgsm_livemon_headless processes from
2416 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
2417 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
2418
2419 &lt;p&gt;The frequencies to listen to, are identified using a slightly
2420 patched scan-and-livemon (to set the --args values for each receiver),
2421 and the Hopglass data is generated using the
2422 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
2423 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
2424 more than four SDRs working. There is also a geographical map trying
2425 to show the location of the base stations, but I believe their
2426 coordinates are hardcoded to some random location in Germany, I
2427 believe. The code should be replaced with code to look up location in
2428 a text file, a sqlite database or one of the online databases
2429 mentioned in
2430 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
2431 issue for the topic&lt;/a&gt;.
2432
2433 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
2434 </description>
2435 </item>
2436
2437 <item>
2438 <title>Easier recipe to observe the cell phones around you</title>
2439 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
2440 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
2441 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
2442 <description>&lt;p&gt;A little more than a month ago I wrote
2443 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html&quot;&gt;how
2444 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2445 to nearby mobile phone base stations using Debian GNU/Linux and a
2446 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
2447 the location of people and equipment (like cars and trains) with an
2448 accuracy of a few kilometer. Since then we have worked to make the
2449 procedure even simpler, and it is now possible to do this without any
2450 manual frequency tuning and without building your own packages.&lt;/p&gt;
2451
2452 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
2453 package is now included in Debian testing and unstable, and the
2454 IMSI-catcher code no longer require root access to fetch and decode
2455 the GSM data collected using gr-gsm.&lt;/p&gt;
2456
2457 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
2458 clone of two python scripts:&lt;/p&gt;
2459
2460 &lt;ol&gt;
2461
2462 &lt;li&gt;Start with a Debian machine running the Buster version (aka
2463 testing).&lt;/li&gt;
2464
2465 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
2466 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
2467
2468 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
2469 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
2470
2471 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
2472
2473 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2474 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
2475 stations and start listening for GSM packages on one of them.&lt;/li&gt;
2476
2477 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2478 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
2479
2480 &lt;/ol&gt;
2481
2482 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
2483 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
2484 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
2485 work with RTL 8232 and other similar USB radio receivers you can get
2486 very cheaply
2487 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
2488 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
2489 and only use HackRF for fetching GSM data.&lt;/p&gt;
2490
2491 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
2492 frequencies at the time, so if you are going to track and count every
2493 cell phone around you, you need to listen to all the frequencies used.
2494 To listen to several frequencies, use the --numrecv argument to
2495 scan-and-livemon to use several receivers. Further, I am not sure if
2496 phones using 3G or 4G will show as talking GSM to base stations, so
2497 this approach might not see all phones around you. I typically see
2498 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
2499
2500 &lt;p&gt;I&#39;ve tried to run the scanner on a
2501 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
2502 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
2503 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
2504 stdout, I am told there it is caused by a buffer overflow between the
2505 radio and GNU Radio, caused by the program being unable to read the
2506 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
2507 where you started scan-and-livemon, you need a give the process more
2508 CPU power. Perhaps someone are able to optimize the code to a point
2509 where it become possible to set up RPi3 based GSM sniffers? I tried
2510 using Raspbian instead of Debian, but there seem to be something wrong
2511 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
2512 </description>
2513 </item>
2514
2515 <item>
2516 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
2517 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
2518 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
2519 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
2520 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
2521 web based ICT news magazine digi.no on
2522 &lt;a href=&quot;https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588&quot;&gt;how
2523 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
2524 DVB-T software defined radios. The article refered to instructions
2525 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
2526 Keld Norman on Youtube on how to make a simple $7 IMSI Catcher&lt;/a&gt;, and I decided to test them out.&lt;/p&gt;
2527
2528 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
2529 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2530 and the ask pybombs to fetch and build everything you need from
2531 scratch. I wanted to see if I could do the same on the most recent
2532 Debian packages, but this did not work because pybombs tried to build
2533 stuff that no longer build with the most recent openssl library or
2534 some other version skew problem. While trying to get this recipe
2535 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
2536 and the only piece of software dependency missing in Debian was the
2537 gr-gsm package. I also found out that the lead upstream developer of
2538 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2539 Debian packages provided in an Ubuntu PPA repository. All I needed to
2540 do was to dget the Debian source package and built it.&lt;/p&gt;
2541
2542 &lt;p&gt;The IMSI collector is a python script listening for packages on the
2543 loopback network device and printing to the terminal some specific GSM
2544 packages with IMSI numbers in them. The code is fairly short and easy
2545 to understand. The reason this work is because gr-gsm include a tool
2546 to read GSM data from a software defined radio like a DVB-T USB stick
2547 and other software defined radios, decode them and inject them into a
2548 network device on your Linux machine (using the loopback device by
2549 default). This proved to work just fine, and I&#39;ve been testing the
2550 collector for a few days now.&lt;/p&gt;
2551
2552 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
2553
2554 &lt;ol&gt;
2555
2556 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
2557
2558 &lt;li&gt;build and install the gr-gsm package available from
2559 &lt;a href=&quot;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&quot;&gt;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&lt;/a&gt;,&lt;/li&gt;
2560
2561 &lt;li&gt;clone the git repostory from &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher&quot;&gt;https://github.com/Oros42/IMSI-catcher&lt;/a&gt;,&lt;/li&gt;
2562
2563 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
2564 where it was started is filled with a stream of text (meaning you
2565 found a GSM station).&lt;/li&gt;
2566
2567 &lt;li&gt;go into the IMSI-catcher directory and run &#39;sudo python simple_IMSI-catcher.py&#39; to extract the IMSI numbers.&lt;/li&gt;
2568
2569 &lt;/ol&gt;
2570
2571 &lt;p&gt;To make it even easier in the future to get this sniffer up and
2572 running, I decided to package
2573 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
2574 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
2575 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
2576 Luckily the gnuradio maintainer has promised to help me, as I do not
2577 know much about gnuradio stuff yet.&lt;/p&gt;
2578
2579 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
2580 commercial tools like
2581 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
2582 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
2583 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
2584 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
2585 more people realise how their whereabouts when carrying a cell phone
2586 is easily tracked. Seeing the data flow on the screen, realizing that
2587 I live close to a police station and knowing that the police is also
2588 wearing cell phones, I wonder how hard it would be for criminals to
2589 track the position of the police officers to discover when there are
2590 police near by, or for foreign military forces to track the location
2591 of the Norwegian military forces, or for anyone to track the location
2592 of government officials...&lt;/p&gt;
2593
2594 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2595 script mentioned above is only a fraction of the data broadcasted on
2596 the GSM network. It will only collect one frequency at the time,
2597 while a typical phone will be using several frequencies, and not all
2598 phones will be using the frequencies tracked by the grgsm_livemod
2599 program. Also, there is a lot of radio chatter being ignored by the
2600 simple_IMSI-catcher script, which would be collected by extending the
2601 parser code. I wonder if gr-gsm can be set up to listen to more than
2602 one frequency?&lt;/p&gt;
2603 </description>
2604 </item>
2605
2606 <item>
2607 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2608 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2609 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2610 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2611 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png&quot;/&gt;&lt;/p&gt;
2612
2613 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2614 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2615 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2616 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2617 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2618 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2619 price. The book is also available for download in electronic form as
2620 PDF, EPUB and Mobipocket, as can be
2621 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2622 as a web page&lt;/a&gt;.&lt;/p&gt;
2623
2624 &lt;p&gt;This is the second book I publish (the first was the book
2625 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2626 in
2627 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2628 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2629 and
2630 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2631 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2632 project. I hope
2633 &quot;&lt;a href=&quot;http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html&quot;&gt;Håndbok
2634 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2635 </description>
2636 </item>
2637
2638 <item>
2639 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2640 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2641 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2642 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2643 <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
2644 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2645 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2646 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2647 på om den fri oversetterløsningen
2648 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2649 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2650
2651 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2652
2653 &lt;blockquote&gt;
2654 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2655 rolle og muligheter til å håndtere internasjonale utfordringer, som
2656 for eksempel flykningekrisen.&lt;/p&gt;
2657
2658 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2659 på temaet:&lt;/p&gt;
2660 &lt;ol&gt;
2661 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2662 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2663 &lt;/ol&gt;
2664
2665 &lt;/blockquote&gt;
2666
2667 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2668
2669 &lt;blockquote&gt;
2670 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2671 andre aktørar og høve til å handtera internasjonale utfordringar, som
2672 til dømes *flykningekrisen.&lt;/p&gt;
2673
2674 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2675 temaet:&lt;/p&gt;
2676
2677 &lt;ol&gt;
2678 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2679 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2680 &lt;/ol&gt;
2681
2682 &lt;/blockquote&gt;
2683
2684 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2685 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2686 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2687 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2688 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2689 det er kanskje flisespikking. Det understreker vel bare at det alltid
2690 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2691 </description>
2692 </item>
2693
2694 <item>
2695 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2696 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2697 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2698 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2699 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2700 computers at the time, I often needed a way to detect if the machine
2701 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2702 file or directory affected by the hang, the process (and possibly the
2703 shell) will hang too. So you want to be able to detect this without
2704 risking the detection process getting stuck too. It has not been
2705 obvious how to do this. When the hang has lasted a while, it is
2706 possible to find messages like these in dmesg:&lt;/p&gt;
2707
2708 &lt;p&gt;&lt;blockquote&gt;
2709 nfs: server nfsserver not responding, still trying
2710 &lt;br&gt;nfs: server nfsserver OK
2711 &lt;/blockquote&gt;&lt;/p&gt;
2712
2713 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
2714 be sure looking in dmesg is going to work. If there are lots of other
2715 messages in dmesg the lines might have rotated out of site before they
2716 are noticed.&lt;/p&gt;
2717
2718 &lt;p&gt;While reading through the nfs client implementation in linux kernel
2719 code, I came across some statistics that seem to give a way to detect
2720 it. The om_timeouts sunrpc value in the kernel will increase every
2721 time the above log entry is inserted into dmesg. And after digging a
2722 bit further, I discovered that this value show up in
2723 /proc/self/mountstats on Linux.&lt;/p&gt;
2724
2725 &lt;p&gt;The mountstats content seem to be shared between files using the
2726 same file system context, so it is enough to check one of the
2727 mountstats files to get the state of the mount point for the machine.
2728 I assume this will not show lazy umounted NFS points, nor NFS mount
2729 points in a different process context (ie with a different filesystem
2730 view), but that does not worry me.&lt;/p&gt;
2731
2732 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
2733
2734 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2735 [...]
2736 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2737 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
2738 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
2739 age: 7863311
2740 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
2741 sec: flavor=1,pseudoflavor=1
2742 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
2743 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2744 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
2745 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2746 per-op statistics
2747 NULL: 0 0 0 0 0 0 0 0
2748 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2749 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
2750 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2751 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2752 READLINK: 125 125 0 20472 18620 0 1112 1118
2753 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2754 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2755 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
2756 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
2757 SYMLINK: 903 903 0 233428 245488 6 5865 5917
2758 MKNOD: 80 80 0 20148 21760 0 299 304
2759 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
2760 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
2761 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
2762 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
2763 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2764 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2765 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
2766 FSINFO: 2 2 0 232 328 0 1 1
2767 PATHCONF: 1 1 0 116 140 0 0 0
2768 COMMIT: 0 0 0 0 0 0 0 0
2769
2770 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2771 [...]
2772 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2773
2774 &lt;p&gt;The key number to look at is the third number in the per-op list.
2775 It is the number of NFS timeouts experiences per file system
2776 operation. Here 22 write timeouts and 5 access timeouts. If these
2777 numbers are increasing, I believe the machine is experiencing NFS
2778 hang. Unfortunately the timeout value do not start to increase right
2779 away. The NFS operations need to time out first, and this can take a
2780 while. The exact timeout value depend on the setup. For example the
2781 defaults for TCP and UDP mount points are quite different, and the
2782 timeout value is affected by the soft, hard, timeo and retrans NFS
2783 mount options.&lt;/p&gt;
2784
2785 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
2786 Enterprise Linux for getting the timeout count is to peek in /proc/.
2787 But according to
2788 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
2789 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
2790 command can be used to get these timeout values. But this do not work
2791 on Linux, as far as I can tell. I
2792 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
2793 but have not seen any replies yet.&lt;/p&gt;
2794
2795 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
2796 experiencing NFS hangs? Is there a way to detect which processes are
2797 affected? Is there a way to get the NFS mount going quickly once the
2798 network problem causing the NFS hang has been cleared? I would very
2799 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
2800 </description>
2801 </item>
2802
2803 <item>
2804 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
2805 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
2806 <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>
2807 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
2808 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
2809 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
2810 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
2811 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2812 we are working on the proof reading to ensure consistent language and
2813 use of correct computer science terms. The plan is to make the book
2814 available on paper, as well as in electronic form. For that to
2815 happen, the proof reading must be completed and all the figures need
2816 to be translated. If you want to help out, get in touch.&lt;/p&gt;
2817
2818 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
2819
2820 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
2821 pages) of the book created every morning is available for
2822 proofreading. If you find any errors, please
2823 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
2824 Weblate and correct the error&lt;/a&gt;. The
2825 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
2826 of the translation including figures&lt;/a&gt; is a useful source for those
2827 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
2828 </description>
2829 </item>
2830
2831 <item>
2832 <title>Unlimited randomness with the ChaosKey?</title>
2833 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
2834 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
2835 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
2836 <description>&lt;p&gt;A few days ago I ordered a small batch of
2837 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
2838 USB dongle for generating entropy created by Bdale Garbee and Keith
2839 Packard. Yesterday it arrived, and I am very happy to report that it
2840 work great! According to its designers, to get it to work out of the
2841 box, you need the Linux kernel version 4.1 or later. I tested on a
2842 Debian Stretch machine (kernel version 4.9), and there it worked just
2843 fine, increasing the available entropy very quickly. I wrote a small
2844 test oneliner to test. It first print the current entropy level,
2845 drain /dev/random, and then print the entropy level for five seconds.
2846 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
2847
2848 &lt;blockquote&gt;&lt;pre&gt;
2849 % cat /proc/sys/kernel/random/entropy_avail; \
2850 dd bs=1M if=/dev/random of=/dev/null count=1; \
2851 for n in $(seq 1 5); do \
2852 cat /proc/sys/kernel/random/entropy_avail; \
2853 sleep 1; \
2854 done
2855 300
2856 0+1 oppføringer inn
2857 0+1 oppføringer ut
2858 28 byte kopiert, 0,000264565 s, 106 kB/s
2859 4
2860 8
2861 12
2862 17
2863 21
2864 %
2865 &lt;/pre&gt;&lt;/blockquote&gt;
2866
2867 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
2868 application requiring random bits (like a HTTPS enabled web server)
2869 will halt and wait for more entrpy. And here is the situation with
2870 the ChaosKey inserted:&lt;/p&gt;
2871
2872 &lt;blockquote&gt;&lt;pre&gt;
2873 % cat /proc/sys/kernel/random/entropy_avail; \
2874 dd bs=1M if=/dev/random of=/dev/null count=1; \
2875 for n in $(seq 1 5); do \
2876 cat /proc/sys/kernel/random/entropy_avail; \
2877 sleep 1; \
2878 done
2879 1079
2880 0+1 oppføringer inn
2881 0+1 oppføringer ut
2882 104 byte kopiert, 0,000487647 s, 213 kB/s
2883 433
2884 1028
2885 1031
2886 1035
2887 1038
2888 %
2889 &lt;/pre&gt;&lt;/blockquote&gt;
2890
2891 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
2892 someone want to buy one here in Norway. :)&lt;/p&gt;
2893
2894 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
2895 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
2896 recording illuminating&lt;/a&gt;. It explains exactly what the source of
2897 randomness is, if you are unable to spot it from the schema drawing
2898 available from the ChaosKey web site linked at the start of this blog
2899 post.&lt;/p&gt;
2900 </description>
2901 </item>
2902
2903 <item>
2904 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
2905 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
2906 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
2907 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
2908 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
2909 web servers, and who own the network equipment it is flowing through?
2910 It is possible to get a glimpse of this from using traceroute, but it
2911 is hard to find all the details. Many years ago, I wrote a system to
2912 map the Norwegian Internet (trying to figure out if our plans for a
2913 network game service would get low enough latency, and who we needed
2914 to talk to about setting up game servers close to the users. Back
2915 then I used traceroute output from many locations (I asked my friends
2916 to run a script and send me their traceroute output) to create the
2917 graph and the map. The output from traceroute typically look like
2918 this:
2919
2920 &lt;p&gt;&lt;pre&gt;
2921 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
2922 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
2923 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
2924 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
2925 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
2926 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
2927 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
2928 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
2929 8 * * *
2930 9 * * *
2931 [...]
2932 &lt;/pre&gt;&lt;/p&gt;
2933
2934 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
2935 network equipment involved in getting the data traffic from me to the
2936 www.stortinget.no server, and how long it took in milliseconds for a
2937 package to reach the equipment and return to me. Three packages are
2938 sent, and some times the packages do not follow the same path. This
2939 is shown for hop 5, where three different IP addresses replied to the
2940 traceroute request.&lt;/p&gt;
2941
2942 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
2943 implementations I use are traceroute (using ICMP packages) mtr (can do
2944 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2945 traceroute and a lot of other capabilities). All of them are easily
2946 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
2947
2948 &lt;p&gt;This time around, I wanted to know the geographic location of
2949 different route points, to visualize how visiting a web page spread
2950 information about the visit to a lot of servers around the globe. The
2951 background is that a web site today often will ask the browser to get
2952 from many servers the parts (for example HTML, JSON, fonts,
2953 JavaScript, CSS, video) required to display the content. This will
2954 leak information about the visit to those controlling these servers
2955 and anyone able to peek at the data traffic passing by (like your ISP,
2956 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
2957
2958 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
2959 www.stortinget.no. It is read daily by all members of parliament and
2960 their staff, as well as political journalists, activits and many other
2961 citizens of Norway. A visit to the www.stortinget.no web site will
2962 ask your browser to contact 8 other servers: ajax.googleapis.com,
2963 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2964 stats.g.doubleclick.net, www.google-analytics.com,
2965 www.googletagmanager.com and www.netigate.se. I extracted this by
2966 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
2967 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2968 render the page (in HAR format using
2969 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
2970 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
2971 to do this). My goal is to visualize network traces to all IP
2972 addresses behind these DNS names, do show where visitors personal
2973 information is spread when visiting the page.&lt;/p&gt;
2974
2975 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
2976 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geoip-small.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using GeoIP&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2977
2978 &lt;p&gt;When I had a look around for options, I could not find any good
2979 free software tools to do this, and decided I needed my own traceroute
2980 wrapper outputting KML based on locations looked up using GeoIP. KML
2981 is easy to work with and easy to generate, and understood by several
2982 of the GIS tools I have available. I got good help from by NUUG
2983 colleague Anders Einar with this, and the result can be seen in
2984 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
2985 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
2986 free GeoIP databases I could find (and the for-pay databases my
2987 friends had access to) is not up to the task. The IP addresses of
2988 central Internet infrastructure would typically be placed near the
2989 controlling companies main office, and not where the router is really
2990 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
2991 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
2992
2993 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;&lt;img
2994 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy-small.png&quot; alt=&quot;scapy traceroute graph for URLs used by www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2995
2996 &lt;p&gt;I also had a look at the visual traceroute graph created by
2997 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
2998 showing IP network ownership (aka AS owner) for the IP address in
2999 question.
3000 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
3001 graph display a lot of useful information about the traceroute in SVG
3002 format&lt;/a&gt;, and give a good indication on who control the network
3003 equipment involved, but it do not include geolocation. This graph
3004 make it possible to see the information is made available at least for
3005 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
3006 3 Communications and NetDNA.&lt;/p&gt;
3007
3008 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;https://geotraceroute.com/index.php?node=4&amp;host=www.stortinget.no&quot;&gt;&lt;img
3009 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png&quot; alt=&quot;example geotraceroute view for www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
3010
3011 &lt;p&gt;In the process, I came across the
3012 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
3013 Salim Gasmi. Its methology of combining guesses based on DNS names,
3014 various location databases and finally use latecy times to rule out
3015 candidate locations seemed to do a very good job of guessing correct
3016 geolocation. But it could only do one trace at the time, did not have
3017 a sensor in Norway and did not make the geolocations easily available
3018 for postprocessing. So I contacted the developer and asked if he
3019 would be willing to share the code (he refused until he had time to
3020 clean it up), but he was interested in providing the geolocations in a
3021 machine readable format, and willing to set up a sensor in Norway. So
3022 since yesterday, it is possible to run traces from Norway in this
3023 service thanks to a sensor node set up by
3024 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
3025 trace in KML format for further processing.&lt;/p&gt;
3026
3027 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.kml&quot;&gt;&lt;img
3028 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using geotraceroute&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
3029
3030 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
3031 Denmark, Germany, Holland and Ireland. Plenty of places where the
3032 Snowden confirmations verified the traffic is read by various actors
3033 without your best interest as their top priority.&lt;/p&gt;
3034
3035 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
3036 over all the hosts behind the urls imported by www.stortinget.no and
3037 ask for the KML file from GeoTraceroute, and create a combined KML
3038 file with all the traces (unfortunately only one of the IP addresses
3039 behind the DNS name is traced this time. To get them all, one would
3040 have to request traces using IP number instead of DNS names from
3041 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
3042
3043 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
3044 the IP traffic moves and who control the boxes involved in moving it.
3045 And every time the link crosses for example the Swedish border, we can
3046 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3047 Britain and NSA in USA and cables around the globe. (Hm, what should
3048 we tell them? :) Keep that in mind if you ever send anything
3049 unencrypted over the Internet.&lt;/p&gt;
3050
3051 &lt;p&gt;PS: KML files are drawn using
3052 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
3053 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
3054 Marble. There are heaps of other options too.&lt;/p&gt;
3055
3056 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3057 activities, please send Bitcoin donations to my address
3058 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3059 </description>
3060 </item>
3061
3062 <item>
3063 <title>Appstream just learned how to map hardware to packages too!</title>
3064 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
3065 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
3066 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
3067 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
3068 readers probably know, I have been working on the
3069 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
3070 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
3071 it easier for users to figure out what to install to get a given piece
3072 of hardware to work in Debian, and a key part of this system is a way
3073 to map hardware to packages. Isenkram have its own mapping database,
3074 and also uses data provided by each package using the AppStream
3075 metadata format. And today,
3076 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
3077 Debian learned to look up hardware the same way Isenkram is doing it,
3078 ie using fnmatch():&lt;/p&gt;
3079
3080 &lt;p&gt;&lt;pre&gt;
3081 % appstreamcli what-provides modalias \
3082 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3083 Identifier: pymissile [generic]
3084 Name: pymissile
3085 Summary: Control original Striker USB Missile Launcher
3086 Package: pymissile
3087 % appstreamcli what-provides modalias usb:v0694p0002d0000
3088 Identifier: libnxt [generic]
3089 Name: libnxt
3090 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3091 Package: libnxt
3092 ---
3093 Identifier: t2n [generic]
3094 Name: t2n
3095 Summary: Simple command-line tool for Lego NXT
3096 Package: t2n
3097 ---
3098 Identifier: python-nxt [generic]
3099 Name: python-nxt
3100 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3101 Package: python-nxt
3102 ---
3103 Identifier: nbc [generic]
3104 Name: nbc
3105 Summary: C compiler for LEGO Mindstorms NXT bricks
3106 Package: nbc
3107 %
3108 &lt;/pre&gt;&lt;/p&gt;
3109
3110 &lt;p&gt;A similar query can be done using the combined AppStream and
3111 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
3112
3113 &lt;p&gt;&lt;pre&gt;
3114 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3115 pymissile
3116 % isenkram-lookup usb:v0694p0002d0000
3117 libnxt
3118 nbc
3119 python-nxt
3120 t2n
3121 %
3122 &lt;/pre&gt;&lt;/p&gt;
3123
3124 &lt;p&gt;You can find modalias values relevant for your machine using
3125 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
3126
3127 &lt;p&gt;If you want to make this system a success and help Debian users
3128 make the most of the hardware they have, please
3129 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
3130 AppStream metadata for your package following the guidelines&lt;/a&gt;
3131 documented in the wiki. So far only 11 packages provide such
3132 information, among the several hundred hardware specific packages in
3133 Debian. The Isenkram database on the other hand contain 101 packages,
3134 mostly related to USB dongles. Most of the packages with hardware
3135 mapping in AppStream are LEGO Mindstorms related, because I have, as
3136 part of my involvement in
3137 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
3138 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
3139 complete set of packages in Debian for that particular hardware. The
3140 team also got a nice Christmas present today. The
3141 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
3142 package&lt;/a&gt; made it into Debian. With this package in place, it is
3143 now possible to use the LEGO Mindstorms NXT unit with only free
3144 software, as the nxt-firmware package contain the source and firmware
3145 binaries for the NXT brick.&lt;/p&gt;
3146
3147 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3148 activities, please send Bitcoin donations to my address
3149 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3150 </description>
3151 </item>
3152
3153 <item>
3154 <title>Isenkram updated with a lot more hardware-package mappings</title>
3155 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
3156 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
3157 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
3158 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3159 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
3160 and install packages to get your hardware dongles to work, is still
3161 going strong. It is a system to look up the hardware present on or
3162 connected to the current system, and map the hardware to Debian
3163 packages. It can either be done using the tools in isenkram-cli or
3164 using the user space daemon in the isenkram package. The latter will
3165 notify you, when inserting new hardware, about what packages to
3166 install to get the dongle working. It will even provide a button to
3167 click on to ask packagekit to install the packages.&lt;/p&gt;
3168
3169 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
3170
3171 &lt;p&gt;&lt;pre&gt;
3172 % isenkram-lookup
3173 bluez
3174 cheese
3175 ethtool
3176 fprintd
3177 fprintd-demo
3178 gkrellm-thinkbat
3179 hdapsd
3180 libpam-fprintd
3181 pidgin-blinklight
3182 thinkfan
3183 tlp
3184 tp-smapi-dkms
3185 tp-smapi-source
3186 tpb
3187 %
3188 &lt;/pre&gt;&lt;/p&gt;
3189
3190 &lt;p&gt;It can also list the firware package providing firmware requested
3191 by the load kernel modules, which in my case is an empty list because
3192 I have all the firmware my machine need:
3193
3194 &lt;p&gt;&lt;pre&gt;
3195 % /usr/sbin/isenkram-autoinstall-firmware -l
3196 info: did not find any firmware files requested by loaded kernel modules. exiting
3197 %
3198 &lt;/pre&gt;&lt;/p&gt;
3199
3200 &lt;p&gt;The last few days I had a look at several of the around 250
3201 packages in Debian with udev rules. These seem like good candidates
3202 to install when a given hardware dongle is inserted, and I found
3203 several that should be proposed by isenkram. I have not had time to
3204 check all of them, but am happy to report that now there are 97
3205 packages packages mapped to hardware by Isenkram. 11 of these
3206 packages provide hardware mapping using AppStream, while the rest are
3207 listed in the modaliases file provided in isenkram.&lt;/p&gt;
3208
3209 &lt;p&gt;These are the packages with hardware mappings at the moment. The
3210 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
3211 support using AppStream, for everyone to use:&lt;/p&gt;
3212
3213 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
3214 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
3215 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
3216 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
3217 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
3218 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3219 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
3220 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3221 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3222 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3223 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
3224 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3225 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
3226 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3227 pcscd, pidgin-blinklight, printer-driver-splix,
3228 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
3229 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3230 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3231 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3232 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3233 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3234 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3235 xserver-xorg-video-vmware, yubikey-personalization and
3236 zd1211-firmware&lt;/p&gt;
3237
3238 &lt;p&gt;If you know of other packages, please let me know with a wishlist
3239 bug report against the isenkram-cli package, and ask the package
3240 maintainer to
3241 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
3242 metadata according to the guidelines&lt;/a&gt; to provide the information
3243 for everyone. In time, I hope to get rid of the isenkram specific
3244 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
3245
3246 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
3247 much hardware, and suggest that the package with with any ethernet
3248 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
3249 the details. I hope the maintainer find time to address it soon. In
3250 the mean time I provide an override in isenkram.&lt;/p&gt;
3251 </description>
3252 </item>
3253
3254 <item>
3255 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
3256 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
3257 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
3258 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
3259 <description>&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-12-11-nice-oolite.png&quot;/&gt;&lt;/p&gt;
3260
3261 &lt;p&gt;In my early years, I played
3262 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
3263 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
3264 space, and reached the &#39;elite&#39; fighting status before I moved on. The
3265 original Elite game was available on Commodore 64 and the IBM PC
3266 edition I played had a 64 KB executable. I am still impressed today
3267 that the authors managed to squeeze both a 3D engine and details about
3268 more than 2000 planet systems across 7 galaxies into a binary so
3269 small.&lt;/p&gt;
3270
3271 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
3272 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
3273 really have time to test it properly until a few days ago. It was
3274 great to discover that my old knowledge about trading routes were
3275 still valid. But my fighting and flying abilities were gone, so I had
3276 to retrain to be able to dock on a space station. And I am still not
3277 able to make much resistance when I am attacked by pirates, so I
3278 bougth and mounted the most powerful laser in the rear to be able to
3279 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
3280
3281 &lt;p&gt;When playing Elite in the late eighties, I had to discover
3282 everything on my own, and I had long lists of prices seen on different
3283 planets to be able to decide where to trade what. This time I had the
3284 advantages of the
3285 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
3286 where information about each planet is easily available with common
3287 price ranges and suggested trading routes. This improved my ability
3288 to earn money and I have been able to earn enough to buy a lot of
3289 useful equipent in a few days. I believe I originally played for
3290 months before I could get a docking computer, while now I could get it
3291 after less then a week.&lt;/p&gt;
3292
3293 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
3294 space, you should try out Oolite. It is available for Linux, MacOSX
3295 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
3296
3297 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3298 activities, please send Bitcoin donations to my address
3299 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3300 </description>
3301 </item>
3302
3303 <item>
3304 <title>Quicker Debian installations using eatmydata</title>
3305 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
3306 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
3307 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
3308 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
3309 installation system, observing how using
3310 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
3311 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
3312 speedup around 20-40 percent for Debian Edu, where we install around
3313 1000 packages from within the installer. The eatmydata package
3314 provide a way to disable/delay file system flushing. This is a bit
3315 risky in the general case, as files that should be stored on disk will
3316 stay only in memory a bit longer than expected, causing problems if a
3317 machine crashes at an inconvenient time. But for an installation, if
3318 the machine crashes during installation the process is normally
3319 restarted, and avoiding disk operations as much as possible to speed
3320 up the process make perfect sense.
3321
3322 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
3323 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
3324 but did not have time to push it any further. But a few months ago I
3325 picked it up again and worked with the libeatmydata package maintainer
3326 Mattia Rizzolo to make it easier for everyone to get this installation
3327 speedup in Debian. Thanks to our cooperation There is now an
3328 eatmydata-udeb package in Debian testing and unstable, and simply
3329 enabling/installing it in debian-installer (d-i) is enough to get the
3330 quicker installations. It can be enabled using preseeding. The
3331 following untested kernel argument should do the trick:&lt;/p&gt;
3332
3333 &lt;blockquote&gt;&lt;pre&gt;
3334 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
3335 &lt;/pre&gt;&lt;/blockquote&gt;
3336
3337 &lt;p&gt;This should ask d-i to install the package inside the d-i
3338 environment early in the installation sequence. Having it installed
3339 in d-i in turn will make sure the relevant scripts are called just
3340 after debootstrap filled /target/ with the freshly installed Debian
3341 system to configure apt to run dpkg with eatmydata. This is enough to
3342 speed up the installation process. There is a proposal to
3343 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
3344 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
3345 tested its impact.&lt;/p&gt;
3346
3347 </description>
3348 </item>
3349
3350 <item>
3351 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
3352 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
3353 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
3354 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
3355 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3356 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3357 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3358 elever over det ganske land skal levere inn hvert år. Det mange ikke
3359 vet er at selv om de kommersielle alternativene
3360 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
3361 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
3362 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3363 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3364 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3365 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3366 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3367 nynorsk, og få den automatoversatt til det andre skriftspråket.
3368 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3369 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3370 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3371 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3372 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
3373 teksten din i webskjemaet der.
3374
3375 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
3376 teknologien kan du enten installere pakken
3377 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
3378 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3379 api.apertium.org. Se
3380 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
3381 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3382 denne teksten som ble skrevet på bokmål over maskinoversatt til
3383 nynorsk.&lt;/p&gt;
3384
3385 &lt;hr/&gt;
3386
3387 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3388 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3389 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3390 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3391 veit er at sjølv om dei kommersielle alternativa
3392 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
3393 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
3394 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3395 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3396 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3397 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3398 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3399 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3400 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3401 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3402 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3403 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3404 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
3405 teksta di i *webskjemaet der.
3406
3407 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
3408 teknologien kan du anten installera pakken
3409 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
3410 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3411 *api.*apertium.org. Sjå
3412 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
3413 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3414 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3415 nynorsk.&lt;/p&gt;
3416 </description>
3417 </item>
3418
3419 <item>
3420 <title>Coz profiler for multi-threaded software is now in Debian</title>
3421 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
3422 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
3423 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
3424 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
3425 profiler able to run benchmarking experiments on the instrumented
3426 multi-threaded program, finally
3427 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
3428 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
3429 months since
3430 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html&quot;&gt;I
3431 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
3432 it suitable for Debian. There are still issues with clang
3433 compatibility, inline assembly only working x86 and minimized
3434 JavaScript libraries.&lt;/p&gt;
3435
3436 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
3437
3438 &lt;p&gt;&lt;blockquote&gt;
3439 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
3440 &lt;/blockquote&gt;&lt;/p&gt;
3441
3442 &lt;p&gt;This will produce a profile.coz file in the current working
3443 directory with the profiling information. This is then given to a
3444 JavaScript application provided in the package and available from
3445 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
3446 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
3447
3448 &lt;p&gt;&lt;blockquote&gt;
3449 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
3450 &lt;/blockquote&gt;&lt;/p&gt;
3451
3452 &lt;p&gt;See the project home page and the
3453 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
3454 ;login: article on Coz&lt;/a&gt; for more information on how it is
3455 working.&lt;/p&gt;
3456 </description>
3457 </item>
3458
3459 <item>
3460 <title>My own self balancing Lego Segway</title>
3461 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
3462 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
3463 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
3464 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
3465 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
3466 present. It had been on my wishlist for a while, because I wanted to
3467 build a Segway like balancing lego robot. I had already built
3468 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
3469 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
3470 NXT kit as the balance sensor, but it was not working very well. It
3471 could balance for a while, but was very sensitive to the light
3472 condition in the room and the reflective properties of the surface and
3473 would fall over after a short while. I wanted something more robust,
3474 and had
3475 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
3476 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
3477 wishlist for some years before it suddenly showed up as a gift from my
3478 loved ones. :)&lt;/p&gt;
3479
3480 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
3481 since then. But that changed some days ago, when I was searching for
3482 lego segway information and came across a recipe from HiTechnic for
3483 building
3484 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
3485 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
3486 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
3487 code&lt;/a&gt; was included, so it was just a question of putting it all
3488 together. And thanks to the great work of many Debian developers, the
3489 compiler needed to build the source for the NXT is already included in
3490 Debian, so I was read to go in less than an hour. The resulting robot
3491 do not look very impressive in its simplicity:&lt;/p&gt;
3492
3493 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg&quot;&gt;&lt;/p&gt;
3494
3495 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
3496 design from HiTechnic, I had to comment out the last task
3497 (taskControl). I simply placed /* and */ around it get the program
3498 working without that sensor present. Now it balances just fine until
3499 the battery status run low:&lt;/p&gt;
3500
3501 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
3502 &lt;source src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv&quot; type=&quot;video/ogg&quot;&gt;
3503 &lt;/video&gt;&lt;/p&gt;
3504
3505 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
3506 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
3507
3508 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
3509 they need to work with LEGO in Debian and all our derivative
3510 distributions like Ubuntu, check out
3511 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
3512 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
3513 RCX and NXT controller (no EV3), and would like to make sure the
3514 Debian tools needed to program the systems I own work as they
3515 should.&lt;/p&gt;
3516 </description>
3517 </item>
3518
3519 <item>
3520 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
3521 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
3522 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
3523 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
3524 <description>&lt;p&gt;In July
3525 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
3526 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
3527 the ability to receive SMS messages (aka without a cell phone). It is
3528 time to share some experiences and provide an updated setup.&lt;/p&gt;
3529
3530 &lt;p&gt;The Signal app have worked fine for several months now, and I use
3531 it regularly to chat with my loved ones. I had a major snag at the
3532 end of my summer vacation, when the the app completely forgot my
3533 setup, identity and keys. The reason behind this major mess was
3534 running out of disk space. To avoid that ever happening again I have
3535 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
3536 roll back to an earlier version if the files are wiped by mistake. I
3537 had to use it once after introducing the git backup. When rolling
3538 back to an earlier version, one need to use the &#39;reset session&#39; option
3539 in Signal to get going, and notify the people you talk with about the
3540 problem. I assume there is some sequence number tracking in the
3541 protocol to detect rollback attacks. The git repository is rather big
3542 (674 MiB so far), but I have not tried to figure out if some of the
3543 content can be added to a .gitignore file due to lack of spare
3544 time.&lt;/p&gt;
3545
3546 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
3547 make it impossible to send messages using Signal. I could still
3548 receive them, but had to patch the code with a new timestamp to send.
3549 I believe the timeout is added by the developers to force people to
3550 upgrade to the latest version of the app, even when there is no
3551 protocol changes, to reduce the version skew among the user base and
3552 thus try to keep the number of support requests down.&lt;/p&gt;
3553
3554 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
3555 making the old patch fail to apply cleanly. Below is an updated
3556 patch, including the shell wrapper I use to start Signal. The
3557 original version required a new user to locate the JavaScript console
3558 and call a function from there. I got help from a friend with more
3559 JavaScript knowledge than me to modify the code to provide a GUI
3560 button instead. This mean that to get started you just need to run
3561 the wrapper and click the &#39;Register without mobile phone&#39; to get going
3562 now. I&#39;ve also modified the timeout code to always set it to 90 days
3563 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
3564
3565 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
3566
3567 &lt;ol&gt;
3568
3569 &lt;li&gt;First, install required packages to get the source code and the
3570 browser you need. Signal only work with Chrome/Chromium, as far as I
3571 know, so you need to install it.
3572
3573 &lt;pre&gt;
3574 apt install git tor chromium
3575 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3576 &lt;/pre&gt;&lt;/li&gt;
3577
3578 &lt;li&gt;Modify the source code using command listed in the the patch
3579 block below.&lt;/li&gt;
3580
3581 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
3582 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
3583
3584 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
3585 number you can receive calls to the next minute, receive the
3586 verification code and enter it into the form field and press
3587 &#39;Register&#39;. Note, the phone number you use will be user Signal
3588 username, ie the way others can find you on Signal.&lt;/li&gt;
3589
3590 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3591 not show up in the contact list until you restart Signal, and there is
3592 no way to assign names to Contacts. There is also no way to create or
3593 update chat groups. I suspect this is because the web app do not have
3594 a associated contact database.&lt;/li&gt;
3595
3596 &lt;/ol&gt;
3597
3598 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3599 main author moxie0 reject federation and accept dependencies to major
3600 corporations like Google (part of the code is fetched from Google) and
3601 Amazon (the central coordination point is owned by Amazon). See for
3602 example
3603 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3604 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3605 view on these issues. But the network effect is strong in this case,
3606 and several of the people I want to communicate with already use
3607 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3608 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3609 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3610 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3611 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3612 working on Debian Stable.&lt;/p&gt;
3613
3614 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3615 working. It switch to the production servers, disable to timeout,
3616 make registration easier and add the shell wrapper:&lt;/p&gt;
3617
3618 &lt;pre&gt;
3619 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3620 diff --git a/js/background.js b/js/background.js
3621 index 24b4c1d..579345f 100644
3622 --- a/js/background.js
3623 +++ b/js/background.js
3624 @@ -33,9 +33,9 @@
3625 });
3626 });
3627
3628 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3629 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3630 var SERVER_PORTS = [80, 4433, 8443];
3631 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3632 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3633 var messageReceiver;
3634 window.getSocketStatus = function() {
3635 if (messageReceiver) {
3636 diff --git a/js/expire.js b/js/expire.js
3637 index 639aeae..beb91c3 100644
3638 --- a/js/expire.js
3639 +++ b/js/expire.js
3640 @@ -1,6 +1,6 @@
3641 ;(function() {
3642 &#39;use strict&#39;;
3643 - var BUILD_EXPIRATION = 0;
3644 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3645
3646 window.extension = window.extension || {};
3647
3648 diff --git a/js/views/install_view.js b/js/views/install_view.js
3649 index 7816f4f..1d6233b 100644
3650 --- a/js/views/install_view.js
3651 +++ b/js/views/install_view.js
3652 @@ -38,7 +38,8 @@
3653 return {
3654 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3655 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3656 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3657 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3658 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3659 };
3660 },
3661 clearQR: function() {
3662 diff --git a/options.html b/options.html
3663 index dc0f28e..8d709f6 100644
3664 --- a/options.html
3665 +++ b/options.html
3666 @@ -14,7 +14,10 @@
3667 &amp;lt;div class=&#39;nav&#39;&gt;
3668 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3669 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3670 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3671 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3672 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3673 +
3674 + &amp;lt;/div&gt;
3675 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3676 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3677 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3678 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3679 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3680 @@ -0,0 +1,12 @@
3681 +#!/bin/sh
3682 +set -e
3683 +cd $(dirname $0)
3684 +mkdir -p userdata
3685 +userdata=&quot;`pwd`/userdata&quot;
3686 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3687 + (cd $userdata &amp;&amp; git init)
3688 +fi
3689 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3690 +exec chromium \
3691 + --proxy-server=&quot;socks://localhost:9050&quot; \
3692 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3693 EOF
3694 chmod a+rx run-signal-app
3695 &lt;/pre&gt;
3696
3697 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3698 activities, please send Bitcoin donations to my address
3699 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3700 </description>
3701 </item>
3702
3703 <item>
3704 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3705 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3706 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3707 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3708 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3709 system&lt;/a&gt; provide a practical and easy way to figure out which
3710 packages support the hardware in a given machine. The command line
3711 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
3712 convenient way to list and install packages relevant for the current
3713 hardware during system installation, both user space packages and
3714 firmware packages. The GUI background daemon on the other hand provide
3715 a pop-up proposing to install packages when a new dongle is inserted
3716 while using the computer. For example, if you plug in a smart card
3717 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
3718 that package isn&#39;t already installed, and if you plug in a USB video
3719 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
3720 cheese is currently missing. This already work just fine.&lt;/p&gt;
3721
3722 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
3723 package names. When I started no such database existed in Debian, so
3724 I made my own data set and included it with the isenkram package and
3725 made isenkram fetch the latest version of this database from git using
3726 http. This way the isenkram users would get updated package proposals
3727 as soon as I learned more about hardware related packages.&lt;/p&gt;
3728
3729 &lt;p&gt;The hardware is identified using modalias strings. The modalias
3730 design is from the Linux kernel where most hardware descriptors are
3731 made available as a strings that can be matched using filename style
3732 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3733 identifiers.&lt;/p&gt;
3734
3735 &lt;p&gt;The downside to the Isenkram specific database is that there is no
3736 information about relevant distribution / Debian version, making
3737 isenkram propose obsolete packages too. But along came AppStream, a
3738 cross distribution mechanism to store and collect metadata about
3739 software packages. When I heard about the proposal, I contacted the
3740 people involved and suggested to add a hardware matching rule using
3741 modalias strings in the specification, to be able to use AppStream for
3742 mapping hardware to packages. This idea was accepted and AppStream is
3743 now a great way for a package to announce the hardware it support in a
3744 distribution neutral way. I wrote
3745 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
3746 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
3747 December. If you have a hardware related package in Debian, please
3748 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
3749
3750 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
3751 RCX or NXT unit, announce this support using AppStream. The effect is
3752 that when you insert such LEGO robot controller into your Debian
3753 machine, Isenkram will propose to install the packages needed to get
3754 it working. The intention is that this should allow the local user to
3755 start programming his robot controller right away without having to
3756 guess what packages to use or which permissions to fix.&lt;/p&gt;
3757
3758 &lt;p&gt;But when I sat down with my son the other day to program our NXT
3759 unit using his Debian Stretch computer, I discovered something
3760 annoying. The local console user (ie my son) did not get access to
3761 the USB device for programming the unit. This used to work, but no
3762 longer in Jessie and Stretch. After some investigation and asking
3763 around on #debian-devel, I discovered that this was because udev had
3764 changed the mechanism used to grant access to local devices. The
3765 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
3766 no longer applied, because LDAP users no longer was added to the
3767 plugdev group during login. Michael Biebl told me that this method
3768 was obsolete and the new method used ACLs instead. This was good
3769 news, as the plugdev mechanism is a mess when using a remote user
3770 directory like LDAP. Using ACLs would make sure a user lost device
3771 access when she logged out, even if the user left behind a background
3772 process which would retain the plugdev membership with the ConsoleKit
3773 setup. Armed with this knowledge I moved on to fix the access problem
3774 for the LEGO Mindstorms related packages.&lt;/p&gt;
3775
3776 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
3777 applied directly for a device, or is applied in
3778 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
3779 LEGO Mindstorms udev rules did not have a class, I decided to add the
3780 tag directly in the udev rules files included in the packages. Here
3781 is one example. For the nqc C compiler for the RCX, the
3782 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
3783
3784 &lt;p&gt;&lt;pre&gt;
3785 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
3786 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
3787 &lt;/pre&gt;&lt;/p&gt;
3788
3789 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
3790 packages using plugdev in their /lib/udev/rules.d/ files should be
3791 changed to use this tag (either directly or indirectly via
3792 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
3793 to detect this?&lt;/p&gt;
3794
3795 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
3796 It is unclear to me if the uaccess tag is an internal implementation
3797 detail like the udev-acl tag used by
3798 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
3799 indirect method is the preferred way. Michael
3800 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
3801 documentation from the systemd project&lt;/a&gt; and I hope it will make
3802 this clearer. For now I use the generic classes when they exist and
3803 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
3804 directly if no such class exist.&lt;/p&gt;
3805
3806 &lt;p&gt;To learn more about the isenkram system, please check out
3807 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3808 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3809
3810 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
3811 please join us on our IRC channel
3812 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
3813 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
3814 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
3815 list is not yet created, but we are working on it. :)&lt;/p&gt;
3816
3817 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3818 activities, please send Bitcoin donations to my address
3819 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3820 </description>
3821 </item>
3822
3823 <item>
3824 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
3825 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
3826 <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>
3827 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
3828 <description>&lt;p&gt;In April we
3829 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
3830 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
3831 how to set up and administrate a Debian system. Today I am happy to
3832 report that the first draft is now publicly available. You can find
3833 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
3834 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
3835 eight chapters have a first draft translation, and we are working on
3836 proofreading the content. If you want to help out, please start
3837 contributing using
3838 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3839 hosted weblate project page&lt;/a&gt;, and get in touch using
3840 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3841 translators mailing list&lt;/a&gt;. Please also check out
3842 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3843 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
3844 and update weblate if you find errors.&lt;/p&gt;
3845
3846 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
3847 electronic form.&lt;/p&gt;
3848 </description>
3849 </item>
3850
3851 <item>
3852 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
3853 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
3854 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
3855 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
3856 <description>&lt;p&gt;This summer, I read a great article
3857 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
3858 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
3859 how to profile multi-threaded programs. It presented a system for
3860 profiling software by running experiences in the running program,
3861 testing how run time performance is affected by &quot;speeding up&quot; parts of
3862 the code to various degrees compared to a normal run. It does this by
3863 slowing down parallel threads while the &quot;faster up&quot; code is running
3864 and measure how this affect processing time. The processing time is
3865 measured using probes inserted into the code, either using progress
3866 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3867 can also measure unmodified code by measuring complete the program
3868 runtime and running the program several times instead.&lt;/p&gt;
3869
3870 &lt;p&gt;The project and presentation was so inspiring that I would like to
3871 get the system into Debian. I
3872 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
3873 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
3874 system ready for Debian by sending patches. The build process need to
3875 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
3876 to include the JavaScript web page used to visualize the collected
3877 profiling information included in the source package.
3878 But I expect that should work out fairly soon.&lt;/p&gt;
3879
3880 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
3881 on a binary with debug symbols available, start the program like this:
3882
3883 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3884 coz run --- program-to-run
3885 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3886
3887 &lt;p&gt;This will create a text file profile.coz with the instrumentation
3888 information. To show what part of the code affect the performance
3889 most, use a web browser and either point it to
3890 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
3891 or use the copy from git (in the gh-pages branch). Check out this web
3892 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
3893 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
3894 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3895 code, rebuild and run the profiler. This allow coz to do more
3896 targeted experiments.&lt;/p&gt;
3897
3898 &lt;p&gt;A video published by ACM
3899 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
3900 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
3901 from the 25th Symposium on Operating Systems Principles available
3902 titled
3903 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
3904 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
3905
3906 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
3907 for Coz is available from github. It will only build with clang
3908 because it uses a
3909 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
3910 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
3911 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
3912 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
3913
3914 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
3915 of software in Debian. I would very much like some help with the
3916 packaging effort, as I lack the in depth knowledge on how to package
3917 C++ libraries.&lt;/p&gt;
3918 </description>
3919 </item>
3920
3921 <item>
3922 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
3923 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
3924 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
3925 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
3926 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3927 to be a slight challenge. Here is the recipe if I ever need to do it
3928 again. It all started by me wanting to try the recipe to set up
3929 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
3930 hardened Android installation&lt;/a&gt; from the Tor project blog on a
3931 device I had access to. It is a old mobile phone with a broken
3932 microphone The initial idea had been to just
3933 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
3934 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
3935 until a few days ago.&lt;/p&gt;
3936
3937 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
3938 loader (press volume down and power at the same time), (2) select
3939 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
3940 machine, (4) request the device identifier token by running &#39;fastboot
3941 oem get_identifier_token&#39;, (5) request the device unlocking key using
3942 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
3943 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
3944
3945 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
3946 or newer, and the device I was working on had 2.00.0027. This
3947 apparently can be easily fixed by downloading a Windows program and
3948 running it on your Windows machine, if you accept the terms Microsoft
3949 require you to accept to use Windows - which I do not. So I had to
3950 come up with a different approach. I got a lot of help from AndyCap
3951 on #nuug, and would not have been able to get this working without
3952 him.&lt;/p&gt;
3953
3954 &lt;p&gt;First I needed to extract the hboot firmware from
3955 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
3956 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
3957 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
3958 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
3959 recognise the file format, but unruu worked and extracted rom.zip,
3960 containing the new hboot firmware and a text file describing which
3961 devices it would work for.&lt;/p&gt;
3962
3963 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
3964 followed some instructions
3965 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
3966 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
3967 machine with Debian testing:&lt;/p&gt;
3968
3969 &lt;p&gt;&lt;pre&gt;
3970 adb reboot-bootloader
3971 fastboot oem rebootRUU
3972 fastboot flash zip rom.zip
3973 fastboot flash zip rom.zip
3974 fastboot reboot
3975 &lt;/pre&gt;&lt;/p&gt;
3976
3977 &lt;p&gt;The flash command apparently need to be done twice to take effect,
3978 as the first is just preparations and the second one do the flashing.
3979 The adb command is just to get to the boot loader menu, so turning the
3980 device on while holding volume down and the power button should work
3981 too.&lt;/p&gt;
3982
3983 &lt;p&gt;With the new hboot version in place I could start following the
3984 instructions on the HTC developer web site. I got the device token
3985 like this:&lt;/p&gt;
3986
3987 &lt;p&gt;&lt;pre&gt;
3988 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
3989 &lt;/pre&gt;
3990
3991 &lt;p&gt;And once I got the unlock code via email, I could use it like
3992 this:&lt;/p&gt;
3993
3994 &lt;p&gt;&lt;pre&gt;
3995 fastboot flash unlocktoken Unlock_code.bin
3996 &lt;/pre&gt;&lt;/p&gt;
3997
3998 &lt;p&gt;And with that final step in place, the phone was unlocked and I
3999 could start stuffing the software of my own choosing into the device.
4000 So far I only inserted a replacement recovery image to wipe the phone
4001 before I start. We will see what happen next. Perhaps I should
4002 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
4003 </description>
4004 </item>
4005
4006 <item>
4007 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
4008 <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>
4009 <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>
4010 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
4011 <description>&lt;p&gt;For a while now, I have wanted to test
4012 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
4013 said to provide end to end encrypted communication and several of my
4014 friends and family are already using it. As I by choice do not own a
4015 mobile phone, this proved to be harder than expected. And I wanted to
4016 have the source of the client and know that it was the code used on my
4017 machine. But yesterday I managed to get it working. I used the
4018 Github source, compared it to the source in
4019 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
4020 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
4021 patches to use the production Signal servers, started the app and
4022 asked for the hidden &quot;register without a smart phone&quot; form. Here is
4023 the recipe how I did it.&lt;/p&gt;
4024
4025 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
4026
4027 &lt;pre&gt;
4028 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4029 &lt;/pre&gt;
4030
4031 &lt;p&gt;Next, I patched the source to use the production servers, to be
4032 able to talk to other Signal users:&lt;/p&gt;
4033
4034 &lt;pre&gt;
4035 cat &amp;lt;&amp;lt;EOF | patch -p0
4036 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
4037 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
4038 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
4039 @@ -47,8 +47,8 @@
4040 });
4041 });
4042
4043 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
4044 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
4045 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
4046 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
4047 var messageReceiver;
4048 window.getSocketStatus = function() {
4049 if (messageReceiver) {
4050 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
4051 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
4052 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
4053 @@ -1,6 +1,6 @@
4054 ;(function() {
4055 &#39;use strict&#39;;
4056 - var BUILD_EXPIRATION = 0;
4057 + var BUILD_EXPIRATION = 1474492690000;
4058
4059 window.extension = window.extension || {};
4060
4061 EOF
4062 &lt;/pre&gt;
4063
4064 &lt;p&gt;The first part is changing the servers, and the second is updating
4065 an expiration timestamp. This timestamp need to be updated regularly.
4066 It is set 90 days in the future by the build process (Gruntfile.js).
4067 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
4068
4069 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
4070 script to launch Signal in Chromium.&lt;/p&gt;
4071
4072 &lt;pre&gt;
4073 #!/bin/sh
4074 cd $(dirname $0)
4075 mkdir -p userdata
4076 exec chromium \
4077 --proxy-server=&quot;socks://localhost:9050&quot; \
4078 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4079 &lt;/pre&gt;
4080
4081 &lt;p&gt; The script start the app and configure Chromium to use the Tor
4082 SOCKS5 proxy to make sure those controlling the Signal servers (today
4083 Amazon and Whisper Systems) as well as those listening on the lines
4084 will have a harder time location my laptop based on the Signal
4085 connections if they use source IP address.&lt;/p&gt;
4086
4087 &lt;p&gt;When the script starts, one need to follow the instructions under
4088 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
4089 repository. I right clicked on the Signal window to get up the
4090 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
4091 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
4092 registration form. Then I entered by land line phone number and
4093 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
4094 repeated the verification code three times. After entering the number
4095 into the verification code field in the form, I could start using
4096 Signal from my laptop.
4097
4098 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
4099 whom and thus who know who to those controlling the central server,
4100 but such leakage is hard to avoid with a centrally controlled server
4101 setup. It is something to keep in mind when using Signal - the
4102 content of your chats are harder to intercept, but the meta data
4103 exposing your contact network is available to people you do not know.
4104 So better than many options, but not great. And sadly the usage is
4105 connected to my land line, thus allowing those controlling the server
4106 to associate it to my home and person. I would prefer it if only
4107 those I knew could tell who I was on Signal. There are options
4108 avoiding such information leakage, but most of my friends are not
4109 using them, so I am stuck with Signal for now.&lt;/p&gt;
4110
4111 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
4112 on this topic in
4113 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;Experience
4114 and updated recipe for using the Signal app without a mobile
4115 phone&lt;/a&gt;.&lt;/p&gt;
4116 </description>
4117 </item>
4118
4119 <item>
4120 <title>The new &quot;best&quot; multimedia player in Debian?</title>
4121 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
4122 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
4123 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
4124 <description>&lt;p&gt;When I set out a few weeks ago to figure out
4125 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
4126 multimedia player in Debian claimed to support most file formats /
4127 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
4128 the various players claimed support for. The range was from 55 to 130
4129 MIME types. I suspect most media formats are supported by all
4130 players, but this is not really reflected in the MimeTypes values in
4131 their desktop files. There are probably also some bogus MIME types
4132 listed, but it is hard to identify which one this is.&lt;/p&gt;
4133
4134 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
4135 the players suggesting to add more MIME types to their desktop files,
4136 and decided to spend some time myself improving the situation for my
4137 favorite media player VLC. The fixes for VLC entered Debian unstable
4138 yesterday. The complete list of MIME types can be seen on the
4139 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
4140 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
4141
4142 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
4143 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4144 kmplayer. I am sure some of the other players desktop files support
4145 several of the formats currently listed as working only with vlc,
4146 toten and parole.&lt;/p&gt;
4147
4148 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
4149 supported by all the tested multimedia players in Debian in their
4150 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4151 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4152 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4153 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4154 it sad that video/ogg and video/webm is not supported by all the media
4155 players in Debian. As far as I can tell, all of them can handle both
4156 formats.&lt;/p&gt;
4157 </description>
4158 </item>
4159
4160 <item>
4161 <title>A program should be able to open its own files on Linux</title>
4162 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
4163 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
4164 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
4165 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
4166 decided to test its presentation tool when making the slides for a
4167 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4168 wrote the first draft of the slides, saved the result and went to bed
4169 the day before I would give the talk. The next day I took a plane to
4170 the location where the meeting should take place, and on the plane I
4171 started up koffice again to polish the talk a bit, only to discover
4172 that kpresenter refused to load its own data file. I cursed a bit and
4173 started making the slides again from memory, to have something to
4174 present when I arrived. I tested that the saved files could be
4175 loaded, and the day seemed to be rescued. I continued to polish the
4176 slides until I suddenly discovered that the saved file could no longer
4177 be loaded into kpresenter. In the end I had to rewrite the slides
4178 three times, condensing the content until the talk became shorter and
4179 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
4180 kpresenter wrote inline images in a way itself could not understand.
4181 Eventually that bug was fixed and kpresenter ended up being a great
4182 program to make slides. The point I&#39;m trying to make is that we
4183 expect a program to be able to load its own data files, and it is
4184 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
4185
4186 &lt;p&gt;Did you ever experience a program failing to load its own data
4187 files from the desktop file browser? It is not a uncommon problem. A
4188 while back I discovered that the screencast recorder
4189 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4190 browser would refuse to open. No video player claimed to understand
4191 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
4192 returning the application/ogg MIME type, which no video player I had
4193 installed listed as a MIME type they would understand. I asked for
4194 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
4195 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
4196 several video players to add video/ogg to their desktop files, to give
4197 the file browser an idea what to do about Ogg Theora files. After a
4198 while, the desktop file browsers in Debian started to handle the
4199 output from gtk-recordmydesktop properly.&lt;/p&gt;
4200
4201 &lt;p&gt;But history repeats itself. A few days ago I tested the music
4202 system Rosegarden again, and I discovered that the KDE and xfce file
4203 browsers did not know what to do with the Rosegarden project files
4204 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
4205 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
4206 included in the next upload. To increase the chance of me remembering
4207 how to fix the problem next time some program fail to load its files
4208 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
4209
4210 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
4211 There are two sources for the MIME type of a given file. The output from
4212 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
4213 shared MIME type registry (under /usr/share/mime/). The file MIME
4214 type is mapped to programs supporting the MIME type, and this
4215 information is collected from
4216 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
4217 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
4218 one desktop file claiming support for the MIME type of the file, it is
4219 activated when asking to open a given file. If there are more, one
4220 can normally select which one to use by right-clicking on the file and
4221 selecting the wanted one using &#39;Open with&#39; or similar. In general
4222 this work well. But it depend on each program picking a good MIME
4223 type (preferably
4224 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
4225 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
4226 registry recognizing the file and the desktop file to list the MIME
4227 type in its list of supported MIME types.&lt;/p&gt;
4228
4229 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
4230 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
4231 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
4232
4233 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4234 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4235 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
4236 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
4237 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
4238 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
4239 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
4240 &amp;lt;/mime-type&amp;gt;
4241 &amp;lt;/mime-info&amp;gt;
4242 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4243
4244 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
4245 (it is a gzipped XML file). Note, it is much better to use an
4246 official MIME type registered with IANA than it is to make up ones own
4247 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
4248
4249 &lt;p&gt;The desktop file of the rosegarden program failed to list
4250 audio/x-rosegarden in its list of supported MIME types, causing the
4251 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
4252
4253 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4254 % grep Mime /usr/share/applications/rosegarden.desktop
4255 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4256 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4257 %
4258 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4259
4260 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
4261 MimeType= line.&lt;/p&gt;
4262
4263 &lt;p&gt;If you run into a file which fail to open the correct program when
4264 selected from the file browser, please check out the output from
4265 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
4266 MIME type is registered somewhere under /usr/share/mime/ and check
4267 that some desktop file under /usr/share/applications/ is claiming
4268 support for this MIME type. If not, please report a bug to have it
4269 fixed. :)&lt;/p&gt;
4270 </description>
4271 </item>
4272
4273 <item>
4274 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
4275 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
4276 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
4277 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
4278 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
4279 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
4280 related packages. The idea is to have a database of mappings between
4281 hardware and packages, and pop up a dialog suggesting for the user to
4282 install the packages to use a given hardware dongle. Some use cases
4283 are when you insert a Yubikey, it proposes to install the software
4284 needed to control it; when you insert a braille reader list it
4285 proposes to install the packages needed to send text to the reader;
4286 and when you insert a ColorHug screen calibrator it suggests to
4287 install the driver for it. The system work well, and even have a few
4288 command line tools to install firmware packages and packages for the
4289 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
4290
4291 &lt;p&gt;The system was initially written using aptdaemon, because I found
4292 good documentation and example code on how to use it. But aptdaemon
4293 is going away and is generally being replaced by
4294 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
4295 so Isenkram needed a rewrite. And today, thanks to the great patch
4296 from my college Sunil Mohan Adapa in the FreedomBox project, the
4297 rewrite finally took place. I&#39;ve just uploaded a new version of
4298 Isenkram into Debian Unstable with the patch included, and the default
4299 for the background daemon is now to use PackageKit. To check it out,
4300 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
4301 and see if it is recognised.&lt;/p&gt;
4302
4303 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
4304 the machine it is running on, you can check out the isenkram-lookup
4305 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
4306
4307 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4308 % isenkram-lookup
4309 bluez
4310 cheese
4311 fprintd
4312 fprintd-demo
4313 gkrellm-thinkbat
4314 hdapsd
4315 libpam-fprintd
4316 pidgin-blinklight
4317 thinkfan
4318 tleds
4319 tp-smapi-dkms
4320 tp-smapi-source
4321 tpb
4322 %p
4323 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4324
4325 &lt;p&gt;The hardware mappings come from several places. The preferred way
4326 is for packages to announce their hardware support using
4327 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4328 cross distribution appstream system&lt;/a&gt;.
4329 See
4330 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
4331 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
4332 </description>
4333 </item>
4334
4335 <item>
4336 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
4337 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
4338 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
4339 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
4340 <description>&lt;p&gt;Yesterday I updated the
4341 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
4342 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
4343 enterprising users. There were some nice user and visible changes.
4344 First of all, both desktop menu entries now work. A design flaw in
4345 one of the script made the history graph fail to show up (its PNG was
4346 dumped in ~/.xsession-errors) if no controlling TTY was available.
4347 The script worked when called from the command line, but not when
4348 called from the desktop menu. I changed this to look for a DISPLAY
4349 variable or a TTY before deciding where to draw the graph, and now the
4350 graph window pop up as expected.&lt;/p&gt;
4351
4352 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
4353 graphs (the one showing the last few hours). New is also the user of
4354 colours showing charging in blue and discharge in red. The percentages
4355 of this graph is relative to last full charge, not battery design
4356 capacity.&lt;/p&gt;
4357
4358 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-rate.png&quot;/&gt;&lt;/p&gt;
4359
4360 &lt;p&gt;The other graph show the entire history of the collected battery
4361 statistics, comparing it to the design capacity of the battery to
4362 visualise how the battery life time get shorter over time. The red
4363 line in this graph is what the previous graph considers 100 percent:
4364
4365 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-history.png&quot;/&gt;&lt;/p&gt;
4366
4367 &lt;p&gt;In this graph you can see that I only charge the battery to 80
4368 percent of last full capacity, and how the capacity of the battery is
4369 shrinking. :(&lt;/p&gt;
4370
4371 &lt;p&gt;The last new feature is in the collector, which now will handle
4372 more hardware models. On some hardware, Linux power supply
4373 information is stored in /sys/class/power_supply/ACAD/, while the
4374 collector previously only looked in /sys/class/power_supply/AC/. Now
4375 both are checked to figure if there is power connected to the
4376 machine.&lt;/p&gt;
4377
4378 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4379 check out the
4380 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4381 in Debian unstable, or rebuild it on Jessie to get it working on
4382 Debian stable. :) The upstream source is available from &lt;a
4383 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4384 Patches are very welcome.&lt;/p&gt;
4385
4386 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4387 activities, please send Bitcoin donations to my address
4388 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4389 </description>
4390 </item>
4391
4392 <item>
4393 <title>Debian now with ZFS on Linux included</title>
4394 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
4395 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
4396 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
4397 <description>&lt;p&gt;Today, after many years of hard work from many people,
4398 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
4399 Debian. The package status can be seen on
4400 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
4401 for zfs-linux&lt;/a&gt;. and
4402 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4403 team status page&lt;/a&gt;. If you want to help out, please join us.
4404 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
4405 source code&lt;/a&gt; is available via git on Alioth. It would also be
4406 great if you could help out with
4407 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
4408 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
4409 </description>
4410 </item>
4411
4412 <item>
4413 <title>What is the best multimedia player in Debian?</title>
4414 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
4415 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
4416 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
4417 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
4418 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
4419
4420 &lt;p&gt;A few years ago, I had a look at the media support for Browser
4421 plugins in Debian, to get an idea which plugins to include in Debian
4422 Edu. I created a script to extract the set of supported MIME types
4423 for each plugin, and used this to find out which multimedia browser
4424 plugin supported most file formats / media types.
4425 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
4426 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
4427 not been updated for a while. But browser plugins are less relevant
4428 these days, so I thought it was time to look at standalone
4429 players.&lt;/p&gt;
4430
4431 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
4432 player when I wanted to play videos from the Norwegian National
4433 Broadcasting Company, and decided to investigate why. The cause is a
4434 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
4435 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
4436 of MIME types announced in the desktop file and the browser plugin,
4437 only to discover that there is quite a large difference between the
4438 two for VLC. This discovery made me dig up the script I used to
4439 compare browser plugins, and adjust it to compare desktop files
4440 instead, to try to figure out which multimedia player in Debian
4441 support most file formats.&lt;/p&gt;
4442
4443 &lt;p&gt;The result can be seen on the Debian Wiki, as
4444 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
4445 table listing all MIME types supported by one of the packages included
4446 in the table&lt;/a&gt;, with the package supporting most MIME types being
4447 listed first in the table.&lt;/p&gt;
4448
4449 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
4450 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4451 kmplayer. Time for the other players to update their announced MIME
4452 support?&lt;/p&gt;
4453 </description>
4454 </item>
4455
4456 <item>
4457 <title>The Pyra - handheld computer with Debian preinstalled</title>
4458 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
4459 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
4460 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
4461 <description>A friend of mine made me aware of
4462 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
4463 handheld computer which will be delivered with Debian preinstalled. I
4464 would love to get one of those for my birthday. :)&lt;/p&gt;
4465
4466 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4467 plugs and many others connectors, and include a full keyboard and a 5&quot;
4468 LCD touch screen. The 6000mAh battery is claimed to provide a whole
4469 day of battery life time, but I have not seen any independent tests
4470 confirming this. The vendor is still collecting preorders, and the
4471 last I heard last night was that 22 more orders were needed before
4472 production started.&lt;/p&gt;
4473
4474 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
4475 Debian. Please let me know if you know of any others. Is it the
4476 first computer being sold with Debian preinstalled?&lt;/p&gt;
4477 </description>
4478 </item>
4479
4480 <item>
4481 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
4482 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
4483 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
4484 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
4485 <description>&lt;p&gt;During this weekends
4486 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
4487 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
4488 to make sure there are good books about Debian available in Norwegian
4489 Bokmål, and got in touch with the people behind the
4490 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
4491 project&lt;/a&gt; to get started. If you want to help out, please start
4492 contributing using
4493 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
4494 hosted weblate project page&lt;/a&gt;, and get in touch using
4495 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
4496 translators mailing list&lt;/a&gt;. Please also check out
4497 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
4498 contributors&lt;/a&gt;.&lt;/p&gt;
4499
4500 &lt;p&gt;The book is already available on paper in English, French and
4501 Japanese, and our goal is to get it available on paper in Norwegian
4502 Bokmål too. In addition to the paper edition, there are also EPUB and
4503 Mobi versions available. And there are incomplete translations
4504 available for many more languages.&lt;/p&gt;
4505 </description>
4506 </item>
4507
4508 <item>
4509 <title>One in two hundred Debian users using ZFS on Linux?</title>
4510 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
4511 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
4512 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
4513 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
4514 packages in Debian, and was quite surprised with what I found. I use
4515 ZFS myself at home, but did not really expect many others to do so.
4516 But I might be wrong.&lt;/p&gt;
4517
4518 &lt;p&gt;According to
4519 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
4520 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
4521 0.53% of the population, with the package installed. As far as I know
4522 the only use of the spl-linux package is as a support library for ZFS
4523 on Linux, so I use it here as proxy for measuring the number of ZFS
4524 installation on Linux in Debian. In the kFreeBSD variant of Debian
4525 the ZFS feature is already available, and there
4526 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
4527 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
4528 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
4529
4530 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
4531 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
4532 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
4533 cleared, the package is still not in Debian. The package is again in
4534 the NEW queue. Several uploads have been rejected so far because the
4535 debian/copyright file was incomplete or wrong, but there is no reason
4536 to give up. The current status can be seen on
4537 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4538 team status page&lt;/a&gt;, and
4539 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
4540 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
4541
4542 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
4543 my home server can function in the future using only official Debian
4544 packages, and the current blocker is to get the debian/copyright file
4545 accepted by the FTP masters in Debian, I decided a while back to try
4546 to help out the team. This was the background for my blog post about
4547 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
4548 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
4549 used the techniques I explored there to try to find any errors in the
4550 copyright file. It is not very easy to check every one of the around
4551 2000 files in the source package, but I hope we this time got it
4552 right. If you want to help out, check out the git source and try to
4553 find missing entries in the debian/copyright file.&lt;/p&gt;
4554 </description>
4555 </item>
4556
4557 <item>
4558 <title>Full battery stats collector is now available in Debian</title>
4559 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
4560 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
4561 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
4562 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
4563 extended collector that will collect the complete battery history for
4564 later processing and graphing. The original collector store the
4565 battery level as percentage of last full level, while the new
4566 collector also record battery vendor, model, serial number, design
4567 full level, last full level and current battery level. This make it
4568 possible to predict the lifetime of the battery as well as visualise
4569 the energy flow when the battery is charging or discharging.&lt;/p&gt;
4570
4571 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
4572 in the version 0.5.1 package in unstable. Get the new battery level graph
4573 and lifetime prediction by running:
4574
4575 &lt;p&gt;&lt;pre&gt;
4576 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4577 &lt;/pre&gt;&lt;/p&gt;
4578
4579 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
4580
4581 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
4582 entry yet):&lt;/p&gt;
4583
4584 &lt;p&gt;&lt;pre&gt;
4585 /usr/share/battery-stats/battery-stats-graph-flow
4586 &lt;/pre&gt;&lt;/p&gt;
4587
4588 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
4589 when there are few data points. The graphs look a bit better with a
4590 few years of data.&lt;/p&gt;
4591
4592 &lt;p&gt;A while back one important feature I use in the battery stats
4593 collector broke in Debian. The scripts in
4594 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4595 suspect it happened when Jessie started using systemd, but I do not
4596 know. The issue is reported as
4597 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4598 pm-utils. I managed to work around it by adding an udev rule to call
4599 the collector script every time the power connector is connected and
4600 disconnected. With this fix in place it was finally time to make a
4601 new release of the package, and get it into Debian.&lt;/p&gt;
4602
4603 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4604 check out the
4605 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4606 in Debian unstable, or rebuild it on Jessie to get it working on
4607 Debian stable. :) The upstream source is available from
4608 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4609 As always, patches are very welcome.&lt;/p&gt;
4610 </description>
4611 </item>
4612
4613 <item>
4614 <title>Making battery measurements a little easier in Debian</title>
4615 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4616 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4617 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4618 <description>&lt;p&gt;Back in September, I blogged about
4619 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4620 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4621 how it showed the decay and death of this battery (now replaced). I
4622 created a simple deb package to handle the collection and graphing,
4623 but did not want to upload it to Debian as there were already
4624 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4625 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4626 a point of uploading a competing package when battery-stats could be
4627 fixed instead. I reported a few bugs about its non-function, and
4628 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4629
4630 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4631 hands. The end result is that I am now the new upstream developer of
4632 battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
4633 battery-stats in Debian, and the package in Debian unstable is finally
4634 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4635 information provided by the Linux kernel. If you install the
4636 battery-stats package from unstable now, you will be able to get a
4637 graph of the current battery fill level, to get some idea about the
4638 status of the battery. The source package build and work just fine in
4639 Debian testing and stable (and probably oldstable too, but I have not
4640 tested). The default graph you get for that system look like this:&lt;/p&gt;
4641
4642 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
4643
4644 &lt;p&gt;My plans for the future is to merge my old scripts into the
4645 battery-stats package, as my old scripts collected a lot more details
4646 about the battery. The scripts are merged into the upstream
4647 battery-stats git repository already, but I am not convinced they work
4648 yet, as I changed a lot of paths along the way. Will have to test a
4649 bit more before I make a new release.&lt;/p&gt;
4650
4651 &lt;p&gt;I will also consider changing the file format slightly, as I
4652 suspect the way I combine several values into one field might make it
4653 impossible to know the type of the value when using it for processing
4654 and graphing.&lt;/p&gt;
4655
4656 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4657 battery, check out the battery-stats package in
4658 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4659 on
4660 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4661 I would love some help to improve the system further.&lt;/p&gt;
4662 </description>
4663 </item>
4664
4665 <item>
4666 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4667 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4668 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4669 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4670 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4671 details. And one of the details is the content of the
4672 debian/copyright file, which should list all relevant licenses used by
4673 the code in the package in question, preferably in
4674 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4675 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4676
4677 &lt;p&gt;For large packages with lots of contributors it is hard to write
4678 and update this file manually, and if you get some detail wrong, the
4679 package is normally rejected by the ftpmasters. So getting it right
4680 the first time around get the package into Debian faster, and save
4681 both you and the ftpmasters some work.. Today, while trying to figure
4682 out what was wrong with
4683 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4684 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4685 figuring out the options for doing this job automatically, or at least
4686 semi-automatically.&lt;/p&gt;
4687
4688 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4689 file based on the code in the source package,
4690 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4691 and &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/cme&quot;&gt;cme&lt;/a&gt;&lt;/tt&gt;. I&#39;m
4692 not sure which one of them came first, but both seem to be able to
4693 create a sensible draft file. As far as I can tell, none of them can
4694 be trusted to get the result just right, so the content need to be
4695 polished a bit before the file is OK to upload. I found the debmake
4696 option in
4697 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4698 blog posts from 2014&lt;/a&gt;.
4699
4700 &lt;p&gt;To generate using debmake, use the -cc option:
4701
4702 &lt;p&gt;&lt;pre&gt;
4703 debmake -cc &gt; debian/copyright
4704 &lt;/pre&gt;&lt;/p&gt;
4705
4706 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4707 this might not be the best option.&lt;/p&gt;
4708
4709 &lt;p&gt;The cme option is based on a config parsing library, and I found
4710 this approach in
4711 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
4712 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
4713 dpkg-copyright&#39; option:
4714
4715 &lt;p&gt;&lt;pre&gt;
4716 cme update dpkg-copyright
4717 &lt;/pre&gt;&lt;/p&gt;
4718
4719 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
4720 handle UTF-8 names better than debmake.&lt;/p&gt;
4721
4722 &lt;p&gt;When the copyright file is created, I would also like some help to
4723 check if the file is correct. For this I found two good options,
4724 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
4725 to focus on license types and file matching, and is able to detect
4726 ineffective blocks in the copyright file. The latter reports missing
4727 copyright holders and years, but was confused by inconsistent license
4728 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
4729 fix all issues reported by them before uploading. But I do not know
4730 if the tools and the ftpmasters agree on what is important to fix in a
4731 copyright file, so the package might still be rejected.&lt;/p&gt;
4732
4733 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
4734 will read through the source and try to find all copyright statements.
4735 It is not comparing the result to the content of debian/copyright, but
4736 can be useful when verifying the content of the copyright file.&lt;/p&gt;
4737
4738 &lt;p&gt;Are you aware of better tools in Debian to create and update
4739 debian/copyright file. Please let me know, or blog about it on
4740 planet.debian.org.&lt;/p&gt;
4741
4742 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4743 activities, please send Bitcoin donations to my address
4744 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4745
4746 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
4747 on how to use licensecheck and cdbs to create a draft copyright file
4748
4749 &lt;p&gt;&lt;pre&gt;
4750 licensecheck --copyright -r `find * -type f` | \
4751 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
4752 &lt;/pre&gt;&lt;/p&gt;
4753
4754 &lt;p&gt;He mentioned that he normally check the generated file into the
4755 version control system to make it easier to discover license and
4756 copyright changes in the upstream source. I will try to do the same
4757 with my packages in the future.&lt;/p&gt;
4758
4759 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
4760 against using -quiet for new users, so I removed it from the proposed
4761 command line.&lt;/p&gt;
4762 </description>
4763 </item>
4764
4765 <item>
4766 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
4767 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
4768 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
4769 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
4770 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
4771 is taking shape in Debian, and one provided feature is a very
4772 convenient way to tell you which package to install to make a given
4773 firmware file available when the kernel is looking for it. This can
4774 be done using apt-file too, but that is for someone else to blog
4775 about. :)&lt;/p&gt;
4776
4777 &lt;p&gt;Here is a small recipe to find the package with a given firmware
4778 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
4779 picked from the set of firmware announced using appstream in Debian
4780 unstable. In general you would be looking for the firmware requested
4781 by the kernel during kernel module loading. To find the package
4782 providing the example file, do like this:&lt;/p&gt;
4783
4784 &lt;blockquote&gt;&lt;pre&gt;
4785 % apt install appstream
4786 [...]
4787 % apt update
4788 [...]
4789 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
4790 awk &#39;/Package:/ {print $2}&#39;
4791 firmware-qlogic
4792 %
4793 &lt;/pre&gt;&lt;/blockquote&gt;
4794
4795 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
4796 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
4797 a way appstream can use.&lt;/p&gt;
4798
4799 &lt;p&gt;This same approach can be used to find any package supporting a
4800 given MIME type. This is very useful when you get a file you do not
4801 know how to handle. First find the mime type using &lt;tt&gt;file
4802 --mime-type&lt;/tt&gt;, and next look up the package providing support for
4803 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4804 and you can find all packages handling this type like this:&lt;/p&gt;
4805
4806 &lt;blockquote&gt;&lt;pre&gt;
4807 % apt install appstream
4808 [...]
4809 % apt update
4810 [...]
4811 % appstreamcli what-provides mimetype image/svg+xml | \
4812 awk &#39;/Package:/ {print $2}&#39;
4813 bkchem
4814 phototonic
4815 inkscape
4816 shutter
4817 tetzle
4818 geeqie
4819 xia
4820 pinta
4821 gthumb
4822 karbon
4823 comix
4824 mirage
4825 viewnior
4826 postr
4827 ristretto
4828 kolourpaint4
4829 eog
4830 eom
4831 gimagereader
4832 midori
4833 %
4834 &lt;/pre&gt;&lt;/blockquote&gt;
4835
4836 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
4837 packages providing appstream metadata.&lt;/p&gt;
4838 </description>
4839 </item>
4840
4841 <item>
4842 <title>Creepy, visualise geotagged social media information - nice free software</title>
4843 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
4844 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
4845 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
4846 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
4847 with the computerised radio beacon known as a mobile phone their
4848 position is tracked by the phone company and often stored for a long
4849 time (like every time a SMS is received or sent). And if their
4850 computerised radio beacon is capable of running programs (often called
4851 mobile apps) downloaded from the Internet, these programs are often
4852 also capable of tracking their location (if the app requested access
4853 during installation). And when these programs send out information to
4854 central collection points, the location is often included, unless
4855 extra care is taken to not send the location. The provided
4856 information is used by several entities, for good and bad (what is
4857 good and bad, depend on your point of view). What is certain, is that
4858 the private sphere and the right to free movement is challenged and
4859 perhaps even eradicated for those announcing their location this way,
4860 when they share their whereabouts with private and public
4861 entities.&lt;/p&gt;
4862
4863 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
4864
4865 &lt;p&gt;The phone company logs provide a register of locations to check out
4866 when one want to figure out what the tracked person was doing. It is
4867 unavailable for most of us, but provided to selected government
4868 officials, company staff, those illegally buying information from
4869 unfaithful servants and crackers stealing the information. But the
4870 public information can be collected and analysed, and a free software
4871 tool to do so is called
4872 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
4873 discovered it when I read
4874 &lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
4875 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
4876 November 2014, and decided to check if it was available in Debian.
4877 The python program was in Debian, but
4878 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
4879 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
4880 uploaded a new version which did not work quite right, but did not
4881 have time to fix it then. This Christmas I decided to finally try to
4882 get Creepy operational in Debian. Now a fixed version is available in
4883 Debian unstable and testing, and almost all Debian specific patches
4884 are now included
4885 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
4886
4887 &lt;p&gt;The Creepy program visualises geolocation information fetched from
4888 Twitter, Instagram, Flickr and Google+, and allow one to get a
4889 complete picture of every social media message posted recently in a
4890 given area, or track the movement of a given individual across all
4891 these services. Earlier it was possible to use the search API of at
4892 least some of these services without identifying oneself, but these
4893 days it is impossible. This mean that to use Creepy, you need to
4894 configure it to log in as yourself on these services, and provide
4895 information to them about your search interests. This should be taken
4896 into account when using Creepy, as it will also share information
4897 about yourself with the services.&lt;/p&gt;
4898
4899 &lt;p&gt;The picture above show the twitter messages sent from (or at least
4900 geotagged with a position from) the city centre of Oslo, the capital
4901 of Norway. One useful way to use Creepy is to first look at
4902 information tagged with an area of interest, and next look at all the
4903 information provided by one or more individuals who was in the area.
4904 I tested it by checking out which celebrity provide their location in
4905 twitter messages by checkout out who sent twitter messages near a
4906 Norwegian TV station, and next could track their position over time,
4907 making it possible to locate their home and work place, among other
4908 things. A similar technique have been
4909 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
4910 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
4911 tool to discover lying governments, and a useful tool to help people
4912 understand the value of the private information they provide to the
4913 public.&lt;/p&gt;
4914
4915 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
4916 it depend on several python modules currently missing in Jessie (at
4917 least python-instagram, python-flickrapi and
4918 python-requests-toolbelt).&lt;/p&gt;
4919
4920 &lt;p&gt;(I have uploaded
4921 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
4922 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
4923 Creepy program in Debian.)&lt;/p&gt;
4924 </description>
4925 </item>
4926
4927 <item>
4928 <title>Always download Debian packages using Tor - the simple recipe</title>
4929 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
4930 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
4931 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
4932 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
4933 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
4934 that those listening on the Internet lines would have good reason to
4935 believe a computer have a given security hole&lt;/a&gt; if it download a
4936 security fix from a Debian mirror. This is a good reason to always
4937 use encrypted connections to the Debian mirror, to make sure those
4938 listening do not know which IP address to attack. In August, Richard
4939 Hartmann observed that encryption was not enough, when it was possible
4940 to interfere download size to security patches or the fact that
4941 download took place shortly after a security fix was released, and
4942 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
4943 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
4944 was not the first to propose this, as the
4945 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
4946 package by Tim Retout already existed to make it easy to convince apt
4947 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
4948 aware of that package when I read the blog post from Richard.&lt;/p&gt;
4949
4950 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
4951 sysadmins, and he set up a Tor hidden service on one of the central
4952 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4953 it possible to download packages directly between two tor nodes,
4954 making sure the network traffic always were encrypted.&lt;/p&gt;
4955
4956 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
4957 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
4958 urls with tor+http and tor+https, and using the hidden service instead
4959 of the official Debian mirror site. I recommend installing
4960 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
4961 done in /etc/.&lt;/p&gt;
4962
4963 &lt;blockquote&gt;&lt;pre&gt;
4964 apt install apt-transport-tor
4965 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
4966 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
4967 &lt;/pre&gt;&lt;/blockquote&gt;
4968
4969 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
4970 the sed commands for these too. The sed command is assuming your are
4971 using the ftp.debian.org Debian mirror. Adjust the command (or just
4972 edit the file manually) to match your mirror.&lt;/p&gt;
4973
4974 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
4975 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
4976 system, and do not work with these tor+http URLs. For
4977 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
4978 which need a recent apt version currently only in unstable. So if you
4979 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
4980
4981 &lt;p&gt;Another advantage from this change is that your machine will start
4982 using Tor regularly and at fairly random intervals (every time you
4983 update the package lists or upgrade or install a new package), thus
4984 masking other Tor traffic done from the same machine. Using Tor will
4985 become normal for the machine in question.&lt;/p&gt;
4986
4987 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
4988 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
4989 enabled. It would be great if it was the default on any Debian
4990 system.&lt;/p&gt;
4991 </description>
4992 </item>
4993
4994 <item>
4995 <title>OpenALPR, find car license plates in video streams - nice free software</title>
4996 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
4997 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
4998 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
4999 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
5000 call the car license plate numbers in those days. I would write the
5001 numbers down in my little book and compare notes with the other kids
5002 to see how many region codes we had seen and if we had seen some
5003 exotic or special region codes and numbers. It was a fun game to pass
5004 time, as we kids have plenty of it.&lt;/p&gt;
5005
5006 &lt;p&gt;A few days I came across
5007 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
5008 project&lt;/a&gt;, a free software project to automatically discover and
5009 report license plates in images and video streams, and provide the
5010 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
5011 such system for a while now, because I believe it is a bad idea that the
5012 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
5013 number plate recognition&lt;/a&gt; tool only is available in the hands of
5014 the powerful, and want it to be available also for the powerless to
5015 even the score when it comes to surveillance and sousveillance. I
5016 discovered the developer
5017 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
5018 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
5019 help him get it into shape to get the package uploaded into the Debian
5020 archive.&lt;/p&gt;
5021
5022 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
5023 it into Debian, where it currently
5024 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
5025 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
5026
5027 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
5028 for the common folks, ie those not running a large government
5029 surveillance system? Well, I plan to put it in a computer on my bike
5030 and in my car, tracking the cars nearby and allowing me to be notified
5031 when number plates on my watch list are discovered. Another use case
5032 was suggested by a friend of mine, who wanted to set it up at his home
5033 to open the car port automatically when it discovered the plate on his
5034 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5035 capable of placing his license plate number of a piece of cardboard to
5036 open his car port, men replied that it was always unlocked anyway. I
5037 guess for such use case it make sense. I am sure there are other use
5038 cases too, for those with imagination and a vision.&lt;/p&gt;
5039
5040 &lt;p&gt;If you want to build your own version of the Debian package, check
5041 out the upstream git source and symlink ./distros/debian to ./debian/
5042 before running &quot;debuild&quot; to build the source. Or wait a bit until the
5043 package show up in unstable.&lt;/p&gt;
5044 </description>
5045 </item>
5046
5047 <item>
5048 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
5049 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
5050 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
5051 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
5052 <description>&lt;p&gt;Around three years ago, I created
5053 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
5054 system&lt;/a&gt; to get a more practical solution in Debian for handing
5055 hardware related packages. A GUI system in the isenkram package will
5056 present a pop-up dialog when some hardware dongle supported by
5057 relevant packages in Debian is inserted into the machine. The same
5058 lookup mechanism to detect packages is available as command line
5059 tools in the isenkram-cli package. In addition to mapping hardware,
5060 it will also map kernel firmware files to packages and make it easy to
5061 install needed firmware packages automatically. The key for this
5062 system to work is a good way to map hardware to packages, in other
5063 words, allow packages to announce what hardware they will work
5064 with.&lt;/p&gt;
5065
5066 &lt;p&gt;I started by providing data files in the isenkram source, and
5067 adding code to download the latest version of these data files at run
5068 time, to ensure every user had the most up to date mapping available.
5069 I also added support for storing the mapping in the Packages file in
5070 the apt repositories, but did not push this approach because while I
5071 was trying to figure out how to best store hardware/package mappings,
5072 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
5073 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
5074 add the hardware mapping into that data set to be able to use
5075 appstream as a data source, and this was accepted at least for the
5076 Debian version of appstream.&lt;/p&gt;
5077
5078 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
5079 and today I uploaded a new version 0.20 of isenkram adding support for
5080 appstream as a data source for mapping hardware to packages. The only
5081 package so far using appstream to announce its hardware support is my
5082 pymissile package. I got help from Matthias Klumpp with figuring out
5083 how do add the required
5084 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
5085 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
5086 this content:&lt;/p&gt;
5087
5088 &lt;blockquote&gt;&lt;pre&gt;
5089 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
5090 &amp;lt;component&amp;gt;
5091 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
5092 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
5093 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
5094 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
5095 &amp;lt;description&amp;gt;
5096 &amp;lt;p&amp;gt;
5097 Pymissile provides a curses interface to control an original
5098 Marks and Spencer / Striker USB Missile Launcher, as well as a
5099 motion control script to allow a webcamera to control the
5100 launcher.
5101 &amp;lt;/p&amp;gt;
5102 &amp;lt;/description&amp;gt;
5103 &amp;lt;provides&amp;gt;
5104 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
5105 &amp;lt;/provides&amp;gt;
5106 &amp;lt;/component&amp;gt;
5107 &lt;/pre&gt;&lt;/blockquote&gt;
5108
5109 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
5110 which is a glob style match rule for hardware specific strings
5111 (modalias strings) provided by the Linux kernel. In this case, it
5112 will map to all USB devices with vendor code 1130 and product code
5113 0202.&lt;/p&gt;
5114
5115 &lt;p&gt;Note, it is important that the license of all the metadata files
5116 are compatible to have permissions to aggregate them into archive wide
5117 appstream files. Matthias suggested to use MIT or BSD licenses for
5118 these files. A challenge is figuring out a good id for the data, as
5119 it is supposed to be globally unique and shared across distributions
5120 (in other words, best to coordinate with upstream what to use). But
5121 it can be changed later or, so we went with the package name as
5122 upstream for this project is dormant.&lt;/p&gt;
5123
5124 &lt;p&gt;To get the metadata file installed in the correct location for the
5125 mirror update scripts to pick it up and include its content the
5126 appstream data source, the file must be installed in the binary
5127 package under /usr/share/appdata/. I did this by adding the following
5128 line to debian/pymissile.install:&lt;/p&gt;
5129
5130 &lt;blockquote&gt;&lt;pre&gt;
5131 debian/pymissile.metainfo.xml usr/share/appdata
5132 &lt;/pre&gt;&lt;/blockquote&gt;
5133
5134 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
5135 all packages useful on the current computer automatically, and the GUI
5136 pop-up handler will propose to install the package not already
5137 installed if a hardware dongle is inserted into the machine in
5138 question.&lt;/p&gt;
5139
5140 &lt;p&gt;Details of the modalias field in appstream is available from the
5141 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
5142
5143 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
5144 try running this command on the command line:&lt;/p&gt;
5145
5146 &lt;blockquote&gt;&lt;pre&gt;
5147 cat $(find /sys/devices/|grep modalias)
5148 &lt;/pre&gt;&lt;/blockquote&gt;
5149
5150 &lt;p&gt;To learn more about the isenkram system, please check out
5151 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
5152 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
5153 </description>
5154 </item>
5155
5156 <item>
5157 <title>The GNU General Public License is not magic pixie dust</title>
5158 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
5159 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
5160 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
5161 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
5162 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
5163 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
5164 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
5165 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
5166
5167 &lt;blockquote&gt;
5168
5169 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
5170
5171 &lt;blockquote&gt;
5172 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
5173
5174 The first step is to choose a
5175 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
5176 code.&lt;br/&gt;
5177
5178 The next step is, when someone fails to follow that copyleft license,
5179 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
5180
5181 and its a simple fact of our modern society that such type of
5182 work&lt;br/&gt;
5183
5184 is incredibly expensive to do and incredibly difficult to do.
5185 &lt;/blockquote&gt;
5186
5187 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
5188 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
5189 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
5190 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
5191
5192 &lt;p&gt;As the Debian Website
5193 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
5194 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
5195 imply, public domain and permissively licensed software can lead to
5196 the production of more proprietary software as people discover useful
5197 software, extend it and or incorporate it into their hardware or
5198 software products. Copyleft licenses such as the GNU GPL were created
5199 to close off this avenue to the production of proprietary software but
5200 such licenses are not enough. With the ongoing adoption of Free
5201 Software by individuals and groups, inevitably the community&#39;s
5202 expectations of license compliance are violated, usually out of
5203 ignorance of the way Free Software works, but not always. As Karen
5204 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
5205 Freedom&quot;&gt;FaiF&lt;/a&gt;
5206 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
5207 copyleft is nothing if no-one is willing and able to stand up in court
5208 to protect it. The reality of today&#39;s world is that legal
5209 representation is expensive, difficult and time consuming. With
5210 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
5211 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
5212 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
5213 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
5214 of the Linux project, Debian and other groups against GPL violations.
5215 In March the SFC supported a
5216 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
5217 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
5218 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
5219 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
5220 kernel. Since then two of their sponsors pulled corporate funding and
5221 conferences
5222 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
5223 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
5224 less on corporate funding and more on the broad community of
5225 individuals who support Free Software and copyleft. So the SFC has
5226 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
5227 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
5228 a community of folks who stand up for copyleft and the GPL by
5229 supporting their work on promoting and supporting copyleft and Free
5230 Software.&lt;/p&gt;
5231
5232 &lt;p&gt;If you support Free Software,
5233 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
5234 what the SFC do, agree with their
5235 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
5236 principles&lt;/a&gt;, are happy about their
5237 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
5238 work on a project that is an SFC
5239 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
5240 just want to stand up for copyleft, please join
5241 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
5242 Allan Webber&lt;/a&gt;,
5243 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
5244 Smith&lt;/a&gt;,
5245 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
5246 Bacon&lt;/a&gt;, myself and
5247 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
5248 becoming a
5249 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
5250 next week your donation will be
5251 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
5252 by an anonymous donor. Please also consider asking your employer to
5253 match your donation or become a sponsor of SFC. Don&#39;t forget to
5254 spread the word about your support for SFC via email, your blog and or
5255 social media accounts.&lt;/p&gt;
5256
5257 &lt;/blockquote&gt;
5258
5259 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
5260 of Software Freedom Conservancy myself. Perhaps you should be a
5261 supporter too?&lt;/p&gt;
5262 </description>
5263 </item>
5264
5265 <item>
5266 <title>PGP key transition statement for key EE4E02F9</title>
5267 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
5268 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
5269 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
5270 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
5271 set it up properly. I wanted to generate it offline and have it
5272 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
5273 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
5274 time to sit down with an offline machine almost took forever. But
5275 finally I&#39;ve been able to complete the process, and have now moved
5276 from my old GPG key to a new GPG key. See
5277 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
5278 full transition statement, signed with both my old and new key&lt;/a&gt; for
5279 the details. This is my new key:&lt;/p&gt;
5280
5281 &lt;pre&gt;
5282 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
5283 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
5284 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
5285 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
5286 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
5287 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
5288 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
5289 &lt;/pre&gt;
5290
5291 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
5292 my old key.&lt;/p&gt;
5293
5294 &lt;p&gt;If you signed my old key
5295 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
5296 I&#39;d very much appreciate a signature on my new key, details and
5297 instructions in the transition statement. I m happy to reciprocate if
5298 you have a similarly signed transition statement to present.&lt;/p&gt;
5299 </description>
5300 </item>
5301
5302 <item>
5303 <title>The life and death of a laptop battery</title>
5304 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
5305 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
5306 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
5307 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
5308 But this do not last. The last few laptops gave me a feeling that
5309 within a year, the life time is just a fraction of what it used to be,
5310 and it slowly become painful to use the laptop without power connected
5311 all the time. Because of this, when I got a new Thinkpad X230 laptop
5312 about two years ago, I decided to monitor its battery state to have
5313 more hard facts when the battery started to fail.&lt;/p&gt;
5314
5315 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
5316
5317 &lt;p&gt;First I tried to find a sensible Debian package to record the
5318 battery status, assuming that this must be a problem already handled
5319 by someone else. I found
5320 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
5321 which collects statistics from the battery, but it was completely
5322 broken. I sent a few suggestions to the maintainer, but decided to
5323 write my own collector as a shell script while I waited for feedback
5324 from him. Via
5325 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
5326 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
5327 discovered
5328 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
5329 available in Debian.&lt;/p&gt;
5330
5331 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
5332 battery stats ever since. Now my
5333 /var/log/hjemmenett-battery-status.log file contain around 115,000
5334 measurements, from the time the battery was working great until now,
5335 when it is unable to charge above 7% of original capacity. My
5336 collector shell script is quite simple and look like this:&lt;/p&gt;
5337
5338 &lt;pre&gt;
5339 #!/bin/sh
5340 # Inspired by
5341 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
5342 # See also
5343 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
5344 logfile=/var/log/hjemmenett-battery-status.log
5345
5346 files=&quot;manufacturer model_name technology serial_number \
5347 energy_full energy_full_design energy_now cycle_count status&quot;
5348
5349 if [ ! -e &quot;$logfile&quot; ] ; then
5350 (
5351 printf &quot;timestamp,&quot;
5352 for f in $files; do
5353 printf &quot;%s,&quot; $f
5354 done
5355 echo
5356 ) &gt; &quot;$logfile&quot;
5357 fi
5358
5359 log_battery() {
5360 # Print complete message in one echo call, to avoid race condition
5361 # when several log processes run in parallel.
5362 msg=$(printf &quot;%s,&quot; $(date +%s); \
5363 for f in $files; do \
5364 printf &quot;%s,&quot; $(cat $f); \
5365 done)
5366 echo &quot;$msg&quot;
5367 }
5368
5369 cd /sys/class/power_supply
5370
5371 for bat in BAT*; do
5372 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
5373 done
5374 &lt;/pre&gt;
5375
5376 &lt;p&gt;The script is called when the power management system detect a
5377 change in the power status (power plug in or out), and when going into
5378 and out of hibernation and suspend. In addition, it collect a value
5379 every 10 minutes. This make it possible for me know when the battery
5380 is discharging, charging and how the maximum charge change over time.
5381 The code for the Debian package
5382 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
5383 available on github&lt;/a&gt;.&lt;/p&gt;
5384
5385 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
5386
5387 &lt;pre&gt;
5388 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5389 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
5390 [...]
5391 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5392 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5393 &lt;/pre&gt;
5394
5395 &lt;p&gt;I wrote a small script to create a graph of the charge development
5396 over time. This graph depicted above show the slow death of my laptop
5397 battery.&lt;/p&gt;
5398
5399 &lt;p&gt;But why is this happening? Why are my laptop batteries always
5400 dying in a year or two, while the batteries of space probes and
5401 satellites keep working year after year. If we are to believe
5402 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
5403 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
5404 chance, and the fix is to not charge the Lithium-ion batteries to 100%
5405 all the time, but to stay below 90% of full charge most of the time.
5406 I&#39;ve been told that the Tesla electric cars
5407 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
5408 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
5409 100% when preparing for a longer trip (not that I would want a car
5410 like Tesla where rights to privacy is abandoned, but that is another
5411 story), which I guess is the option we should have for laptops on
5412 Linux too.&lt;/p&gt;
5413
5414 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
5415 stop charging at 80%, unless requested to charge to 100% once in
5416 preparation for a longer trip? I found
5417 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
5418 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5419 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
5420 load).&lt;/p&gt;
5421
5422 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
5423 at the start. I also wonder why the &quot;full capacity&quot; increases some
5424 times, and if it is possible to repeat the process to get the battery
5425 back to design capacity. And I wonder if the discharge and charge
5426 speed change over time, or if this stay the same. I did not yet try
5427 to write a tool to calculate the derivative values of the battery
5428 level, but suspect some interesting insights might be learned from
5429 those.&lt;/p&gt;
5430
5431 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
5432 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5433 packages instead of the tp-smapi-dkms package I had tried to use
5434 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
5435 and stop. I&#39;ve done so now, but expect my existing battery is toast
5436 and need to be replaced. The proposal is unfortunately Thinkpad
5437 specific.&lt;/p&gt;
5438 </description>
5439 </item>
5440
5441 <item>
5442 <title>New laptop - some more clues and ideas based on feedback</title>
5443 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
5444 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
5445 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
5446 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
5447 need for a new laptop, and provided very useful feedback. I wish to
5448 thank every one of these. Several pointed me to the possibility of
5449 fixing my X230, and I am already in the process of getting Lenovo to
5450 do so thanks to the on site, next day support contract covering the
5451 machine. But the battery is almost useless (I expect to replace it
5452 with a non-official battery) and I do not expect the machine to live
5453 for many more years, so it is time to plan its replacement. If I did
5454 not have a support contract, it was suggested to find replacement parts
5455 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
5456 might present a language barrier as I do not understand French.&lt;/p&gt;
5457
5458 &lt;p&gt;One tip I got was to use the
5459 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
5460 compare laptop models. It seem to have more models available than
5461 prisjakt.no. Another tip I got from someone I know have similar
5462 keyboard preferences was that the HP EliteBook 840 keyboard is not
5463 very good, and this matches my experience with earlier EliteBook
5464 keyboards I tested. Because of this, I will not consider it any further.
5465
5466 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
5467 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5468 (which is missing from the X240), and is working fairly well with
5469 Debian Sid/Unstable according to
5470 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
5471 got on the keyboard quality are not consistent. Some say the keyboard
5472 is good, others say it is ok, while others say it is not very good.
5473 Those with experience from X41 and and X60 agree that the X250
5474 keyboard is not as good as those trusty old laptops, and suggest I
5475 keep and fix my X230 instead of upgrading, or get a used X230 to
5476 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
5477 activity and battery status, which is very convenient on my X230. I&#39;m
5478 also told that the CPU fan is running very often, making it a bit
5479 noisy. In any case, the X250 do not work out of the box with Debian
5480 Stable/Jessie, one of my requirements.&lt;/p&gt;
5481
5482 &lt;p&gt;I have also gotten a few vendor proposals, one was
5483 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
5484 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
5485 The latter look very attractive to me.&lt;/p&gt;
5486
5487 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
5488 as I keep looking for a replacement.&lt;/p&gt;
5489
5490 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
5491 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
5492 different
5493 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
5494 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
5495 </description>
5496 </item>
5497
5498 <item>
5499 <title>Time to find a new laptop, as the old one is broken after only two years</title>
5500 <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>
5501 <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>
5502 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
5503 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
5504 replacement soon. The left 5 cm of the screen on my Thinkpad X230
5505 started flickering yesterday, and I suspect the cause is a broken
5506 cable, as changing the angle of the screen some times get rid of the
5507 flickering.&lt;/p&gt;
5508
5509 &lt;p&gt;My requirements have not really changed since I bought it, and is
5510 still as
5511 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
5512 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
5513 good help from
5514 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
5515 where I could select at least a few of the requirements (mouse pin,
5516 wifi, weight) and go through the rest manually. Three button mouse
5517 and a good keyboard is not available as an option, and all the three
5518 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
5519 G2) lack three mouse buttons). It is also unclear to me how good the
5520 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5521 the keyboard, even if the quality and robustness in the X series have
5522 deteriorated since X41.&lt;/p&gt;
5523
5524 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
5525 seem sensible to me? Are there better services around to search the
5526 set of available laptops for features? Please send me an email if you
5527 have suggestions.&lt;/p&gt;
5528
5529 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
5530 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
5531 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
5532 </description>
5533 </item>
5534
5535 <item>
5536 <title>How to stay with sysvinit in Debian Jessie</title>
5537 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
5538 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
5539 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
5540 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
5541 sysvinit as its boot system by default. But how can one keep using
5542 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5543 courtesy of
5544 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
5545 Schubert&lt;/a&gt; and
5546 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
5547 McVittie&lt;/a&gt;.
5548
5549 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
5550 keep sysvinit as your boot system, create a file
5551 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
5552 you upgrade:&lt;/p&gt;
5553
5554 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5555 Package: systemd-sysv
5556 Pin: release o=Debian
5557 Pin-Priority: -1
5558 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5559
5560 &lt;p&gt;This file content will tell apt and aptitude to not consider
5561 installing systemd-sysv as part of any installation and upgrade
5562 solution when resolving dependencies, and thus tell it to avoid
5563 systemd as a default boot system. The end result should be that the
5564 upgraded system keep using sysvinit.&lt;/p&gt;
5565
5566 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
5567 get sysvinit installed by default (debootstrap used by
5568 debian-installer have no option for this), but one can tell the
5569 installer to switch to sysvinit before the first boot. Either by
5570 using a kernel argument to the installer, or by adding a line to the
5571 preseed file used. First, the kernel command line argument:
5572
5573 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5574 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
5575 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5576
5577 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
5578
5579 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5580 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5581 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5582
5583 &lt;p&gt;One can of course also do this after the first boot by installing
5584 the sysvinit-core package.&lt;/p&gt;
5585
5586 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
5587 sysvinit boot sequence in Debian have several hardware specific bugs
5588 on Linux caused by the fact that it is unpredictable when hardware
5589 devices show up during boot. But on the other hand, the new default
5590 boot system still have a few rough edges I hope will be fixed before
5591 Jessie is released.&lt;/p&gt;
5592
5593 &lt;p&gt;Update 2014-11-26: Inspired by
5594 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5595 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5596 line.&lt;/p&gt;
5597 </description>
5598 </item>
5599
5600 <item>
5601 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5602 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5603 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5604 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5605 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5606 without anyone snooping, is a right every citicen have in a liberal
5607 democracy. But this right is under serious attack these days.&lt;/p&gt;
5608
5609 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5610 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5611 the whisleblower Snowden) more expensive for Internet email,
5612 is to deliver all email using SMTP via Tor. Such SMTP option would be
5613 a nice addition to the FreedomBox project if we could send email
5614 between FreedomBox machines without leaking metadata about the emails
5615 to the people peeking on the wire. I
5616 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5617 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5618 lot of useful feedback and suggestions. It also became obvious to me
5619 that this was not a novel idea, as the same idea was tested and
5620 documented by Johannes Berg as early as 2006, and both
5621 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5622 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5623 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5624
5625 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5626 providing the SMTP protocol on port 25, and use email addresses
5627 looking like username@hidden-service-name.onion. With such addresses
5628 the connections to port 25 on hidden-service-name.onion using Tor will
5629 go to the correct SMTP server. To do this, one need to configure the
5630 Tor daemon to provide the hidden service and the mail server to accept
5631 emails for this .onion domain. To learn more about Exim configuration
5632 in Debian and test the design provided by Johannes Berg in his FAQ, I
5633 set out yesterday to create a Debian package for making it trivial to
5634 set up such SMTP over Tor service based on Debian. Getting it to work
5635 were fairly easy, and
5636 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5637 source code for the Debian package&lt;/a&gt; is available from github. I
5638 plan to move it into Debian if further testing prove this to be a
5639 useful approach.&lt;/p&gt;
5640
5641 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5642 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5643 get rid of exim4). Install tor, clone the git repository mentioned
5644 above, build the deb and install it on the machine. Next, run
5645 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5646 the instructions to get the service up and running. Restart tor and
5647 exim when it is done, and test mail delivery using swaks like
5648 this:&lt;/p&gt;
5649
5650 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5651 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5652 --to fbx@dutlqrrmjhtfa3vp.onion
5653 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5654
5655 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5656 address with your own address to test your server. :)&lt;/p&gt;
5657
5658 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5659 easier and more automatic. Especially the tor setup need more work.
5660 Also, the package include a tor-smtp tool written in C, but its task
5661 should probably be rewritten in some script language to make the deb
5662 architecture independent. It would probably also make the code easier
5663 to review. The tor-smtp tool currently need to listen on a socket for
5664 exim to talk to it and is started using xinetd. It would be better if
5665 no daemon and no socket is needed. I suspect it is possible to get
5666 exim to run a command line tool for delivery instead of talking to a
5667 socket, and hope to figure out how in a future version of this
5668 system.&lt;/p&gt;
5669
5670 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5671 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5672 SMTorP. :)&lt;/p&gt;
5673 </description>
5674 </item>
5675
5676 <item>
5677 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5678 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5679 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5680 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5681 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5682 alioth.debian.org, you know the web interface is fairly slow to
5683 operate. First you visit one web page, enter the moderation password
5684 and get a new page shown with a list of all the messages to moderate
5685 and various options for each email address. This take a while for
5686 every list you moderate, and you need to do it regularly to do a good
5687 job as a list moderator. But there is a quick alternative,
5688 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5689 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5690 to moderate in a fraction of a second. Here is a test run on two
5691 lists I recently took over:&lt;/p&gt;
5692
5693 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5694 % time listadmin xiph
5695 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5696 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5697
5698 real 0m1.709s
5699 user 0m0.232s
5700 sys 0m0.012s
5701 %
5702 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5703
5704 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5705 there are no message in the moderation queue. Every morning I
5706 currently moderate 68 mailman lists, and it normally take around two
5707 minutes. When I took over the two pkg-xiph lists above a few days
5708 ago, there were 400 emails waiting in the moderator queue. It took me
5709 less than 15 minutes to process them all using the listadmin
5710 program.&lt;/p&gt;
5711
5712 &lt;p&gt;If you install
5713 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
5714 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
5715 with content like this, the moderation task is a breeze:&lt;/p&gt;
5716
5717 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5718 username username@example.org
5719 spamlevel 23
5720 default discard
5721 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
5722
5723 password secret
5724 adminurl https://{domain}/mailman/admindb/{list}
5725 mailman-list@lists.example.com
5726
5727 password hidden
5728 other-list@otherserver.example.org
5729 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5730
5731 &lt;p&gt;There are other options to set as well. Check the manual page to
5732 learn the details.&lt;/p&gt;
5733
5734 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
5735 the SSL certificate is self signed or not properly signed by a
5736 generally accepted signing authority, you can set a environment
5737 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
5738
5739 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5740 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
5741 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5742
5743 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
5744 can provide an argument to the listadmin script like I do in the
5745 initial screen dump (the xiph argument). Using an argument, only
5746 lists matching the argument string will be processed. This make it
5747 quick to accept messages if you notice the moderation request in your
5748 email.&lt;/p&gt;
5749
5750 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
5751 mailing lists, as I simply do not have time to spend on that if the
5752 process was any slower. The listadmin program have saved me hours of
5753 time I could spend elsewhere over the years. It truly is nice free
5754 software.&lt;/p&gt;
5755
5756 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5757 activities, please send Bitcoin donations to my address
5758 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5759
5760 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
5761 configuration example. Also, I&#39;ve been told that the
5762 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
5763 sure why.&lt;/p&gt;
5764 </description>
5765 </item>
5766
5767 <item>
5768 <title>Debian Jessie, PXE and automatic firmware installation</title>
5769 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
5770 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
5771 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
5772 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
5773 problem that the WiFi card require some firmware to work properly.
5774 And it has been a pain to fix this using preseeding in Debian.
5775 Normally something more is needed. But thanks to
5776 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
5777 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
5778 to do this using simple preseeding.&lt;/p&gt;
5779
5780 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
5781 firmware for the hardware found in the machine (actually, requested by
5782 the kernel modules for the hardware). (It can also install user space
5783 programs supporting the hardware detected, but that is not the focus
5784 of this story.)&lt;/p&gt;
5785
5786 &lt;p&gt;To get this working in the default installation, two preeseding
5787 values are needed. First, the isenkram-cli package must be installed
5788 into the target chroot (aka the hard drive) before tasksel is executed
5789 in the pkgsel step of the debian-installer system. This is done by
5790 preseeding the base-installer/includes debconf value to include the
5791 isenkram-cli package. The package name is next passed to debootstrap
5792 for installation. With the isenkram-cli package in place, tasksel
5793 will automatically use the isenkram tasks to detect hardware specific
5794 packages for the machine being installed and install them, because
5795 isenkram-cli contain tasksel tasks.&lt;/p&gt;
5796
5797 &lt;p&gt;Second, one need to enable the non-free APT repository, because
5798 most firmware unfortunately is non-free. This is done by preseeding
5799 the apt-mirror-setup step. This is unfortunate, but for a lot of
5800 hardware it is the only option in Debian.&lt;/p&gt;
5801
5802 &lt;p&gt;The end result is two lines needed in your preseeding file to get
5803 firmware installed automatically by the installer:&lt;/p&gt;
5804
5805 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5806 base-installer base-installer/includes string isenkram-cli
5807 apt-mirror-setup apt-setup/non-free boolean true
5808 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5809
5810 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
5811 both firmware and user space packages when using this method. It also
5812 do not work well, so use version 0.15 or later. Installing both
5813 firmware and user space packages might give you a bit more than you
5814 want, so I decided to split the tasksel task in two, one for firmware
5815 and one for user space programs. The firmware task is enabled by
5816 default, while the one for user space programs is not. This split is
5817 implemented in the package currently in unstable.&lt;/p&gt;
5818
5819 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
5820 this recipe work for you. :)&lt;/p&gt;
5821
5822 &lt;p&gt;So, I bet you are wondering, how can this work. First and
5823 foremost, it work because tasksel is modular, and driven by whatever
5824 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5825 isenkram-cli package place two files for tasksel to find. First there
5826 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
5827
5828 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5829 Task: isenkram-packages
5830 Section: hardware
5831 Description: Hardware specific packages (autodetected by isenkram)
5832 Based on the detected hardware various hardware specific packages are
5833 proposed.
5834 Test-new-install: show show
5835 Relevance: 8
5836 Packages: for-current-hardware
5837
5838 Task: isenkram-firmware
5839 Section: hardware
5840 Description: Hardware specific firmware packages (autodetected by isenkram)
5841 Based on the detected hardware various hardware specific firmware
5842 packages are proposed.
5843 Test-new-install: mark show
5844 Relevance: 8
5845 Packages: for-current-hardware-firmware
5846 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5847
5848 &lt;p&gt;The key parts are Test-new-install which indicate how the task
5849 should be handled and the Packages line referencing to a script in
5850 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5851 list of packages to install. The for-current-hardware-firmware script
5852 look like this to list relevant firmware for the machine:
5853
5854 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5855 #!/bin/sh
5856 #
5857 PATH=/usr/sbin:$PATH
5858 export PATH
5859 isenkram-autoinstall-firmware -l
5860 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5861
5862 &lt;p&gt;With those two pieces in place, the firmware is installed by
5863 tasksel during the normal d-i run. :)&lt;/p&gt;
5864
5865 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
5866 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
5867 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
5868 install.&lt;/p&gt;
5869
5870 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
5871 pilots in testing this feature, as isenkram is used there now to
5872 install firmware, replacing the earlier scripts.&lt;/p&gt;
5873 </description>
5874 </item>
5875
5876 <item>
5877 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
5878 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
5879 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
5880 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
5881 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
5882 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5883 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
5884 on a screen normally showing the bread types and prizes:&lt;/p&gt;
5885
5886 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
5887
5888 &lt;p&gt;If it had booted as it was supposed to, I would never had known
5889 about this hidden Linux installation. It is interesting what
5890 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
5891 </description>
5892 </item>
5893
5894 <item>
5895 <title>New lsdvd release version 0.17 is ready</title>
5896 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
5897 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
5898 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
5899 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
5900 got a new set of developers a few weeks ago, after the original
5901 developer decided to step down and pass the project to fresh blood.
5902 This project is now maintained by Petter Reinholdtsen and Steve
5903 Dibb.&lt;/p&gt;
5904
5905 &lt;p&gt;I just wrapped up
5906 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
5907 new lsdvd release&lt;/a&gt;, available in git or from
5908 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
5909 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
5910 0.17.&lt;/p&gt;
5911
5912 &lt;ul&gt;
5913
5914 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
5915 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
5916 non-existant, to work around additional copy protection&lt;/li&gt;
5917 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
5918 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
5919 &lt;li&gt;Fix include orders&lt;/li&gt;
5920 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
5921 &lt;li&gt;Fix the chapter count&lt;/li&gt;
5922 &lt;li&gt;Make sure the array size and the array limit used when initialising
5923 the palette size is the same.&lt;/li&gt;
5924 &lt;li&gt;Fix array printing.&lt;/li&gt;
5925 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
5926 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
5927 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
5928 with more GCC compiler warnings.&lt;/li&gt;
5929
5930 &lt;/ul&gt;
5931
5932 &lt;p&gt;This change bring together patches for lsdvd in use in various
5933 Linux and Unix distributions, as well as patches submitted to the
5934 project the last nine years. Please check it out. :)&lt;/p&gt;
5935 </description>
5936 </item>
5937
5938 <item>
5939 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
5940 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
5941 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
5942 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
5943 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5944 project&lt;/a&gt; provide a Linux solution for schools, including a
5945 powerful desktop with education software, a central server providing
5946 web pages, user database, user home directories, central login and PXE
5947 boot of both clients without disk and the installation to install Debian
5948 Edu on machines with disk (and a few other services perhaps to small
5949 to mention here). We in the Debian Edu team are currently working on
5950 the Jessie based version, trying to get everything in shape before the
5951 freeze, to avoid having to maintain our own package repository in the
5952 future. The
5953 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
5954 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
5955 work left. Some fatal problems block testing, breaking the installer,
5956 but it is possible to work around these to get anyway. Here is a
5957 recipe on how to get the installation limping along.&lt;/p&gt;
5958
5959 &lt;p&gt;First, download the test ISO via
5960 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
5961 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
5962 or rsync (use
5963 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
5964 The ISO build was broken on Tuesday, so we do not get a new ISO every
5965 12 hours or so, but thankfully the ISO we already got we are able to
5966 install with some tweaking.&lt;/p&gt;
5967
5968 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
5969 (use Alt-Ctrl-F2), run&lt;/p&gt;
5970
5971 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5972 nano /usr/bin/edu-eatmydata-install
5973 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5974
5975 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
5976 optimization. Return to the installation, select the profile you want
5977 and continue. Without this change, exim4-config will fail to install
5978 due to a known bug in eatmydata.&lt;/p&gt;
5979
5980 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
5981 this do not work, figure out what your correct value would be. All my
5982 test machines need /dev/sda, so I have no advice if it do not fit
5983 your need.&lt;/p&gt;
5984
5985 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
5986 root after the initial boot from hard drive, and install the
5987 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5988 or mate. If you want several desktop options, install more than one
5989 metapackage. Once this is done, reboot and you should have a working
5990 graphical login screen. This workaround should no longer be needed
5991 once the education-tasks package version 1.801 enter testing in two
5992 days.&lt;/p&gt;
5993
5994 &lt;p&gt;I believe the ISO build will start working on two days when the new
5995 tasksel package enter testing and Steve McIntyre get a chance to
5996 update the debian-cd git repository. The eatmydata, grub and desktop
5997 issues are already fixed in unstable and testing, and should show up
5998 on the ISO as soon as the ISO build start working again. Well the
5999 eatmydata optimization is really just disabled. The proper fix
6000 require an upload by the eatmydata maintainer applying the patch
6001 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
6002 The rest have proper fixes in unstable.&lt;/p&gt;
6003
6004 &lt;p&gt;I hope this get you going with the installation testing, as we are
6005 quickly running out of time trying to get our Jessie based
6006 installation ready before the distribution freeze in a month.&lt;/p&gt;
6007 </description>
6008 </item>
6009
6010 <item>
6011 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
6012 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
6013 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
6014 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
6015 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
6016 to handle my fairly large DVD collection. It is a nice command line
6017 tool to get details about a DVD, like title, tracks, track length,
6018 etc, in XML, Perl or human readable format. But lsdvd have not seen
6019 any new development since 2006 and had a few irritating bugs affecting
6020 its use with some DVDs. Upstream seemed to be dead, and in January I
6021 sent a small probe asking for a version control repository for the
6022 project, without any reply. But I use it regularly and would like to
6023 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
6024 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
6025 the project admin, and after getting a reply from him explaining that
6026 he was no longer interested in the project, I asked if I could take
6027 over. And yesterday, I became project admin.&lt;/p&gt;
6028
6029 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
6030 maintainer interested in joining forces to maintain the upstream
6031 project, and I hope we can get a new release out fairly quickly,
6032 collecting the patches spread around on the internet into on place.
6033 I&#39;ve added the relevant Debian patches to the freshly created git
6034 repository, and expect the Gentoo patches to make it too. If you got
6035 a DVD collection and care about command line tools, check out
6036 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
6037 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
6038 list&lt;/a&gt;. :)&lt;/p&gt;
6039 </description>
6040 </item>
6041
6042 <item>
6043 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
6044 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
6045 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
6046 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
6047 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
6048 a lot quicker. When we install more than 2000 packages in
6049 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
6050 tasksel in the installer, unpacking the binary packages take forever.
6051 A part of the slow I/O issue was discussed in
6052 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
6053 much file system sync-ing done by dpkg, which is the package
6054 responsible for unpacking the binary packages. Other parts (like code
6055 executed by postinst scripts) might also sync to disk during
6056 installation. All this sync-ing to disk do not really make sense to
6057 me. If the machine crash half-way through, I start over, I do not try
6058 to salvage the half installed system. So the failure sync-ing is
6059 supposed to protect against, hardware or system crash, is not really
6060 relevant while the installer is running.&lt;/p&gt;
6061
6062 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
6063 system sync()-ing in a fairly non-intrusive way, without the need to
6064 change the code in several packages. The idea is not new, but I have
6065 not heard anyone propose the approach using dpkg-divert before. It
6066 depend on the small and clever package
6067 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
6068 uses LD_PRELOAD to replace the system functions for syncing data to
6069 disk with functions doing nothing, thus allowing programs to live
6070 dangerous while speeding up disk I/O significantly. Instead of
6071 modifying the implementation of dpkg, apt and tasksel (which are the
6072 packages responsible for selecting, fetching and installing packages),
6073 it occurred to me that we could just divert the programs away, replace
6074 them with a simple shell wrapper calling
6075 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
6076 Two days ago I decided to test the idea, and wrapped up a simple
6077 implementation for the Debian Edu udeb.&lt;/p&gt;
6078
6079 &lt;p&gt;The effect was stunning. In my first test it reduced the running
6080 time of the pkgsel step (installing tasks) from 64 to less than 44
6081 minutes (20 minutes shaved off the installation) on an old Dell
6082 Latitude D505 machine. I am not quite sure what the optimised time
6083 would have been, as I messed up the testing a bit, causing the debconf
6084 priority to get low enough for two questions to pop up during
6085 installation. As soon as I saw the questions I moved the installation
6086 along, but do not know how long the question were holding up the
6087 installation. I did some more measurements using Debian Edu Jessie,
6088 and got these results. The time measured is the time stamp in
6089 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
6090 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
6091 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6092 timing thus do not depend on how quickly the user handle the tasksel
6093 dialog.&lt;/p&gt;
6094
6095 &lt;p&gt;&lt;table&gt;
6096
6097 &lt;tr&gt;
6098 &lt;th&gt;Machine/setup&lt;/th&gt;
6099 &lt;th&gt;Original tasksel&lt;/th&gt;
6100 &lt;th&gt;Optimised tasksel&lt;/th&gt;
6101 &lt;th&gt;Reduction&lt;/th&gt;
6102 &lt;/tr&gt;
6103
6104 &lt;tr&gt;
6105 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
6106 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
6107 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
6108 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
6109 &lt;/tr&gt;
6110
6111 &lt;tr&gt;
6112 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
6113 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
6114 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
6115 &lt;td&gt;23 min 40%&lt;/td&gt;
6116 &lt;/tr&gt;
6117
6118 &lt;tr&gt;
6119 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
6120 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
6121 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
6122 &lt;td&gt;11 min 50%&lt;/td&gt;
6123 &lt;/tr&gt;
6124
6125 &lt;tr&gt;
6126 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
6127 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
6128 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
6129 &lt;td&gt;2 min 33%&lt;/td&gt;
6130 &lt;/tr&gt;
6131
6132 &lt;tr&gt;
6133 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
6134 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
6135 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
6136 &lt;td&gt;4 min 21%&lt;/td&gt;
6137 &lt;/tr&gt;
6138
6139 &lt;/table&gt;&lt;/p&gt;
6140
6141 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
6142 time is spent downloading packages. The connection to the Internet
6143 was 100Mbit/s during testing, so downloading should not be a
6144 significant factor in the measurement. Download typically took a few
6145 seconds to a few minutes, depending on the amount of packages being
6146 installed.&lt;/p&gt;
6147
6148 &lt;p&gt;The speedup is implemented by using two hooks in
6149 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
6150 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
6151 finish-install.d hook to remove the divert at the end of the
6152 installation. I picked the pre-pkgsel.d hook instead of the
6153 post-base-installer.d hook because I test using an ISO without the
6154 eatmydata package included, and the post-base-installer.d hook in
6155 Debian Edu can only operate on packages included in the ISO. The
6156 negative effect of this is that I am unable to activate this
6157 optimization for the kernel installation step in d-i. If the code is
6158 moved to the post-base-installer.d hook, the speedup would be larger
6159 for the entire installation.&lt;/p&gt;
6160
6161 &lt;p&gt;I&#39;ve implemented this in the
6162 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
6163 git repository, and plan to provide the optimization as part of the
6164 Debian Edu installation. If you want to test this yourself, you can
6165 create two files in the installer (or in an udeb). One shell script
6166 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
6167
6168 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6169 #!/bin/sh
6170 set -e
6171 . /usr/share/debconf/confmodule
6172 info() {
6173 logger -t my-pkgsel &quot;info: $*&quot;
6174 }
6175 error() {
6176 logger -t my-pkgsel &quot;error: $*&quot;
6177 }
6178 override_install() {
6179 apt-install eatmydata || true
6180 if [ -x /target/usr/bin/eatmydata ] ; then
6181 for bin in dpkg apt-get aptitude tasksel ; do
6182 file=/usr/bin/$bin
6183 # Test that the file exist and have not been diverted already.
6184 if [ -f /target$file ] ; then
6185 info &quot;diverting $file using eatmydata&quot;
6186 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
6187 &gt; /target$file.edu
6188 chmod 755 /target$file.edu
6189 in-target dpkg-divert --package debian-edu-config \
6190 --rename --quiet --add $file
6191 ln -sf ./$bin.edu /target$file
6192 else
6193 error &quot;unable to divert $file, as it is missing.&quot;
6194 fi
6195 done
6196 else
6197 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
6198 fi
6199 }
6200
6201 override_install
6202 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6203
6204 &lt;p&gt;To clean up, another shell script should go into
6205 /usr/lib/finish-install.d/ with code like this:
6206
6207 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6208 #! /bin/sh -e
6209 . /usr/share/debconf/confmodule
6210 error() {
6211 logger -t my-finish-install &quot;error: $@&quot;
6212 }
6213 remove_install_override() {
6214 for bin in dpkg apt-get aptitude tasksel ; do
6215 file=/usr/bin/$bin
6216 if [ -x /target$file.edu ] ; then
6217 rm /target$file
6218 in-target dpkg-divert --package debian-edu-config \
6219 --rename --quiet --remove $file
6220 rm /target$file.edu
6221 else
6222 error &quot;Missing divert for $file.&quot;
6223 fi
6224 done
6225 sync # Flush file buffers before continuing
6226 }
6227
6228 remove_install_override
6229 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6230
6231 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
6232 edu-eatmydata-install and call it from the pre-pkgsel.d and
6233 finish-install.d scripts.&lt;/p&gt;
6234
6235 &lt;p&gt;By now you might ask if this change should get into the normal
6236 Debian installer too? I suspect it should, but am not sure the
6237 current debian-installer coordinators find it useful enough. It also
6238 depend on the side effects of the change. I&#39;m not aware of any, but I
6239 guess we will see if the change is safe after some more testing.
6240 Perhaps there is some package in Debian depending on sync() and
6241 fsync() having effect? Perhaps it should go into its own udeb, to
6242 allow those of us wanting to enable it to do so without affecting
6243 everyone.&lt;/p&gt;
6244
6245 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
6246 will break installation of all programs using gnutls because of
6247 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
6248 eatmydata package in Debian will solve it.&lt;/p&gt;
6249
6250 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
6251 the optimization work again. And I have discovered that the
6252 dpkg-divert trick is not really needed and implemented a slightly
6253 simpler approach as part of the debian-edu-install package. See
6254 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
6255
6256 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
6257 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
6258 triggering on i386 made it into testing, and broke this installation
6259 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
6260 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
6261 </description>
6262 </item>
6263
6264 <item>
6265 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
6266 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
6267 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
6268 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
6269 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
6270 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
6271 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
6272 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
6273 learn that there is a large set of publicly available key servers to
6274 use when looking for peoples public key. So far I have used
6275 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6276 were misbehaving, but those days are ended. The servers I have used
6277 up until yesterday have been slow and some times unavailable. I hope
6278 those problems are gone now.&lt;/p&gt;
6279
6280 &lt;p&gt;Behind the round robin DNS entry of the
6281 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
6282 there is a pool of more than 100 keyservers which are checked every
6283 day to ensure they are well connected and up to date. It must be
6284 better than what I have used so far. :)&lt;/p&gt;
6285
6286 &lt;p&gt;Yesterdays speaker told me that the service is the default
6287 keyserver provided by the default configuration in GnuPG, but this do
6288 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
6289
6290 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
6291 line:&lt;/p&gt;
6292
6293 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6294 keyserver pool.sks-keyservers.net
6295 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6296
6297 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
6298 entries in DNS. Just for fun, I did just that at work, so now every
6299 user of GnuPG at the University of Oslo should find a OpenGPG
6300 keyserver automatically should their need it:&lt;/p&gt;
6301
6302 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6303 % host -t srv _pgpkey-http._tcp.uio.no
6304 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
6305 %
6306 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6307
6308 &lt;p&gt;Now if only
6309 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
6310 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
6311 very happy. It can look up a given key or search for a user ID, but I
6312 normally do not want that, but to find a trust path from my key to
6313 another key. Given a user ID or key ID, I would like to find (and
6314 download) the keys representing a signature path from my key to the
6315 key in question, to be able to get a trust path between the two keys.
6316 This is as far as I can tell not possible today. Perhaps something
6317 for a future version of the protocol?&lt;/p&gt;
6318 </description>
6319 </item>
6320
6321 <item>
6322 <title>From English wiki to translated PDF and epub via Docbook</title>
6323 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
6324 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
6325 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
6326 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6327 project&lt;/a&gt; provide an instruction manual for teachers, system
6328 administrators and other users that contain useful tips for setting up
6329 and maintaining a Debian Edu installation. This text is about how the
6330 text processing of this manual is handled in the project.&lt;/p&gt;
6331
6332 &lt;p&gt;One goal of the project is to provide information in the native
6333 language of its users, and for this we need to handle translations.
6334 But we also want to make sure each language contain the same
6335 information, so for this we need a good way to keep the translations
6336 in sync. And we want it to be easy for our users to improve the
6337 documentation, avoiding the need to learn special formats or tools to
6338 contribute, and the obvious way to do this is to make it possible to
6339 edit the documentation using a web browser. We also want it to be
6340 easy for translators to keep the translation up to date, and give them
6341 help in figuring out what need to be translated. Here is the list of
6342 tools and the process we have found trying to reach all these
6343 goals.&lt;/p&gt;
6344
6345 &lt;p&gt;We maintain the authoritative source of our manual in the
6346 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
6347 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
6348 front page with references to the different chapters, several pages
6349 for each chapter, and finally one &quot;collection page&quot; gluing all the
6350 chapters together into one large web page (aka
6351 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
6352 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
6353 processing and translations. Thanks to the fact that the
6354 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
6355 wiki.debian.org support exporting pages in
6356 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
6357 the list of pages to export using the raw version of the AllInOne
6358 page, loop over each of them to generate a Docbook XML version of the
6359 manual. This process also download images and transform image
6360 references to use the locally downloaded images. The generated
6361 Docbook XML files are slightly broken, so some post-processing is done
6362 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
6363 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6364 a handfull of images. The XML file can now be used to generate PDF, HTML
6365 and epub versions of the English manual. This is the basic step of
6366 our process, making PDF (using dblatex), HTML (using xsltproc) and
6367 epub (using dbtoepub) version from Docbook XML, and the resulting files
6368 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
6369
6370 &lt;p&gt;But English documentation is not enough for us. We want translated
6371 documentation too, and we want to make it easy for translators to
6372 track the English original. For this we use the
6373 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
6374 which allow us to transform the English Docbook XML file into a
6375 translation file (a .pot file), usable with the normal gettext based
6376 translation tools used by those translating free software. The pot
6377 file is used to create and maintain translation files (several .po
6378 files), which the translations update with the native language
6379 translations of all titles, paragraphs and blocks of text in the
6380 original. The next step is combining the original English Docbook XML
6381 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6382 create a translated Docbook XML file (in this case
6383 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6384 translated, if the translation is not complete) Docbook XML file can
6385 then be used like the original to create a PDF, HTML and epub version
6386 of the documentation.&lt;/p&gt;
6387
6388 &lt;p&gt;The translators use different tools to edit the .po files. We
6389 recommend using
6390 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
6391 while some use emacs and vi, others can use web based editors like
6392 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
6393 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
6394 is where the .po file end up, in our git repository. Updated
6395 translations can either be committed directly to git, or submitted as
6396 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
6397 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
6398
6399 &lt;p&gt;One challenge is images, which both might need to be translated (if
6400 they show translated user applications), and are needed in different
6401 formats when creating PDF and HTML versions (epub is a HTML version in
6402 this regard). For this we transform the original PNG images to the
6403 needed density and format during build, and have a way to provide
6404 translated images by storing translated versions in
6405 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6406 package maintainers know more.&lt;/p&gt;
6407
6408 &lt;p&gt;If you wonder what the result look like, we provide
6409 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
6410 of the documentation packages on the web&lt;/a&gt;. See for example the
6411 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
6412 PDF version&lt;/a&gt; or the
6413 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
6414 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
6415 but perhaps it will be done in the future.&lt;/p&gt;
6416
6417 &lt;p&gt;To learn more, check out
6418 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
6419 debian-edu-doc package&lt;/a&gt;,
6420 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
6421 manual on the wiki&lt;/a&gt; and
6422 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
6423 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
6424 </description>
6425 </item>
6426
6427 <item>
6428 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
6429 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
6430 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
6431 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
6432 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
6433 related packages relevant for the computer installed automatically.
6434 So I implemented one, using
6435 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
6436 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
6437 run tasksel as user root. You should be presented with a new option,
6438 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
6439 select it, tasksel will install the packages isenkram claim is fit for
6440 the current hardware, hot pluggable or not.&lt;p&gt;
6441
6442 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
6443 description, and the other is the script used to extract the list of
6444 packages to install. The first part is in
6445 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
6446 this:&lt;/p&gt;
6447
6448 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6449 Task: isenkram
6450 Section: hardware
6451 Description: Hardware specific packages (autodetected by isenkram)
6452 Based on the detected hardware various hardware specific packages are
6453 proposed.
6454 Test-new-install: mark show
6455 Relevance: 8
6456 Packages: for-current-hardware
6457 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6458
6459 &lt;p&gt;The second part is in
6460 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
6461 this:&lt;/p&gt;
6462
6463 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6464 #!/bin/sh
6465 #
6466 (
6467 isenkram-lookup
6468 isenkram-autoinstall-firmware -l
6469 ) | sort -u
6470 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6471
6472 &lt;p&gt;All in all, a very short and simple implementation making it
6473 trivial to install the hardware dependent package we all may want to
6474 have installed on our machines. I&#39;ve not been able to find a way to
6475 get tasksel to tell you exactly which packages it plan to install
6476 before doing the installation. So if you are curious or careful,
6477 check the output from the isenkram-* command line tools first.&lt;/p&gt;
6478
6479 &lt;p&gt;The information about which packages are handling which hardware is
6480 fetched either from the isenkram package itself in
6481 /usr/share/isenkram/, from git.debian.org or from the APT package
6482 database (using the Modaliases header). The APT package database
6483 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6484 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
6485 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
6486 the python-apt code (bug
6487 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
6488 workaround I was able to get rid of the file descriptor leak and
6489 reduce the memory leak from ~30 MiB per hardware detection down to
6490 around 2 MiB per hardware detection. It should make the desktop
6491 daemon a lot more useful. The fix is in version 0.7 uploaded to
6492 unstable today.&lt;/p&gt;
6493
6494 &lt;p&gt;I believe the current way of mapping hardware to packages in
6495 Isenkram is is a good draft, but in the future I expect isenkram to
6496 use the AppStream data source for this. A proposal for getting proper
6497 AppStream support into Debian is floating around as
6498 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
6499 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
6500 project&lt;/a&gt; will take place this summer to improve the situation. I
6501 look forward to seeing the result, and welcome patches for isenkram to
6502 start using the information when it is ready.&lt;/p&gt;
6503
6504 &lt;p&gt;If you want your package to map to some specific hardware, either
6505 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
6506 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
6507 package&lt;/a&gt; or submit a bug report with the details to the isenkram
6508 package. See also
6509 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
6510 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
6511 the information will be migrated to AppStream eventually, but for the
6512 moment I got no better place to store it.&lt;/p&gt;
6513 </description>
6514 </item>
6515
6516 <item>
6517 <title>FreedomBox milestone - all packages now in Debian Sid</title>
6518 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
6519 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
6520 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
6521 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6522 project&lt;/a&gt; is working on providing the software and hardware to make
6523 it easy for non-technical people to host their data and communication
6524 at home, and being able to communicate with their friends and family
6525 encrypted and away from prying eyes. It is still going strong, and
6526 today a major mile stone was reached.&lt;/p&gt;
6527
6528 &lt;p&gt;Today, the last of the packages currently used by the project to
6529 created the system images were accepted into Debian Unstable. It was
6530 the freedombox-setup package, which is used to configure the images
6531 during build and on the first boot. Now all one need to get going is
6532 the build code from the freedom-maker git repository and packages from
6533 Debian. And once the freedombox-setup package enter testing, we can
6534 build everything directly from Debian. :)&lt;/p&gt;
6535
6536 &lt;p&gt;Some key packages used by Freedombox are
6537 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
6538 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
6539 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
6540 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
6541 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
6542 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
6543 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
6544 are plans to integrate more packages into the setup. User
6545 documentation is maintained on the Debian wiki. Please
6546 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
6547 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
6548
6549 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
6550 setup, run this on a Debian machine using a user with sudo rights to
6551 become root:&lt;/p&gt;
6552
6553 &lt;p&gt;&lt;pre&gt;
6554 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6555 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6556 u-boot-tools
6557 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6558 freedom-maker
6559 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6560 &lt;/pre&gt;&lt;/p&gt;
6561
6562 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6563 devices. See the README in the freedom-maker git repo for more
6564 details on the build. If you do not want all three images, trim the
6565 make line. Note that the virtualbox-image target is not really
6566 virtualbox specific. It create a x86 image usable in kvm, qemu,
6567 vmware and any other x86 virtual machine environment. You might need
6568 the version of vmdebootstrap in Jessie to get the build working, as it
6569 include fixes for a race condition with kpartx.&lt;/p&gt;
6570
6571 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6572 method, boot a Debian Wheezy ISO and use this boot argument to load
6573 the preseed values:&lt;/p&gt;
6574
6575 &lt;p&gt;&lt;pre&gt;
6576 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
6577 &lt;/pre&gt;&lt;/p&gt;
6578
6579 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
6580 it still work.&lt;/p&gt;
6581
6582 &lt;p&gt;If you wonder how to help, one task you could look at is using
6583 systemd as the boot system. It will become the default for Linux in
6584 Jessie, so we need to make sure it is usable on the Freedombox. I did
6585 a simple test a few weeks ago, and noticed dnsmasq failed to start
6586 during boot when using systemd. I suspect there are other problems
6587 too. :) To detect problems, there is a test suite included, which can
6588 be run from the plinth web interface.&lt;/p&gt;
6589
6590 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6591 us get the new release published. :) Please join us on
6592 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6593 irc.debian.org)&lt;/a&gt; and
6594 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6595 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6596 </description>
6597 </item>
6598
6599 <item>
6600 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6601 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6602 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6603 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6604 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6605 solution for use at home. My requirements are simple, it must be
6606 cheap and locally encrypted (in other words, I keep the encryption
6607 keys, the storage provider do not have access to my private files).
6608 One idea me and my friends had many years ago, before the cloud
6609 storage providers showed up, was to use Google mail as storage,
6610 writing a Linux block device storing blocks as emails in the mail
6611 service provided by Google, and thus get heaps of free space. On top
6612 of this one can add encryption, RAID and volume management to have
6613 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6614 I never found time to implement such system. But the last few weeks I
6615 have looked at a system called
6616 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6617 mounted network backed file system with the features I need.&lt;/p&gt;
6618
6619 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6620 handling several different storage providers, any with Amazon S3,
6621 Google Drive or OpenStack API. There are heaps of such storage
6622 providers. S3QL can also use a local directory as storage, which
6623 combined with sshfs allow for file storage on any ssh server. S3QL
6624 include support for encryption, compression, de-duplication, snapshots
6625 and immutable file systems, allowing me to mount the remote storage as
6626 a local mount point, look at and use the files as if they were local,
6627 while the content is stored in the cloud as well. This allow me to
6628 have a backup that should survive fire. The file system can not be
6629 shared between several machines at the same time, as only one can
6630 mount it at the time, but any machine with the encryption key and
6631 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6632
6633 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6634 package is included already. So to get started, run &lt;tt&gt;apt-get
6635 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6636 Greenqloud, after reading their nice recipe on
6637 &lt;a href=&quot;https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy&quot;&gt;how
6638 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6639 in Iceland more than those in USA when it come to keeping my personal
6640 data safe and private, and thus would rather spend money on a company
6641 in Iceland. Another nice recipe is available from the article
6642 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6643 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6644 Admin magazine. When the provider is picked, figure out how to get
6645 the API key needed to connect to the storage API. With Greencloud,
6646 the key did not show up until I had added payment details to my
6647 account.&lt;/p&gt;
6648
6649 &lt;p&gt;Armed with the API access details, it is time to create the file
6650 system. First, create a new bucket in the cloud. This bucket is the
6651 file system storage area. I picked a bucket name reflecting the
6652 machine that was going to store data there, but any name will do.
6653 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6654 the API login and password, and a locally created password. Store it
6655 all in ~root/.s3ql/authinfo2 like this:
6656
6657 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6658 [s3c]
6659 storage-url: s3c://s.greenqloud.com:443/bucket-name
6660 backend-login: API-login
6661 backend-password: API-password
6662 fs-passphrase: local-password
6663 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6664
6665 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6666 but any sensible way to create a fairly random password should do it.
6667 Armed with these details, it is now time to run mkfs, entering the API
6668 details and password to create it:&lt;/p&gt;
6669
6670 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6671 # mkdir -m 700 /var/lib/s3ql-cache
6672 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6673 --ssl s3c://s.greenqloud.com:443/bucket-name
6674 Enter backend login:
6675 Enter backend password:
6676 Before using S3QL, make sure to read the user&#39;s guide, especially
6677 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6678 Enter encryption password:
6679 Confirm encryption password:
6680 Generating random encryption key...
6681 Creating metadata tables...
6682 Dumping metadata...
6683 ..objects..
6684 ..blocks..
6685 ..inodes..
6686 ..inode_blocks..
6687 ..symlink_targets..
6688 ..names..
6689 ..contents..
6690 ..ext_attributes..
6691 Compressing and uploading metadata...
6692 Wrote 0.00 MB of compressed metadata.
6693 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6694
6695 &lt;p&gt;The next step is mounting the file system to make the storage available.
6696
6697 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6698 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6699 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6700 Using 4 upload threads.
6701 Downloading and decompressing metadata...
6702 Reading metadata...
6703 ..objects..
6704 ..blocks..
6705 ..inodes..
6706 ..inode_blocks..
6707 ..symlink_targets..
6708 ..names..
6709 ..contents..
6710 ..ext_attributes..
6711 Mounting filesystem...
6712 # df -h /s3ql
6713 Filesystem Size Used Avail Use% Mounted on
6714 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
6715 #
6716 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6717
6718 &lt;p&gt;The file system is now ready for use. I use rsync to store my
6719 backups in it, and as the metadata used by rsync is downloaded at
6720 mount time, no network traffic (and storage cost) is triggered by
6721 running rsync. To unmount, one should not use the normal umount
6722 command, as this will not flush the cache to the cloud storage, but
6723 instead running the umount.s3ql command like this:
6724
6725 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6726 # umount.s3ql /s3ql
6727 #
6728 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6729
6730 &lt;p&gt;There is a fsck command available to check the file system and
6731 correct any problems detected. This can be used if the local server
6732 crashes while the file system is mounted, to reset the &quot;already
6733 mounted&quot; flag. This is what it look like when processing a working
6734 file system:&lt;/p&gt;
6735
6736 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6737 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
6738 Using cached metadata.
6739 File system seems clean, checking anyway.
6740 Checking DB integrity...
6741 Creating temporary extra indices...
6742 Checking lost+found...
6743 Checking cached objects...
6744 Checking names (refcounts)...
6745 Checking contents (names)...
6746 Checking contents (inodes)...
6747 Checking contents (parent inodes)...
6748 Checking objects (reference counts)...
6749 Checking objects (backend)...
6750 ..processed 5000 objects so far..
6751 ..processed 10000 objects so far..
6752 ..processed 15000 objects so far..
6753 Checking objects (sizes)...
6754 Checking blocks (referenced objects)...
6755 Checking blocks (refcounts)...
6756 Checking inode-block mapping (blocks)...
6757 Checking inode-block mapping (inodes)...
6758 Checking inodes (refcounts)...
6759 Checking inodes (sizes)...
6760 Checking extended attributes (names)...
6761 Checking extended attributes (inodes)...
6762 Checking symlinks (inodes)...
6763 Checking directory reachability...
6764 Checking unix conventions...
6765 Checking referential integrity...
6766 Dropping temporary indices...
6767 Backing up old metadata...
6768 Dumping metadata...
6769 ..objects..
6770 ..blocks..
6771 ..inodes..
6772 ..inode_blocks..
6773 ..symlink_targets..
6774 ..names..
6775 ..contents..
6776 ..ext_attributes..
6777 Compressing and uploading metadata...
6778 Wrote 0.89 MB of compressed metadata.
6779 #
6780 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6781
6782 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
6783 quick, about the same speed as local file access. Uploading large
6784 amount of data is to me limited by the bandwidth out of and into my
6785 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
6786 which is very close to my upload speed, and downloading the same
6787 Debian installation ISO gave me 610 kiB/s, close to my download speed.
6788 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
6789 network, not the file system code. I do not know what a good cache
6790 size would be, but suspect that the cache should e larger than your
6791 working set.&lt;/p&gt;
6792
6793 &lt;p&gt;I mentioned that only one machine can mount the file system at the
6794 time. If another machine try, it is told that the file system is
6795 busy:&lt;/p&gt;
6796
6797 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6798 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6799 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6800 Using 8 upload threads.
6801 Backend reports that fs is still mounted elsewhere, aborting.
6802 #
6803 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6804
6805 &lt;p&gt;The file content is uploaded when the cache is full, while the
6806 metadata is uploaded once every 24 hour by default. To ensure the
6807 file system content is flushed to the cloud, one can either umount the
6808 file system, or ask S3QL to flush the cache and metadata using
6809 s3qlctrl:
6810
6811 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6812 # s3qlctrl upload-meta /s3ql
6813 # s3qlctrl flushcache /s3ql
6814 #
6815 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6816
6817 &lt;p&gt;If you are curious about how much space your data uses in the
6818 cloud, and how much compression and deduplication cut down on the
6819 storage usage, you can use s3qlstat on the mounted file system to get
6820 a report:&lt;/p&gt;
6821
6822 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6823 # s3qlstat /s3ql
6824 Directory entries: 9141
6825 Inodes: 9143
6826 Data blocks: 8851
6827 Total data size: 22049.38 MB
6828 After de-duplication: 21955.46 MB (99.57% of total)
6829 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
6830 Database size: 2.39 MB (uncompressed)
6831 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6832 #
6833 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6834
6835 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
6836 storage. I did not try to locate them all, but am aware of at least
6837 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
6838 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
6839 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
6840 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
6841 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
6842 accept payment in Bitcoin. Pick one that suit your need. Some of
6843 them provide several GiB of free storage, but the prize models are
6844 quite different and you will have to figure out what suits you
6845 best.&lt;/p&gt;
6846
6847 &lt;p&gt;While researching this blog post, I had a look at research papers
6848 and posters discussing the S3QL file system. There are several, which
6849 told me that the file system is getting a critical check by the
6850 science community and increased my confidence in using it. One nice
6851 poster is titled
6852 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
6853 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6854 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
6855 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6856 and Pamela Smith. Please have a look.&lt;/p&gt;
6857
6858 &lt;p&gt;Given my problems with different file systems earlier, I decided to
6859 check out the mounted S3QL file system to see if it would be usable as
6860 a home directory (in other word, that it provided POSIX semantics when
6861 it come to locking and umask handling etc). Running
6862 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html&quot;&gt;my
6863 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
6864 no error was found. So the file system can be used for home
6865 directories, if one chooses to do so.&lt;/p&gt;
6866
6867 &lt;p&gt;If you do not want a locally file system, and want something that
6868 work without the Linux fuse file system, I would like to mention the
6869 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
6870 provide locally encrypted backup using a command line client. It have
6871 a nicer access control system, where one can split out read and write
6872 access, allowing some systems to write to the backup and others to
6873 only read from it.&lt;/p&gt;
6874
6875 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6876 activities, please send Bitcoin donations to my address
6877 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6878 </description>
6879 </item>
6880
6881 <item>
6882 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
6883 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
6884 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
6885 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
6886 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6887 project&lt;/a&gt; is working on providing the software and hardware for
6888 making it easy for non-technical people to host their data and
6889 communication at home, and being able to communicate with their
6890 friends and family encrypted and away from prying eyes. It has been
6891 going on for a while, and is slowly progressing towards a new test
6892 release (0.2).&lt;/p&gt;
6893
6894 &lt;p&gt;And what day could be better than the Pi day to announce that the
6895 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
6896 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6897 system), and can also be installed using a Debian installer preseed
6898 file. The Debian based Freedombox is now based on Debian Jessie,
6899 where most of the needed packages used are already present. Only one,
6900 the freedombox-setup package, is missing. To try to build your own
6901 boot image to test the current status, fetch the freedom-maker scripts
6902 and build using
6903 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
6904 with a user with sudo access to become root:
6905
6906 &lt;pre&gt;
6907 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6908 freedom-maker
6909 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6910 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6911 u-boot-tools
6912 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6913 &lt;/pre&gt;
6914
6915 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6916 devices. See the README for more details on the build. If you do not
6917 want all three images, trim the make line. But note that thanks to &lt;a
6918 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
6919 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
6920 kpartx call.&lt;/p&gt;
6921
6922 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6923 method, boot a Debian Wheezy ISO and use this boot argument to load
6924 the preseed values:&lt;/p&gt;
6925
6926 &lt;pre&gt;
6927 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
6928 &lt;/pre&gt;
6929
6930 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
6931 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
6932 currently hang while setting up APT sources. Killing the
6933 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
6934 installation will get the installation going. This affect all
6935 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
6936
6937 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6938 us get the new release published. :) Please join us on
6939 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6940 irc.debian.org)&lt;/a&gt; and
6941 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6942 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6943 </description>
6944 </item>
6945
6946 <item>
6947 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
6948 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
6949 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
6950 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
6951 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
6952 innetgr tools, because I needed them in
6953 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
6954 ng-utils, and it has served me well. I placed the project under the
6955 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
6956 repository. But many years ago, the CVS repository was dropped (lost,
6957 not migrated to new hardware, not sure), and the project have lacked a
6958 proper home since then.&lt;/p&gt;
6959
6960 &lt;p&gt;Last summer, I had a look at the package and made a new release
6961 fixing a irritating crash bug, but was unable to store the changes in
6962 a proper source control system. I applied for a project on
6963 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
6964 to follow up on it. Until today. :)&lt;/p&gt;
6965
6966 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
6967 now have a new home, and a git repository with the highlight of the
6968 history of the project. I published all release tarballs and imported
6969 them into the git repository. As the project is really stable and not
6970 expected to gain new features any time soon, I decided to make a new
6971 release and call it 1.0. Visit the new project home on
6972 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
6973 if you want to check it out. The new version is also uploaded into
6974 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
6975 </description>
6976 </item>
6977
6978 <item>
6979 <title>Testing sysvinit from experimental in Debian Hurd</title>
6980 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
6981 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
6982 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
6983 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
6984 their changes into sysvinit, to allow them to use the normal sysvinit
6985 boot system instead of their old one. This follow up on the
6986 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
6987 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
6988 get Debian on Hurd working more like Debian on Linux. To get started,
6989 I downloaded a prebuilt hard disk image from
6990 &lt;a href=&quot;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&quot;&gt;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&lt;/a&gt;,
6991 and started it using virt-manager.&lt;/p&gt;
6992
6993 &lt;p&gt;The first think I had to do after logging in (root without any
6994 password) was to get the network operational. I followed
6995 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
6996 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
6997 commands as root to get the machine to accept a IP address from the
6998 kvm internal DHCP server:&lt;/p&gt;
6999
7000 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7001 settrans -fgap /dev/netdde /hurd/netdde
7002 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
7003 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
7004 dhclient /dev/eth0
7005 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7006
7007 &lt;p&gt;After this, the machine had internet connectivity, and I could
7008 upgrade it and install the sysvinit packages from experimental and
7009 enable it as the default boot system in Hurd.&lt;/p&gt;
7010
7011 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
7012 running on the machine it for ssh login to work a password need to be
7013 set. Also, note that a bug somewhere in openssh on Hurd block
7014 compression from working. Remember to turn that off on the client
7015 side.&lt;/p&gt;
7016
7017 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
7018 stuff:&lt;/p&gt;
7019
7020 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7021 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
7022 deb http://http.debian.net/debian/ experimental main
7023 EOF
7024 apt-get update
7025 apt-get dist-upgrade
7026 apt-get install -t experimental initscripts sysv-rc sysvinit \
7027 sysvinit-core sysvinit-utils
7028 update-alternatives --config runsystem
7029 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7030
7031 &lt;p&gt;To reboot after switching boot system, you have to use
7032 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
7033 yet a sysvinit process able to receive the signals from the normal
7034 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
7035 upgrading every package and rebooting, the network come up with DHCP
7036 after boot as it should, and the settrans/pkill hack mentioned at the
7037 start is no longer needed. But for some strange reason, there are no
7038 longer any login prompt in the virtual console, so I logged in using
7039 ssh instead.
7040
7041 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
7042 fail some times. No idea what the cause is, but hope the Hurd porters
7043 figure it out. At least Justus said on IRC (#debian-hurd on
7044 irc.debian.org) that they are aware of the problem. A way to reduce
7045 the impact is to upgrade to the Hurd packages built by Justus by
7046 adding this repository to the machine:&lt;/p&gt;
7047
7048 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7049 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
7050 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7051 EOF
7052 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7053
7054 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
7055 http://ftp.debian-ports.org/debian, because some of the packages in
7056 unstable do not yet include the required patches that are lingering in
7057 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
7058
7059 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7060 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
7061 i emacs - GNU Emacs editor (metapackage)
7062 i gdb - GNU Debugger
7063 i hurd-recommended - Miscellaneous translators
7064 i isc-dhcp-client - ISC DHCP client
7065 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7066 i libc-bin - Embedded GNU C Library: Binaries
7067 i libc-dev-bin - Embedded GNU C Library: Development binaries
7068 i libc0.3 - Embedded GNU C Library: Shared libraries
7069 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7070 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7071 i multiarch-support - Transitional package to ensure multiarch compatibilit
7072 i A x11-common - X Window System (X.Org) infrastructure
7073 i xorg - X.Org X Window System
7074 i A xserver-xorg - X.Org X server
7075 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7076 #
7077 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7078
7079 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
7080 X.org did not work out of the box and I never took the time to follow
7081 the porters instructions to fix it. This time I was interested in the
7082 command line stuff.&lt;p&gt;
7083 </description>
7084 </item>
7085
7086 <item>
7087 <title>New chrpath release 0.16</title>
7088 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
7089 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
7090 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
7091 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
7092 find problems in C, C++ and Java code using static source code
7093 analysis. It can detect a lot of different problems, and is very
7094 useful to find memory and locking bugs in the error handling part of
7095 the source. The company behind it provide
7096 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
7097 a community service&lt;/a&gt;, and many hundred free software projects are
7098 already checked. A few days ago I decided to have a closer look at
7099 the Coverity system, and discovered that the
7100 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
7101 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
7102 projects I am involved with was already registered. But these are
7103 fairly big, and I would also like to have a small and easy project to
7104 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
7105 checking of the chrpath project&lt;/a&gt;. It was
7106 added to the checker and discovered seven potential defects. Six of
7107 these were real, mostly resource &quot;leak&quot; when the program detected an
7108 error. Nothing serious, as the resources would be released a fraction
7109 of a second later when the program exited because of the error, but it
7110 is nice to do it right in case the source of the program some time in
7111 the future end up in a library. Having fixed all defects and added
7112 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
7113 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
7114 publish a new release. These are the release notes:&lt;/p&gt;
7115
7116 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
7117
7118 &lt;ul&gt;
7119
7120 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
7121 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
7122 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
7123
7124 &lt;/ul&gt;
7125
7126 &lt;p&gt;You can
7127 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7128 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
7129 project if something is wrong with the new release. The test suite
7130 did not discover any old errors, so if you find a new one, please also
7131 include a test suite check.&lt;/p&gt;
7132 </description>
7133 </item>
7134
7135 <item>
7136 <title>New chrpath release 0.15</title>
7137 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
7138 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
7139 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
7140 <description>&lt;p&gt;After many years break from the package and a vain hope that
7141 development would be continued by someone else, I finally pulled my
7142 acts together this morning and wrapped up a new release of chrpath,
7143 the command line tool to modify the rpath and runpath of already
7144 compiled ELF programs. The update was triggered by the persistence of
7145 Isha Vishnoi at IBM, which needed a new config.guess file to get
7146 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
7147 is working on. I checked the
7148 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
7149 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
7150 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
7151 packages for interesting patches (failed to find the source from
7152 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7153 These are the release notes:&lt;/p&gt;
7154
7155 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
7156
7157 &lt;ul&gt;
7158
7159 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
7160 with newer architectures. Thanks to isha vishnoi for the heads
7161 up.&lt;/li&gt;
7162
7163 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
7164
7165 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7166 Matthias Klose.&lt;/li&gt;
7167
7168 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
7169 Petr Machata found in Fedora.&lt;/li&gt;
7170
7171 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
7172 .dynamic is a NULL terminated string. Based on patch found in
7173 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
7174
7175 &lt;/ul&gt;
7176
7177 &lt;p&gt;You can
7178 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7179 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
7180 project if something is wrong with the new release. The test suite
7181 did not discover any old errors, so if you find a new one, please also
7182 include a testsuite check.&lt;/p&gt;
7183 </description>
7184 </item>
7185
7186 <item>
7187 <title>Debian init.d boot script example for rsyslog</title>
7188 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
7189 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
7190 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
7191 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
7192 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
7193 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
7194 init.d scripts at all. Here is an example init.d script, ie a rewrite
7195 of /etc/init.d/rsyslog:&lt;/p&gt;
7196
7197 &lt;p&gt;&lt;pre&gt;
7198 #!/lib/init/init-d-script
7199 ### BEGIN INIT INFO
7200 # Provides: rsyslog
7201 # Required-Start: $remote_fs $time
7202 # Required-Stop: umountnfs $time
7203 # X-Stop-After: sendsigs
7204 # Default-Start: 2 3 4 5
7205 # Default-Stop: 0 1 6
7206 # Short-Description: enhanced syslogd
7207 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7208 # It is quite compatible to stock sysklogd and can be
7209 # used as a drop-in replacement.
7210 ### END INIT INFO
7211 DESC=&quot;enhanced syslogd&quot;
7212 DAEMON=/usr/sbin/rsyslogd
7213 &lt;/pre&gt;&lt;/p&gt;
7214
7215 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
7216 script was 137 lines, and the above is just 15 lines, most of it meta
7217 info/comments.&lt;/p&gt;
7218
7219 &lt;p&gt;How to do this, you ask? Well, one create a new script
7220 /lib/init/init-d-script looking something like this:
7221
7222 &lt;p&gt;&lt;pre&gt;
7223 #!/bin/sh
7224
7225 # Define LSB log_* functions.
7226 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
7227 # and status_of_proc is working.
7228 . /lib/lsb/init-functions
7229
7230 #
7231 # Function that starts the daemon/service
7232
7233 #
7234 do_start()
7235 {
7236 # Return
7237 # 0 if daemon has been started
7238 # 1 if daemon was already running
7239 # 2 if daemon could not be started
7240 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
7241 || return 1
7242 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7243 $DAEMON_ARGS \
7244 || return 2
7245 # Add code here, if necessary, that waits for the process to be ready
7246 # to handle requests from services started subsequently which depend
7247 # on this one. As a last resort, sleep for some time.
7248 }
7249
7250 #
7251 # Function that stops the daemon/service
7252 #
7253 do_stop()
7254 {
7255 # Return
7256 # 0 if daemon has been stopped
7257 # 1 if daemon was already stopped
7258 # 2 if daemon could not be stopped
7259 # other if a failure occurred
7260 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
7261 RETVAL=&quot;$?&quot;
7262 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
7263 # Wait for children to finish too if this is a daemon that forks
7264 # and if the daemon is only ever run from this initscript.
7265 # If the above conditions are not satisfied then add some other code
7266 # that waits for the process to drop all resources that could be
7267 # needed by services started subsequently. A last resort is to
7268 # sleep for some time.
7269 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
7270 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
7271 # Many daemons don&#39;t delete their pidfiles when they exit.
7272 rm -f $PIDFILE
7273 return &quot;$RETVAL&quot;
7274 }
7275
7276 #
7277 # Function that sends a SIGHUP to the daemon/service
7278 #
7279 do_reload() {
7280 #
7281 # If the daemon can reload its configuration without
7282 # restarting (for example, when it is sent a SIGHUP),
7283 # then implement that here.
7284 #
7285 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
7286 return 0
7287 }
7288
7289 SCRIPTNAME=$1
7290 scriptbasename=&quot;$(basename $1)&quot;
7291 echo &quot;SN: $scriptbasename&quot;
7292 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
7293 script=&quot;$1&quot;
7294 shift
7295 . $script
7296 else
7297 exit 0
7298 fi
7299
7300 NAME=$(basename $DAEMON)
7301 PIDFILE=/var/run/$NAME.pid
7302
7303 # Exit if the package is not installed
7304 #[ -x &quot;$DAEMON&quot; ] || exit 0
7305
7306 # Read configuration variable file if it is present
7307 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
7308
7309 # Load the VERBOSE setting and other rcS variables
7310 . /lib/init/vars.sh
7311
7312 case &quot;$1&quot; in
7313 start)
7314 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
7315 do_start
7316 case &quot;$?&quot; in
7317 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7318 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7319 esac
7320 ;;
7321 stop)
7322 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
7323 do_stop
7324 case &quot;$?&quot; in
7325 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7326 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7327 esac
7328 ;;
7329 status)
7330 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
7331 ;;
7332 #reload|force-reload)
7333 #
7334 # If do_reload() is not implemented then leave this commented out
7335 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
7336 #
7337 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
7338 #do_reload
7339 #log_end_msg $?
7340 #;;
7341 restart|force-reload)
7342 #
7343 # If the &quot;reload&quot; option is implemented then remove the
7344 # &#39;force-reload&#39; alias
7345 #
7346 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
7347 do_stop
7348 case &quot;$?&quot; in
7349 0|1)
7350 do_start
7351 case &quot;$?&quot; in
7352 0) log_end_msg 0 ;;
7353 1) log_end_msg 1 ;; # Old process is still running
7354 *) log_end_msg 1 ;; # Failed to start
7355 esac
7356 ;;
7357 *)
7358 # Failed to stop
7359 log_end_msg 1
7360 ;;
7361 esac
7362 ;;
7363 *)
7364 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
7365 exit 3
7366 ;;
7367 esac
7368
7369 :
7370 &lt;/pre&gt;&lt;/p&gt;
7371
7372 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
7373 lot. I did not really polish the approach, so it might not always
7374 work out of the box, but you get the idea. I did not try very hard to
7375 optimize it nor make it more robust either.&lt;/p&gt;
7376
7377 &lt;p&gt;A better argument for switching init system in Debian than reducing
7378 the size of init scripts (which is a good thing to do anyway), is to
7379 get boot system that is able to handle the kernel events sensibly and
7380 robustly, and do not depend on the boot to run sequentially. The boot
7381 and the kernel have not behaved sequentially in years.&lt;/p&gt;
7382 </description>
7383 </item>
7384
7385 <item>
7386 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
7387 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
7388 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
7389 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
7390 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
7391 remote display access is the preferred solution with oVirt and RedHat
7392 Enterprise Virtualization, and I was sad to discover the other day
7393 that the browser plugin needed to use these systems seamlessly was
7394 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
7395 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
7396 2013-04-01, so I decided to wrap up a package based on the great work
7397 from Cajus Pollmeier and put it in a collab-maint maintained git
7398 repository to get a package I could use. I would very much like
7399 others to help me maintain the package (or just take over, I do not
7400 mind), but as no-one had volunteered so far, I just uploaded it to
7401 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
7402
7403 &lt;p&gt;The source is now available from
7404 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&quot;&gt;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&lt;/a&gt;.&lt;/p&gt;
7405 </description>
7406 </item>
7407
7408 <item>
7409 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
7410 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
7411 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
7412 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
7413 <description>&lt;p&gt;The
7414 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
7415 program is a a very nice system to create virtual machine images. It
7416 create a image file, add a partition table, mount it and run
7417 debootstrap in the mounted directory to create a Debian system on a
7418 stick. Yesterday, I decided to try to teach it how to make images for
7419 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
7420 of a plan to simplify the build system for
7421 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
7422 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
7423 the virtualbox images, but its current build system made multistrap
7424 based system for Dreamplug images, and it is lacking support for
7425 Raspberry Pi.&lt;/p&gt;
7426
7427 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
7428 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7429 code and adjusted it to be able to build armel images on my amd64
7430 Debian laptop. I ended up giving vmdebootstrap five new options,
7431 allowing me to replicate the image creation process I use to make
7432 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
7433 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
7434 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
7435 call debootstrap with --foreign and to copy the handler into the
7436 generated chroot before running the second stage. This allow
7437 vmdebootstrap to create armel images on an amd64 host. Next I added
7438 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
7439 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
7440 given file system type, allowing me to create an image with a vfat
7441 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
7442 variant&lt;/tt&gt; option to allow me to create smaller images without the
7443 Debian base system packages installed. Finally, I added an option
7444 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
7445 as a boot loader. It is not needed on the Raspberry Pi and probably
7446 most other non-x86 architectures. The changes were accepted by the
7447 upstream author of vmdebootstrap yesterday and today, and is now
7448 available from
7449 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
7450 upstream project page&lt;/a&gt;.&lt;/p&gt;
7451
7452 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
7453 create a small script (the customize script) to add the non-free
7454 binary blob needed to boot the Raspberry Pi and the APT source
7455 list:&lt;/p&gt;
7456
7457 &lt;p&gt;&lt;pre&gt;
7458 #!/bin/sh
7459 set -e # Exit on first error
7460 rootdir=&quot;$1&quot;
7461 cd &quot;$rootdir&quot;
7462 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
7463 deb http://http.debian.net/debian/ jessie main contrib non-free
7464 EOF
7465 # Install non-free binary blob needed to boot Raspberry Pi. This
7466 # install a kernel somewhere too.
7467 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7468 -O $rootdir/usr/bin/rpi-update
7469 chmod a+x $rootdir/usr/bin/rpi-update
7470 mkdir -p $rootdir/lib/modules
7471 touch $rootdir/boot/start.elf
7472 chroot $rootdir rpi-update
7473 &lt;/pre&gt;&lt;/p&gt;
7474
7475 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
7476 to build the image:&lt;/p&gt;
7477
7478 &lt;pre&gt;
7479 sudo ./vmdebootstrap \
7480 --variant minbase \
7481 --arch armel \
7482 --distribution jessie \
7483 --mirror http://http.debian.net/debian \
7484 --image test.img \
7485 --size 600M \
7486 --bootsize 64M \
7487 --boottype vfat \
7488 --log-level debug \
7489 --verbose \
7490 --no-kernel \
7491 --no-extlinux \
7492 --root-password raspberry \
7493 --hostname raspberrypi \
7494 --foreign /usr/bin/qemu-arm-static \
7495 --customize `pwd`/customize \
7496 --package netbase \
7497 --package git-core \
7498 --package binutils \
7499 --package ca-certificates \
7500 --package wget \
7501 --package kmod
7502 &lt;/pre&gt;&lt;/p&gt;
7503
7504 &lt;p&gt;The list of packages being installed are the ones needed by
7505 rpi-update to make the image bootable on the Raspberry Pi, with the
7506 exception of netbase, which is needed by debootstrap to find
7507 /etc/hosts with the minbase variant. I really wish there was a way to
7508 set up an Raspberry Pi using only packages in the Debian archive, but
7509 that is not possible as far as I know, because it boots from the GPU
7510 using a non-free binary blob.&lt;/p&gt;
7511
7512 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
7513 probably a few others installed. I have not checked the complete
7514 build dependency list.&lt;/p&gt;
7515
7516 &lt;p&gt;The resulting image will not use the hardware floating point unit
7517 on the Raspberry PI, because the armel architecture in Debian is not
7518 optimized for that use. So the images created will be a bit slower
7519 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
7520 </description>
7521 </item>
7522
7523 <item>
7524 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
7525 <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>
7526 <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>
7527 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
7528 <description>&lt;p&gt;The last few days I came across a few good causes that should get
7529 wider attention. I recommend signing and donating to each one of
7530 these. :)&lt;/p&gt;
7531
7532 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
7533 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
7534 Women program which is a Google Summer of Code like initiative to get
7535 more women involved in free software. One debian sponsor has offered
7536 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
7537 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
7538 hope you will to. :)&lt;/p&gt;
7539
7540 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
7541 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
7542 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
7543 take place these days, and their need to fund the work. I&#39;ve already
7544 donated. Are you next?&lt;/p&gt;
7545
7546 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
7547 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7548 statement under the heading
7549 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
7550 Access&lt;/a&gt; for those of us asking for more focus on open access in the
7551 Norwegian government. So far 499 signatures. I hope you will sign it
7552 too.&lt;/p&gt;
7553 </description>
7554 </item>
7555
7556 <item>
7557 <title>Videos about the Freedombox project - for inspiration and learning</title>
7558 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
7559 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
7560 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
7561 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
7562 project&lt;/a&gt; have been going on for a while, and have presented the
7563 vision, ideas and solution several places. Here is a little
7564 collection of videos of talks and presentation of the project.&lt;/p&gt;
7565
7566 &lt;ul&gt;
7567
7568 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
7569 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
7570
7571 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
7572 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7573
7574 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
7575 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7576 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
7577 (Youtube)&lt;/li&gt;
7578
7579 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
7580 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
7581
7582 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
7583 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7584
7585 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
7586 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7587 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
7588
7589 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7590 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7591 (Youtube)&lt;/li&gt;
7592
7593 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7594 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7595
7596 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7597 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7598
7599 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7600 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7601 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7602
7603 &lt;/ul&gt;
7604
7605 &lt;p&gt;A larger list is available from
7606 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7607 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7608
7609 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7610 Jessie is coming along quite well, and soon both Owncloud and using
7611 Tor should be available for testers of the Freedombox solution. :) In
7612 a few weeks I hope everything needed to test it is included in Debian.
7613 The withsqlite package is already in Debian, and the plinth package is
7614 pending in NEW. The third and vital part of that puzzle is the
7615 metapackage/setup framework, which is still pending an upload. Join
7616 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7617 (#freedombox on irc.debian.org)&lt;/a&gt; and
7618 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7619 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7620 </description>
7621 </item>
7622
7623 <item>
7624 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7625 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7626 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7627 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7628 <description>&lt;p&gt;I was introduced to the
7629 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7630 in 2010, when Eben Moglen presented his vision about serving the need
7631 of non-technical people to keep their personal information private and
7632 within the legal protection of their own homes. The idea is to give
7633 people back the power over their network and machines, and return
7634 Internet back to its intended peer-to-peer architecture. Instead of
7635 depending on a central service, the Freedombox will give everyone
7636 control over their own basic infrastructure.&lt;/p&gt;
7637
7638 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7639 taken priority. But this summers nasty news about the misuse of trust
7640 and privilege exercised by the &quot;western&quot; intelligence gathering
7641 communities increased my eagerness to contribute to a point where I
7642 actually started working on the project a while back.&lt;/p&gt;
7643
7644 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7645 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7646 create a simple and cheap Debian based appliance that anyone can hook
7647 up in their home and get access to secure and private services and
7648 communication. The initial deployment platform have been the
7649 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7650 which is a piece of hardware I do not own. So to be able to test what
7651 the current Freedombox setup look like, I had to come up with a way to install
7652 it on some hardware I do have access to. I have rewritten the
7653 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7654 image build framework to use .deb packages instead of only copying
7655 setup into the boot images, and thanks to this rewrite I am able to
7656 set up any machine supported by Debian Wheezy as a Freedombox, using
7657 the previously mentioned deb (and a few support debs for packages
7658 missing in Debian).&lt;/p&gt;
7659
7660 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7661 scripts
7662 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7663 and a administrative web interface
7664 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7665 withsqlite), as well as a privacy enhancing proxy based on
7666 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7667 (freedombox-privoxy). There is also a web/javascript based XMPP
7668 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7669 trying (unsuccessfully so far) to talk to the XMPP server
7670 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7671 web interface is pluggable, and the goal is to use it to enable OpenID
7672 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7673 this is really working yet, see
7674 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7675 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7676 on github at the moment. The HTTP proxy is operational out of the
7677 box, and the admin web interface can be used to add/remove plinth
7678 users. I&#39;ve not been able to do anything else with it so far, but
7679 know there are several branches spread around github and other places
7680 with lots of half baked features.&lt;/p&gt;
7681
7682 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7683 following recipes should work to give you a test machine to poke
7684 at.&lt;/p&gt;
7685
7686 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7687
7688 &lt;ol&gt;
7689
7690 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7691 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7692 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7693 to the Debian installer:&lt;p&gt;
7694 &lt;pre&gt;url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&lt;/a&gt;&lt;/pre&gt;&lt;/li&gt;
7695
7696 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7697 install on.&lt;/li&gt;
7698
7699 &lt;li&gt;When the installation is finished and the machine have rebooted a
7700 few times, your Freedombox is ready for testing.&lt;/li&gt;
7701
7702 &lt;/ol&gt;
7703
7704 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7705
7706 &lt;ol&gt;
7707
7708 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7709 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
7710 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
7711 &lt;pre&gt;
7712 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
7713 &lt;/pre&gt;&lt;/li&gt;
7714 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
7715 &lt;pre&gt;
7716 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7717 apt-key add -
7718 apt-get update
7719 apt-get install freedombox-setup
7720 /usr/lib/freedombox/setup
7721 &lt;/pre&gt;&lt;/li&gt;
7722 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
7723
7724 &lt;/ol&gt;
7725
7726 &lt;p&gt;You can test it on other architectures too, but because the
7727 freedombox-privoxy package is binary, it will only work as intended on
7728 the architectures where I have had time to build the binary and put it
7729 in my APT repository. But do not let this stop you. It is only a
7730 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
7731
7732 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
7733 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
7734 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
7735 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
7736
7737 &lt;p&gt;Please let me know if this works for you, or if you have any
7738 problems. We gather on the IRC channel
7739 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
7740 irc.debian.org and the
7741 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
7742 mailing list&lt;/a&gt;.&lt;/p&gt;
7743
7744 &lt;p&gt;Once you get your freedombox operational, you can visit
7745 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
7746 welcome screen (dead end - do not be surprised if you are unable to
7747 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
7748 to look at the rest of plinth. The default user is &#39;admin&#39; and the
7749 default password is &#39;secret&#39;.&lt;/p&gt;
7750 </description>
7751 </item>
7752
7753 <item>
7754 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
7755 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
7756 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
7757 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
7758 <description>&lt;p&gt;Earlier, I reported about
7759 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html&quot;&gt;my
7760 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
7761 told by IBM that the original disk should be thrown away. And as
7762 there no longer was a problem if I bricked the firmware, I decided
7763 today to try to install Intel firmware to replace the Lenovo firmware
7764 currently on the disk.&lt;/p&gt;
7765
7766 &lt;p&gt;I searched the Intel site for firmware, and found
7767 &lt;a href=&quot;https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&amp;ProdId=3472&amp;DwnldID=18363&amp;ProductFamily=Solid-State+Drives+and+Caching&amp;ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&amp;ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&amp;lang=eng&quot;&gt;issdfut_2.0.4.iso&lt;/a&gt;
7768 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7769 according to the site should contain the latest firmware for SSD
7770 disks. I inserted the broken disk in one of my spare laptops and
7771 booted the ISO from a USB stick. The disk was recognized, but the
7772 program claimed the newest firmware already were installed and refused
7773 to insert any Intel firmware. So no change, and the disk is still
7774 unable to handle write load. :( I guess the only way to get them
7775 working would be if Lenovo releases new firmware. No idea how likely
7776 that is. Anyway, just blogging about this test for completeness. I
7777 got a working Samsung disk, and see no point in spending more time on
7778 the broken disks.&lt;/p&gt;
7779 </description>
7780 </item>
7781
7782 <item>
7783 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
7784 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
7785 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
7786 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
7787 <description>&lt;p&gt;Today I switched to
7788 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
7789 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
7790 my new Thinkpad X230, which was delivered with an
7791 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html&quot;&gt;180
7792 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
7793 sustained writes. My hardware supplier have been very forthcoming in
7794 trying to find a solution, and after first trying with another
7795 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
7796 disk instead to fix it once and for all. The Samsung disk survived
7797 the installation of Debian with encrypted disks (filling the disk with
7798 random data during installation killed the first two), and I thus
7799 decided to trust it with my data. I have installed it as a Debian Edu
7800 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7801 server at home using Kerberos and LDAP, and will use it as my work
7802 station from now on.&lt;/p&gt;
7803
7804 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
7805 Debian Wheezy default installation need to be tuned a bit to increase
7806 performance and increase life time of the disk. The Linux kernel and
7807 user space applications do not yet adjust automatically to such
7808 environment. To make it easier for my self, I created a draft Debian
7809 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
7810 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
7811 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
7812 is set up to adjust the setup of the machine by just installing the
7813 package. If there is any non-SSD disk in the machine, the package
7814 will refuse to install, as I did not try to write any logic to sort
7815 file systems in SSD and non-SSD file systems.&lt;/p&gt;
7816
7817 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
7818 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7819 where I set up the machine with one large encrypted partition (in
7820 addition to /boot), put LVM on top of this and set up partitions on
7821 top of this again. See the README file in the package source for the
7822 references I used to pick the settings. At the moment these
7823 parameters are tuned:&lt;/p&gt;
7824
7825 &lt;ul&gt;
7826
7827 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
7828 (adding discard to /etc/crypttab)&lt;/li&gt;
7829
7830 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
7831 this case a cryptsetup partition) by changing issue_discards from
7832 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
7833
7834 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
7835 systems.&lt;/li&gt;
7836
7837 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
7838 /etc/fstab.&lt;/li&gt;
7839
7840 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
7841
7842 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
7843 cron.daily).&lt;/li&gt;
7844
7845 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
7846 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
7847
7848 &lt;/ul&gt;
7849
7850 &lt;p&gt;During installation, I cancelled the part where the installer fill
7851 the disk with random data, as this would kill the SSD performance for
7852 little gain. My goal with the encrypted file system is to ensure
7853 those stealing my laptop end up with a brick and not a working
7854 computer. I have no hope in keeping the really resourceful people
7855 from getting the data on the disk (see
7856 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
7857 Thus I concluded that adding the discard option to crypttab is the
7858 right thing to do.&lt;/p&gt;
7859
7860 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
7861 it for SSD, but others recommended deadline and a benchmark I found
7862 indicated that deadline might be better for interactive use.&lt;/p&gt;
7863
7864 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
7865 and ext4, but read that it would give a performance hit ever time a
7866 file is removed, and thought it best to that that slowdown once a day
7867 instead of during my work.&lt;/p&gt;
7868
7869 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7870 this is already done by Debian Edu.&lt;/p&gt;
7871
7872 &lt;p&gt;I have not yet started on the user space tuning. I expect
7873 iceweasel need some tuning, and perhaps other applications too, but
7874 have not yet had time to investigate those parts.&lt;/p&gt;
7875
7876 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
7877 there.&lt;/p&gt;
7878
7879 &lt;p&gt;As for the answer to the question in the title of this blog post,
7880 as far as I know, the only solution I know about is to replace the
7881 disk. It might be possible to flash it with Intel firmware instead of
7882 the Lenovo firmware. But I have not tried and did not want to do so
7883 without approval from Lenovo as I wanted to keep the warranty on the
7884 disk until a solution was found and they wanted the broken disks
7885 back.&lt;/p&gt;
7886 </description>
7887 </item>
7888
7889 <item>
7890 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
7891 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
7892 <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>
7893 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
7894 <description>&lt;p&gt;A few days ago, I wrote about
7895 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
7896 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
7897 was dying during installation because it is unable to cope with
7898 sustained write. My supplier is in contact with
7899 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
7900 replacement disk to try to fix the problem. They decided to send an
7901 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
7902
7903 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
7904 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7905 same firmware version as the original. This time my hope raised
7906 slightly as the installation progressed, as the original disk used to
7907 die after 4-7% of the disk was written to, while this time it kept
7908 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
7909 died again and I was back on square one. I still do not have a new
7910 laptop with a disk I can trust. I can not live with a disk that might
7911 lock up when I download a new
7912 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
7913 other large files. I look forward to hearing from my supplier with
7914 the next proposal from Lenovo.&lt;/p&gt;
7915
7916 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
7917 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7918 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7919 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
7920 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7921 P/N 45N8295, P0C38732.&lt;/p&gt;
7922
7923 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
7924 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
7925 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7926 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
7927 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7928 P/N 45N8295, P0C38732.&lt;/p&gt;
7929
7930 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
7931 SA, date and WNPP values. Mentioning all the details here in case
7932 someone is able to use the information to find a way to identify the
7933 failing disk among working ones (if any such working disk actually
7934 exist).&lt;/p&gt;
7935 </description>
7936 </item>
7937
7938 <item>
7939 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
7940 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
7941 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
7942 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
7943 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
7944 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7945 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
7946 member assosiation NUUG&lt;/a&gt; and
7947 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
7948 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
7949 Bitraf&lt;/a&gt;.&lt;/p&gt;
7950
7951 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
7952 welcome, and there is no fee to participate. There is on the other
7953 hand limited space, and only room for 30 people. Please put your name
7954 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
7955 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
7956 </description>
7957 </item>
7958
7959 <item>
7960 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
7961 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
7962 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
7963 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
7964 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
7965 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
7966 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
7967 time to spend on it, and it took a while to find a model I believe
7968 will do the job, but two days ago the replacement finally arrived. I
7969 ended up picking a
7970 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
7971 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7972 a roaming workstation, and it seemed to work flawlessly. But my
7973 second installation with encrypted disk was not as successful. More
7974 on that below.&lt;/p&gt;
7975
7976 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
7977 important requirements (robust and with a good keyboard) are never
7978 listed in the feature list. But I did get good help from the search
7979 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
7980 allowed me to limit the list of interesting laptops based on my other
7981 requirements. A bit surprising that SSD disk are not disks according
7982 to that search interface, so I had to drop specifying the number of
7983 disks from my search parameters. I also asked around among friends to
7984 get their impression on keyboards and robustness.&lt;/p&gt;
7985
7986 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
7987 X41. I am not quite convinced about the keyboard, as it is
7988 significantly wider than my old keyboard, and I have to stretch my
7989 hand a lot more to reach the edges. But the key response is fairly
7990 good and the individual key shape is fairly easy to handle, so I hope
7991 I will get used to it. My old X40 was starting to fail, and I really
7992 needed a new laptop now. :)&lt;/p&gt;
7993
7994 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
7995 visit to the BIOS during boot it disable it.&lt;/p&gt;
7996
7997 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
7998 lock up during load. And this happen when installing Debian Wheezy
7999 with encrypted disk, while the disk is being filled with random data.
8000 I also tested to install Ubuntu Raring, and it happen there too if I
8001 reenable the code to fill the disk with random data (it is disabled by
8002 default in Ubuntu). And the bug with is already known. It was
8003 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
8004 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
8005 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
8006 kernel developers as
8007 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
8008 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
8009 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
8010 Lenovo forums, both for
8011 &lt;a href=&quot;http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-520-180GB-issue/m-p/1070549&quot;&gt;T430
8012 2012-11-10&lt;/a&gt; and for
8013 &lt;a href=&quot;http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-180GB-Intel-520-SSD-under-heavy-write-load/m-p/1068147&quot;&gt;X230
8014 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
8015 reports state that the disk lock up during use if many writes are done
8016 on the disk, so it is much no use to work around the installation
8017 problem and end up with a computer that can lock up at any moment.
8018 There is even a
8019 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
8020 available&lt;/a&gt; that will lock up the hard drive after running a few
8021 minutes by writing to a file.&lt;/p&gt;
8022
8023 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
8024 contacting PCHELP Norway (request 01D1FDP) which handle support
8025 requests for Lenovo, his first suggestion was to upgrade the disk
8026 firmware. Unfortunately there is no newer firmware available from
8027 Lenovo, as my disk already have the most recent one (version LF1i). I
8028 hope to hear more from him today and hope the problem can be
8029 fixed. :)&lt;/p&gt;
8030 </description>
8031 </item>
8032
8033 <item>
8034 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
8035 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
8036 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
8037 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
8038 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
8039 trusty old Thinkpad X41. Unfortunately I did not have much time to
8040 spend on it, but today the replacement finally arrived. I ended up
8041 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
8042 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
8043 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8044 this, it is installing what I hope will be a more final installation,
8045 with a encrypted hard drive to ensure any dope head stealing it end up
8046 with an expencive door stop.&lt;/p&gt;
8047
8048 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8049 important requirements (robust and with a good keyboard) are never
8050 listed in the feature list. But I did get good help from the search
8051 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8052 allowed me to limit the list of interesting laptops based on my other
8053 requirements. A bit surprising that SSD disk are not disks, so I had
8054 to drop number of disks from my search parameters.&lt;/p&gt;
8055
8056 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
8057 wider than my old keyboard, and I have to stretch my hand a lot more
8058 to reach the edges. But the key response is fairly good and the
8059 individual key shape is fairly easy to handle, so I hope I will get
8060 used to it. My old X40 was starting to fail, and I really needed a
8061 new laptop now. :)&lt;/p&gt;
8062
8063 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
8064 </description>
8065 </item>
8066
8067 <item>
8068 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
8069 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
8070 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
8071 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
8072 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
8073 perfectly capable of, and I have to do it manually to get things
8074 working. One such task is to find out what firmware packages are
8075 needed to get the hardware on my computer working. Most often this
8076 affect the wifi card, but some times it even affect the RAID
8077 controller or the ethernet card. Today I pushed version 0.4 of the
8078 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
8079 including a new script isenkram-autoinstall-firmware handling the
8080 process of asking all the loaded kernel modules what firmware files
8081 they want, find debian packages providing these files and install the
8082 debian packages. Here is a test run on my laptop:&lt;/p&gt;
8083
8084 &lt;p&gt;&lt;pre&gt;
8085 # isenkram-autoinstall-firmware
8086 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8087 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8088 info: locating packages with the requested firmware files
8089 info: Updating APT sources after adding non-free APT source
8090 info: trying to install firmware-ipw2x00
8091 firmware-ipw2x00
8092 firmware-ipw2x00
8093 Preconfiguring packages ...
8094 Selecting previously deselected package firmware-ipw2x00.
8095 (Reading database ... 259727 files and directories currently installed.)
8096 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8097 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
8098 #
8099 &lt;/pre&gt;&lt;/p&gt;
8100
8101 &lt;p&gt;When all the requested firmware is present, a simple message is
8102 printed instead:&lt;/p&gt;
8103
8104 &lt;p&gt;&lt;pre&gt;
8105 # isenkram-autoinstall-firmware
8106 info: did not find any firmware files requested by loaded kernel modules. exiting
8107 #
8108 &lt;/pre&gt;&lt;/p&gt;
8109
8110 &lt;p&gt;It could use some polish, but it is already working well and saving
8111 me some time when setting up new machines. :)&lt;/p&gt;
8112
8113 &lt;p&gt;So, how does it work? It look at the set of currently loaded
8114 kernel modules, and look up each one of them using modinfo, to find
8115 the firmware files listed in the module meta-information. Next, it
8116 download the Contents file from a nearby APT mirror, and search for
8117 the firmware files in this file to locate the package with the
8118 requested firmware file. If the package is in the non-free section, a
8119 non-free APT source is added and the package is installed using
8120 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
8121 machine.&lt;/p&gt;
8122
8123 &lt;p&gt;I hope someone find time to implement a more polished version of
8124 this script as part of the hw-detect debian-installer module, to
8125 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
8126 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
8127 firmware during a PXE install when the packages already are available
8128 from the nearby Debian mirror.&lt;/p&gt;
8129 </description>
8130 </item>
8131
8132 <item>
8133 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
8134 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
8135 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
8136 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
8137 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8138 the screen just turn black when Linux boot, either during installation
8139 or on first boot from the hard disk. I&#39;ve seen it once in a while the
8140 last few years, but only recently understood the cause. I&#39;ve seen it
8141 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8142 The reason seem to be in the wiring of some laptops. The system to
8143 control the screen background light is inverted, so when Linux try to
8144 turn the brightness fully on, it end up turning it off instead. I do
8145 not know which Linux drivers are affected, but this post is about the
8146 i915 driver used by the
8147 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8148 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
8149
8150 &lt;p&gt;The problem can be worked around two ways. Either by adding
8151 i915.invert_brightness=1 as a kernel option, or by adding a file in
8152 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
8153 option when it load the i915 kernel module. On Debian and Ubuntu, it
8154 can be done by running these commands as root:&lt;/p&gt;
8155
8156 &lt;pre&gt;
8157 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
8158 update-initramfs -u -k all
8159 &lt;/pre&gt;
8160
8161 &lt;p&gt;Since March 2012 there is
8162 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
8163 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
8164 hardware have this problem, and get the driver to invert the
8165 brightness setting automatically. To use it, one need to add a row in
8166 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c&quot;&gt;the
8167 intel_quirks array&lt;/a&gt; in the driver source
8168 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
8169 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
8170 number (vendor number 8086 is assumed) and subdevice vendor and device
8171 number.&lt;/p&gt;
8172
8173 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
8174 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
8175
8176 &lt;p&gt;&lt;pre&gt;
8177 00:02.0 VGA compatible controller [0300]: Intel Corporation \
8178 3rd Gen Core processor Graphics Controller [8086:0156] \
8179 (rev 09) (prog-if 00 [VGA controller])
8180 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
8181 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8182 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8183 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
8184 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
8185 Latency: 0
8186 Interrupt: pin A routed to IRQ 42
8187 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
8188 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
8189 Region 4: I/O ports at 4000 [size=64]
8190 Expansion ROM at &lt;unassigned&gt; [disabled]
8191 Capabilities: &lt;access denied&gt;
8192 Kernel driver in use: i915
8193 &lt;/pre&gt;&lt;/p&gt;
8194
8195 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
8196
8197 &lt;p&gt;&lt;pre&gt;
8198 struct intel_quirk intel_quirks[] = {
8199 ...
8200 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8201 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
8202 ...
8203 }
8204 &lt;/pre&gt;&lt;/p&gt;
8205
8206 &lt;p&gt;According to the kernel module instructions (as seen using
8207 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
8208 invert_brightness flag should be sent to the
8209 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
8210 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
8211 developers. But my email about the laptop sent 2013-06-03 have not
8212 yet shown up in
8213 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
8214 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
8215 emails from non-subscribers. Because of this, I sent my patch also to
8216 the Debian bug tracking system instead as
8217 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
8218 sure the patch is not lost.&lt;/p&gt;
8219
8220 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
8221 with this problem working properly with Linux. If you use Gnome, your
8222 worries should be over at this point. But if you use KDE, there is
8223 something in KDE ignoring the invert_brightness setting and turning on
8224 the screen during login. I&#39;ve reported it to Debian as
8225 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
8226 have no idea yet how to figure out exactly what subsystem is doing
8227 this. Perhaps you can help? Perhaps you know what the Gnome
8228 developers did to handle this, and this can give a clue to the KDE
8229 developers? Or you know where in KDE the screen brightness is changed
8230 during login? If so, please update the BTS report (or get in touch if
8231 you do not know how to update BTS).&lt;/p&gt;
8232
8233 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
8234 acpi_backlight=vendor, to disable ACPI backlight support completely,
8235 as the ACPI information on the machine is trash and it is better to
8236 leave it to the intel video driver to control the screen
8237 backlight.&lt;/p&gt;
8238 </description>
8239 </item>
8240
8241 <item>
8242 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
8243 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
8244 <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>
8245 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
8246 <description>&lt;p&gt;Two days ago, I asked
8247 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html&quot;&gt;how
8248 I could install Linux on a Packard Bell EasyNote LV computer
8249 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
8250 with the obstacles put in the way of Linux users on a laptop with UEFI
8251 and Windows 8.&lt;/p&gt;
8252
8253 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
8254 secure booting or fast boot. I suspect fast boot was the problem,
8255 causing the firmware to boot directly from HD without considering any
8256 key presses and alternative devices, but do not know UEFI settings
8257 enough to tell.&lt;/p&gt;
8258
8259 &lt;p&gt;There is no way to install Linux on the machine in question without
8260 opening the box and disconnecting the hard drive! This is as far as I
8261 can tell, the only way to get access to the firmware setup menu
8262 without accepting the Windows 8 license agreement. I am told (and
8263 found description on how to) that it is possible to configure the
8264 firmware setup once booted into Windows 8. But as I believe the terms
8265 of that agreement are completely unacceptable, accepting the license
8266 was never an alternative. I do not enter agreements I do not intend
8267 to follow.&lt;/p&gt;
8268
8269 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
8270 waste many hours on this, but luckily there was a way to get it to
8271 work. But I would not recommend it to anyone planning to run Linux on
8272 it, and I have become sceptical to Windows 8 certified laptops. Is
8273 this the way Linux will be forced out of the market place, by making
8274 it close to impossible for &quot;normal&quot; users to install Linux without
8275 accepting the Microsoft Windows license terms? Or at least not
8276 without risking to loose the warranty?&lt;/p&gt;
8277
8278 &lt;p&gt;I&#39;ve updated the
8279 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
8280 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
8281 do not have to struggle as much as I did to get Linux into the
8282 machine.&lt;/p&gt;
8283
8284 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8285 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
8286 </description>
8287 </item>
8288
8289 <item>
8290 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
8291 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
8292 <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>
8293 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
8294 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
8295 new laptops for my parents and a few others. I bought Packard Bell
8296 Easynote LV to run Kubuntu on and use as their home computer. But I
8297 am completely unable to figure out how to install Linux on it. The
8298 computer is preinstalled with Windows 8, and I suspect it uses UEFI
8299 instead of a BIOS to boot.&lt;/p&gt;
8300
8301 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
8302 to get it to boot the Linux installer from my USB stick. I have yet
8303 to try the DVD install, and still hope it will work. when I turn on
8304 the computer, there is no information on what buttons to press to get
8305 the normal boot menu. I expect to get some boot menu to select PXE or
8306 USB stick booting. When booting, it first ask for the language to
8307 use, then for some regional settings, and finally if I will accept the
8308 Windows 8 terms of use. As these terms are completely unacceptable to
8309 me, I have no other choice but to turn off the computer and try again
8310 to get it to boot the Linux installer.&lt;/p&gt;
8311
8312 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
8313 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8314 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
8315 installed on this machine, please get in touch or update that wiki
8316 page. If I can&#39;t find a way to install Linux, I will have to return
8317 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
8318
8319 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
8320 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
8321 on new Laptops?&lt;/p&gt;
8322 </description>
8323 </item>
8324
8325 <item>
8326 <title>How to transform a Debian based system to a Debian Edu installation</title>
8327 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
8328 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
8329 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
8330 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
8331 an operating system based on Debian intended for use in schools. It
8332 contain a turn-key solution for the computer network provided to
8333 pupils in the primary schools. It provide both the central server,
8334 network boot servers and desktop environments with heaps of
8335 educational software. The project was founded almost 12 years ago,
8336 2001-07-02. If you want to support the project, which is in need for
8337 cash to fund developer gatherings and other project related activity,
8338 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
8339 donate some money&lt;/a&gt;.
8340
8341 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
8342 lists and elsewhere, is the question on how to transform a Debian or
8343 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
8344 hard, and last week I wrote a script to replicate the steps done by
8345 the Debian Edu installer.&lt;/p&gt;
8346
8347 &lt;p&gt;The script,
8348 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup&quot;&gt;debian-edu-bless&lt;a/&gt;
8349 in the debian-edu-config package, will go through these six steps and
8350 transform an existing Debian Wheezy or Ubuntu (untested) installation
8351 into a Debian Edu Workstation:&lt;/p&gt;
8352
8353 &lt;ol&gt;
8354
8355 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
8356 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
8357 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
8358 our configuration.&lt;/li&gt;
8359 &lt;li&gt;Preseed debconf database with profile setup in
8360 /etc/debian-edu/config, and run tasksel to install packages
8361 according to the profile specified in the config above,
8362 overriding some of the Debian automation machinery.&lt;/li&gt;
8363 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
8364 that could not be done using preseeding.&lt;/li&gt;
8365 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
8366
8367 &lt;/ol&gt;
8368
8369 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
8370 replicated like this. Disk partitioning and LVM setup, for example.
8371 So this script just assume there is enough disk space to install all
8372 the needed packages.&lt;/p&gt;
8373
8374 &lt;p&gt;The script was created to help a Debian Edu student working on
8375 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
8376 Debian Edu client, and using it he can take the existing
8377 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
8378 transform it into a fully functioning Debian Edu Workstation (or
8379 Roaming Workstation, or whatever :).&lt;/p&gt;
8380
8381 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
8382 If a LXDE based Roaming workstation is wanted instead, modify the
8383 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
8384
8385 &lt;p&gt;&lt;pre&gt;
8386 PROFILE=&quot;Roaming-Workstation&quot;
8387 DESKTOP=&quot;lxde&quot;
8388 &lt;/pre&gt;&lt;/p&gt;
8389
8390 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
8391 the cloud, by starting with a virtual Debian installation at some
8392 virtual hosting service and setting up all the services on first
8393 boot.&lt;/p&gt;
8394 </description>
8395 </item>
8396
8397 <item>
8398 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
8399 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
8400 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
8401 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
8402 <description>&lt;P&gt;In January,
8403 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
8404 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
8405 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
8406 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
8407 marvellous construction system from Denmark. We also created
8408 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
8409 a place to take notes and write down our plans and hopes. And several
8410 people showed up to help. I was very happy to see the effect of my
8411 call. Since the small start, we have a debtags tag
8412 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
8413 tag for LEGO related packages, and now count 10 packages related to
8414 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
8415
8416 &lt;p&gt;&lt;table&gt;
8417 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/brickos&quot;&gt;brickos&lt;/a&gt;&lt;/td&gt;&lt;td&gt;alternative OS for LEGO Mindstorms RCX. Supports development in C/C++&lt;/td&gt;&lt;/tr&gt;
8418 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/leocad&quot;&gt;leocad&lt;/a&gt;&lt;/td&gt;&lt;td&gt;virtual brick CAD software&lt;/td&gt;&lt;/tr&gt;
8419 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/libnxt&quot;&gt;libnxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;utility library for talking to the LEGO Mindstorms NX&lt;/td&gt;&lt;/tr&gt;
8420 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/lnpd&quot;&gt;lnpd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;daemon for LNP communication with BrickOS&lt;/td&gt;&lt;/tr&gt;
8421 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nbc&quot;&gt;nbc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;compiler for LEGO Mindstorms NXT bricks&lt;/td&gt;&lt;/tr&gt;
8422 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nqc&quot;&gt;nqc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Not Quite C compiler for LEGO Mindstorms RCX&lt;/td&gt;&lt;/tr&gt;
8423 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt&quot;&gt;python-nxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;python driver/interface/wrapper for the Lego Mindstorms NXT robot&lt;/td&gt;&lt;/tr&gt;
8424 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt-filer&quot;&gt;python-nxt-filer&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple GUI to manage files on a LEGO Mindstorms NXT&lt;/td&gt;&lt;/tr&gt;
8425 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/scratch&quot;&gt;scratch&lt;/a&gt;&lt;/td&gt;&lt;td&gt;easy to use programming environment for ages 8 and up&lt;/td&gt;&lt;/tr&gt;
8426 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/t2n&quot;&gt;t2n&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple command-line tool for Lego NXT&lt;/td&gt;&lt;/tr&gt;
8427 &lt;/table&gt;&lt;/p&gt;
8428
8429 &lt;p&gt;Some of these are available in Wheezy, and all but one are
8430 currently available in Jessie/testing. leocad is so far only
8431 available in experimental.&lt;/p&gt;
8432
8433 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
8434 adding the rest of the great free software tools available on Linux
8435 for LEGO designers.&lt;/p&gt;
8436 </description>
8437 </item>
8438
8439 <item>
8440 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
8441 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
8442 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
8443 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
8444 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
8445 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
8446 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
8447 Debian release, and I expect to move my machines at home over to it fairly
8448 soon.&lt;/p&gt;
8449
8450 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
8451 in particular make me very happy to see included. The
8452 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
8453 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
8454 included for the first time. Alongside similar programs like
8455 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
8456 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
8457 it allow for visual programming where syntax errors can not happen,
8458 and a friendly programming environment for learning to control the
8459 computer. Scratch will also be included in the next release of Debian
8460 Edu.&lt;/a&gt;
8461
8462 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
8463 Edu/Skolelinux release too. The
8464 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
8465 alpha release&lt;/a&gt; went out last week, and the next should soon
8466 follow.&lt;p&gt;
8467 </description>
8468 </item>
8469
8470 <item>
8471 <title>Isenkram 0.2 finally in the Debian archive</title>
8472 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
8473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
8474 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
8475 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
8476 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
8477 for many months. I uploaded it to the Debian experimental suite
8478 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
8479
8480 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
8481 install to work with a pluggable hardware device. The suggestion pop
8482 up when the device is plugged in. For example if a Lego Mindstorm NXT
8483 is inserted, it will suggest to install the program needed to program
8484 the NXT controller. Give it a go, and report bugs and suggestions to
8485 BTS. :)&lt;/p&gt;
8486 </description>
8487 </item>
8488
8489 <item>
8490 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
8491 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
8492 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
8493 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
8494 <description>&lt;p&gt;My
8495 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
8496 bitcoin related blog post&lt;/a&gt; mentioned that the new
8497 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
8498 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8499 2013-01-19, and have been available in unstable since then. It was
8500 automatically copied to Ubuntu, and is available in their Raring
8501 version too.&lt;/p&gt;
8502
8503 &lt;p&gt;But there is a strange problem with the build that block this new
8504 version from being available on the i386 and kfreebsd-i386
8505 architectures. For some strange reason, the autobuilders in Debian
8506 for these architectures fail to run the test suite on these
8507 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
8508 We are so far unable to reproduce it when building it manually, and
8509 no-one have been able to propose a fix. If you got an idea what is
8510 failing, please let us know via the BTS.&lt;/p&gt;
8511
8512 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
8513 I often run low on disk space, is the fact that the client will exit
8514 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
8515 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
8516 it. :)&lt;/p&gt;
8517
8518 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8519 activities, please send Bitcoin donations to my address
8520 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8521 </description>
8522 </item>
8523
8524 <item>
8525 <title>Welcome to the world, Isenkram!</title>
8526 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
8527 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
8528 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
8529 <description>&lt;p&gt;Yesterday, I
8530 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
8531 for testers&lt;/a&gt; for my prototype for making Debian better at handling
8532 pluggable hardware devices, which I
8533 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
8534 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
8535 up, and caused me to really want to to open up the development to more
8536 people. But before I did this, I want to come up with a sensible name
8537 for this project. Today I finally decided on a new name, and I have
8538 renamed the project from hw-support-handler to this new name. In the
8539 process, I moved the source to git and made it available as a
8540 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
8541 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
8542 To fetch and build the latest version of the source, use&lt;/p&gt;
8543
8544 &lt;pre&gt;
8545 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8546 cd isenkram &amp;&amp; git-buildpackage -us -uc
8547 &lt;/pre&gt;
8548
8549 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
8550 want to hack on the source or improve the package, please go ahead.
8551 But please talk to me first on IRC or via email before you do major
8552 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
8553
8554 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
8555 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8556 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
8557 the German word eisenkram, for those that are familiar with that
8558 word.&lt;/p&gt;
8559
8560 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
8561 instructions, to avoid confusing people with an error from the signing
8562 process.&lt;/p&gt;
8563
8564 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
8565 clone argument to avoid the need for authentication.&lt;/p&gt;
8566 </description>
8567 </item>
8568
8569 <item>
8570 <title>First prototype ready making hardware easier to use in Debian</title>
8571 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
8572 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
8573 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
8574 <description>&lt;p&gt;Early this month I set out to try to
8575 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
8576 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
8577 prototype is working, and it is ready for a larger audience. To test
8578 it, fetch the
8579 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
8580 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
8581 package. You might have to log out and in again activate the
8582 autostart script.&lt;/p&gt;
8583
8584 &lt;p&gt;The design is simple:&lt;/p&gt;
8585
8586 &lt;ul&gt;
8587
8588 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
8589 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8590
8591 &lt;li&gt;This program listen for kernel events about new hardware (directly
8592 from the kernel like udev does), not using HAL dbus events as I
8593 initially did.&lt;/li&gt;
8594
8595 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8596 the APT database, a database
8597 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8598 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8599
8600 &lt;li&gt;If a package is mapped to the hardware in question, the package
8601 isn&#39;t installed yet and this is the first time the hardware was
8602 plugged in, show a desktop notification suggesting to install the
8603 package or packages.&lt;/li&gt;
8604
8605 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8606 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8607
8608 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8609 package while showing progress information in a window.&lt;/li&gt;
8610
8611 &lt;/ul&gt;
8612
8613 &lt;p&gt;I still need to come up with a better name for the system. Here
8614 are some screen shots showing the prototype in action. First the
8615 notification, then the password request, and finally the request to
8616 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8617
8618 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8619 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8620 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8621 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8622 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
8623
8624 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8625 is already useful. The database of hardware to package mappings also
8626 need more work. It is currently compatible with the Ubuntu way of
8627 storing such information in the package control file, but could be
8628 changed to use other formats instead or in addition to the current
8629 method. I&#39;ve dropped the use of discover for this mapping, as the
8630 modalias approach is more flexible and easier to use on Linux as long
8631 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8632
8633 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8634 here is the command required to check out and build the source: Use
8635 &#39;&lt;tt&gt;svn checkout
8636 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8637 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8638 devscripts package.&lt;/p&gt;
8639
8640 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8641 renamed to Isenkram and the source moved from the Debian Edu
8642 subversion repository to a Debian collab-maint git repository. See
8643 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8644 instructions&lt;/a&gt; for details.&lt;/p&gt;
8645 </description>
8646 </item>
8647
8648 <item>
8649 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8650 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8651 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8652 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8653 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8654 suddenly in bed. With a quiet whimper, it went completely quiet and
8655 black. The power button was no longer able to turn it on. It was a
8656 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8657 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8658 Compaq I had before that. Now I need to find a replacement. To keep
8659 going during Christmas, I moved the one year old SSD disk to my old
8660 X40 where it fitted (only one I had left that could use it), but it is
8661 not a durable solution.
8662
8663 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8664 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8665
8666 &lt;ul&gt;
8667
8668 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8669 than A4).&lt;/li&gt;
8670 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8671 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8672 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8673 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8674 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8675 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8676 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8677 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8678 size).&lt;/li&gt;
8679 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8680 X.org packages.&lt;/li&gt;
8681 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8682 the time).
8683
8684 &lt;/ul&gt;
8685
8686 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8687 list. The reason is simply that the specifications on laptops the
8688 last 10-15 years have been sufficient for my needs, and I have to look
8689 at other features to choose my laptop. But are there still made as
8690 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8691 robust, and Thinkpads seem to be heading in the wrong direction since
8692 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8693 still be useful.&lt;/p&gt;
8694
8695 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8696 external keyboard? I&#39;ll have to check the
8697 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8698 well-supported laptops, or perhaps just buy one preinstalled from one
8699 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8700 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8701 </description>
8702 </item>
8703
8704 <item>
8705 <title>How to find a browser plugin supporting a given MIME type</title>
8706 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8707 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8708 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8709 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
8710 install to get support for a given MIME type. Thanks to
8711 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
8712 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
8713 Unfortunately, not very many packages provide the needed meta
8714 information, Anyway, here is a small script to look up all browser
8715 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
8716
8717 &lt;pre&gt;
8718 #!/usr/bin/python
8719 import sys
8720 import apt
8721 def pkgs_handling_mimetype(mimetype):
8722 cache = apt.Cache()
8723 cache.open(None)
8724 thepkgs = []
8725 for pkg in cache:
8726 version = pkg.candidate
8727 if version is None:
8728 version = pkg.installed
8729 if version is None:
8730 continue
8731 record = version.record
8732 if not record.has_key(&#39;Npp-MimeType&#39;):
8733 continue
8734 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
8735 for t in mime_types:
8736 t = t.rstrip().strip()
8737 if t == mimetype:
8738 thepkgs.append(pkg.name)
8739 return thepkgs
8740 mimetype = &quot;audio/ogg&quot;
8741 if 1 &lt; len(sys.argv):
8742 mimetype = sys.argv[1]
8743 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
8744 for pkg in pkgs_handling_mimetype(mimetype):
8745 print &quot; %s&quot; %pkg
8746 &lt;/pre&gt;
8747
8748 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
8749
8750 &lt;pre&gt;
8751 % ./apt-find-browserplug-for-mimetype
8752 Browser plugin packages supporting audio/ogg:
8753 gecko-mediaplayer
8754 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8755 Browser plugin packages supporting application/x-shockwave-flash:
8756 browser-plugin-gnash
8757 %
8758 &lt;/pre&gt;
8759
8760 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
8761 itself to query for plugins and propose to install the needed
8762 packages. It would be great if Debian supported such feature too. Is
8763 anyone working on adding it?&lt;/p&gt;
8764
8765 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
8766 request for icweasel support for this feature is
8767 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
8768 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
8769 of manpower and wish for a different design is the reason thus feature
8770 is not yet in iceweasel from Debian.&lt;/p&gt;
8771 </description>
8772 </item>
8773
8774 <item>
8775 <title>What is the most supported MIME type in Debian?</title>
8776 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
8777 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
8778 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
8779 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
8780 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
8781 proposal to make it possible for a Desktop application to propose to
8782 the user some package to install to gain support for a given MIME
8783 type, font, library etc. that is currently missing. With such
8784 mechanism in place, it would be possible for the desktop to
8785 automatically propose and install leocad if some LDraw file is
8786 downloaded by the browser.&lt;/p&gt;
8787
8788 &lt;p&gt;To get some idea about the current content of the archive, I decided
8789 to write a simple program to extract all .desktop files from the
8790 Debian archive and look up the claimed MIME support there. The result
8791 can be found on the
8792 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
8793 site&lt;/a&gt;. Using the collected information, it become possible to
8794 answer the question in the title. Here are the 20 most supported MIME
8795 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8796 The complete list is available from the link above.&lt;/p&gt;
8797
8798 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
8799
8800 &lt;pre&gt;
8801 count MIME type
8802 ----- -----------------------
8803 32 text/plain
8804 30 audio/mpeg
8805 29 image/png
8806 28 image/jpeg
8807 27 application/ogg
8808 26 audio/x-mp3
8809 25 image/tiff
8810 25 image/gif
8811 22 image/bmp
8812 22 audio/x-wav
8813 20 audio/x-flac
8814 19 audio/x-mpegurl
8815 18 video/x-ms-asf
8816 18 audio/x-musepack
8817 18 audio/x-mpeg
8818 18 application/x-ogg
8819 17 video/mpeg
8820 17 audio/x-scpls
8821 17 audio/ogg
8822 16 video/x-ms-wmv
8823 &lt;/pre&gt;
8824
8825 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
8826
8827 &lt;pre&gt;
8828 count MIME type
8829 ----- -----------------------
8830 33 text/plain
8831 32 image/png
8832 32 image/jpeg
8833 29 audio/mpeg
8834 27 image/gif
8835 26 image/tiff
8836 26 application/ogg
8837 25 audio/x-mp3
8838 22 image/bmp
8839 21 audio/x-wav
8840 19 audio/x-mpegurl
8841 19 audio/x-mpeg
8842 18 video/mpeg
8843 18 audio/x-scpls
8844 18 audio/x-flac
8845 18 application/x-ogg
8846 17 video/x-ms-asf
8847 17 text/html
8848 17 audio/x-musepack
8849 16 image/x-xbitmap
8850 &lt;/pre&gt;
8851
8852 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
8853
8854 &lt;pre&gt;
8855 count MIME type
8856 ----- -----------------------
8857 31 text/plain
8858 31 image/png
8859 31 image/jpeg
8860 29 audio/mpeg
8861 28 application/ogg
8862 27 image/gif
8863 26 image/tiff
8864 26 audio/x-mp3
8865 23 audio/x-wav
8866 22 image/bmp
8867 21 audio/x-flac
8868 20 audio/x-mpegurl
8869 19 audio/x-mpeg
8870 18 video/x-ms-asf
8871 18 video/mpeg
8872 18 audio/x-scpls
8873 18 application/x-ogg
8874 17 audio/x-musepack
8875 16 video/x-ms-wmv
8876 16 video/x-msvideo
8877 &lt;/pre&gt;
8878
8879 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
8880 information mentioned in DEP-11. I have not yet had time to look at
8881 it, but hope the PackageKit people in Debian are on top of these
8882 issues.&lt;/p&gt;
8883
8884 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
8885 discovering a typo in my script.&lt;/p&gt;
8886 </description>
8887 </item>
8888
8889 <item>
8890 <title>Using modalias info to find packages handling my hardware</title>
8891 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
8892 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
8893 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
8894 <description>&lt;p&gt;Yesterday, I wrote about the
8895 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
8896 values provided by the Linux kernel&lt;/a&gt; following my hope for
8897 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
8898 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
8899 modalias values attached to package names can be used to map packages
8900 to hardware. This allow the system to look up and suggest relevant
8901 packages when I plug in some new hardware into my machine, and replace
8902 discover and discover-data as the database used to map hardware to
8903 packages.&lt;/p&gt;
8904
8905 &lt;p&gt;I create a modaliases file with entries like the following,
8906 containing package name, kernel module name (if relevant, otherwise
8907 the package name) and globs matching the relevant hardware
8908 modalias.&lt;/p&gt;
8909
8910 &lt;p&gt;&lt;blockquote&gt;
8911 Package: package-name
8912 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
8913 &lt;/blockquote&gt;&lt;/p&gt;
8914
8915 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
8916 for a given modalias value using this file.&lt;/p&gt;
8917
8918 &lt;p&gt;An entry like this would suggest the video and picture application
8919 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
8920
8921 &lt;p&gt;&lt;blockquote&gt;
8922 Package: cheese
8923 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
8924 &lt;/blockquote&gt;&lt;/p&gt;
8925
8926 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
8927 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
8928
8929 &lt;p&gt;&lt;blockquote&gt;
8930 Package: pcmciautils
8931 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8932 &lt;/blockquote&gt;&lt;/p&gt;
8933
8934 &lt;p&gt;An entry like this would suggest the package colorhug-client when
8935 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
8936
8937 &lt;p&gt;&lt;blockquote&gt;
8938 Package: colorhug-client
8939 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
8940 &lt;/blockquote&gt;&lt;/p&gt;
8941
8942 &lt;p&gt;I believe the format is compatible with the format of the Packages
8943 file in the Debian archive. Ubuntu already uses their Packages file
8944 to store their mappings from packages to hardware.&lt;/p&gt;
8945
8946 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
8947 announce the hardware it support in a way my prototype understand.
8948 This allow those publishing packages in an APT source outside the
8949 Debian archive as well as those backporting packages to make sure the
8950 hardware mapping are included in the package meta information. I&#39;ve
8951 tested such header in the pymissile package, and its modalias mapping
8952 is working as it should with my prototype. It even made it to Ubuntu
8953 Raring.&lt;/p&gt;
8954
8955 &lt;p&gt;To test if it was possible to look up supported hardware using only
8956 the shell tools available in the Debian installer, I wrote a shell
8957 implementation of the lookup code. The idea is to create files for
8958 each modalias and let the shell do the matching. Please check out and
8959 try the
8960 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
8961 shell script. It run without any extra dependencies and fetch the
8962 hardware mappings from the Debian archive and the subversion
8963 repository where I currently work on my prototype.&lt;/p&gt;
8964
8965 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
8966 install yubikey-personalization:&lt;/p&gt;
8967
8968 &lt;p&gt;&lt;blockquote&gt;
8969 % ./hw-support-lookup
8970 &lt;br&gt;yubikey-personalization
8971 &lt;br&gt;%
8972 &lt;/blockquote&gt;&lt;/p&gt;
8973
8974 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8975 propose to install the pcmciautils package:&lt;/p&gt;
8976
8977 &lt;p&gt;&lt;blockquote&gt;
8978 % ./hw-support-lookup
8979 &lt;br&gt;pcmciautils
8980 &lt;br&gt;%
8981 &lt;/blockquote&gt;&lt;/p&gt;
8982
8983 &lt;p&gt;If you know of any hardware-package mapping that should be added to
8984 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
8985 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
8986
8987 &lt;p&gt;It could be possible to generate several of the mappings between
8988 packages and hardware. One source would be to look at packages with
8989 kernel modules, ie packages with *.ko files in /lib/modules/, and
8990 extract their modalias information. Another would be to look at
8991 packages with udev rules, ie packages with files in
8992 /lib/udev/rules.d/, and extract their vendor/model information to
8993 generate a modalias matching rule. I have not tested any of these to
8994 see if it work.&lt;/p&gt;
8995
8996 &lt;p&gt;If you want to help implementing a system to let us propose what
8997 packages to install when new hardware is plugged into a Debian
8998 machine, please send me an email or talk to me on
8999 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9000 </description>
9001 </item>
9002
9003 <item>
9004 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
9005 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
9006 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
9007 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
9008 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
9009 information, to find the packages that support a given piece of
9010 hardware, I refreshed my memory regarding modalias values, and decided
9011 to document the details. Here are my findings so far, also available
9012 in
9013 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9014 Debian Edu subversion repository&lt;/a&gt;:
9015
9016 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
9017
9018 &lt;p&gt;This document try to explain what the different types of modalias
9019 values stands for. It is in part based on information from
9020 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
9021 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
9022 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
9023 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
9024
9025 &lt;p&gt;The modalias entries for a given Linux machine can be found using
9026 this shell script:&lt;/p&gt;
9027
9028 &lt;pre&gt;
9029 find /sys -name modalias -print0 | xargs -0 cat | sort -u
9030 &lt;/pre&gt;
9031
9032 &lt;p&gt;The supported modalias globs for a given kernel module can be found
9033 using modinfo:&lt;/p&gt;
9034
9035 &lt;pre&gt;
9036 % /sbin/modinfo psmouse | grep alias:
9037 alias: serio:ty05pr*id*ex*
9038 alias: serio:ty01pr*id*ex*
9039 %
9040 &lt;/pre&gt;
9041
9042 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
9043
9044 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
9045 Bridge memory controller:&lt;/p&gt;
9046
9047 &lt;p&gt;&lt;blockquote&gt;
9048 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9049 &lt;/blockquote&gt;&lt;/p&gt;
9050
9051 &lt;p&gt;This represent these values:&lt;/p&gt;
9052
9053 &lt;pre&gt;
9054 v 00008086 (vendor)
9055 d 00002770 (device)
9056 sv 00001028 (subvendor)
9057 sd 000001AD (subdevice)
9058 bc 06 (bus class)
9059 sc 00 (bus subclass)
9060 i 00 (interface)
9061 &lt;/pre&gt;
9062
9063 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
9064 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
9065 0600. The 0600 class is a host bridge. Other useful bus values are
9066 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
9067
9068 &lt;p&gt;Not sure how to figure out the interface value, nor what it
9069 means.&lt;/p&gt;
9070
9071 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
9072
9073 &lt;p&gt;Some typical USB entries can look like this. This is an internal
9074 USB hub in a laptop:&lt;/p&gt;
9075
9076 &lt;p&gt;&lt;blockquote&gt;
9077 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9078 &lt;/blockquote&gt;&lt;/p&gt;
9079
9080 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
9081
9082 &lt;pre&gt;
9083 v 1D6B (device vendor)
9084 p 0001 (device product)
9085 d 0206 (bcddevice)
9086 dc 09 (device class)
9087 dsc 00 (device subclass)
9088 dp 00 (device protocol)
9089 ic 09 (interface class)
9090 isc 00 (interface subclass)
9091 ip 00 (interface protocol)
9092 &lt;/pre&gt;
9093
9094 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
9095 class is in the interface class section. For a simple USB web camera,
9096 these alias entries show up:&lt;/p&gt;
9097
9098 &lt;p&gt;&lt;blockquote&gt;
9099 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9100 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9101 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9102 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9103 &lt;/blockquote&gt;&lt;/p&gt;
9104
9105 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
9106 camera), 0101 is audio control device and 0102 is audio streaming (aka
9107 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
9108
9109 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
9110
9111 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
9112 receiver in a Thinkpad X40:&lt;/p&gt;
9113
9114 &lt;p&gt;&lt;blockquote&gt;
9115 acpi:IBM0071:PNP0511:
9116 &lt;/blockquote&gt;&lt;/p&gt;
9117
9118 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
9119
9120 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
9121
9122 &lt;p&gt;The DMI table contain lots of information about the computer case
9123 and model. This is an entry for a IBM Thinkpad X40, fetched from
9124 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
9125
9126 &lt;p&gt;&lt;blockquote&gt;
9127 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9128 &lt;/blockquote&gt;&lt;/p&gt;
9129
9130 &lt;p&gt;The values present are&lt;/p&gt;
9131
9132 &lt;pre&gt;
9133 bvn IBM (BIOS vendor)
9134 bvr 1UETB6WW(1.66) (BIOS version)
9135 bd 06/15/2005 (BIOS date)
9136 svn IBM (system vendor)
9137 pn 2371H4G (product name)
9138 pvr ThinkPadX40 (product version)
9139 rvn IBM (board vendor)
9140 rn 2371H4G (board name)
9141 rvr NotAvailable (board version)
9142 cvn IBM (chassis vendor)
9143 ct 10 (chassis type)
9144 cvr NotAvailable (chassis version)
9145 &lt;/pre&gt;
9146
9147 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
9148 found in the dmidecode source:&lt;/p&gt;
9149
9150 &lt;pre&gt;
9151 3 Desktop
9152 4 Low Profile Desktop
9153 5 Pizza Box
9154 6 Mini Tower
9155 7 Tower
9156 8 Portable
9157 9 Laptop
9158 10 Notebook
9159 11 Hand Held
9160 12 Docking Station
9161 13 All In One
9162 14 Sub Notebook
9163 15 Space-saving
9164 16 Lunch Box
9165 17 Main Server Chassis
9166 18 Expansion Chassis
9167 19 Sub Chassis
9168 20 Bus Expansion Chassis
9169 21 Peripheral Chassis
9170 22 RAID Chassis
9171 23 Rack Mount Chassis
9172 24 Sealed-case PC
9173 25 Multi-system
9174 26 CompactPCI
9175 27 AdvancedTCA
9176 28 Blade
9177 29 Blade Enclosing
9178 &lt;/pre&gt;
9179
9180 &lt;p&gt;The chassis type values are not always accurately set in the DMI
9181 table. For example my home server is a tower, but the DMI modalias
9182 claim it is a desktop.&lt;/p&gt;
9183
9184 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
9185
9186 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
9187 test machine:&lt;/p&gt;
9188
9189 &lt;p&gt;&lt;blockquote&gt;
9190 serio:ty01pr00id00ex00
9191 &lt;/blockquote&gt;&lt;/p&gt;
9192
9193 &lt;p&gt;The values present are&lt;/p&gt;
9194
9195 &lt;pre&gt;
9196 ty 01 (type)
9197 pr 00 (prototype)
9198 id 00 (id)
9199 ex 00 (extra)
9200 &lt;/pre&gt;
9201
9202 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
9203 the valid values are.&lt;/p&gt;
9204
9205 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
9206
9207 &lt;p&gt;There are heaps of other modalias subtypes according to
9208 file2alias.c. There is the rest of the list from that source: amba,
9209 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9210 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9211 vmbus, x86cpu and zorro. I did not spend time documenting all of
9212 these, as they do not seem relevant for my intended use with mapping
9213 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
9214
9215 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
9216
9217 &lt;p&gt;To check which kernel modules provide support for a given modalias,
9218 one can use the following shell script:&lt;/p&gt;
9219
9220 &lt;pre&gt;
9221 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
9222 echo &quot;$id&quot; ; \
9223 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
9224 done
9225 &lt;/pre&gt;
9226
9227 &lt;p&gt;The output can look like this (only the first few entries as the
9228 list is very long on my test machine):&lt;/p&gt;
9229
9230 &lt;pre&gt;
9231 acpi:ACPI0003:
9232 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
9233 acpi:device:
9234 FATAL: Module acpi:device: not found.
9235 acpi:IBM0068:
9236 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
9237 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
9238 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
9239 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9240 acpi:IBM0071:PNP0511:
9241 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
9242 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
9243 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
9244 [...]
9245 &lt;/pre&gt;
9246
9247 &lt;p&gt;If you want to help implementing a system to let us propose what
9248 packages to install when new hardware is plugged into a Debian
9249 machine, please send me an email or talk to me on
9250 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9251
9252 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
9253 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
9254 in /sys/ with space in them.&lt;/p&gt;
9255 </description>
9256 </item>
9257
9258 <item>
9259 <title>Moved the pymissile Debian packaging to collab-maint</title>
9260 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
9261 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
9262 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
9263 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
9264 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9265 Launcher and updated the Debian package
9266 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
9267 sure udev will fix the device permissions when it is plugged in. I
9268 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
9269 hopefully make the package be proposed by jockey in Ubuntu when a user
9270 plug in his rocket launcher. In the process I moved the source to a
9271 git repository under collab-maint, to make it easier for any DD to
9272 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
9273 is not very active, but the software still work for me even after five
9274 years of relative silence. The new git repository is not listed in
9275 the uploaded package yet, because I want to test the other changes a
9276 bit more before I upload the new version. If you want to check out
9277 the new version with a .desktop file included, visit the
9278 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
9279 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
9280 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
9281 </description>
9282 </item>
9283
9284 <item>
9285 <title>Lets make hardware dongles easier to use in Debian</title>
9286 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
9287 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
9288 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
9289 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
9290 general, is that there is a great package management system with the
9291 ability to automatically install software packages by downloading them
9292 from the distribution mirrors, but no way to get it to automatically
9293 install the packages I need to use the hardware I plug into my
9294 machine. Even if the package to use it is easily available from the
9295 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9296 suggest to automatically install the python-nxt, nbc and t2n packages
9297 I need to talk to it. When I plug in a Yubikey, it could propose the
9298 yubikey-personalization package. The information required to do this
9299 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
9300
9301 &lt;p&gt;Some years ago, I proposed to
9302 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
9303 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
9304 simple:
9305
9306 &lt;ul&gt;
9307
9308 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
9309 starting when a user log in.&lt;/li&gt;
9310
9311 &lt;li&gt;Set this program up to listen for kernel events emitted when new
9312 hardware is inserted into the computer.&lt;/li&gt;
9313
9314 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
9315 database mapping to packages, and take note of any non-installed
9316 packages.&lt;/li&gt;
9317
9318 &lt;li&gt;Show a message to the user proposing to install the discovered
9319 package, and make it easy to install it.&lt;/li&gt;
9320
9321 &lt;/ul&gt;
9322
9323 &lt;p&gt;I am not sure what the best way to implement this is, but my
9324 initial idea was to use dbus events to discover new hardware, the
9325 discover database to find packages and
9326 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
9327 packages.&lt;/p&gt;
9328
9329 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
9330 draft package is now checked into
9331 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9332 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
9333 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
9334 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9335 the relevant packages in Debian, and uploaded a new version
9336 2.2013.01.09 to unstable. I also discovered that the current
9337 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
9338 package in Debian no longer discovered any USB devices, because
9339 /proc/bus/usb/devices is no longer present. I ported it to use
9340 libusb as a fall back option to get it working. The fixed package
9341 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
9342 because of the freeze).&lt;/p&gt;
9343
9344 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
9345 desktop notification to show up (only once, the first time it is
9346 inserted):&lt;/p&gt;
9347
9348 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-09-hw-autoinstall.png&quot;&gt;&lt;/p&gt;
9349
9350 &lt;p&gt;For this prototype to be really useful, some way to automatically
9351 install the proposed packages by pressing the &quot;Please install
9352 program(s)&quot; button should to be implemented.&lt;/p&gt;
9353
9354 &lt;p&gt;If this idea seem useful to you, and you want to help make it
9355 happen, please help me update the discover-data database with mappings
9356 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
9357 list the package you would like to have installed when a given
9358 hardware device is inserted into your computer, and report bugs using
9359 reportbug if it isn&#39;t. Or, if you know of a better way to provide
9360 such mapping, please let me know.&lt;/p&gt;
9361
9362 &lt;p&gt;This prototype need more work, and there are several questions that
9363 should be considered before it is ready for production use. Is dbus
9364 the correct way to detect new hardware? At the moment I look for HAL
9365 dbus events on the system bus, because that is the events I could see
9366 on my Debian Squeeze KDE desktop. Are there better events to use?
9367 How should the user be notified? Is the desktop notification
9368 mechanism the best option, or should the background daemon raise a
9369 popup instead? How should packages be installed? When should they
9370 not be installed?&lt;/p&gt;
9371
9372 &lt;p&gt;If you want to help getting such feature implemented in Debian,
9373 please send me an email. :)&lt;/p&gt;
9374 </description>
9375 </item>
9376
9377 <item>
9378 <title>New IRC channel for LEGO designers using Debian</title>
9379 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
9380 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
9381 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
9382 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
9383 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
9384 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
9385 discovered I had to build all the tools myself because none were
9386 already in Debian Squeeze. If Debian support for LEGO is something
9387 you care about, please join me on the IRC channel
9388 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
9389 irc.debian.org). There is a lot that could be done to improve the
9390 Debian support for LEGO designers. For example both CAD software
9391 and Mindstorm compilers are missing. :)&lt;/p&gt;
9392
9393 &lt;p&gt;Update 2012-01-03: A
9394 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
9395 including links to Lego related packages is now available.&lt;/p&gt;
9396 </description>
9397 </item>
9398
9399 <item>
9400 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
9401 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
9402 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
9403 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
9404 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
9405 year! I hope next year will prove to be a good year.&lt;/p&gt;
9406
9407 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
9408 decentralised &quot;currency&quot; that allow people to transfer bitcoins
9409 between each other with minimal overhead, is a very interesting
9410 experiment. And as I wrote a few days ago, the bitcoin situation in
9411 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
9412 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
9413 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
9414 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
9415 for one of the ftpmasters to approve the new bitcoin-qt package
9416 name.&lt;/p&gt;
9417
9418 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
9419 team in Debian, you can easily test the package in Debian Squeeze
9420 using the following steps to get a set of working packages:&lt;/p&gt;
9421
9422 &lt;blockquote&gt;&lt;pre&gt;
9423 git clone git://git.debian.org/git/collab-maint/bitcoin
9424 cd bitcoin
9425 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9426 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9427 &lt;/pre&gt;&lt;/blockquote&gt;
9428
9429 &lt;p&gt;You might have to install some build dependencies as well. The
9430 list of commands should give you two packages, bitcoind and
9431 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9432 client will download the complete set of bitcoin &quot;blocks&quot;, which need
9433 around 5.6 GiB of data on my machine at the moment. Make sure your
9434 ~/.bitcoin/ directory have lots of spare room if you want to download
9435 all the blocks. The client will warn if the disk is getting full, so
9436 there is not really a problem if you got too little room, but you will
9437 not be able to get all the features out of the client.&lt;/p&gt;
9438
9439 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
9440 activities, please send Bitcoin donations to my address
9441 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9442 </description>
9443 </item>
9444
9445 <item>
9446 <title>A word on bitcoin support in Debian</title>
9447 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
9448 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
9449 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
9450 <description>&lt;p&gt;It has been a while since I wrote about
9451 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
9452 peer-to-peer based crypto-currency, and the reason is simply that I
9453 have been busy elsewhere. But two days ago, I started looking at the
9454 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
9455 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
9456 is now maintained by a
9457 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
9458 people&lt;/a&gt;, and the grunt work had already been done by this team. We
9459 owe a huge thank you to all these team members. :)
9460 But I was sad to discover that the bitcoin client is missing in
9461 Wheezy. It is only available in Sid (and an outdated client from
9462 backports). The client had several RC bugs registered in BTS blocking
9463 it from entering testing. To try to help the team and improve the
9464 situation, I spent some time providing patches and triaging the bug
9465 reports. I also had a look at the bitcoin package available from Matt
9466 Corallo in a
9467 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
9468 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
9469 Debian package.&lt;/p&gt;
9470
9471 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
9472 IRC, I pushed several patches into the collab-maint git repository to
9473 improve the package. It now contains fixes for the RC issues (not from
9474 me, but fixed by Scott Howard), build rules for a Qt GUI client
9475 package, konqueror support for the bitcoin: URI and bash completion
9476 setup. As I work on Debian Squeeze, I also created
9477 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
9478 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
9479 it and try to integrate it into the git repository before uploading a
9480 new version to unstable.
9481
9482 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
9483 centralized control currently exercised in the monetary system. I
9484 find it completely unacceptable that the USA government is collecting
9485 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9486 that the major credit card companies can block legal money
9487 transactions to Wikileaks. But for bitcoin to succeed, more people
9488 need to use bitcoins, and more people need to accept bitcoins when
9489 they sell products and services. Improving the bitcoin support in
9490 Debian is a small step in the right direction, but not enough.
9491 Unfortunately the user experience when browsing the web and wanting to
9492 pay with bitcoin is still not very good. The bitcoin: URI is a step
9493 in the right direction, but need to work in most or every browser in
9494 use. Also the bitcoin-qt client is too heavy to fire up to do a
9495 quick transaction. I believe there are other clients available, but
9496 have not tested them.&lt;/p&gt;
9497
9498 &lt;p&gt;My
9499 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
9500 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
9501 I received 20.15 BTC so far on the address I provided in my blog two
9502 years ago, as can be
9503 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
9504 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
9505 donation. The blockexplorer service demonstrates quite well that
9506 bitcoin is not quite anonymous and untracked. :) I wonder if the
9507 number of users have gone up since then. If you use bitcoin and want
9508 to show your support of my activity, please send Bitcoin donations to
9509 the same address as last time,
9510 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9511 </description>
9512 </item>
9513
9514 <item>
9515 <title>Git repository for song book for Computer Scientists</title>
9516 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
9517 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
9518 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
9519 <description>&lt;p&gt;As I
9520 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
9521 this summer&lt;/a&gt;, I have created a Computer Science song book a few
9522 years ago, and today I finally found time to create a public
9523 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
9524 repository for the project&lt;/a&gt;.&lt;/p&gt;
9525
9526 &lt;p&gt;If you want to help out, please clone the source and submit patches
9527 to the HTML version. To generate the PDF and PostScript version,
9528 please use prince XML, or let me know about a useful free software
9529 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
9530
9531 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
9532 PostScript formats at
9533 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
9534 Science Songbook&lt;/a&gt;.&lt;/p&gt;
9535 </description>
9536 </item>
9537
9538 <item>
9539 <title>Gratulerer med 19-årsdagen, Debian!</title>
9540 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
9541 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
9542 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
9543 <description>&lt;p&gt;I dag fyller
9544 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
9545 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
9546 si gratulerer med dagen, Debian!&lt;/p&gt;
9547 </description>
9548 </item>
9549
9550 <item>
9551 <title>Song book for Computer Scientists</title>
9552 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
9553 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
9554 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
9555 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
9556 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
9557 collecting computer related songs for use at parties. The original
9558 version was written in LaTeX, but a few years ago I got help from
9559 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9560 while keeping the ability to create a nice book in PDF format. I have
9561 not had time to maintain the book for a while now, and guess I should
9562 put it up on some public version control repository where others can
9563 help me extend and update the book. If anyone is volunteering to help
9564 me with this, send me an email. Also let me know if there are songs
9565 missing in my book.&lt;/p&gt;
9566
9567 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
9568 me today that I really should let all my readers share the joys of
9569 singing out load about programming, computers and computer networks.
9570 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
9571 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
9572 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
9573 Computer Science Songbook&lt;/a&gt;.
9574 </description>
9575 </item>
9576
9577 <item>
9578 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
9579 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
9580 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
9581 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
9582 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
9583 around 1000 at the moment. To be able to get help from the vendors
9584 when something go wrong, we want to keep the firmware on the servers
9585 up to date. If the firmware isn&#39;t the latest and greatest, the
9586 vendors typically refuse to start debugging any problems until the
9587 firmware is upgraded. So before every reboot, we want to upgrade the
9588 firmware, and we would really like everyone handling servers at the
9589 university to do this themselves when they plan to reboot a machine.
9590 For that to happen we at the unix server admin group need to provide
9591 the tools to do so.&lt;/p&gt;
9592
9593 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9594 fetch and install the latest firmware for the servers we got. Most of
9595 our hardware are from Dell and HP, so I have focused on these servers
9596 so far. This blog post is about the Dell part.&lt;/P&gt;
9597
9598 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9599 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9600 with firmware information for all 11th generation servers, listing
9601 which firmware should be used on a given model and where on the FTP
9602 site I can find it. Using a simple perl XML parser I can then
9603 download the shell scripts Dell provides to do firmware upgrades from
9604 within Linux and reboot when all the firmware is primed and ready to
9605 be activated on the first reboot.&lt;/p&gt;
9606
9607 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9608 Are there anyone working on similar tools for firmware upgrading all
9609 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9610
9611 &lt;p&gt;&lt;pre&gt;
9612 #!/usr/bin/perl
9613 use strict;
9614 use warnings;
9615 use File::Temp qw(tempdir);
9616 BEGIN {
9617 # Install needed RHEL packages if missing
9618 my %rhelmodules = (
9619 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9620 );
9621 for my $module (keys %rhelmodules) {
9622 eval &quot;use $module;&quot;;
9623 if ($@) {
9624 my $pkg = $rhelmodules{$module};
9625 system(&quot;yum install -y $pkg&quot;);
9626 eval &quot;use $module;&quot;;
9627 }
9628 }
9629 }
9630 my $errorsto = &#39;pere@hungry.com&#39;;
9631
9632 upgrade_dell();
9633
9634 exit 0;
9635
9636 sub run_firmware_script {
9637 my ($opts, $script) = @_;
9638 unless ($script) {
9639 print STDERR &quot;fail: missing script name\n&quot;;
9640 exit 1
9641 }
9642 print STDERR &quot;Running $script\n\n&quot;;
9643
9644 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9645 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9646 } else {
9647 print STDERR &quot;fail: firmware script returned error\n&quot;;
9648 }
9649 }
9650
9651 sub run_firmware_scripts {
9652 my ($opts, @dirs) = @_;
9653 # Run firmware packages
9654 for my $dir (@dirs) {
9655 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9656 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9657 while (my $s = readdir $dh) {
9658 next if $s =~ m/^\.\.?/;
9659 run_firmware_script($opts, &quot;$dir/$s&quot;);
9660 }
9661 closedir $dh;
9662 }
9663 }
9664
9665 sub download {
9666 my $url = shift;
9667 print STDERR &quot;info: Downloading $url\n&quot;;
9668 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9669 }
9670
9671 sub upgrade_dell {
9672 my @dirs;
9673 my $product = `dmidecode -s system-product-name`;
9674 chomp $product;
9675
9676 if ($product =~ m/PowerEdge/) {
9677
9678 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9679 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9680
9681 my $tmpdir = tempdir(
9682 CLEANUP =&gt; 1
9683 );
9684 chdir($tmpdir);
9685 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9686 system(&#39;gunzip Catalog.xml.gz&#39;);
9687 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9688 # -q is quiet, disabling interactivity and reducing console output
9689 my $fwopts = &quot;-q&quot;;
9690 if (@paths) {
9691 for my $url (@paths) {
9692 fetch_dell_fw($url);
9693 }
9694 run_firmware_scripts($fwopts, $tmpdir);
9695 } else {
9696 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9697 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9698 }
9699 chdir(&#39;/&#39;);
9700 } else {
9701 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9702 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9703 }
9704 }
9705
9706 sub fetch_dell_fw {
9707 my $path = shift;
9708 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9709 download($url);
9710 }
9711
9712 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9713 # firmware packages to download from Dell. Only work for Linux
9714 # machines and 11th generation Dell servers.
9715 sub fetch_dell_fw_list {
9716 my $filename = shift;
9717
9718 my $product = `dmidecode -s system-product-name`;
9719 chomp $product;
9720 my ($mybrand, $mymodel) = split(/\s+/, $product);
9721
9722 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
9723
9724 my $xml = XMLin($filename);
9725 my @paths;
9726 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
9727 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
9728 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
9729 my $oscode;
9730 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
9731 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
9732 } else {
9733 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
9734 }
9735 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
9736 {
9737 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
9738 }
9739 }
9740 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
9741 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
9742
9743 # Drop application packages, only firmware and BIOS
9744 next if &#39;APAC&#39; eq $componenttype;
9745
9746 my $cpath = $component-&gt;{path};
9747 for my $path (@paths) {
9748 if ($cpath =~ m%/$path$%) {
9749 push(@paths, $cpath);
9750 }
9751 }
9752 }
9753 return @paths;
9754 }
9755 &lt;/pre&gt;
9756
9757 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
9758 it could work on other platforms with some tweaking. Anyone know a
9759 index like Catalog.xml is available from HP for HP servers? At the
9760 moment I maintain a similar list manually and it is quickly getting
9761 outdated.&lt;/p&gt;
9762 </description>
9763 </item>
9764
9765 <item>
9766 <title>How is booting into runlevel 1 different from single user boots?</title>
9767 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
9768 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
9769 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
9770 <description>&lt;p&gt;Wouter Verhelst have some
9771 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
9772 comments and opinions&lt;/a&gt; on my blog post on
9773 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html&quot;&gt;the
9774 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
9775 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html&quot;&gt;the
9776 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
9777 small piece of his comment now, and though it best to address the
9778 misunderstanding he bring forward:&lt;/p&gt;
9779
9780 &lt;p&gt;&lt;blockquote&gt;
9781 Currently, a system admin has four options: [...] boot to a
9782 single-user system (by adding &#39;single&#39; to the kernel command line;
9783 this runs rcS and rc1 scripts)
9784 &lt;/blockquote&gt;&lt;/p&gt;
9785
9786 &lt;p&gt;This make me believe Wouter believe booting into single user mode
9787 and booting into runlevel 1 is the same. I am not surprised he
9788 believe this, because it would make sense and is a quite sensible
9789 thing to believe. But because the boot in Debian is slightly broken,
9790 runlevel 1 do not work properly and it isn&#39;t the same as single user
9791 mode. I&#39;ll try to explain what is actually happing, but it is a bit
9792 hard to explain.&lt;/p&gt;
9793
9794 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
9795 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
9796 executed in single user mode is sulogin. Single user mode is a boot
9797 state &quot;between&quot; the runlevels, and when booting into single user mode,
9798 only the scripts in /etc/rcS.d/ are executed before the init process
9799 enters the single user state. When switching to runlevel 1, the state
9800 is in fact not ending in runlevel 1, but it passes through runlevel 1
9801 and end up in the single user mode (see /etc/rc1.d/S03single, which
9802 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
9803 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
9804 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9805 mode).&lt;/p&gt;
9806
9807 &lt;p&gt;This summary might make it clearer. When booting for the first
9808 time into single user mode, the following commands are executed:
9809 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
9810 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
9811 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
9812 trying to continue after visiting single user mode. Not all services
9813 are started again as they should, causing the machine to end up in an
9814 unpredicatble state. This is why Debian admins recommend rebooting
9815 after visiting single user mode.&lt;/p&gt;
9816
9817 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
9818 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
9819 to runlevel 1, the services started from /etc/rcS.d/ are not properly
9820 stopped when passing through the scripts in /etc/rc1.d/, and not
9821 started again when switching away from runlevel 1 to the runlevels
9822 2-5. I believe the problem is best fixed by moving all the scripts
9823 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
9824 functioning single user mode during boot.&lt;/p&gt;
9825
9826 &lt;p&gt;I have spent several years investigating the Debian boot system,
9827 and discovered this problem a few years ago. I suspect it originates
9828 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
9829 </description>
9830 </item>
9831
9832 <item>
9833 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
9834 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
9835 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
9836 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
9837 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
9838 are started from /etc/rcS.d/. In fact, there is a bite more of them
9839 than make sense, and this causes a few problems. What kind of
9840 problems, you might ask. There are at least two problems. The first
9841 is that it is not possible to recover a machine after switching to
9842 runlevel 1. One need to actually reboot to get the machine back to
9843 the expected state. The other is that single user boot will sometimes
9844 run into problems because some of the subsystems are activated before
9845 the root login is presented, causing problems when trying to recover a
9846 machine from a problem in that subsystem. A minor additional point is
9847 that moving more scripts out of rcS.d/ and into the other rc#.d/
9848 directories will increase the amount of scripts that can run in
9849 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
9850
9851 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
9852 scripts that _have_ to execute before the root login prompt is
9853 presented during a single user boot should go there. Everything else
9854 should go into the numeric runlevels. This means things like
9855 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9856 the numeric runlevels. Today in Debian, there are around 115 init.d
9857 scripts that are started from rcS.d/, and most of them should be moved
9858 out. Do your package have one of them? Please help us make single
9859 user and runlevel 1 better by moving it.&lt;/p&gt;
9860
9861 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
9862 etc. should still be started from rcS.d/, but there is for example no
9863 need to have the network enabled before the single user login prompt
9864 is presented.&lt;/p&gt;
9865
9866 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
9867 Debian systems working while scripts migrate and during upgrades, the
9868 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9869 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9870 and the next ones can only be moved when their dependencies have been
9871 moved first. This migration must be done sequentially while we ensure
9872 that the package system upgrade packages in the right order to keep
9873 the system state correct. This will require some coordination when it
9874 comes to network related packages, but most of the packages with
9875 scripts that should migrate do not have anything in rcS.d/ depending
9876 on them. Some packages have already been updated, like the sudo
9877 package, while others are still left to do. I wish I had time to work
9878 on this myself, but real live constrains make it unlikely that I will
9879 find time to push this forward.&lt;/p&gt;
9880 </description>
9881 </item>
9882
9883 <item>
9884 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
9885 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
9886 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
9887 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
9888 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
9889 mentioned the issues I believe should be improved in Debian for its
9890 desktop to be useful for more people. The use case for this is my
9891 parents, which are currently running Kubuntu which solve the
9892 issues.&lt;/p&gt;
9893
9894 &lt;p&gt;I suspect these four missing features are not very hard to
9895 implement. After all, they are present in Ubuntu, so if we wanted to
9896 do this in Debian we would have a source.&lt;/p&gt;
9897
9898 &lt;ol&gt;
9899
9900 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
9901 are new packages available for upgrades, a icon in the KDE status bar
9902 indicate this, and clicking on it will activate the simple upgrade
9903 tool to handle it. I have no problem guiding both of my parents
9904 through the process over the phone. If a kernel reboot is required,
9905 this too is indicated by the status bars and the upgrade tool. Last
9906 time I checked, nothing with the same features was working in KDE in
9907 Debian.&lt;/li&gt;
9908
9909 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
9910 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
9911 currently have a handler for, it will ask the user if the system
9912 should search for a package that would add support for this MIME type,
9913 and if the user say yes, the APT sources will be searched for packages
9914 advertising the MIME type in their control file (visible in the
9915 Packages file in the APT archive). If one or more packages are found,
9916 it is a simple click of the mouse to add support for the missing mime
9917 type. If the package require the user to accept some non-free
9918 license, this is explained to the user. The entire process make it
9919 more clear to the user why something do not work in the browser, and
9920 make the chances higher for the user to blame the web page authors and
9921 not the browser for any missing features.&lt;/li&gt;
9922
9923 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
9924 handlers.&lt;/strong&gt; When the media players encounter a format or codec
9925 it is not supporting, a dialog pop up asking the user if the system
9926 should search for a package that would add support for it. This
9927 happen with things like MP3, Windows Media or H.264. The selection
9928 and installation procedure is very similar to the Firefox browser
9929 plugin handling. This is as far as I know implemented using a
9930 gstreamer hook. The end result is that the user easily get access to
9931 the codecs that are present from the APT archives available, while
9932 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
9933
9934 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
9935 displaying a text/plain file in my Debian browser, it will propose to
9936 start emacs to show it. If I remember correctly, when doing the same
9937 in Kunbutu it show the file as a text file in the browser. At least I
9938 know Opera will show text files within the browser. I much prefer the
9939 latter behaviour.&lt;/li&gt;
9940
9941 &lt;/ol&gt;
9942
9943 &lt;p&gt;There are other nice features as well, like the simplified suite
9944 upgrader, but given that I am the one mostly doing the dist-upgrade,
9945 it do not matter much.&lt;/p&gt;
9946
9947 &lt;p&gt;I really hope we could get these features in place for the next
9948 Debian release. It would require the coordinated effort of several
9949 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
9950 </description>
9951 </item>
9952
9953 <item>
9954 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
9955 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
9956 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
9957 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
9958 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
9959 site is build on Debian/Squeeze, and this platform was chosen because
9960 I am most familiar with Debian (being a Debian Developer for around 10
9961 years) because it is the latest stable Debian release which should get
9962 security support for a few years.&lt;/p&gt;
9963
9964 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
9965 that are missing in Debian at the moment. It would be great if these
9966 modules were added to the Debian archive, allowing anyone to set up
9967 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
9968 in their own country using only Debian packages. The list of modules
9969 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
9970 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
9971 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9972 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9973 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9974 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9975 easier in the future.&lt;/p&gt;
9976
9977 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
9978 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
9979 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
9980 with the responsibility of tracking security problems, which I really
9981 do not have time for.&lt;/p&gt;
9982 </description>
9983 </item>
9984
9985 <item>
9986 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
9987 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
9988 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
9989 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
9990 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
9991 posts have been in Norwegian the last few weeks, so here is a short
9992 update in English.&lt;/p&gt;
9993
9994 &lt;p&gt;The kids still keep me too busy to get much free software work
9995 done, but I did manage to organise a project to get a Norwegian port
9996 of the British service
9997 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
9998 and it has been running for a month now. The entire project has been
9999 organised by me and two others. Around Christmas we gathered sponsors
10000 to fund the development work. In January I drafted a contract with
10001 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
10002 and in February the development took place. Most of it involved
10003 converting the source to use GPS coordinates instead of British
10004 easting/northing, and the resulting code should be a lot easier to get
10005 running in any country by now. The Norwegian
10006 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
10007 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
10008 source and the source for administrative borders in Norway, and
10009 support for this had to be added/fixed.&lt;/p&gt;
10010
10011 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
10012 polishing the system before we announced it March 7th. The system is
10013 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
10014 problem reports in a few weeks. Soon we hope to announce the Android
10015 and iPhone versions making it even easier to report problems with the
10016 public infrastructure.&lt;/p&gt;
10017
10018 &lt;p&gt;Perhaps something to consider for those of you in countries without
10019 such service?&lt;/p&gt;
10020 </description>
10021 </item>
10022
10023 <item>
10024 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
10025 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
10026 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
10027 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
10028 <description>&lt;p&gt;The last few days I have looked at ways to track open security
10029 issues here at my work with the University of Oslo. My idea is that
10030 it should be possible to use the information about security issues
10031 available on the Internet, and check our locally
10032 maintained/distributed software against this information. It should
10033 allow us to verify that no known security issues are forgotten. The
10034 CVE database listing vulnerabilities seem like a great central point,
10035 and by using the package lists from Debian mapped to CVEs provided by
10036 the testing security team, I believed it should be possible to figure
10037 out which security holes were present in our free software
10038 collection.&lt;/p&gt;
10039
10040 &lt;p&gt;After reading up on the topic, it became obvious that the first
10041 building block is to be able to name software packages in a unique and
10042 consistent way across data sources. I considered several ways to do
10043 this, for example coming up with my own naming scheme like using URLs
10044 to project home pages or URLs to the Freshmeat entries, or using some
10045 existing naming scheme. And it seem like I am not the first one to
10046 come across this problem, as MITRE already proposed and implemented a
10047 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
10048 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
10049 software, hardware and other platform components. The CPE ids are
10050 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
10051 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
10052 issues for any CPE name. With this in place, all I need to do is to
10053 locate the CPE id for the software packages we use at the university.
10054 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
10055 NVD entry if a CVE for the package exist).&lt;/p&gt;
10056
10057 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
10058 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
10059 check out, one could look up
10060 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%3A%2Fa%3Agnu%3Agzip:1.3.3&quot;&gt;cpe:/a:gnu:gzip:1.3.3
10061 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
10062 The most recent one is
10063 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
10064 and at the bottom of the NVD page for this vulnerability the complete
10065 list of affected versions is provided.&lt;/p&gt;
10066
10067 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
10068 for offline processing of issues. Using this dump, I&#39;ve written a
10069 small script taking a list of CPEs as input and list all CVEs
10070 affecting the packages represented by these CPEs. One give it CPEs
10071 with version numbers as specified above and get a list of open
10072 security issues out.&lt;/p&gt;
10073
10074 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
10075 information need to be high. For that to happen, I believe as many as
10076 possible need to use and contribute to the NVD database. I notice
10077 RHEL is providing
10078 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
10079 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
10080 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
10081
10082 &lt;p&gt;To get an idea about the quality for free software, I spent some
10083 time making it possible to compare the CVE database from Debian with
10084 the CVE database in NVD. The result look fairly good, but there are
10085 some inconsistencies in NVD (same software package having several
10086 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10087 Debian believe are affected by a CVE). Hope to find time to improve
10088 the quality of NVD, but that require being able to get in touch with
10089 someone maintaining it. So far my three emails with questions and
10090 corrections have not seen any reply, but I hope contact can be
10091 established soon.&lt;/p&gt;
10092
10093 &lt;p&gt;An interesting application for CPEs is cross platform package
10094 mapping. It would be useful to know which packages in for example
10095 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10096 this would be trivial if all linux distributions provided CPE entries
10097 for their packages.&lt;/p&gt;
10098 </description>
10099 </item>
10100
10101 <item>
10102 <title>Which module is loaded for a given PCI and USB device?</title>
10103 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
10104 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
10105 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
10106 <description>&lt;p&gt;In the
10107 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
10108 package in Debian, there is a script to report useful information
10109 about the running hardware for use when people report missing
10110 information. One part of this script that I find very useful when
10111 debugging hardware problems, is the part mapping loaded kernel module
10112 to the PCI device it claims. It allow me to quickly see if the kernel
10113 module I expect is driving the hardware I am struggling with. To see
10114 the output, make sure discover-data is installed and run
10115 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
10116 one of my machines like this:&lt;/p&gt;
10117
10118 &lt;pre&gt;
10119 loaded modules:
10120 10de:03eb i2c_nforce2
10121 10de:03f1 ohci_hcd
10122 10de:03f2 ehci_hcd
10123 10de:03f0 snd_hda_intel
10124 10de:03ec pata_amd
10125 10de:03f6 sata_nv
10126 1022:1103 k8temp
10127 109e:036e bttv
10128 109e:0878 snd_bt87x
10129 11ab:4364 sky2
10130 &lt;/pre&gt;
10131
10132 &lt;p&gt;The code in question look like this, slightly modified for
10133 readability and to drop the output to file descriptor 3:&lt;/p&gt;
10134
10135 &lt;pre&gt;
10136 if [ -d /sys/bus/pci/devices/ ] ; then
10137 echo loaded pci modules:
10138 (
10139 cd /sys/bus/pci/devices/
10140 for address in * ; do
10141 if [ -d &quot;$address/driver/module&quot; ] ; then
10142 module=`cd $address/driver/module ; pwd -P | xargs basename`
10143 if grep -q &quot;^$module &quot; /proc/modules ; then
10144 address=$(echo $address |sed s/0000://)
10145 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
10146 echo &quot;$id $module&quot;
10147 fi
10148 fi
10149 done
10150 )
10151 echo
10152 fi
10153 &lt;/pre&gt;
10154
10155 &lt;p&gt;Similar code could be used to extract USB device module
10156 mappings:&lt;/p&gt;
10157
10158 &lt;pre&gt;
10159 if [ -d /sys/bus/usb/devices/ ] ; then
10160 echo loaded usb modules:
10161 (
10162 cd /sys/bus/usb/devices/
10163 for address in * ; do
10164 if [ -d &quot;$address/driver/module&quot; ] ; then
10165 module=`cd $address/driver/module ; pwd -P | xargs basename`
10166 if grep -q &quot;^$module &quot; /proc/modules ; then
10167 address=$(echo $address |sed s/0000://)
10168 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
10169 if [ &quot;$id&quot; ] ; then
10170 echo &quot;$id $module&quot;
10171 fi
10172 fi
10173 fi
10174 done
10175 )
10176 echo
10177 fi
10178 &lt;/pre&gt;
10179
10180 &lt;p&gt;This might perhaps be something to include in other tools as
10181 well.&lt;/p&gt;
10182 </description>
10183 </item>
10184
10185 <item>
10186 <title>How to test if a laptop is working with Linux</title>
10187 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
10188 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
10189 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
10190 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
10191 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
10192 batch of computers will work with Linux. Every year for the last few
10193 years the university have organised shared bid of a few thousand
10194 computers, and this year HP won the bid. Two different desktops and
10195 five different laptops are on the list this year. We in the UNIX
10196 group want to know which one of these computers work well with RHEL
10197 and Ubuntu, the two Linux distributions we currently handle at the
10198 university.&lt;/p&gt;
10199
10200 &lt;p&gt;My test method is simple, and I share it here to get feedback and
10201 perhaps inspire others to test hardware as well. To test, I PXE
10202 install the OS version of choice, and log in as my normal user and run
10203 a few applications and plug in selected pieces of hardware. When
10204 something fail, I make a note about this in the test matrix and move
10205 on. If I have some spare time I try to report the bug to the OS
10206 vendor, but as I only have the machines for a short time, I rarely
10207 have the time to do this for all the problems I find.&lt;/p&gt;
10208
10209 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
10210 I perform on a new model.&lt;/p&gt;
10211
10212 &lt;ul&gt;
10213
10214 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
10215 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10216 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
10217
10218 &lt;li&gt;Is X.org working? If the graphical login screen show up after
10219 installation, X.org is working.&lt;/li&gt;
10220
10221 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
10222 package mesa-utils on Ubuntu) and writing down the frames per second
10223 reported by the program.&lt;/li&gt;
10224
10225 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
10226 logging in, and if I can hear this the test is successful. If there
10227 are several audio exits on the machine, I try them all and check if
10228 the Gnome/KDE audio mixer can control where to send the sound. I
10229 normally test this by playing
10230 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
10231 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
10232
10233 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
10234 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
10235
10236 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
10237 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
10238
10239 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
10240 picture from the v4l device show up.&lt;/li&gt;
10241
10242 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10243 any bluetooth devices are discovered. In my office, I normally see a
10244 few.&lt;/li&gt;
10245
10246 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
10247 memory modules lying around, and stick them in and see if Gnome/KDE
10248 notice this.&lt;/li&gt;
10249
10250 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
10251 special button work, and if the laptop continue to work after
10252 resume.&lt;/li&gt;
10253
10254 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
10255 adjusting background light, switching on/off external video output,
10256 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10257 laptop to laptop, so I just write down which are working and which are
10258 not.&lt;/li&gt;
10259
10260 &lt;li&gt;Some laptops have smart card readers, finger print readers,
10261 acceleration sensors etc. I rarely test these, as I do not know how
10262 to quickly test if they are working or not, so I only document their
10263 existence.&lt;/li&gt;
10264
10265 &lt;/ul&gt;
10266
10267 &lt;p&gt;By now I suspect you are really curious what the test results are
10268 for the HP machines I am testing. I&#39;m not done yet, so I will report
10269 the test results later. For now I can report that HP 8100 Elite work
10270 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
10271 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
10272 can see, I have most machines left to test. One interesting
10273 observation is that Ubuntu Lucid has almost twice the frame rate than
10274 RHEL6 with glxgears. No idea why.&lt;/p&gt;
10275 </description>
10276 </item>
10277
10278 <item>
10279 <title>Some thoughts on BitCoins</title>
10280 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
10281 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
10282 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
10283 <description>&lt;p&gt;As I continue to explore
10284 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
10285 what properties the system have, and how it will be affected by laws
10286 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
10287
10288 &lt;p&gt;One interesting thing to note is that since the transactions are
10289 verified using a peer to peer network, all details about a transaction
10290 is known to everyone. This means that if a BitCoin address has been
10291 published like I did with mine in my initial post about BitCoin, it is
10292 possible for everyone to see how many BitCoins have been transfered to
10293 that address. There is even a web service to look at the details for
10294 all transactions. There I can see that my address
10295 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
10296 have received 16.06 Bitcoin, the
10297 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
10298 address of Simon Phipps have received 181.97 BitCoin and the address
10299 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
10300 of EFF have received 2447.38 BitCoins so far. Thank you to each and
10301 every one of you that donated bitcoins to support my activity. The
10302 fact that anyone can see how much money was transfered to a given
10303 address make it more obvious why the BitCoin community recommend to
10304 generate and hand out a new address for each transaction. I&#39;m told
10305 there is no way to track which addresses belong to a given person or
10306 organisation without the person or organisation revealing it
10307 themselves, as Simon, EFF and I have done.&lt;/p&gt;
10308
10309 &lt;p&gt;In Norway, and in most other countries, there are laws and
10310 regulations limiting how much money one can transfer across the border
10311 without declaring it. There are money laundering, tax and accounting
10312 laws and regulations I would expect to apply to the use of BitCoin.
10313 If the Skolelinux foundation
10314 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
10315 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
10316 normal bank transfers like EFF is doing, how should this be accounted?
10317 Given that it is impossible to know if money can cross the border or
10318 not, should everything or nothing be declared? What exchange rate
10319 should be used when calculating taxes? Would receivers have to pay
10320 income tax if the foundation were to pay Skolelinux contributors in
10321 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
10322
10323 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
10324 accepted by a lot of users. It must be possible to get easy access to
10325 the currency (as a wage or using currency exchanges), and it must be
10326 easy to spend it. At the moment BitCoin seem fairly easy to get
10327 access to, but there are very few places to spend it. I am not really
10328 a regular user of any of the vendor types currently accepting BitCoin,
10329 so I wonder when my kind of shop would start accepting BitCoins. I
10330 would like to buy electronics, travels and subway tickets, not herbs
10331 and books. :) The currency is young, and this will improve over time
10332 if it become popular, but I suspect regular banks will start to lobby
10333 to get BitCoin declared illegal if it become popular. I&#39;m sure they
10334 will claim it is helping fund terrorism and money laundering (which
10335 probably would be true, as is any currency in existence), but I
10336 believe the problems should be solved elsewhere and not by blaming
10337 currencies.&lt;/p&gt;
10338
10339 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
10340 CPU intensive process that depend on a bit of luck as well (as one is
10341 competing against all the other miners currently spending CPU cycles
10342 to see which one get the next lump of cash). The &quot;winner&quot; get 50
10343 BitCoin when this happen. Yesterday I came across the obvious way to
10344 join forces to increase ones changes of getting at least some coins,
10345 by coordinating the work on mining BitCoins across several machines
10346 and people, and sharing the result if one is lucky and get the 50
10347 BitCoins. Check out
10348 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
10349 if this sounds interesting. I have not had time to try to set up a
10350 machine to participate there yet, but have seen that running on ones
10351 own for a few days have not yield any BitCoins througth mining
10352 yet.&lt;/p&gt;
10353
10354 &lt;p&gt;Update 2010-12-15: Found an &lt;a
10355 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
10356 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
10357 it was interesting to read. The arguments presented seem to be
10358 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
10359 </description>
10360 </item>
10361
10362 <item>
10363 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
10364 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
10365 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
10366 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
10367 <description>&lt;p&gt;With this weeks lawless
10368 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
10369 attacks&lt;/a&gt; on Wikileak and
10370 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
10371 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
10372 not be trusted to handle money transactions.
10373 A blog post from
10374 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
10375 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
10376 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
10377 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
10378 some help from my friend to get it all running, and he even handed me
10379 some bitcoins to get started. I even donated a few bitcoins to Simon
10380 for helping me remember BitCoin.&lt;/p&gt;
10381
10382 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
10383 crypto-currency, decentralised and handled using peer-to-peer
10384 networks. It allows anonymous transactions and prohibits central
10385 control over the transactions, making it impossible for governments
10386 and companies alike to block donations and other transactions. The
10387 source is free software, and while the key dependency wxWidgets 2.9
10388 for the graphical user interface is missing in Debian, the command
10389 line client builds just fine. Hopefully Jonas
10390 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
10391 Debian&lt;/a&gt; soon.&lt;/p&gt;
10392
10393 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
10394 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
10395 bitcoins&lt;/a&gt; when selling services and goods, and there are even
10396 currency &quot;stock&quot; markets where the exchange rate is decided. There
10397 are not many users so far, but the concept seems promising. If you
10398 want to get started and lack a friend with any bitcoins to spare,
10399 you can even get
10400 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
10401 bitcoin at the time of writing). Use
10402 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
10403 on the current exchange rates.&lt;/p&gt;
10404
10405 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
10406 machines. If you want to support my activity, please send Bitcoin
10407 donations to the address
10408 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
10409 </description>
10410 </item>
10411
10412 <item>
10413 <title>Why isn&#39;t Debian Edu using VLC?</title>
10414 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
10415 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
10416 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
10417 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
10418 presented, and the winner among the multimedia player were VLC.
10419 Personally, I like VLC, and it is my player of choice when I first try
10420 to play a video file or stream. Only if VLC fail will I drag out
10421 gmplayer to see if it can do better. The reason is mostly the failure
10422 model and trust. When VLC fail, it normally pop up a error message
10423 reporting the problem. When mplayer fail, it normally segfault or
10424 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
10425
10426 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
10427 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10428 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
10429 plugin to play web videos seamlessly, and the VLC browser plugin is
10430 not very good. For example, it lack in-line control buttons, so there
10431 is no way for the user to pause the video. Also, when I
10432 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
10433 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
10434 failed on several video pages where mplayer based plugins worked. If
10435 the browser plugin for VLC was as good as the gecko-mediaplayer
10436 package (which uses mplayer), we would switch.&lt;/P&gt;
10437
10438 &lt;p&gt;While VLC is a good player, its user interface is slightly
10439 annoying. The most annoying feature is its inconsistent use of
10440 keyboard shortcuts. When the player is in full screen mode, its
10441 shortcuts are different from when it is playing the video in a window.
10442 For example, space only work as pause when in full screen mode. I
10443 wish it had consisten shortcuts and that space also would work when in
10444 window mode. Another nice shortcut in gmplayer is [enter] to restart
10445 the current video. It is very nice when playing short videos from the
10446 web and want to restart it when new people arrive to have a look at
10447 what is going on.&lt;/p&gt;
10448 </description>
10449 </item>
10450
10451 <item>
10452 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
10453 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
10454 <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>
10455 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
10456 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
10457 upgrade testing of the
10458 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10459 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
10460 This seem like a very good idea, so I adjusted by test scripts and
10461 can now present the updated result from today:&lt;/p&gt;
10462
10463 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10464
10465 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10466
10467 &lt;blockquote&gt;&lt;p&gt;
10468 apache2.2-bin
10469 aptdaemon
10470 baobab
10471 binfmt-support
10472 browser-plugin-gnash
10473 cheese-common
10474 cli-common
10475 cups-pk-helper
10476 dmz-cursor-theme
10477 empathy
10478 empathy-common
10479 freedesktop-sound-theme
10480 freeglut3
10481 gconf-defaults-service
10482 gdm-themes
10483 gedit-plugins
10484 geoclue
10485 geoclue-hostip
10486 geoclue-localnet
10487 geoclue-manual
10488 geoclue-yahoo
10489 gnash
10490 gnash-common
10491 gnome
10492 gnome-backgrounds
10493 gnome-cards-data
10494 gnome-codec-install
10495 gnome-core
10496 gnome-desktop-environment
10497 gnome-disk-utility
10498 gnome-screenshot
10499 gnome-search-tool
10500 gnome-session-canberra
10501 gnome-system-log
10502 gnome-themes-extras
10503 gnome-themes-more
10504 gnome-user-share
10505 gstreamer0.10-fluendo-mp3
10506 gstreamer0.10-tools
10507 gtk2-engines
10508 gtk2-engines-pixbuf
10509 gtk2-engines-smooth
10510 hamster-applet
10511 libapache2-mod-dnssd
10512 libapr1
10513 libaprutil1
10514 libaprutil1-dbd-sqlite3
10515 libaprutil1-ldap
10516 libart2.0-cil
10517 libboost-date-time1.42.0
10518 libboost-python1.42.0
10519 libboost-thread1.42.0
10520 libchamplain-0.4-0
10521 libchamplain-gtk-0.4-0
10522 libcheese-gtk18
10523 libclutter-gtk-0.10-0
10524 libcryptui0
10525 libdiscid0
10526 libelf1
10527 libepc-1.0-2
10528 libepc-common
10529 libepc-ui-1.0-2
10530 libfreerdp-plugins-standard
10531 libfreerdp0
10532 libgconf2.0-cil
10533 libgdata-common
10534 libgdata7
10535 libgdu-gtk0
10536 libgee2
10537 libgeoclue0
10538 libgexiv2-0
10539 libgif4
10540 libglade2.0-cil
10541 libglib2.0-cil
10542 libgmime2.4-cil
10543 libgnome-vfs2.0-cil
10544 libgnome2.24-cil
10545 libgnomepanel2.24-cil
10546 libgpod-common
10547 libgpod4
10548 libgtk2.0-cil
10549 libgtkglext1
10550 libgtksourceview2.0-common
10551 libmono-addins-gui0.2-cil
10552 libmono-addins0.2-cil
10553 libmono-cairo2.0-cil
10554 libmono-corlib2.0-cil
10555 libmono-i18n-west2.0-cil
10556 libmono-posix2.0-cil
10557 libmono-security2.0-cil
10558 libmono-sharpzip2.84-cil
10559 libmono-system2.0-cil
10560 libmtp8
10561 libmusicbrainz3-6
10562 libndesk-dbus-glib1.0-cil
10563 libndesk-dbus1.0-cil
10564 libopal3.6.8
10565 libpolkit-gtk-1-0
10566 libpt2.6.7
10567 libpython2.6
10568 librpm1
10569 librpmio1
10570 libsdl1.2debian
10571 libsrtp0
10572 libssh-4
10573 libtelepathy-farsight0
10574 libtelepathy-glib0
10575 libtidy-0.99-0
10576 media-player-info
10577 mesa-utils
10578 mono-2.0-gac
10579 mono-gac
10580 mono-runtime
10581 nautilus-sendto
10582 nautilus-sendto-empathy
10583 p7zip-full
10584 pkg-config
10585 python-aptdaemon
10586 python-aptdaemon-gtk
10587 python-axiom
10588 python-beautifulsoup
10589 python-bugbuddy
10590 python-clientform
10591 python-coherence
10592 python-configobj
10593 python-crypto
10594 python-cupshelpers
10595 python-elementtree
10596 python-epsilon
10597 python-evolution
10598 python-feedparser
10599 python-gdata
10600 python-gdbm
10601 python-gst0.10
10602 python-gtkglext1
10603 python-gtksourceview2
10604 python-httplib2
10605 python-louie
10606 python-mako
10607 python-markupsafe
10608 python-mechanize
10609 python-nevow
10610 python-notify
10611 python-opengl
10612 python-openssl
10613 python-pam
10614 python-pkg-resources
10615 python-pyasn1
10616 python-pysqlite2
10617 python-rdflib
10618 python-serial
10619 python-tagpy
10620 python-twisted-bin
10621 python-twisted-conch
10622 python-twisted-core
10623 python-twisted-web
10624 python-utidylib
10625 python-webkit
10626 python-xdg
10627 python-zope.interface
10628 remmina
10629 remmina-plugin-data
10630 remmina-plugin-rdp
10631 remmina-plugin-vnc
10632 rhythmbox-plugin-cdrecorder
10633 rhythmbox-plugins
10634 rpm-common
10635 rpm2cpio
10636 seahorse-plugins
10637 shotwell
10638 software-center
10639 system-config-printer-udev
10640 telepathy-gabble
10641 telepathy-mission-control-5
10642 telepathy-salut
10643 tomboy
10644 totem
10645 totem-coherence
10646 totem-mozilla
10647 totem-plugins
10648 transmission-common
10649 xdg-user-dirs
10650 xdg-user-dirs-gtk
10651 xserver-xephyr
10652 &lt;/p&gt;&lt;/blockquote&gt;
10653
10654 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10655
10656 &lt;blockquote&gt;&lt;p&gt;
10657 cheese
10658 ekiga
10659 eog
10660 epiphany-extensions
10661 evolution-exchange
10662 fast-user-switch-applet
10663 file-roller
10664 gcalctool
10665 gconf-editor
10666 gdm
10667 gedit
10668 gedit-common
10669 gnome-games
10670 gnome-games-data
10671 gnome-nettool
10672 gnome-system-tools
10673 gnome-themes
10674 gnuchess
10675 gucharmap
10676 guile-1.8-libs
10677 libavahi-ui0
10678 libdmx1
10679 libgalago3
10680 libgtk-vnc-1.0-0
10681 libgtksourceview2.0-0
10682 liblircclient0
10683 libsdl1.2debian-alsa
10684 libspeexdsp1
10685 libsvga1
10686 rhythmbox
10687 seahorse
10688 sound-juicer
10689 system-config-printer
10690 totem-common
10691 transmission-gtk
10692 vinagre
10693 vino
10694 &lt;/p&gt;&lt;/blockquote&gt;
10695
10696 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10697
10698 &lt;blockquote&gt;&lt;p&gt;
10699 gstreamer0.10-gnomevfs
10700 &lt;/p&gt;&lt;/blockquote&gt;
10701
10702 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10703
10704 &lt;blockquote&gt;&lt;p&gt;
10705 [nothing]
10706 &lt;/p&gt;&lt;/blockquote&gt;
10707
10708 &lt;p&gt;This is for KDE:&lt;/p&gt;
10709
10710 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10711
10712 &lt;blockquote&gt;&lt;p&gt;
10713 ksmserver
10714 &lt;/p&gt;&lt;/blockquote&gt;
10715
10716 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10717
10718 &lt;blockquote&gt;&lt;p&gt;
10719 kwin
10720 network-manager-kde
10721 &lt;/p&gt;&lt;/blockquote&gt;
10722
10723 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10724
10725 &lt;blockquote&gt;&lt;p&gt;
10726 arts
10727 dolphin
10728 freespacenotifier
10729 google-gadgets-gst
10730 google-gadgets-xul
10731 kappfinder
10732 kcalc
10733 kcharselect
10734 kde-core
10735 kde-plasma-desktop
10736 kde-standard
10737 kde-window-manager
10738 kdeartwork
10739 kdeartwork-emoticons
10740 kdeartwork-style
10741 kdeartwork-theme-icon
10742 kdebase
10743 kdebase-apps
10744 kdebase-workspace
10745 kdebase-workspace-bin
10746 kdebase-workspace-data
10747 kdeeject
10748 kdelibs
10749 kdeplasma-addons
10750 kdeutils
10751 kdewallpapers
10752 kdf
10753 kfloppy
10754 kgpg
10755 khelpcenter4
10756 kinfocenter
10757 konq-plugins-l10n
10758 konqueror-nsplugins
10759 kscreensaver
10760 kscreensaver-xsavers
10761 ktimer
10762 kwrite
10763 libgle3
10764 libkde4-ruby1.8
10765 libkonq5
10766 libkonq5-templates
10767 libnetpbm10
10768 libplasma-ruby
10769 libplasma-ruby1.8
10770 libqt4-ruby1.8
10771 marble-data
10772 marble-plugins
10773 netpbm
10774 nuvola-icon-theme
10775 plasma-dataengines-workspace
10776 plasma-desktop
10777 plasma-desktopthemes-artwork
10778 plasma-runners-addons
10779 plasma-scriptengine-googlegadgets
10780 plasma-scriptengine-python
10781 plasma-scriptengine-qedje
10782 plasma-scriptengine-ruby
10783 plasma-scriptengine-webkit
10784 plasma-scriptengines
10785 plasma-wallpapers-addons
10786 plasma-widget-folderview
10787 plasma-widget-networkmanagement
10788 ruby
10789 sweeper
10790 update-notifier-kde
10791 xscreensaver-data-extra
10792 xscreensaver-gl
10793 xscreensaver-gl-extra
10794 xscreensaver-screensaver-bsod
10795 &lt;/p&gt;&lt;/blockquote&gt;
10796
10797 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10798
10799 &lt;blockquote&gt;&lt;p&gt;
10800 ark
10801 google-gadgets-common
10802 google-gadgets-qt
10803 htdig
10804 kate
10805 kdebase-bin
10806 kdebase-data
10807 kdepasswd
10808 kfind
10809 klipper
10810 konq-plugins
10811 konqueror
10812 ksysguard
10813 ksysguardd
10814 libarchive1
10815 libcln6
10816 libeet1
10817 libeina-svn-06
10818 libggadget-1.0-0b
10819 libggadget-qt-1.0-0b
10820 libgps19
10821 libkdecorations4
10822 libkephal4
10823 libkonq4
10824 libkonqsidebarplugin4a
10825 libkscreensaver5
10826 libksgrd4
10827 libksignalplotter4
10828 libkunitconversion4
10829 libkwineffects1a
10830 libmarblewidget4
10831 libntrack-qt4-1
10832 libntrack0
10833 libplasma-geolocation-interface4
10834 libplasmaclock4a
10835 libplasmagenericshell4
10836 libprocesscore4a
10837 libprocessui4a
10838 libqalculate5
10839 libqedje0a
10840 libqtruby4shared2
10841 libqzion0a
10842 libruby1.8
10843 libscim8c2a
10844 libsmokekdecore4-3
10845 libsmokekdeui4-3
10846 libsmokekfile3
10847 libsmokekhtml3
10848 libsmokekio3
10849 libsmokeknewstuff2-3
10850 libsmokeknewstuff3-3
10851 libsmokekparts3
10852 libsmokektexteditor3
10853 libsmokekutils3
10854 libsmokenepomuk3
10855 libsmokephonon3
10856 libsmokeplasma3
10857 libsmokeqtcore4-3
10858 libsmokeqtdbus4-3
10859 libsmokeqtgui4-3
10860 libsmokeqtnetwork4-3
10861 libsmokeqtopengl4-3
10862 libsmokeqtscript4-3
10863 libsmokeqtsql4-3
10864 libsmokeqtsvg4-3
10865 libsmokeqttest4-3
10866 libsmokeqtuitools4-3
10867 libsmokeqtwebkit4-3
10868 libsmokeqtxml4-3
10869 libsmokesolid3
10870 libsmokesoprano3
10871 libtaskmanager4a
10872 libtidy-0.99-0
10873 libweather-ion4a
10874 libxklavier16
10875 libxxf86misc1
10876 okteta
10877 oxygencursors
10878 plasma-dataengines-addons
10879 plasma-scriptengine-superkaramba
10880 plasma-widget-lancelot
10881 plasma-widgets-addons
10882 plasma-widgets-workspace
10883 polkit-kde-1
10884 ruby1.8
10885 systemsettings
10886 update-notifier-common
10887 &lt;/p&gt;&lt;/blockquote&gt;
10888
10889 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
10890 aptitude a bit more similar, but there are still quite a lott of
10891 differences. I have no idea what packages should be installed after
10892 the upgrade, but hope those that do can have a look.&lt;/p&gt;
10893 </description>
10894 </item>
10895
10896 <item>
10897 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
10898 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
10899 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
10900 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
10901 <description>&lt;p&gt;Most of the computers in use by the
10902 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
10903 are virtual machines. And they have been Xen machines running on a
10904 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
10905 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
10906 bit harder that it could have been, because we set up the Xen virtual
10907 machines to get the virtual partitions from LVM, which as far as I
10908 know is not supported by KVM. So to migrate, we had to convert
10909 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
10910
10911 &lt;p&gt;I found
10912 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
10913 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
10914 migration. It uses qemu-img from the qemu package to make the disk
10915 image, parted to partition it, losetup and kpartx to present the disk
10916 image partions as devices, and dd to copy the data. I NFS mounted the
10917 new servers storage area on the old server to do the migration.&lt;/p&gt;
10918
10919 &lt;pre&gt;
10920 #!/bin/sh
10921
10922 # Based on
10923 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10924
10925 set -e
10926 set -x
10927
10928 if [ -z &quot;$1&quot; ] ; then
10929 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
10930 exit 1
10931 else
10932 host=&quot;$1&quot;
10933 fi
10934
10935 if [ ! -e /dev/vg_data/$host-disk ] ; then
10936 echo &quot;error: unable to find LVM volume for $host&quot;
10937 exit 1
10938 fi
10939
10940 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10941 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10942 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10943 totalsize=$(( ( $disksize + $swapsize ) ))
10944
10945 img=$host.img
10946 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
10947 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10948
10949 parted $img mklabel msdos
10950 parted $img mkpart primary linux-swap 0 $disksize
10951 parted $img mkpart primary ext2 $disksize $totalsize
10952 parted $img set 1 boot on
10953
10954 modprobe dm-mod
10955 losetup /dev/loop0 $img
10956 kpartx -a /dev/loop0
10957
10958 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
10959 fsck.ext3 -f /dev/mapper/loop0p1 || true
10960 mkswap /dev/mapper/loop0p2
10961
10962 kpartx -d /dev/loop0
10963 losetup -d /dev/loop0
10964 &lt;/pre&gt;
10965
10966 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
10967 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
10968
10969 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
10970 the new disk image attached, installed grub-pc and linux-image-686 and
10971 set up grub to boot from the disk image. After this, the KVM machines
10972 seem to work just fine.&lt;/p&gt;
10973 </description>
10974 </item>
10975
10976 <item>
10977 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
10978 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
10979 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
10980 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
10981 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
10982 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10983 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
10984 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
10985
10986 &lt;p&gt;I still do not know what a correct migration should look like, so I
10987 report any differences between apt and aptitude and hope someone else
10988 can see if anything should be changed.&lt;/p&gt;
10989
10990 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10991
10992 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10993
10994 &lt;blockquote&gt;&lt;p&gt;
10995 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10996 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
10997 dmz-cursor-theme empathy empathy-common finger
10998 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10999 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11000 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11001 gnome-cards-data gnome-codec-install gnome-core
11002 gnome-desktop-environment gnome-disk-utility gnome-screenshot
11003 gnome-search-tool gnome-session-canberra gnome-spell
11004 gnome-system-log gnome-themes-extras gnome-themes-more
11005 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
11006 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
11007 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
11008 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
11009 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
11010 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
11011 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
11012 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
11013 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
11014 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
11015 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
11016 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
11017 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
11018 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
11019 libgtk2.0-cil libgtkglext1 libgtksourceview-common
11020 libgtksourceview2.0-common libmono-addins-gui0.2-cil
11021 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
11022 libmono-i18n-west2.0-cil libmono-posix2.0-cil
11023 libmono-security2.0-cil libmono-sharpzip2.84-cil
11024 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
11025 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
11026 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
11027 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
11028 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
11029 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
11030 libxalan2-java libxerces2-java media-player-info mesa-utils
11031 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
11032 nautilus-sendto-empathy openoffice.org-writer2latex
11033 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
11034 python-aptdaemon python-aptdaemon-gtk python-axiom
11035 python-beautifulsoup python-bugbuddy python-clientform
11036 python-coherence python-configobj python-crypto python-cupshelpers
11037 python-cupsutils python-eggtrayicon python-elementtree
11038 python-epsilon python-evolution python-feedparser python-gdata
11039 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11040 python-gtksourceview2 python-httplib2 python-louie python-mako
11041 python-markupsafe python-mechanize python-nevow python-notify
11042 python-opengl python-openssl python-pam python-pkg-resources
11043 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11044 python-tagpy python-twisted-bin python-twisted-conch
11045 python-twisted-core python-twisted-web python-utidylib python-webkit
11046 python-xdg python-zope.interface remmina remmina-plugin-data
11047 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11048 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11049 software-center svgalibg1 system-config-printer-udev
11050 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
11051 totem totem-coherence totem-mozilla totem-plugins
11052 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11053 zip
11054 &lt;/p&gt;&lt;/blockquote&gt;
11055
11056 Installed using apt-get, removed with aptitude
11057
11058 &lt;blockquote&gt;&lt;p&gt;
11059 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11060 epiphany-extensions epiphany-gecko evolution-exchange
11061 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11062 gedit-common gnome-app-install gnome-games gnome-games-data
11063 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11064 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11065 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11066 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
11067 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
11068 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
11069 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
11070 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11071 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11072 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11073 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
11074 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
11075 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11076 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11077 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11078 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11079 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
11080 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
11081 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
11082 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
11083 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
11084 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11085 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11086 sound-juicer swfdec-gnome system-config-printer totem-common
11087 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11088 &lt;/p&gt;&lt;/blockquote&gt;
11089
11090 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11091
11092 &lt;blockquote&gt;&lt;p&gt;
11093 gstreamer0.10-gnomevfs
11094 &lt;/p&gt;&lt;/blockquote&gt;
11095
11096 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11097
11098 &lt;blockquote&gt;&lt;p&gt;
11099 [nothing]
11100 &lt;/p&gt;&lt;/blockquote&gt;
11101
11102 &lt;p&gt;This is for KDE:&lt;/p&gt;
11103
11104 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11105
11106 &lt;blockquote&gt;&lt;p&gt;
11107 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
11108 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11109 ghostscript-x git gnome-audio gnugo granatier gs-common
11110 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11111 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11112 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11113 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11114 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11115 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11116 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11117 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11118 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11119 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11120 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11121 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
11122 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11123 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11124 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11125 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11126 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11127 libkrossui4 libmailtools-perl libmime-tools-perl
11128 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11129 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11130 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11131 lirc luatex marble networkstatus noatun-plugins
11132 openoffice.org-writer2latex palapeli palapeli-data parley
11133 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11134 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11135 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11136 ttf-sazanami-gothic
11137 &lt;/p&gt;&lt;/blockquote&gt;
11138
11139 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11140
11141 &lt;blockquote&gt;&lt;p&gt;
11142 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11143 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11144 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11145 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11146 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11147 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11148 kitchensync kiten kjumpingcube klatin klettres klickety klines
11149 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11150 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11151 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11152 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11153 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11154 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11155 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11156 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11157 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11158 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
11159 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
11160 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11161 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
11162 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
11163 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11164 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11165 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11166 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11167 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11168 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11169 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
11170 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
11171 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11172 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11173 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11174 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11175 &lt;/p&gt;&lt;/blockquote&gt;
11176
11177 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11178
11179 &lt;blockquote&gt;&lt;p&gt;
11180 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11181 kdeartwork kdebase kdebase-apps kdebase-workspace
11182 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11183 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11184 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11185 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11186 xscreensaver-screensaver-bsod
11187 &lt;/p&gt;&lt;/blockquote&gt;
11188
11189 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11190
11191 &lt;blockquote&gt;&lt;p&gt;
11192 kdebase-bin konq-plugins konqueror
11193 &lt;/p&gt;&lt;/blockquote&gt;
11194 </description>
11195 </item>
11196
11197 <item>
11198 <title>Gnash buildbot slave and Debian kfreebsd</title>
11199 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
11200 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
11201 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
11202 <description>&lt;p&gt;Answering
11203 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
11204 call from the Gnash project&lt;/a&gt; for
11205 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
11206 current source, I have set up a virtual KVM machine on the Debian
11207 Edu/Skolelinux virtualization host to test the git source on
11208 Debian/Squeeze. I hope this can help the developers in getting new
11209 releases out more often.&lt;/p&gt;
11210
11211 &lt;p&gt;As the developers want less main-stream build platforms tested to,
11212 I have considered setting up a &lt;a
11213 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
11214 machine as well. I have also considered using the kfreebsd
11215 architecture in Debian as a file server in NUUG to get access to the 5
11216 TB zfs volume we currently use to store DV video. Because of this, I
11217 finally got around to do a test installation of Debian/Squeeze with
11218 kfreebsd. Installation went fairly smooth, thought I noticed some
11219 visual glitches in the cdebconf dialogs (black cursor left on the
11220 screen at random locations). Have not gotten very far with the
11221 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11222 fatal problem. Have to spend some more time on it to see if it is
11223 useful as a file server for NUUG. Will try to find time to set up a
11224 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
11225 </description>
11226 </item>
11227
11228 <item>
11229 <title>Debian in 3D</title>
11230 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
11231 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
11232 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
11233 <description>&lt;p&gt;&lt;img src=&quot;http://thingiverse-production.s3.amazonaws.com/renders/23/e0/c4/f9/2b/debswagtdose_preview_medium.jpg&quot;&gt;&lt;/p&gt;
11234
11235 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
11236 3D linked in from
11237 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
11238 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
11239 </description>
11240 </item>
11241
11242 <item>
11243 <title>Software updates 2010-10-24</title>
11244 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
11245 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
11246 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
11247 <description>&lt;p&gt;Some updates.&lt;/p&gt;
11248
11249 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
11250 raise money for the project is going well. The lower limit of 10
11251 signers was reached in 24 hours, and so far 13 people have signed it.
11252 More signers and more funding is most welcome, and I am really curious
11253 how far we can get before the time limit of December 24 is reached.
11254 :)&lt;/p&gt;
11255
11256 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
11257 about what appear to be a great code coverage tool capable of
11258 generating code coverage stats without any changes to the source code.
11259 It is called
11260 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
11261 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
11262 It is missing in Debian, but the git source built just fine in Squeeze
11263 after I installed libelf-dev, libdwarf-dev, pkg-config and
11264 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11265 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
11266
11267 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
11268 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
11269 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
11270 alpha test release of the Squeeze based Debian Edu /
11271 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
11272 release. Give it a try if you need a complete linux solution for your
11273 school, including central infrastructure server, workstations, thin
11274 client servers and diskless workstations. A nice touch added
11275 yesterday is RDP support on the thin client servers, for windows
11276 clients to get a Linux desktop on request.&lt;/p&gt;
11277 </description>
11278 </item>
11279
11280 <item>
11281 <title>Some notes on Flash in Debian and Debian Edu</title>
11282 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
11283 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
11284 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
11285 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
11286 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
11287 second most popular used package that is missing in Debian. The sixth
11288 most popular is flashplayer-mozilla. This is a clear indication that
11289 working flash is important for Debian users. Around 10 percent of the
11290 users submitting data to popcon.debian.org have this package
11291 installed.&lt;/p&gt;
11292
11293 &lt;p&gt;In the report written by Lars Risan in August 2008
11294&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
11295 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11296 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
11297 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
11298 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
11299 web sites require Flash to work, and lacking working Flash support in
11300 the web browser and the problems with installing it was perceived as a
11301 good reason to stay with Windows.&lt;/p&gt;
11302
11303 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
11304 said to be the retarded cousin that did not really understand
11305 everything you told him but could work fairly well. This was a
11306 comment regarding the problems Linux have with proprietary formats and
11307 non-standard web pages, and is sad because it exposes a fairly common
11308 understanding of whose fault it is if web pages that only work in for
11309 example Internet Explorer 6 fail to work on Firefox, and funny because
11310 it explain very well how annoying it is for users when Linux
11311 distributions do not work with the documents they receive or the web
11312 pages they want to visit.&lt;/p&gt;
11313
11314 &lt;p&gt;This is part of the reason why I believe it is important for Debian
11315 and Debian Edu to have a well working Flash implementation in the
11316 distribution, to get at least popular sites as Youtube and Google
11317 Video to working out of the box. For Squeeze, Debian have the chance
11318 to include the latest version of Gnash that will make this happen, as
11319 the new release 0.8.8 was published a few weeks ago and is resting in
11320 unstable. The new version work with more sites that version 0.8.7.
11321 The Gnash maintainers have asked for a freeze exception, but the
11322 release team have not had time to reply to it yet. I hope they agree
11323 with me that Flash is important for the Debian desktop users, and thus
11324 accept the new package into Squeeze.&lt;/p&gt;
11325 </description>
11326 </item>
11327
11328 <item>
11329 <title>Circular package dependencies harms apt recovery</title>
11330 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
11331 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
11332 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
11333 <description>&lt;p&gt;I discovered this while doing
11334 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
11335 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
11336 in Debian still got circular dependencies, and it is often claimed
11337 that apt and aptitude should be able to handle this just fine, but
11338 some times these dependency loops causes apt to fail.&lt;/p&gt;
11339
11340 &lt;p&gt;An example is from todays
11341 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
11342 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
11343 causes perl-modules to fail to upgrade. The cause is simple. If a
11344 package fail to unpack, then only part of packages with the circular
11345 dependency might end up being unpacked when unpacking aborts, and the
11346 ones already unpacked will fail to configure in the recovery phase
11347 because its dependencies are unavailable.&lt;/p&gt;
11348
11349 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
11350
11351 &lt;blockquote&gt;&lt;pre&gt;
11352 dpkg: dependency problems prevent configuration of perl-modules:
11353 perl-modules depends on perl (&gt;= 5.10.1-1); however:
11354 Version of perl on system is 5.10.0-19lenny2.
11355 dpkg: error processing perl-modules (--configure):
11356 dependency problems - leaving unconfigured
11357 &lt;/pre&gt;&lt;/blockquote&gt;
11358
11359 &lt;p&gt;The perl/perl-modules circular dependency is already
11360 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
11361 hopefully be solved as soon as possible, but it is not the only one,
11362 and each one of these loops in the dependency tree can cause similar
11363 failures. Of course, they only occur when there are bugs in other
11364 packages causing the unpacking to fail, but it is rather nasty when
11365 the failure of one package causes the problem to become worse because
11366 of dependency loops.&lt;/p&gt;
11367
11368 &lt;p&gt;Thanks to
11369 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
11370 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
11371 dependencies
11372 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
11373 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
11374
11375 &lt;p&gt;Todays testing also exposed a bug in
11376 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
11377 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
11378 apt-get and aptitude, the latter possibly caused by some circular
11379 dependency. Reported both to BTS to try to get someone to look at
11380 it.&lt;/p&gt;
11381 </description>
11382 </item>
11383
11384 <item>
11385 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
11386 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
11387 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
11388 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
11389 <description>&lt;p&gt;This is a
11390 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;followup&lt;/a&gt;
11391 on my
11392 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html&quot;&gt;previous
11393 work&lt;/a&gt; on
11394 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
11395 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
11396
11397 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
11398 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11399 and dhcp3-server-ldap in Debian use the LDAP server. The two
11400 implementations are quite different in how they use LDAP.&lt;/p&gt;
11401
11402 To get this information, I started slapd with debugging enabled and
11403 dumped the debug output to a file to get the LDAP searches performed
11404 on a Debian Edu main-server. Here is a summary.
11405
11406 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
11407
11408 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
11409 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
11410 the web.
11411
11412 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
11413 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
11414 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
11415 reverse entries are in two different subtrees in LDAP with a structure
11416 based on the DNS names, as in tjener.intern and
11417 2.2.0.10.in-addr.arpa.&lt;/p&gt;
11418
11419 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
11420 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
11421 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
11422 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
11423 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
11424 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
11425 forward entries, it is looking for attributes named dnsttl, arecord,
11426 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11427 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11428 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11429 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11430 spfrecord and modifytimestamp. For reverse entries it is looking for
11431 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11432 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11433 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11434 ldapsearch commands could look like this:&lt;/p&gt;
11435
11436 &lt;blockquote&gt;&lt;pre&gt;
11437 ldapsearch -h ldap \
11438 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11439 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11440 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11441 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11442 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11443 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11444
11445 ldapsearch -h ldap \
11446 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11447 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
11448 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11449 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11450 srvrecord naptrrecord modifytimestamp
11451 &lt;/pre&gt;&lt;/blockquote&gt;
11452
11453 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
11454 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11455 example LDAP objects used there. In addition to these objects, the
11456 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11457 also exist.&lt;/p&gt;
11458
11459 &lt;blockquote&gt;&lt;pre&gt;
11460 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11461 objectclass: top
11462 objectclass: dnsdomain
11463 objectclass: domainrelatedobject
11464 dc: tjener
11465 arecord: 10.0.2.2
11466 associateddomain: tjener.intern
11467
11468 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11469 objectclass: top
11470 objectclass: dnsdomain2
11471 objectclass: domainrelatedobject
11472 dc: 2
11473 ptrrecord: tjener.intern
11474 associateddomain: 2.2.0.10.in-addr.arpa
11475 &lt;/pre&gt;&lt;/blockquote&gt;
11476
11477 &lt;p&gt;In strict mode, the server behaves differently. When looking for
11478 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
11479 same base as in the tree mode for a object with filter
11480 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
11481 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11482 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11483 naptrrecord and modifytimestamp. For reverse entires it also do a
11484 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
11485 and the requested attributes are associateddomain, dnsttl and
11486 modifytimestamp. In short, in strict mode the objects with ptrrecord
11487 go away, and the arecord attribute in the forward object is used
11488 instead.&lt;/p&gt;
11489
11490 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
11491 like this:&lt;/p&gt;
11492
11493 &lt;blockquote&gt;&lt;pre&gt;
11494 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11495 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11496 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11497 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11498 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11499 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11500
11501 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11502 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
11503 &lt;/pre&gt;&lt;/blockquote&gt;
11504
11505 &lt;p&gt;In addition to the forward and reverse searches , there is also a
11506 search for SOA records, which behave similar to the forward and
11507 reverse lookups.&lt;/p&gt;
11508
11509 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
11510 specify any objectclass names, and instead look for the attributes it
11511 need to generate a DNS reply. This make it able to work with any
11512 objectclass that provide the needed attributes.&lt;/p&gt;
11513
11514 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
11515 dnsdomain2 schemas. The latter is used for reverse entries like
11516 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
11517
11518 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
11519 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11520 attributes) and domainrelatedobject (for associatedDomain). The use
11521 of structural object classes make it impossible to combine these
11522 classes with the object classes used by DHCP.&lt;/p&gt;
11523
11524 &lt;p&gt;There are other schemas that could be used too, for example the
11525 dnszone structural object class used by Gosa and bind-sdb for the DNS
11526 attributes combined with the domainrelatedobject object class, but in
11527 this case some unused attributes would have to be included as well
11528 (zonename and relativedomainname).&lt;/p&gt;
11529
11530 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
11531 mode and not use any of the existing objectclasses (dnsdomain,
11532 dnsdomain2 and dnszone) when one want to combine the DNS information
11533 with DHCP information, and instead create a auxiliary object class
11534 defined something like this (using the attributes defined for
11535 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
11536
11537 &lt;blockquote&gt;&lt;pre&gt;
11538 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
11539 SUP top
11540 AUXILIARY
11541 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11542 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11543 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11544 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11545 A6Record $ DNAMERecord
11546 ))
11547 &lt;/pre&gt;&lt;/blockquote&gt;
11548
11549 &lt;p&gt;This will allow any object to become a DNS entry when combined with
11550 the domainrelatedobject object class, and allow any entity to include
11551 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
11552 developers asking for their view on this schema and if they are
11553 interested in providing such schema with PowerDNS, and I hope my
11554 message will be accepted into their mailing list soon.&lt;/p&gt;
11555
11556 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
11557
11558 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
11559 the object attributes, and then uses the attributes it want. This
11560 make it harder to figure out exactly what attributes are used, but
11561 thanks to the working example in Debian Edu I can at least get an idea
11562 what is needed without having to read the source code.&lt;/p&gt;
11563
11564 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
11565 search filter to use to locate the correct dhcpServer entity is
11566 stored. These are the relevant entries from
11567 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
11568
11569 &lt;blockquote&gt;&lt;pre&gt;
11570 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
11571 ldap-dhcp-server-cn &quot;dhcp&quot;;
11572 &lt;/pre&gt;&lt;/blockquote&gt;
11573
11574 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
11575 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
11576 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
11577 search result is this entry:&lt;/p&gt;
11578
11579 &lt;blockquote&gt;&lt;pre&gt;
11580 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11581 cn: dhcp
11582 objectClass: top
11583 objectClass: dhcpServer
11584 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11585 &lt;/pre&gt;&lt;/blockquote&gt;
11586
11587 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
11588 subtree with DHCP configuration. The DHCP configuration subtree base
11589 is located using a base scope search with base &quot;cn=DHCP
11590 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11591 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11592 The search result is this entry:&lt;/p&gt;
11593
11594 &lt;blockquote&gt;&lt;pre&gt;
11595 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11596 cn: DHCP Config
11597 objectClass: top
11598 objectClass: dhcpService
11599 objectClass: dhcpOptions
11600 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11601 dhcpStatements: ddns-update-style none
11602 dhcpStatements: authoritative
11603 dhcpOption: smtp-server code 69 = array of ip-address
11604 dhcpOption: www-server code 72 = array of ip-address
11605 dhcpOption: wpad-url code 252 = text
11606 &lt;/pre&gt;&lt;/blockquote&gt;
11607
11608 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11609 all the DHCP configuration is loaded, it is ready to receive requests.
11610 The subtree in Debian Edu contain objects with object classes
11611 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11612 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11613 and information about netmasks, dynamic range etc. Leaving out the
11614 details here because it is not relevant for the focus of my
11615 investigation, which is to see if it is possible to merge dns and dhcp
11616 related computer objects.&lt;/p&gt;
11617
11618 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11619 of the client (00:00:00:00:00:00 in this example), using a subtree
11620 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11621 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11622 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11623 like:&lt;/p&gt;
11624
11625 &lt;blockquote&gt;&lt;pre&gt;
11626 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11627 cn: hostname
11628 objectClass: top
11629 objectClass: dhcpHost
11630 dhcpHWAddress: ethernet 00:00:00:00:00:00
11631 dhcpStatements: fixed-address hostname
11632 &lt;/pre&gt;&lt;/blockquote&gt;
11633
11634 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11635 The object classes need to have fixed names, and the configuration
11636 need to be stored in a fairly specific LDAP structure. On the
11637 positive side, the invidiual dhcpHost entires can be anywhere without
11638 the DN pointed to by the dhcpServer entries. The latter should make
11639 it possible to group all host entries in a subtree next to the
11640 configuration entries, and this subtree can also be shared with the
11641 DNS server if the schema proposed above is combined with the dhcpHost
11642 structural object class.
11643
11644 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11645
11646 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11647 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11648 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11649 allowing DNS objects to be stored anywhere under the base cn specified
11650 in the configuration.&lt;/p&gt;
11651
11652 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11653 regarding which LDAP schemas to use and which LDAP structure to use.
11654 I guess one could implement ones own schema, as long as the
11655 objectclasses and attributes have the names used, but this do not
11656 really help when the DHCP subtree need to have a fairly fixed
11657 structure.&lt;/p&gt;
11658
11659 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11660 this might work for Debian Edu:&lt;/p&gt;
11661
11662 &lt;blockquote&gt;&lt;pre&gt;
11663 ou=services
11664 cn=machine-info (dhcpService) - dhcpServiceDN points here
11665 cn=dhcp (dhcpServer)
11666 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11667 cn=10.0.2.0 (dhcpSubnet)
11668 cn=group1 (dhcpGroup/dhcpOptions)
11669 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11670 cn=192.168.0.0 (dhcpSubnet)
11671 cn=group1 (dhcpGroup/dhcpOptions)
11672 ou=machines - PowerDNS base points here
11673 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11674 &lt;/pre&gt;&lt;/blockquote&gt;
11675
11676 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11677 entries to be in the dhcpGroup subtrees, the entries can be stored
11678 there instead of a common machines subtree, and the PowerDNS base
11679 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11680
11681 &lt;p&gt;The combined object under the machines subtree would look something
11682 like this:&lt;/p&gt;
11683
11684 &lt;blockquote&gt;&lt;pre&gt;
11685 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11686 dc: hostname
11687 objectClass: top
11688 objectClass: dhcpHost
11689 objectclass: domainrelatedobject
11690 objectclass: dnsDomainAux
11691 associateddomain: hostname.intern
11692 arecord: 10.11.12.13
11693 dhcpHWAddress: ethernet 00:00:00:00:00:00
11694 dhcpStatements: fixed-address hostname.intern
11695 &lt;/pre&gt;&lt;/blockquote&gt;
11696
11697 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11698 machine, as long as the required attributes are available in a
11699 auxiliary object class.&lt;/p&gt;
11700 </description>
11701 </item>
11702
11703 <item>
11704 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11705 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11706 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11707 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11708 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11709 DHCP services in Debian Edu to use the same LDAP objects for a given
11710 computer, to avoid the possibility of having a inconsistent state for
11711 a computer in LDAP (as in DHCP but no DNS entry or the other way
11712 around) and make it easier to add computers to LDAP.&lt;/p&gt;
11713
11714 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
11715 information finally found a solution that seem to work.&lt;/p&gt;
11716
11717 &lt;p&gt;The old setup required three LDAP objects for a given computer.
11718 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11719 we switch powerdns to use its strict LDAP method (ldap-method=strict
11720 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11721 merged into one while making it impossible to transfer the reverse map
11722 to a slave DNS server.&lt;/p&gt;
11723
11724 &lt;p&gt;If we also replace the object class used to get the DNS related
11725 attributes to one allowing these attributes to be combined with the
11726 dhcphost object class, we can merge the DNS and DHCP entries into one.
11727 I&#39;ve written such object class in the dnsdomainaux.schema file (need
11728 proper OIDs, but that is a minor issue), and tested the setup. It
11729 seem to work.&lt;/p&gt;
11730
11731 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
11732 for both DNS and DHCP, and even the LTSP configuration I suggested in
11733 an earlier email. The combined LDAP object will look something like
11734 this:&lt;/p&gt;
11735
11736 &lt;blockquote&gt;&lt;pre&gt;
11737 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11738 cn: hostname
11739 objectClass: dhcphost
11740 objectclass: domainrelatedobject
11741 objectclass: dnsdomainaux
11742 associateddomain: hostname.intern
11743 arecord: 10.11.12.13
11744 dhcphwaddress: ethernet 00:00:00:00:00:00
11745 dhcpstatements: fixed-address hostname
11746 ldapconfigsound: Y
11747 &lt;/pre&gt;&lt;/blockquote&gt;
11748
11749 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
11750 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11751 before asking DNS to resolve the fixed-adddress. LTSP will use
11752 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
11753
11754 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
11755 dhcphost in a different location, to allow us to put the objects
11756 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
11757 that. If I can&#39;t figure out a way to do that, we can still get rid of
11758 the hosts subtree and move all its content into the DHCP Config tree
11759 (which probably should be renamed to be more related to the new
11760 content. I suspect cn=dnsdhcp,ou=services or something like that
11761 might be a good place to put it.&lt;/p&gt;
11762
11763 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11764 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11765 </description>
11766 </item>
11767
11768 <item>
11769 <title>Idea for storing LTSP configuration in LDAP</title>
11770 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
11771 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
11772 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
11773 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
11774 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11775 clients, and that this can be used to fetch configuration from LDAP if
11776 Debian Edu choose to store configuration there.&lt;/p&gt;
11777
11778 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
11779 to get configuration from LDAP. The idea is to look up the MAC
11780 address of the client in LDAP, and look for attributes on the form
11781 ltspconfigsetting=value, and use this to export SETTING=value to the
11782 LTSP clients.&lt;/p&gt;
11783
11784 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
11785 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
11786 allowing us to store all information about a computer in one place.&lt;/p&gt;
11787
11788 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
11789 this approach. A real LDAP schema for the ltspClientAux objectclass
11790 need to be written. Comments, suggestions, etc?&lt;/p&gt;
11791
11792 &lt;blockquote&gt;&lt;pre&gt;
11793 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11794 #
11795 # Fetch LTSP client settings from LDAP based on MAC address
11796 #
11797 # Uses ethernet address as stored in the dhcpHost objectclass using
11798 # the dhcpHWAddress attribute or ethernet address stored in the
11799 # ieee802Device objectclass with the macAddress attribute.
11800 #
11801 # This module is written to be schema agnostic, and only depend on the
11802 # existence of attribute names.
11803 #
11804 # The LTSP configuration variables are saved directly using a
11805 # ltspConfig prefix and uppercasing the rest of the attribute name.
11806 # To set the SERVER variable, set the ltspConfigServer attribute.
11807 #
11808 # Some LDAP schema should be created with all the relevant
11809 # configuration settings. Something like this should work:
11810 #
11811 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
11812 # SUP top
11813 # AUXILIARY
11814 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11815
11816 LDAPSERVER=$(debian-edu-ldapserver)
11817 if [ &quot;$LDAPSERVER&quot; ] ; then
11818 LDAPBASE=$(debian-edu-ldapserver -b)
11819 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
11820 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
11821 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
11822 grep &#39;^ltspConfig&#39; | while read attr value ; do
11823 # Remove prefix and convert to upper case
11824 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
11825 # bass value on to clients
11826 eval &quot;$attr=$value; export $attr&quot;
11827 done
11828 done
11829 fi
11830 &lt;/pre&gt;&lt;/blockquote&gt;
11831
11832 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
11833 the while block might end up in a subshell causing the variables set
11834 there to not show up in ltsp-config, but if that is the case I am sure
11835 the code can be restructured to make sure the variables are passed on.
11836 I expect that can be solved with some testing. :)&lt;/p&gt;
11837
11838 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11839 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11840
11841 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
11842 configuration in LDAP that was created around year 2000 by
11843 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
11844 Xperience, Inc., 2000&lt;/a&gt;. I found its
11845 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
11846 personal home page over at redhat.com.&lt;/p&gt;
11847 </description>
11848 </item>
11849
11850 <item>
11851 <title>jXplorer, a very nice LDAP GUI</title>
11852 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
11853 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
11854 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
11855 <description>&lt;p&gt;Since
11856 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
11857 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
11858 LDAP GUI that is even better than luma. The java application
11859 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
11860 moving LDAP objects and subtrees using drag-and-drop, and can
11861 authenticate using Kerberos. I have only tested the Kerberos
11862 authentication, but do not have a LDAP setup allowing me to rewrite
11863 LDAP with my test user yet. It is
11864 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
11865 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
11866 have with it is how it handle errors. If something go wrong, its
11867 non-intuitive behaviour require me to go through some query work list
11868 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
11869 </description>
11870 </item>
11871
11872 <item>
11873 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
11874 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
11875 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
11876 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
11877 <description>&lt;p&gt;Here is a short update on my &lt;a
11878 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
11879 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
11880 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
11881 not reporting the status for KDE, because the upgrade crashes when
11882 aptitude try because of missing conflicts
11883 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
11884 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
11885
11886 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
11887 complete list of the installed packages. Based on this I see these
11888 differences when I did a test run today. As usual, I do not really
11889 know what the correct set of packages would be, but thought it best to
11890 publish the difference.&lt;/p&gt;
11891
11892 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11893
11894 &lt;blockquote&gt;&lt;p&gt;
11895 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
11896 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
11897 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11898 libgtksourceview-common libpt-1.10.10-plugins-alsa
11899 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11900 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11901 python-4suite-xml python-eggtrayicon python-gtkhtml2
11902 python-gtkmozembed svgalibg1 xserver-xephyr zip
11903 &lt;/p&gt;&lt;/blockquote&gt;
11904
11905 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11906
11907 &lt;blockquote&gt;&lt;p&gt;
11908 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11909 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11910 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
11911 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
11912 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
11913 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
11914 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11915 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11916 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11917 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
11918 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
11919 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
11920 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11921 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
11922 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11923 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
11924 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
11925 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11926 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11927 mysql-common swfdec-gnome totem-gstreamer wodim
11928 &lt;/p&gt;&lt;/blockquote&gt;
11929
11930 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11931
11932 &lt;blockquote&gt;&lt;p&gt;
11933 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11934 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11935 xserver-xorg-input-all xserver-xorg-input-evdev
11936 xserver-xorg-input-kbd xserver-xorg-input-mouse
11937 xserver-xorg-input-synaptics xserver-xorg-video-all
11938 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11939 xserver-xorg-video-chips xserver-xorg-video-cirrus
11940 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11941 xserver-xorg-video-glint xserver-xorg-video-i128
11942 xserver-xorg-video-i740 xserver-xorg-video-mach64
11943 xserver-xorg-video-mga xserver-xorg-video-neomagic
11944 xserver-xorg-video-nouveau xserver-xorg-video-nv
11945 xserver-xorg-video-r128 xserver-xorg-video-radeon
11946 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11947 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11948 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11949 xserver-xorg-video-sis xserver-xorg-video-sisusb
11950 xserver-xorg-video-tdfx xserver-xorg-video-tga
11951 xserver-xorg-video-trident xserver-xorg-video-tseng
11952 xserver-xorg-video-vesa xserver-xorg-video-vmware
11953 xserver-xorg-video-voodoo
11954 &lt;/p&gt;&lt;/blockquote&gt;
11955
11956 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11957
11958 &lt;blockquote&gt;&lt;p&gt;
11959 deskbar-applet xserver-xorg xserver-xorg-core
11960 xserver-xorg-input-wacom xserver-xorg-video-intel
11961 xserver-xorg-video-openchrome
11962 &lt;/p&gt;&lt;/blockquote&gt;
11963
11964 &lt;p&gt;I was told on IRC that the xorg-xserver package was
11965 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
11966 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
11967 No idea when it hits Squeeze, but when it does I hope it will reduce
11968 the difference somewhat.
11969 </description>
11970 </item>
11971
11972 <item>
11973 <title>LUMA, a very nice LDAP GUI</title>
11974 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
11975 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
11976 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
11977 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
11978 directory in Debian Edu, and in the process I started to miss a GUI
11979 tool to browse the LDAP tree. The only one I was able to find in
11980 Debian/Squeeze and Lenny is
11981 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
11982 be a great tool to get a overview of the current LDAP directory
11983 populated by default in Skolelinux. Thanks to it, I have been able to
11984 find empty and obsolete subtrees, misplaced objects and duplicate
11985 objects. It will be installed by default in Debian/Squeeze. If you
11986 are working with LDAP, give it a go. :)&lt;/p&gt;
11987
11988 &lt;p&gt;I did notice one problem with it I have not had time to report to
11989 the BTS yet. There is no .desktop file in the package, so the tool do
11990 not show up in the Gnome and KDE menus, but only deep down in in the
11991 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11992 released.&lt;/p&gt;
11993
11994 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
11995 like to move objects and remove subtrees directly in the GUI, but have
11996 not found a way to do that with LUMA yet. So in the mean time, I use
11997 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
11998
11999 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
12000 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12001
12002 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
12003 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
12004 useful GUI alternative. It seem like a good tool, but is unmaintained
12005 in Debian and got a RC bug keeping it out of Squeeze. Unless that
12006 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
12007 </description>
12008 </item>
12009
12010 <item>
12011 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
12012 <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>
12013 <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>
12014 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
12015 <description>&lt;p&gt;A while back, I
12016 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
12017 about the fact&lt;/a&gt; that it is not possible with the provided schemas
12018 for storing DNS and DHCP information in LDAP to combine the two sets
12019 of information into one LDAP object representing a computer.&lt;/p&gt;
12020
12021 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
12022 the dhcpHost object class auxiliary, to allow it to be combined with
12023 the dNSDomain object class, and thus forming one object for one
12024 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
12025
12026 &lt;p&gt;If I understand this correctly, it is not safe to do this change
12027 without also changing the assigned number for the object class, and I
12028 do not know enough about LDAP schema design to do that properly for
12029 Debian Edu.&lt;/p&gt;
12030
12031 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
12032 the
12033 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
12034 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
12035 available today from IETF.&lt;/p&gt;
12036
12037 &lt;pre&gt;
12038 --- dhcp.schema (revision 65192)
12039 +++ dhcp.schema (working copy)
12040 @@ -376,7 +376,7 @@
12041 objectclass ( 2.16.840.1.113719.1.203.6.6
12042 NAME &#39;dhcpHost&#39;
12043 DESC &#39;This represents information about a particular client&#39;
12044 - SUP top
12045 + SUP top AUXILIARY
12046 MUST cn
12047 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12048 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
12049 &lt;/pre&gt;
12050
12051 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
12052 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12053 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
12054
12055 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12056 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12057 </description>
12058 </item>
12059
12060 <item>
12061 <title>Calling tasksel like the installer, while still getting useful output</title>
12062 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
12063 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
12064 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
12065 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
12066 installs packages during the normal debian-installer run. Until now,
12067 I have ended up letting tasksel do the work, with the annoying problem
12068 of not getting any feedback at all when something fails (like a
12069 conffile question from dpkg or a download that fails), using code like
12070 this:
12071
12072 &lt;blockquote&gt;&lt;pre&gt;
12073 export DEBIAN_FRONTEND=noninteractive
12074 tasksel --new-install
12075 &lt;/pre&gt;&lt;/blockquote&gt;
12076
12077 This would invoke tasksel, let its automatic task selection pick the
12078 tasks to install, and continue to install the requested tasks without
12079 any output what so ever.
12080
12081 Recently I revisited this problem while working on the automatic
12082 package upgrade testing, because tasksel would some times hang without
12083 any useful feedback, and I want to see what is going on when it
12084 happen. Then it occured to me, I can parse the output from tasksel
12085 when asked to run in test mode, and use that aptitude command line
12086 printed by tasksel then to simulate the tasksel run. I ended up using
12087 code like this:
12088
12089 &lt;blockquote&gt;&lt;pre&gt;
12090 export DEBIAN_FRONTEND=noninteractive
12091 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
12092 $cmd
12093 &lt;/pre&gt;&lt;/blockquote&gt;
12094
12095 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
12096 --without-recommends -o APT::Install-Recommends=no -y install
12097 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12098 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
12099 laptop task and all packages with priority standard , required and
12100 important, just like tasksel would have done it during
12101 installation.&lt;/p&gt;
12102
12103 &lt;p&gt;A better approach is probably to extend tasksel to be able to
12104 install packages without using debconf-apt-progress, for use cases
12105 like this.&lt;/p&gt;
12106 </description>
12107 </item>
12108
12109 <item>
12110 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
12111 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
12112 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
12113 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
12114 <description>&lt;p&gt;My
12115 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
12116 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
12117 finally made the upgrade logs available from
12118 &lt;a href=&quot;http://people.skolelinux.org/pere/debian-upgrade-testing/&quot;&gt;http://people.skolelinux.org/pere/debian-upgrade-testing/&lt;/a&gt;.
12119 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12120 apt and aptitude, and found their differences interesting. This time
12121 I will only focus on their removal plans.&lt;/p&gt;
12122
12123 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
12124 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
12125 surprising part is that it want to remove xorg and all
12126 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12127 sure why. When asking aptitude to do the same, it want to remove 129
12128 packages, but most of them are library packages I suspect are no
12129 longer needed. Both of them want to remove bluetooth packages, which
12130 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
12131
12132 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
12133 which seem like a bad idea and xorg the same way as with Gnome. Asking
12134 aptitude for the same, it wants to remove 192 packages, none which are
12135 too surprising.&lt;/p&gt;
12136
12137 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
12138 and avoided, and perhaps others as well. Here are the complete list
12139 of planned removals. The complete logs is available from the URL
12140 above. Note if you want to repeat these tests, that the upgrade test
12141 for kde+apt-get hung in the tasksel setup because of dpkg asking
12142 conffile questions. No idea why. I worked around it by using
12143 &#39;&lt;tt&gt;echo &gt;&gt; /proc/&lt;em&gt;pidofdpkg&lt;/em&gt;/fd/0&lt;/tt&gt;&#39; to tell dpkg to
12144 continue.&lt;/p&gt;
12145
12146 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
12147 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
12148 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12149 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
12150 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12151 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12152 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12153 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12154 xserver-xorg-input-kbd xserver-xorg-input-mouse
12155 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12156 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12157 xserver-xorg-video-ati xserver-xorg-video-chips
12158 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12159 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12160 xserver-xorg-video-glint xserver-xorg-video-i128
12161 xserver-xorg-video-i740 xserver-xorg-video-imstt
12162 xserver-xorg-video-intel xserver-xorg-video-mach64
12163 xserver-xorg-video-mga xserver-xorg-video-neomagic
12164 xserver-xorg-video-nsc xserver-xorg-video-nv
12165 xserver-xorg-video-openchrome xserver-xorg-video-r128
12166 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12167 xserver-xorg-video-rendition xserver-xorg-video-s3
12168 xserver-xorg-video-s3virge xserver-xorg-video-savage
12169 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12170 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12171 xserver-xorg-video-tga xserver-xorg-video-trident
12172 xserver-xorg-video-tseng xserver-xorg-video-v4l
12173 xserver-xorg-video-vesa xserver-xorg-video-vga
12174 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
12175 xulrunner-1.9-gnome-support&lt;/p&gt;
12176
12177 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
12178
12179 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
12180 djvulibre-desktop finger gnome-app-install gnome-mount
12181 gnome-network-admin gnome-spell gnome-vfs-obexftp
12182 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12183 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12184 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12185 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
12186 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
12187 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
12188 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
12189 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
12190 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
12191 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
12192 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
12193 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
12194 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12195 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
12196 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
12197 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
12198 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
12199 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
12200 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12201 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12202 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12203 openoffice.org-writer2latex openssl-blacklist p7zip
12204 python-4suite-xml python-eggtrayicon python-gnome2-desktop
12205 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12206 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12207 swfdec-mozilla totem-gstreamer update-manager wodim
12208 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12209 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12210 zip&lt;/p&gt;
12211
12212 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
12213
12214 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12215 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12216 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12217 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12218 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12219 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12220 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12221 xserver-xorg-input-kbd xserver-xorg-input-mouse
12222 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12223 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12224 xserver-xorg-video-ati xserver-xorg-video-chips
12225 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12226 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12227 xserver-xorg-video-glint xserver-xorg-video-i128
12228 xserver-xorg-video-i740 xserver-xorg-video-imstt
12229 xserver-xorg-video-intel xserver-xorg-video-mach64
12230 xserver-xorg-video-mga xserver-xorg-video-neomagic
12231 xserver-xorg-video-nsc xserver-xorg-video-nv
12232 xserver-xorg-video-openchrome xserver-xorg-video-r128
12233 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12234 xserver-xorg-video-rendition xserver-xorg-video-s3
12235 xserver-xorg-video-s3virge xserver-xorg-video-savage
12236 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12237 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12238 xserver-xorg-video-tga xserver-xorg-video-trident
12239 xserver-xorg-video-tseng xserver-xorg-video-v4l
12240 xserver-xorg-video-vesa xserver-xorg-video-vga
12241 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
12242
12243 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
12244 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
12245 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12246 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12247 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12248 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12249 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12250 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12251 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12252 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12253 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12254 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12255 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12256 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12257 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12258 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12259 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12260 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12261 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12262 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
12263 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12264 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12265 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
12266 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12267 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12268 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12269 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12270 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12271 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
12272 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
12273 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12274 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12275 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12276 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12277 texlive-common texlive-doc-base texlive-fonts-recommended
12278 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12279 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12280 xulrunner-1.9&lt;/p&gt;
12281
12282 </description>
12283 </item>
12284
12285 <item>
12286 <title>Automatic upgrade testing from Lenny to Squeeze</title>
12287 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
12288 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
12289 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
12290 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
12291 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12292 have been discovered and reported in the process
12293 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
12294 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
12295 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
12296 kdebase-workspace-data), and to get a more regular testing going on, I
12297 am working on a script to automate the test.&lt;/p&gt;
12298
12299 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
12300 Gnome or KDE desktop installation inside the chroot before upgrading
12301 it. To ensure no services are started in the chroot, a policy-rc.d
12302 script is inserted. To make sure tasksel believe it is to install a
12303 desktop on a laptop, the tasksel tests are replaced in the chroot
12304 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
12305
12306 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12307 currently always fail because udev refuses to upgrade with the kernel
12308 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12309 is created. The bug report
12310 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
12311 this problem do not trigger in a chroot, but I touch the file anyway
12312 to make sure the upgrade go well. Testing on virtual and real
12313 hardware have failed me because of udev so far, and creating this file
12314 do the trick in such settings anyway. This is a
12315 &lt;a href=&quot;http://www.linuxquestions.org/questions/debian-26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-804130/&quot;&gt;known
12316 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
12317 maintainer because he lack the resources to rewrite udev to keep
12318 working with old kernels or something like that. I really wish the
12319 udev upstream would keep udev backwards compatible, to avoid such
12320 upgrade problem, but given that they fail to do so, I guess
12321 documenting the way out of this mess is the best option we got for
12322 Debian Squeeze.&lt;/p&gt;
12323
12324 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
12325 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
12326 trick:&lt;/p&gt;
12327
12328 &lt;blockquote&gt;&lt;pre&gt;
12329 #!/bin/sh
12330 set -ex
12331
12332 if [ &quot;$1&quot; ] ; then
12333 desktop=$1
12334 else
12335 desktop=gnome
12336 fi
12337
12338 from=lenny
12339 to=squeeze
12340
12341 exec &amp;lt; /dev/null
12342 unset LANG
12343 mirror=http://ftp.skolelinux.org/debian
12344 tmpdir=chroot-$from-upgrade-$to-$desktop
12345 fuser -mv .
12346 debootstrap $from $tmpdir $mirror
12347 chroot $tmpdir aptitude update
12348 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
12349 #!/bin/sh
12350 exit 101
12351 EOF
12352 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12353 exit_cleanup() {
12354 umount $tmpdir/proc
12355 }
12356 mount -t proc proc $tmpdir/proc
12357 # Make sure proc is unmounted also on failure
12358 trap exit_cleanup EXIT INT
12359
12360 chroot $tmpdir aptitude -y install debconf-utils
12361
12362 # Make sure tasksel autoselection trigger. It need the test scripts
12363 # to return the correct answers.
12364 echo tasksel tasksel/desktop multiselect $desktop | \
12365 chroot $tmpdir debconf-set-selections
12366
12367 # Include the desktop and laptop task
12368 for test in desktop laptop ; do
12369 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
12370 #!/bin/sh
12371 exit 2
12372 EOF
12373 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12374 done
12375
12376 DEBIAN_FRONTEND=noninteractive
12377 DEBIAN_PRIORITY=critical
12378 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12379 chroot $tmpdir tasksel --new-install
12380
12381 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
12382 chroot $tmpdir aptitude update
12383 touch $tmpdir/etc/udev/kernel-upgrade
12384 chroot $tmpdir aptitude -y dist-upgrade
12385 fuser -mv
12386 &lt;/pre&gt;&lt;/blockquote&gt;
12387
12388 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
12389 with aptitude, but I have not had time to look at how they behave
12390 differently so far. I hope to get a cron job running to do the test
12391 regularly and post the result on the web. The Gnome upgrade currently
12392 work, while the KDE upgrade fail because of the bug in
12393 kdebase-workspace-data&lt;/p&gt;
12394
12395 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
12396 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
12397 post, so I will refrain from trying. I can report that for Gnome,
12398 aptitude report 760 packages upgraded, 448 newly installed, 129 to
12399 remove and 1 not upgraded and 1024MB need to be downloaded while for
12400 KDE the same numbers are 702 packages upgraded, 507 newly installed,
12401 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
12402
12403 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
12404 is able to migrate to dependency based boot sequencing and parallel
12405 booting without a hitch. Was unsure if there were still bugs with
12406 packages failing to clean up their obsolete init.d script during
12407 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12408 packages.&lt;/p&gt;
12409 </description>
12410 </item>
12411
12412 <item>
12413 <title>Upstart or sysvinit - as init.d scripts see it</title>
12414 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
12415 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
12416 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
12417 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
12418 scripts to migrate (some of) their operations to upstart job while
12419 keeping the init.d for hurd and kfreebsd. The packages with such
12420 needs will need a way to get their init.d scripts to behave
12421 differently when used with sysvinit and with upstart. Because of
12422 this, I had a look at the environment variables set when a init.d
12423 script is running under upstart, and when it is not.&lt;/p&gt;
12424
12425 &lt;p&gt;With upstart, I notice these environment variables are set when a
12426 script is started from rcS.d/ (ignoring some irrelevant ones like
12427 COLUMNS):&lt;/p&gt;
12428
12429 &lt;blockquote&gt;&lt;pre&gt;
12430 DEFAULT_RUNLEVEL=2
12431 previous=N
12432 PREVLEVEL=
12433 RUNLEVEL=
12434 runlevel=S
12435 UPSTART_EVENTS=startup
12436 UPSTART_INSTANCE=
12437 UPSTART_JOB=rc-sysinit
12438 &lt;/pre&gt;&lt;/blockquote&gt;
12439
12440 &lt;p&gt;With sysvinit, these environment variables are set for the same
12441 script.&lt;/p&gt;
12442
12443 &lt;blockquote&gt;&lt;pre&gt;
12444 INIT_VERSION=sysvinit-2.88
12445 previous=N
12446 PREVLEVEL=N
12447 RUNLEVEL=S
12448 runlevel=S
12449 &lt;/pre&gt;&lt;/blockquote&gt;
12450
12451 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
12452 sysvinit are not set by upstart. Not sure if it is intentional or not
12453 to not be compatible with sysvinit in this regard.&lt;/p&gt;
12454
12455 &lt;p&gt;For scripts needing to behave differently when upstart is used,
12456 looking for the UPSTART_JOB environment variable seem to be a good
12457 choice.&lt;/p&gt;
12458 </description>
12459 </item>
12460
12461 <item>
12462 <title>A manual for standards wars...</title>
12463 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
12464 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
12465 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
12466 <description>&lt;p&gt;Via the
12467 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
12468 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
12469 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
12470 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
12471 following the standards wars of today.&lt;/p&gt;
12472 </description>
12473 </item>
12474
12475 <item>
12476 <title>Sitesummary tip: Listing computer hardware models used at site</title>
12477 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
12478 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
12479 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
12480 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
12481 to get a list of the machine types in use thanks to the DMI
12482 information extracted from each machine. The script to do so is
12483 included in the sitesummary package, and here is example output from
12484 the Skolelinux build servers:&lt;/p&gt;
12485
12486 &lt;blockquote&gt;&lt;pre&gt;
12487 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12488 vendor count
12489 Dell Computer Corporation 1
12490 PowerEdge 1750 1
12491 IBM 1
12492 eserver xSeries 345 -[8670M1X]- 1
12493 Intel 2
12494 [no-dmi-info] 3
12495 maintainer:~#
12496 &lt;/pre&gt;&lt;/blockquote&gt;
12497
12498 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
12499 provided in each machine. Here there are Intel machines without model
12500 information listed with Intel as vendor and no model, and virtual Xen
12501 machines listed as [no-dmi-info]. One can add -l as a command line
12502 option to list the individual machines.&lt;/p&gt;
12503
12504 &lt;p&gt;A larger list is
12505 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
12506 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
12507 provide the basic sitesummary report publicly. In their report there
12508 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
12509 their machines, and as sitesummary is available in both distributions,
12510 it is trivial to get all of them to report to the same central
12511 collector.&lt;/p&gt;
12512 </description>
12513 </item>
12514
12515 <item>
12516 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
12517 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
12518 <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>
12519 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
12520 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
12521 start at boot when an NVidia video card is used is handled. The
12522 problem seem to be that the nvidia X.org driver uses a long time to
12523 initialize, and this duration is longer than kdm is configured to
12524 wait.&lt;/p&gt;
12525
12526 &lt;p&gt;I came across two bugs related to this issue,
12527 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
12528 against initscripts and passed on to nvidia-glx when it became obvious
12529 that the nvidia drivers were involved, and
12530 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
12531 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
12532
12533 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
12534 problem nvidia video card owners experience and make sure the Debian
12535 distribution work out of the box for these users. The nvidia driver
12536 maintainers expect kdm to be set up to wait longer, while kdm expect
12537 the nvidia driver maintainers to fix the driver to start faster, and
12538 while they wait for each other I guess the users end up switching to a
12539 distribution that work for them. I have no idea what the solution is,
12540 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
12541
12542 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
12543 </description>
12544 </item>
12545
12546 <item>
12547 <title>Parallellized boot seem to hold up well in Debian/testing</title>
12548 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
12549 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
12550 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
12551 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
12552 The feature seem to hold up pretty well, but three fairly serious
12553 issues are known and should be solved:
12554
12555 &lt;p&gt;&lt;ul&gt;
12556
12557 &lt;li&gt;The wicd package seen to
12558 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
12559 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
12560 parallel booting is enabled. No idea why, but the wicd maintainer
12561 seem to be on the case.&lt;/li&gt;
12562
12563 &lt;li&gt;The nvidia X driver seem to
12564 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
12565 triggered more easily when parallel booting is in effect. The
12566 maintainer is on the case.&lt;/li&gt;
12567
12568 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
12569 sequencing (the shutdown is broken) when old file-rc users
12570 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
12571 sysv-rc. One way to solve it would be for file-rc to create
12572 /etc/init.d/.legacy-bootordering, and another is to try to make
12573 sysv-rc more robust. Will investigate some more and probably upload a
12574 workaround in sysv-rc to help those trying to move from file-rc to
12575 sysv-rc get a working shutdown.&lt;/li&gt;
12576
12577 &lt;/ul&gt;&lt;/p&gt;
12578
12579 &lt;p&gt;All in all not many surprising issues, and all of them seem
12580 solvable before Squeeze is released. In addition to these there are
12581 some packages with bugs in their dependencies and run level settings,
12582 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
12583
12584 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12585 the BTS, please usertag the report to get it to show up at
12586 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12587 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12588
12589 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12590 </description>
12591 </item>
12592
12593 <item>
12594 <title>More flexible firmware handling in debian-installer</title>
12595 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12596 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12597 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12598 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12599 found time today to return to the project. Having to spend less time
12600 working dependency based boot in debian, as it is almost complete now,
12601 definitely helped freeing some time.&lt;/p&gt;
12602
12603 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12604 include some firmware packages on the Debian Edu CDs, those needed to
12605 get disk and network controllers working. Without having these
12606 firmware packages available during installation, it is impossible to
12607 install Debian Edu on the given machine, and because our target group
12608 are non-technical people, asking them to provide firmware packages on
12609 an external medium is a support pain. Initially, I expected it to be
12610 enough to include the firmware packages on the CD to get
12611 debian-installer to find and use them. This proved to be wrong.
12612 Next, I hoped it was enough to symlink the relevant firmware packages
12613 to some useful location on the CD (tried /cdrom/ and
12614 /cdrom/firmware/). This also proved to not work, and at this point I
12615 found time to look at the debian-installer code to figure out what was
12616 going to work.&lt;/p&gt;
12617
12618 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12619 look revealed that it would only look for firmware packages outside
12620 the installation media, so the CD was never checked for firmware
12621 packages. It would only check USB sticks, floppies and other
12622 &quot;external&quot; media devices. Today I changed it to also look in the
12623 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12624 solve the problem I ran into with Debian edu. I also changed it to
12625 look in /firmware/, to make sure the installer also find firmware
12626 provided in the initrd when booting the installer via PXE, to allow us
12627 to provide the same feature in the PXE setup included in Debian
12628 Edu.&lt;/p&gt;
12629
12630 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12631 activated without asking if the license is accepted, I extended
12632 hw-detect to look for preinst scripts in the firmware packages, and
12633 run these before activating the firmware during installation. The
12634 license question is asked using debconf in the preinst, so this should
12635 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12636
12637 &lt;p&gt;If you want to discuss the details of these features, please
12638 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12639 </description>
12640 </item>
12641
12642 <item>
12643 <title>Parallellized boot is now the default in Debian/unstable</title>
12644 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12645 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12646 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12647 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12648 Debian/unstable for machines using dependency based boot sequencing.
12649 Apparently the testing of concurrent booting has been wider than
12650 expected, if I am to believe the
12651 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12652 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12653 with the feature this weekend, to give us some time to detect any
12654 remaining problems before Squeeze is frozen. If serious problems are
12655 detected, it is simple to change the default back to sequential boot.
12656 The upload of the new sysvinit package also activate a new upstream
12657 version.&lt;/p&gt;
12658
12659 More information about
12660 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12661 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12662 currently possible to disable parallel booting when one run into
12663 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12664
12665 &lt;blockquote&gt;&lt;pre&gt;
12666 CONCURRENCY=none
12667 &lt;/pre&gt;&lt;/blockquote&gt;
12668
12669 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12670 the BTS, please usertag the report to get it to show up at
12671 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12672 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12673 </description>
12674 </item>
12675
12676 <item>
12677 <title>Sitesummary tip: Listing MAC address of all clients</title>
12678 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12679 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12680 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12681 <description>&lt;p&gt;In the recent Debian Edu versions, the
12682 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12683 system&lt;/a&gt; is used to keep track of the machines in the school
12684 network. Each machine will automatically report its status to the
12685 central server after boot and once per night. The network setup is
12686 also reported, and using this information it is possible to get the
12687 MAC address of all network interfaces in the machines. This is useful
12688 to update the DHCP configuration.&lt;/p&gt;
12689
12690 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12691 ist all MAC addresses of all machines reporting to sitesummary. Run
12692 this on the collector host:&lt;/p&gt;
12693
12694 &lt;blockquote&gt;&lt;pre&gt;
12695 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12696 &lt;/pre&gt;&lt;/blockquote&gt;
12697
12698 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12699 line per machine and with space between the MAC addresses.&lt;/p&gt;
12700
12701 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12702 addresses for hosts, it would be possible to extend this to fetch
12703 machine information from sitesummary and update the DHCP and DNS
12704 tables in LDAP using this information. Such tool is unfortunately not
12705 written yet.&lt;/p&gt;
12706 </description>
12707 </item>
12708
12709 <item>
12710 <title>systemd, an interesting alternative to upstart</title>
12711 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
12712 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
12713 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
12714 <description>&lt;p&gt;The last few days a new boot system called
12715 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
12716 has been
12717 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
12718
12719 to the free software world. I have not yet had time to play around
12720 with it, but it seem to be a very interesting alternative to
12721 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
12722 a good alternative for Debian when we are able to switch to an event
12723 based boot system. Tollef is
12724 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
12725 systemd into Debian, and I look forward to seeing how well it work. I
12726 like the fact that systemd handles init.d scripts with dependency
12727 information natively, allowing them to run in parallel where upstart
12728 at the moment do not.&lt;/p&gt;
12729
12730 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
12731 platform support. It only work on recent Linux kernels, and also need
12732 some new kernel features enabled to function properly. This means
12733 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12734 system. Not sure how that will be handled if systemd proves to be the
12735 way forward.&lt;/p&gt;
12736
12737 &lt;p&gt;In the mean time, based on the
12738 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12739 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
12740 decided to enable full parallel booting as the default in Debian as
12741 soon as possible (probably this weekend or early next week), to see if
12742 there are any remaining serious bugs in the init.d dependencies. A
12743 new version of the sysvinit package implementing this change is
12744 already in experimental. If all go well, Squeeze will be released
12745 with parallel booting enabled by default.&lt;/p&gt;
12746 </description>
12747 </item>
12748
12749 <item>
12750 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
12751 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
12752 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
12753 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
12754 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
12755 complete, so complete that it is actually possible to run all the
12756 init.d scripts in parallell based on these dependencies. If you want
12757 to test your Squeeze system, make sure
12758 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12759 based boot sequencing&lt;/a&gt; is enabled, and add this line to
12760 /etc/default/rcS:&lt;/p&gt;
12761
12762 &lt;blockquote&gt;&lt;pre&gt;
12763 CONCURRENCY=makefile
12764 &lt;/pre&gt;&lt;/blockquote&gt;
12765
12766 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
12767 scripts in parallel using the dependency information stored in
12768 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12769 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12770 to try to start the kdm and gdm scripts as early as possible, and will
12771 start the facilities required by kdm or gdm as early as possible to
12772 make this happen.&lt;/p&gt;
12773
12774 &lt;p&gt;Give it a try, and see if you like the result. If some services
12775 fail to start properly, it is most likely because they have incomplete
12776 init.d script dependencies in their startup script (or some of their
12777 dependent scripts have incomplete dependencies). Report bugs and get
12778 the package maintainers to fix it. :)&lt;/p&gt;
12779
12780 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
12781 manage to get the init.d script dependencies complete and correct. I
12782 expect we will get there in Squeeze+1, if we get manage to test and
12783 fix the remaining issues.&lt;/p&gt;
12784
12785 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12786 the BTS, please usertag the report to get it to show up at
12787 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12788 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12789 </description>
12790 </item>
12791
12792 <item>
12793 <title>Debian has switched to dependency based boot sequencing</title>
12794 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
12795 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
12796 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
12797 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
12798 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
12799 have been migrated to using dependency based boot sequencing. This
12800 conclude work me and others have been doing for the last three days.
12801 It feels great to see this finally part of the default Debian
12802 installation. Now we just need to weed out the last few problems that
12803 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
12804
12805 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
12806 fixing the more fundamental problem of handing the event based
12807 non-predictable kernel in the early boot.&lt;/p&gt;
12808 </description>
12809 </item>
12810
12811 <item>
12812 <title>Taking over sysvinit development</title>
12813 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
12814 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
12815 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
12816 <description>&lt;p&gt;After several years of frustration with the lack of activity from
12817 the existing sysvinit upstream developer, I decided a few weeks ago to
12818 take over the package and become the new upstream. The number of
12819 patches to track for the Debian package was becoming a burden, and the
12820 lack of synchronization between the distribution made it hard to keep
12821 the package up to date.&lt;/p&gt;
12822
12823 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12824 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
12825 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
12826 and Fedora), based on the patches currently in use in these
12827 distributions. We Debian maintainers plan to move to this tarball as
12828 the new upstream as soon as we find time to do the merge. Since the
12829 new tarball was created, we agreed with Werner at SuSe to make a new
12830 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
12831 development there. The project is registered and currently waiting
12832 for approval by the Savannah administrators, and as soon as it is
12833 approved, we will import the old versions from svn and continue
12834 working on the future release.&lt;/p&gt;
12835
12836 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
12837 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
12838 </description>
12839 </item>
12840
12841 <item>
12842 <title>Debian boots quicker and quicker</title>
12843 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
12844 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
12845 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
12846 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
12847 people involved in the boot system on Debian and Ubuntu, to see if we
12848 could find more ways to speed up the boot system. This was an Ubuntu
12849 funded
12850 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
12851 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
12852 of boot systems, and ways to handle the increasing number of boot
12853 issues introduced by the Linux kernel becoming more and more
12854 asynchronous and event base. The Ubuntu approach using udev and
12855 upstart might be a good way forward. Time will show.&lt;/p&gt;
12856
12857 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
12858 process in Debian. All of these should be applied to get a quick
12859 boot:&lt;/p&gt;
12860
12861 &lt;ul&gt;
12862
12863 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
12864
12865 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
12866 clock is in UTC.&lt;/li&gt;
12867
12868 &lt;li&gt;Install and activate the insserv package to enable
12869 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12870 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
12871
12872 &lt;/ul&gt;
12873
12874 These points are based on the Google summer of code work done by
12875 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
12876 Villegas&lt;/a&gt;.
12877
12878 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
12879 unstable yesterday. When we tested it, we were able to cut 6 seconds
12880 from the boot sequence. It depend on very correct dependency
12881 declaration in all init.d scripts, so I expect us to find edge cases
12882 where the dependences in some scripts are slightly wrong when we start
12883 using this.&lt;/p&gt;
12884
12885 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12886 introduced by Raphael Geissert today, one that could affect the
12887 startup speed as well. Instead of starting some scripts concurrently
12888 from rcS.d/ and another set of scripts from rc2.d/, it would be
12889 possible to run a of them in the same process. A quick way to test
12890 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
12891 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
12892 </description>
12893 </item>
12894
12895 <item>
12896 <title>BSAs påstander om piratkopiering møter motstand</title>
12897 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
12898 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
12899 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
12900 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
12901 programvareselskapene som Microsoft og Apple, publisert en rapport der
12902 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12903 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12904 dager siden kom
12905 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
12906 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
12907 dagene. Et spesielt interessant kommentar fra Sverige,
12908 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
12909 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
12910
12911 &lt;blockquote&gt;
12912 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
12913 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12914 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
12915 exakta&quot;, säger BSAs Sverigechef John Hugosson.
12916 &lt;/blockquote&gt;
12917
12918 &lt;p&gt;Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er &lt;a
12919 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
12920 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
12921 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
12922 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
12923
12924 &lt;p&gt;Fant lenkene via &lt;a
12925 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
12926 på Slashdot&lt;/a&gt;.&lt;/p&gt;
12927 </description>
12928 </item>
12929
12930 <item>
12931 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
12932 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
12933 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
12934 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
12935 <description>&lt;p&gt;Kom over
12936 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
12937 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12938 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12939 jobber til daglig. En rask opptelling forteller meg at vi har 490
12940 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
12941 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
12942 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
12943 </description>
12944 </item>
12945
12946 <item>
12947 <title>Kryptert harddisk - naturligvis</title>
12948 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
12949 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
12950 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
12951 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
12952 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
12953 når en tar tap av arbeidstid, fortrolige dokumenter,
12954 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12955 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12956 til at jeg har kryptert harddisken på både kontormaskinen og min
12957 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12958 komme på avveie, den første informasjon relatert til jobben min ved
12959 Universitetet i Oslo, og den andre relatert til blant annet
12960 foreningsarbeide. Kryptering av diskene gjør at det er lite
12961 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12962 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12963 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12964 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12965 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12966 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12967 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12968 det er gjort slik jeg gjør det er minimale, og gevinstene er
12969 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12970 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
12971
12972 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12973 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12974 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12975 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12976 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12977 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12978 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12979 betydelige.&lt;/p&gt;
12980 </description>
12981 </item>
12982
12983 <item>
12984 <title>Two projects that have improved the quality of free software a lot</title>
12985 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
12986 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
12987 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
12988 <description>&lt;p&gt;There are two software projects that have had huge influence on the
12989 quality of free software, and I wanted to mention both in case someone
12990 do not yet know them.&lt;/p&gt;
12991
12992 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
12993 tool to detect and expose errors in the memory handling of programs.
12994 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
12995 and it will report any problems on stdout. It is even better if the
12996 program include debug information. With debug information, it is able
12997 to report the source file name and line number where the problem
12998 occurs. It can report things like &#39;reading past memory block in file
12999 X line N, the memory block was allocated in file Y, line M&#39;, and
13000 &#39;using uninitialised value in control logic&#39;. This tool has made it
13001 trivial to investigate reproducible crash bugs in programs, and have
13002 reduced the number of this kind of bugs in free software a lot.
13003
13004 &lt;p&gt;The second one is
13005 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
13006 a source code checker. It is able to process the source of a program
13007 and find problems in the logic without running the program. It
13008 started out as the Stanford Checker and became well known when it was
13009 used to find bugs in the Linux kernel. It is now a commercial tool
13010 and the company behind it is running
13011 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
13012 free software community, where a lot of free software projects get
13013 their source checked for free. Several thousand defects have been
13014 found and fixed so far. It can find errors like &#39;lock L taken in file
13015 X line N is never released if exiting in line M&#39;, or &#39;the code in file
13016 Y lines O to P can never be executed&#39;. The projects included in the
13017 community service project have managed to get rid of a lot of
13018 reliability problems thanks to Coverity.&lt;/p&gt;
13019
13020 &lt;p&gt;I believe tools like this, that are able to automatically find
13021 errors in the source, are vital to improve the quality of software and
13022 make sure we can get rid of the crashing and failing software we are
13023 surrounded by today.&lt;/p&gt;
13024 </description>
13025 </item>
13026
13027 <item>
13028 <title>No patch is not better than a useless patch</title>
13029 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
13030 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
13031 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
13032 <description>&lt;p&gt;Julien Blache
13033 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
13034 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
13035 patch allow one to discuss a concrete and proposed solution, and also
13036 prove that the issue at hand is important enough for someone to spent
13037 time on fixing it. No patch do not provide any of these positive
13038 properties.&lt;/p&gt;
13039 </description>
13040 </item>
13041
13042 <item>
13043 <title>Standardize on protocols and formats, not vendors and applications</title>
13044 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
13045 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
13046 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
13047 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
13048 very good one to form a long lived computer infrastructure. It is the
13049 simple one, lost by many in todays computer industry: Standardize on
13050 open network protocols and open exchange/storage formats, not applications.
13051 Applications come and go, while protocols and files tend to stay, and
13052 thus one want to make it easy to change application and vendor, while
13053 avoiding conversion costs and locking users to a specific platform or
13054 application.&lt;/p&gt;
13055
13056 &lt;p&gt;This approach make it possible to replace the client applications
13057 independently of the server applications. One can even allow users to
13058 use several different applications as long as they handle the selected
13059 protocol and format. In the normal case, only one client application
13060 is recommended and users only get help if they choose to use this
13061 application, but those that want to deviate from the easy path are not
13062 blocked from doing so.&lt;/p&gt;
13063
13064 &lt;p&gt;It also allow us to replace the server side without forcing the
13065 users to replace their applications, and thus allow us to select the
13066 best server implementation at any moment, when scale and resouce
13067 requirements change.&lt;/p&gt;
13068
13069 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
13070 open formats, but I would never recommend standardizing on a single
13071 application that do not use open network protocol or open formats.&lt;/p&gt;
13072 </description>
13073 </item>
13074
13075 <item>
13076 <title>Returning from Skolelinux developer gathering</title>
13077 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
13078 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
13079 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
13080 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
13081 Edu/Skolelinux development gathering. I got a bit done tuning the
13082 desktop, and looked into the dynamic service location protocol
13083 implementation avahi. It look like it could be useful for us. Almost
13084 30 people participated, and I believe it was a great environment to
13085 get to know the Skolelinux system. Walter Bender, involved in the
13086 development of the Sugar educational platform, presented his stuff and
13087 also helped me improve my OLPC installation. He also showed me that
13088 his Turtle Art application can be used in standalone mode, and we
13089 agreed that I would help getting it packaged for Debian. As a
13090 standalone application it would be great for Debian Edu. We also
13091 tried to get the video conferencing working with two OLPCs, but that
13092 proved to be too hard for us. The application seem to need more work
13093 before it is ready for me. I look forward to getting home and relax
13094 now. :)&lt;/p&gt;
13095 </description>
13096 </item>
13097
13098 <item>
13099 <title>Time for new LDAP schemas replacing RFC 2307?</title>
13100 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
13101 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
13102 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
13103 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
13104 optimal. There is RFC 2307 documenting one way to store NIS maps in
13105 LDAP, and a modified version of this normally called RFC 2307bis, with
13106 some modifications to be compatible with Active Directory. The RFC
13107 specification handle the content of a lot of system databases, but do
13108 not handle DNS zones and DHCP configuration.&lt;/p&gt;
13109
13110 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
13111 we would like to store information about users, SMB clients/hosts,
13112 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13113 and LTSP configuration in LDAP. These objects have a lot in common,
13114 but with the current LDAP schemas it is not possible to have one
13115 object per entity. For example, one need to have at least three LDAP
13116 objects for a given computer, one with the SMB related stuff, one with
13117 DNS information and another with DHCP information. The schemas
13118 provided for DNS and DHCP are impossible to combine into one LDAP
13119 object. In addition, it is impossible to implement quick queries for
13120 netgroup membership, because of the way NIS triples are implemented.
13121 It just do not scale. I believe it is time for a few RFC
13122 specifications to cleam up this mess.&lt;/p&gt;
13123
13124 &lt;p&gt;I would like to have one LDAP object representing each computer in
13125 the network, and this object can then keep the SMB (ie host key), DHCP
13126 (mac address/name) and DNS (name/IP address) settings in one place.
13127 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
13128
13129 &lt;p&gt;I would also like to have a quick way to map from a user or
13130 computer and to the net group this user or computer is a member.&lt;/p&gt;
13131
13132 &lt;p&gt;Active Directory have done a better job than unix heads like myself
13133 in this regard, and the unix side need to catch up. Time to start a
13134 new IETF work group?&lt;/p&gt;
13135 </description>
13136 </item>
13137
13138 <item>
13139 <title>Endelig er Debian Lenny gitt ut</title>
13140 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
13141 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
13142 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
13143 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
13144 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
13145 Et langt steg videre for Debian-prosjektet, og en rekke nye
13146 programpakker blir nå tilgjengelig for de av oss som bruker den
13147 stabile utgaven av Debian. Neste steg er nå å få
13148 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
13149 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
13150 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13151 slippes løs på skolene. Takk til alle debian-utviklerne som har
13152 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13153 bootsekvens tilgjengelig i stabil utgave, vha pakken
13154 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
13155 </description>
13156 </item>
13157
13158 <item>
13159 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
13160 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
13161 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
13162 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
13163 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
13164 Oslo. Most of Saturday was used for the general assemly for the
13165 member organization, but the rest of the weekend I used to tune the
13166 LTSP installation. LTSP now work out of the box on the 10-network.
13167 Acer Aspire One proved to be a very nice thin client, with both
13168 screen, mouse and keybard in a small box. Was working on getting the
13169 diskless workstation setup configured out of the box, but did not
13170 finish it before the weekend was up.&lt;/p&gt;
13171
13172 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
13173 the Brazilian group, so that will have to wait for the next
13174 development gathering. Would love to have the Debian Edu installer
13175 automatically detect and configure a multiseat setup when it find one
13176 of these cards.&lt;/p&gt;
13177 </description>
13178 </item>
13179
13180 <item>
13181 <title>The sorry state of multimedia browser plugins in Debian</title>
13182 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
13183 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
13184 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
13185 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
13186 plugins available in Debian Lenny, to see which one we should use by
13187 default in Debian Edu. We need an embedded video playing plugin with
13188 control buttons to pause or stop the video, and capable of streaming
13189 all the multimedia content available on the web. The test results and
13190 notes are available on
13191 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
13192 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
13193 fill this need. My personal video player favorite, VLC, has a really
13194 bad plugin which fail on a lot of the test pages. A lot of the MIME
13195 types I would expect to work with any free software player (like
13196 video/ogg), just do not work. And simple formats like the
13197 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
13198 totem and vlc plugins. I hope the situation will improve soon. No
13199 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
13200
13201 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
13202 be the only one fitting our needs. :/&lt;/p&gt;
13203 </description>
13204 </item>
13205
13206 </channel>
13207 </rss>