]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
af875a95d9e31d8aeb18d92b854d3e2ce4636c2e
[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>The 2023 LinuxCNC Norwegian developer gathering</title>
11 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</guid>
13 <pubDate>Sun, 14 May 2023 20:30:00 +0200</pubDate>
14 <description>&lt;p&gt;The LinuxCNC project is making headway these days. A lot of
15 patches and issues have seen activity on
16 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/&quot;&gt;the project github
17 pages&lt;/a&gt; recently. A few weeks ago there was a developer gathering
18 over at the &lt;a href=&quot;https://tormach.com/&quot;&gt;Tormach&lt;/a&gt; headquarter in
19 Wisconsin, and now we are planning a new gathering in Norway. If you
20 wonder what LinuxCNC is, lets quote Wikipedia:&lt;/p&gt;
21
22 &lt;blockquote&gt;
23 &quot;LinuxCNC is a software system for numerical control of
24 machines such as milling machines, lathes, plasma cutters, routers,
25 cutting machines, robots and hexapods. It can control up to 9 axes or
26 joints of a CNC machine using G-code (RS-274NGC) as input. It has
27 several GUIs suited to specific kinds of usage (touch screen,
28 interactive development).&quot;
29 &lt;/blockquote&gt;
30
31 &lt;p&gt;The Norwegian developer gathering take place the weekend June 16th
32 to 18th this year, and is open for everyone interested in contributing
33 to LinuxCNC. Up to date information about the gathering can be found
34 in
35 &lt;a href=&quot;https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%40hjemme.reinholdtsen.name/#msg37837251&quot;&gt;the
36 developer mailing list thread&lt;/a&gt; where the gathering was announced.
37 Thanks to the good people at
38 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;,
39 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill-Linpro&lt;/a&gt; and
40 &lt;a href=&quot;https://www.nuugfoundation.no/no/&quot;&gt;NUUG Foundation&lt;/a&gt;, we
41 have enough sponsor funds to pay for food, and shelter for the people
42 traveling from afar to join us. If you would like to join the
43 gathering, get in touch.&lt;/p&gt;
44
45 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
46 activities, please send Bitcoin donations to my address
47 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
48 </description>
49 </item>
50
51 <item>
52 <title>OpenSnitch in Debian ready for prime time</title>
53 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</link>
54 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</guid>
55 <pubDate>Sat, 13 May 2023 12:10:00 +0200</pubDate>
56 <description>&lt;p&gt;A bit delayed,
57 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
58 application firewall OpenSnitch&lt;/a&gt; package in Debian now got the
59 latest fixes ready for Debian Bookworm. Because it depend on a
60 package missing on some architectures, the autopkgtest check of the
61 testing migration script did not understand that the tests were
62 actually working, so the migration was delayed. A bug in the package
63 dependencies is also fixed, so those installing the firewall package
64 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
65 installed by default. I am very grateful to Gustavo Iñiguez Goya for
66 his work on getting the package ready for Debian Bookworm.&lt;/p&gt;
67
68 &lt;p&gt;Armed with this package I have discovered some surprising
69 connections from programs I believed were able to work completly
70 offline, and it has already proven its worth, at least to me. If you
71 too want to get more familiar with the kind of programs using
72 Internett connections on your machine, I recommend testing &lt;tt&gt;apt
73 install opensnitch&lt;/tt&gt; in Bookworm and see what you think.&lt;/p&gt;
74
75 &lt;p&gt;The package is still not able to build its eBPF module within
76 Debian. Not sure how much work it would be to get it working, but
77 suspect some kernel related packages need to be extended with more
78 header files to get it working.&lt;/p&gt;
79
80 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
81 activities, please send Bitcoin donations to my address
82 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
83 </description>
84 </item>
85
86 <item>
87 <title>Speech to text, she APTly whispered, how hard can it be?</title>
88 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</link>
89 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</guid>
90 <pubDate>Sun, 23 Apr 2023 09:40:00 +0200</pubDate>
91 <description>&lt;p&gt;While visiting a convention during Easter, it occurred to me that
92 it would be great if I could have a digital Dictaphone with
93 transcribing capabilities, providing me with texts to cut-n-paste into
94 stuff I need to write. The background is that long drives often bring
95 up the urge to write on texts I am working on, which of course is out
96 of the question while driving. With the release of
97 &lt;a href=&quot;https://github.com/openai/whisper/&quot;&gt;OpenAI Whisper&lt;/a&gt;, this
98 seem to be within reach with Free Software, so I decided to give it a
99 go. OpenAI Whisper is a Linux based neural network system to read in
100 audio files and provide text representation of the speech in that
101 audio recording. It handle multiple languages and according to its
102 creators even can translate into a different language than the spoken
103 one. I have not tested the latter feature. It can either use the CPU
104 or a GPU with CUDA support. As far as I can tell, CUDA in practice
105 limit that feature to NVidia graphics cards. I have few of those, as
106 they do not work great with free software drivers, and have not tested
107 the GPU option. While looking into the matter, I did discover some
108 work to provide CUDA support on non-NVidia GPUs, and some work with
109 the library used by Whisper to port it to other GPUs, but have not
110 spent much time looking into GPU support yet. I&#39;ve so far used an old
111 X220 laptop as my test machine, and only transcribed using its
112 CPU.&lt;/p&gt;
113
114 &lt;p&gt;As it from a privacy standpoint is unthinkable to use computers
115 under control of someone else (aka a &quot;cloud&quot; service) to transcribe
116 ones thoughts and personal notes, I want to run the transcribing
117 system locally on my own computers. The only sensible approach to me
118 is to make the effort I put into this available for any Linux user and
119 to upload the needed packages into Debian. Looking at Debian Bookworm, I
120 discovered that only three packages were missing,
121 &lt;a href=&quot;https://bugs.debian.org/1034307&quot;&gt;tiktoken&lt;/a&gt;,
122 &lt;a href=&quot;https://bugs.debian.org/1034144&quot;&gt;triton&lt;/a&gt;, and
123 &lt;a href=&quot;https://bugs.debian.org/1034091&quot;&gt;openai-whisper&lt;/a&gt;. For a while
124 I also believed
125 &lt;a href=&quot;https://bugs.debian.org/1034286&quot;&gt;ffmpeg-python&lt;/a&gt; was
126 needed, but as its
127 &lt;a href=&quot;https://github.com/kkroening/ffmpeg-python/issues/760&quot;&gt;upstream
128 seem to have vanished&lt;/a&gt; I found it safer
129 &lt;a href=&quot;https://github.com/openai/whisper/pull/1242&quot;&gt;to rewrite
130 whisper&lt;/a&gt; to stop depending on in than to introduce ffmpeg-python
131 into Debian. I decided to place these packages under the umbrella of
132 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team&quot;&gt;the Debian Deep
133 Learning Team&lt;/a&gt;, which seem like the best team to look after such
134 packages. Discussing the topic within the group also made me aware
135 that the triton package was already a future dependency of newer
136 versions of the torch package being planned, and would be needed after
137 Bookworm is released.&lt;/p&gt;
138
139 &lt;p&gt;All required code packages have been now waiting in
140 &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the Debian NEW
141 queue&lt;/a&gt; since Wednesday, heading for Debian Experimental until
142 Bookworm is released. An unsolved issue is how to handle the neural
143 network models used by Whisper. The default behaviour of Whisper is
144 to require Internet connectivity and download the model requested to
145 &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt; on first invocation. This obviously would
146 fail &lt;a href=&quot;https://people.debian.org/~bap/dfsg-faq.html&quot;&gt;the
147 deserted island test of free software&lt;/a&gt; as the Debian packages would
148 be unusable for someone stranded with only the Debian archive and solar
149 powered computer on a deserted island.&lt;/p&gt;
150
151 &lt;p&gt;Because of this, I would love to include the models in the Debian
152 mirror system. This is problematic, as the models are very large
153 files, which would put a heavy strain on the Debian mirror
154 infrastructure around the globe. The strain would be even higher if
155 the models change often, which luckily as far as I can tell they do
156 not. The small model, which according to its creator is most useful
157 for English and in my experience is not doing a great job there
158 either, is 462 MiB (deb is 414 MiB). The medium model, which to me
159 seem to handle English speech fairly well is 1.5 GiB (deb is 1.3 GiB)
160 and the large model is 2.9 GiB (deb is 2.6 GiB). I would assume
161 everyone with enough resources would prefer to use the large model for
162 highest quality. I believe the models themselves would have to go
163 into the non-free part of the Debian archive, as they are not really
164 including any useful source code for updating the models. The
165 &quot;source&quot;, aka the model training set, according to the creators
166 consist of &quot;680,000 hours of multilingual and multitask supervised
167 data collected from the web&quot;, which to me reads material with both
168 unknown copyright terms, unavailable to the general public. In other
169 words, the source is not available according to the Debian Free
170 Software Guidelines and the model should be considered non-free.&lt;/p&gt;
171
172 &lt;p&gt;I asked the Debian FTP masters for advice regarding uploading a
173 model package on their IRC channel, and based on the feedback there it
174 is still unclear to me if such package would be accepted into the
175 archive. In any case I wrote build rules for a
176 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team/openai-whisper-model&quot;&gt;OpenAI
177 Whisper model package&lt;/a&gt; and
178 &lt;a href=&quot;https://github.com/openai/whisper/pull/1257&quot;&gt;modified the
179 Whisper code base&lt;/a&gt; to prefer shared files under &lt;tt&gt;/usr/&lt;/tt&gt; and
180 &lt;tt&gt;/var/&lt;/tt&gt; over user specific files in &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt;
181 to be able to use these model packages, to prepare for such
182 possibility. One solution might be to include only one of the models
183 (small or medium, I guess) in the Debian archive, and ask people to
184 download the others from the Internet. Not quite sure what to do
185 here, and advice is most welcome (use the debian-ai mailing list).&lt;/p&gt;
186
187 &lt;p&gt;To make it easier to test the new packages while I wait for them to
188 clear the NEW queue, I created an APT source targeting bookworm. I
189 selected Bookworm instead of Bullseye, even though I know the latter
190 would reach more users, is that some of the required dependencies are
191 missing from Bullseye and I during this phase of testing did not want
192 to backport a lot of packages just to get up and running.&lt;/p&gt;
193
194 &lt;p&gt;Here is a recipe to run as user root if you want to test OpenAI
195 Whisper using Debian packages on your Debian Bookworm installation,
196 first adding the APT repository GPG key to the list of trusted keys,
197 then setting up the APT repository and finally installing the packages
198 and one of the models:&lt;/p&gt;
199
200 &lt;p&gt;&lt;pre&gt;
201 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
202 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
203 mkdir -p /etc/apt/sources.list.d
204 cat &gt; /etc/apt/sources.list.d/pere-whisper.list &amp;lt;&amp;lt;EOF
205 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
206 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
207 EOF
208 apt update
209 apt install openai-whisper
210 &lt;/pre&gt;&lt;/p&gt;
211
212 &lt;p&gt;The package work for me, but have not yet been tested on any other
213 computer than my own. With it, I have been able to (badly) transcribe
214 a 2 minute 40 second Norwegian audio clip to test using the small
215 model. This took 11 minutes and around 2.2 GiB of RAM. Transcribing
216 the same file with the medium model gave a accurate text in 77 minutes
217 using around 5.2 GiB of RAM. My test machine had too little memory to
218 test the large model, which I believe require 11 GiB of RAM. In
219 short, this now work for me using Debian packages, and I hope it will
220 for you and everyone else once the packages enter Debian.&lt;/p&gt;
221
222 &lt;p&gt;Now I can start on the audio recording part of this project.&lt;/p&gt;
223
224 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
225 activities, please send Bitcoin donations to my address
226 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
227 </description>
228 </item>
229
230 <item>
231 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software</title>
232 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</link>
233 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</guid>
234 <pubDate>Fri, 7 Apr 2023 23:10:00 +0200</pubDate>
235 <description>&lt;p&gt;Today I finally found time to track down a useful radio frequency
236 scanner for my software defined radio. Just for fun I tried to locate
237 the radios used in the areas, and a good start would be to scan all
238 the frequencies to see what is in use. I&#39;ve tried to find a useful
239 program earlier, but ran out of time before I managed to find a useful
240 tool. This time I was more successful, and after a few false leads I
241 found a description of
242 &lt;a href=&quot;https://www.kali.org/tools/rtlsdr-scanner/&quot;&gt;rtlsdr-scanner
243 over at the Kali site&lt;/a&gt;, and was able to track down
244 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git&quot;&gt;the
245 Kali package git repository&lt;/a&gt; to build a deb package for the
246 scanner. Sadly the package is missing from the Debian project itself,
247 at least in Debian Bullseye. Two runtime dependencies,
248 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-visvis.git&quot;&gt;python-visvis&lt;/a&gt;
249 and
250 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-rtlsdr.git&quot;&gt;python-rtlsdr&lt;/a&gt;
251 had to be built and installed separately. Luckily &#39;&lt;tt&gt;gbp
252 buildpackage&lt;/tt&gt;&#39; handled them just fine and no further packages had
253 to be manually built. The end result worked out of the box after
254 installation.&lt;/p&gt;
255
256 &lt;p&gt;My initial scans for FM channels worked just fine, so I knew the
257 scanner was functioning. But when I tried to scan every frequency
258 from 100 to 1000 MHz, the program stopped unexpectedly near the
259 completion. After some debugging I discovered USB software radio I
260 used rejected frequencies above 948 MHz, triggering a unreported
261 exception breaking the scan. Changing the scan to end at 957 worked
262 better. I similarly found the lower limit to be around 15, and ended
263 up with the following full scan:&lt;/p&gt;
264
265 &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;
266
267 &lt;p&gt;Saving the scan did not work, but exporting it as a CSV file worked
268 just fine. I ended up with around 477k CVS lines with dB level for
269 the given frequency.&lt;/p&gt;
270
271 &lt;p&gt;The save failure seem to be a missing UTF-8 encoding issue in the
272 python code. Will see if I can find time to send a patch
273 &lt;a href=&quot;https://github.com/CdeMills/RTLSDR-Scanner/&quot;&gt;upstream&lt;/a&gt;
274 later to fix this exception:&lt;/p&gt;
275
276 &lt;pre&gt;
277 Traceback (most recent call last):
278 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
279 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
280 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
281 handle.write(json.dumps(data, indent=4))
282 TypeError: a bytes-like object is required, not &#39;str&#39;
283 Traceback (most recent call last):
284 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
285 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
286 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
287 handle.write(json.dumps(data, indent=4))
288 TypeError: a bytes-like object is required, not &#39;str&#39;
289 &lt;/pre&gt;
290
291 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
292 activities, please send Bitcoin donations to my address
293 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
294 </description>
295 </item>
296
297 <item>
298 <title>OpenSnitch available in Debian Sid and Bookworm</title>
299 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</link>
300 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</guid>
301 <pubDate>Sat, 25 Feb 2023 20:30:00 +0100</pubDate>
302 <description>&lt;p&gt;Thanks to the efforts of the OpenSnitch lead developer Gustavo
303 Iñiguez Goya allowing me to sponsor the upload,
304 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
305 application firewall OpenSnitch&lt;/a&gt; is now available in Debian
306 Testing, soon to become the next stable release of Debian.&lt;/p&gt;
307
308 &lt;p&gt;This is a package which set up a network firewall on one or more
309 machines, which is controlled by a graphical user interface that will
310 ask the user if a program should be allowed to connect to the local
311 network or the Internet. If some background daemon is trying to dial
312 home, it can be blocked from doing so with a simple mouse click, or by
313 default simply by not doing anything when the GUI question dialog pop
314 up. A list of all programs discovered using the network is provided
315 in the GUI, giving the user an overview of how the machine(s) programs
316 use the network.&lt;/p&gt;
317
318 &lt;p&gt;OpenSnitch was uploaded for NEW processing about a month ago, and I
319 had little hope of it getting accepted and shaping up in time for the
320 package freeze, but the Debian ftpmasters proved to be amazingly quick
321 at checking out the package and it was accepted into the archive about
322 week after the first upload. It is now team maintained under the Go
323 language team umbrella. A few fixes to the default setup is only in
324 Sid, and should migrate to Testing/Bookworm in a week.&lt;/p&gt;
325
326 &lt;p&gt;During testing I ran into an
327 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/813&quot;&gt;issue
328 with Minecraft server broadcasts disappearing&lt;/a&gt;, which was quickly
329 resolved by the developer with a patch and a proposed configuration
330 change. I&#39;ve been told this was caused by the Debian packages default
331 use if /proc/ information to track down kernel status, instead of the
332 newer eBPF module that can be used. The reason is simply that
333 upstream and I have failed to find a way to build the eBPF modules for
334 OpenSnitch without a complete configured Linux kernel source tree,
335 which as far as we can tell is unavailable as a build dependency in
336 Debian. We tried unsuccessfully so far to use the kernel-headers
337 package. It would be great if someone could provide some clues how to
338 build eBPF modules on build daemons in Debian, possibly without the full
339 kernel source.&lt;/p&gt;
340
341 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
342 activities, please send Bitcoin donations to my address
343 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
344 </description>
345 </item>
346
347 <item>
348 <title>Is the desktop recommending your program for opening its files?</title>
349 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</link>
350 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</guid>
351 <pubDate>Sun, 29 Jan 2023 11:00:00 +0100</pubDate>
352 <description>&lt;p&gt;Linux desktop systems
353 &lt;a href=&quot;https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html&quot;&gt;have
354 standardized&lt;/a&gt; how programs present themselves to the desktop
355 system. If a package include a .desktop file in
356 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
357 environments will pick up the file and use its content to generate the
358 menu of available programs in the system. A lesser known fact is that
359 a package can also explain to the desktop system how to recognize the
360 files created by the program in question, and use it to open these
361 files on request, for example via a GUI file browser.&lt;/p&gt;
362
363 &lt;p&gt;A while back I ran into a package that did not tell the desktop
364 system how to recognize its files and was not used to open its files
365 in the file browser and fixed it. In the process I wrote a simple
366 debian/tests/ script to ensure the setup keep working. It might be
367 useful for other packages too, to ensure any future version of the
368 package keep handling its own files.&lt;/p&gt;
369
370 &lt;p&gt;For this to work the file format need a useful MIME type that can
371 be used to identify the format. If the file format do not yet have a
372 MIME type, it should define one and preferably also
373 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;register
374 it with IANA&lt;/a&gt; to ensure the MIME type string is reserved.&lt;/p&gt;
375
376 &lt;p&gt;The script uses the &lt;tt&gt;xdg-mime&lt;/tt&gt; program from xdg-utils to
377 query the database of standardized package information and ensure it
378 return sensible values. It also need the location of an example file
379 for xdg-mime to guess the format of.&lt;/p&gt;
380
381 &lt;pre&gt;
382 #!/bin/sh
383 #
384 # Author: Petter Reinholdtsen
385 # License: GPL v2 or later at your choice.
386 #
387 # Validate the MIME setup, making sure motor types have
388 # application/vnd.openmotor+yaml associated with them and is connected
389 # to the openmotor desktop file.
390
391 retval=0
392
393 mimetype=&quot;application/vnd.openmotor+yaml&quot;
394 testfile=&quot;test/data/real/o3100/motor.ric&quot;
395 mydesktopfile=&quot;openmotor.desktop&quot;
396
397 filemime=&quot;$(xdg-mime query filetype &quot;$testfile&quot;)&quot;
398
399 if [ &quot;$mimetype&quot; != &quot;$filemime&quot; ] ; then
400 retval=1
401 echo &quot;error: xdg-mime claim motor file MIME type is $filemine, not $mimetype&quot;
402 else
403 echo &quot;success: xdg-mime report correct mime type $mimetype for motor file&quot;
404 fi
405
406 desktop=$(xdg-mime query default &quot;$mimetype&quot;)
407
408 if [ &quot;$mydesktopfile&quot; != &quot;$desktop&quot; ]; then
409 retval=1
410 echo &quot;error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile&quot;
411 else
412 echo &quot;success: xdg-mime agree motor file should be handled by $mydesktopfile&quot;
413 fi
414
415 exit $retval
416 &lt;/pre&gt;
417
418 &lt;p&gt;It is a simple way to ensure your users are not very surprised when
419 they try to open one of your file formats in their file browser.&lt;/p&gt;
420
421 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
422 activities, please send Bitcoin donations to my address
423 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
424 </description>
425 </item>
426
427 <item>
428 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive</title>
429 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</link>
430 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</guid>
431 <pubDate>Sun, 22 Jan 2023 23:55:00 +0100</pubDate>
432 <description>&lt;p&gt;While reading a
433 &lt;a href=&quot;https://sneak.berlin/20230115/macos-scans-your-local-files-now/&quot;&gt;blog
434 post claiming MacOS X recently started scanning local files and
435 reporting information about them to Apple&lt;/a&gt;, even on a machine where
436 all such callback features had been disabled, I came across a
437 description of the Little Snitch application for MacOS X. It seemed
438 like a very nice tool to have in the tool box, and I decided to see if
439 something similar was available for Linux.&lt;/p&gt;
440
441 &lt;p&gt;It did not take long to find
442 &lt;a href=&quot;https://github.com/evilsocket/opensnitch&quot;&gt;the OpenSnitch
443 package&lt;/a&gt;, which has been in development since 2017, and now is in
444 version 1.5.0. It has had a
445 &lt;a href=&quot;https://bugs.debian.org/909567&quot;&gt;request for Debian
446 packaging&lt;/a&gt; since 2018, but no-one completed the job so far. Just
447 for fun, I decided to see if I could help, and I was very happy to
448 discover that
449 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/304&quot;&gt;upstream
450 want a Debian package too&lt;/a&gt;.&lt;/p&gt;
451
452 &lt;p&gt;After struggling a bit with getting the program to run, figuring
453 out building Go programs (and a little failed detour to look at eBPF
454 builds too - help needed), I am very happy to report that I am
455 sponsoring upstream to maintain the package in Debian, and it has
456 since this morning been waiting in NEW for the ftpmasters to have a
457 look. Perhaps it can get into the archive in time for the Bookworm
458 release?&lt;/p&gt;
459
460 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
461 activities, please send Bitcoin donations to my address
462 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
463 </description>
464 </item>
465
466 <item>
467 <title>LinuxCNC MQTT publisher component</title>
468 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</link>
469 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</guid>
470 <pubDate>Sun, 8 Jan 2023 19:30:00 +0100</pubDate>
471 <description>&lt;p&gt;I watched &lt;a href=&quot;https://yewtu.be/watch?v=jmKUV3aNLjk&quot;&gt;a 2015
472 video from Andreas Schiffler&lt;/a&gt; the other day, where he set up
473 &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;LinuxCNC&lt;/a&gt; to send status
474 information to the MQTT broker IBM Bluemix. As I also use MQTT for
475 graphing, it occured to me that a generic MQTT LinuxCNC component
476 would be useful and I set out to implement it. Today I got the first
477 draft limping along and submitted as
478 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/2253&quot;&gt;a patch to the
479 LinuxCNC project&lt;/a&gt;.&lt;/p&gt;
480
481 &lt;p&gt;The simple part was setting up the MQTT publishing code in Python.
482 I already have set up other parts submitting data to my Mosquito MQTT
483 broker, so I could reuse that code. Writing a LinuxCNC component in
484 Python as new to me, but using existing examples in the code
485 repository and the extensive documentation, this was fairly straight
486 forward. The hardest part was creating a automated test for the
487 component to ensure it was working. Testing it in a simulated
488 LinuxCNC machine proved very useful, as I discovered features I needed
489 that I had not thought of yet, and adjusted the code quite a bit to
490 make it easier to test without a operational MQTT broker
491 available.&lt;/p&gt;
492
493 &lt;p&gt;The draft is ready and working, but I am unsure which LinuxCNC HAL
494 pins I should collect and publish by default (in other words, the
495 default set of information pieces published), and how to get the
496 machine name from the LinuxCNC INI file. The latter is a minor
497 detail, but I expect it would be useful in a setup with several
498 machines available. I am hoping for feedback from the experienced
499 LinuxCNC developers and users, to make the component even better
500 before it can go into the mainland LinuxCNC code base.&lt;/p&gt;
501
502 &lt;p&gt;Since I started on the MQTT component, I came across
503 &lt;a href=&quot;https://yewtu.be/watch?v=Bqa2grG0XtA&quot;&gt;another video from Kent
504 VanderVelden&lt;/a&gt; where he combine LinuxCNC with a set of screen glasses
505 controlled by a Raspberry Pi, and it occured to me that it would
506 be useful for such use cases if LinuxCNC also provided a REST API for
507 querying its status. I hope to start on such component once the MQTT
508 component is working well.&lt;/p&gt;
509
510 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
511 activities, please send Bitcoin donations to my address
512 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
513 </description>
514 </item>
515
516 <item>
517 <title>ONVIF IP camera management tool finally in Debian</title>
518 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</link>
519 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</guid>
520 <pubDate>Sat, 24 Dec 2022 08:00:00 +0100</pubDate>
521 <description>&lt;p&gt;Merry Christmas to you all. Here is a small gift to all those with
522 IP cameras following the &lt;a href=&quot;https://www.onvif.org/&quot;&gt;ONVIF
523 specification&lt;/a&gt;. There is finally a nice command line and GUI tool
524 in Debian to manage ONVIF IP cameras. After working with upstream for
525 a few months and sponsoring the upload, I am very happy to report that
526 the &lt;a href=&quot;https://tracker.debian.org/libonvif&quot;&gt;libonvif package&lt;/a&gt;
527 entered Debian Sid last night.&lt;/p&gt;
528
529 &lt;p&gt;The package provide a C library to communicate with such cameras, a
530 command line tool to locate and update settings of (like password) the
531 cameras and a GUI tool to configure and control the units as well as
532 preview the video from the camera. Libonvif is available on Both
533 Linux and Windows and the GUI tool uses the Qt library. The main
534 competitors are non-free software, while libonvif is GNU GPL licensed.
535 I am very glad Debian users in the future can control their cameras
536 using a free software system provided by Debian. But the ONVIF world
537 is full of slightly broken firmware, where the cameras pretend to
538 follow the ONVIF specification but fail to set some configuration
539 values or refuse to provide video to more than one recipient at the
540 time, and the onvif project is quite young and might take a while
541 before it completely work with your camera. Upstream seem eager to
542 improve the library, so handling any broken camera might be just &lt;a
543 href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;a bug report away&lt;/a&gt;.&lt;/p&gt;
544
545 &lt;p&gt;The package just cleared NEW, and need a new source only upload
546 before it can enter testing. This will happen in the next few
547 days.&lt;/p&gt;
548
549 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
550 activities, please send Bitcoin donations to my address
551 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
552 </description>
553 </item>
554
555 <item>
556 <title>Managing and using ONVIF IP cameras with Linux</title>
557 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</link>
558 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</guid>
559 <pubDate>Wed, 19 Oct 2022 12:30:00 +0200</pubDate>
560 <description>&lt;p&gt;Recently I have been looking at how to control and collect data
561 from a handful IP cameras using Linux. I both wanted to change their
562 settings and to make their imagery available via a free software
563 service under my control. Here is a summary of the tools I found.&lt;/p&gt;
564
565 &lt;p&gt;First I had to identify the cameras and their protocols. As far as
566 I could tell, they were using some SOAP looking protocol and their
567 internal web server seem to only work with Microsoft Internet Explorer
568 with some proprietary binary plugin, which in these days of course is
569 a security disaster and also made it impossible for me to use the
570 camera web interface. Luckily I discovered that the SOAP looking
571 protocol is actually following &lt;a href=&quot;https://www.onvif.org/&quot;&gt;the
572 ONVIF specification&lt;/a&gt;, which seem to be supported by a lot of IP
573 cameras these days.&lt;/p&gt;
574
575 &lt;p&gt;Once the protocol was identified, I was able to find what appear to
576 be the most popular way to configure ONVIF cameras, the free software
577 Windows tool named
578 &lt;a href=&quot;https://sourceforge.net/projects/onvifdm/&quot;&gt;ONVIF Device
579 Manager&lt;/a&gt;. Lacking any other options at the time, I tried
580 unsuccessfully to get it running using Wine, but was missing a dotnet
581 40 library and I found no way around it to run it on Linux.&lt;/p&gt;
582
583 &lt;p&gt;The next tool I found to configure the cameras were a non-free Linux Qt
584 client &lt;a href=&quot;https://www.lingodigit.com/onvif_nvcdemo.html&quot;&gt;ONVIF
585 Device Tool&lt;/a&gt;. I did not like its terms of use, so did not spend
586 much time on it.&lt;/p&gt;
587
588 &lt;p&gt;To collect the video and make it available in a web interface, I
589 found the Zoneminder tool in Debian. A recent version was able to
590 automatically detect and configure ONVIF devices, so I could use it to
591 set up motion detection in and collection of the camera output. I had
592 initial problems getting the ONVIF autodetection to work, as both
593 Firefox and Chromium &lt;a href=&quot;https://bugs.debian.org/1001188&quot;&gt;refused
594 the inter-tab communication&lt;/a&gt; being used by the Zoneminder web
595 pages, but managed to get konqueror to work. Apparently the &quot;Enhanced
596 Tracking Protection&quot; in Firefox cause the problem. I ended up
597 upgrading to the Bookworm edition of Zoneminder in the process to try
598 to fix the issue, and believe the problem might be solved now.&lt;/p&gt;
599
600 &lt;p&gt;In the process I came across the nice Linux GUI tool
601 &lt;a href=&quot;https://gitlab.com/caspermeijn/onvifviewer/&quot;&gt;ONVIF Viewer&lt;/a&gt;
602 allowing me to preview the camera output and validate the login
603 passwords required. Sadly its author has grown tired of maintaining
604 the software, so it might not see any future updates. Which is sad,
605 as the viewer is sightly unstable and the picture tend to lock up.
606 Note, this lockup might be due to limitations in the cameras and not
607 the viewer implementation. I suspect the camera is only able to
608 provide pictures to one client at the time, and the Zoneminder feed
609 might interfere with the GUI viewer. I have
610 &lt;a href=&quot;https://bugs.debian.org/1000820&quot;&gt;asked for the tool to be
611 included in Debian&lt;/a&gt;.&lt;/p&gt;
612
613 &lt;p&gt;Finally, I found what appear to be very nice Linux free software
614 replacement for the Windows tool, named
615 &lt;a href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;libonvif&lt;/a&gt;. It
616 provide a C library to talk to ONVIF devices as well as a command line
617 and GUI tool using the library. Using the GUI tool I was able to change
618 the admin passwords and update other settings of the cameras. I have
619 &lt;a href=&quot;https://bugs.debian.org/1021980&quot;&gt;asked for the package to be
620 included in Debian&lt;/a&gt;.&lt;/p&gt;
621
622 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
623 activities, please send Bitcoin donations to my address
624 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
625
626 &lt;p&gt;&lt;strong&gt;Update 2022-10-20&lt;/strong&gt;: Since my initial publication of
627 this text, I got several suggestions for more free software Linux
628 tools. There is &lt;a href=&quot;https://github.com/quatanium/python-onvif&quot;&gt;a
629 ONVIF python library&lt;/a&gt; (already
630 &lt;a href=&quot;https://bugs.debian.org/824240&quot;&gt;requested into Debian&lt;/a&gt;) and
631 &lt;a href=&quot;https://github.com/FalkTannhaeuser/python-onvif-zeep&quot;&gt;a python 3
632 fork&lt;/a&gt; using a different SOAP dependency. There is also
633 &lt;a href=&quot;https://www.home-assistant.io/integrations/onvif/&quot;&gt;support for
634 ONVIF in Home Assistant&lt;/a&gt;, and there is an alternative to Zoneminder
635 called &lt;a href=&quot;https://www.shinobi.video/&quot;&gt;Shinobi&lt;/a&gt;. The latter
636 two are not included in Debian either. I have not tested any of these
637 so far.&lt;/p&gt;
638 </description>
639 </item>
640
641 <item>
642 <title>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
643 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
644 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
645 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
646 <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;
647
648 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
649
650 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
651 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
652 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
653 english text is updated, and it is time to start working on the
654 translations. Around 37 percent of the strings have been updated, one
655 way or another, and the translations starting from a complete Debian Buster
656 edition now need to bring their translation up from 63% to 100%. The
657 complete book is licensed using a Creative Commons license, and has
658 been published in several languages over the years. The translations
659 are done by volunteers to bring Linux in their native tongue. The
660 last time I checked, it complete text was available in English,
661 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
662 In addition, work has been started for Arabic (Morocco), Catalan,
663 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
664 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
665 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
666
667 &lt;p&gt;The translation is conducted on
668 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
669 hosted weblate project page&lt;/a&gt;. Prospective translators are
670 recommeded to subscribe to
671 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
672 translators mailing list&lt;/a&gt; and should also check out
673 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
674 contributors&lt;/a&gt;.&lt;/p&gt;
675
676 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
677 have just started. Your contribution is most welcome.&lt;/p&gt;
678
679 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
680 activities, please send Bitcoin donations to my address
681 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
682 </description>
683 </item>
684
685 <item>
686 <title>Automatic LinuxCNC servo PID tuning?</title>
687 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
688 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
689 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
690 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
691 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
692 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
693 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
694 that control such mathematical machinery that a PID controller is. It
695 proved to be a lot harder than I hoped, and I still have not succeeded
696 in getting the Z PID controller to successfully defy gravity, nor X
697 and Y to move accurately and reliably. But while climbing up this
698 rather steep learning curve, I discovered that some motor control
699 systems are able to tune their PID controllers. I got the impression
700 from the documentation that LinuxCNC were not. This proved to be not
701 true.&lt;/p&gt;
702
703 &lt;p&gt;The LinuxCNC
704 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
705 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
706 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
707 &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
708 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
709 state, and all of these need to have a sensible value for the
710 controller to behave properly. Note, there are even more values
711 involved, theser are just the most important ones. In my case I need
712 the X, Y and Z axes to follow the requested path with little error.
713 This has proved quite a challenge for someone who have never tuned a
714 PID controller before, but there is at least some help to be found.
715
716 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
717 at_pid claiming to have auto tuning capabilities. Sadly it had been
718 neglected since 2011, and could not be used as a plug in replacement
719 for the default pid component. One would have to rewriting the
720 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
721 to quickly test auto tuning to see if it did a better job than me at
722 figuring out good P, I and D values to use.&lt;/p&gt;
723
724 &lt;p&gt;I decided to have a look if the situation could be improved. This
725 involved trying to understand the code and history of the pid and
726 at_pid components. Apparently they had a common ancestor, as code
727 structure, comments and variable names were quite close to each other.
728 Sadly this was not reflected in the git history, making it hard to
729 figure out what really happened. My guess is that the author of
730 &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;
731 took a version of
732 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
733 rewrote it to follow the structure he wished pid.c to have, then added
734 support for auto tuning and finally got it included into the LinuxCNC
735 repository. The restructuring and lack of early history made it
736 harder to figure out which part of the code were relevant to the auto
737 tuning, and which part of the code needed to be updated to work the
738 same way as the current pid.c implementation. I started by trying to
739 isolate relevant changes in pid.c, and applying them to at_pid.c. My
740 aim was to make sure the at_pid component could replace the pid
741 component with a simple change in the HAL setup loadrt line, without
742 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
743 hours following this approach, I had learned quite a lot about the
744 code structure of both components, while concluding I was heading down
745 the wrong rabbit hole, and should get back to the surface and find a
746 different path.&lt;/p&gt;
747
748 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
749 related part of the original at_pid.c, and instead isolate and lift
750 the auto tuning part of the code and inject it into a copy of pid.c.
751 This ensured compatibility with the current pid component, while
752 adding auto tuning as a run time option. To make it easier to identify
753 the relevant parts in the future, I wrapped all the auto tuning code
754 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
755 pid component by default, as that part of the code is identical. The
756 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
757 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
758
759 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
760 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
761 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
762 back, and see what the auto tuning code will do. I do not know the
763 mathematical foundation of the at_pid algorithm, but from observation
764 I can tell that the algorithm will, when enabled, produce a square
765 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
766 of the PID controller. This can be seen using the HAL Scope provided
767 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
768 to the motor controller, which in turn is translated into motor speed.
769 So at_pid will ask the motor to move the axis back and forth. The
770 number of cycles in the pattern is controlled by the
771 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
772 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
773 change the direction of a physical object instantly (as in going
774 directly from a positive voltage to the equivalent negative voltage)
775 do not change velocity instantly, and it take some time for the object
776 to slow down and move in the opposite direction. This result in a
777 more smooth movement wave form, as the axis in question were vibrating
778 back and forth. When the axis reached the target speed in the
779 opposing direction, the auto tuner change direction again. After
780 several of these changes, the average time delay between the &#39;peaks&#39;
781 and &#39;valleys&#39; of this movement graph is then used to calculate
782 proposed values for Pgain, Igain and Dgain, and insert them into the
783 HAL model to use by the pid controller. The auto tuned settings are
784 not great, but htye work a lot better than the values I had been able
785 to cook up on my own, at least for the horizontal X and Y axis. But I
786 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
787 controllers error out if the voltage change too quickly. I&#39;ve been
788 less lucky with the Z axis, which is moving a heavy object up and
789 down, and seem to confuse the algorithm. The Z axis movement became a
790 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
791 gravitational drag, but I will have to work a lot more on the Z axis
792 PID values.&lt;/p&gt;
793
794 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
795 tuning. Lets say the HAL configuration in question load the PID
796 component for X, Y and Z like this:&lt;/p&gt;
797
798 &lt;blockquote&gt;&lt;pre&gt;
799 loadrt pid names=pid.x,pid.y,pid.z
800 &lt;/pre&gt;&lt;/blockquote&gt;
801
802 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
803 look like this:&lt;/p&gt;
804
805 &lt;blockquote&gt;&lt;pre&gt;
806 loadrt at_pid names=pid.x,pid.y,pid.z
807 &lt;/pre&gt;&lt;/blockquote&gt;
808
809 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
810 components are referenced by name. If the component had used count=3
811 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
812
813 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
814 range, to make sure it do not hit anything when it start moving back
815 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
816 output range. I used 0.1 as my initial value. Next, assign 1 to the
817 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
818 part and feed 0 to the output pin, which in my case initially caused a
819 lot of drift. In my case it proved to be a good idea with X and Y to
820 tune the motor driver to make sure 0 voltage stopped the motor
821 rotation. On the other hand, for the Z axis this proved to be a bad
822 idea, so it will depend on your setup. It might help to set the
823 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
824 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
825 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
826 your axis will vibrate for a few seconds and when it is done, new
827 values for Pgain, Igain and Dgain will be active. To test them,
828 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
829 machine to suddenly jerk as it bring the axis back to its commanded
830 position, which it might have drifted away from during tuning. To
831 summarize with some halcmd lines:&lt;/p&gt;
832
833 &lt;blockquote&gt;&lt;pre&gt;
834 setp pid.x.tune-effort 0.1
835 setp pid.x.tune-mode 1
836 setp pid.x.tune-start 1
837 # wait for the tuning to complete
838 setp pid.x.tune-mode 0
839 &lt;/pre&gt;&lt;/blockquote&gt;
840
841 &lt;p&gt;After doing this task quite a few times while trying to figure out
842 how to properly tune the PID controllers on the machine in, I decided
843 to figure out if this process could be automated, and wrote a script
844 to do the entire tuning process from power on. The end result will
845 ensure the machine is powered on and ready to run, home all axis if it
846 is not already done, check that the extra tuning pins are available,
847 move the axis to its mid point, run the auto tuning and re-enable the
848 pid controller when it is done. It can be run several times. Check
849 out the
850 &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;
851 script on github if you want to learn how it is done.&lt;/p&gt;
852
853 &lt;p&gt;My hope is that this little adventure can inspire someone who know
854 more about motor PID controller tuning can implement even better
855 algorithms for automatic PID tuning in LinuxCNC, making life easier
856 for both me and all the others that want to use LinuxCNC but lack the
857 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
858
859 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
860 activities, please send Bitcoin donations to my address
861 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
862 </description>
863 </item>
864
865 <item>
866 <title>LinuxCNC translators life just got a bit easier</title>
867 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
868 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
869 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
870 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
871 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
872 proposed to change the documentation build system make life easier for
873 translators. The original system consisted of independently written
874 documentation files for each language, with no automated way to track
875 changes done in other translations and no help for the translators to
876 know how much was left to translated. By using
877 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
878 files from the English documentation, this can be improved. A small
879 team of LinuxCNC contributors got together and today our labour
880 finally payed off. Since a few hours ago, it is now possible to
881 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
882 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
883
884 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
885 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
886
887 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
888 activities, please send Bitcoin donations to my address
889 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
890 </description>
891 </item>
892
893 <item>
894 <title>geteltorito make CD firmware upgrades a breeze</title>
895 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
896 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
897 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
898 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
899 located the firmware download page from Lenovo (which annoyingly do
900 not allow access via Tor, forcing me to hand them more personal
901 information that I would like). The
902 &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
903 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
904 when all I got available is a USB memory stick. I tried booting the
905 ISO as a USB stick, but this did not work. But genisoimage came to
906 the rescue.&lt;/p&gt;
907
908 &lt;P&gt;The geteltorito program in
909 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
910 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
911 USB stick using a simple command line recipe, which I then can write
912 to the most recently inserted USB stick:&lt;/p&gt;
913
914 &lt;blockquote&gt;&lt;pre&gt;
915 geteltorito -o usbstick.img lenovo-firmware.iso
916 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
917 &lt;/pre&gt;&lt;/blockquote&gt;
918
919 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
920 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
921 </description>
922 </item>
923
924 <item>
925 <title>Run your industrial metal working machine using Debian?</title>
926 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
927 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
928 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
929 <description>&lt;p&gt;After many months of hard work by the good people involved in
930 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
931 system was accepted Sunday
932 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
933 Once it was available from Debian, I was surprised to discover from
934 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
935 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
936 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
937 be a good place to check out, but sadly is not working when visiting
938 via Tor.&lt;/p&gt;
939
940 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
941 Wikipedia quote is in place?&lt;/p&gt;
942
943 &lt;blockquote&gt;
944 &quot;LinuxCNC is a software system for numerical control of
945 machines such as milling machines, lathes, plasma cutters, routers,
946 cutting machines, robots and hexapods. It can control up to 9 axes or
947 joints of a CNC machine using G-code (RS-274NGC) as input. It has
948 several GUIs suited to specific kinds of usage (touch screen,
949 interactive development).&quot;
950 &lt;/blockquote&gt;
951
952 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
953 page indicate that it can only work with hard real time kernel
954 features, it can also work with the user space soft real time features
955 provided by the Debian kernel.
956 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
957 available from Github. The last few months I&#39;ve been involved in the
958 translation setup for the program and documentation. Translators are
959 most welcome to
960 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
961 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
962
963 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
964 activities, please send Bitcoin donations to my address
965 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
966 </description>
967 </item>
968
969 <item>
970 <title>Debian still an excellent choice for Lego builders</title>
971 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
972 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
973 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
974 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
975 the packages under the team umbrella has been updated to fix
976 packaging, lintian issues and BTS reports. In addition, a new and
977 inspiring team member appeared on both the
978 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
979 Team mailing list&lt;/a&gt; and
980 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
981 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
982 Mindstorms programming, check out the
983 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
984 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
985
986 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
987 even the first one in more than ten years, and old upstreams was
988 released with new ones. There are still a lot of work left, and the
989 team welcome more members to help us make sure Debian is the Linux
990 distribution of choice for Lego builders. If you want to contribute,
991 join us in the IRC channel and become part of
992 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
993 Salsa&lt;/a&gt;.&lt;/p&gt;
994
995 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
996 activities, please send Bitcoin donations to my address
997 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
998 </description>
999 </item>
1000
1001 <item>
1002 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
1003 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
1004 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
1005 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
1006 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
1007 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
1008 I am not sure which one of these are completely proof read, but the
1009 complete book is available in these languages:
1010
1011 &lt;ul&gt;
1012
1013 &lt;li&gt;English&lt;/li&gt;
1014 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
1015 &lt;li&gt;German&lt;/li&gt;
1016 &lt;li&gt;Indonesian&lt;/li&gt;
1017 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
1018 &lt;li&gt;Spanish&lt;/li&gt;
1019
1020 &lt;/ul&gt;
1021
1022 &lt;p&gt;This is the list of languages more than 70% complete, in other
1023 words with not too much left to do:&lt;/p&gt;
1024
1025 &lt;ul&gt;
1026
1027 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
1028 &lt;li&gt;French - 79%&lt;/li&gt;
1029 &lt;li&gt;Italian - 79%&lt;/li&gt;
1030 &lt;li&gt;Japanese - 77%&lt;/li&gt;
1031 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
1032 &lt;li&gt;Persian - 71%&lt;/li&gt;
1033
1034 &lt;/ul&gt;
1035
1036 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
1037
1038 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
1039
1040 &lt;ul&gt;
1041
1042 &lt;li&gt;Russian - 63%&lt;/li&gt;
1043 &lt;li&gt;Swedish - 53%&lt;/li&gt;
1044 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
1045 &lt;li&gt;Catalan - 45%&lt;/li&gt;
1046
1047 &lt;/ul&gt;
1048
1049 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
1050
1051 &lt;ul&gt;
1052
1053 &lt;li&gt;Dutch - 26%&lt;/li&gt;
1054 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
1055 &lt;li&gt;Polish - 23%&lt;/li&gt;
1056 &lt;li&gt;Czech - 22%&lt;/li&gt;
1057 &lt;li&gt;Turkish - 18%&lt;/li&gt;
1058
1059 &lt;/ul&gt;
1060
1061 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
1062
1063 &lt;ul&gt;
1064
1065 &lt;li&gt;Korean - 4%&lt;/li&gt;
1066 &lt;li&gt;Croatian - 2%&lt;/li&gt;
1067 &lt;li&gt;Greek - 2%&lt;/li&gt;
1068 &lt;li&gt;Danish - 1%&lt;/li&gt;
1069 &lt;li&gt;Romanian - 1%&lt;/li&gt;
1070
1071 &lt;/ul&gt;
1072
1073 &lt;p&gt;If you want to help provide a Debian instruction book in your own
1074 language, visit
1075 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
1076 to contribute to the translations.&lt;/p&gt;
1077
1078 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1079 activities, please send Bitcoin donations to my address
1080 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1081 </description>
1082 </item>
1083
1084 <item>
1085 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
1086 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
1087 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
1088 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
1089 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
1090 others, the decentralized communication platform
1091 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
1092 (earlier known as Ring), managed to get
1093 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
1094 into Debian Testing. Several of its dependencies has caused build and
1095 propagation problems, which all seem to be solved now.&lt;/p&gt;
1096
1097 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
1098 bittorrent is decentralized, I first of all like how it is not
1099 connected to external IDs like phone numbers. This allow me to set up
1100 computers to send me notifications using Jami without having to find
1101 get a phone number for each computer. Automatic notification via Jami
1102 is also made trivial thanks to the provided client side API (as a DBus
1103 service). Here is my bourne shell script demonstrating how to let any
1104 system send a message to any Jami address. It will create a new
1105 identity before sending the message, if no Jami identity exist
1106 already:&lt;/p&gt;
1107
1108 &lt;p&gt;&lt;pre&gt;
1109 #!/bin/sh
1110 #
1111 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
1112 #
1113 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
1114 # missing.
1115 #
1116 # License: GPL v2 or later at your choice
1117 # Author: Petter Reinholdtsen
1118
1119
1120 if [ -z &quot;$HOME&quot; ] ; then
1121 echo &quot;error: missing \$HOME, required for dbus to work&quot;
1122 exit 1
1123 fi
1124
1125 # First, get dbus running if not already running
1126 DBUSLAUNCH=/usr/bin/dbus-launch
1127 PIDFILE=/run/asterisk/dbus-session.pid
1128 if [ -e $PIDFILE ] ; then
1129 . $PIDFILE
1130 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
1131 unset DBUS_SESSION_BUS_ADDRESS
1132 fi
1133 fi
1134 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
1135 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
1136 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;
1137 DBUS_SESSION_BUS_PID=$!
1138 (
1139 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1140 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
1141 echo export DBUS_SESSION_BUS_ADDRESS
1142 ) &gt; $PIDFILE
1143 . $PIDFILE
1144 fi &amp;
1145
1146 dringop() {
1147 part=&quot;$1&quot;; shift
1148 op=&quot;$1&quot;; shift
1149 dbus-send --session \
1150 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1151 }
1152
1153 dringopreply() {
1154 part=&quot;$1&quot;; shift
1155 op=&quot;$1&quot;; shift
1156 dbus-send --session --print-reply \
1157 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1158 }
1159
1160 firstaccount() {
1161 dringopreply ConfigurationManager getAccountList | \
1162 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
1163 }
1164
1165 account=$(firstaccount)
1166
1167 if [ -z &quot;$account&quot; ] ; then
1168 echo &quot;Missing local account, trying to create it&quot;
1169 dringop ConfigurationManager addAccount \
1170 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
1171 account=$(firstaccount)
1172 if [ -z &quot;$account&quot; ] ; then
1173 echo &quot;unable to create local account&quot;
1174 exit 1
1175 fi
1176 fi
1177
1178 # Not using dringopreply to ensure $2 can contain spaces
1179 dbus-send --print-reply --session \
1180 --dest=cx.ring.Ring \
1181 /cx/ring/Ring/ConfigurationManager \
1182 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1183 string:&quot;$account&quot; string:&quot;$1&quot; \
1184 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
1185 &lt;/pre&gt;&lt;/p&gt;
1186
1187 &lt;p&gt;If you want to check it out yourself, visit the
1188 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
1189 more, and install the latest Jami client from Debian Unstable or
1190 Testing.&lt;/p&gt;
1191
1192 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1193 activities, please send Bitcoin donations to my address
1194 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1195 </description>
1196 </item>
1197
1198 <item>
1199 <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
1200 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1201 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1202 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
1203 <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;
1204
1205 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
1206 became the first translation published on paper of the new Buster
1207 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1208 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
1209 some days ago, and it looked good, so now the book is approved for
1210 general distribution. This updated paperback edition &lt;a
1211 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
1212 lulu.com&lt;/a&gt;. The book is also available for download in electronic
1213 form as PDF, EPUB and Mobipocket, and can also be
1214 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
1215
1216 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
1217 which concludes several months of work by several volunteers. The
1218 number of Linux related books published in Norwegian are few, and I
1219 really hope this one will gain many readers, as it is packed with deep
1220 knowledge on Linux and the Debian ecosystem. The book will be
1221 available for various Internet book stores like Amazon and Barnes &amp;
1222 Noble soon, but I recommend buying
1223 &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
1224 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
1225
1226 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1227 activities, please send Bitcoin donations to my address
1228 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1229 </description>
1230 </item>
1231
1232 <item>
1233 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
1234 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
1235 <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>
1236 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
1237 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
1238 of the Norwegian translation for
1239 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1240 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
1241 reading, I consider the proof reading complete enough for us to move
1242 to the next step, and have asked for the print version to be prepared
1243 and sent of to the print on demand service lulu.com. While it is
1244 still not to late if you find any incorrect translations on
1245 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1246 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
1247 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
1248 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
1249
1250 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
1251 with links available from the web site for the book linked to above.
1252 I hope a lot of readers find it useful.&lt;/p&gt;
1253
1254 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1255 activities, please send Bitcoin donations to my address
1256 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1257 </description>
1258 </item>
1259
1260 <item>
1261 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
1262 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1263 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1264 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
1265 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
1266 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1267 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
1268 new and updated version based on Buster is getting ready. Work on the
1269 updated Norwegian Bokmål edition has been going on for a few months
1270 now, and yesterday, we reached the first mile stone, with 100% of the
1271 texts being translated. A lot of proof reading remains, of course,
1272 but a major step towards a new edition has been taken.&lt;/p&gt;
1273
1274 &lt;p&gt;The book is translated by volunteers, and we would love to get some
1275 help with the proof reading. The translation uses
1276 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1277 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
1278 submit improvements and suggestions. There is also a proof readers
1279 PDF available on request, get in touch if you want to help out that
1280 way.&lt;/p&gt;
1281
1282 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1283 activities, please send Bitcoin donations to my address
1284 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1285 </description>
1286 </item>
1287
1288 <item>
1289 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
1290 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
1291 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
1292 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
1293 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
1294 User Group&lt;/a&gt;, I have the pleasure of receiving the
1295 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
1296 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
1297 several times a year. I rarely have time to read all the articles,
1298 but try to at least skim through them all as there is a lot of nice
1299 knowledge passed on there. I even carry the latest issue with me most
1300 of the time to try to get through all the articles when I have a few
1301 spare minutes.&lt;/p&gt;
1302
1303 &lt;p&gt;The other day I came across a nice article titled
1304 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
1305 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
1306 marvellous idea I hope can make it all the way into the POSIX standard.
1307 The idea is as simple as it is powerful. By introducing a new
1308 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1309 handle setting up TLS connections, one both make it trivial to add TLS
1310 support to any program currently using the POSIX socket API, and gain
1311 system wide control over certificates, TLS versions and encryption
1312 systems used. Instead of doing this:&lt;/p&gt;
1313
1314 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1315 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1316 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1317
1318 &lt;p&gt;the program code would be doing this:&lt;p&gt;
1319
1320 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1321 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1322 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1323
1324 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
1325 would normally modify only 5-10 lines in the code, which is amazing
1326 when compared to using for example the OpenSSL API.&lt;/p&gt;
1327
1328 &lt;p&gt;The project has set up the
1329 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
1330 web site to spread the idea, and the code for a kernel module and the
1331 associated system daemon is available from two github repositories:
1332 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
1333 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
1334 Unfortunately there is no explicit license information with the code,
1335 so its copyright status is unclear. A
1336 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
1337 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
1338
1339 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
1340 understand why it is an advantage to implement this as a kernel module
1341 and system wide service daemon, but can not help to think that it
1342 would be a lot easier to get projects to move to this way of setting
1343 up TLS if it was done with a user space approach where programs
1344 wanting to use this API approach could just link with a wrapper
1345 library.&lt;/p&gt;
1346
1347 &lt;p&gt;I recommend you check out this simple and powerful approach to more
1348 secure network connections. :)&lt;/p&gt;
1349
1350 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1351 activities, please send Bitcoin donations to my address
1352 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1353 </description>
1354 </item>
1355
1356 <item>
1357 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
1358 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
1359 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
1360 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
1361 <description>&lt;p&gt;Half a year ago,
1362 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
1363 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
1364 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
1365 handle both messages, audio and video. It uses distributed hash
1366 tables instead of central infrastructure to connect its users to each
1367 other, which in my book is a plus. I mentioned briefly that it could
1368 also work as a SIP client, which came in handy when the higher
1369 educational sector in Norway started to promote Zoom as its video
1370 conferencing solution. I am reluctant to use the official Zoom client
1371 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
1372 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
1373 to check the security) and benchmark it, and thus prefer to connect to
1374 Zoom meetings with free software clients.&lt;/p&gt;
1375
1376 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
1377 password set on the room. The Jami daemon leak memory like crazy
1378 (approximately 1 GiB a minute) when I am connected to the video
1379 conference, so I had to restart the client every 7-10 minutes, which
1380 is not great. I tried to get other SIP Linux clients to work
1381 without success, so I decided I would have to live with this wart
1382 until someone managed to fix the leak in the dring code base. But
1383 another problem showed up once the rooms were password protected. I
1384 could not get my dial tone signaling through from Jami to Zoom, and
1385 dial tone signaling is used to enter the password when connecting to
1386 Zoom. I tried a lot of different permutations with my Jami and
1387 Asterisk setup to try to figure out why the signaling did not get
1388 through, only to finally discover that the fundamental problem seem to
1389 be that Zoom is simply not able to receive dial tone signaling when
1390 connecting via SIP. There seem to be nothing wrong with the Jami and
1391 Asterisk end, it is simply broken in the Zoom end. I got help from a
1392 very skilled VoIP engineer figuring out this last part. And being a
1393 very skilled engineer, he was also able to locate a solution for me.
1394 Or to be exact, a workaround that solve my initial problem of
1395 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
1396
1397 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
1398 trick is already
1399 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
1400 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
1401 password. What is most surprising about this is that the
1402 automatically generated email from Zoom with instructions on how to
1403 connect via SIP do not mention this. The SIP address to use normally
1404 consist of the room ID (a number), an @ character and the IP address
1405 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1406 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
1407 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
1408 can both enter password, control the layout (full screen, active
1409 presence and gallery) and specify the host key to start the meeting.
1410 The full SIP address entered into Jami to provide the password will
1411 then look like this (all using made up numbers):&lt;/p&gt;
1412
1413 &lt;p&gt;&lt;blockquote&gt;
1414 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
1415 &lt;/blockquote&gt;&lt;/p&gt;
1416
1417 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
1418 recommend this setup to others. :)&lt;/p&gt;
1419
1420 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1421 activities, please send Bitcoin donations to my address
1422 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1423 </description>
1424 </item>
1425
1426 <item>
1427 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
1428 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
1429 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
1430 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
1431 <description>&lt;p&gt;The curiosity got the better of me when
1432 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
1433 reported&lt;/a&gt; that New Jersey was desperately looking for
1434 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
1435 and a few days later it was reported that
1436 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
1437 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
1438
1439 &lt;p&gt;I thus decided to have a look at free software alternatives to
1440 learn COBOL, and had the pleasure to find
1441 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
1442 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
1443 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
1444 transforming COBOL code to C or C++ before giving it to GCC or Visual
1445 Studio to build binaries.&lt;/p&gt;
1446
1447 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
1448 quick response, and also was happy to see a new Debian maintainer
1449 taking over when the original one recently asked to be replaced. A
1450 new Debian upload was done as recently as yesterday.&lt;/p&gt;
1451
1452 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
1453 introduction and make and run simple COBOL programs. It was fun to
1454 learn a new programming language. If you want to test for yourself,
1455 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
1456 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
1457
1458 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
1459 standard compliant it is, but it claim to pass most tests from COBOL
1460 test suite, which sound good to me. It is nice to know it is possible
1461 to learn COBOL using software without any usage restrictions, and I am
1462 very happy such nice free software project as this is available. If
1463 you as me is curious about COBOL, check it out.&lt;/p&gt;
1464
1465 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1466 activities, please send Bitcoin donations to my address
1467 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1468 </description>
1469 </item>
1470
1471 <item>
1472 <title>Jami/Ring, finally functioning peer to peer communication client</title>
1473 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
1474 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
1475 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
1476 <description>&lt;p&gt;Some years ago, in 2016, I
1477 &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
1478 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
1479 It would provide messaging without any central server coordinating the
1480 system and without requiring all users to register a phone number or
1481 own a mobile phone. Back then, I could not get it to work, and put it
1482 aside until it had seen more development. A few days ago I decided to
1483 give it another try, and am happy to report that this time I am able
1484 to not only send and receive messages, but also place audio and video
1485 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
1486
1487 &lt;p&gt;The Ring system changed name earlier this year to
1488 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
1489 tried doing web search for &#39;ring&#39; when I discovered it for the first
1490 time, and can only applaud this change as it is impossible to find
1491 something called Ring among the noise of other uses of that word. Now
1492 you can search for &#39;jami&#39; and this client and
1493 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
1494 least on duckduckgo.&lt;/p&gt;
1495
1496 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
1497 calls, and try to send them directly between the communicating parties
1498 if possible. If this proves impossible (for example if both ends are
1499 behind NAT), it will use a central SIP TURN server maintained by the
1500 Jami project. Jami can also be a normal SIP client. If the SIP
1501 server is unencrypted, the audio and video calls will also be
1502 unencrypted. This is as far as I know the only case where Jami will
1503 do anything without encryption.&lt;/p&gt;
1504
1505 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
1506 Android, iOS, and Android TV. It is included in Debian already. Jami
1507 also work for those using F-Droid without any Google connections,
1508 while Signal do not.
1509 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
1510 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
1511 distributed hash table (DHT) system (similar to BitTorrent) running
1512 over UDP. On one of the networks I use, I discovered Jami failed to
1513 work. I tracked this down to the fact that incoming UDP packages
1514 going to ports 1-49999 were blocked, and the DHT would pick a random
1515 port and end up in the low range most of the time. After talking to
1516 the developers, I solved this by enabling the dhtproxy in the
1517 settings, thus using TCP to talk to a central DHT proxy instead of
1518
1519 peering directly with others. I&#39;ve been told the developers are
1520 working on allowing DHT to use TCP to avoid this problem. I also ran
1521 into a problem when trying to talk to the version of Ring included in
1522 Debian Stable (Stretch). Apparently the protocol changed between
1523 beta2 and the current version, making these clients incompatible.
1524 Hopefully the protocol will not be made incompatible in the
1525 future.&lt;/p&gt;
1526
1527 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
1528 came across another communication platform I have not tested yet. The
1529 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
1530 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
1531 become the topic of a future blog post.&lt;/p&gt;
1532
1533 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1534 activities, please send Bitcoin donations to my address
1535 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1536 </description>
1537 </item>
1538
1539 <item>
1540 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
1541 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
1542 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
1543 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
1544 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
1545 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
1546 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
1547 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1548 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1549 nye versjonen kom på nyåret, og ble
1550 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
1551 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
1552 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1553 måtte justeres, men ikke noe alvorlig. Har oppdatert
1554 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
1555 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
1556
1557 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1558 å spille for oss som liker slikt. :)&lt;/p&gt;
1559
1560 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1561 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1562 til min adresse
1563 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
1564 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1565 </description>
1566 </item>
1567
1568 <item>
1569 <title>Debian now got everything you need to program Micro:bit</title>
1570 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
1571 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
1572 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
1573 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
1574 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
1575 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
1576 thanks to the hard work of Nick Morrott and the Debian python
1577 packaging team. The micro:bit project recommend the mu-editor to
1578 program the microcomputer, as this editor will take care of all the
1579 machinery required to injekt/flash micropython alongside the program
1580 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
1581
1582 &lt;p&gt;There are three main pieces involved. The first to enter Debian
1583 was
1584 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
1585 which was accepted into the archive 2019-01-12. The next one was
1586 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
1587 showed up 2019-01-13. The final and hardest part to to into the
1588 archive was
1589 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
1590 which needed to get its build system and dependencies into Debian
1591 before it was accepted 2019-01-20. The last one is already in Debian
1592 Unstable and should enter Debian Testing / Buster in three days. This
1593 all allow any user of the micro:bit to get going by simply running
1594 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
1595 Buster is released as stable, all the users of Debian stable will be
1596 catered for.&lt;/p&gt;
1597
1598 &lt;p&gt;As a minor final touch, I added rules to
1599 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
1600 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
1601 package. This make sure any user of the isenkram desktop daemon will
1602 get a popup suggesting to install mu-editor then the USB cable from
1603 the micro:bit is inserted for the first time.&lt;/p&gt;
1604
1605 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
1606
1607 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1608 activities, please send Bitcoin donations to my address
1609 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1610 </description>
1611 </item>
1612
1613 <item>
1614 <title>Learn to program with Minetest on Debian</title>
1615 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
1616 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
1617 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
1618 <description>&lt;p&gt;A fun way to learn how to program
1619 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
1620 instructions in the book
1621 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
1622 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
1623 who like to play with Minecraft. The book uses a Python library to
1624 talk to a TCP/IP socket with an API accepting build instructions and
1625 providing information about the current players in a Minecraft world.
1626 The TCP/IP API was first created for the Minecraft implementation for
1627 Raspberry Pi, and has since been ported to some server versions of
1628 Minecraft. The book contain recipes for those using Windows, MacOSX
1629 and Raspian. But a little known fact is that you can follow the same
1630 recipes using the free software construction game
1631 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1632
1633 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1634 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1635 use the Python programs coded to talk to Minecraft with Minetest too.
1636 I
1637 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1638 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1639 FTP masters NEW queue, learning to program Python with Minetest on
1640 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1641 maintained as part of the Debian Games team, and
1642 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1643 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1644 Salsa.&lt;/p&gt;
1645
1646 &lt;p&gt;You will most likely need to install several of the Minetest
1647 modules in Debian for the examples included with the library to work
1648 well, as there are several blocks used by the example scripts that are
1649 provided via modules in Minetest. Without the required blocks, a
1650 simple stone block is used instead. My initial testing with a analog
1651 clock did not get gold arms as instructed in the python library, but
1652 instead used stone arms.&lt;/p&gt;
1653
1654 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1655 Minecraft, but were unable to find any working recipes. The
1656 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1657 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1658 working with a standalone Minecraft server setup. Are there any
1659 options to use with the normal desktop version?&lt;/p&gt;
1660
1661 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1662 activities, please send Bitcoin donations to my address
1663 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1664 </description>
1665 </item>
1666
1667 <item>
1668 <title>Time for an official MIME type for patches?</title>
1669 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1670 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1671 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1672 <description>&lt;p&gt;As part of my involvement in
1673 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1674 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1675 emails into a test instance of the archive to see how well this would
1676 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1677 notmuch email database&lt;/a&gt;, all public emails sent to me via
1678 @lists.debian.org, giving me a set of around 216 000 emails to import.
1679 In the process, I had a look at the various attachments included in
1680 these emails, to figure out what to do with attachments, and noticed
1681 that one of the most common attachment formats do not have
1682 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1683 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1684 diff, ie the input for patch, is on the top 10 list of formats
1685 included in these emails. At the moment people seem to use either
1686 text/x-patch or text/x-diff, but neither is officially registered. It
1687 would be better if one official MIME type were registered and used
1688 everywhere.&lt;/p&gt;
1689
1690 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1691 up the topic on
1692 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1693 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1694 which MIME type to use as the official for patch files, or involved in
1695 making software using a MIME type for patches, perhaps you would like
1696 to join the discussion?&lt;/p&gt;
1697
1698 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1699 activities, please send Bitcoin donations to my address
1700 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1701 </description>
1702 </item>
1703
1704 <item>
1705 <title>Automatic Google Drive sync using grive in Debian</title>
1706 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1707 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1708 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1709 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1710 rescue the remains, I helped set up automatic sync with Google Drive.
1711 I did not find any sensible Debian package handling this
1712 automatically, so I rebuild the grive2 source from
1713 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1714 task and added a autostart desktop entry and a small shell script to
1715 run in the background while the user is logged in to do the sync.
1716 Here is a sketch of the setup for future reference.&lt;/p&gt;
1717
1718 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1719 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1720 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1721 to start the sync when the user log in:&lt;/p&gt;
1722
1723 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1724 [Desktop Entry]
1725 Name=Google drive autosync
1726 Type=Application
1727 Exec=/home/user/bin/grive-sync
1728 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1729
1730 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1731 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1732
1733 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1734 #!/bin/sh
1735 set -e
1736 cd ~/
1737 cleanup() {
1738 if [ &quot;$syncpid&quot; ] ; then
1739 kill $syncpid
1740 fi
1741 }
1742 trap cleanup EXIT INT QUIT
1743 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1744 syncpdi=$!
1745 while true; do
1746 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1747 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1748 exit 1
1749 fi
1750 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1751 /usr/lib/grive/grive-sync.sh sync googledrive
1752 fi
1753 sleep 300
1754 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
1755 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1756
1757 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
1758 GNU GPL v2 licensed (or any later version, at your leisure), but I
1759 doubt this code is possible to claim copyright on.&lt;/p&gt;
1760
1761 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1762 activities, please send Bitcoin donations to my address
1763 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1764 </description>
1765 </item>
1766
1767 <item>
1768 <title>Using the Kodi API to play Youtube videos</title>
1769 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
1770 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
1771 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
1772 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
1773 tell it to play a youtube URL I received in a chat, without having to
1774 insert search terms using the on-screen keyboard. After searching the
1775 web for API access to the Youtube plugin and testing a bit, I managed
1776 to find a recipe that worked. If you got a kodi instance with its API
1777 available from http://kodihost/jsonrpc, you can try the following to
1778 have check out a nice cover band.&lt;/p&gt;
1779
1780 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
1781 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
1782 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
1783 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
1784 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1785
1786 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
1787 first argument. It can now handle direct video links, youtube links
1788 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
1789 Chromecast. :)&lt;/p&gt;
1790
1791 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1792 activities, please send Bitcoin donations to my address
1793 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1794 </description>
1795 </item>
1796
1797 <item>
1798 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
1799 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
1800 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
1801 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
1802 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
1803 with my family using a self hosted solution, as it is unacceptable to
1804 place images from my personal life under the control of strangers
1805 working for data hoarders like Google or Dropbox. The last few days I
1806 have drafted an approach that might work out, and I would like to
1807 share it with you. I would like to publish images on a server under
1808 my control, and point some Internet connected display units using some
1809 free and open standard to the images I published. As my primary
1810 language is not limited to ASCII, I need to store metadata using
1811 UTF-8. Many years ago, I hoped to find a digital photo frame capable
1812 of reading a RSS feed with image references (aka using the
1813 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
1814 of such frames. In the end I gave up that approach.&lt;/p&gt;
1815
1816 &lt;p&gt;Some months ago, I discovered that
1817 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
1818 read images from a RSS feed, and used it to set up a screen saver on
1819 my home info screen, showing images from the Daily images feed from
1820 NASA. This proved to work well. More recently I discovered that
1821 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
1822 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
1823 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
1824 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
1825 screen saver capable of reading a RSS feed with images and news. For
1826 fun, I used it this summer to test Kodi on my parents TV by hooking up
1827 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1828 screen saver showing selected pictures from my selection.&lt;/p&gt;
1829
1830 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
1831 a RSS feed for the Kodi instance. I adjusted my &lt;a
1832 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
1833 /var/www/html/privatepictures/, wrote a small Perl script to extract
1834 title and description metadata from the photo files and generate the
1835 RSS file. I ended up using Perl instead of python, as the
1836 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1837 tags I ended up using, while python3-exif did not. The relevant EXIF
1838 tags only support ASCII, so I had to find better alternatives. XMP
1839 seem to have the support I need.&lt;/p&gt;
1840
1841 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
1842 use tags that can be easily added/updated using normal free software
1843 photo managing software. I ended up using the tags set using this
1844 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
1845
1846 &lt;blockquote&gt;&lt;pre&gt;
1847 exiftool -headline=&#39;The RSS image title&#39; \
1848 -description=&#39;The RSS image description.&#39; \
1849 -subject+=for-family photo.jpeg
1850 &lt;/pre&gt;&lt;/blockquote&gt;
1851
1852 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
1853 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
1854 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
1855 shared with my family. Images with this keyword set are located and
1856 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
1857
1858 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
1859 suggestions.&lt;/p&gt;
1860
1861 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1862 activities, please send Bitcoin donations to my address
1863 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1864 </description>
1865 </item>
1866
1867 <item>
1868 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
1869 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
1870 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
1871 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
1872 <description>&lt;p&gt;Last night, I wrote
1873 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
1874 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
1875 During the day I received valuable feedback, and thanks to the
1876 suggestions I have been able to rewrite the recipe into a much simpler
1877 approach requiring no setup at all. It is a single script that take
1878 care of it all.&lt;/p&gt;
1879
1880 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
1881 desktop and stream it to Kodi. This fixed the video quality issue I
1882 saw initially. It further removes the need to add a m3u file on the
1883 Kodi machine, as it instead connects to
1884 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
1885 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
1886 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1887 the script below, run it with the DNS name or IP address of the kodi
1888 server to stream to as the only argument, and watch your screen show
1889 up on the Kodi screen. Note, it depend on multicast on the local
1890 network, so if you need to stream outside the local network, the
1891 script must be modified. Also note, I have no idea if audio work, as
1892 I only care about the picture part.&lt;/p&gt;
1893
1894 &lt;blockquote&gt;&lt;pre&gt;
1895 #!/bin/sh
1896 #
1897 # Stream the Linux desktop view to Kodi. See
1898 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1899 # for backgorund information.
1900
1901 # Make sure the stream is stopped in Kodi and the gstreamer process is
1902 # killed if something go wrong (for example if curl is unable to find the
1903 # kodi server). Do the same when interrupting this script.
1904 kodicmd() {
1905 host=&quot;$1&quot;
1906 cmd=&quot;$2&quot;
1907 params=&quot;$3&quot;
1908 curl --silent --header &#39;Content-Type: application/json&#39; \
1909 --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; \
1910 &quot;http://$host/jsonrpc&quot;
1911 }
1912 cleanup() {
1913 if [ -n &quot;$kodihost&quot; ] ; then
1914 # Stop the playing when we end
1915 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
1916 jq .result[].playerid)
1917 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
1918 fi
1919 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
1920 kill &quot;$gstpid&quot;
1921 fi
1922 }
1923 trap cleanup EXIT INT
1924
1925 if [ -n &quot;$1&quot; ]; then
1926 kodihost=$1
1927 shift
1928 else
1929 kodihost=kodi.local
1930 fi
1931
1932 mcast=239.255.0.1
1933 mcastport=1234
1934 mcastttl=1
1935
1936 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
1937 cut -d&quot; &quot; -f2|head -1)
1938 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1939 videoconvert ! queue2 ! \
1940 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1941 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1942 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1943 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
1944 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1945 &gt; /dev/null 2&gt;&amp;1 &amp;
1946 gstpid=$!
1947
1948 # Give stream a second to get going
1949 sleep 1
1950
1951 # Ask kodi to start streaming using its JSON-RPC API
1952 kodicmd &quot;$kodihost&quot; Player.Open \
1953 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
1954
1955 # wait for gst to end
1956 wait &quot;$gstpid&quot;
1957 &lt;/pre&gt;&lt;/blockquote&gt;
1958
1959 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
1960
1961 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1962 activities, please send Bitcoin donations to my address
1963 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1964 </description>
1965 </item>
1966
1967 <item>
1968 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
1969 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
1970 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
1971 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
1972 <description>&lt;p&gt;PS: See
1973 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
1974 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
1975
1976 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
1977 my projector connected to Kodi. I sadly had to admit that I had no
1978 idea, as it was a task I never had tried. Since then, I have been
1979 looking for a way to do so, preferable without much extra software to
1980 install on either side. Today I found a way that seem to kind of
1981 work. Not great, but it is a start.&lt;/p&gt;
1982
1983 &lt;p&gt;I had a look at several approaches, for example
1984 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
1985 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
1986 local storage enough to store the stream locally. This is not going
1987 to work well for me, lacking enough free space, and it would
1988 impossible for my friend to get working.&lt;/p&gt;
1989
1990 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
1991 video stream that Kodi could play. Preferably using
1992 broadcast/multicast, to avoid having to change any setup on the Kodi
1993 side when starting such stream. Unfortunately, the only recipe I
1994 could find using multicast used the rtp protocol, and this protocol
1995 seem to not be supported by Kodi.&lt;/p&gt;
1996
1997 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
1998 have to specify the IP address of the streaming machine in both the
1999 sending command and the file on the Kodi server. But it is showing my
2000 desktop, and thus allow us to have a shared look on the big screen at
2001 the programs I work on.&lt;/p&gt;
2002
2003 &lt;p&gt;I did not spend much time investigating codeces. I combined the
2004 rtp and rtsp recipes from
2005 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
2006 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
2007 this working on the desktop/streaming end.&lt;/p&gt;
2008
2009 &lt;blockquote&gt;&lt;pre&gt;
2010 vlc screen:// --sout \
2011 &#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;
2012 &lt;/pre&gt;&lt;/blockquote&gt;
2013
2014 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
2015 same IP address:&lt;/p&gt;
2016
2017 &lt;blockquote&gt;&lt;pre&gt;
2018 echo rtsp://192.168.11.4:8080/test.sdp \
2019 &gt; /storage/videos/screenstream.m3u
2020 &lt;/pre&gt;&lt;/blockquote&gt;
2021
2022 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
2023 as I can tell the IP must be hardcoded for this to work. In other
2024 words, if someone elses machine is going to do the steaming, you have
2025 to update screenstream.m3u on the Kodi machine and adjust the vlc
2026 recipe. To get started, locate the file in Kodi and select the m3u
2027 file while the VLC stream is running. The desktop then show up in my
2028 big screen. :)&lt;/p&gt;
2029
2030 &lt;p&gt;When using the same technique to stream a video file with audio,
2031 the audio quality is really bad. No idea if the problem is package
2032 loss or bad parameters for the transcode. I do not know VLC nor Kodi
2033 enough to tell.&lt;/p&gt;
2034
2035 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
2036 succestions and reminded me about an important step. The &quot;screen:&quot;
2037 input source is only available once the vlc-plugin-access-extra
2038 package is installed on Debian. Without it, you will see this error
2039 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
2040 for details.&quot; He further found that it is possible to drop some parts
2041 of the VLC command line to reduce the amount of hardcoded information.
2042 It is also useful to consider using cvlc to avoid having the VLC
2043 window in the desktop view. In sum, this give us this command line on
2044 the source end
2045
2046 &lt;blockquote&gt;&lt;pre&gt;
2047 cvlc screen:// --sout \
2048 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
2049 &lt;/pre&gt;&lt;/blockquote&gt;
2050
2051 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2052
2053 &lt;blockquote&gt;&lt;pre&gt;
2054 echo rtsp://192.168.11.4:8080/ \
2055 &gt; /storage/videos/screenstream.m3u
2056 &lt;/pre&gt;&lt;/blockquote&gt;
2057
2058 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
2059 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
2060 audio quality, so I guess the issue is in the input or transcoding
2061 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
2062 parameters to use more bandwidth, but it did not make a
2063 difference.&lt;/p&gt;
2064
2065 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
2066 gstreamer instead of VLC, and this proved to work great! He also
2067 provided me with the trick to get Kodi to use a multicast stream as
2068 its source. By using this monstrous oneliner, I can stream my desktop
2069 with good video quality in reasonable framerate to the 239.255.0.1
2070 multicast address on port 1234:
2071
2072 &lt;blockquote&gt;&lt;pre&gt;
2073 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
2074 videoconvert ! queue2 ! \
2075 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
2076 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
2077 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
2078 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
2079 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
2080 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
2081 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2082 &lt;/pre&gt;&lt;/blockquote&gt;
2083
2084 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2085
2086 &lt;blockquote&gt;&lt;pre&gt;
2087 echo udp://@239.255.0.1:1234 \
2088 &gt; /storage/videos/screenstream.m3u
2089 &lt;/pre&gt;&lt;/blockquote&gt;
2090
2091 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
2092 pick the one you need. This approach will of course lead to trouble
2093 if more than one source uses the same multicast port and address.
2094 Note the ttl-mc=1 setting, which limit the multicast packages to the
2095 local network. If the value is increased, your screen will be
2096 broadcasted further, one network &quot;hop&quot; for each increase (read up on
2097 multicast to learn more. :)!&lt;/p&gt;
2098
2099 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
2100 could use this VLC command to stream to the same multicast address.
2101 The image quality is way better than the rtsp approach, but gstreamer
2102 seem to be doing a better job.&lt;/p&gt;
2103
2104 &lt;blockquote&gt;&lt;pre&gt;
2105 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;
2106 &lt;/pre&gt;&lt;/blockquote&gt;
2107
2108 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2109 activities, please send Bitcoin donations to my address
2110 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2111 </description>
2112 </item>
2113
2114 <item>
2115 <title>What is the most supported MIME type in Debian in 2018?</title>
2116 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
2117 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
2118 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
2119 <description>&lt;p&gt;Five years ago,
2120 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
2121 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
2122 analysing the desktop files in all packages in the archive. Since
2123 then, the DEP-11 AppStream system has been put into production, making
2124 the task a lot easier. This made me want to repeat the measurement,
2125 to see how much things changed. Here are the new numbers, for
2126 unstable only this time:
2127
2128 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2129
2130 &lt;pre&gt;
2131 count MIME type
2132 ----- -----------------------
2133 56 image/jpeg
2134 55 image/png
2135 49 image/tiff
2136 48 image/gif
2137 39 image/bmp
2138 38 text/plain
2139 37 audio/mpeg
2140 34 application/ogg
2141 33 audio/x-flac
2142 32 audio/x-mp3
2143 30 audio/x-wav
2144 30 audio/x-vorbis+ogg
2145 29 image/x-portable-pixmap
2146 27 inode/directory
2147 27 image/x-portable-bitmap
2148 27 audio/x-mpeg
2149 26 application/x-ogg
2150 25 audio/x-mpegurl
2151 25 audio/ogg
2152 24 text/html
2153 &lt;/pre&gt;
2154
2155 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
2156 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
2157 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
2158
2159 &lt;p&gt;It is interesting to see how image formats have passed text/plain
2160 as the most announced supported MIME type. These days, thanks to the
2161 AppStream system, if you run into a file format you do not know, and
2162 want to figure out which packages support the format, you can find the
2163 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
2164 look up all packages announcing support for this format in their
2165 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
2166 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
2167 me, want to know which packages support inode/directory, you can get a
2168 list like this:&lt;/p&gt;
2169
2170 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2171 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2172 Package: anjuta
2173 Package: audacious
2174 Package: baobab
2175 Package: cervisia
2176 Package: chirp
2177 Package: dolphin
2178 Package: doublecmd-common
2179 Package: easytag
2180 Package: enlightenment
2181 Package: ephoto
2182 Package: filelight
2183 Package: gwenview
2184 Package: k4dirstat
2185 Package: kaffeine
2186 Package: kdesvn
2187 Package: kid3
2188 Package: kid3-qt
2189 Package: nautilus
2190 Package: nemo
2191 Package: pcmanfm
2192 Package: pcmanfm-qt
2193 Package: qweborf
2194 Package: ranger
2195 Package: sirikali
2196 Package: spacefm
2197 Package: spacefm
2198 Package: vifm
2199 %
2200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2201
2202 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
2203 format is not yet supported by any package in Debian:&lt;/p&gt;
2204
2205 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2206 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2207 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
2208 %
2209 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2210
2211 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
2212 format:&lt;/p&gt;
2213
2214 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2215 % appstreamcli what-provides mimetype application/sla|grep Package
2216 Package: cura
2217 Package: meshlab
2218 Package: printrun
2219 %
2220 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2221
2222 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
2223
2224 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2225 activities, please send Bitcoin donations to my address
2226 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2227 </description>
2228 </item>
2229
2230 <item>
2231 <title>Debian APT upgrade without enough free space on the disk...</title>
2232 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
2233 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
2234 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
2235 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2236 for a while, and when I need to update it there is not enough free
2237 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
2238 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
2239 upgrade only some of the packages in one batch, until the amount of
2240 packages to download fall below the amount of free space available.
2241 Today, I had about 500 packages to upgrade, and after a while I got
2242 tired of trying to install chunks of packages manually. I concluded
2243 that I did not have the spare hours required to complete the task, and
2244 decided to see if I could automate it. I came up with this small
2245 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
2246
2247 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2248 #!/bin/sh
2249 #
2250 # Upgrade packages when the disk is too full to upgrade every
2251 # upgradable package in one lump. Fetching packages to upgrade using
2252 # apt, and then installing using dpkg, to avoid changing the package
2253 # flag for manual/automatic.
2254
2255 set -e
2256
2257 ignore() {
2258 if [ &quot;$1&quot; ]; then
2259 grep -v &quot;$1&quot;
2260 else
2261 cat
2262 fi
2263 }
2264
2265 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
2266 echo &quot;Upgrading $p&quot;
2267 apt clean
2268 apt install --download-only -y $p
2269 for f in /var/cache/apt/archives/*.deb; do
2270 if [ -e &quot;$f&quot; ]; then
2271 dpkg -i /var/cache/apt/archives/*.deb
2272 break
2273 fi
2274 done
2275 done
2276 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2277
2278 &lt;p&gt;The script will extract the list of packages to upgrade, try to
2279 download the packages needed to upgrade one package, install the
2280 downloaded packages using dpkg. The idea is to upgrade packages
2281 without changing the APT mark for the package (ie the one recording of
2282 the package was manually requested or pulled in as a dependency). To
2283 use it, simply run it as root from the command line. If it fail, try
2284 &#39;apt install -f&#39; to clean up the mess and run the script again. This
2285 might happen if the new packages conflict with one of the old
2286 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
2287
2288 &lt;p&gt;It take one option, a package to ignore in the list of packages to
2289 upgrade. The option to ignore a package is there to be able to skip
2290 the packages that are simply too large to unpack. Today this was
2291 &#39;ghc&#39;, but I have run into other large packages causing similar
2292 problems earlier (like TeX).&lt;/p&gt;
2293
2294 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
2295 alternative ways to handle this. The &quot;unattended-upgrades
2296 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
2297 each package to upgrade, and then upgrade them in order, smallest set
2298 first. It might be a better option than my above mentioned script.
2299 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
2300 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
2301
2302 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2303 activities, please send Bitcoin donations to my address
2304 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2305 </description>
2306 </item>
2307
2308 <item>
2309 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
2310 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
2311 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
2312 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
2313 <description>&lt;p&gt;A new version of the
2314 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
2315 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
2316 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2317 useful. It was uploaded the last few days, and the last update will
2318 enter testing tomorrow. See the
2319 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
2320 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
2321 was announced 6 days ago. We will try to get it into Debian as
2322 well.&lt;/p&gt;
2323
2324 &lt;p&gt;More information related to 3D printing is available on the
2325 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
2326 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
2327 in Debian.&lt;/p&gt;
2328
2329 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2330 activities, please send Bitcoin donations to my address
2331 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2332 </description>
2333 </item>
2334
2335 <item>
2336 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
2337 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
2338 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
2339 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
2340 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
2341 that the nice and user friendly 3D printer slicer software Cura just
2342 entered Debian Unstable. It consist of five packages,
2343 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
2344 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
2345 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
2346 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
2347 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
2348 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
2349 two, uranium and cura, entered Unstable yesterday. This should make
2350 it easier for Debian users to print on at least the Ultimaker class of
2351 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
2352 make life easier for at least me. :)&lt;/p&gt;
2353
2354 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
2355 happy to assist him in sponsoring the packages. With the introduction
2356 of Cura, Debian is up to three 3D printer slicers at your service,
2357 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
2358 printer, give it a go. :)&lt;/p&gt;
2359
2360 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
2361 team, flocking together on the
2362 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
2363 mailing list and the
2364 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
2365 IRC channel.&lt;/p&gt;
2366
2367 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
2368 version 3.0.3 and then update the entire set of packages to version
2369 3.1.0 which showed up the last few days.&lt;/p&gt;
2370 </description>
2371 </item>
2372
2373 <item>
2374 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
2375 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
2376 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
2377 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
2378 <description>&lt;p&gt;At my nearby maker space,
2379 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
2380 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
2381 on Windows and MacOS X than Linux, because the software involved had
2382 to be manually compiled and set up on Linux while premade packages
2383 worked out of the box on Windows and MacOS X. I found this annoying,
2384 as the software involved,
2385 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
2386 and should be trivial to get up and running on Linux if someone took
2387 the time to package it for the relevant distributions. I even found
2388 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
2389 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
2390 never resulted in the software showing up in Debian. So a few days
2391 ago I offered my help to try to improve the situation.&lt;/p&gt;
2392
2393 &lt;p&gt;Now I am very happy to see that all the packages required by a
2394 working Cura in Debian are uploaded into Debian and waiting in the NEW
2395 queue for the ftpmasters to have a look. You can track the progress
2396 on
2397 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
2398 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
2399
2400 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
2401 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
2402 queue&lt;/a&gt; while we work up updating the packages to the latest
2403 upstream version.&lt;/p&gt;
2404
2405 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
2406 to use and was unable to configure correctly for Ultimaker 2+ in the
2407 short time I spent on it, are already in Debian. If you are looking
2408 for 3D printer &quot;slicers&quot; and want something already available in
2409 Debian, check out
2410 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
2411 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
2412 The latter is a fork of the former.&lt;/p&gt;
2413
2414 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2415 activities, please send Bitcoin donations to my address
2416 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2417 </description>
2418 </item>
2419
2420 <item>
2421 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
2422 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
2423 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
2424 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
2425 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
2426 mobile cell towers. And this radio chatter is available for anyone
2427 with a radio receiver capable of receiving them. Details about the
2428 mobile phones with very good accuracy is of course collected by the
2429 phone companies, but this is not the topic of this blog post. The
2430 mobile phone radio chatter make it possible to figure out when a cell
2431 phone is nearby, as it include the SIM card ID (IMSI). By paying
2432 attention over time, one can see when a phone arrive and when it leave
2433 an area. I believe it would be nice to make this information more
2434 available to the general public, to make more people aware of how
2435 their phones are announcing their whereabouts to anyone that care to
2436 listen.&lt;/p&gt;
2437
2438 &lt;p&gt;I am very happy to report that we managed to get something
2439 visualizing this information up and running for
2440 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
2441 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2442 library. The solution is based on the
2443 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
2444 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
2445 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
2446 Sone from the Computer Science department of the University of
2447 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
2448 IMSIs) as dots in a web browser graph, with lines to the dot
2449 representing mobile base station it is talking to. It was working in
2450 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
2451
2452 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
2453 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2454 connected and visualize the visible cell phone towers using an
2455 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
2456 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
2457 grgsm_livemon_headless processes from
2458 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
2459 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
2460
2461 &lt;p&gt;The frequencies to listen to, are identified using a slightly
2462 patched scan-and-livemon (to set the --args values for each receiver),
2463 and the Hopglass data is generated using the
2464 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
2465 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
2466 more than four SDRs working. There is also a geographical map trying
2467 to show the location of the base stations, but I believe their
2468 coordinates are hardcoded to some random location in Germany, I
2469 believe. The code should be replaced with code to look up location in
2470 a text file, a sqlite database or one of the online databases
2471 mentioned in
2472 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
2473 issue for the topic&lt;/a&gt;.
2474
2475 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
2476 </description>
2477 </item>
2478
2479 <item>
2480 <title>Easier recipe to observe the cell phones around you</title>
2481 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
2482 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
2483 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
2484 <description>&lt;p&gt;A little more than a month ago I wrote
2485 &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
2486 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2487 to nearby mobile phone base stations using Debian GNU/Linux and a
2488 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
2489 the location of people and equipment (like cars and trains) with an
2490 accuracy of a few kilometer. Since then we have worked to make the
2491 procedure even simpler, and it is now possible to do this without any
2492 manual frequency tuning and without building your own packages.&lt;/p&gt;
2493
2494 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
2495 package is now included in Debian testing and unstable, and the
2496 IMSI-catcher code no longer require root access to fetch and decode
2497 the GSM data collected using gr-gsm.&lt;/p&gt;
2498
2499 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
2500 clone of two python scripts:&lt;/p&gt;
2501
2502 &lt;ol&gt;
2503
2504 &lt;li&gt;Start with a Debian machine running the Buster version (aka
2505 testing).&lt;/li&gt;
2506
2507 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
2508 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
2509
2510 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
2511 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
2512
2513 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
2514
2515 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2516 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
2517 stations and start listening for GSM packages on one of them.&lt;/li&gt;
2518
2519 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2520 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
2521
2522 &lt;/ol&gt;
2523
2524 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
2525 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
2526 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
2527 work with RTL 8232 and other similar USB radio receivers you can get
2528 very cheaply
2529 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
2530 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
2531 and only use HackRF for fetching GSM data.&lt;/p&gt;
2532
2533 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
2534 frequencies at the time, so if you are going to track and count every
2535 cell phone around you, you need to listen to all the frequencies used.
2536 To listen to several frequencies, use the --numrecv argument to
2537 scan-and-livemon to use several receivers. Further, I am not sure if
2538 phones using 3G or 4G will show as talking GSM to base stations, so
2539 this approach might not see all phones around you. I typically see
2540 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
2541
2542 &lt;p&gt;I&#39;ve tried to run the scanner on a
2543 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
2544 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
2545 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
2546 stdout, I am told there it is caused by a buffer overflow between the
2547 radio and GNU Radio, caused by the program being unable to read the
2548 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
2549 where you started scan-and-livemon, you need a give the process more
2550 CPU power. Perhaps someone are able to optimize the code to a point
2551 where it become possible to set up RPi3 based GSM sniffers? I tried
2552 using Raspbian instead of Debian, but there seem to be something wrong
2553 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
2554 </description>
2555 </item>
2556
2557 <item>
2558 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
2559 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
2560 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
2561 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
2562 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
2563 web based ICT news magazine digi.no on
2564 &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
2565 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
2566 DVB-T software defined radios. The article refered to instructions
2567 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
2568 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;
2569
2570 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
2571 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2572 and the ask pybombs to fetch and build everything you need from
2573 scratch. I wanted to see if I could do the same on the most recent
2574 Debian packages, but this did not work because pybombs tried to build
2575 stuff that no longer build with the most recent openssl library or
2576 some other version skew problem. While trying to get this recipe
2577 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
2578 and the only piece of software dependency missing in Debian was the
2579 gr-gsm package. I also found out that the lead upstream developer of
2580 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2581 Debian packages provided in an Ubuntu PPA repository. All I needed to
2582 do was to dget the Debian source package and built it.&lt;/p&gt;
2583
2584 &lt;p&gt;The IMSI collector is a python script listening for packages on the
2585 loopback network device and printing to the terminal some specific GSM
2586 packages with IMSI numbers in them. The code is fairly short and easy
2587 to understand. The reason this work is because gr-gsm include a tool
2588 to read GSM data from a software defined radio like a DVB-T USB stick
2589 and other software defined radios, decode them and inject them into a
2590 network device on your Linux machine (using the loopback device by
2591 default). This proved to work just fine, and I&#39;ve been testing the
2592 collector for a few days now.&lt;/p&gt;
2593
2594 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
2595
2596 &lt;ol&gt;
2597
2598 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
2599
2600 &lt;li&gt;build and install the gr-gsm package available from
2601 &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;
2602
2603 &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;
2604
2605 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
2606 where it was started is filled with a stream of text (meaning you
2607 found a GSM station).&lt;/li&gt;
2608
2609 &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;
2610
2611 &lt;/ol&gt;
2612
2613 &lt;p&gt;To make it even easier in the future to get this sniffer up and
2614 running, I decided to package
2615 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
2616 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
2617 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
2618 Luckily the gnuradio maintainer has promised to help me, as I do not
2619 know much about gnuradio stuff yet.&lt;/p&gt;
2620
2621 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
2622 commercial tools like
2623 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
2624 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
2625 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
2626 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
2627 more people realise how their whereabouts when carrying a cell phone
2628 is easily tracked. Seeing the data flow on the screen, realizing that
2629 I live close to a police station and knowing that the police is also
2630 wearing cell phones, I wonder how hard it would be for criminals to
2631 track the position of the police officers to discover when there are
2632 police near by, or for foreign military forces to track the location
2633 of the Norwegian military forces, or for anyone to track the location
2634 of government officials...&lt;/p&gt;
2635
2636 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2637 script mentioned above is only a fraction of the data broadcasted on
2638 the GSM network. It will only collect one frequency at the time,
2639 while a typical phone will be using several frequencies, and not all
2640 phones will be using the frequencies tracked by the grgsm_livemod
2641 program. Also, there is a lot of radio chatter being ignored by the
2642 simple_IMSI-catcher script, which would be collected by extending the
2643 parser code. I wonder if gr-gsm can be set up to listen to more than
2644 one frequency?&lt;/p&gt;
2645 </description>
2646 </item>
2647
2648 <item>
2649 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2650 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2651 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2652 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2653 <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;
2654
2655 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2656 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2657 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2658 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2659 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2660 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2661 price. The book is also available for download in electronic form as
2662 PDF, EPUB and Mobipocket, as can be
2663 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2664 as a web page&lt;/a&gt;.&lt;/p&gt;
2665
2666 &lt;p&gt;This is the second book I publish (the first was the book
2667 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2668 in
2669 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2670 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2671 and
2672 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2673 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2674 project. I hope
2675 &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
2676 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2677 </description>
2678 </item>
2679
2680 <item>
2681 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2682 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2683 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2684 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2685 <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
2686 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2687 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2688 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2689 på om den fri oversetterløsningen
2690 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2691 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2692
2693 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2694
2695 &lt;blockquote&gt;
2696 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2697 rolle og muligheter til å håndtere internasjonale utfordringer, som
2698 for eksempel flykningekrisen.&lt;/p&gt;
2699
2700 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2701 på temaet:&lt;/p&gt;
2702 &lt;ol&gt;
2703 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2704 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2705 &lt;/ol&gt;
2706
2707 &lt;/blockquote&gt;
2708
2709 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2710
2711 &lt;blockquote&gt;
2712 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2713 andre aktørar og høve til å handtera internasjonale utfordringar, som
2714 til dømes *flykningekrisen.&lt;/p&gt;
2715
2716 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2717 temaet:&lt;/p&gt;
2718
2719 &lt;ol&gt;
2720 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2721 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2722 &lt;/ol&gt;
2723
2724 &lt;/blockquote&gt;
2725
2726 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2727 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2728 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2729 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2730 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2731 det er kanskje flisespikking. Det understreker vel bare at det alltid
2732 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2733 </description>
2734 </item>
2735
2736 <item>
2737 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2738 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2739 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2740 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2741 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2742 computers at the time, I often needed a way to detect if the machine
2743 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2744 file or directory affected by the hang, the process (and possibly the
2745 shell) will hang too. So you want to be able to detect this without
2746 risking the detection process getting stuck too. It has not been
2747 obvious how to do this. When the hang has lasted a while, it is
2748 possible to find messages like these in dmesg:&lt;/p&gt;
2749
2750 &lt;p&gt;&lt;blockquote&gt;
2751 nfs: server nfsserver not responding, still trying
2752 &lt;br&gt;nfs: server nfsserver OK
2753 &lt;/blockquote&gt;&lt;/p&gt;
2754
2755 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
2756 be sure looking in dmesg is going to work. If there are lots of other
2757 messages in dmesg the lines might have rotated out of site before they
2758 are noticed.&lt;/p&gt;
2759
2760 &lt;p&gt;While reading through the nfs client implementation in linux kernel
2761 code, I came across some statistics that seem to give a way to detect
2762 it. The om_timeouts sunrpc value in the kernel will increase every
2763 time the above log entry is inserted into dmesg. And after digging a
2764 bit further, I discovered that this value show up in
2765 /proc/self/mountstats on Linux.&lt;/p&gt;
2766
2767 &lt;p&gt;The mountstats content seem to be shared between files using the
2768 same file system context, so it is enough to check one of the
2769 mountstats files to get the state of the mount point for the machine.
2770 I assume this will not show lazy umounted NFS points, nor NFS mount
2771 points in a different process context (ie with a different filesystem
2772 view), but that does not worry me.&lt;/p&gt;
2773
2774 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
2775
2776 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2777 [...]
2778 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2779 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
2780 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
2781 age: 7863311
2782 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
2783 sec: flavor=1,pseudoflavor=1
2784 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
2785 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2786 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
2787 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2788 per-op statistics
2789 NULL: 0 0 0 0 0 0 0 0
2790 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2791 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
2792 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2793 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2794 READLINK: 125 125 0 20472 18620 0 1112 1118
2795 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2796 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2797 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
2798 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
2799 SYMLINK: 903 903 0 233428 245488 6 5865 5917
2800 MKNOD: 80 80 0 20148 21760 0 299 304
2801 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
2802 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
2803 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
2804 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
2805 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2806 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2807 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
2808 FSINFO: 2 2 0 232 328 0 1 1
2809 PATHCONF: 1 1 0 116 140 0 0 0
2810 COMMIT: 0 0 0 0 0 0 0 0
2811
2812 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2813 [...]
2814 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2815
2816 &lt;p&gt;The key number to look at is the third number in the per-op list.
2817 It is the number of NFS timeouts experiences per file system
2818 operation. Here 22 write timeouts and 5 access timeouts. If these
2819 numbers are increasing, I believe the machine is experiencing NFS
2820 hang. Unfortunately the timeout value do not start to increase right
2821 away. The NFS operations need to time out first, and this can take a
2822 while. The exact timeout value depend on the setup. For example the
2823 defaults for TCP and UDP mount points are quite different, and the
2824 timeout value is affected by the soft, hard, timeo and retrans NFS
2825 mount options.&lt;/p&gt;
2826
2827 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
2828 Enterprise Linux for getting the timeout count is to peek in /proc/.
2829 But according to
2830 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
2831 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
2832 command can be used to get these timeout values. But this do not work
2833 on Linux, as far as I can tell. I
2834 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
2835 but have not seen any replies yet.&lt;/p&gt;
2836
2837 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
2838 experiencing NFS hangs? Is there a way to detect which processes are
2839 affected? Is there a way to get the NFS mount going quickly once the
2840 network problem causing the NFS hang has been cleared? I would very
2841 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
2842 </description>
2843 </item>
2844
2845 <item>
2846 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
2847 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
2848 <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>
2849 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
2850 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
2851 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
2852 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
2853 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2854 we are working on the proof reading to ensure consistent language and
2855 use of correct computer science terms. The plan is to make the book
2856 available on paper, as well as in electronic form. For that to
2857 happen, the proof reading must be completed and all the figures need
2858 to be translated. If you want to help out, get in touch.&lt;/p&gt;
2859
2860 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
2861
2862 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
2863 pages) of the book created every morning is available for
2864 proofreading. If you find any errors, please
2865 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
2866 Weblate and correct the error&lt;/a&gt;. The
2867 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
2868 of the translation including figures&lt;/a&gt; is a useful source for those
2869 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
2870 </description>
2871 </item>
2872
2873 <item>
2874 <title>Unlimited randomness with the ChaosKey?</title>
2875 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
2876 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
2877 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
2878 <description>&lt;p&gt;A few days ago I ordered a small batch of
2879 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
2880 USB dongle for generating entropy created by Bdale Garbee and Keith
2881 Packard. Yesterday it arrived, and I am very happy to report that it
2882 work great! According to its designers, to get it to work out of the
2883 box, you need the Linux kernel version 4.1 or later. I tested on a
2884 Debian Stretch machine (kernel version 4.9), and there it worked just
2885 fine, increasing the available entropy very quickly. I wrote a small
2886 test oneliner to test. It first print the current entropy level,
2887 drain /dev/random, and then print the entropy level for five seconds.
2888 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
2889
2890 &lt;blockquote&gt;&lt;pre&gt;
2891 % cat /proc/sys/kernel/random/entropy_avail; \
2892 dd bs=1M if=/dev/random of=/dev/null count=1; \
2893 for n in $(seq 1 5); do \
2894 cat /proc/sys/kernel/random/entropy_avail; \
2895 sleep 1; \
2896 done
2897 300
2898 0+1 oppføringer inn
2899 0+1 oppføringer ut
2900 28 byte kopiert, 0,000264565 s, 106 kB/s
2901 4
2902 8
2903 12
2904 17
2905 21
2906 %
2907 &lt;/pre&gt;&lt;/blockquote&gt;
2908
2909 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
2910 application requiring random bits (like a HTTPS enabled web server)
2911 will halt and wait for more entrpy. And here is the situation with
2912 the ChaosKey inserted:&lt;/p&gt;
2913
2914 &lt;blockquote&gt;&lt;pre&gt;
2915 % cat /proc/sys/kernel/random/entropy_avail; \
2916 dd bs=1M if=/dev/random of=/dev/null count=1; \
2917 for n in $(seq 1 5); do \
2918 cat /proc/sys/kernel/random/entropy_avail; \
2919 sleep 1; \
2920 done
2921 1079
2922 0+1 oppføringer inn
2923 0+1 oppføringer ut
2924 104 byte kopiert, 0,000487647 s, 213 kB/s
2925 433
2926 1028
2927 1031
2928 1035
2929 1038
2930 %
2931 &lt;/pre&gt;&lt;/blockquote&gt;
2932
2933 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
2934 someone want to buy one here in Norway. :)&lt;/p&gt;
2935
2936 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
2937 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
2938 recording illuminating&lt;/a&gt;. It explains exactly what the source of
2939 randomness is, if you are unable to spot it from the schema drawing
2940 available from the ChaosKey web site linked at the start of this blog
2941 post.&lt;/p&gt;
2942 </description>
2943 </item>
2944
2945 <item>
2946 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
2947 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
2948 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
2949 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
2950 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
2951 web servers, and who own the network equipment it is flowing through?
2952 It is possible to get a glimpse of this from using traceroute, but it
2953 is hard to find all the details. Many years ago, I wrote a system to
2954 map the Norwegian Internet (trying to figure out if our plans for a
2955 network game service would get low enough latency, and who we needed
2956 to talk to about setting up game servers close to the users. Back
2957 then I used traceroute output from many locations (I asked my friends
2958 to run a script and send me their traceroute output) to create the
2959 graph and the map. The output from traceroute typically look like
2960 this:
2961
2962 &lt;p&gt;&lt;pre&gt;
2963 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
2964 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
2965 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
2966 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
2967 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
2968 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
2969 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
2970 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
2971 8 * * *
2972 9 * * *
2973 [...]
2974 &lt;/pre&gt;&lt;/p&gt;
2975
2976 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
2977 network equipment involved in getting the data traffic from me to the
2978 www.stortinget.no server, and how long it took in milliseconds for a
2979 package to reach the equipment and return to me. Three packages are
2980 sent, and some times the packages do not follow the same path. This
2981 is shown for hop 5, where three different IP addresses replied to the
2982 traceroute request.&lt;/p&gt;
2983
2984 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
2985 implementations I use are traceroute (using ICMP packages) mtr (can do
2986 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2987 traceroute and a lot of other capabilities). All of them are easily
2988 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
2989
2990 &lt;p&gt;This time around, I wanted to know the geographic location of
2991 different route points, to visualize how visiting a web page spread
2992 information about the visit to a lot of servers around the globe. The
2993 background is that a web site today often will ask the browser to get
2994 from many servers the parts (for example HTML, JSON, fonts,
2995 JavaScript, CSS, video) required to display the content. This will
2996 leak information about the visit to those controlling these servers
2997 and anyone able to peek at the data traffic passing by (like your ISP,
2998 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
2999
3000 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
3001 www.stortinget.no. It is read daily by all members of parliament and
3002 their staff, as well as political journalists, activits and many other
3003 citizens of Norway. A visit to the www.stortinget.no web site will
3004 ask your browser to contact 8 other servers: ajax.googleapis.com,
3005 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3006 stats.g.doubleclick.net, www.google-analytics.com,
3007 www.googletagmanager.com and www.netigate.se. I extracted this by
3008 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
3009 Stortinget web page and tell me all the URLs PhantomJS downloaded to
3010 render the page (in HAR format using
3011 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
3012 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
3013 to do this). My goal is to visualize network traces to all IP
3014 addresses behind these DNS names, do show where visitors personal
3015 information is spread when visiting the page.&lt;/p&gt;
3016
3017 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
3018 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;
3019
3020 &lt;p&gt;When I had a look around for options, I could not find any good
3021 free software tools to do this, and decided I needed my own traceroute
3022 wrapper outputting KML based on locations looked up using GeoIP. KML
3023 is easy to work with and easy to generate, and understood by several
3024 of the GIS tools I have available. I got good help from by NUUG
3025 colleague Anders Einar with this, and the result can be seen in
3026 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
3027 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
3028 free GeoIP databases I could find (and the for-pay databases my
3029 friends had access to) is not up to the task. The IP addresses of
3030 central Internet infrastructure would typically be placed near the
3031 controlling companies main office, and not where the router is really
3032 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
3033 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
3034
3035 &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
3036 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;
3037
3038 &lt;p&gt;I also had a look at the visual traceroute graph created by
3039 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
3040 showing IP network ownership (aka AS owner) for the IP address in
3041 question.
3042 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
3043 graph display a lot of useful information about the traceroute in SVG
3044 format&lt;/a&gt;, and give a good indication on who control the network
3045 equipment involved, but it do not include geolocation. This graph
3046 make it possible to see the information is made available at least for
3047 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
3048 3 Communications and NetDNA.&lt;/p&gt;
3049
3050 &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
3051 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;
3052
3053 &lt;p&gt;In the process, I came across the
3054 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
3055 Salim Gasmi. Its methology of combining guesses based on DNS names,
3056 various location databases and finally use latecy times to rule out
3057 candidate locations seemed to do a very good job of guessing correct
3058 geolocation. But it could only do one trace at the time, did not have
3059 a sensor in Norway and did not make the geolocations easily available
3060 for postprocessing. So I contacted the developer and asked if he
3061 would be willing to share the code (he refused until he had time to
3062 clean it up), but he was interested in providing the geolocations in a
3063 machine readable format, and willing to set up a sensor in Norway. So
3064 since yesterday, it is possible to run traces from Norway in this
3065 service thanks to a sensor node set up by
3066 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
3067 trace in KML format for further processing.&lt;/p&gt;
3068
3069 &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
3070 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;
3071
3072 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
3073 Denmark, Germany, Holland and Ireland. Plenty of places where the
3074 Snowden confirmations verified the traffic is read by various actors
3075 without your best interest as their top priority.&lt;/p&gt;
3076
3077 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
3078 over all the hosts behind the urls imported by www.stortinget.no and
3079 ask for the KML file from GeoTraceroute, and create a combined KML
3080 file with all the traces (unfortunately only one of the IP addresses
3081 behind the DNS name is traced this time. To get them all, one would
3082 have to request traces using IP number instead of DNS names from
3083 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
3084
3085 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
3086 the IP traffic moves and who control the boxes involved in moving it.
3087 And every time the link crosses for example the Swedish border, we can
3088 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3089 Britain and NSA in USA and cables around the globe. (Hm, what should
3090 we tell them? :) Keep that in mind if you ever send anything
3091 unencrypted over the Internet.&lt;/p&gt;
3092
3093 &lt;p&gt;PS: KML files are drawn using
3094 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
3095 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
3096 Marble. There are heaps of other options too.&lt;/p&gt;
3097
3098 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3099 activities, please send Bitcoin donations to my address
3100 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3101 </description>
3102 </item>
3103
3104 <item>
3105 <title>Appstream just learned how to map hardware to packages too!</title>
3106 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
3107 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
3108 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
3109 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
3110 readers probably know, I have been working on the
3111 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
3112 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
3113 it easier for users to figure out what to install to get a given piece
3114 of hardware to work in Debian, and a key part of this system is a way
3115 to map hardware to packages. Isenkram have its own mapping database,
3116 and also uses data provided by each package using the AppStream
3117 metadata format. And today,
3118 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
3119 Debian learned to look up hardware the same way Isenkram is doing it,
3120 ie using fnmatch():&lt;/p&gt;
3121
3122 &lt;p&gt;&lt;pre&gt;
3123 % appstreamcli what-provides modalias \
3124 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3125 Identifier: pymissile [generic]
3126 Name: pymissile
3127 Summary: Control original Striker USB Missile Launcher
3128 Package: pymissile
3129 % appstreamcli what-provides modalias usb:v0694p0002d0000
3130 Identifier: libnxt [generic]
3131 Name: libnxt
3132 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3133 Package: libnxt
3134 ---
3135 Identifier: t2n [generic]
3136 Name: t2n
3137 Summary: Simple command-line tool for Lego NXT
3138 Package: t2n
3139 ---
3140 Identifier: python-nxt [generic]
3141 Name: python-nxt
3142 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3143 Package: python-nxt
3144 ---
3145 Identifier: nbc [generic]
3146 Name: nbc
3147 Summary: C compiler for LEGO Mindstorms NXT bricks
3148 Package: nbc
3149 %
3150 &lt;/pre&gt;&lt;/p&gt;
3151
3152 &lt;p&gt;A similar query can be done using the combined AppStream and
3153 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
3154
3155 &lt;p&gt;&lt;pre&gt;
3156 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3157 pymissile
3158 % isenkram-lookup usb:v0694p0002d0000
3159 libnxt
3160 nbc
3161 python-nxt
3162 t2n
3163 %
3164 &lt;/pre&gt;&lt;/p&gt;
3165
3166 &lt;p&gt;You can find modalias values relevant for your machine using
3167 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
3168
3169 &lt;p&gt;If you want to make this system a success and help Debian users
3170 make the most of the hardware they have, please
3171 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
3172 AppStream metadata for your package following the guidelines&lt;/a&gt;
3173 documented in the wiki. So far only 11 packages provide such
3174 information, among the several hundred hardware specific packages in
3175 Debian. The Isenkram database on the other hand contain 101 packages,
3176 mostly related to USB dongles. Most of the packages with hardware
3177 mapping in AppStream are LEGO Mindstorms related, because I have, as
3178 part of my involvement in
3179 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
3180 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
3181 complete set of packages in Debian for that particular hardware. The
3182 team also got a nice Christmas present today. The
3183 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
3184 package&lt;/a&gt; made it into Debian. With this package in place, it is
3185 now possible to use the LEGO Mindstorms NXT unit with only free
3186 software, as the nxt-firmware package contain the source and firmware
3187 binaries for the NXT brick.&lt;/p&gt;
3188
3189 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3190 activities, please send Bitcoin donations to my address
3191 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3192 </description>
3193 </item>
3194
3195 <item>
3196 <title>Isenkram updated with a lot more hardware-package mappings</title>
3197 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
3198 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
3199 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
3200 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3201 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
3202 and install packages to get your hardware dongles to work, is still
3203 going strong. It is a system to look up the hardware present on or
3204 connected to the current system, and map the hardware to Debian
3205 packages. It can either be done using the tools in isenkram-cli or
3206 using the user space daemon in the isenkram package. The latter will
3207 notify you, when inserting new hardware, about what packages to
3208 install to get the dongle working. It will even provide a button to
3209 click on to ask packagekit to install the packages.&lt;/p&gt;
3210
3211 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
3212
3213 &lt;p&gt;&lt;pre&gt;
3214 % isenkram-lookup
3215 bluez
3216 cheese
3217 ethtool
3218 fprintd
3219 fprintd-demo
3220 gkrellm-thinkbat
3221 hdapsd
3222 libpam-fprintd
3223 pidgin-blinklight
3224 thinkfan
3225 tlp
3226 tp-smapi-dkms
3227 tp-smapi-source
3228 tpb
3229 %
3230 &lt;/pre&gt;&lt;/p&gt;
3231
3232 &lt;p&gt;It can also list the firware package providing firmware requested
3233 by the load kernel modules, which in my case is an empty list because
3234 I have all the firmware my machine need:
3235
3236 &lt;p&gt;&lt;pre&gt;
3237 % /usr/sbin/isenkram-autoinstall-firmware -l
3238 info: did not find any firmware files requested by loaded kernel modules. exiting
3239 %
3240 &lt;/pre&gt;&lt;/p&gt;
3241
3242 &lt;p&gt;The last few days I had a look at several of the around 250
3243 packages in Debian with udev rules. These seem like good candidates
3244 to install when a given hardware dongle is inserted, and I found
3245 several that should be proposed by isenkram. I have not had time to
3246 check all of them, but am happy to report that now there are 97
3247 packages packages mapped to hardware by Isenkram. 11 of these
3248 packages provide hardware mapping using AppStream, while the rest are
3249 listed in the modaliases file provided in isenkram.&lt;/p&gt;
3250
3251 &lt;p&gt;These are the packages with hardware mappings at the moment. The
3252 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
3253 support using AppStream, for everyone to use:&lt;/p&gt;
3254
3255 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
3256 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
3257 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
3258 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
3259 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
3260 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3261 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
3262 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3263 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3264 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3265 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
3266 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3267 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
3268 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3269 pcscd, pidgin-blinklight, printer-driver-splix,
3270 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
3271 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3272 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3273 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3274 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3275 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3276 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3277 xserver-xorg-video-vmware, yubikey-personalization and
3278 zd1211-firmware&lt;/p&gt;
3279
3280 &lt;p&gt;If you know of other packages, please let me know with a wishlist
3281 bug report against the isenkram-cli package, and ask the package
3282 maintainer to
3283 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
3284 metadata according to the guidelines&lt;/a&gt; to provide the information
3285 for everyone. In time, I hope to get rid of the isenkram specific
3286 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
3287
3288 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
3289 much hardware, and suggest that the package with with any ethernet
3290 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
3291 the details. I hope the maintainer find time to address it soon. In
3292 the mean time I provide an override in isenkram.&lt;/p&gt;
3293 </description>
3294 </item>
3295
3296 <item>
3297 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
3298 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
3299 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
3300 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
3301 <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;
3302
3303 &lt;p&gt;In my early years, I played
3304 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
3305 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
3306 space, and reached the &#39;elite&#39; fighting status before I moved on. The
3307 original Elite game was available on Commodore 64 and the IBM PC
3308 edition I played had a 64 KB executable. I am still impressed today
3309 that the authors managed to squeeze both a 3D engine and details about
3310 more than 2000 planet systems across 7 galaxies into a binary so
3311 small.&lt;/p&gt;
3312
3313 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
3314 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
3315 really have time to test it properly until a few days ago. It was
3316 great to discover that my old knowledge about trading routes were
3317 still valid. But my fighting and flying abilities were gone, so I had
3318 to retrain to be able to dock on a space station. And I am still not
3319 able to make much resistance when I am attacked by pirates, so I
3320 bougth and mounted the most powerful laser in the rear to be able to
3321 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
3322
3323 &lt;p&gt;When playing Elite in the late eighties, I had to discover
3324 everything on my own, and I had long lists of prices seen on different
3325 planets to be able to decide where to trade what. This time I had the
3326 advantages of the
3327 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
3328 where information about each planet is easily available with common
3329 price ranges and suggested trading routes. This improved my ability
3330 to earn money and I have been able to earn enough to buy a lot of
3331 useful equipent in a few days. I believe I originally played for
3332 months before I could get a docking computer, while now I could get it
3333 after less then a week.&lt;/p&gt;
3334
3335 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
3336 space, you should try out Oolite. It is available for Linux, MacOSX
3337 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
3338
3339 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3340 activities, please send Bitcoin donations to my address
3341 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3342 </description>
3343 </item>
3344
3345 <item>
3346 <title>Quicker Debian installations using eatmydata</title>
3347 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
3348 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
3349 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
3350 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
3351 installation system, observing how using
3352 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
3353 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
3354 speedup around 20-40 percent for Debian Edu, where we install around
3355 1000 packages from within the installer. The eatmydata package
3356 provide a way to disable/delay file system flushing. This is a bit
3357 risky in the general case, as files that should be stored on disk will
3358 stay only in memory a bit longer than expected, causing problems if a
3359 machine crashes at an inconvenient time. But for an installation, if
3360 the machine crashes during installation the process is normally
3361 restarted, and avoiding disk operations as much as possible to speed
3362 up the process make perfect sense.
3363
3364 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
3365 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
3366 but did not have time to push it any further. But a few months ago I
3367 picked it up again and worked with the libeatmydata package maintainer
3368 Mattia Rizzolo to make it easier for everyone to get this installation
3369 speedup in Debian. Thanks to our cooperation There is now an
3370 eatmydata-udeb package in Debian testing and unstable, and simply
3371 enabling/installing it in debian-installer (d-i) is enough to get the
3372 quicker installations. It can be enabled using preseeding. The
3373 following untested kernel argument should do the trick:&lt;/p&gt;
3374
3375 &lt;blockquote&gt;&lt;pre&gt;
3376 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
3377 &lt;/pre&gt;&lt;/blockquote&gt;
3378
3379 &lt;p&gt;This should ask d-i to install the package inside the d-i
3380 environment early in the installation sequence. Having it installed
3381 in d-i in turn will make sure the relevant scripts are called just
3382 after debootstrap filled /target/ with the freshly installed Debian
3383 system to configure apt to run dpkg with eatmydata. This is enough to
3384 speed up the installation process. There is a proposal to
3385 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
3386 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
3387 tested its impact.&lt;/p&gt;
3388
3389 </description>
3390 </item>
3391
3392 <item>
3393 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
3394 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
3395 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
3396 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
3397 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3398 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3399 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3400 elever over det ganske land skal levere inn hvert år. Det mange ikke
3401 vet er at selv om de kommersielle alternativene
3402 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
3403 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
3404 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3405 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3406 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3407 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3408 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3409 nynorsk, og få den automatoversatt til det andre skriftspråket.
3410 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3411 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3412 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3413 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3414 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
3415 teksten din i webskjemaet der.
3416
3417 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
3418 teknologien kan du enten installere pakken
3419 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
3420 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3421 api.apertium.org. Se
3422 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
3423 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3424 denne teksten som ble skrevet på bokmål over maskinoversatt til
3425 nynorsk.&lt;/p&gt;
3426
3427 &lt;hr/&gt;
3428
3429 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3430 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3431 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3432 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3433 veit er at sjølv om dei kommersielle alternativa
3434 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
3435 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
3436 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3437 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3438 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3439 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3440 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3441 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3442 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3443 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3444 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3445 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3446 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
3447 teksta di i *webskjemaet der.
3448
3449 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
3450 teknologien kan du anten installera pakken
3451 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
3452 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3453 *api.*apertium.org. Sjå
3454 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
3455 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3456 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3457 nynorsk.&lt;/p&gt;
3458 </description>
3459 </item>
3460
3461 <item>
3462 <title>Coz profiler for multi-threaded software is now in Debian</title>
3463 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
3464 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
3465 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
3466 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
3467 profiler able to run benchmarking experiments on the instrumented
3468 multi-threaded program, finally
3469 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
3470 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
3471 months since
3472 &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
3473 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
3474 it suitable for Debian. There are still issues with clang
3475 compatibility, inline assembly only working x86 and minimized
3476 JavaScript libraries.&lt;/p&gt;
3477
3478 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
3479
3480 &lt;p&gt;&lt;blockquote&gt;
3481 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
3482 &lt;/blockquote&gt;&lt;/p&gt;
3483
3484 &lt;p&gt;This will produce a profile.coz file in the current working
3485 directory with the profiling information. This is then given to a
3486 JavaScript application provided in the package and available from
3487 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
3488 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
3489
3490 &lt;p&gt;&lt;blockquote&gt;
3491 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
3492 &lt;/blockquote&gt;&lt;/p&gt;
3493
3494 &lt;p&gt;See the project home page and the
3495 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
3496 ;login: article on Coz&lt;/a&gt; for more information on how it is
3497 working.&lt;/p&gt;
3498 </description>
3499 </item>
3500
3501 <item>
3502 <title>My own self balancing Lego Segway</title>
3503 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
3504 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
3505 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
3506 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
3507 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
3508 present. It had been on my wishlist for a while, because I wanted to
3509 build a Segway like balancing lego robot. I had already built
3510 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
3511 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
3512 NXT kit as the balance sensor, but it was not working very well. It
3513 could balance for a while, but was very sensitive to the light
3514 condition in the room and the reflective properties of the surface and
3515 would fall over after a short while. I wanted something more robust,
3516 and had
3517 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
3518 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
3519 wishlist for some years before it suddenly showed up as a gift from my
3520 loved ones. :)&lt;/p&gt;
3521
3522 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
3523 since then. But that changed some days ago, when I was searching for
3524 lego segway information and came across a recipe from HiTechnic for
3525 building
3526 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
3527 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
3528 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
3529 code&lt;/a&gt; was included, so it was just a question of putting it all
3530 together. And thanks to the great work of many Debian developers, the
3531 compiler needed to build the source for the NXT is already included in
3532 Debian, so I was read to go in less than an hour. The resulting robot
3533 do not look very impressive in its simplicity:&lt;/p&gt;
3534
3535 &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;
3536
3537 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
3538 design from HiTechnic, I had to comment out the last task
3539 (taskControl). I simply placed /* and */ around it get the program
3540 working without that sensor present. Now it balances just fine until
3541 the battery status run low:&lt;/p&gt;
3542
3543 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
3544 &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;
3545 &lt;/video&gt;&lt;/p&gt;
3546
3547 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
3548 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
3549
3550 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
3551 they need to work with LEGO in Debian and all our derivative
3552 distributions like Ubuntu, check out
3553 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
3554 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
3555 RCX and NXT controller (no EV3), and would like to make sure the
3556 Debian tools needed to program the systems I own work as they
3557 should.&lt;/p&gt;
3558 </description>
3559 </item>
3560
3561 <item>
3562 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
3563 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
3564 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
3565 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
3566 <description>&lt;p&gt;In July
3567 &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
3568 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
3569 the ability to receive SMS messages (aka without a cell phone). It is
3570 time to share some experiences and provide an updated setup.&lt;/p&gt;
3571
3572 &lt;p&gt;The Signal app have worked fine for several months now, and I use
3573 it regularly to chat with my loved ones. I had a major snag at the
3574 end of my summer vacation, when the the app completely forgot my
3575 setup, identity and keys. The reason behind this major mess was
3576 running out of disk space. To avoid that ever happening again I have
3577 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
3578 roll back to an earlier version if the files are wiped by mistake. I
3579 had to use it once after introducing the git backup. When rolling
3580 back to an earlier version, one need to use the &#39;reset session&#39; option
3581 in Signal to get going, and notify the people you talk with about the
3582 problem. I assume there is some sequence number tracking in the
3583 protocol to detect rollback attacks. The git repository is rather big
3584 (674 MiB so far), but I have not tried to figure out if some of the
3585 content can be added to a .gitignore file due to lack of spare
3586 time.&lt;/p&gt;
3587
3588 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
3589 make it impossible to send messages using Signal. I could still
3590 receive them, but had to patch the code with a new timestamp to send.
3591 I believe the timeout is added by the developers to force people to
3592 upgrade to the latest version of the app, even when there is no
3593 protocol changes, to reduce the version skew among the user base and
3594 thus try to keep the number of support requests down.&lt;/p&gt;
3595
3596 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
3597 making the old patch fail to apply cleanly. Below is an updated
3598 patch, including the shell wrapper I use to start Signal. The
3599 original version required a new user to locate the JavaScript console
3600 and call a function from there. I got help from a friend with more
3601 JavaScript knowledge than me to modify the code to provide a GUI
3602 button instead. This mean that to get started you just need to run
3603 the wrapper and click the &#39;Register without mobile phone&#39; to get going
3604 now. I&#39;ve also modified the timeout code to always set it to 90 days
3605 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
3606
3607 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
3608
3609 &lt;ol&gt;
3610
3611 &lt;li&gt;First, install required packages to get the source code and the
3612 browser you need. Signal only work with Chrome/Chromium, as far as I
3613 know, so you need to install it.
3614
3615 &lt;pre&gt;
3616 apt install git tor chromium
3617 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3618 &lt;/pre&gt;&lt;/li&gt;
3619
3620 &lt;li&gt;Modify the source code using command listed in the the patch
3621 block below.&lt;/li&gt;
3622
3623 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
3624 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
3625
3626 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
3627 number you can receive calls to the next minute, receive the
3628 verification code and enter it into the form field and press
3629 &#39;Register&#39;. Note, the phone number you use will be user Signal
3630 username, ie the way others can find you on Signal.&lt;/li&gt;
3631
3632 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3633 not show up in the contact list until you restart Signal, and there is
3634 no way to assign names to Contacts. There is also no way to create or
3635 update chat groups. I suspect this is because the web app do not have
3636 a associated contact database.&lt;/li&gt;
3637
3638 &lt;/ol&gt;
3639
3640 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3641 main author moxie0 reject federation and accept dependencies to major
3642 corporations like Google (part of the code is fetched from Google) and
3643 Amazon (the central coordination point is owned by Amazon). See for
3644 example
3645 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3646 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3647 view on these issues. But the network effect is strong in this case,
3648 and several of the people I want to communicate with already use
3649 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3650 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3651 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3652 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3653 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3654 working on Debian Stable.&lt;/p&gt;
3655
3656 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3657 working. It switch to the production servers, disable to timeout,
3658 make registration easier and add the shell wrapper:&lt;/p&gt;
3659
3660 &lt;pre&gt;
3661 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3662 diff --git a/js/background.js b/js/background.js
3663 index 24b4c1d..579345f 100644
3664 --- a/js/background.js
3665 +++ b/js/background.js
3666 @@ -33,9 +33,9 @@
3667 });
3668 });
3669
3670 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3671 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3672 var SERVER_PORTS = [80, 4433, 8443];
3673 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3674 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3675 var messageReceiver;
3676 window.getSocketStatus = function() {
3677 if (messageReceiver) {
3678 diff --git a/js/expire.js b/js/expire.js
3679 index 639aeae..beb91c3 100644
3680 --- a/js/expire.js
3681 +++ b/js/expire.js
3682 @@ -1,6 +1,6 @@
3683 ;(function() {
3684 &#39;use strict&#39;;
3685 - var BUILD_EXPIRATION = 0;
3686 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3687
3688 window.extension = window.extension || {};
3689
3690 diff --git a/js/views/install_view.js b/js/views/install_view.js
3691 index 7816f4f..1d6233b 100644
3692 --- a/js/views/install_view.js
3693 +++ b/js/views/install_view.js
3694 @@ -38,7 +38,8 @@
3695 return {
3696 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3697 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3698 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3699 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3700 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3701 };
3702 },
3703 clearQR: function() {
3704 diff --git a/options.html b/options.html
3705 index dc0f28e..8d709f6 100644
3706 --- a/options.html
3707 +++ b/options.html
3708 @@ -14,7 +14,10 @@
3709 &amp;lt;div class=&#39;nav&#39;&gt;
3710 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3711 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3712 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3713 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3714 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3715 +
3716 + &amp;lt;/div&gt;
3717 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3718 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3719 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3720 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3721 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3722 @@ -0,0 +1,12 @@
3723 +#!/bin/sh
3724 +set -e
3725 +cd $(dirname $0)
3726 +mkdir -p userdata
3727 +userdata=&quot;`pwd`/userdata&quot;
3728 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3729 + (cd $userdata &amp;&amp; git init)
3730 +fi
3731 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3732 +exec chromium \
3733 + --proxy-server=&quot;socks://localhost:9050&quot; \
3734 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3735 EOF
3736 chmod a+rx run-signal-app
3737 &lt;/pre&gt;
3738
3739 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3740 activities, please send Bitcoin donations to my address
3741 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3742 </description>
3743 </item>
3744
3745 <item>
3746 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3747 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3748 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3749 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3750 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3751 system&lt;/a&gt; provide a practical and easy way to figure out which
3752 packages support the hardware in a given machine. The command line
3753 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
3754 convenient way to list and install packages relevant for the current
3755 hardware during system installation, both user space packages and
3756 firmware packages. The GUI background daemon on the other hand provide
3757 a pop-up proposing to install packages when a new dongle is inserted
3758 while using the computer. For example, if you plug in a smart card
3759 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
3760 that package isn&#39;t already installed, and if you plug in a USB video
3761 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
3762 cheese is currently missing. This already work just fine.&lt;/p&gt;
3763
3764 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
3765 package names. When I started no such database existed in Debian, so
3766 I made my own data set and included it with the isenkram package and
3767 made isenkram fetch the latest version of this database from git using
3768 http. This way the isenkram users would get updated package proposals
3769 as soon as I learned more about hardware related packages.&lt;/p&gt;
3770
3771 &lt;p&gt;The hardware is identified using modalias strings. The modalias
3772 design is from the Linux kernel where most hardware descriptors are
3773 made available as a strings that can be matched using filename style
3774 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3775 identifiers.&lt;/p&gt;
3776
3777 &lt;p&gt;The downside to the Isenkram specific database is that there is no
3778 information about relevant distribution / Debian version, making
3779 isenkram propose obsolete packages too. But along came AppStream, a
3780 cross distribution mechanism to store and collect metadata about
3781 software packages. When I heard about the proposal, I contacted the
3782 people involved and suggested to add a hardware matching rule using
3783 modalias strings in the specification, to be able to use AppStream for
3784 mapping hardware to packages. This idea was accepted and AppStream is
3785 now a great way for a package to announce the hardware it support in a
3786 distribution neutral way. I wrote
3787 &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
3788 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
3789 December. If you have a hardware related package in Debian, please
3790 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
3791
3792 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
3793 RCX or NXT unit, announce this support using AppStream. The effect is
3794 that when you insert such LEGO robot controller into your Debian
3795 machine, Isenkram will propose to install the packages needed to get
3796 it working. The intention is that this should allow the local user to
3797 start programming his robot controller right away without having to
3798 guess what packages to use or which permissions to fix.&lt;/p&gt;
3799
3800 &lt;p&gt;But when I sat down with my son the other day to program our NXT
3801 unit using his Debian Stretch computer, I discovered something
3802 annoying. The local console user (ie my son) did not get access to
3803 the USB device for programming the unit. This used to work, but no
3804 longer in Jessie and Stretch. After some investigation and asking
3805 around on #debian-devel, I discovered that this was because udev had
3806 changed the mechanism used to grant access to local devices. The
3807 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
3808 no longer applied, because LDAP users no longer was added to the
3809 plugdev group during login. Michael Biebl told me that this method
3810 was obsolete and the new method used ACLs instead. This was good
3811 news, as the plugdev mechanism is a mess when using a remote user
3812 directory like LDAP. Using ACLs would make sure a user lost device
3813 access when she logged out, even if the user left behind a background
3814 process which would retain the plugdev membership with the ConsoleKit
3815 setup. Armed with this knowledge I moved on to fix the access problem
3816 for the LEGO Mindstorms related packages.&lt;/p&gt;
3817
3818 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
3819 applied directly for a device, or is applied in
3820 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
3821 LEGO Mindstorms udev rules did not have a class, I decided to add the
3822 tag directly in the udev rules files included in the packages. Here
3823 is one example. For the nqc C compiler for the RCX, the
3824 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
3825
3826 &lt;p&gt;&lt;pre&gt;
3827 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
3828 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
3829 &lt;/pre&gt;&lt;/p&gt;
3830
3831 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
3832 packages using plugdev in their /lib/udev/rules.d/ files should be
3833 changed to use this tag (either directly or indirectly via
3834 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
3835 to detect this?&lt;/p&gt;
3836
3837 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
3838 It is unclear to me if the uaccess tag is an internal implementation
3839 detail like the udev-acl tag used by
3840 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
3841 indirect method is the preferred way. Michael
3842 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
3843 documentation from the systemd project&lt;/a&gt; and I hope it will make
3844 this clearer. For now I use the generic classes when they exist and
3845 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
3846 directly if no such class exist.&lt;/p&gt;
3847
3848 &lt;p&gt;To learn more about the isenkram system, please check out
3849 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3850 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3851
3852 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
3853 please join us on our IRC channel
3854 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
3855 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
3856 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
3857 list is not yet created, but we are working on it. :)&lt;/p&gt;
3858
3859 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3860 activities, please send Bitcoin donations to my address
3861 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3862 </description>
3863 </item>
3864
3865 <item>
3866 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
3867 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
3868 <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>
3869 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
3870 <description>&lt;p&gt;In April we
3871 &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
3872 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
3873 how to set up and administrate a Debian system. Today I am happy to
3874 report that the first draft is now publicly available. You can find
3875 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
3876 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
3877 eight chapters have a first draft translation, and we are working on
3878 proofreading the content. If you want to help out, please start
3879 contributing using
3880 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3881 hosted weblate project page&lt;/a&gt;, and get in touch using
3882 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3883 translators mailing list&lt;/a&gt;. Please also check out
3884 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3885 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
3886 and update weblate if you find errors.&lt;/p&gt;
3887
3888 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
3889 electronic form.&lt;/p&gt;
3890 </description>
3891 </item>
3892
3893 <item>
3894 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
3895 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
3896 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
3897 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
3898 <description>&lt;p&gt;This summer, I read a great article
3899 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
3900 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
3901 how to profile multi-threaded programs. It presented a system for
3902 profiling software by running experiences in the running program,
3903 testing how run time performance is affected by &quot;speeding up&quot; parts of
3904 the code to various degrees compared to a normal run. It does this by
3905 slowing down parallel threads while the &quot;faster up&quot; code is running
3906 and measure how this affect processing time. The processing time is
3907 measured using probes inserted into the code, either using progress
3908 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3909 can also measure unmodified code by measuring complete the program
3910 runtime and running the program several times instead.&lt;/p&gt;
3911
3912 &lt;p&gt;The project and presentation was so inspiring that I would like to
3913 get the system into Debian. I
3914 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
3915 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
3916 system ready for Debian by sending patches. The build process need to
3917 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
3918 to include the JavaScript web page used to visualize the collected
3919 profiling information included in the source package.
3920 But I expect that should work out fairly soon.&lt;/p&gt;
3921
3922 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
3923 on a binary with debug symbols available, start the program like this:
3924
3925 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3926 coz run --- program-to-run
3927 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3928
3929 &lt;p&gt;This will create a text file profile.coz with the instrumentation
3930 information. To show what part of the code affect the performance
3931 most, use a web browser and either point it to
3932 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
3933 or use the copy from git (in the gh-pages branch). Check out this web
3934 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
3935 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
3936 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3937 code, rebuild and run the profiler. This allow coz to do more
3938 targeted experiments.&lt;/p&gt;
3939
3940 &lt;p&gt;A video published by ACM
3941 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
3942 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
3943 from the 25th Symposium on Operating Systems Principles available
3944 titled
3945 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
3946 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
3947
3948 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
3949 for Coz is available from github. It will only build with clang
3950 because it uses a
3951 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
3952 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
3953 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
3954 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
3955
3956 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
3957 of software in Debian. I would very much like some help with the
3958 packaging effort, as I lack the in depth knowledge on how to package
3959 C++ libraries.&lt;/p&gt;
3960 </description>
3961 </item>
3962
3963 <item>
3964 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
3965 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
3966 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
3967 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
3968 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3969 to be a slight challenge. Here is the recipe if I ever need to do it
3970 again. It all started by me wanting to try the recipe to set up
3971 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
3972 hardened Android installation&lt;/a&gt; from the Tor project blog on a
3973 device I had access to. It is a old mobile phone with a broken
3974 microphone The initial idea had been to just
3975 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
3976 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
3977 until a few days ago.&lt;/p&gt;
3978
3979 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
3980 loader (press volume down and power at the same time), (2) select
3981 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
3982 machine, (4) request the device identifier token by running &#39;fastboot
3983 oem get_identifier_token&#39;, (5) request the device unlocking key using
3984 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
3985 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
3986
3987 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
3988 or newer, and the device I was working on had 2.00.0027. This
3989 apparently can be easily fixed by downloading a Windows program and
3990 running it on your Windows machine, if you accept the terms Microsoft
3991 require you to accept to use Windows - which I do not. So I had to
3992 come up with a different approach. I got a lot of help from AndyCap
3993 on #nuug, and would not have been able to get this working without
3994 him.&lt;/p&gt;
3995
3996 &lt;p&gt;First I needed to extract the hboot firmware from
3997 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
3998 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
3999 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
4000 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
4001 recognise the file format, but unruu worked and extracted rom.zip,
4002 containing the new hboot firmware and a text file describing which
4003 devices it would work for.&lt;/p&gt;
4004
4005 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
4006 followed some instructions
4007 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
4008 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
4009 machine with Debian testing:&lt;/p&gt;
4010
4011 &lt;p&gt;&lt;pre&gt;
4012 adb reboot-bootloader
4013 fastboot oem rebootRUU
4014 fastboot flash zip rom.zip
4015 fastboot flash zip rom.zip
4016 fastboot reboot
4017 &lt;/pre&gt;&lt;/p&gt;
4018
4019 &lt;p&gt;The flash command apparently need to be done twice to take effect,
4020 as the first is just preparations and the second one do the flashing.
4021 The adb command is just to get to the boot loader menu, so turning the
4022 device on while holding volume down and the power button should work
4023 too.&lt;/p&gt;
4024
4025 &lt;p&gt;With the new hboot version in place I could start following the
4026 instructions on the HTC developer web site. I got the device token
4027 like this:&lt;/p&gt;
4028
4029 &lt;p&gt;&lt;pre&gt;
4030 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
4031 &lt;/pre&gt;
4032
4033 &lt;p&gt;And once I got the unlock code via email, I could use it like
4034 this:&lt;/p&gt;
4035
4036 &lt;p&gt;&lt;pre&gt;
4037 fastboot flash unlocktoken Unlock_code.bin
4038 &lt;/pre&gt;&lt;/p&gt;
4039
4040 &lt;p&gt;And with that final step in place, the phone was unlocked and I
4041 could start stuffing the software of my own choosing into the device.
4042 So far I only inserted a replacement recovery image to wipe the phone
4043 before I start. We will see what happen next. Perhaps I should
4044 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
4045 </description>
4046 </item>
4047
4048 <item>
4049 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
4050 <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>
4051 <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>
4052 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
4053 <description>&lt;p&gt;For a while now, I have wanted to test
4054 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
4055 said to provide end to end encrypted communication and several of my
4056 friends and family are already using it. As I by choice do not own a
4057 mobile phone, this proved to be harder than expected. And I wanted to
4058 have the source of the client and know that it was the code used on my
4059 machine. But yesterday I managed to get it working. I used the
4060 Github source, compared it to the source in
4061 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
4062 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
4063 patches to use the production Signal servers, started the app and
4064 asked for the hidden &quot;register without a smart phone&quot; form. Here is
4065 the recipe how I did it.&lt;/p&gt;
4066
4067 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
4068
4069 &lt;pre&gt;
4070 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4071 &lt;/pre&gt;
4072
4073 &lt;p&gt;Next, I patched the source to use the production servers, to be
4074 able to talk to other Signal users:&lt;/p&gt;
4075
4076 &lt;pre&gt;
4077 cat &amp;lt;&amp;lt;EOF | patch -p0
4078 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
4079 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
4080 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
4081 @@ -47,8 +47,8 @@
4082 });
4083 });
4084
4085 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
4086 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
4087 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
4088 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
4089 var messageReceiver;
4090 window.getSocketStatus = function() {
4091 if (messageReceiver) {
4092 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
4093 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
4094 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
4095 @@ -1,6 +1,6 @@
4096 ;(function() {
4097 &#39;use strict&#39;;
4098 - var BUILD_EXPIRATION = 0;
4099 + var BUILD_EXPIRATION = 1474492690000;
4100
4101 window.extension = window.extension || {};
4102
4103 EOF
4104 &lt;/pre&gt;
4105
4106 &lt;p&gt;The first part is changing the servers, and the second is updating
4107 an expiration timestamp. This timestamp need to be updated regularly.
4108 It is set 90 days in the future by the build process (Gruntfile.js).
4109 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
4110
4111 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
4112 script to launch Signal in Chromium.&lt;/p&gt;
4113
4114 &lt;pre&gt;
4115 #!/bin/sh
4116 cd $(dirname $0)
4117 mkdir -p userdata
4118 exec chromium \
4119 --proxy-server=&quot;socks://localhost:9050&quot; \
4120 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4121 &lt;/pre&gt;
4122
4123 &lt;p&gt; The script start the app and configure Chromium to use the Tor
4124 SOCKS5 proxy to make sure those controlling the Signal servers (today
4125 Amazon and Whisper Systems) as well as those listening on the lines
4126 will have a harder time location my laptop based on the Signal
4127 connections if they use source IP address.&lt;/p&gt;
4128
4129 &lt;p&gt;When the script starts, one need to follow the instructions under
4130 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
4131 repository. I right clicked on the Signal window to get up the
4132 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
4133 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
4134 registration form. Then I entered by land line phone number and
4135 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
4136 repeated the verification code three times. After entering the number
4137 into the verification code field in the form, I could start using
4138 Signal from my laptop.
4139
4140 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
4141 whom and thus who know who to those controlling the central server,
4142 but such leakage is hard to avoid with a centrally controlled server
4143 setup. It is something to keep in mind when using Signal - the
4144 content of your chats are harder to intercept, but the meta data
4145 exposing your contact network is available to people you do not know.
4146 So better than many options, but not great. And sadly the usage is
4147 connected to my land line, thus allowing those controlling the server
4148 to associate it to my home and person. I would prefer it if only
4149 those I knew could tell who I was on Signal. There are options
4150 avoiding such information leakage, but most of my friends are not
4151 using them, so I am stuck with Signal for now.&lt;/p&gt;
4152
4153 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
4154 on this topic in
4155 &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
4156 and updated recipe for using the Signal app without a mobile
4157 phone&lt;/a&gt;.&lt;/p&gt;
4158 </description>
4159 </item>
4160
4161 <item>
4162 <title>The new &quot;best&quot; multimedia player in Debian?</title>
4163 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
4164 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
4165 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
4166 <description>&lt;p&gt;When I set out a few weeks ago to figure out
4167 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
4168 multimedia player in Debian claimed to support most file formats /
4169 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
4170 the various players claimed support for. The range was from 55 to 130
4171 MIME types. I suspect most media formats are supported by all
4172 players, but this is not really reflected in the MimeTypes values in
4173 their desktop files. There are probably also some bogus MIME types
4174 listed, but it is hard to identify which one this is.&lt;/p&gt;
4175
4176 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
4177 the players suggesting to add more MIME types to their desktop files,
4178 and decided to spend some time myself improving the situation for my
4179 favorite media player VLC. The fixes for VLC entered Debian unstable
4180 yesterday. The complete list of MIME types can be seen on the
4181 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
4182 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
4183
4184 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
4185 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4186 kmplayer. I am sure some of the other players desktop files support
4187 several of the formats currently listed as working only with vlc,
4188 toten and parole.&lt;/p&gt;
4189
4190 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
4191 supported by all the tested multimedia players in Debian in their
4192 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4193 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4194 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4195 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4196 it sad that video/ogg and video/webm is not supported by all the media
4197 players in Debian. As far as I can tell, all of them can handle both
4198 formats.&lt;/p&gt;
4199 </description>
4200 </item>
4201
4202 <item>
4203 <title>A program should be able to open its own files on Linux</title>
4204 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
4205 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
4206 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
4207 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
4208 decided to test its presentation tool when making the slides for a
4209 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4210 wrote the first draft of the slides, saved the result and went to bed
4211 the day before I would give the talk. The next day I took a plane to
4212 the location where the meeting should take place, and on the plane I
4213 started up koffice again to polish the talk a bit, only to discover
4214 that kpresenter refused to load its own data file. I cursed a bit and
4215 started making the slides again from memory, to have something to
4216 present when I arrived. I tested that the saved files could be
4217 loaded, and the day seemed to be rescued. I continued to polish the
4218 slides until I suddenly discovered that the saved file could no longer
4219 be loaded into kpresenter. In the end I had to rewrite the slides
4220 three times, condensing the content until the talk became shorter and
4221 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
4222 kpresenter wrote inline images in a way itself could not understand.
4223 Eventually that bug was fixed and kpresenter ended up being a great
4224 program to make slides. The point I&#39;m trying to make is that we
4225 expect a program to be able to load its own data files, and it is
4226 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
4227
4228 &lt;p&gt;Did you ever experience a program failing to load its own data
4229 files from the desktop file browser? It is not a uncommon problem. A
4230 while back I discovered that the screencast recorder
4231 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4232 browser would refuse to open. No video player claimed to understand
4233 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
4234 returning the application/ogg MIME type, which no video player I had
4235 installed listed as a MIME type they would understand. I asked for
4236 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
4237 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
4238 several video players to add video/ogg to their desktop files, to give
4239 the file browser an idea what to do about Ogg Theora files. After a
4240 while, the desktop file browsers in Debian started to handle the
4241 output from gtk-recordmydesktop properly.&lt;/p&gt;
4242
4243 &lt;p&gt;But history repeats itself. A few days ago I tested the music
4244 system Rosegarden again, and I discovered that the KDE and xfce file
4245 browsers did not know what to do with the Rosegarden project files
4246 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
4247 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
4248 included in the next upload. To increase the chance of me remembering
4249 how to fix the problem next time some program fail to load its files
4250 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
4251
4252 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
4253 There are two sources for the MIME type of a given file. The output from
4254 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
4255 shared MIME type registry (under /usr/share/mime/). The file MIME
4256 type is mapped to programs supporting the MIME type, and this
4257 information is collected from
4258 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
4259 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
4260 one desktop file claiming support for the MIME type of the file, it is
4261 activated when asking to open a given file. If there are more, one
4262 can normally select which one to use by right-clicking on the file and
4263 selecting the wanted one using &#39;Open with&#39; or similar. In general
4264 this work well. But it depend on each program picking a good MIME
4265 type (preferably
4266 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
4267 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
4268 registry recognizing the file and the desktop file to list the MIME
4269 type in its list of supported MIME types.&lt;/p&gt;
4270
4271 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
4272 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
4273 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
4274
4275 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4276 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4277 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
4278 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
4279 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
4280 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
4281 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
4282 &amp;lt;/mime-type&amp;gt;
4283 &amp;lt;/mime-info&amp;gt;
4284 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4285
4286 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
4287 (it is a gzipped XML file). Note, it is much better to use an
4288 official MIME type registered with IANA than it is to make up ones own
4289 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
4290
4291 &lt;p&gt;The desktop file of the rosegarden program failed to list
4292 audio/x-rosegarden in its list of supported MIME types, causing the
4293 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
4294
4295 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4296 % grep Mime /usr/share/applications/rosegarden.desktop
4297 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4298 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4299 %
4300 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4301
4302 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
4303 MimeType= line.&lt;/p&gt;
4304
4305 &lt;p&gt;If you run into a file which fail to open the correct program when
4306 selected from the file browser, please check out the output from
4307 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
4308 MIME type is registered somewhere under /usr/share/mime/ and check
4309 that some desktop file under /usr/share/applications/ is claiming
4310 support for this MIME type. If not, please report a bug to have it
4311 fixed. :)&lt;/p&gt;
4312 </description>
4313 </item>
4314
4315 <item>
4316 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
4317 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
4318 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
4319 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
4320 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
4321 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
4322 related packages. The idea is to have a database of mappings between
4323 hardware and packages, and pop up a dialog suggesting for the user to
4324 install the packages to use a given hardware dongle. Some use cases
4325 are when you insert a Yubikey, it proposes to install the software
4326 needed to control it; when you insert a braille reader list it
4327 proposes to install the packages needed to send text to the reader;
4328 and when you insert a ColorHug screen calibrator it suggests to
4329 install the driver for it. The system work well, and even have a few
4330 command line tools to install firmware packages and packages for the
4331 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
4332
4333 &lt;p&gt;The system was initially written using aptdaemon, because I found
4334 good documentation and example code on how to use it. But aptdaemon
4335 is going away and is generally being replaced by
4336 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
4337 so Isenkram needed a rewrite. And today, thanks to the great patch
4338 from my college Sunil Mohan Adapa in the FreedomBox project, the
4339 rewrite finally took place. I&#39;ve just uploaded a new version of
4340 Isenkram into Debian Unstable with the patch included, and the default
4341 for the background daemon is now to use PackageKit. To check it out,
4342 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
4343 and see if it is recognised.&lt;/p&gt;
4344
4345 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
4346 the machine it is running on, you can check out the isenkram-lookup
4347 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
4348
4349 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4350 % isenkram-lookup
4351 bluez
4352 cheese
4353 fprintd
4354 fprintd-demo
4355 gkrellm-thinkbat
4356 hdapsd
4357 libpam-fprintd
4358 pidgin-blinklight
4359 thinkfan
4360 tleds
4361 tp-smapi-dkms
4362 tp-smapi-source
4363 tpb
4364 %p
4365 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4366
4367 &lt;p&gt;The hardware mappings come from several places. The preferred way
4368 is for packages to announce their hardware support using
4369 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4370 cross distribution appstream system&lt;/a&gt;.
4371 See
4372 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
4373 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
4374 </description>
4375 </item>
4376
4377 <item>
4378 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
4379 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
4380 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
4381 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
4382 <description>&lt;p&gt;Yesterday I updated the
4383 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
4384 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
4385 enterprising users. There were some nice user and visible changes.
4386 First of all, both desktop menu entries now work. A design flaw in
4387 one of the script made the history graph fail to show up (its PNG was
4388 dumped in ~/.xsession-errors) if no controlling TTY was available.
4389 The script worked when called from the command line, but not when
4390 called from the desktop menu. I changed this to look for a DISPLAY
4391 variable or a TTY before deciding where to draw the graph, and now the
4392 graph window pop up as expected.&lt;/p&gt;
4393
4394 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
4395 graphs (the one showing the last few hours). New is also the user of
4396 colours showing charging in blue and discharge in red. The percentages
4397 of this graph is relative to last full charge, not battery design
4398 capacity.&lt;/p&gt;
4399
4400 &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;
4401
4402 &lt;p&gt;The other graph show the entire history of the collected battery
4403 statistics, comparing it to the design capacity of the battery to
4404 visualise how the battery life time get shorter over time. The red
4405 line in this graph is what the previous graph considers 100 percent:
4406
4407 &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;
4408
4409 &lt;p&gt;In this graph you can see that I only charge the battery to 80
4410 percent of last full capacity, and how the capacity of the battery is
4411 shrinking. :(&lt;/p&gt;
4412
4413 &lt;p&gt;The last new feature is in the collector, which now will handle
4414 more hardware models. On some hardware, Linux power supply
4415 information is stored in /sys/class/power_supply/ACAD/, while the
4416 collector previously only looked in /sys/class/power_supply/AC/. Now
4417 both are checked to figure if there is power connected to the
4418 machine.&lt;/p&gt;
4419
4420 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4421 check out the
4422 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4423 in Debian unstable, or rebuild it on Jessie to get it working on
4424 Debian stable. :) The upstream source is available from &lt;a
4425 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4426 Patches are very welcome.&lt;/p&gt;
4427
4428 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4429 activities, please send Bitcoin donations to my address
4430 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4431 </description>
4432 </item>
4433
4434 <item>
4435 <title>Debian now with ZFS on Linux included</title>
4436 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
4437 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
4438 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
4439 <description>&lt;p&gt;Today, after many years of hard work from many people,
4440 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
4441 Debian. The package status can be seen on
4442 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
4443 for zfs-linux&lt;/a&gt;. and
4444 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4445 team status page&lt;/a&gt;. If you want to help out, please join us.
4446 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
4447 source code&lt;/a&gt; is available via git on Alioth. It would also be
4448 great if you could help out with
4449 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
4450 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
4451 </description>
4452 </item>
4453
4454 <item>
4455 <title>What is the best multimedia player in Debian?</title>
4456 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
4457 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
4458 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
4459 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
4460 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
4461
4462 &lt;p&gt;A few years ago, I had a look at the media support for Browser
4463 plugins in Debian, to get an idea which plugins to include in Debian
4464 Edu. I created a script to extract the set of supported MIME types
4465 for each plugin, and used this to find out which multimedia browser
4466 plugin supported most file formats / media types.
4467 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
4468 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
4469 not been updated for a while. But browser plugins are less relevant
4470 these days, so I thought it was time to look at standalone
4471 players.&lt;/p&gt;
4472
4473 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
4474 player when I wanted to play videos from the Norwegian National
4475 Broadcasting Company, and decided to investigate why. The cause is a
4476 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
4477 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
4478 of MIME types announced in the desktop file and the browser plugin,
4479 only to discover that there is quite a large difference between the
4480 two for VLC. This discovery made me dig up the script I used to
4481 compare browser plugins, and adjust it to compare desktop files
4482 instead, to try to figure out which multimedia player in Debian
4483 support most file formats.&lt;/p&gt;
4484
4485 &lt;p&gt;The result can be seen on the Debian Wiki, as
4486 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
4487 table listing all MIME types supported by one of the packages included
4488 in the table&lt;/a&gt;, with the package supporting most MIME types being
4489 listed first in the table.&lt;/p&gt;
4490
4491 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
4492 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4493 kmplayer. Time for the other players to update their announced MIME
4494 support?&lt;/p&gt;
4495 </description>
4496 </item>
4497
4498 <item>
4499 <title>The Pyra - handheld computer with Debian preinstalled</title>
4500 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
4501 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
4502 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
4503 <description>A friend of mine made me aware of
4504 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
4505 handheld computer which will be delivered with Debian preinstalled. I
4506 would love to get one of those for my birthday. :)&lt;/p&gt;
4507
4508 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4509 plugs and many others connectors, and include a full keyboard and a 5&quot;
4510 LCD touch screen. The 6000mAh battery is claimed to provide a whole
4511 day of battery life time, but I have not seen any independent tests
4512 confirming this. The vendor is still collecting preorders, and the
4513 last I heard last night was that 22 more orders were needed before
4514 production started.&lt;/p&gt;
4515
4516 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
4517 Debian. Please let me know if you know of any others. Is it the
4518 first computer being sold with Debian preinstalled?&lt;/p&gt;
4519 </description>
4520 </item>
4521
4522 <item>
4523 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
4524 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
4525 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
4526 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
4527 <description>&lt;p&gt;During this weekends
4528 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
4529 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
4530 to make sure there are good books about Debian available in Norwegian
4531 Bokmål, and got in touch with the people behind the
4532 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
4533 project&lt;/a&gt; to get started. If you want to help out, please start
4534 contributing using
4535 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
4536 hosted weblate project page&lt;/a&gt;, and get in touch using
4537 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
4538 translators mailing list&lt;/a&gt;. Please also check out
4539 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
4540 contributors&lt;/a&gt;.&lt;/p&gt;
4541
4542 &lt;p&gt;The book is already available on paper in English, French and
4543 Japanese, and our goal is to get it available on paper in Norwegian
4544 Bokmål too. In addition to the paper edition, there are also EPUB and
4545 Mobi versions available. And there are incomplete translations
4546 available for many more languages.&lt;/p&gt;
4547 </description>
4548 </item>
4549
4550 <item>
4551 <title>One in two hundred Debian users using ZFS on Linux?</title>
4552 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
4553 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
4554 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
4555 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
4556 packages in Debian, and was quite surprised with what I found. I use
4557 ZFS myself at home, but did not really expect many others to do so.
4558 But I might be wrong.&lt;/p&gt;
4559
4560 &lt;p&gt;According to
4561 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
4562 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
4563 0.53% of the population, with the package installed. As far as I know
4564 the only use of the spl-linux package is as a support library for ZFS
4565 on Linux, so I use it here as proxy for measuring the number of ZFS
4566 installation on Linux in Debian. In the kFreeBSD variant of Debian
4567 the ZFS feature is already available, and there
4568 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
4569 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
4570 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
4571
4572 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
4573 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
4574 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
4575 cleared, the package is still not in Debian. The package is again in
4576 the NEW queue. Several uploads have been rejected so far because the
4577 debian/copyright file was incomplete or wrong, but there is no reason
4578 to give up. The current status can be seen on
4579 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4580 team status page&lt;/a&gt;, and
4581 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
4582 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
4583
4584 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
4585 my home server can function in the future using only official Debian
4586 packages, and the current blocker is to get the debian/copyright file
4587 accepted by the FTP masters in Debian, I decided a while back to try
4588 to help out the team. This was the background for my blog post about
4589 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
4590 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
4591 used the techniques I explored there to try to find any errors in the
4592 copyright file. It is not very easy to check every one of the around
4593 2000 files in the source package, but I hope we this time got it
4594 right. If you want to help out, check out the git source and try to
4595 find missing entries in the debian/copyright file.&lt;/p&gt;
4596 </description>
4597 </item>
4598
4599 <item>
4600 <title>Full battery stats collector is now available in Debian</title>
4601 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
4602 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
4603 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
4604 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
4605 extended collector that will collect the complete battery history for
4606 later processing and graphing. The original collector store the
4607 battery level as percentage of last full level, while the new
4608 collector also record battery vendor, model, serial number, design
4609 full level, last full level and current battery level. This make it
4610 possible to predict the lifetime of the battery as well as visualise
4611 the energy flow when the battery is charging or discharging.&lt;/p&gt;
4612
4613 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
4614 in the version 0.5.1 package in unstable. Get the new battery level graph
4615 and lifetime prediction by running:
4616
4617 &lt;p&gt;&lt;pre&gt;
4618 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4619 &lt;/pre&gt;&lt;/p&gt;
4620
4621 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
4622
4623 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
4624 entry yet):&lt;/p&gt;
4625
4626 &lt;p&gt;&lt;pre&gt;
4627 /usr/share/battery-stats/battery-stats-graph-flow
4628 &lt;/pre&gt;&lt;/p&gt;
4629
4630 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
4631 when there are few data points. The graphs look a bit better with a
4632 few years of data.&lt;/p&gt;
4633
4634 &lt;p&gt;A while back one important feature I use in the battery stats
4635 collector broke in Debian. The scripts in
4636 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4637 suspect it happened when Jessie started using systemd, but I do not
4638 know. The issue is reported as
4639 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4640 pm-utils. I managed to work around it by adding an udev rule to call
4641 the collector script every time the power connector is connected and
4642 disconnected. With this fix in place it was finally time to make a
4643 new release of the package, and get it into Debian.&lt;/p&gt;
4644
4645 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4646 check out the
4647 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4648 in Debian unstable, or rebuild it on Jessie to get it working on
4649 Debian stable. :) The upstream source is available from
4650 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4651 As always, patches are very welcome.&lt;/p&gt;
4652 </description>
4653 </item>
4654
4655 <item>
4656 <title>Making battery measurements a little easier in Debian</title>
4657 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4658 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4659 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4660 <description>&lt;p&gt;Back in September, I blogged about
4661 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4662 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4663 how it showed the decay and death of this battery (now replaced). I
4664 created a simple deb package to handle the collection and graphing,
4665 but did not want to upload it to Debian as there were already
4666 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4667 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4668 a point of uploading a competing package when battery-stats could be
4669 fixed instead. I reported a few bugs about its non-function, and
4670 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4671
4672 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4673 hands. The end result is that I am now the new upstream developer of
4674 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
4675 battery-stats in Debian, and the package in Debian unstable is finally
4676 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4677 information provided by the Linux kernel. If you install the
4678 battery-stats package from unstable now, you will be able to get a
4679 graph of the current battery fill level, to get some idea about the
4680 status of the battery. The source package build and work just fine in
4681 Debian testing and stable (and probably oldstable too, but I have not
4682 tested). The default graph you get for that system look like this:&lt;/p&gt;
4683
4684 &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;
4685
4686 &lt;p&gt;My plans for the future is to merge my old scripts into the
4687 battery-stats package, as my old scripts collected a lot more details
4688 about the battery. The scripts are merged into the upstream
4689 battery-stats git repository already, but I am not convinced they work
4690 yet, as I changed a lot of paths along the way. Will have to test a
4691 bit more before I make a new release.&lt;/p&gt;
4692
4693 &lt;p&gt;I will also consider changing the file format slightly, as I
4694 suspect the way I combine several values into one field might make it
4695 impossible to know the type of the value when using it for processing
4696 and graphing.&lt;/p&gt;
4697
4698 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4699 battery, check out the battery-stats package in
4700 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4701 on
4702 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4703 I would love some help to improve the system further.&lt;/p&gt;
4704 </description>
4705 </item>
4706
4707 <item>
4708 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4709 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4710 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4711 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4712 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4713 details. And one of the details is the content of the
4714 debian/copyright file, which should list all relevant licenses used by
4715 the code in the package in question, preferably in
4716 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4717 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4718
4719 &lt;p&gt;For large packages with lots of contributors it is hard to write
4720 and update this file manually, and if you get some detail wrong, the
4721 package is normally rejected by the ftpmasters. So getting it right
4722 the first time around get the package into Debian faster, and save
4723 both you and the ftpmasters some work.. Today, while trying to figure
4724 out what was wrong with
4725 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4726 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4727 figuring out the options for doing this job automatically, or at least
4728 semi-automatically.&lt;/p&gt;
4729
4730 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4731 file based on the code in the source package,
4732 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4733 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
4734 not sure which one of them came first, but both seem to be able to
4735 create a sensible draft file. As far as I can tell, none of them can
4736 be trusted to get the result just right, so the content need to be
4737 polished a bit before the file is OK to upload. I found the debmake
4738 option in
4739 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4740 blog posts from 2014&lt;/a&gt;.
4741
4742 &lt;p&gt;To generate using debmake, use the -cc option:
4743
4744 &lt;p&gt;&lt;pre&gt;
4745 debmake -cc &gt; debian/copyright
4746 &lt;/pre&gt;&lt;/p&gt;
4747
4748 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4749 this might not be the best option.&lt;/p&gt;
4750
4751 &lt;p&gt;The cme option is based on a config parsing library, and I found
4752 this approach in
4753 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
4754 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
4755 dpkg-copyright&#39; option:
4756
4757 &lt;p&gt;&lt;pre&gt;
4758 cme update dpkg-copyright
4759 &lt;/pre&gt;&lt;/p&gt;
4760
4761 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
4762 handle UTF-8 names better than debmake.&lt;/p&gt;
4763
4764 &lt;p&gt;When the copyright file is created, I would also like some help to
4765 check if the file is correct. For this I found two good options,
4766 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
4767 to focus on license types and file matching, and is able to detect
4768 ineffective blocks in the copyright file. The latter reports missing
4769 copyright holders and years, but was confused by inconsistent license
4770 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
4771 fix all issues reported by them before uploading. But I do not know
4772 if the tools and the ftpmasters agree on what is important to fix in a
4773 copyright file, so the package might still be rejected.&lt;/p&gt;
4774
4775 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
4776 will read through the source and try to find all copyright statements.
4777 It is not comparing the result to the content of debian/copyright, but
4778 can be useful when verifying the content of the copyright file.&lt;/p&gt;
4779
4780 &lt;p&gt;Are you aware of better tools in Debian to create and update
4781 debian/copyright file. Please let me know, or blog about it on
4782 planet.debian.org.&lt;/p&gt;
4783
4784 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4785 activities, please send Bitcoin donations to my address
4786 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4787
4788 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
4789 on how to use licensecheck and cdbs to create a draft copyright file
4790
4791 &lt;p&gt;&lt;pre&gt;
4792 licensecheck --copyright -r `find * -type f` | \
4793 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
4794 &lt;/pre&gt;&lt;/p&gt;
4795
4796 &lt;p&gt;He mentioned that he normally check the generated file into the
4797 version control system to make it easier to discover license and
4798 copyright changes in the upstream source. I will try to do the same
4799 with my packages in the future.&lt;/p&gt;
4800
4801 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
4802 against using -quiet for new users, so I removed it from the proposed
4803 command line.&lt;/p&gt;
4804 </description>
4805 </item>
4806
4807 <item>
4808 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
4809 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
4810 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
4811 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
4812 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
4813 is taking shape in Debian, and one provided feature is a very
4814 convenient way to tell you which package to install to make a given
4815 firmware file available when the kernel is looking for it. This can
4816 be done using apt-file too, but that is for someone else to blog
4817 about. :)&lt;/p&gt;
4818
4819 &lt;p&gt;Here is a small recipe to find the package with a given firmware
4820 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
4821 picked from the set of firmware announced using appstream in Debian
4822 unstable. In general you would be looking for the firmware requested
4823 by the kernel during kernel module loading. To find the package
4824 providing the example file, do like this:&lt;/p&gt;
4825
4826 &lt;blockquote&gt;&lt;pre&gt;
4827 % apt install appstream
4828 [...]
4829 % apt update
4830 [...]
4831 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
4832 awk &#39;/Package:/ {print $2}&#39;
4833 firmware-qlogic
4834 %
4835 &lt;/pre&gt;&lt;/blockquote&gt;
4836
4837 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
4838 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
4839 a way appstream can use.&lt;/p&gt;
4840
4841 &lt;p&gt;This same approach can be used to find any package supporting a
4842 given MIME type. This is very useful when you get a file you do not
4843 know how to handle. First find the mime type using &lt;tt&gt;file
4844 --mime-type&lt;/tt&gt;, and next look up the package providing support for
4845 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4846 and you can find all packages handling this type like this:&lt;/p&gt;
4847
4848 &lt;blockquote&gt;&lt;pre&gt;
4849 % apt install appstream
4850 [...]
4851 % apt update
4852 [...]
4853 % appstreamcli what-provides mimetype image/svg+xml | \
4854 awk &#39;/Package:/ {print $2}&#39;
4855 bkchem
4856 phototonic
4857 inkscape
4858 shutter
4859 tetzle
4860 geeqie
4861 xia
4862 pinta
4863 gthumb
4864 karbon
4865 comix
4866 mirage
4867 viewnior
4868 postr
4869 ristretto
4870 kolourpaint4
4871 eog
4872 eom
4873 gimagereader
4874 midori
4875 %
4876 &lt;/pre&gt;&lt;/blockquote&gt;
4877
4878 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
4879 packages providing appstream metadata.&lt;/p&gt;
4880 </description>
4881 </item>
4882
4883 <item>
4884 <title>Creepy, visualise geotagged social media information - nice free software</title>
4885 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
4886 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
4887 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
4888 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
4889 with the computerised radio beacon known as a mobile phone their
4890 position is tracked by the phone company and often stored for a long
4891 time (like every time a SMS is received or sent). And if their
4892 computerised radio beacon is capable of running programs (often called
4893 mobile apps) downloaded from the Internet, these programs are often
4894 also capable of tracking their location (if the app requested access
4895 during installation). And when these programs send out information to
4896 central collection points, the location is often included, unless
4897 extra care is taken to not send the location. The provided
4898 information is used by several entities, for good and bad (what is
4899 good and bad, depend on your point of view). What is certain, is that
4900 the private sphere and the right to free movement is challenged and
4901 perhaps even eradicated for those announcing their location this way,
4902 when they share their whereabouts with private and public
4903 entities.&lt;/p&gt;
4904
4905 &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;
4906
4907 &lt;p&gt;The phone company logs provide a register of locations to check out
4908 when one want to figure out what the tracked person was doing. It is
4909 unavailable for most of us, but provided to selected government
4910 officials, company staff, those illegally buying information from
4911 unfaithful servants and crackers stealing the information. But the
4912 public information can be collected and analysed, and a free software
4913 tool to do so is called
4914 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
4915 discovered it when I read
4916 &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
4917 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
4918 November 2014, and decided to check if it was available in Debian.
4919 The python program was in Debian, but
4920 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
4921 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
4922 uploaded a new version which did not work quite right, but did not
4923 have time to fix it then. This Christmas I decided to finally try to
4924 get Creepy operational in Debian. Now a fixed version is available in
4925 Debian unstable and testing, and almost all Debian specific patches
4926 are now included
4927 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
4928
4929 &lt;p&gt;The Creepy program visualises geolocation information fetched from
4930 Twitter, Instagram, Flickr and Google+, and allow one to get a
4931 complete picture of every social media message posted recently in a
4932 given area, or track the movement of a given individual across all
4933 these services. Earlier it was possible to use the search API of at
4934 least some of these services without identifying oneself, but these
4935 days it is impossible. This mean that to use Creepy, you need to
4936 configure it to log in as yourself on these services, and provide
4937 information to them about your search interests. This should be taken
4938 into account when using Creepy, as it will also share information
4939 about yourself with the services.&lt;/p&gt;
4940
4941 &lt;p&gt;The picture above show the twitter messages sent from (or at least
4942 geotagged with a position from) the city centre of Oslo, the capital
4943 of Norway. One useful way to use Creepy is to first look at
4944 information tagged with an area of interest, and next look at all the
4945 information provided by one or more individuals who was in the area.
4946 I tested it by checking out which celebrity provide their location in
4947 twitter messages by checkout out who sent twitter messages near a
4948 Norwegian TV station, and next could track their position over time,
4949 making it possible to locate their home and work place, among other
4950 things. A similar technique have been
4951 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
4952 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
4953 tool to discover lying governments, and a useful tool to help people
4954 understand the value of the private information they provide to the
4955 public.&lt;/p&gt;
4956
4957 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
4958 it depend on several python modules currently missing in Jessie (at
4959 least python-instagram, python-flickrapi and
4960 python-requests-toolbelt).&lt;/p&gt;
4961
4962 &lt;p&gt;(I have uploaded
4963 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
4964 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
4965 Creepy program in Debian.)&lt;/p&gt;
4966 </description>
4967 </item>
4968
4969 <item>
4970 <title>Always download Debian packages using Tor - the simple recipe</title>
4971 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
4972 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
4973 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
4974 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
4975 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
4976 that those listening on the Internet lines would have good reason to
4977 believe a computer have a given security hole&lt;/a&gt; if it download a
4978 security fix from a Debian mirror. This is a good reason to always
4979 use encrypted connections to the Debian mirror, to make sure those
4980 listening do not know which IP address to attack. In August, Richard
4981 Hartmann observed that encryption was not enough, when it was possible
4982 to interfere download size to security patches or the fact that
4983 download took place shortly after a security fix was released, and
4984 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
4985 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
4986 was not the first to propose this, as the
4987 &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;
4988 package by Tim Retout already existed to make it easy to convince apt
4989 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
4990 aware of that package when I read the blog post from Richard.&lt;/p&gt;
4991
4992 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
4993 sysadmins, and he set up a Tor hidden service on one of the central
4994 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4995 it possible to download packages directly between two tor nodes,
4996 making sure the network traffic always were encrypted.&lt;/p&gt;
4997
4998 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
4999 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
5000 urls with tor+http and tor+https, and using the hidden service instead
5001 of the official Debian mirror site. I recommend installing
5002 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
5003 done in /etc/.&lt;/p&gt;
5004
5005 &lt;blockquote&gt;&lt;pre&gt;
5006 apt install apt-transport-tor
5007 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
5008 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
5009 &lt;/pre&gt;&lt;/blockquote&gt;
5010
5011 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
5012 the sed commands for these too. The sed command is assuming your are
5013 using the ftp.debian.org Debian mirror. Adjust the command (or just
5014 edit the file manually) to match your mirror.&lt;/p&gt;
5015
5016 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
5017 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
5018 system, and do not work with these tor+http URLs. For
5019 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
5020 which need a recent apt version currently only in unstable. So if you
5021 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
5022
5023 &lt;p&gt;Another advantage from this change is that your machine will start
5024 using Tor regularly and at fairly random intervals (every time you
5025 update the package lists or upgrade or install a new package), thus
5026 masking other Tor traffic done from the same machine. Using Tor will
5027 become normal for the machine in question.&lt;/p&gt;
5028
5029 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
5030 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
5031 enabled. It would be great if it was the default on any Debian
5032 system.&lt;/p&gt;
5033 </description>
5034 </item>
5035
5036 <item>
5037 <title>OpenALPR, find car license plates in video streams - nice free software</title>
5038 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
5039 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
5040 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
5041 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
5042 call the car license plate numbers in those days. I would write the
5043 numbers down in my little book and compare notes with the other kids
5044 to see how many region codes we had seen and if we had seen some
5045 exotic or special region codes and numbers. It was a fun game to pass
5046 time, as we kids have plenty of it.&lt;/p&gt;
5047
5048 &lt;p&gt;A few days I came across
5049 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
5050 project&lt;/a&gt;, a free software project to automatically discover and
5051 report license plates in images and video streams, and provide the
5052 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
5053 such system for a while now, because I believe it is a bad idea that the
5054 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
5055 number plate recognition&lt;/a&gt; tool only is available in the hands of
5056 the powerful, and want it to be available also for the powerless to
5057 even the score when it comes to surveillance and sousveillance. I
5058 discovered the developer
5059 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
5060 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
5061 help him get it into shape to get the package uploaded into the Debian
5062 archive.&lt;/p&gt;
5063
5064 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
5065 it into Debian, where it currently
5066 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
5067 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
5068
5069 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
5070 for the common folks, ie those not running a large government
5071 surveillance system? Well, I plan to put it in a computer on my bike
5072 and in my car, tracking the cars nearby and allowing me to be notified
5073 when number plates on my watch list are discovered. Another use case
5074 was suggested by a friend of mine, who wanted to set it up at his home
5075 to open the car port automatically when it discovered the plate on his
5076 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5077 capable of placing his license plate number of a piece of cardboard to
5078 open his car port, men replied that it was always unlocked anyway. I
5079 guess for such use case it make sense. I am sure there are other use
5080 cases too, for those with imagination and a vision.&lt;/p&gt;
5081
5082 &lt;p&gt;If you want to build your own version of the Debian package, check
5083 out the upstream git source and symlink ./distros/debian to ./debian/
5084 before running &quot;debuild&quot; to build the source. Or wait a bit until the
5085 package show up in unstable.&lt;/p&gt;
5086 </description>
5087 </item>
5088
5089 <item>
5090 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
5091 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
5092 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
5093 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
5094 <description>&lt;p&gt;Around three years ago, I created
5095 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
5096 system&lt;/a&gt; to get a more practical solution in Debian for handing
5097 hardware related packages. A GUI system in the isenkram package will
5098 present a pop-up dialog when some hardware dongle supported by
5099 relevant packages in Debian is inserted into the machine. The same
5100 lookup mechanism to detect packages is available as command line
5101 tools in the isenkram-cli package. In addition to mapping hardware,
5102 it will also map kernel firmware files to packages and make it easy to
5103 install needed firmware packages automatically. The key for this
5104 system to work is a good way to map hardware to packages, in other
5105 words, allow packages to announce what hardware they will work
5106 with.&lt;/p&gt;
5107
5108 &lt;p&gt;I started by providing data files in the isenkram source, and
5109 adding code to download the latest version of these data files at run
5110 time, to ensure every user had the most up to date mapping available.
5111 I also added support for storing the mapping in the Packages file in
5112 the apt repositories, but did not push this approach because while I
5113 was trying to figure out how to best store hardware/package mappings,
5114 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
5115 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
5116 add the hardware mapping into that data set to be able to use
5117 appstream as a data source, and this was accepted at least for the
5118 Debian version of appstream.&lt;/p&gt;
5119
5120 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
5121 and today I uploaded a new version 0.20 of isenkram adding support for
5122 appstream as a data source for mapping hardware to packages. The only
5123 package so far using appstream to announce its hardware support is my
5124 pymissile package. I got help from Matthias Klumpp with figuring out
5125 how do add the required
5126 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
5127 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
5128 this content:&lt;/p&gt;
5129
5130 &lt;blockquote&gt;&lt;pre&gt;
5131 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
5132 &amp;lt;component&amp;gt;
5133 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
5134 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
5135 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
5136 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
5137 &amp;lt;description&amp;gt;
5138 &amp;lt;p&amp;gt;
5139 Pymissile provides a curses interface to control an original
5140 Marks and Spencer / Striker USB Missile Launcher, as well as a
5141 motion control script to allow a webcamera to control the
5142 launcher.
5143 &amp;lt;/p&amp;gt;
5144 &amp;lt;/description&amp;gt;
5145 &amp;lt;provides&amp;gt;
5146 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
5147 &amp;lt;/provides&amp;gt;
5148 &amp;lt;/component&amp;gt;
5149 &lt;/pre&gt;&lt;/blockquote&gt;
5150
5151 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
5152 which is a glob style match rule for hardware specific strings
5153 (modalias strings) provided by the Linux kernel. In this case, it
5154 will map to all USB devices with vendor code 1130 and product code
5155 0202.&lt;/p&gt;
5156
5157 &lt;p&gt;Note, it is important that the license of all the metadata files
5158 are compatible to have permissions to aggregate them into archive wide
5159 appstream files. Matthias suggested to use MIT or BSD licenses for
5160 these files. A challenge is figuring out a good id for the data, as
5161 it is supposed to be globally unique and shared across distributions
5162 (in other words, best to coordinate with upstream what to use). But
5163 it can be changed later or, so we went with the package name as
5164 upstream for this project is dormant.&lt;/p&gt;
5165
5166 &lt;p&gt;To get the metadata file installed in the correct location for the
5167 mirror update scripts to pick it up and include its content the
5168 appstream data source, the file must be installed in the binary
5169 package under /usr/share/appdata/. I did this by adding the following
5170 line to debian/pymissile.install:&lt;/p&gt;
5171
5172 &lt;blockquote&gt;&lt;pre&gt;
5173 debian/pymissile.metainfo.xml usr/share/appdata
5174 &lt;/pre&gt;&lt;/blockquote&gt;
5175
5176 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
5177 all packages useful on the current computer automatically, and the GUI
5178 pop-up handler will propose to install the package not already
5179 installed if a hardware dongle is inserted into the machine in
5180 question.&lt;/p&gt;
5181
5182 &lt;p&gt;Details of the modalias field in appstream is available from the
5183 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
5184
5185 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
5186 try running this command on the command line:&lt;/p&gt;
5187
5188 &lt;blockquote&gt;&lt;pre&gt;
5189 cat $(find /sys/devices/|grep modalias)
5190 &lt;/pre&gt;&lt;/blockquote&gt;
5191
5192 &lt;p&gt;To learn more about the isenkram system, please check out
5193 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
5194 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
5195 </description>
5196 </item>
5197
5198 <item>
5199 <title>The GNU General Public License is not magic pixie dust</title>
5200 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
5201 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
5202 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
5203 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
5204 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
5205 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
5206 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
5207 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
5208
5209 &lt;blockquote&gt;
5210
5211 &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;
5212
5213 &lt;blockquote&gt;
5214 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
5215
5216 The first step is to choose a
5217 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
5218 code.&lt;br/&gt;
5219
5220 The next step is, when someone fails to follow that copyleft license,
5221 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
5222
5223 and its a simple fact of our modern society that such type of
5224 work&lt;br/&gt;
5225
5226 is incredibly expensive to do and incredibly difficult to do.
5227 &lt;/blockquote&gt;
5228
5229 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
5230 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
5231 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
5232 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
5233
5234 &lt;p&gt;As the Debian Website
5235 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
5236 &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;
5237 imply, public domain and permissively licensed software can lead to
5238 the production of more proprietary software as people discover useful
5239 software, extend it and or incorporate it into their hardware or
5240 software products. Copyleft licenses such as the GNU GPL were created
5241 to close off this avenue to the production of proprietary software but
5242 such licenses are not enough. With the ongoing adoption of Free
5243 Software by individuals and groups, inevitably the community&#39;s
5244 expectations of license compliance are violated, usually out of
5245 ignorance of the way Free Software works, but not always. As Karen
5246 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
5247 Freedom&quot;&gt;FaiF&lt;/a&gt;
5248 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
5249 copyleft is nothing if no-one is willing and able to stand up in court
5250 to protect it. The reality of today&#39;s world is that legal
5251 representation is expensive, difficult and time consuming. With
5252 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
5253 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
5254 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
5255 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
5256 of the Linux project, Debian and other groups against GPL violations.
5257 In March the SFC supported a
5258 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
5259 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
5260 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
5261 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
5262 kernel. Since then two of their sponsors pulled corporate funding and
5263 conferences
5264 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
5265 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
5266 less on corporate funding and more on the broad community of
5267 individuals who support Free Software and copyleft. So the SFC has
5268 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
5269 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
5270 a community of folks who stand up for copyleft and the GPL by
5271 supporting their work on promoting and supporting copyleft and Free
5272 Software.&lt;/p&gt;
5273
5274 &lt;p&gt;If you support Free Software,
5275 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
5276 what the SFC do, agree with their
5277 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
5278 principles&lt;/a&gt;, are happy about their
5279 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
5280 work on a project that is an SFC
5281 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
5282 just want to stand up for copyleft, please join
5283 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
5284 Allan Webber&lt;/a&gt;,
5285 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
5286 Smith&lt;/a&gt;,
5287 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
5288 Bacon&lt;/a&gt;, myself and
5289 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
5290 becoming a
5291 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
5292 next week your donation will be
5293 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
5294 by an anonymous donor. Please also consider asking your employer to
5295 match your donation or become a sponsor of SFC. Don&#39;t forget to
5296 spread the word about your support for SFC via email, your blog and or
5297 social media accounts.&lt;/p&gt;
5298
5299 &lt;/blockquote&gt;
5300
5301 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
5302 of Software Freedom Conservancy myself. Perhaps you should be a
5303 supporter too?&lt;/p&gt;
5304 </description>
5305 </item>
5306
5307 <item>
5308 <title>PGP key transition statement for key EE4E02F9</title>
5309 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
5310 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
5311 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
5312 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
5313 set it up properly. I wanted to generate it offline and have it
5314 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
5315 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
5316 time to sit down with an offline machine almost took forever. But
5317 finally I&#39;ve been able to complete the process, and have now moved
5318 from my old GPG key to a new GPG key. See
5319 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
5320 full transition statement, signed with both my old and new key&lt;/a&gt; for
5321 the details. This is my new key:&lt;/p&gt;
5322
5323 &lt;pre&gt;
5324 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]
5325 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
5326 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
5327 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
5328 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
5329 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
5330 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
5331 &lt;/pre&gt;
5332
5333 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
5334 my old key.&lt;/p&gt;
5335
5336 &lt;p&gt;If you signed my old key
5337 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
5338 I&#39;d very much appreciate a signature on my new key, details and
5339 instructions in the transition statement. I m happy to reciprocate if
5340 you have a similarly signed transition statement to present.&lt;/p&gt;
5341 </description>
5342 </item>
5343
5344 <item>
5345 <title>The life and death of a laptop battery</title>
5346 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
5347 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
5348 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
5349 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
5350 But this do not last. The last few laptops gave me a feeling that
5351 within a year, the life time is just a fraction of what it used to be,
5352 and it slowly become painful to use the laptop without power connected
5353 all the time. Because of this, when I got a new Thinkpad X230 laptop
5354 about two years ago, I decided to monitor its battery state to have
5355 more hard facts when the battery started to fail.&lt;/p&gt;
5356
5357 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
5358
5359 &lt;p&gt;First I tried to find a sensible Debian package to record the
5360 battery status, assuming that this must be a problem already handled
5361 by someone else. I found
5362 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
5363 which collects statistics from the battery, but it was completely
5364 broken. I sent a few suggestions to the maintainer, but decided to
5365 write my own collector as a shell script while I waited for feedback
5366 from him. Via
5367 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
5368 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
5369 discovered
5370 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
5371 available in Debian.&lt;/p&gt;
5372
5373 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
5374 battery stats ever since. Now my
5375 /var/log/hjemmenett-battery-status.log file contain around 115,000
5376 measurements, from the time the battery was working great until now,
5377 when it is unable to charge above 7% of original capacity. My
5378 collector shell script is quite simple and look like this:&lt;/p&gt;
5379
5380 &lt;pre&gt;
5381 #!/bin/sh
5382 # Inspired by
5383 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
5384 # See also
5385 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
5386 logfile=/var/log/hjemmenett-battery-status.log
5387
5388 files=&quot;manufacturer model_name technology serial_number \
5389 energy_full energy_full_design energy_now cycle_count status&quot;
5390
5391 if [ ! -e &quot;$logfile&quot; ] ; then
5392 (
5393 printf &quot;timestamp,&quot;
5394 for f in $files; do
5395 printf &quot;%s,&quot; $f
5396 done
5397 echo
5398 ) &gt; &quot;$logfile&quot;
5399 fi
5400
5401 log_battery() {
5402 # Print complete message in one echo call, to avoid race condition
5403 # when several log processes run in parallel.
5404 msg=$(printf &quot;%s,&quot; $(date +%s); \
5405 for f in $files; do \
5406 printf &quot;%s,&quot; $(cat $f); \
5407 done)
5408 echo &quot;$msg&quot;
5409 }
5410
5411 cd /sys/class/power_supply
5412
5413 for bat in BAT*; do
5414 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
5415 done
5416 &lt;/pre&gt;
5417
5418 &lt;p&gt;The script is called when the power management system detect a
5419 change in the power status (power plug in or out), and when going into
5420 and out of hibernation and suspend. In addition, it collect a value
5421 every 10 minutes. This make it possible for me know when the battery
5422 is discharging, charging and how the maximum charge change over time.
5423 The code for the Debian package
5424 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
5425 available on github&lt;/a&gt;.&lt;/p&gt;
5426
5427 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
5428
5429 &lt;pre&gt;
5430 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5431 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
5432 [...]
5433 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5434 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5435 &lt;/pre&gt;
5436
5437 &lt;p&gt;I wrote a small script to create a graph of the charge development
5438 over time. This graph depicted above show the slow death of my laptop
5439 battery.&lt;/p&gt;
5440
5441 &lt;p&gt;But why is this happening? Why are my laptop batteries always
5442 dying in a year or two, while the batteries of space probes and
5443 satellites keep working year after year. If we are to believe
5444 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
5445 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
5446 chance, and the fix is to not charge the Lithium-ion batteries to 100%
5447 all the time, but to stay below 90% of full charge most of the time.
5448 I&#39;ve been told that the Tesla electric cars
5449 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
5450 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
5451 100% when preparing for a longer trip (not that I would want a car
5452 like Tesla where rights to privacy is abandoned, but that is another
5453 story), which I guess is the option we should have for laptops on
5454 Linux too.&lt;/p&gt;
5455
5456 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
5457 stop charging at 80%, unless requested to charge to 100% once in
5458 preparation for a longer trip? I found
5459 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
5460 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5461 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
5462 load).&lt;/p&gt;
5463
5464 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
5465 at the start. I also wonder why the &quot;full capacity&quot; increases some
5466 times, and if it is possible to repeat the process to get the battery
5467 back to design capacity. And I wonder if the discharge and charge
5468 speed change over time, or if this stay the same. I did not yet try
5469 to write a tool to calculate the derivative values of the battery
5470 level, but suspect some interesting insights might be learned from
5471 those.&lt;/p&gt;
5472
5473 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
5474 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5475 packages instead of the tp-smapi-dkms package I had tried to use
5476 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
5477 and stop. I&#39;ve done so now, but expect my existing battery is toast
5478 and need to be replaced. The proposal is unfortunately Thinkpad
5479 specific.&lt;/p&gt;
5480 </description>
5481 </item>
5482
5483 <item>
5484 <title>New laptop - some more clues and ideas based on feedback</title>
5485 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
5486 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
5487 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
5488 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
5489 need for a new laptop, and provided very useful feedback. I wish to
5490 thank every one of these. Several pointed me to the possibility of
5491 fixing my X230, and I am already in the process of getting Lenovo to
5492 do so thanks to the on site, next day support contract covering the
5493 machine. But the battery is almost useless (I expect to replace it
5494 with a non-official battery) and I do not expect the machine to live
5495 for many more years, so it is time to plan its replacement. If I did
5496 not have a support contract, it was suggested to find replacement parts
5497 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
5498 might present a language barrier as I do not understand French.&lt;/p&gt;
5499
5500 &lt;p&gt;One tip I got was to use the
5501 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
5502 compare laptop models. It seem to have more models available than
5503 prisjakt.no. Another tip I got from someone I know have similar
5504 keyboard preferences was that the HP EliteBook 840 keyboard is not
5505 very good, and this matches my experience with earlier EliteBook
5506 keyboards I tested. Because of this, I will not consider it any further.
5507
5508 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
5509 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5510 (which is missing from the X240), and is working fairly well with
5511 Debian Sid/Unstable according to
5512 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
5513 got on the keyboard quality are not consistent. Some say the keyboard
5514 is good, others say it is ok, while others say it is not very good.
5515 Those with experience from X41 and and X60 agree that the X250
5516 keyboard is not as good as those trusty old laptops, and suggest I
5517 keep and fix my X230 instead of upgrading, or get a used X230 to
5518 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
5519 activity and battery status, which is very convenient on my X230. I&#39;m
5520 also told that the CPU fan is running very often, making it a bit
5521 noisy. In any case, the X250 do not work out of the box with Debian
5522 Stable/Jessie, one of my requirements.&lt;/p&gt;
5523
5524 &lt;p&gt;I have also gotten a few vendor proposals, one was
5525 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
5526 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
5527 The latter look very attractive to me.&lt;/p&gt;
5528
5529 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
5530 as I keep looking for a replacement.&lt;/p&gt;
5531
5532 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
5533 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
5534 different
5535 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
5536 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
5537 </description>
5538 </item>
5539
5540 <item>
5541 <title>Time to find a new laptop, as the old one is broken after only two years</title>
5542 <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>
5543 <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>
5544 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
5545 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
5546 replacement soon. The left 5 cm of the screen on my Thinkpad X230
5547 started flickering yesterday, and I suspect the cause is a broken
5548 cable, as changing the angle of the screen some times get rid of the
5549 flickering.&lt;/p&gt;
5550
5551 &lt;p&gt;My requirements have not really changed since I bought it, and is
5552 still as
5553 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
5554 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
5555 good help from
5556 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
5557 where I could select at least a few of the requirements (mouse pin,
5558 wifi, weight) and go through the rest manually. Three button mouse
5559 and a good keyboard is not available as an option, and all the three
5560 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
5561 G2) lack three mouse buttons). It is also unclear to me how good the
5562 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5563 the keyboard, even if the quality and robustness in the X series have
5564 deteriorated since X41.&lt;/p&gt;
5565
5566 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
5567 seem sensible to me? Are there better services around to search the
5568 set of available laptops for features? Please send me an email if you
5569 have suggestions.&lt;/p&gt;
5570
5571 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
5572 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
5573 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
5574 </description>
5575 </item>
5576
5577 <item>
5578 <title>How to stay with sysvinit in Debian Jessie</title>
5579 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
5580 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
5581 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
5582 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
5583 sysvinit as its boot system by default. But how can one keep using
5584 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5585 courtesy of
5586 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
5587 Schubert&lt;/a&gt; and
5588 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
5589 McVittie&lt;/a&gt;.
5590
5591 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
5592 keep sysvinit as your boot system, create a file
5593 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
5594 you upgrade:&lt;/p&gt;
5595
5596 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5597 Package: systemd-sysv
5598 Pin: release o=Debian
5599 Pin-Priority: -1
5600 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5601
5602 &lt;p&gt;This file content will tell apt and aptitude to not consider
5603 installing systemd-sysv as part of any installation and upgrade
5604 solution when resolving dependencies, and thus tell it to avoid
5605 systemd as a default boot system. The end result should be that the
5606 upgraded system keep using sysvinit.&lt;/p&gt;
5607
5608 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
5609 get sysvinit installed by default (debootstrap used by
5610 debian-installer have no option for this), but one can tell the
5611 installer to switch to sysvinit before the first boot. Either by
5612 using a kernel argument to the installer, or by adding a line to the
5613 preseed file used. First, the kernel command line argument:
5614
5615 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5616 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
5617 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5618
5619 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
5620
5621 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5622 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5623 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5624
5625 &lt;p&gt;One can of course also do this after the first boot by installing
5626 the sysvinit-core package.&lt;/p&gt;
5627
5628 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
5629 sysvinit boot sequence in Debian have several hardware specific bugs
5630 on Linux caused by the fact that it is unpredictable when hardware
5631 devices show up during boot. But on the other hand, the new default
5632 boot system still have a few rough edges I hope will be fixed before
5633 Jessie is released.&lt;/p&gt;
5634
5635 &lt;p&gt;Update 2014-11-26: Inspired by
5636 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5637 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5638 line.&lt;/p&gt;
5639 </description>
5640 </item>
5641
5642 <item>
5643 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5644 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5645 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5646 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5647 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5648 without anyone snooping, is a right every citicen have in a liberal
5649 democracy. But this right is under serious attack these days.&lt;/p&gt;
5650
5651 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5652 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5653 the whisleblower Snowden) more expensive for Internet email,
5654 is to deliver all email using SMTP via Tor. Such SMTP option would be
5655 a nice addition to the FreedomBox project if we could send email
5656 between FreedomBox machines without leaking metadata about the emails
5657 to the people peeking on the wire. I
5658 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5659 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5660 lot of useful feedback and suggestions. It also became obvious to me
5661 that this was not a novel idea, as the same idea was tested and
5662 documented by Johannes Berg as early as 2006, and both
5663 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5664 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5665 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5666
5667 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5668 providing the SMTP protocol on port 25, and use email addresses
5669 looking like username@hidden-service-name.onion. With such addresses
5670 the connections to port 25 on hidden-service-name.onion using Tor will
5671 go to the correct SMTP server. To do this, one need to configure the
5672 Tor daemon to provide the hidden service and the mail server to accept
5673 emails for this .onion domain. To learn more about Exim configuration
5674 in Debian and test the design provided by Johannes Berg in his FAQ, I
5675 set out yesterday to create a Debian package for making it trivial to
5676 set up such SMTP over Tor service based on Debian. Getting it to work
5677 were fairly easy, and
5678 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5679 source code for the Debian package&lt;/a&gt; is available from github. I
5680 plan to move it into Debian if further testing prove this to be a
5681 useful approach.&lt;/p&gt;
5682
5683 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5684 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5685 get rid of exim4). Install tor, clone the git repository mentioned
5686 above, build the deb and install it on the machine. Next, run
5687 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5688 the instructions to get the service up and running. Restart tor and
5689 exim when it is done, and test mail delivery using swaks like
5690 this:&lt;/p&gt;
5691
5692 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5693 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5694 --to fbx@dutlqrrmjhtfa3vp.onion
5695 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5696
5697 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5698 address with your own address to test your server. :)&lt;/p&gt;
5699
5700 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5701 easier and more automatic. Especially the tor setup need more work.
5702 Also, the package include a tor-smtp tool written in C, but its task
5703 should probably be rewritten in some script language to make the deb
5704 architecture independent. It would probably also make the code easier
5705 to review. The tor-smtp tool currently need to listen on a socket for
5706 exim to talk to it and is started using xinetd. It would be better if
5707 no daemon and no socket is needed. I suspect it is possible to get
5708 exim to run a command line tool for delivery instead of talking to a
5709 socket, and hope to figure out how in a future version of this
5710 system.&lt;/p&gt;
5711
5712 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5713 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5714 SMTorP. :)&lt;/p&gt;
5715 </description>
5716 </item>
5717
5718 <item>
5719 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5720 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5721 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5722 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5723 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5724 alioth.debian.org, you know the web interface is fairly slow to
5725 operate. First you visit one web page, enter the moderation password
5726 and get a new page shown with a list of all the messages to moderate
5727 and various options for each email address. This take a while for
5728 every list you moderate, and you need to do it regularly to do a good
5729 job as a list moderator. But there is a quick alternative,
5730 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5731 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5732 to moderate in a fraction of a second. Here is a test run on two
5733 lists I recently took over:&lt;/p&gt;
5734
5735 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5736 % time listadmin xiph
5737 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5738 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5739
5740 real 0m1.709s
5741 user 0m0.232s
5742 sys 0m0.012s
5743 %
5744 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5745
5746 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5747 there are no message in the moderation queue. Every morning I
5748 currently moderate 68 mailman lists, and it normally take around two
5749 minutes. When I took over the two pkg-xiph lists above a few days
5750 ago, there were 400 emails waiting in the moderator queue. It took me
5751 less than 15 minutes to process them all using the listadmin
5752 program.&lt;/p&gt;
5753
5754 &lt;p&gt;If you install
5755 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
5756 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
5757 with content like this, the moderation task is a breeze:&lt;/p&gt;
5758
5759 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5760 username username@example.org
5761 spamlevel 23
5762 default discard
5763 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
5764
5765 password secret
5766 adminurl https://{domain}/mailman/admindb/{list}
5767 mailman-list@lists.example.com
5768
5769 password hidden
5770 other-list@otherserver.example.org
5771 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5772
5773 &lt;p&gt;There are other options to set as well. Check the manual page to
5774 learn the details.&lt;/p&gt;
5775
5776 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
5777 the SSL certificate is self signed or not properly signed by a
5778 generally accepted signing authority, you can set a environment
5779 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
5780
5781 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5782 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
5783 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5784
5785 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
5786 can provide an argument to the listadmin script like I do in the
5787 initial screen dump (the xiph argument). Using an argument, only
5788 lists matching the argument string will be processed. This make it
5789 quick to accept messages if you notice the moderation request in your
5790 email.&lt;/p&gt;
5791
5792 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
5793 mailing lists, as I simply do not have time to spend on that if the
5794 process was any slower. The listadmin program have saved me hours of
5795 time I could spend elsewhere over the years. It truly is nice free
5796 software.&lt;/p&gt;
5797
5798 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5799 activities, please send Bitcoin donations to my address
5800 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5801
5802 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
5803 configuration example. Also, I&#39;ve been told that the
5804 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
5805 sure why.&lt;/p&gt;
5806 </description>
5807 </item>
5808
5809 <item>
5810 <title>Debian Jessie, PXE and automatic firmware installation</title>
5811 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
5812 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
5813 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
5814 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
5815 problem that the WiFi card require some firmware to work properly.
5816 And it has been a pain to fix this using preseeding in Debian.
5817 Normally something more is needed. But thanks to
5818 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
5819 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
5820 to do this using simple preseeding.&lt;/p&gt;
5821
5822 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
5823 firmware for the hardware found in the machine (actually, requested by
5824 the kernel modules for the hardware). (It can also install user space
5825 programs supporting the hardware detected, but that is not the focus
5826 of this story.)&lt;/p&gt;
5827
5828 &lt;p&gt;To get this working in the default installation, two preeseding
5829 values are needed. First, the isenkram-cli package must be installed
5830 into the target chroot (aka the hard drive) before tasksel is executed
5831 in the pkgsel step of the debian-installer system. This is done by
5832 preseeding the base-installer/includes debconf value to include the
5833 isenkram-cli package. The package name is next passed to debootstrap
5834 for installation. With the isenkram-cli package in place, tasksel
5835 will automatically use the isenkram tasks to detect hardware specific
5836 packages for the machine being installed and install them, because
5837 isenkram-cli contain tasksel tasks.&lt;/p&gt;
5838
5839 &lt;p&gt;Second, one need to enable the non-free APT repository, because
5840 most firmware unfortunately is non-free. This is done by preseeding
5841 the apt-mirror-setup step. This is unfortunate, but for a lot of
5842 hardware it is the only option in Debian.&lt;/p&gt;
5843
5844 &lt;p&gt;The end result is two lines needed in your preseeding file to get
5845 firmware installed automatically by the installer:&lt;/p&gt;
5846
5847 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5848 base-installer base-installer/includes string isenkram-cli
5849 apt-mirror-setup apt-setup/non-free boolean true
5850 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5851
5852 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
5853 both firmware and user space packages when using this method. It also
5854 do not work well, so use version 0.15 or later. Installing both
5855 firmware and user space packages might give you a bit more than you
5856 want, so I decided to split the tasksel task in two, one for firmware
5857 and one for user space programs. The firmware task is enabled by
5858 default, while the one for user space programs is not. This split is
5859 implemented in the package currently in unstable.&lt;/p&gt;
5860
5861 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
5862 this recipe work for you. :)&lt;/p&gt;
5863
5864 &lt;p&gt;So, I bet you are wondering, how can this work. First and
5865 foremost, it work because tasksel is modular, and driven by whatever
5866 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5867 isenkram-cli package place two files for tasksel to find. First there
5868 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
5869
5870 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5871 Task: isenkram-packages
5872 Section: hardware
5873 Description: Hardware specific packages (autodetected by isenkram)
5874 Based on the detected hardware various hardware specific packages are
5875 proposed.
5876 Test-new-install: show show
5877 Relevance: 8
5878 Packages: for-current-hardware
5879
5880 Task: isenkram-firmware
5881 Section: hardware
5882 Description: Hardware specific firmware packages (autodetected by isenkram)
5883 Based on the detected hardware various hardware specific firmware
5884 packages are proposed.
5885 Test-new-install: mark show
5886 Relevance: 8
5887 Packages: for-current-hardware-firmware
5888 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5889
5890 &lt;p&gt;The key parts are Test-new-install which indicate how the task
5891 should be handled and the Packages line referencing to a script in
5892 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5893 list of packages to install. The for-current-hardware-firmware script
5894 look like this to list relevant firmware for the machine:
5895
5896 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5897 #!/bin/sh
5898 #
5899 PATH=/usr/sbin:$PATH
5900 export PATH
5901 isenkram-autoinstall-firmware -l
5902 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5903
5904 &lt;p&gt;With those two pieces in place, the firmware is installed by
5905 tasksel during the normal d-i run. :)&lt;/p&gt;
5906
5907 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
5908 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
5909 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
5910 install.&lt;/p&gt;
5911
5912 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
5913 pilots in testing this feature, as isenkram is used there now to
5914 install firmware, replacing the earlier scripts.&lt;/p&gt;
5915 </description>
5916 </item>
5917
5918 <item>
5919 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
5920 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
5921 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
5922 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
5923 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
5924 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5925 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
5926 on a screen normally showing the bread types and prizes:&lt;/p&gt;
5927
5928 &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;
5929
5930 &lt;p&gt;If it had booted as it was supposed to, I would never had known
5931 about this hidden Linux installation. It is interesting what
5932 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
5933 </description>
5934 </item>
5935
5936 <item>
5937 <title>New lsdvd release version 0.17 is ready</title>
5938 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
5939 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
5940 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
5941 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
5942 got a new set of developers a few weeks ago, after the original
5943 developer decided to step down and pass the project to fresh blood.
5944 This project is now maintained by Petter Reinholdtsen and Steve
5945 Dibb.&lt;/p&gt;
5946
5947 &lt;p&gt;I just wrapped up
5948 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
5949 new lsdvd release&lt;/a&gt;, available in git or from
5950 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
5951 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
5952 0.17.&lt;/p&gt;
5953
5954 &lt;ul&gt;
5955
5956 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
5957 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
5958 non-existant, to work around additional copy protection&lt;/li&gt;
5959 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
5960 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
5961 &lt;li&gt;Fix include orders&lt;/li&gt;
5962 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
5963 &lt;li&gt;Fix the chapter count&lt;/li&gt;
5964 &lt;li&gt;Make sure the array size and the array limit used when initialising
5965 the palette size is the same.&lt;/li&gt;
5966 &lt;li&gt;Fix array printing.&lt;/li&gt;
5967 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
5968 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
5969 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
5970 with more GCC compiler warnings.&lt;/li&gt;
5971
5972 &lt;/ul&gt;
5973
5974 &lt;p&gt;This change bring together patches for lsdvd in use in various
5975 Linux and Unix distributions, as well as patches submitted to the
5976 project the last nine years. Please check it out. :)&lt;/p&gt;
5977 </description>
5978 </item>
5979
5980 <item>
5981 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
5982 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
5983 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
5984 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
5985 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5986 project&lt;/a&gt; provide a Linux solution for schools, including a
5987 powerful desktop with education software, a central server providing
5988 web pages, user database, user home directories, central login and PXE
5989 boot of both clients without disk and the installation to install Debian
5990 Edu on machines with disk (and a few other services perhaps to small
5991 to mention here). We in the Debian Edu team are currently working on
5992 the Jessie based version, trying to get everything in shape before the
5993 freeze, to avoid having to maintain our own package repository in the
5994 future. The
5995 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
5996 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
5997 work left. Some fatal problems block testing, breaking the installer,
5998 but it is possible to work around these to get anyway. Here is a
5999 recipe on how to get the installation limping along.&lt;/p&gt;
6000
6001 &lt;p&gt;First, download the test ISO via
6002 &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;,
6003 &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;
6004 or rsync (use
6005 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
6006 The ISO build was broken on Tuesday, so we do not get a new ISO every
6007 12 hours or so, but thankfully the ISO we already got we are able to
6008 install with some tweaking.&lt;/p&gt;
6009
6010 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
6011 (use Alt-Ctrl-F2), run&lt;/p&gt;
6012
6013 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6014 nano /usr/bin/edu-eatmydata-install
6015 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6016
6017 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
6018 optimization. Return to the installation, select the profile you want
6019 and continue. Without this change, exim4-config will fail to install
6020 due to a known bug in eatmydata.&lt;/p&gt;
6021
6022 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
6023 this do not work, figure out what your correct value would be. All my
6024 test machines need /dev/sda, so I have no advice if it do not fit
6025 your need.&lt;/p&gt;
6026
6027 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
6028 root after the initial boot from hard drive, and install the
6029 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
6030 or mate. If you want several desktop options, install more than one
6031 metapackage. Once this is done, reboot and you should have a working
6032 graphical login screen. This workaround should no longer be needed
6033 once the education-tasks package version 1.801 enter testing in two
6034 days.&lt;/p&gt;
6035
6036 &lt;p&gt;I believe the ISO build will start working on two days when the new
6037 tasksel package enter testing and Steve McIntyre get a chance to
6038 update the debian-cd git repository. The eatmydata, grub and desktop
6039 issues are already fixed in unstable and testing, and should show up
6040 on the ISO as soon as the ISO build start working again. Well the
6041 eatmydata optimization is really just disabled. The proper fix
6042 require an upload by the eatmydata maintainer applying the patch
6043 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
6044 The rest have proper fixes in unstable.&lt;/p&gt;
6045
6046 &lt;p&gt;I hope this get you going with the installation testing, as we are
6047 quickly running out of time trying to get our Jessie based
6048 installation ready before the distribution freeze in a month.&lt;/p&gt;
6049 </description>
6050 </item>
6051
6052 <item>
6053 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
6054 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
6055 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
6056 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
6057 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
6058 to handle my fairly large DVD collection. It is a nice command line
6059 tool to get details about a DVD, like title, tracks, track length,
6060 etc, in XML, Perl or human readable format. But lsdvd have not seen
6061 any new development since 2006 and had a few irritating bugs affecting
6062 its use with some DVDs. Upstream seemed to be dead, and in January I
6063 sent a small probe asking for a version control repository for the
6064 project, without any reply. But I use it regularly and would like to
6065 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
6066 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
6067 the project admin, and after getting a reply from him explaining that
6068 he was no longer interested in the project, I asked if I could take
6069 over. And yesterday, I became project admin.&lt;/p&gt;
6070
6071 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
6072 maintainer interested in joining forces to maintain the upstream
6073 project, and I hope we can get a new release out fairly quickly,
6074 collecting the patches spread around on the internet into on place.
6075 I&#39;ve added the relevant Debian patches to the freshly created git
6076 repository, and expect the Gentoo patches to make it too. If you got
6077 a DVD collection and care about command line tools, check out
6078 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
6079 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
6080 list&lt;/a&gt;. :)&lt;/p&gt;
6081 </description>
6082 </item>
6083
6084 <item>
6085 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
6086 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
6087 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
6088 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
6089 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
6090 a lot quicker. When we install more than 2000 packages in
6091 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
6092 tasksel in the installer, unpacking the binary packages take forever.
6093 A part of the slow I/O issue was discussed in
6094 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
6095 much file system sync-ing done by dpkg, which is the package
6096 responsible for unpacking the binary packages. Other parts (like code
6097 executed by postinst scripts) might also sync to disk during
6098 installation. All this sync-ing to disk do not really make sense to
6099 me. If the machine crash half-way through, I start over, I do not try
6100 to salvage the half installed system. So the failure sync-ing is
6101 supposed to protect against, hardware or system crash, is not really
6102 relevant while the installer is running.&lt;/p&gt;
6103
6104 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
6105 system sync()-ing in a fairly non-intrusive way, without the need to
6106 change the code in several packages. The idea is not new, but I have
6107 not heard anyone propose the approach using dpkg-divert before. It
6108 depend on the small and clever package
6109 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
6110 uses LD_PRELOAD to replace the system functions for syncing data to
6111 disk with functions doing nothing, thus allowing programs to live
6112 dangerous while speeding up disk I/O significantly. Instead of
6113 modifying the implementation of dpkg, apt and tasksel (which are the
6114 packages responsible for selecting, fetching and installing packages),
6115 it occurred to me that we could just divert the programs away, replace
6116 them with a simple shell wrapper calling
6117 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
6118 Two days ago I decided to test the idea, and wrapped up a simple
6119 implementation for the Debian Edu udeb.&lt;/p&gt;
6120
6121 &lt;p&gt;The effect was stunning. In my first test it reduced the running
6122 time of the pkgsel step (installing tasks) from 64 to less than 44
6123 minutes (20 minutes shaved off the installation) on an old Dell
6124 Latitude D505 machine. I am not quite sure what the optimised time
6125 would have been, as I messed up the testing a bit, causing the debconf
6126 priority to get low enough for two questions to pop up during
6127 installation. As soon as I saw the questions I moved the installation
6128 along, but do not know how long the question were holding up the
6129 installation. I did some more measurements using Debian Edu Jessie,
6130 and got these results. The time measured is the time stamp in
6131 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
6132 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
6133 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6134 timing thus do not depend on how quickly the user handle the tasksel
6135 dialog.&lt;/p&gt;
6136
6137 &lt;p&gt;&lt;table&gt;
6138
6139 &lt;tr&gt;
6140 &lt;th&gt;Machine/setup&lt;/th&gt;
6141 &lt;th&gt;Original tasksel&lt;/th&gt;
6142 &lt;th&gt;Optimised tasksel&lt;/th&gt;
6143 &lt;th&gt;Reduction&lt;/th&gt;
6144 &lt;/tr&gt;
6145
6146 &lt;tr&gt;
6147 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
6148 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
6149 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
6150 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
6151 &lt;/tr&gt;
6152
6153 &lt;tr&gt;
6154 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
6155 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
6156 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
6157 &lt;td&gt;23 min 40%&lt;/td&gt;
6158 &lt;/tr&gt;
6159
6160 &lt;tr&gt;
6161 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
6162 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
6163 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
6164 &lt;td&gt;11 min 50%&lt;/td&gt;
6165 &lt;/tr&gt;
6166
6167 &lt;tr&gt;
6168 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
6169 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
6170 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
6171 &lt;td&gt;2 min 33%&lt;/td&gt;
6172 &lt;/tr&gt;
6173
6174 &lt;tr&gt;
6175 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
6176 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
6177 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
6178 &lt;td&gt;4 min 21%&lt;/td&gt;
6179 &lt;/tr&gt;
6180
6181 &lt;/table&gt;&lt;/p&gt;
6182
6183 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
6184 time is spent downloading packages. The connection to the Internet
6185 was 100Mbit/s during testing, so downloading should not be a
6186 significant factor in the measurement. Download typically took a few
6187 seconds to a few minutes, depending on the amount of packages being
6188 installed.&lt;/p&gt;
6189
6190 &lt;p&gt;The speedup is implemented by using two hooks in
6191 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
6192 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
6193 finish-install.d hook to remove the divert at the end of the
6194 installation. I picked the pre-pkgsel.d hook instead of the
6195 post-base-installer.d hook because I test using an ISO without the
6196 eatmydata package included, and the post-base-installer.d hook in
6197 Debian Edu can only operate on packages included in the ISO. The
6198 negative effect of this is that I am unable to activate this
6199 optimization for the kernel installation step in d-i. If the code is
6200 moved to the post-base-installer.d hook, the speedup would be larger
6201 for the entire installation.&lt;/p&gt;
6202
6203 &lt;p&gt;I&#39;ve implemented this in the
6204 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
6205 git repository, and plan to provide the optimization as part of the
6206 Debian Edu installation. If you want to test this yourself, you can
6207 create two files in the installer (or in an udeb). One shell script
6208 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
6209
6210 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6211 #!/bin/sh
6212 set -e
6213 . /usr/share/debconf/confmodule
6214 info() {
6215 logger -t my-pkgsel &quot;info: $*&quot;
6216 }
6217 error() {
6218 logger -t my-pkgsel &quot;error: $*&quot;
6219 }
6220 override_install() {
6221 apt-install eatmydata || true
6222 if [ -x /target/usr/bin/eatmydata ] ; then
6223 for bin in dpkg apt-get aptitude tasksel ; do
6224 file=/usr/bin/$bin
6225 # Test that the file exist and have not been diverted already.
6226 if [ -f /target$file ] ; then
6227 info &quot;diverting $file using eatmydata&quot;
6228 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
6229 &gt; /target$file.edu
6230 chmod 755 /target$file.edu
6231 in-target dpkg-divert --package debian-edu-config \
6232 --rename --quiet --add $file
6233 ln -sf ./$bin.edu /target$file
6234 else
6235 error &quot;unable to divert $file, as it is missing.&quot;
6236 fi
6237 done
6238 else
6239 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
6240 fi
6241 }
6242
6243 override_install
6244 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6245
6246 &lt;p&gt;To clean up, another shell script should go into
6247 /usr/lib/finish-install.d/ with code like this:
6248
6249 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6250 #! /bin/sh -e
6251 . /usr/share/debconf/confmodule
6252 error() {
6253 logger -t my-finish-install &quot;error: $@&quot;
6254 }
6255 remove_install_override() {
6256 for bin in dpkg apt-get aptitude tasksel ; do
6257 file=/usr/bin/$bin
6258 if [ -x /target$file.edu ] ; then
6259 rm /target$file
6260 in-target dpkg-divert --package debian-edu-config \
6261 --rename --quiet --remove $file
6262 rm /target$file.edu
6263 else
6264 error &quot;Missing divert for $file.&quot;
6265 fi
6266 done
6267 sync # Flush file buffers before continuing
6268 }
6269
6270 remove_install_override
6271 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6272
6273 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
6274 edu-eatmydata-install and call it from the pre-pkgsel.d and
6275 finish-install.d scripts.&lt;/p&gt;
6276
6277 &lt;p&gt;By now you might ask if this change should get into the normal
6278 Debian installer too? I suspect it should, but am not sure the
6279 current debian-installer coordinators find it useful enough. It also
6280 depend on the side effects of the change. I&#39;m not aware of any, but I
6281 guess we will see if the change is safe after some more testing.
6282 Perhaps there is some package in Debian depending on sync() and
6283 fsync() having effect? Perhaps it should go into its own udeb, to
6284 allow those of us wanting to enable it to do so without affecting
6285 everyone.&lt;/p&gt;
6286
6287 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
6288 will break installation of all programs using gnutls because of
6289 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
6290 eatmydata package in Debian will solve it.&lt;/p&gt;
6291
6292 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
6293 the optimization work again. And I have discovered that the
6294 dpkg-divert trick is not really needed and implemented a slightly
6295 simpler approach as part of the debian-edu-install package. See
6296 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
6297
6298 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
6299 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
6300 triggering on i386 made it into testing, and broke this installation
6301 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
6302 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
6303 </description>
6304 </item>
6305
6306 <item>
6307 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
6308 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
6309 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
6310 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
6311 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
6312 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
6313 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
6314 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
6315 learn that there is a large set of publicly available key servers to
6316 use when looking for peoples public key. So far I have used
6317 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6318 were misbehaving, but those days are ended. The servers I have used
6319 up until yesterday have been slow and some times unavailable. I hope
6320 those problems are gone now.&lt;/p&gt;
6321
6322 &lt;p&gt;Behind the round robin DNS entry of the
6323 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
6324 there is a pool of more than 100 keyservers which are checked every
6325 day to ensure they are well connected and up to date. It must be
6326 better than what I have used so far. :)&lt;/p&gt;
6327
6328 &lt;p&gt;Yesterdays speaker told me that the service is the default
6329 keyserver provided by the default configuration in GnuPG, but this do
6330 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
6331
6332 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
6333 line:&lt;/p&gt;
6334
6335 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6336 keyserver pool.sks-keyservers.net
6337 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6338
6339 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
6340 entries in DNS. Just for fun, I did just that at work, so now every
6341 user of GnuPG at the University of Oslo should find a OpenGPG
6342 keyserver automatically should their need it:&lt;/p&gt;
6343
6344 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6345 % host -t srv _pgpkey-http._tcp.uio.no
6346 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
6347 %
6348 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6349
6350 &lt;p&gt;Now if only
6351 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
6352 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
6353 very happy. It can look up a given key or search for a user ID, but I
6354 normally do not want that, but to find a trust path from my key to
6355 another key. Given a user ID or key ID, I would like to find (and
6356 download) the keys representing a signature path from my key to the
6357 key in question, to be able to get a trust path between the two keys.
6358 This is as far as I can tell not possible today. Perhaps something
6359 for a future version of the protocol?&lt;/p&gt;
6360 </description>
6361 </item>
6362
6363 <item>
6364 <title>From English wiki to translated PDF and epub via Docbook</title>
6365 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
6366 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
6367 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
6368 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6369 project&lt;/a&gt; provide an instruction manual for teachers, system
6370 administrators and other users that contain useful tips for setting up
6371 and maintaining a Debian Edu installation. This text is about how the
6372 text processing of this manual is handled in the project.&lt;/p&gt;
6373
6374 &lt;p&gt;One goal of the project is to provide information in the native
6375 language of its users, and for this we need to handle translations.
6376 But we also want to make sure each language contain the same
6377 information, so for this we need a good way to keep the translations
6378 in sync. And we want it to be easy for our users to improve the
6379 documentation, avoiding the need to learn special formats or tools to
6380 contribute, and the obvious way to do this is to make it possible to
6381 edit the documentation using a web browser. We also want it to be
6382 easy for translators to keep the translation up to date, and give them
6383 help in figuring out what need to be translated. Here is the list of
6384 tools and the process we have found trying to reach all these
6385 goals.&lt;/p&gt;
6386
6387 &lt;p&gt;We maintain the authoritative source of our manual in the
6388 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
6389 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
6390 front page with references to the different chapters, several pages
6391 for each chapter, and finally one &quot;collection page&quot; gluing all the
6392 chapters together into one large web page (aka
6393 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
6394 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
6395 processing and translations. Thanks to the fact that the
6396 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
6397 wiki.debian.org support exporting pages in
6398 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
6399 the list of pages to export using the raw version of the AllInOne
6400 page, loop over each of them to generate a Docbook XML version of the
6401 manual. This process also download images and transform image
6402 references to use the locally downloaded images. The generated
6403 Docbook XML files are slightly broken, so some post-processing is done
6404 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
6405 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6406 a handfull of images. The XML file can now be used to generate PDF, HTML
6407 and epub versions of the English manual. This is the basic step of
6408 our process, making PDF (using dblatex), HTML (using xsltproc) and
6409 epub (using dbtoepub) version from Docbook XML, and the resulting files
6410 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
6411
6412 &lt;p&gt;But English documentation is not enough for us. We want translated
6413 documentation too, and we want to make it easy for translators to
6414 track the English original. For this we use the
6415 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
6416 which allow us to transform the English Docbook XML file into a
6417 translation file (a .pot file), usable with the normal gettext based
6418 translation tools used by those translating free software. The pot
6419 file is used to create and maintain translation files (several .po
6420 files), which the translations update with the native language
6421 translations of all titles, paragraphs and blocks of text in the
6422 original. The next step is combining the original English Docbook XML
6423 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6424 create a translated Docbook XML file (in this case
6425 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6426 translated, if the translation is not complete) Docbook XML file can
6427 then be used like the original to create a PDF, HTML and epub version
6428 of the documentation.&lt;/p&gt;
6429
6430 &lt;p&gt;The translators use different tools to edit the .po files. We
6431 recommend using
6432 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
6433 while some use emacs and vi, others can use web based editors like
6434 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
6435 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
6436 is where the .po file end up, in our git repository. Updated
6437 translations can either be committed directly to git, or submitted as
6438 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
6439 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
6440
6441 &lt;p&gt;One challenge is images, which both might need to be translated (if
6442 they show translated user applications), and are needed in different
6443 formats when creating PDF and HTML versions (epub is a HTML version in
6444 this regard). For this we transform the original PNG images to the
6445 needed density and format during build, and have a way to provide
6446 translated images by storing translated versions in
6447 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6448 package maintainers know more.&lt;/p&gt;
6449
6450 &lt;p&gt;If you wonder what the result look like, we provide
6451 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
6452 of the documentation packages on the web&lt;/a&gt;. See for example the
6453 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
6454 PDF version&lt;/a&gt; or the
6455 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
6456 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
6457 but perhaps it will be done in the future.&lt;/p&gt;
6458
6459 &lt;p&gt;To learn more, check out
6460 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
6461 debian-edu-doc package&lt;/a&gt;,
6462 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
6463 manual on the wiki&lt;/a&gt; and
6464 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
6465 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
6466 </description>
6467 </item>
6468
6469 <item>
6470 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
6471 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
6472 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
6473 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
6474 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
6475 related packages relevant for the computer installed automatically.
6476 So I implemented one, using
6477 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
6478 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
6479 run tasksel as user root. You should be presented with a new option,
6480 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
6481 select it, tasksel will install the packages isenkram claim is fit for
6482 the current hardware, hot pluggable or not.&lt;p&gt;
6483
6484 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
6485 description, and the other is the script used to extract the list of
6486 packages to install. The first part is in
6487 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
6488 this:&lt;/p&gt;
6489
6490 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6491 Task: isenkram
6492 Section: hardware
6493 Description: Hardware specific packages (autodetected by isenkram)
6494 Based on the detected hardware various hardware specific packages are
6495 proposed.
6496 Test-new-install: mark show
6497 Relevance: 8
6498 Packages: for-current-hardware
6499 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6500
6501 &lt;p&gt;The second part is in
6502 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
6503 this:&lt;/p&gt;
6504
6505 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6506 #!/bin/sh
6507 #
6508 (
6509 isenkram-lookup
6510 isenkram-autoinstall-firmware -l
6511 ) | sort -u
6512 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6513
6514 &lt;p&gt;All in all, a very short and simple implementation making it
6515 trivial to install the hardware dependent package we all may want to
6516 have installed on our machines. I&#39;ve not been able to find a way to
6517 get tasksel to tell you exactly which packages it plan to install
6518 before doing the installation. So if you are curious or careful,
6519 check the output from the isenkram-* command line tools first.&lt;/p&gt;
6520
6521 &lt;p&gt;The information about which packages are handling which hardware is
6522 fetched either from the isenkram package itself in
6523 /usr/share/isenkram/, from git.debian.org or from the APT package
6524 database (using the Modaliases header). The APT package database
6525 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6526 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
6527 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
6528 the python-apt code (bug
6529 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
6530 workaround I was able to get rid of the file descriptor leak and
6531 reduce the memory leak from ~30 MiB per hardware detection down to
6532 around 2 MiB per hardware detection. It should make the desktop
6533 daemon a lot more useful. The fix is in version 0.7 uploaded to
6534 unstable today.&lt;/p&gt;
6535
6536 &lt;p&gt;I believe the current way of mapping hardware to packages in
6537 Isenkram is is a good draft, but in the future I expect isenkram to
6538 use the AppStream data source for this. A proposal for getting proper
6539 AppStream support into Debian is floating around as
6540 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
6541 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
6542 project&lt;/a&gt; will take place this summer to improve the situation. I
6543 look forward to seeing the result, and welcome patches for isenkram to
6544 start using the information when it is ready.&lt;/p&gt;
6545
6546 &lt;p&gt;If you want your package to map to some specific hardware, either
6547 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
6548 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
6549 package&lt;/a&gt; or submit a bug report with the details to the isenkram
6550 package. See also
6551 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
6552 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
6553 the information will be migrated to AppStream eventually, but for the
6554 moment I got no better place to store it.&lt;/p&gt;
6555 </description>
6556 </item>
6557
6558 <item>
6559 <title>FreedomBox milestone - all packages now in Debian Sid</title>
6560 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
6561 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
6562 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
6563 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6564 project&lt;/a&gt; is working on providing the software and hardware to make
6565 it easy for non-technical people to host their data and communication
6566 at home, and being able to communicate with their friends and family
6567 encrypted and away from prying eyes. It is still going strong, and
6568 today a major mile stone was reached.&lt;/p&gt;
6569
6570 &lt;p&gt;Today, the last of the packages currently used by the project to
6571 created the system images were accepted into Debian Unstable. It was
6572 the freedombox-setup package, which is used to configure the images
6573 during build and on the first boot. Now all one need to get going is
6574 the build code from the freedom-maker git repository and packages from
6575 Debian. And once the freedombox-setup package enter testing, we can
6576 build everything directly from Debian. :)&lt;/p&gt;
6577
6578 &lt;p&gt;Some key packages used by Freedombox are
6579 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
6580 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
6581 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
6582 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
6583 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
6584 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
6585 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
6586 are plans to integrate more packages into the setup. User
6587 documentation is maintained on the Debian wiki. Please
6588 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
6589 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
6590
6591 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
6592 setup, run this on a Debian machine using a user with sudo rights to
6593 become root:&lt;/p&gt;
6594
6595 &lt;p&gt;&lt;pre&gt;
6596 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6597 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6598 u-boot-tools
6599 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6600 freedom-maker
6601 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6602 &lt;/pre&gt;&lt;/p&gt;
6603
6604 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6605 devices. See the README in the freedom-maker git repo for more
6606 details on the build. If you do not want all three images, trim the
6607 make line. Note that the virtualbox-image target is not really
6608 virtualbox specific. It create a x86 image usable in kvm, qemu,
6609 vmware and any other x86 virtual machine environment. You might need
6610 the version of vmdebootstrap in Jessie to get the build working, as it
6611 include fixes for a race condition with kpartx.&lt;/p&gt;
6612
6613 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6614 method, boot a Debian Wheezy ISO and use this boot argument to load
6615 the preseed values:&lt;/p&gt;
6616
6617 &lt;p&gt;&lt;pre&gt;
6618 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;
6619 &lt;/pre&gt;&lt;/p&gt;
6620
6621 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
6622 it still work.&lt;/p&gt;
6623
6624 &lt;p&gt;If you wonder how to help, one task you could look at is using
6625 systemd as the boot system. It will become the default for Linux in
6626 Jessie, so we need to make sure it is usable on the Freedombox. I did
6627 a simple test a few weeks ago, and noticed dnsmasq failed to start
6628 during boot when using systemd. I suspect there are other problems
6629 too. :) To detect problems, there is a test suite included, which can
6630 be run from the plinth web interface.&lt;/p&gt;
6631
6632 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6633 us get the new release published. :) Please join us on
6634 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6635 irc.debian.org)&lt;/a&gt; and
6636 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6637 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6638 </description>
6639 </item>
6640
6641 <item>
6642 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6643 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6644 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6645 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6646 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6647 solution for use at home. My requirements are simple, it must be
6648 cheap and locally encrypted (in other words, I keep the encryption
6649 keys, the storage provider do not have access to my private files).
6650 One idea me and my friends had many years ago, before the cloud
6651 storage providers showed up, was to use Google mail as storage,
6652 writing a Linux block device storing blocks as emails in the mail
6653 service provided by Google, and thus get heaps of free space. On top
6654 of this one can add encryption, RAID and volume management to have
6655 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6656 I never found time to implement such system. But the last few weeks I
6657 have looked at a system called
6658 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6659 mounted network backed file system with the features I need.&lt;/p&gt;
6660
6661 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6662 handling several different storage providers, any with Amazon S3,
6663 Google Drive or OpenStack API. There are heaps of such storage
6664 providers. S3QL can also use a local directory as storage, which
6665 combined with sshfs allow for file storage on any ssh server. S3QL
6666 include support for encryption, compression, de-duplication, snapshots
6667 and immutable file systems, allowing me to mount the remote storage as
6668 a local mount point, look at and use the files as if they were local,
6669 while the content is stored in the cloud as well. This allow me to
6670 have a backup that should survive fire. The file system can not be
6671 shared between several machines at the same time, as only one can
6672 mount it at the time, but any machine with the encryption key and
6673 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6674
6675 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6676 package is included already. So to get started, run &lt;tt&gt;apt-get
6677 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6678 Greenqloud, after reading their nice recipe on
6679 &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
6680 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6681 in Iceland more than those in USA when it come to keeping my personal
6682 data safe and private, and thus would rather spend money on a company
6683 in Iceland. Another nice recipe is available from the article
6684 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6685 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6686 Admin magazine. When the provider is picked, figure out how to get
6687 the API key needed to connect to the storage API. With Greencloud,
6688 the key did not show up until I had added payment details to my
6689 account.&lt;/p&gt;
6690
6691 &lt;p&gt;Armed with the API access details, it is time to create the file
6692 system. First, create a new bucket in the cloud. This bucket is the
6693 file system storage area. I picked a bucket name reflecting the
6694 machine that was going to store data there, but any name will do.
6695 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6696 the API login and password, and a locally created password. Store it
6697 all in ~root/.s3ql/authinfo2 like this:
6698
6699 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6700 [s3c]
6701 storage-url: s3c://s.greenqloud.com:443/bucket-name
6702 backend-login: API-login
6703 backend-password: API-password
6704 fs-passphrase: local-password
6705 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6706
6707 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6708 but any sensible way to create a fairly random password should do it.
6709 Armed with these details, it is now time to run mkfs, entering the API
6710 details and password to create it:&lt;/p&gt;
6711
6712 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6713 # mkdir -m 700 /var/lib/s3ql-cache
6714 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6715 --ssl s3c://s.greenqloud.com:443/bucket-name
6716 Enter backend login:
6717 Enter backend password:
6718 Before using S3QL, make sure to read the user&#39;s guide, especially
6719 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6720 Enter encryption password:
6721 Confirm encryption password:
6722 Generating random encryption key...
6723 Creating metadata tables...
6724 Dumping metadata...
6725 ..objects..
6726 ..blocks..
6727 ..inodes..
6728 ..inode_blocks..
6729 ..symlink_targets..
6730 ..names..
6731 ..contents..
6732 ..ext_attributes..
6733 Compressing and uploading metadata...
6734 Wrote 0.00 MB of compressed metadata.
6735 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6736
6737 &lt;p&gt;The next step is mounting the file system to make the storage available.
6738
6739 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6740 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6741 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6742 Using 4 upload threads.
6743 Downloading and decompressing metadata...
6744 Reading metadata...
6745 ..objects..
6746 ..blocks..
6747 ..inodes..
6748 ..inode_blocks..
6749 ..symlink_targets..
6750 ..names..
6751 ..contents..
6752 ..ext_attributes..
6753 Mounting filesystem...
6754 # df -h /s3ql
6755 Filesystem Size Used Avail Use% Mounted on
6756 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
6757 #
6758 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6759
6760 &lt;p&gt;The file system is now ready for use. I use rsync to store my
6761 backups in it, and as the metadata used by rsync is downloaded at
6762 mount time, no network traffic (and storage cost) is triggered by
6763 running rsync. To unmount, one should not use the normal umount
6764 command, as this will not flush the cache to the cloud storage, but
6765 instead running the umount.s3ql command like this:
6766
6767 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6768 # umount.s3ql /s3ql
6769 #
6770 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6771
6772 &lt;p&gt;There is a fsck command available to check the file system and
6773 correct any problems detected. This can be used if the local server
6774 crashes while the file system is mounted, to reset the &quot;already
6775 mounted&quot; flag. This is what it look like when processing a working
6776 file system:&lt;/p&gt;
6777
6778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6779 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
6780 Using cached metadata.
6781 File system seems clean, checking anyway.
6782 Checking DB integrity...
6783 Creating temporary extra indices...
6784 Checking lost+found...
6785 Checking cached objects...
6786 Checking names (refcounts)...
6787 Checking contents (names)...
6788 Checking contents (inodes)...
6789 Checking contents (parent inodes)...
6790 Checking objects (reference counts)...
6791 Checking objects (backend)...
6792 ..processed 5000 objects so far..
6793 ..processed 10000 objects so far..
6794 ..processed 15000 objects so far..
6795 Checking objects (sizes)...
6796 Checking blocks (referenced objects)...
6797 Checking blocks (refcounts)...
6798 Checking inode-block mapping (blocks)...
6799 Checking inode-block mapping (inodes)...
6800 Checking inodes (refcounts)...
6801 Checking inodes (sizes)...
6802 Checking extended attributes (names)...
6803 Checking extended attributes (inodes)...
6804 Checking symlinks (inodes)...
6805 Checking directory reachability...
6806 Checking unix conventions...
6807 Checking referential integrity...
6808 Dropping temporary indices...
6809 Backing up old metadata...
6810 Dumping metadata...
6811 ..objects..
6812 ..blocks..
6813 ..inodes..
6814 ..inode_blocks..
6815 ..symlink_targets..
6816 ..names..
6817 ..contents..
6818 ..ext_attributes..
6819 Compressing and uploading metadata...
6820 Wrote 0.89 MB of compressed metadata.
6821 #
6822 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6823
6824 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
6825 quick, about the same speed as local file access. Uploading large
6826 amount of data is to me limited by the bandwidth out of and into my
6827 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
6828 which is very close to my upload speed, and downloading the same
6829 Debian installation ISO gave me 610 kiB/s, close to my download speed.
6830 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
6831 network, not the file system code. I do not know what a good cache
6832 size would be, but suspect that the cache should e larger than your
6833 working set.&lt;/p&gt;
6834
6835 &lt;p&gt;I mentioned that only one machine can mount the file system at the
6836 time. If another machine try, it is told that the file system is
6837 busy:&lt;/p&gt;
6838
6839 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6840 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6841 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6842 Using 8 upload threads.
6843 Backend reports that fs is still mounted elsewhere, aborting.
6844 #
6845 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6846
6847 &lt;p&gt;The file content is uploaded when the cache is full, while the
6848 metadata is uploaded once every 24 hour by default. To ensure the
6849 file system content is flushed to the cloud, one can either umount the
6850 file system, or ask S3QL to flush the cache and metadata using
6851 s3qlctrl:
6852
6853 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6854 # s3qlctrl upload-meta /s3ql
6855 # s3qlctrl flushcache /s3ql
6856 #
6857 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6858
6859 &lt;p&gt;If you are curious about how much space your data uses in the
6860 cloud, and how much compression and deduplication cut down on the
6861 storage usage, you can use s3qlstat on the mounted file system to get
6862 a report:&lt;/p&gt;
6863
6864 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6865 # s3qlstat /s3ql
6866 Directory entries: 9141
6867 Inodes: 9143
6868 Data blocks: 8851
6869 Total data size: 22049.38 MB
6870 After de-duplication: 21955.46 MB (99.57% of total)
6871 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
6872 Database size: 2.39 MB (uncompressed)
6873 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6874 #
6875 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6876
6877 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
6878 storage. I did not try to locate them all, but am aware of at least
6879 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
6880 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
6881 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
6882 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
6883 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
6884 accept payment in Bitcoin. Pick one that suit your need. Some of
6885 them provide several GiB of free storage, but the prize models are
6886 quite different and you will have to figure out what suits you
6887 best.&lt;/p&gt;
6888
6889 &lt;p&gt;While researching this blog post, I had a look at research papers
6890 and posters discussing the S3QL file system. There are several, which
6891 told me that the file system is getting a critical check by the
6892 science community and increased my confidence in using it. One nice
6893 poster is titled
6894 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
6895 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6896 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
6897 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6898 and Pamela Smith. Please have a look.&lt;/p&gt;
6899
6900 &lt;p&gt;Given my problems with different file systems earlier, I decided to
6901 check out the mounted S3QL file system to see if it would be usable as
6902 a home directory (in other word, that it provided POSIX semantics when
6903 it come to locking and umask handling etc). Running
6904 &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
6905 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
6906 no error was found. So the file system can be used for home
6907 directories, if one chooses to do so.&lt;/p&gt;
6908
6909 &lt;p&gt;If you do not want a locally file system, and want something that
6910 work without the Linux fuse file system, I would like to mention the
6911 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
6912 provide locally encrypted backup using a command line client. It have
6913 a nicer access control system, where one can split out read and write
6914 access, allowing some systems to write to the backup and others to
6915 only read from it.&lt;/p&gt;
6916
6917 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6918 activities, please send Bitcoin donations to my address
6919 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6920 </description>
6921 </item>
6922
6923 <item>
6924 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
6925 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
6926 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
6927 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
6928 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6929 project&lt;/a&gt; is working on providing the software and hardware for
6930 making it easy for non-technical people to host their data and
6931 communication at home, and being able to communicate with their
6932 friends and family encrypted and away from prying eyes. It has been
6933 going on for a while, and is slowly progressing towards a new test
6934 release (0.2).&lt;/p&gt;
6935
6936 &lt;p&gt;And what day could be better than the Pi day to announce that the
6937 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
6938 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6939 system), and can also be installed using a Debian installer preseed
6940 file. The Debian based Freedombox is now based on Debian Jessie,
6941 where most of the needed packages used are already present. Only one,
6942 the freedombox-setup package, is missing. To try to build your own
6943 boot image to test the current status, fetch the freedom-maker scripts
6944 and build using
6945 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
6946 with a user with sudo access to become root:
6947
6948 &lt;pre&gt;
6949 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6950 freedom-maker
6951 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6952 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6953 u-boot-tools
6954 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6955 &lt;/pre&gt;
6956
6957 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6958 devices. See the README for more details on the build. If you do not
6959 want all three images, trim the make line. But note that thanks to &lt;a
6960 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
6961 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
6962 kpartx call.&lt;/p&gt;
6963
6964 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6965 method, boot a Debian Wheezy ISO and use this boot argument to load
6966 the preseed values:&lt;/p&gt;
6967
6968 &lt;pre&gt;
6969 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;
6970 &lt;/pre&gt;
6971
6972 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
6973 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
6974 currently hang while setting up APT sources. Killing the
6975 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
6976 installation will get the installation going. This affect all
6977 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
6978
6979 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6980 us get the new release published. :) Please join us on
6981 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6982 irc.debian.org)&lt;/a&gt; and
6983 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6984 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6985 </description>
6986 </item>
6987
6988 <item>
6989 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
6990 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
6991 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
6992 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
6993 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
6994 innetgr tools, because I needed them in
6995 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
6996 ng-utils, and it has served me well. I placed the project under the
6997 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
6998 repository. But many years ago, the CVS repository was dropped (lost,
6999 not migrated to new hardware, not sure), and the project have lacked a
7000 proper home since then.&lt;/p&gt;
7001
7002 &lt;p&gt;Last summer, I had a look at the package and made a new release
7003 fixing a irritating crash bug, but was unable to store the changes in
7004 a proper source control system. I applied for a project on
7005 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
7006 to follow up on it. Until today. :)&lt;/p&gt;
7007
7008 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
7009 now have a new home, and a git repository with the highlight of the
7010 history of the project. I published all release tarballs and imported
7011 them into the git repository. As the project is really stable and not
7012 expected to gain new features any time soon, I decided to make a new
7013 release and call it 1.0. Visit the new project home on
7014 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
7015 if you want to check it out. The new version is also uploaded into
7016 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
7017 </description>
7018 </item>
7019
7020 <item>
7021 <title>Testing sysvinit from experimental in Debian Hurd</title>
7022 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
7023 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
7024 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
7025 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
7026 their changes into sysvinit, to allow them to use the normal sysvinit
7027 boot system instead of their old one. This follow up on the
7028 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
7029 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
7030 get Debian on Hurd working more like Debian on Linux. To get started,
7031 I downloaded a prebuilt hard disk image from
7032 &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;,
7033 and started it using virt-manager.&lt;/p&gt;
7034
7035 &lt;p&gt;The first think I had to do after logging in (root without any
7036 password) was to get the network operational. I followed
7037 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
7038 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
7039 commands as root to get the machine to accept a IP address from the
7040 kvm internal DHCP server:&lt;/p&gt;
7041
7042 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7043 settrans -fgap /dev/netdde /hurd/netdde
7044 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
7045 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
7046 dhclient /dev/eth0
7047 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7048
7049 &lt;p&gt;After this, the machine had internet connectivity, and I could
7050 upgrade it and install the sysvinit packages from experimental and
7051 enable it as the default boot system in Hurd.&lt;/p&gt;
7052
7053 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
7054 running on the machine it for ssh login to work a password need to be
7055 set. Also, note that a bug somewhere in openssh on Hurd block
7056 compression from working. Remember to turn that off on the client
7057 side.&lt;/p&gt;
7058
7059 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
7060 stuff:&lt;/p&gt;
7061
7062 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7063 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
7064 deb http://http.debian.net/debian/ experimental main
7065 EOF
7066 apt-get update
7067 apt-get dist-upgrade
7068 apt-get install -t experimental initscripts sysv-rc sysvinit \
7069 sysvinit-core sysvinit-utils
7070 update-alternatives --config runsystem
7071 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7072
7073 &lt;p&gt;To reboot after switching boot system, you have to use
7074 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
7075 yet a sysvinit process able to receive the signals from the normal
7076 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
7077 upgrading every package and rebooting, the network come up with DHCP
7078 after boot as it should, and the settrans/pkill hack mentioned at the
7079 start is no longer needed. But for some strange reason, there are no
7080 longer any login prompt in the virtual console, so I logged in using
7081 ssh instead.
7082
7083 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
7084 fail some times. No idea what the cause is, but hope the Hurd porters
7085 figure it out. At least Justus said on IRC (#debian-hurd on
7086 irc.debian.org) that they are aware of the problem. A way to reduce
7087 the impact is to upgrade to the Hurd packages built by Justus by
7088 adding this repository to the machine:&lt;/p&gt;
7089
7090 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7091 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
7092 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7093 EOF
7094 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7095
7096 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
7097 http://ftp.debian-ports.org/debian, because some of the packages in
7098 unstable do not yet include the required patches that are lingering in
7099 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
7100
7101 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7102 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
7103 i emacs - GNU Emacs editor (metapackage)
7104 i gdb - GNU Debugger
7105 i hurd-recommended - Miscellaneous translators
7106 i isc-dhcp-client - ISC DHCP client
7107 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7108 i libc-bin - Embedded GNU C Library: Binaries
7109 i libc-dev-bin - Embedded GNU C Library: Development binaries
7110 i libc0.3 - Embedded GNU C Library: Shared libraries
7111 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7112 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7113 i multiarch-support - Transitional package to ensure multiarch compatibilit
7114 i A x11-common - X Window System (X.Org) infrastructure
7115 i xorg - X.Org X Window System
7116 i A xserver-xorg - X.Org X server
7117 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7118 #
7119 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7120
7121 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
7122 X.org did not work out of the box and I never took the time to follow
7123 the porters instructions to fix it. This time I was interested in the
7124 command line stuff.&lt;p&gt;
7125 </description>
7126 </item>
7127
7128 <item>
7129 <title>New chrpath release 0.16</title>
7130 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
7131 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
7132 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
7133 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
7134 find problems in C, C++ and Java code using static source code
7135 analysis. It can detect a lot of different problems, and is very
7136 useful to find memory and locking bugs in the error handling part of
7137 the source. The company behind it provide
7138 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
7139 a community service&lt;/a&gt;, and many hundred free software projects are
7140 already checked. A few days ago I decided to have a closer look at
7141 the Coverity system, and discovered that the
7142 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
7143 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
7144 projects I am involved with was already registered. But these are
7145 fairly big, and I would also like to have a small and easy project to
7146 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
7147 checking of the chrpath project&lt;/a&gt;. It was
7148 added to the checker and discovered seven potential defects. Six of
7149 these were real, mostly resource &quot;leak&quot; when the program detected an
7150 error. Nothing serious, as the resources would be released a fraction
7151 of a second later when the program exited because of the error, but it
7152 is nice to do it right in case the source of the program some time in
7153 the future end up in a library. Having fixed all defects and added
7154 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
7155 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
7156 publish a new release. These are the release notes:&lt;/p&gt;
7157
7158 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
7159
7160 &lt;ul&gt;
7161
7162 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
7163 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
7164 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
7165
7166 &lt;/ul&gt;
7167
7168 &lt;p&gt;You can
7169 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7170 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
7171 project if something is wrong with the new release. The test suite
7172 did not discover any old errors, so if you find a new one, please also
7173 include a test suite check.&lt;/p&gt;
7174 </description>
7175 </item>
7176
7177 <item>
7178 <title>New chrpath release 0.15</title>
7179 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
7180 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
7181 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
7182 <description>&lt;p&gt;After many years break from the package and a vain hope that
7183 development would be continued by someone else, I finally pulled my
7184 acts together this morning and wrapped up a new release of chrpath,
7185 the command line tool to modify the rpath and runpath of already
7186 compiled ELF programs. The update was triggered by the persistence of
7187 Isha Vishnoi at IBM, which needed a new config.guess file to get
7188 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
7189 is working on. I checked the
7190 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
7191 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
7192 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
7193 packages for interesting patches (failed to find the source from
7194 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7195 These are the release notes:&lt;/p&gt;
7196
7197 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
7198
7199 &lt;ul&gt;
7200
7201 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
7202 with newer architectures. Thanks to isha vishnoi for the heads
7203 up.&lt;/li&gt;
7204
7205 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
7206
7207 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7208 Matthias Klose.&lt;/li&gt;
7209
7210 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
7211 Petr Machata found in Fedora.&lt;/li&gt;
7212
7213 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
7214 .dynamic is a NULL terminated string. Based on patch found in
7215 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
7216
7217 &lt;/ul&gt;
7218
7219 &lt;p&gt;You can
7220 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7221 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
7222 project if something is wrong with the new release. The test suite
7223 did not discover any old errors, so if you find a new one, please also
7224 include a testsuite check.&lt;/p&gt;
7225 </description>
7226 </item>
7227
7228 <item>
7229 <title>Debian init.d boot script example for rsyslog</title>
7230 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
7231 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
7232 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
7233 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
7234 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
7235 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
7236 init.d scripts at all. Here is an example init.d script, ie a rewrite
7237 of /etc/init.d/rsyslog:&lt;/p&gt;
7238
7239 &lt;p&gt;&lt;pre&gt;
7240 #!/lib/init/init-d-script
7241 ### BEGIN INIT INFO
7242 # Provides: rsyslog
7243 # Required-Start: $remote_fs $time
7244 # Required-Stop: umountnfs $time
7245 # X-Stop-After: sendsigs
7246 # Default-Start: 2 3 4 5
7247 # Default-Stop: 0 1 6
7248 # Short-Description: enhanced syslogd
7249 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7250 # It is quite compatible to stock sysklogd and can be
7251 # used as a drop-in replacement.
7252 ### END INIT INFO
7253 DESC=&quot;enhanced syslogd&quot;
7254 DAEMON=/usr/sbin/rsyslogd
7255 &lt;/pre&gt;&lt;/p&gt;
7256
7257 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
7258 script was 137 lines, and the above is just 15 lines, most of it meta
7259 info/comments.&lt;/p&gt;
7260
7261 &lt;p&gt;How to do this, you ask? Well, one create a new script
7262 /lib/init/init-d-script looking something like this:
7263
7264 &lt;p&gt;&lt;pre&gt;
7265 #!/bin/sh
7266
7267 # Define LSB log_* functions.
7268 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
7269 # and status_of_proc is working.
7270 . /lib/lsb/init-functions
7271
7272 #
7273 # Function that starts the daemon/service
7274
7275 #
7276 do_start()
7277 {
7278 # Return
7279 # 0 if daemon has been started
7280 # 1 if daemon was already running
7281 # 2 if daemon could not be started
7282 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
7283 || return 1
7284 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7285 $DAEMON_ARGS \
7286 || return 2
7287 # Add code here, if necessary, that waits for the process to be ready
7288 # to handle requests from services started subsequently which depend
7289 # on this one. As a last resort, sleep for some time.
7290 }
7291
7292 #
7293 # Function that stops the daemon/service
7294 #
7295 do_stop()
7296 {
7297 # Return
7298 # 0 if daemon has been stopped
7299 # 1 if daemon was already stopped
7300 # 2 if daemon could not be stopped
7301 # other if a failure occurred
7302 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
7303 RETVAL=&quot;$?&quot;
7304 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
7305 # Wait for children to finish too if this is a daemon that forks
7306 # and if the daemon is only ever run from this initscript.
7307 # If the above conditions are not satisfied then add some other code
7308 # that waits for the process to drop all resources that could be
7309 # needed by services started subsequently. A last resort is to
7310 # sleep for some time.
7311 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
7312 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
7313 # Many daemons don&#39;t delete their pidfiles when they exit.
7314 rm -f $PIDFILE
7315 return &quot;$RETVAL&quot;
7316 }
7317
7318 #
7319 # Function that sends a SIGHUP to the daemon/service
7320 #
7321 do_reload() {
7322 #
7323 # If the daemon can reload its configuration without
7324 # restarting (for example, when it is sent a SIGHUP),
7325 # then implement that here.
7326 #
7327 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
7328 return 0
7329 }
7330
7331 SCRIPTNAME=$1
7332 scriptbasename=&quot;$(basename $1)&quot;
7333 echo &quot;SN: $scriptbasename&quot;
7334 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
7335 script=&quot;$1&quot;
7336 shift
7337 . $script
7338 else
7339 exit 0
7340 fi
7341
7342 NAME=$(basename $DAEMON)
7343 PIDFILE=/var/run/$NAME.pid
7344
7345 # Exit if the package is not installed
7346 #[ -x &quot;$DAEMON&quot; ] || exit 0
7347
7348 # Read configuration variable file if it is present
7349 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
7350
7351 # Load the VERBOSE setting and other rcS variables
7352 . /lib/init/vars.sh
7353
7354 case &quot;$1&quot; in
7355 start)
7356 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
7357 do_start
7358 case &quot;$?&quot; in
7359 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7360 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7361 esac
7362 ;;
7363 stop)
7364 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
7365 do_stop
7366 case &quot;$?&quot; in
7367 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7368 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7369 esac
7370 ;;
7371 status)
7372 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
7373 ;;
7374 #reload|force-reload)
7375 #
7376 # If do_reload() is not implemented then leave this commented out
7377 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
7378 #
7379 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
7380 #do_reload
7381 #log_end_msg $?
7382 #;;
7383 restart|force-reload)
7384 #
7385 # If the &quot;reload&quot; option is implemented then remove the
7386 # &#39;force-reload&#39; alias
7387 #
7388 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
7389 do_stop
7390 case &quot;$?&quot; in
7391 0|1)
7392 do_start
7393 case &quot;$?&quot; in
7394 0) log_end_msg 0 ;;
7395 1) log_end_msg 1 ;; # Old process is still running
7396 *) log_end_msg 1 ;; # Failed to start
7397 esac
7398 ;;
7399 *)
7400 # Failed to stop
7401 log_end_msg 1
7402 ;;
7403 esac
7404 ;;
7405 *)
7406 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
7407 exit 3
7408 ;;
7409 esac
7410
7411 :
7412 &lt;/pre&gt;&lt;/p&gt;
7413
7414 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
7415 lot. I did not really polish the approach, so it might not always
7416 work out of the box, but you get the idea. I did not try very hard to
7417 optimize it nor make it more robust either.&lt;/p&gt;
7418
7419 &lt;p&gt;A better argument for switching init system in Debian than reducing
7420 the size of init scripts (which is a good thing to do anyway), is to
7421 get boot system that is able to handle the kernel events sensibly and
7422 robustly, and do not depend on the boot to run sequentially. The boot
7423 and the kernel have not behaved sequentially in years.&lt;/p&gt;
7424 </description>
7425 </item>
7426
7427 <item>
7428 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
7429 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
7430 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
7431 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
7432 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
7433 remote display access is the preferred solution with oVirt and RedHat
7434 Enterprise Virtualization, and I was sad to discover the other day
7435 that the browser plugin needed to use these systems seamlessly was
7436 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
7437 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
7438 2013-04-01, so I decided to wrap up a package based on the great work
7439 from Cajus Pollmeier and put it in a collab-maint maintained git
7440 repository to get a package I could use. I would very much like
7441 others to help me maintain the package (or just take over, I do not
7442 mind), but as no-one had volunteered so far, I just uploaded it to
7443 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
7444
7445 &lt;p&gt;The source is now available from
7446 &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;
7447 </description>
7448 </item>
7449
7450 <item>
7451 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
7452 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
7453 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
7454 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
7455 <description>&lt;p&gt;The
7456 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
7457 program is a a very nice system to create virtual machine images. It
7458 create a image file, add a partition table, mount it and run
7459 debootstrap in the mounted directory to create a Debian system on a
7460 stick. Yesterday, I decided to try to teach it how to make images for
7461 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
7462 of a plan to simplify the build system for
7463 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
7464 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
7465 the virtualbox images, but its current build system made multistrap
7466 based system for Dreamplug images, and it is lacking support for
7467 Raspberry Pi.&lt;/p&gt;
7468
7469 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
7470 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7471 code and adjusted it to be able to build armel images on my amd64
7472 Debian laptop. I ended up giving vmdebootstrap five new options,
7473 allowing me to replicate the image creation process I use to make
7474 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
7475 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
7476 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
7477 call debootstrap with --foreign and to copy the handler into the
7478 generated chroot before running the second stage. This allow
7479 vmdebootstrap to create armel images on an amd64 host. Next I added
7480 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
7481 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
7482 given file system type, allowing me to create an image with a vfat
7483 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
7484 variant&lt;/tt&gt; option to allow me to create smaller images without the
7485 Debian base system packages installed. Finally, I added an option
7486 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
7487 as a boot loader. It is not needed on the Raspberry Pi and probably
7488 most other non-x86 architectures. The changes were accepted by the
7489 upstream author of vmdebootstrap yesterday and today, and is now
7490 available from
7491 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
7492 upstream project page&lt;/a&gt;.&lt;/p&gt;
7493
7494 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
7495 create a small script (the customize script) to add the non-free
7496 binary blob needed to boot the Raspberry Pi and the APT source
7497 list:&lt;/p&gt;
7498
7499 &lt;p&gt;&lt;pre&gt;
7500 #!/bin/sh
7501 set -e # Exit on first error
7502 rootdir=&quot;$1&quot;
7503 cd &quot;$rootdir&quot;
7504 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
7505 deb http://http.debian.net/debian/ jessie main contrib non-free
7506 EOF
7507 # Install non-free binary blob needed to boot Raspberry Pi. This
7508 # install a kernel somewhere too.
7509 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7510 -O $rootdir/usr/bin/rpi-update
7511 chmod a+x $rootdir/usr/bin/rpi-update
7512 mkdir -p $rootdir/lib/modules
7513 touch $rootdir/boot/start.elf
7514 chroot $rootdir rpi-update
7515 &lt;/pre&gt;&lt;/p&gt;
7516
7517 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
7518 to build the image:&lt;/p&gt;
7519
7520 &lt;pre&gt;
7521 sudo ./vmdebootstrap \
7522 --variant minbase \
7523 --arch armel \
7524 --distribution jessie \
7525 --mirror http://http.debian.net/debian \
7526 --image test.img \
7527 --size 600M \
7528 --bootsize 64M \
7529 --boottype vfat \
7530 --log-level debug \
7531 --verbose \
7532 --no-kernel \
7533 --no-extlinux \
7534 --root-password raspberry \
7535 --hostname raspberrypi \
7536 --foreign /usr/bin/qemu-arm-static \
7537 --customize `pwd`/customize \
7538 --package netbase \
7539 --package git-core \
7540 --package binutils \
7541 --package ca-certificates \
7542 --package wget \
7543 --package kmod
7544 &lt;/pre&gt;&lt;/p&gt;
7545
7546 &lt;p&gt;The list of packages being installed are the ones needed by
7547 rpi-update to make the image bootable on the Raspberry Pi, with the
7548 exception of netbase, which is needed by debootstrap to find
7549 /etc/hosts with the minbase variant. I really wish there was a way to
7550 set up an Raspberry Pi using only packages in the Debian archive, but
7551 that is not possible as far as I know, because it boots from the GPU
7552 using a non-free binary blob.&lt;/p&gt;
7553
7554 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
7555 probably a few others installed. I have not checked the complete
7556 build dependency list.&lt;/p&gt;
7557
7558 &lt;p&gt;The resulting image will not use the hardware floating point unit
7559 on the Raspberry PI, because the armel architecture in Debian is not
7560 optimized for that use. So the images created will be a bit slower
7561 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
7562 </description>
7563 </item>
7564
7565 <item>
7566 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
7567 <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>
7568 <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>
7569 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
7570 <description>&lt;p&gt;The last few days I came across a few good causes that should get
7571 wider attention. I recommend signing and donating to each one of
7572 these. :)&lt;/p&gt;
7573
7574 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
7575 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
7576 Women program which is a Google Summer of Code like initiative to get
7577 more women involved in free software. One debian sponsor has offered
7578 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
7579 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
7580 hope you will to. :)&lt;/p&gt;
7581
7582 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
7583 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
7584 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
7585 take place these days, and their need to fund the work. I&#39;ve already
7586 donated. Are you next?&lt;/p&gt;
7587
7588 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
7589 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7590 statement under the heading
7591 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
7592 Access&lt;/a&gt; for those of us asking for more focus on open access in the
7593 Norwegian government. So far 499 signatures. I hope you will sign it
7594 too.&lt;/p&gt;
7595 </description>
7596 </item>
7597
7598 <item>
7599 <title>Videos about the Freedombox project - for inspiration and learning</title>
7600 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
7601 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
7602 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
7603 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
7604 project&lt;/a&gt; have been going on for a while, and have presented the
7605 vision, ideas and solution several places. Here is a little
7606 collection of videos of talks and presentation of the project.&lt;/p&gt;
7607
7608 &lt;ul&gt;
7609
7610 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
7611 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
7612
7613 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
7614 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7615
7616 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
7617 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7618 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
7619 (Youtube)&lt;/li&gt;
7620
7621 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
7622 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
7623
7624 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
7625 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7626
7627 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
7628 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7629 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
7630
7631 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7632 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7633 (Youtube)&lt;/li&gt;
7634
7635 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7636 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7637
7638 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7639 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7640
7641 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7642 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7643 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7644
7645 &lt;/ul&gt;
7646
7647 &lt;p&gt;A larger list is available from
7648 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7649 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7650
7651 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7652 Jessie is coming along quite well, and soon both Owncloud and using
7653 Tor should be available for testers of the Freedombox solution. :) In
7654 a few weeks I hope everything needed to test it is included in Debian.
7655 The withsqlite package is already in Debian, and the plinth package is
7656 pending in NEW. The third and vital part of that puzzle is the
7657 metapackage/setup framework, which is still pending an upload. Join
7658 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7659 (#freedombox on irc.debian.org)&lt;/a&gt; and
7660 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7661 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7662 </description>
7663 </item>
7664
7665 <item>
7666 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7667 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7668 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7669 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7670 <description>&lt;p&gt;I was introduced to the
7671 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7672 in 2010, when Eben Moglen presented his vision about serving the need
7673 of non-technical people to keep their personal information private and
7674 within the legal protection of their own homes. The idea is to give
7675 people back the power over their network and machines, and return
7676 Internet back to its intended peer-to-peer architecture. Instead of
7677 depending on a central service, the Freedombox will give everyone
7678 control over their own basic infrastructure.&lt;/p&gt;
7679
7680 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7681 taken priority. But this summers nasty news about the misuse of trust
7682 and privilege exercised by the &quot;western&quot; intelligence gathering
7683 communities increased my eagerness to contribute to a point where I
7684 actually started working on the project a while back.&lt;/p&gt;
7685
7686 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7687 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7688 create a simple and cheap Debian based appliance that anyone can hook
7689 up in their home and get access to secure and private services and
7690 communication. The initial deployment platform have been the
7691 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7692 which is a piece of hardware I do not own. So to be able to test what
7693 the current Freedombox setup look like, I had to come up with a way to install
7694 it on some hardware I do have access to. I have rewritten the
7695 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7696 image build framework to use .deb packages instead of only copying
7697 setup into the boot images, and thanks to this rewrite I am able to
7698 set up any machine supported by Debian Wheezy as a Freedombox, using
7699 the previously mentioned deb (and a few support debs for packages
7700 missing in Debian).&lt;/p&gt;
7701
7702 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7703 scripts
7704 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7705 and a administrative web interface
7706 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7707 withsqlite), as well as a privacy enhancing proxy based on
7708 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7709 (freedombox-privoxy). There is also a web/javascript based XMPP
7710 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7711 trying (unsuccessfully so far) to talk to the XMPP server
7712 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7713 web interface is pluggable, and the goal is to use it to enable OpenID
7714 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7715 this is really working yet, see
7716 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7717 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7718 on github at the moment. The HTTP proxy is operational out of the
7719 box, and the admin web interface can be used to add/remove plinth
7720 users. I&#39;ve not been able to do anything else with it so far, but
7721 know there are several branches spread around github and other places
7722 with lots of half baked features.&lt;/p&gt;
7723
7724 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7725 following recipes should work to give you a test machine to poke
7726 at.&lt;/p&gt;
7727
7728 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7729
7730 &lt;ol&gt;
7731
7732 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7733 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7734 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7735 to the Debian installer:&lt;p&gt;
7736 &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;
7737
7738 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7739 install on.&lt;/li&gt;
7740
7741 &lt;li&gt;When the installation is finished and the machine have rebooted a
7742 few times, your Freedombox is ready for testing.&lt;/li&gt;
7743
7744 &lt;/ol&gt;
7745
7746 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7747
7748 &lt;ol&gt;
7749
7750 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7751 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
7752 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
7753 &lt;pre&gt;
7754 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
7755 &lt;/pre&gt;&lt;/li&gt;
7756 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
7757 &lt;pre&gt;
7758 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7759 apt-key add -
7760 apt-get update
7761 apt-get install freedombox-setup
7762 /usr/lib/freedombox/setup
7763 &lt;/pre&gt;&lt;/li&gt;
7764 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
7765
7766 &lt;/ol&gt;
7767
7768 &lt;p&gt;You can test it on other architectures too, but because the
7769 freedombox-privoxy package is binary, it will only work as intended on
7770 the architectures where I have had time to build the binary and put it
7771 in my APT repository. But do not let this stop you. It is only a
7772 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
7773
7774 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
7775 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
7776 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
7777 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
7778
7779 &lt;p&gt;Please let me know if this works for you, or if you have any
7780 problems. We gather on the IRC channel
7781 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
7782 irc.debian.org and the
7783 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
7784 mailing list&lt;/a&gt;.&lt;/p&gt;
7785
7786 &lt;p&gt;Once you get your freedombox operational, you can visit
7787 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
7788 welcome screen (dead end - do not be surprised if you are unable to
7789 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
7790 to look at the rest of plinth. The default user is &#39;admin&#39; and the
7791 default password is &#39;secret&#39;.&lt;/p&gt;
7792 </description>
7793 </item>
7794
7795 <item>
7796 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
7797 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
7798 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
7799 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
7800 <description>&lt;p&gt;Earlier, I reported about
7801 &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
7802 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
7803 told by IBM that the original disk should be thrown away. And as
7804 there no longer was a problem if I bricked the firmware, I decided
7805 today to try to install Intel firmware to replace the Lenovo firmware
7806 currently on the disk.&lt;/p&gt;
7807
7808 &lt;p&gt;I searched the Intel site for firmware, and found
7809 &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;
7810 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7811 according to the site should contain the latest firmware for SSD
7812 disks. I inserted the broken disk in one of my spare laptops and
7813 booted the ISO from a USB stick. The disk was recognized, but the
7814 program claimed the newest firmware already were installed and refused
7815 to insert any Intel firmware. So no change, and the disk is still
7816 unable to handle write load. :( I guess the only way to get them
7817 working would be if Lenovo releases new firmware. No idea how likely
7818 that is. Anyway, just blogging about this test for completeness. I
7819 got a working Samsung disk, and see no point in spending more time on
7820 the broken disks.&lt;/p&gt;
7821 </description>
7822 </item>
7823
7824 <item>
7825 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
7826 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
7827 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
7828 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
7829 <description>&lt;p&gt;Today I switched to
7830 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
7831 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
7832 my new Thinkpad X230, which was delivered with an
7833 &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
7834 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
7835 sustained writes. My hardware supplier have been very forthcoming in
7836 trying to find a solution, and after first trying with another
7837 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
7838 disk instead to fix it once and for all. The Samsung disk survived
7839 the installation of Debian with encrypted disks (filling the disk with
7840 random data during installation killed the first two), and I thus
7841 decided to trust it with my data. I have installed it as a Debian Edu
7842 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7843 server at home using Kerberos and LDAP, and will use it as my work
7844 station from now on.&lt;/p&gt;
7845
7846 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
7847 Debian Wheezy default installation need to be tuned a bit to increase
7848 performance and increase life time of the disk. The Linux kernel and
7849 user space applications do not yet adjust automatically to such
7850 environment. To make it easier for my self, I created a draft Debian
7851 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
7852 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
7853 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
7854 is set up to adjust the setup of the machine by just installing the
7855 package. If there is any non-SSD disk in the machine, the package
7856 will refuse to install, as I did not try to write any logic to sort
7857 file systems in SSD and non-SSD file systems.&lt;/p&gt;
7858
7859 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
7860 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7861 where I set up the machine with one large encrypted partition (in
7862 addition to /boot), put LVM on top of this and set up partitions on
7863 top of this again. See the README file in the package source for the
7864 references I used to pick the settings. At the moment these
7865 parameters are tuned:&lt;/p&gt;
7866
7867 &lt;ul&gt;
7868
7869 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
7870 (adding discard to /etc/crypttab)&lt;/li&gt;
7871
7872 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
7873 this case a cryptsetup partition) by changing issue_discards from
7874 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
7875
7876 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
7877 systems.&lt;/li&gt;
7878
7879 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
7880 /etc/fstab.&lt;/li&gt;
7881
7882 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
7883
7884 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
7885 cron.daily).&lt;/li&gt;
7886
7887 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
7888 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
7889
7890 &lt;/ul&gt;
7891
7892 &lt;p&gt;During installation, I cancelled the part where the installer fill
7893 the disk with random data, as this would kill the SSD performance for
7894 little gain. My goal with the encrypted file system is to ensure
7895 those stealing my laptop end up with a brick and not a working
7896 computer. I have no hope in keeping the really resourceful people
7897 from getting the data on the disk (see
7898 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
7899 Thus I concluded that adding the discard option to crypttab is the
7900 right thing to do.&lt;/p&gt;
7901
7902 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
7903 it for SSD, but others recommended deadline and a benchmark I found
7904 indicated that deadline might be better for interactive use.&lt;/p&gt;
7905
7906 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
7907 and ext4, but read that it would give a performance hit ever time a
7908 file is removed, and thought it best to that that slowdown once a day
7909 instead of during my work.&lt;/p&gt;
7910
7911 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7912 this is already done by Debian Edu.&lt;/p&gt;
7913
7914 &lt;p&gt;I have not yet started on the user space tuning. I expect
7915 iceweasel need some tuning, and perhaps other applications too, but
7916 have not yet had time to investigate those parts.&lt;/p&gt;
7917
7918 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
7919 there.&lt;/p&gt;
7920
7921 &lt;p&gt;As for the answer to the question in the title of this blog post,
7922 as far as I know, the only solution I know about is to replace the
7923 disk. It might be possible to flash it with Intel firmware instead of
7924 the Lenovo firmware. But I have not tried and did not want to do so
7925 without approval from Lenovo as I wanted to keep the warranty on the
7926 disk until a solution was found and they wanted the broken disks
7927 back.&lt;/p&gt;
7928 </description>
7929 </item>
7930
7931 <item>
7932 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
7933 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
7934 <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>
7935 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
7936 <description>&lt;p&gt;A few days ago, I wrote about
7937 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
7938 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
7939 was dying during installation because it is unable to cope with
7940 sustained write. My supplier is in contact with
7941 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
7942 replacement disk to try to fix the problem. They decided to send an
7943 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
7944
7945 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
7946 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7947 same firmware version as the original. This time my hope raised
7948 slightly as the installation progressed, as the original disk used to
7949 die after 4-7% of the disk was written to, while this time it kept
7950 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
7951 died again and I was back on square one. I still do not have a new
7952 laptop with a disk I can trust. I can not live with a disk that might
7953 lock up when I download a new
7954 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
7955 other large files. I look forward to hearing from my supplier with
7956 the next proposal from Lenovo.&lt;/p&gt;
7957
7958 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
7959 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7960 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7961 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
7962 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7963 P/N 45N8295, P0C38732.&lt;/p&gt;
7964
7965 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
7966 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
7967 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7968 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
7969 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7970 P/N 45N8295, P0C38732.&lt;/p&gt;
7971
7972 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
7973 SA, date and WNPP values. Mentioning all the details here in case
7974 someone is able to use the information to find a way to identify the
7975 failing disk among working ones (if any such working disk actually
7976 exist).&lt;/p&gt;
7977 </description>
7978 </item>
7979
7980 <item>
7981 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
7982 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
7983 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
7984 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
7985 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
7986 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7987 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
7988 member assosiation NUUG&lt;/a&gt; and
7989 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
7990 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
7991 Bitraf&lt;/a&gt;.&lt;/p&gt;
7992
7993 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
7994 welcome, and there is no fee to participate. There is on the other
7995 hand limited space, and only room for 30 people. Please put your name
7996 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
7997 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
7998 </description>
7999 </item>
8000
8001 <item>
8002 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
8003 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
8004 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
8005 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
8006 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
8007 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
8008 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
8009 time to spend on it, and it took a while to find a model I believe
8010 will do the job, but two days ago the replacement finally arrived. I
8011 ended up picking a
8012 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
8013 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
8014 a roaming workstation, and it seemed to work flawlessly. But my
8015 second installation with encrypted disk was not as successful. More
8016 on that below.&lt;/p&gt;
8017
8018 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8019 important requirements (robust and with a good keyboard) are never
8020 listed in the feature list. But I did get good help from the search
8021 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8022 allowed me to limit the list of interesting laptops based on my other
8023 requirements. A bit surprising that SSD disk are not disks according
8024 to that search interface, so I had to drop specifying the number of
8025 disks from my search parameters. I also asked around among friends to
8026 get their impression on keyboards and robustness.&lt;/p&gt;
8027
8028 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
8029 X41. I am not quite convinced about the keyboard, as it is
8030 significantly wider than my old keyboard, and I have to stretch my
8031 hand a lot more to reach the edges. But the key response is fairly
8032 good and the individual key shape is fairly easy to handle, so I hope
8033 I will get used to it. My old X40 was starting to fail, and I really
8034 needed a new laptop now. :)&lt;/p&gt;
8035
8036 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
8037 visit to the BIOS during boot it disable it.&lt;/p&gt;
8038
8039 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
8040 lock up during load. And this happen when installing Debian Wheezy
8041 with encrypted disk, while the disk is being filled with random data.
8042 I also tested to install Ubuntu Raring, and it happen there too if I
8043 reenable the code to fill the disk with random data (it is disabled by
8044 default in Ubuntu). And the bug with is already known. It was
8045 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
8046 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
8047 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
8048 kernel developers as
8049 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
8050 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
8051 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
8052 Lenovo forums, both for
8053 &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
8054 2012-11-10&lt;/a&gt; and for
8055 &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
8056 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
8057 reports state that the disk lock up during use if many writes are done
8058 on the disk, so it is much no use to work around the installation
8059 problem and end up with a computer that can lock up at any moment.
8060 There is even a
8061 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
8062 available&lt;/a&gt; that will lock up the hard drive after running a few
8063 minutes by writing to a file.&lt;/p&gt;
8064
8065 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
8066 contacting PCHELP Norway (request 01D1FDP) which handle support
8067 requests for Lenovo, his first suggestion was to upgrade the disk
8068 firmware. Unfortunately there is no newer firmware available from
8069 Lenovo, as my disk already have the most recent one (version LF1i). I
8070 hope to hear more from him today and hope the problem can be
8071 fixed. :)&lt;/p&gt;
8072 </description>
8073 </item>
8074
8075 <item>
8076 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
8077 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
8078 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
8079 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
8080 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
8081 trusty old Thinkpad X41. Unfortunately I did not have much time to
8082 spend on it, but today the replacement finally arrived. I ended up
8083 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
8084 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
8085 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8086 this, it is installing what I hope will be a more final installation,
8087 with a encrypted hard drive to ensure any dope head stealing it end up
8088 with an expencive door stop.&lt;/p&gt;
8089
8090 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8091 important requirements (robust and with a good keyboard) are never
8092 listed in the feature list. But I did get good help from the search
8093 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8094 allowed me to limit the list of interesting laptops based on my other
8095 requirements. A bit surprising that SSD disk are not disks, so I had
8096 to drop number of disks from my search parameters.&lt;/p&gt;
8097
8098 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
8099 wider than my old keyboard, and I have to stretch my hand a lot more
8100 to reach the edges. But the key response is fairly good and the
8101 individual key shape is fairly easy to handle, so I hope I will get
8102 used to it. My old X40 was starting to fail, and I really needed a
8103 new laptop now. :)&lt;/p&gt;
8104
8105 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
8106 </description>
8107 </item>
8108
8109 <item>
8110 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
8111 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
8112 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
8113 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
8114 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
8115 perfectly capable of, and I have to do it manually to get things
8116 working. One such task is to find out what firmware packages are
8117 needed to get the hardware on my computer working. Most often this
8118 affect the wifi card, but some times it even affect the RAID
8119 controller or the ethernet card. Today I pushed version 0.4 of the
8120 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
8121 including a new script isenkram-autoinstall-firmware handling the
8122 process of asking all the loaded kernel modules what firmware files
8123 they want, find debian packages providing these files and install the
8124 debian packages. Here is a test run on my laptop:&lt;/p&gt;
8125
8126 &lt;p&gt;&lt;pre&gt;
8127 # isenkram-autoinstall-firmware
8128 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8129 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8130 info: locating packages with the requested firmware files
8131 info: Updating APT sources after adding non-free APT source
8132 info: trying to install firmware-ipw2x00
8133 firmware-ipw2x00
8134 firmware-ipw2x00
8135 Preconfiguring packages ...
8136 Selecting previously deselected package firmware-ipw2x00.
8137 (Reading database ... 259727 files and directories currently installed.)
8138 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8139 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
8140 #
8141 &lt;/pre&gt;&lt;/p&gt;
8142
8143 &lt;p&gt;When all the requested firmware is present, a simple message is
8144 printed instead:&lt;/p&gt;
8145
8146 &lt;p&gt;&lt;pre&gt;
8147 # isenkram-autoinstall-firmware
8148 info: did not find any firmware files requested by loaded kernel modules. exiting
8149 #
8150 &lt;/pre&gt;&lt;/p&gt;
8151
8152 &lt;p&gt;It could use some polish, but it is already working well and saving
8153 me some time when setting up new machines. :)&lt;/p&gt;
8154
8155 &lt;p&gt;So, how does it work? It look at the set of currently loaded
8156 kernel modules, and look up each one of them using modinfo, to find
8157 the firmware files listed in the module meta-information. Next, it
8158 download the Contents file from a nearby APT mirror, and search for
8159 the firmware files in this file to locate the package with the
8160 requested firmware file. If the package is in the non-free section, a
8161 non-free APT source is added and the package is installed using
8162 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
8163 machine.&lt;/p&gt;
8164
8165 &lt;p&gt;I hope someone find time to implement a more polished version of
8166 this script as part of the hw-detect debian-installer module, to
8167 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
8168 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
8169 firmware during a PXE install when the packages already are available
8170 from the nearby Debian mirror.&lt;/p&gt;
8171 </description>
8172 </item>
8173
8174 <item>
8175 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
8176 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
8177 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
8178 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
8179 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8180 the screen just turn black when Linux boot, either during installation
8181 or on first boot from the hard disk. I&#39;ve seen it once in a while the
8182 last few years, but only recently understood the cause. I&#39;ve seen it
8183 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8184 The reason seem to be in the wiring of some laptops. The system to
8185 control the screen background light is inverted, so when Linux try to
8186 turn the brightness fully on, it end up turning it off instead. I do
8187 not know which Linux drivers are affected, but this post is about the
8188 i915 driver used by the
8189 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8190 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
8191
8192 &lt;p&gt;The problem can be worked around two ways. Either by adding
8193 i915.invert_brightness=1 as a kernel option, or by adding a file in
8194 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
8195 option when it load the i915 kernel module. On Debian and Ubuntu, it
8196 can be done by running these commands as root:&lt;/p&gt;
8197
8198 &lt;pre&gt;
8199 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
8200 update-initramfs -u -k all
8201 &lt;/pre&gt;
8202
8203 &lt;p&gt;Since March 2012 there is
8204 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
8205 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
8206 hardware have this problem, and get the driver to invert the
8207 brightness setting automatically. To use it, one need to add a row in
8208 &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
8209 intel_quirks array&lt;/a&gt; in the driver source
8210 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
8211 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
8212 number (vendor number 8086 is assumed) and subdevice vendor and device
8213 number.&lt;/p&gt;
8214
8215 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
8216 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
8217
8218 &lt;p&gt;&lt;pre&gt;
8219 00:02.0 VGA compatible controller [0300]: Intel Corporation \
8220 3rd Gen Core processor Graphics Controller [8086:0156] \
8221 (rev 09) (prog-if 00 [VGA controller])
8222 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
8223 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8224 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8225 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
8226 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
8227 Latency: 0
8228 Interrupt: pin A routed to IRQ 42
8229 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
8230 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
8231 Region 4: I/O ports at 4000 [size=64]
8232 Expansion ROM at &lt;unassigned&gt; [disabled]
8233 Capabilities: &lt;access denied&gt;
8234 Kernel driver in use: i915
8235 &lt;/pre&gt;&lt;/p&gt;
8236
8237 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
8238
8239 &lt;p&gt;&lt;pre&gt;
8240 struct intel_quirk intel_quirks[] = {
8241 ...
8242 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8243 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
8244 ...
8245 }
8246 &lt;/pre&gt;&lt;/p&gt;
8247
8248 &lt;p&gt;According to the kernel module instructions (as seen using
8249 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
8250 invert_brightness flag should be sent to the
8251 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
8252 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
8253 developers. But my email about the laptop sent 2013-06-03 have not
8254 yet shown up in
8255 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
8256 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
8257 emails from non-subscribers. Because of this, I sent my patch also to
8258 the Debian bug tracking system instead as
8259 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
8260 sure the patch is not lost.&lt;/p&gt;
8261
8262 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
8263 with this problem working properly with Linux. If you use Gnome, your
8264 worries should be over at this point. But if you use KDE, there is
8265 something in KDE ignoring the invert_brightness setting and turning on
8266 the screen during login. I&#39;ve reported it to Debian as
8267 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
8268 have no idea yet how to figure out exactly what subsystem is doing
8269 this. Perhaps you can help? Perhaps you know what the Gnome
8270 developers did to handle this, and this can give a clue to the KDE
8271 developers? Or you know where in KDE the screen brightness is changed
8272 during login? If so, please update the BTS report (or get in touch if
8273 you do not know how to update BTS).&lt;/p&gt;
8274
8275 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
8276 acpi_backlight=vendor, to disable ACPI backlight support completely,
8277 as the ACPI information on the machine is trash and it is better to
8278 leave it to the intel video driver to control the screen
8279 backlight.&lt;/p&gt;
8280 </description>
8281 </item>
8282
8283 <item>
8284 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
8285 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
8286 <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>
8287 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
8288 <description>&lt;p&gt;Two days ago, I asked
8289 &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
8290 I could install Linux on a Packard Bell EasyNote LV computer
8291 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
8292 with the obstacles put in the way of Linux users on a laptop with UEFI
8293 and Windows 8.&lt;/p&gt;
8294
8295 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
8296 secure booting or fast boot. I suspect fast boot was the problem,
8297 causing the firmware to boot directly from HD without considering any
8298 key presses and alternative devices, but do not know UEFI settings
8299 enough to tell.&lt;/p&gt;
8300
8301 &lt;p&gt;There is no way to install Linux on the machine in question without
8302 opening the box and disconnecting the hard drive! This is as far as I
8303 can tell, the only way to get access to the firmware setup menu
8304 without accepting the Windows 8 license agreement. I am told (and
8305 found description on how to) that it is possible to configure the
8306 firmware setup once booted into Windows 8. But as I believe the terms
8307 of that agreement are completely unacceptable, accepting the license
8308 was never an alternative. I do not enter agreements I do not intend
8309 to follow.&lt;/p&gt;
8310
8311 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
8312 waste many hours on this, but luckily there was a way to get it to
8313 work. But I would not recommend it to anyone planning to run Linux on
8314 it, and I have become sceptical to Windows 8 certified laptops. Is
8315 this the way Linux will be forced out of the market place, by making
8316 it close to impossible for &quot;normal&quot; users to install Linux without
8317 accepting the Microsoft Windows license terms? Or at least not
8318 without risking to loose the warranty?&lt;/p&gt;
8319
8320 &lt;p&gt;I&#39;ve updated the
8321 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
8322 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
8323 do not have to struggle as much as I did to get Linux into the
8324 machine.&lt;/p&gt;
8325
8326 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8327 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
8328 </description>
8329 </item>
8330
8331 <item>
8332 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
8333 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
8334 <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>
8335 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
8336 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
8337 new laptops for my parents and a few others. I bought Packard Bell
8338 Easynote LV to run Kubuntu on and use as their home computer. But I
8339 am completely unable to figure out how to install Linux on it. The
8340 computer is preinstalled with Windows 8, and I suspect it uses UEFI
8341 instead of a BIOS to boot.&lt;/p&gt;
8342
8343 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
8344 to get it to boot the Linux installer from my USB stick. I have yet
8345 to try the DVD install, and still hope it will work. when I turn on
8346 the computer, there is no information on what buttons to press to get
8347 the normal boot menu. I expect to get some boot menu to select PXE or
8348 USB stick booting. When booting, it first ask for the language to
8349 use, then for some regional settings, and finally if I will accept the
8350 Windows 8 terms of use. As these terms are completely unacceptable to
8351 me, I have no other choice but to turn off the computer and try again
8352 to get it to boot the Linux installer.&lt;/p&gt;
8353
8354 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
8355 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8356 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
8357 installed on this machine, please get in touch or update that wiki
8358 page. If I can&#39;t find a way to install Linux, I will have to return
8359 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
8360
8361 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
8362 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
8363 on new Laptops?&lt;/p&gt;
8364 </description>
8365 </item>
8366
8367 <item>
8368 <title>How to transform a Debian based system to a Debian Edu installation</title>
8369 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
8370 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
8371 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
8372 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
8373 an operating system based on Debian intended for use in schools. It
8374 contain a turn-key solution for the computer network provided to
8375 pupils in the primary schools. It provide both the central server,
8376 network boot servers and desktop environments with heaps of
8377 educational software. The project was founded almost 12 years ago,
8378 2001-07-02. If you want to support the project, which is in need for
8379 cash to fund developer gatherings and other project related activity,
8380 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
8381 donate some money&lt;/a&gt;.
8382
8383 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
8384 lists and elsewhere, is the question on how to transform a Debian or
8385 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
8386 hard, and last week I wrote a script to replicate the steps done by
8387 the Debian Edu installer.&lt;/p&gt;
8388
8389 &lt;p&gt;The script,
8390 &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;
8391 in the debian-edu-config package, will go through these six steps and
8392 transform an existing Debian Wheezy or Ubuntu (untested) installation
8393 into a Debian Edu Workstation:&lt;/p&gt;
8394
8395 &lt;ol&gt;
8396
8397 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
8398 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
8399 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
8400 our configuration.&lt;/li&gt;
8401 &lt;li&gt;Preseed debconf database with profile setup in
8402 /etc/debian-edu/config, and run tasksel to install packages
8403 according to the profile specified in the config above,
8404 overriding some of the Debian automation machinery.&lt;/li&gt;
8405 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
8406 that could not be done using preseeding.&lt;/li&gt;
8407 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
8408
8409 &lt;/ol&gt;
8410
8411 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
8412 replicated like this. Disk partitioning and LVM setup, for example.
8413 So this script just assume there is enough disk space to install all
8414 the needed packages.&lt;/p&gt;
8415
8416 &lt;p&gt;The script was created to help a Debian Edu student working on
8417 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
8418 Debian Edu client, and using it he can take the existing
8419 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
8420 transform it into a fully functioning Debian Edu Workstation (or
8421 Roaming Workstation, or whatever :).&lt;/p&gt;
8422
8423 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
8424 If a LXDE based Roaming workstation is wanted instead, modify the
8425 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
8426
8427 &lt;p&gt;&lt;pre&gt;
8428 PROFILE=&quot;Roaming-Workstation&quot;
8429 DESKTOP=&quot;lxde&quot;
8430 &lt;/pre&gt;&lt;/p&gt;
8431
8432 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
8433 the cloud, by starting with a virtual Debian installation at some
8434 virtual hosting service and setting up all the services on first
8435 boot.&lt;/p&gt;
8436 </description>
8437 </item>
8438
8439 <item>
8440 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
8441 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
8442 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
8443 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
8444 <description>&lt;P&gt;In January,
8445 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
8446 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
8447 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
8448 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
8449 marvellous construction system from Denmark. We also created
8450 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
8451 a place to take notes and write down our plans and hopes. And several
8452 people showed up to help. I was very happy to see the effect of my
8453 call. Since the small start, we have a debtags tag
8454 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
8455 tag for LEGO related packages, and now count 10 packages related to
8456 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
8457
8458 &lt;p&gt;&lt;table&gt;
8459 &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;
8460 &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;
8461 &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;
8462 &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;
8463 &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;
8464 &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;
8465 &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;
8466 &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;
8467 &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;
8468 &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;
8469 &lt;/table&gt;&lt;/p&gt;
8470
8471 &lt;p&gt;Some of these are available in Wheezy, and all but one are
8472 currently available in Jessie/testing. leocad is so far only
8473 available in experimental.&lt;/p&gt;
8474
8475 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
8476 adding the rest of the great free software tools available on Linux
8477 for LEGO designers.&lt;/p&gt;
8478 </description>
8479 </item>
8480
8481 <item>
8482 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
8483 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
8484 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
8485 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
8486 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
8487 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
8488 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
8489 Debian release, and I expect to move my machines at home over to it fairly
8490 soon.&lt;/p&gt;
8491
8492 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
8493 in particular make me very happy to see included. The
8494 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
8495 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
8496 included for the first time. Alongside similar programs like
8497 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
8498 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
8499 it allow for visual programming where syntax errors can not happen,
8500 and a friendly programming environment for learning to control the
8501 computer. Scratch will also be included in the next release of Debian
8502 Edu.&lt;/a&gt;
8503
8504 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
8505 Edu/Skolelinux release too. The
8506 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
8507 alpha release&lt;/a&gt; went out last week, and the next should soon
8508 follow.&lt;p&gt;
8509 </description>
8510 </item>
8511
8512 <item>
8513 <title>Isenkram 0.2 finally in the Debian archive</title>
8514 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
8515 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
8516 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
8517 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
8518 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
8519 for many months. I uploaded it to the Debian experimental suite
8520 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
8521
8522 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
8523 install to work with a pluggable hardware device. The suggestion pop
8524 up when the device is plugged in. For example if a Lego Mindstorm NXT
8525 is inserted, it will suggest to install the program needed to program
8526 the NXT controller. Give it a go, and report bugs and suggestions to
8527 BTS. :)&lt;/p&gt;
8528 </description>
8529 </item>
8530
8531 <item>
8532 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
8533 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
8534 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
8535 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
8536 <description>&lt;p&gt;My
8537 &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
8538 bitcoin related blog post&lt;/a&gt; mentioned that the new
8539 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
8540 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8541 2013-01-19, and have been available in unstable since then. It was
8542 automatically copied to Ubuntu, and is available in their Raring
8543 version too.&lt;/p&gt;
8544
8545 &lt;p&gt;But there is a strange problem with the build that block this new
8546 version from being available on the i386 and kfreebsd-i386
8547 architectures. For some strange reason, the autobuilders in Debian
8548 for these architectures fail to run the test suite on these
8549 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
8550 We are so far unable to reproduce it when building it manually, and
8551 no-one have been able to propose a fix. If you got an idea what is
8552 failing, please let us know via the BTS.&lt;/p&gt;
8553
8554 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
8555 I often run low on disk space, is the fact that the client will exit
8556 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
8557 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
8558 it. :)&lt;/p&gt;
8559
8560 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8561 activities, please send Bitcoin donations to my address
8562 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8563 </description>
8564 </item>
8565
8566 <item>
8567 <title>Welcome to the world, Isenkram!</title>
8568 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
8569 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
8570 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
8571 <description>&lt;p&gt;Yesterday, I
8572 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
8573 for testers&lt;/a&gt; for my prototype for making Debian better at handling
8574 pluggable hardware devices, which I
8575 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
8576 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
8577 up, and caused me to really want to to open up the development to more
8578 people. But before I did this, I want to come up with a sensible name
8579 for this project. Today I finally decided on a new name, and I have
8580 renamed the project from hw-support-handler to this new name. In the
8581 process, I moved the source to git and made it available as a
8582 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
8583 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
8584 To fetch and build the latest version of the source, use&lt;/p&gt;
8585
8586 &lt;pre&gt;
8587 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8588 cd isenkram &amp;&amp; git-buildpackage -us -uc
8589 &lt;/pre&gt;
8590
8591 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
8592 want to hack on the source or improve the package, please go ahead.
8593 But please talk to me first on IRC or via email before you do major
8594 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
8595
8596 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
8597 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8598 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
8599 the German word eisenkram, for those that are familiar with that
8600 word.&lt;/p&gt;
8601
8602 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
8603 instructions, to avoid confusing people with an error from the signing
8604 process.&lt;/p&gt;
8605
8606 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
8607 clone argument to avoid the need for authentication.&lt;/p&gt;
8608 </description>
8609 </item>
8610
8611 <item>
8612 <title>First prototype ready making hardware easier to use in Debian</title>
8613 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
8614 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
8615 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
8616 <description>&lt;p&gt;Early this month I set out to try to
8617 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
8618 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
8619 prototype is working, and it is ready for a larger audience. To test
8620 it, fetch the
8621 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
8622 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
8623 package. You might have to log out and in again activate the
8624 autostart script.&lt;/p&gt;
8625
8626 &lt;p&gt;The design is simple:&lt;/p&gt;
8627
8628 &lt;ul&gt;
8629
8630 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
8631 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8632
8633 &lt;li&gt;This program listen for kernel events about new hardware (directly
8634 from the kernel like udev does), not using HAL dbus events as I
8635 initially did.&lt;/li&gt;
8636
8637 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8638 the APT database, a database
8639 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8640 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8641
8642 &lt;li&gt;If a package is mapped to the hardware in question, the package
8643 isn&#39;t installed yet and this is the first time the hardware was
8644 plugged in, show a desktop notification suggesting to install the
8645 package or packages.&lt;/li&gt;
8646
8647 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8648 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8649
8650 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8651 package while showing progress information in a window.&lt;/li&gt;
8652
8653 &lt;/ul&gt;
8654
8655 &lt;p&gt;I still need to come up with a better name for the system. Here
8656 are some screen shots showing the prototype in action. First the
8657 notification, then the password request, and finally the request to
8658 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8659
8660 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8661 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8662 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8663 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8664 &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;
8665
8666 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8667 is already useful. The database of hardware to package mappings also
8668 need more work. It is currently compatible with the Ubuntu way of
8669 storing such information in the package control file, but could be
8670 changed to use other formats instead or in addition to the current
8671 method. I&#39;ve dropped the use of discover for this mapping, as the
8672 modalias approach is more flexible and easier to use on Linux as long
8673 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8674
8675 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8676 here is the command required to check out and build the source: Use
8677 &#39;&lt;tt&gt;svn checkout
8678 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8679 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8680 devscripts package.&lt;/p&gt;
8681
8682 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8683 renamed to Isenkram and the source moved from the Debian Edu
8684 subversion repository to a Debian collab-maint git repository. See
8685 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8686 instructions&lt;/a&gt; for details.&lt;/p&gt;
8687 </description>
8688 </item>
8689
8690 <item>
8691 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8692 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8693 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8694 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8695 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8696 suddenly in bed. With a quiet whimper, it went completely quiet and
8697 black. The power button was no longer able to turn it on. It was a
8698 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8699 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8700 Compaq I had before that. Now I need to find a replacement. To keep
8701 going during Christmas, I moved the one year old SSD disk to my old
8702 X40 where it fitted (only one I had left that could use it), but it is
8703 not a durable solution.
8704
8705 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8706 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8707
8708 &lt;ul&gt;
8709
8710 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8711 than A4).&lt;/li&gt;
8712 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8713 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8714 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8715 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8716 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8717 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8718 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8719 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8720 size).&lt;/li&gt;
8721 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8722 X.org packages.&lt;/li&gt;
8723 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8724 the time).
8725
8726 &lt;/ul&gt;
8727
8728 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8729 list. The reason is simply that the specifications on laptops the
8730 last 10-15 years have been sufficient for my needs, and I have to look
8731 at other features to choose my laptop. But are there still made as
8732 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8733 robust, and Thinkpads seem to be heading in the wrong direction since
8734 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8735 still be useful.&lt;/p&gt;
8736
8737 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8738 external keyboard? I&#39;ll have to check the
8739 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8740 well-supported laptops, or perhaps just buy one preinstalled from one
8741 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8742 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8743 </description>
8744 </item>
8745
8746 <item>
8747 <title>How to find a browser plugin supporting a given MIME type</title>
8748 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8749 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8750 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8751 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
8752 install to get support for a given MIME type. Thanks to
8753 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
8754 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
8755 Unfortunately, not very many packages provide the needed meta
8756 information, Anyway, here is a small script to look up all browser
8757 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
8758
8759 &lt;pre&gt;
8760 #!/usr/bin/python
8761 import sys
8762 import apt
8763 def pkgs_handling_mimetype(mimetype):
8764 cache = apt.Cache()
8765 cache.open(None)
8766 thepkgs = []
8767 for pkg in cache:
8768 version = pkg.candidate
8769 if version is None:
8770 version = pkg.installed
8771 if version is None:
8772 continue
8773 record = version.record
8774 if not record.has_key(&#39;Npp-MimeType&#39;):
8775 continue
8776 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
8777 for t in mime_types:
8778 t = t.rstrip().strip()
8779 if t == mimetype:
8780 thepkgs.append(pkg.name)
8781 return thepkgs
8782 mimetype = &quot;audio/ogg&quot;
8783 if 1 &lt; len(sys.argv):
8784 mimetype = sys.argv[1]
8785 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
8786 for pkg in pkgs_handling_mimetype(mimetype):
8787 print &quot; %s&quot; %pkg
8788 &lt;/pre&gt;
8789
8790 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
8791
8792 &lt;pre&gt;
8793 % ./apt-find-browserplug-for-mimetype
8794 Browser plugin packages supporting audio/ogg:
8795 gecko-mediaplayer
8796 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8797 Browser plugin packages supporting application/x-shockwave-flash:
8798 browser-plugin-gnash
8799 %
8800 &lt;/pre&gt;
8801
8802 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
8803 itself to query for plugins and propose to install the needed
8804 packages. It would be great if Debian supported such feature too. Is
8805 anyone working on adding it?&lt;/p&gt;
8806
8807 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
8808 request for icweasel support for this feature is
8809 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
8810 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
8811 of manpower and wish for a different design is the reason thus feature
8812 is not yet in iceweasel from Debian.&lt;/p&gt;
8813 </description>
8814 </item>
8815
8816 <item>
8817 <title>What is the most supported MIME type in Debian?</title>
8818 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
8819 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
8820 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
8821 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
8822 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
8823 proposal to make it possible for a Desktop application to propose to
8824 the user some package to install to gain support for a given MIME
8825 type, font, library etc. that is currently missing. With such
8826 mechanism in place, it would be possible for the desktop to
8827 automatically propose and install leocad if some LDraw file is
8828 downloaded by the browser.&lt;/p&gt;
8829
8830 &lt;p&gt;To get some idea about the current content of the archive, I decided
8831 to write a simple program to extract all .desktop files from the
8832 Debian archive and look up the claimed MIME support there. The result
8833 can be found on the
8834 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
8835 site&lt;/a&gt;. Using the collected information, it become possible to
8836 answer the question in the title. Here are the 20 most supported MIME
8837 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8838 The complete list is available from the link above.&lt;/p&gt;
8839
8840 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
8841
8842 &lt;pre&gt;
8843 count MIME type
8844 ----- -----------------------
8845 32 text/plain
8846 30 audio/mpeg
8847 29 image/png
8848 28 image/jpeg
8849 27 application/ogg
8850 26 audio/x-mp3
8851 25 image/tiff
8852 25 image/gif
8853 22 image/bmp
8854 22 audio/x-wav
8855 20 audio/x-flac
8856 19 audio/x-mpegurl
8857 18 video/x-ms-asf
8858 18 audio/x-musepack
8859 18 audio/x-mpeg
8860 18 application/x-ogg
8861 17 video/mpeg
8862 17 audio/x-scpls
8863 17 audio/ogg
8864 16 video/x-ms-wmv
8865 &lt;/pre&gt;
8866
8867 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
8868
8869 &lt;pre&gt;
8870 count MIME type
8871 ----- -----------------------
8872 33 text/plain
8873 32 image/png
8874 32 image/jpeg
8875 29 audio/mpeg
8876 27 image/gif
8877 26 image/tiff
8878 26 application/ogg
8879 25 audio/x-mp3
8880 22 image/bmp
8881 21 audio/x-wav
8882 19 audio/x-mpegurl
8883 19 audio/x-mpeg
8884 18 video/mpeg
8885 18 audio/x-scpls
8886 18 audio/x-flac
8887 18 application/x-ogg
8888 17 video/x-ms-asf
8889 17 text/html
8890 17 audio/x-musepack
8891 16 image/x-xbitmap
8892 &lt;/pre&gt;
8893
8894 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
8895
8896 &lt;pre&gt;
8897 count MIME type
8898 ----- -----------------------
8899 31 text/plain
8900 31 image/png
8901 31 image/jpeg
8902 29 audio/mpeg
8903 28 application/ogg
8904 27 image/gif
8905 26 image/tiff
8906 26 audio/x-mp3
8907 23 audio/x-wav
8908 22 image/bmp
8909 21 audio/x-flac
8910 20 audio/x-mpegurl
8911 19 audio/x-mpeg
8912 18 video/x-ms-asf
8913 18 video/mpeg
8914 18 audio/x-scpls
8915 18 application/x-ogg
8916 17 audio/x-musepack
8917 16 video/x-ms-wmv
8918 16 video/x-msvideo
8919 &lt;/pre&gt;
8920
8921 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
8922 information mentioned in DEP-11. I have not yet had time to look at
8923 it, but hope the PackageKit people in Debian are on top of these
8924 issues.&lt;/p&gt;
8925
8926 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
8927 discovering a typo in my script.&lt;/p&gt;
8928 </description>
8929 </item>
8930
8931 <item>
8932 <title>Using modalias info to find packages handling my hardware</title>
8933 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
8934 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
8935 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
8936 <description>&lt;p&gt;Yesterday, I wrote about the
8937 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
8938 values provided by the Linux kernel&lt;/a&gt; following my hope for
8939 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
8940 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
8941 modalias values attached to package names can be used to map packages
8942 to hardware. This allow the system to look up and suggest relevant
8943 packages when I plug in some new hardware into my machine, and replace
8944 discover and discover-data as the database used to map hardware to
8945 packages.&lt;/p&gt;
8946
8947 &lt;p&gt;I create a modaliases file with entries like the following,
8948 containing package name, kernel module name (if relevant, otherwise
8949 the package name) and globs matching the relevant hardware
8950 modalias.&lt;/p&gt;
8951
8952 &lt;p&gt;&lt;blockquote&gt;
8953 Package: package-name
8954 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
8955 &lt;/blockquote&gt;&lt;/p&gt;
8956
8957 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
8958 for a given modalias value using this file.&lt;/p&gt;
8959
8960 &lt;p&gt;An entry like this would suggest the video and picture application
8961 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
8962
8963 &lt;p&gt;&lt;blockquote&gt;
8964 Package: cheese
8965 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
8966 &lt;/blockquote&gt;&lt;/p&gt;
8967
8968 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
8969 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
8970
8971 &lt;p&gt;&lt;blockquote&gt;
8972 Package: pcmciautils
8973 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8974 &lt;/blockquote&gt;&lt;/p&gt;
8975
8976 &lt;p&gt;An entry like this would suggest the package colorhug-client when
8977 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
8978
8979 &lt;p&gt;&lt;blockquote&gt;
8980 Package: colorhug-client
8981 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
8982 &lt;/blockquote&gt;&lt;/p&gt;
8983
8984 &lt;p&gt;I believe the format is compatible with the format of the Packages
8985 file in the Debian archive. Ubuntu already uses their Packages file
8986 to store their mappings from packages to hardware.&lt;/p&gt;
8987
8988 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
8989 announce the hardware it support in a way my prototype understand.
8990 This allow those publishing packages in an APT source outside the
8991 Debian archive as well as those backporting packages to make sure the
8992 hardware mapping are included in the package meta information. I&#39;ve
8993 tested such header in the pymissile package, and its modalias mapping
8994 is working as it should with my prototype. It even made it to Ubuntu
8995 Raring.&lt;/p&gt;
8996
8997 &lt;p&gt;To test if it was possible to look up supported hardware using only
8998 the shell tools available in the Debian installer, I wrote a shell
8999 implementation of the lookup code. The idea is to create files for
9000 each modalias and let the shell do the matching. Please check out and
9001 try the
9002 &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;
9003 shell script. It run without any extra dependencies and fetch the
9004 hardware mappings from the Debian archive and the subversion
9005 repository where I currently work on my prototype.&lt;/p&gt;
9006
9007 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
9008 install yubikey-personalization:&lt;/p&gt;
9009
9010 &lt;p&gt;&lt;blockquote&gt;
9011 % ./hw-support-lookup
9012 &lt;br&gt;yubikey-personalization
9013 &lt;br&gt;%
9014 &lt;/blockquote&gt;&lt;/p&gt;
9015
9016 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
9017 propose to install the pcmciautils package:&lt;/p&gt;
9018
9019 &lt;p&gt;&lt;blockquote&gt;
9020 % ./hw-support-lookup
9021 &lt;br&gt;pcmciautils
9022 &lt;br&gt;%
9023 &lt;/blockquote&gt;&lt;/p&gt;
9024
9025 &lt;p&gt;If you know of any hardware-package mapping that should be added to
9026 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
9027 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
9028
9029 &lt;p&gt;It could be possible to generate several of the mappings between
9030 packages and hardware. One source would be to look at packages with
9031 kernel modules, ie packages with *.ko files in /lib/modules/, and
9032 extract their modalias information. Another would be to look at
9033 packages with udev rules, ie packages with files in
9034 /lib/udev/rules.d/, and extract their vendor/model information to
9035 generate a modalias matching rule. I have not tested any of these to
9036 see if it work.&lt;/p&gt;
9037
9038 &lt;p&gt;If you want to help implementing a system to let us propose what
9039 packages to install when new hardware is plugged into a Debian
9040 machine, please send me an email or talk to me on
9041 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9042 </description>
9043 </item>
9044
9045 <item>
9046 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
9047 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
9048 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
9049 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
9050 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
9051 information, to find the packages that support a given piece of
9052 hardware, I refreshed my memory regarding modalias values, and decided
9053 to document the details. Here are my findings so far, also available
9054 in
9055 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9056 Debian Edu subversion repository&lt;/a&gt;:
9057
9058 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
9059
9060 &lt;p&gt;This document try to explain what the different types of modalias
9061 values stands for. It is in part based on information from
9062 &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;,
9063 &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;,
9064 &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
9065 &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;.
9066
9067 &lt;p&gt;The modalias entries for a given Linux machine can be found using
9068 this shell script:&lt;/p&gt;
9069
9070 &lt;pre&gt;
9071 find /sys -name modalias -print0 | xargs -0 cat | sort -u
9072 &lt;/pre&gt;
9073
9074 &lt;p&gt;The supported modalias globs for a given kernel module can be found
9075 using modinfo:&lt;/p&gt;
9076
9077 &lt;pre&gt;
9078 % /sbin/modinfo psmouse | grep alias:
9079 alias: serio:ty05pr*id*ex*
9080 alias: serio:ty01pr*id*ex*
9081 %
9082 &lt;/pre&gt;
9083
9084 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
9085
9086 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
9087 Bridge memory controller:&lt;/p&gt;
9088
9089 &lt;p&gt;&lt;blockquote&gt;
9090 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9091 &lt;/blockquote&gt;&lt;/p&gt;
9092
9093 &lt;p&gt;This represent these values:&lt;/p&gt;
9094
9095 &lt;pre&gt;
9096 v 00008086 (vendor)
9097 d 00002770 (device)
9098 sv 00001028 (subvendor)
9099 sd 000001AD (subdevice)
9100 bc 06 (bus class)
9101 sc 00 (bus subclass)
9102 i 00 (interface)
9103 &lt;/pre&gt;
9104
9105 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
9106 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
9107 0600. The 0600 class is a host bridge. Other useful bus values are
9108 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
9109
9110 &lt;p&gt;Not sure how to figure out the interface value, nor what it
9111 means.&lt;/p&gt;
9112
9113 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
9114
9115 &lt;p&gt;Some typical USB entries can look like this. This is an internal
9116 USB hub in a laptop:&lt;/p&gt;
9117
9118 &lt;p&gt;&lt;blockquote&gt;
9119 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9120 &lt;/blockquote&gt;&lt;/p&gt;
9121
9122 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
9123
9124 &lt;pre&gt;
9125 v 1D6B (device vendor)
9126 p 0001 (device product)
9127 d 0206 (bcddevice)
9128 dc 09 (device class)
9129 dsc 00 (device subclass)
9130 dp 00 (device protocol)
9131 ic 09 (interface class)
9132 isc 00 (interface subclass)
9133 ip 00 (interface protocol)
9134 &lt;/pre&gt;
9135
9136 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
9137 class is in the interface class section. For a simple USB web camera,
9138 these alias entries show up:&lt;/p&gt;
9139
9140 &lt;p&gt;&lt;blockquote&gt;
9141 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9142 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9143 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9144 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9145 &lt;/blockquote&gt;&lt;/p&gt;
9146
9147 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
9148 camera), 0101 is audio control device and 0102 is audio streaming (aka
9149 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
9150
9151 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
9152
9153 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
9154 receiver in a Thinkpad X40:&lt;/p&gt;
9155
9156 &lt;p&gt;&lt;blockquote&gt;
9157 acpi:IBM0071:PNP0511:
9158 &lt;/blockquote&gt;&lt;/p&gt;
9159
9160 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
9161
9162 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
9163
9164 &lt;p&gt;The DMI table contain lots of information about the computer case
9165 and model. This is an entry for a IBM Thinkpad X40, fetched from
9166 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
9167
9168 &lt;p&gt;&lt;blockquote&gt;
9169 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9170 &lt;/blockquote&gt;&lt;/p&gt;
9171
9172 &lt;p&gt;The values present are&lt;/p&gt;
9173
9174 &lt;pre&gt;
9175 bvn IBM (BIOS vendor)
9176 bvr 1UETB6WW(1.66) (BIOS version)
9177 bd 06/15/2005 (BIOS date)
9178 svn IBM (system vendor)
9179 pn 2371H4G (product name)
9180 pvr ThinkPadX40 (product version)
9181 rvn IBM (board vendor)
9182 rn 2371H4G (board name)
9183 rvr NotAvailable (board version)
9184 cvn IBM (chassis vendor)
9185 ct 10 (chassis type)
9186 cvr NotAvailable (chassis version)
9187 &lt;/pre&gt;
9188
9189 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
9190 found in the dmidecode source:&lt;/p&gt;
9191
9192 &lt;pre&gt;
9193 3 Desktop
9194 4 Low Profile Desktop
9195 5 Pizza Box
9196 6 Mini Tower
9197 7 Tower
9198 8 Portable
9199 9 Laptop
9200 10 Notebook
9201 11 Hand Held
9202 12 Docking Station
9203 13 All In One
9204 14 Sub Notebook
9205 15 Space-saving
9206 16 Lunch Box
9207 17 Main Server Chassis
9208 18 Expansion Chassis
9209 19 Sub Chassis
9210 20 Bus Expansion Chassis
9211 21 Peripheral Chassis
9212 22 RAID Chassis
9213 23 Rack Mount Chassis
9214 24 Sealed-case PC
9215 25 Multi-system
9216 26 CompactPCI
9217 27 AdvancedTCA
9218 28 Blade
9219 29 Blade Enclosing
9220 &lt;/pre&gt;
9221
9222 &lt;p&gt;The chassis type values are not always accurately set in the DMI
9223 table. For example my home server is a tower, but the DMI modalias
9224 claim it is a desktop.&lt;/p&gt;
9225
9226 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
9227
9228 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
9229 test machine:&lt;/p&gt;
9230
9231 &lt;p&gt;&lt;blockquote&gt;
9232 serio:ty01pr00id00ex00
9233 &lt;/blockquote&gt;&lt;/p&gt;
9234
9235 &lt;p&gt;The values present are&lt;/p&gt;
9236
9237 &lt;pre&gt;
9238 ty 01 (type)
9239 pr 00 (prototype)
9240 id 00 (id)
9241 ex 00 (extra)
9242 &lt;/pre&gt;
9243
9244 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
9245 the valid values are.&lt;/p&gt;
9246
9247 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
9248
9249 &lt;p&gt;There are heaps of other modalias subtypes according to
9250 file2alias.c. There is the rest of the list from that source: amba,
9251 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9252 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9253 vmbus, x86cpu and zorro. I did not spend time documenting all of
9254 these, as they do not seem relevant for my intended use with mapping
9255 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
9256
9257 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
9258
9259 &lt;p&gt;To check which kernel modules provide support for a given modalias,
9260 one can use the following shell script:&lt;/p&gt;
9261
9262 &lt;pre&gt;
9263 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
9264 echo &quot;$id&quot; ; \
9265 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
9266 done
9267 &lt;/pre&gt;
9268
9269 &lt;p&gt;The output can look like this (only the first few entries as the
9270 list is very long on my test machine):&lt;/p&gt;
9271
9272 &lt;pre&gt;
9273 acpi:ACPI0003:
9274 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
9275 acpi:device:
9276 FATAL: Module acpi:device: not found.
9277 acpi:IBM0068:
9278 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
9279 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
9280 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
9281 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9282 acpi:IBM0071:PNP0511:
9283 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
9284 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
9285 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
9286 [...]
9287 &lt;/pre&gt;
9288
9289 &lt;p&gt;If you want to help implementing a system to let us propose what
9290 packages to install when new hardware is plugged into a Debian
9291 machine, please send me an email or talk to me on
9292 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9293
9294 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
9295 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
9296 in /sys/ with space in them.&lt;/p&gt;
9297 </description>
9298 </item>
9299
9300 <item>
9301 <title>Moved the pymissile Debian packaging to collab-maint</title>
9302 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
9303 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
9304 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
9305 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
9306 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9307 Launcher and updated the Debian package
9308 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
9309 sure udev will fix the device permissions when it is plugged in. I
9310 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
9311 hopefully make the package be proposed by jockey in Ubuntu when a user
9312 plug in his rocket launcher. In the process I moved the source to a
9313 git repository under collab-maint, to make it easier for any DD to
9314 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
9315 is not very active, but the software still work for me even after five
9316 years of relative silence. The new git repository is not listed in
9317 the uploaded package yet, because I want to test the other changes a
9318 bit more before I upload the new version. If you want to check out
9319 the new version with a .desktop file included, visit the
9320 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
9321 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
9322 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
9323 </description>
9324 </item>
9325
9326 <item>
9327 <title>Lets make hardware dongles easier to use in Debian</title>
9328 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
9329 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
9330 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
9331 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
9332 general, is that there is a great package management system with the
9333 ability to automatically install software packages by downloading them
9334 from the distribution mirrors, but no way to get it to automatically
9335 install the packages I need to use the hardware I plug into my
9336 machine. Even if the package to use it is easily available from the
9337 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9338 suggest to automatically install the python-nxt, nbc and t2n packages
9339 I need to talk to it. When I plug in a Yubikey, it could propose the
9340 yubikey-personalization package. The information required to do this
9341 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
9342
9343 &lt;p&gt;Some years ago, I proposed to
9344 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
9345 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
9346 simple:
9347
9348 &lt;ul&gt;
9349
9350 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
9351 starting when a user log in.&lt;/li&gt;
9352
9353 &lt;li&gt;Set this program up to listen for kernel events emitted when new
9354 hardware is inserted into the computer.&lt;/li&gt;
9355
9356 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
9357 database mapping to packages, and take note of any non-installed
9358 packages.&lt;/li&gt;
9359
9360 &lt;li&gt;Show a message to the user proposing to install the discovered
9361 package, and make it easy to install it.&lt;/li&gt;
9362
9363 &lt;/ul&gt;
9364
9365 &lt;p&gt;I am not sure what the best way to implement this is, but my
9366 initial idea was to use dbus events to discover new hardware, the
9367 discover database to find packages and
9368 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
9369 packages.&lt;/p&gt;
9370
9371 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
9372 draft package is now checked into
9373 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9374 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
9375 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
9376 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9377 the relevant packages in Debian, and uploaded a new version
9378 2.2013.01.09 to unstable. I also discovered that the current
9379 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
9380 package in Debian no longer discovered any USB devices, because
9381 /proc/bus/usb/devices is no longer present. I ported it to use
9382 libusb as a fall back option to get it working. The fixed package
9383 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
9384 because of the freeze).&lt;/p&gt;
9385
9386 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
9387 desktop notification to show up (only once, the first time it is
9388 inserted):&lt;/p&gt;
9389
9390 &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;
9391
9392 &lt;p&gt;For this prototype to be really useful, some way to automatically
9393 install the proposed packages by pressing the &quot;Please install
9394 program(s)&quot; button should to be implemented.&lt;/p&gt;
9395
9396 &lt;p&gt;If this idea seem useful to you, and you want to help make it
9397 happen, please help me update the discover-data database with mappings
9398 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
9399 list the package you would like to have installed when a given
9400 hardware device is inserted into your computer, and report bugs using
9401 reportbug if it isn&#39;t. Or, if you know of a better way to provide
9402 such mapping, please let me know.&lt;/p&gt;
9403
9404 &lt;p&gt;This prototype need more work, and there are several questions that
9405 should be considered before it is ready for production use. Is dbus
9406 the correct way to detect new hardware? At the moment I look for HAL
9407 dbus events on the system bus, because that is the events I could see
9408 on my Debian Squeeze KDE desktop. Are there better events to use?
9409 How should the user be notified? Is the desktop notification
9410 mechanism the best option, or should the background daemon raise a
9411 popup instead? How should packages be installed? When should they
9412 not be installed?&lt;/p&gt;
9413
9414 &lt;p&gt;If you want to help getting such feature implemented in Debian,
9415 please send me an email. :)&lt;/p&gt;
9416 </description>
9417 </item>
9418
9419 <item>
9420 <title>New IRC channel for LEGO designers using Debian</title>
9421 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
9422 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
9423 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
9424 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
9425 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
9426 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
9427 discovered I had to build all the tools myself because none were
9428 already in Debian Squeeze. If Debian support for LEGO is something
9429 you care about, please join me on the IRC channel
9430 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
9431 irc.debian.org). There is a lot that could be done to improve the
9432 Debian support for LEGO designers. For example both CAD software
9433 and Mindstorm compilers are missing. :)&lt;/p&gt;
9434
9435 &lt;p&gt;Update 2012-01-03: A
9436 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
9437 including links to Lego related packages is now available.&lt;/p&gt;
9438 </description>
9439 </item>
9440
9441 <item>
9442 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
9443 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
9444 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
9445 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
9446 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
9447 year! I hope next year will prove to be a good year.&lt;/p&gt;
9448
9449 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
9450 decentralised &quot;currency&quot; that allow people to transfer bitcoins
9451 between each other with minimal overhead, is a very interesting
9452 experiment. And as I wrote a few days ago, the bitcoin situation in
9453 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
9454 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
9455 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
9456 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
9457 for one of the ftpmasters to approve the new bitcoin-qt package
9458 name.&lt;/p&gt;
9459
9460 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
9461 team in Debian, you can easily test the package in Debian Squeeze
9462 using the following steps to get a set of working packages:&lt;/p&gt;
9463
9464 &lt;blockquote&gt;&lt;pre&gt;
9465 git clone git://git.debian.org/git/collab-maint/bitcoin
9466 cd bitcoin
9467 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9468 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9469 &lt;/pre&gt;&lt;/blockquote&gt;
9470
9471 &lt;p&gt;You might have to install some build dependencies as well. The
9472 list of commands should give you two packages, bitcoind and
9473 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9474 client will download the complete set of bitcoin &quot;blocks&quot;, which need
9475 around 5.6 GiB of data on my machine at the moment. Make sure your
9476 ~/.bitcoin/ directory have lots of spare room if you want to download
9477 all the blocks. The client will warn if the disk is getting full, so
9478 there is not really a problem if you got too little room, but you will
9479 not be able to get all the features out of the client.&lt;/p&gt;
9480
9481 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
9482 activities, please send Bitcoin donations to my address
9483 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9484 </description>
9485 </item>
9486
9487 <item>
9488 <title>A word on bitcoin support in Debian</title>
9489 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
9490 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
9491 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
9492 <description>&lt;p&gt;It has been a while since I wrote about
9493 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
9494 peer-to-peer based crypto-currency, and the reason is simply that I
9495 have been busy elsewhere. But two days ago, I started looking at the
9496 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
9497 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
9498 is now maintained by a
9499 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
9500 people&lt;/a&gt;, and the grunt work had already been done by this team. We
9501 owe a huge thank you to all these team members. :)
9502 But I was sad to discover that the bitcoin client is missing in
9503 Wheezy. It is only available in Sid (and an outdated client from
9504 backports). The client had several RC bugs registered in BTS blocking
9505 it from entering testing. To try to help the team and improve the
9506 situation, I spent some time providing patches and triaging the bug
9507 reports. I also had a look at the bitcoin package available from Matt
9508 Corallo in a
9509 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
9510 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
9511 Debian package.&lt;/p&gt;
9512
9513 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
9514 IRC, I pushed several patches into the collab-maint git repository to
9515 improve the package. It now contains fixes for the RC issues (not from
9516 me, but fixed by Scott Howard), build rules for a Qt GUI client
9517 package, konqueror support for the bitcoin: URI and bash completion
9518 setup. As I work on Debian Squeeze, I also created
9519 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
9520 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
9521 it and try to integrate it into the git repository before uploading a
9522 new version to unstable.
9523
9524 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
9525 centralized control currently exercised in the monetary system. I
9526 find it completely unacceptable that the USA government is collecting
9527 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9528 that the major credit card companies can block legal money
9529 transactions to Wikileaks. But for bitcoin to succeed, more people
9530 need to use bitcoins, and more people need to accept bitcoins when
9531 they sell products and services. Improving the bitcoin support in
9532 Debian is a small step in the right direction, but not enough.
9533 Unfortunately the user experience when browsing the web and wanting to
9534 pay with bitcoin is still not very good. The bitcoin: URI is a step
9535 in the right direction, but need to work in most or every browser in
9536 use. Also the bitcoin-qt client is too heavy to fire up to do a
9537 quick transaction. I believe there are other clients available, but
9538 have not tested them.&lt;/p&gt;
9539
9540 &lt;p&gt;My
9541 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
9542 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
9543 I received 20.15 BTC so far on the address I provided in my blog two
9544 years ago, as can be
9545 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
9546 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
9547 donation. The blockexplorer service demonstrates quite well that
9548 bitcoin is not quite anonymous and untracked. :) I wonder if the
9549 number of users have gone up since then. If you use bitcoin and want
9550 to show your support of my activity, please send Bitcoin donations to
9551 the same address as last time,
9552 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9553 </description>
9554 </item>
9555
9556 <item>
9557 <title>Git repository for song book for Computer Scientists</title>
9558 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
9559 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
9560 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
9561 <description>&lt;p&gt;As I
9562 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
9563 this summer&lt;/a&gt;, I have created a Computer Science song book a few
9564 years ago, and today I finally found time to create a public
9565 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
9566 repository for the project&lt;/a&gt;.&lt;/p&gt;
9567
9568 &lt;p&gt;If you want to help out, please clone the source and submit patches
9569 to the HTML version. To generate the PDF and PostScript version,
9570 please use prince XML, or let me know about a useful free software
9571 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
9572
9573 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
9574 PostScript formats at
9575 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
9576 Science Songbook&lt;/a&gt;.&lt;/p&gt;
9577 </description>
9578 </item>
9579
9580 <item>
9581 <title>Gratulerer med 19-årsdagen, Debian!</title>
9582 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
9583 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
9584 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
9585 <description>&lt;p&gt;I dag fyller
9586 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
9587 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
9588 si gratulerer med dagen, Debian!&lt;/p&gt;
9589 </description>
9590 </item>
9591
9592 <item>
9593 <title>Song book for Computer Scientists</title>
9594 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
9595 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
9596 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
9597 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
9598 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
9599 collecting computer related songs for use at parties. The original
9600 version was written in LaTeX, but a few years ago I got help from
9601 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9602 while keeping the ability to create a nice book in PDF format. I have
9603 not had time to maintain the book for a while now, and guess I should
9604 put it up on some public version control repository where others can
9605 help me extend and update the book. If anyone is volunteering to help
9606 me with this, send me an email. Also let me know if there are songs
9607 missing in my book.&lt;/p&gt;
9608
9609 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
9610 me today that I really should let all my readers share the joys of
9611 singing out load about programming, computers and computer networks.
9612 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
9613 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
9614 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
9615 Computer Science Songbook&lt;/a&gt;.
9616 </description>
9617 </item>
9618
9619 <item>
9620 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
9621 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
9622 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
9623 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
9624 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
9625 around 1000 at the moment. To be able to get help from the vendors
9626 when something go wrong, we want to keep the firmware on the servers
9627 up to date. If the firmware isn&#39;t the latest and greatest, the
9628 vendors typically refuse to start debugging any problems until the
9629 firmware is upgraded. So before every reboot, we want to upgrade the
9630 firmware, and we would really like everyone handling servers at the
9631 university to do this themselves when they plan to reboot a machine.
9632 For that to happen we at the unix server admin group need to provide
9633 the tools to do so.&lt;/p&gt;
9634
9635 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9636 fetch and install the latest firmware for the servers we got. Most of
9637 our hardware are from Dell and HP, so I have focused on these servers
9638 so far. This blog post is about the Dell part.&lt;/P&gt;
9639
9640 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9641 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9642 with firmware information for all 11th generation servers, listing
9643 which firmware should be used on a given model and where on the FTP
9644 site I can find it. Using a simple perl XML parser I can then
9645 download the shell scripts Dell provides to do firmware upgrades from
9646 within Linux and reboot when all the firmware is primed and ready to
9647 be activated on the first reboot.&lt;/p&gt;
9648
9649 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9650 Are there anyone working on similar tools for firmware upgrading all
9651 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9652
9653 &lt;p&gt;&lt;pre&gt;
9654 #!/usr/bin/perl
9655 use strict;
9656 use warnings;
9657 use File::Temp qw(tempdir);
9658 BEGIN {
9659 # Install needed RHEL packages if missing
9660 my %rhelmodules = (
9661 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9662 );
9663 for my $module (keys %rhelmodules) {
9664 eval &quot;use $module;&quot;;
9665 if ($@) {
9666 my $pkg = $rhelmodules{$module};
9667 system(&quot;yum install -y $pkg&quot;);
9668 eval &quot;use $module;&quot;;
9669 }
9670 }
9671 }
9672 my $errorsto = &#39;pere@hungry.com&#39;;
9673
9674 upgrade_dell();
9675
9676 exit 0;
9677
9678 sub run_firmware_script {
9679 my ($opts, $script) = @_;
9680 unless ($script) {
9681 print STDERR &quot;fail: missing script name\n&quot;;
9682 exit 1
9683 }
9684 print STDERR &quot;Running $script\n\n&quot;;
9685
9686 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9687 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9688 } else {
9689 print STDERR &quot;fail: firmware script returned error\n&quot;;
9690 }
9691 }
9692
9693 sub run_firmware_scripts {
9694 my ($opts, @dirs) = @_;
9695 # Run firmware packages
9696 for my $dir (@dirs) {
9697 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9698 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9699 while (my $s = readdir $dh) {
9700 next if $s =~ m/^\.\.?/;
9701 run_firmware_script($opts, &quot;$dir/$s&quot;);
9702 }
9703 closedir $dh;
9704 }
9705 }
9706
9707 sub download {
9708 my $url = shift;
9709 print STDERR &quot;info: Downloading $url\n&quot;;
9710 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9711 }
9712
9713 sub upgrade_dell {
9714 my @dirs;
9715 my $product = `dmidecode -s system-product-name`;
9716 chomp $product;
9717
9718 if ($product =~ m/PowerEdge/) {
9719
9720 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9721 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9722
9723 my $tmpdir = tempdir(
9724 CLEANUP =&gt; 1
9725 );
9726 chdir($tmpdir);
9727 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9728 system(&#39;gunzip Catalog.xml.gz&#39;);
9729 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9730 # -q is quiet, disabling interactivity and reducing console output
9731 my $fwopts = &quot;-q&quot;;
9732 if (@paths) {
9733 for my $url (@paths) {
9734 fetch_dell_fw($url);
9735 }
9736 run_firmware_scripts($fwopts, $tmpdir);
9737 } else {
9738 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9739 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9740 }
9741 chdir(&#39;/&#39;);
9742 } else {
9743 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9744 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9745 }
9746 }
9747
9748 sub fetch_dell_fw {
9749 my $path = shift;
9750 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9751 download($url);
9752 }
9753
9754 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9755 # firmware packages to download from Dell. Only work for Linux
9756 # machines and 11th generation Dell servers.
9757 sub fetch_dell_fw_list {
9758 my $filename = shift;
9759
9760 my $product = `dmidecode -s system-product-name`;
9761 chomp $product;
9762 my ($mybrand, $mymodel) = split(/\s+/, $product);
9763
9764 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
9765
9766 my $xml = XMLin($filename);
9767 my @paths;
9768 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
9769 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
9770 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
9771 my $oscode;
9772 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
9773 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
9774 } else {
9775 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
9776 }
9777 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
9778 {
9779 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
9780 }
9781 }
9782 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
9783 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
9784
9785 # Drop application packages, only firmware and BIOS
9786 next if &#39;APAC&#39; eq $componenttype;
9787
9788 my $cpath = $component-&gt;{path};
9789 for my $path (@paths) {
9790 if ($cpath =~ m%/$path$%) {
9791 push(@paths, $cpath);
9792 }
9793 }
9794 }
9795 return @paths;
9796 }
9797 &lt;/pre&gt;
9798
9799 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
9800 it could work on other platforms with some tweaking. Anyone know a
9801 index like Catalog.xml is available from HP for HP servers? At the
9802 moment I maintain a similar list manually and it is quickly getting
9803 outdated.&lt;/p&gt;
9804 </description>
9805 </item>
9806
9807 <item>
9808 <title>How is booting into runlevel 1 different from single user boots?</title>
9809 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
9810 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
9811 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
9812 <description>&lt;p&gt;Wouter Verhelst have some
9813 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
9814 comments and opinions&lt;/a&gt; on my blog post on
9815 &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
9816 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
9817 &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
9818 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
9819 small piece of his comment now, and though it best to address the
9820 misunderstanding he bring forward:&lt;/p&gt;
9821
9822 &lt;p&gt;&lt;blockquote&gt;
9823 Currently, a system admin has four options: [...] boot to a
9824 single-user system (by adding &#39;single&#39; to the kernel command line;
9825 this runs rcS and rc1 scripts)
9826 &lt;/blockquote&gt;&lt;/p&gt;
9827
9828 &lt;p&gt;This make me believe Wouter believe booting into single user mode
9829 and booting into runlevel 1 is the same. I am not surprised he
9830 believe this, because it would make sense and is a quite sensible
9831 thing to believe. But because the boot in Debian is slightly broken,
9832 runlevel 1 do not work properly and it isn&#39;t the same as single user
9833 mode. I&#39;ll try to explain what is actually happing, but it is a bit
9834 hard to explain.&lt;/p&gt;
9835
9836 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
9837 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
9838 executed in single user mode is sulogin. Single user mode is a boot
9839 state &quot;between&quot; the runlevels, and when booting into single user mode,
9840 only the scripts in /etc/rcS.d/ are executed before the init process
9841 enters the single user state. When switching to runlevel 1, the state
9842 is in fact not ending in runlevel 1, but it passes through runlevel 1
9843 and end up in the single user mode (see /etc/rc1.d/S03single, which
9844 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
9845 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
9846 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9847 mode).&lt;/p&gt;
9848
9849 &lt;p&gt;This summary might make it clearer. When booting for the first
9850 time into single user mode, the following commands are executed:
9851 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
9852 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
9853 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
9854 trying to continue after visiting single user mode. Not all services
9855 are started again as they should, causing the machine to end up in an
9856 unpredicatble state. This is why Debian admins recommend rebooting
9857 after visiting single user mode.&lt;/p&gt;
9858
9859 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
9860 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
9861 to runlevel 1, the services started from /etc/rcS.d/ are not properly
9862 stopped when passing through the scripts in /etc/rc1.d/, and not
9863 started again when switching away from runlevel 1 to the runlevels
9864 2-5. I believe the problem is best fixed by moving all the scripts
9865 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
9866 functioning single user mode during boot.&lt;/p&gt;
9867
9868 &lt;p&gt;I have spent several years investigating the Debian boot system,
9869 and discovered this problem a few years ago. I suspect it originates
9870 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
9871 </description>
9872 </item>
9873
9874 <item>
9875 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
9876 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
9877 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
9878 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
9879 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
9880 are started from /etc/rcS.d/. In fact, there is a bite more of them
9881 than make sense, and this causes a few problems. What kind of
9882 problems, you might ask. There are at least two problems. The first
9883 is that it is not possible to recover a machine after switching to
9884 runlevel 1. One need to actually reboot to get the machine back to
9885 the expected state. The other is that single user boot will sometimes
9886 run into problems because some of the subsystems are activated before
9887 the root login is presented, causing problems when trying to recover a
9888 machine from a problem in that subsystem. A minor additional point is
9889 that moving more scripts out of rcS.d/ and into the other rc#.d/
9890 directories will increase the amount of scripts that can run in
9891 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
9892
9893 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
9894 scripts that _have_ to execute before the root login prompt is
9895 presented during a single user boot should go there. Everything else
9896 should go into the numeric runlevels. This means things like
9897 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9898 the numeric runlevels. Today in Debian, there are around 115 init.d
9899 scripts that are started from rcS.d/, and most of them should be moved
9900 out. Do your package have one of them? Please help us make single
9901 user and runlevel 1 better by moving it.&lt;/p&gt;
9902
9903 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
9904 etc. should still be started from rcS.d/, but there is for example no
9905 need to have the network enabled before the single user login prompt
9906 is presented.&lt;/p&gt;
9907
9908 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
9909 Debian systems working while scripts migrate and during upgrades, the
9910 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9911 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9912 and the next ones can only be moved when their dependencies have been
9913 moved first. This migration must be done sequentially while we ensure
9914 that the package system upgrade packages in the right order to keep
9915 the system state correct. This will require some coordination when it
9916 comes to network related packages, but most of the packages with
9917 scripts that should migrate do not have anything in rcS.d/ depending
9918 on them. Some packages have already been updated, like the sudo
9919 package, while others are still left to do. I wish I had time to work
9920 on this myself, but real live constrains make it unlikely that I will
9921 find time to push this forward.&lt;/p&gt;
9922 </description>
9923 </item>
9924
9925 <item>
9926 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
9927 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
9928 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
9929 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
9930 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
9931 mentioned the issues I believe should be improved in Debian for its
9932 desktop to be useful for more people. The use case for this is my
9933 parents, which are currently running Kubuntu which solve the
9934 issues.&lt;/p&gt;
9935
9936 &lt;p&gt;I suspect these four missing features are not very hard to
9937 implement. After all, they are present in Ubuntu, so if we wanted to
9938 do this in Debian we would have a source.&lt;/p&gt;
9939
9940 &lt;ol&gt;
9941
9942 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
9943 are new packages available for upgrades, a icon in the KDE status bar
9944 indicate this, and clicking on it will activate the simple upgrade
9945 tool to handle it. I have no problem guiding both of my parents
9946 through the process over the phone. If a kernel reboot is required,
9947 this too is indicated by the status bars and the upgrade tool. Last
9948 time I checked, nothing with the same features was working in KDE in
9949 Debian.&lt;/li&gt;
9950
9951 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
9952 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
9953 currently have a handler for, it will ask the user if the system
9954 should search for a package that would add support for this MIME type,
9955 and if the user say yes, the APT sources will be searched for packages
9956 advertising the MIME type in their control file (visible in the
9957 Packages file in the APT archive). If one or more packages are found,
9958 it is a simple click of the mouse to add support for the missing mime
9959 type. If the package require the user to accept some non-free
9960 license, this is explained to the user. The entire process make it
9961 more clear to the user why something do not work in the browser, and
9962 make the chances higher for the user to blame the web page authors and
9963 not the browser for any missing features.&lt;/li&gt;
9964
9965 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
9966 handlers.&lt;/strong&gt; When the media players encounter a format or codec
9967 it is not supporting, a dialog pop up asking the user if the system
9968 should search for a package that would add support for it. This
9969 happen with things like MP3, Windows Media or H.264. The selection
9970 and installation procedure is very similar to the Firefox browser
9971 plugin handling. This is as far as I know implemented using a
9972 gstreamer hook. The end result is that the user easily get access to
9973 the codecs that are present from the APT archives available, while
9974 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
9975
9976 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
9977 displaying a text/plain file in my Debian browser, it will propose to
9978 start emacs to show it. If I remember correctly, when doing the same
9979 in Kunbutu it show the file as a text file in the browser. At least I
9980 know Opera will show text files within the browser. I much prefer the
9981 latter behaviour.&lt;/li&gt;
9982
9983 &lt;/ol&gt;
9984
9985 &lt;p&gt;There are other nice features as well, like the simplified suite
9986 upgrader, but given that I am the one mostly doing the dist-upgrade,
9987 it do not matter much.&lt;/p&gt;
9988
9989 &lt;p&gt;I really hope we could get these features in place for the next
9990 Debian release. It would require the coordinated effort of several
9991 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
9992 </description>
9993 </item>
9994
9995 <item>
9996 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
9997 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
9998 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
9999 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
10000 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
10001 site is build on Debian/Squeeze, and this platform was chosen because
10002 I am most familiar with Debian (being a Debian Developer for around 10
10003 years) because it is the latest stable Debian release which should get
10004 security support for a few years.&lt;/p&gt;
10005
10006 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
10007 that are missing in Debian at the moment. It would be great if these
10008 modules were added to the Debian archive, allowing anyone to set up
10009 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
10010 in their own country using only Debian packages. The list of modules
10011 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
10012 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
10013 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
10014 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
10015 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
10016 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
10017 easier in the future.&lt;/p&gt;
10018
10019 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
10020 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
10021 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
10022 with the responsibility of tracking security problems, which I really
10023 do not have time for.&lt;/p&gt;
10024 </description>
10025 </item>
10026
10027 <item>
10028 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
10029 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
10030 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
10031 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
10032 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
10033 posts have been in Norwegian the last few weeks, so here is a short
10034 update in English.&lt;/p&gt;
10035
10036 &lt;p&gt;The kids still keep me too busy to get much free software work
10037 done, but I did manage to organise a project to get a Norwegian port
10038 of the British service
10039 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
10040 and it has been running for a month now. The entire project has been
10041 organised by me and two others. Around Christmas we gathered sponsors
10042 to fund the development work. In January I drafted a contract with
10043 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
10044 and in February the development took place. Most of it involved
10045 converting the source to use GPS coordinates instead of British
10046 easting/northing, and the resulting code should be a lot easier to get
10047 running in any country by now. The Norwegian
10048 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
10049 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
10050 source and the source for administrative borders in Norway, and
10051 support for this had to be added/fixed.&lt;/p&gt;
10052
10053 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
10054 polishing the system before we announced it March 7th. The system is
10055 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
10056 problem reports in a few weeks. Soon we hope to announce the Android
10057 and iPhone versions making it even easier to report problems with the
10058 public infrastructure.&lt;/p&gt;
10059
10060 &lt;p&gt;Perhaps something to consider for those of you in countries without
10061 such service?&lt;/p&gt;
10062 </description>
10063 </item>
10064
10065 <item>
10066 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
10067 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
10068 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
10069 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
10070 <description>&lt;p&gt;The last few days I have looked at ways to track open security
10071 issues here at my work with the University of Oslo. My idea is that
10072 it should be possible to use the information about security issues
10073 available on the Internet, and check our locally
10074 maintained/distributed software against this information. It should
10075 allow us to verify that no known security issues are forgotten. The
10076 CVE database listing vulnerabilities seem like a great central point,
10077 and by using the package lists from Debian mapped to CVEs provided by
10078 the testing security team, I believed it should be possible to figure
10079 out which security holes were present in our free software
10080 collection.&lt;/p&gt;
10081
10082 &lt;p&gt;After reading up on the topic, it became obvious that the first
10083 building block is to be able to name software packages in a unique and
10084 consistent way across data sources. I considered several ways to do
10085 this, for example coming up with my own naming scheme like using URLs
10086 to project home pages or URLs to the Freshmeat entries, or using some
10087 existing naming scheme. And it seem like I am not the first one to
10088 come across this problem, as MITRE already proposed and implemented a
10089 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
10090 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
10091 software, hardware and other platform components. The CPE ids are
10092 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
10093 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
10094 issues for any CPE name. With this in place, all I need to do is to
10095 locate the CPE id for the software packages we use at the university.
10096 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
10097 NVD entry if a CVE for the package exist).&lt;/p&gt;
10098
10099 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
10100 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
10101 check out, one could look up
10102 &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
10103 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
10104 The most recent one is
10105 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
10106 and at the bottom of the NVD page for this vulnerability the complete
10107 list of affected versions is provided.&lt;/p&gt;
10108
10109 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
10110 for offline processing of issues. Using this dump, I&#39;ve written a
10111 small script taking a list of CPEs as input and list all CVEs
10112 affecting the packages represented by these CPEs. One give it CPEs
10113 with version numbers as specified above and get a list of open
10114 security issues out.&lt;/p&gt;
10115
10116 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
10117 information need to be high. For that to happen, I believe as many as
10118 possible need to use and contribute to the NVD database. I notice
10119 RHEL is providing
10120 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
10121 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
10122 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
10123
10124 &lt;p&gt;To get an idea about the quality for free software, I spent some
10125 time making it possible to compare the CVE database from Debian with
10126 the CVE database in NVD. The result look fairly good, but there are
10127 some inconsistencies in NVD (same software package having several
10128 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10129 Debian believe are affected by a CVE). Hope to find time to improve
10130 the quality of NVD, but that require being able to get in touch with
10131 someone maintaining it. So far my three emails with questions and
10132 corrections have not seen any reply, but I hope contact can be
10133 established soon.&lt;/p&gt;
10134
10135 &lt;p&gt;An interesting application for CPEs is cross platform package
10136 mapping. It would be useful to know which packages in for example
10137 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10138 this would be trivial if all linux distributions provided CPE entries
10139 for their packages.&lt;/p&gt;
10140 </description>
10141 </item>
10142
10143 <item>
10144 <title>Which module is loaded for a given PCI and USB device?</title>
10145 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
10146 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
10147 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
10148 <description>&lt;p&gt;In the
10149 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
10150 package in Debian, there is a script to report useful information
10151 about the running hardware for use when people report missing
10152 information. One part of this script that I find very useful when
10153 debugging hardware problems, is the part mapping loaded kernel module
10154 to the PCI device it claims. It allow me to quickly see if the kernel
10155 module I expect is driving the hardware I am struggling with. To see
10156 the output, make sure discover-data is installed and run
10157 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
10158 one of my machines like this:&lt;/p&gt;
10159
10160 &lt;pre&gt;
10161 loaded modules:
10162 10de:03eb i2c_nforce2
10163 10de:03f1 ohci_hcd
10164 10de:03f2 ehci_hcd
10165 10de:03f0 snd_hda_intel
10166 10de:03ec pata_amd
10167 10de:03f6 sata_nv
10168 1022:1103 k8temp
10169 109e:036e bttv
10170 109e:0878 snd_bt87x
10171 11ab:4364 sky2
10172 &lt;/pre&gt;
10173
10174 &lt;p&gt;The code in question look like this, slightly modified for
10175 readability and to drop the output to file descriptor 3:&lt;/p&gt;
10176
10177 &lt;pre&gt;
10178 if [ -d /sys/bus/pci/devices/ ] ; then
10179 echo loaded pci modules:
10180 (
10181 cd /sys/bus/pci/devices/
10182 for address in * ; do
10183 if [ -d &quot;$address/driver/module&quot; ] ; then
10184 module=`cd $address/driver/module ; pwd -P | xargs basename`
10185 if grep -q &quot;^$module &quot; /proc/modules ; then
10186 address=$(echo $address |sed s/0000://)
10187 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
10188 echo &quot;$id $module&quot;
10189 fi
10190 fi
10191 done
10192 )
10193 echo
10194 fi
10195 &lt;/pre&gt;
10196
10197 &lt;p&gt;Similar code could be used to extract USB device module
10198 mappings:&lt;/p&gt;
10199
10200 &lt;pre&gt;
10201 if [ -d /sys/bus/usb/devices/ ] ; then
10202 echo loaded usb modules:
10203 (
10204 cd /sys/bus/usb/devices/
10205 for address in * ; do
10206 if [ -d &quot;$address/driver/module&quot; ] ; then
10207 module=`cd $address/driver/module ; pwd -P | xargs basename`
10208 if grep -q &quot;^$module &quot; /proc/modules ; then
10209 address=$(echo $address |sed s/0000://)
10210 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
10211 if [ &quot;$id&quot; ] ; then
10212 echo &quot;$id $module&quot;
10213 fi
10214 fi
10215 fi
10216 done
10217 )
10218 echo
10219 fi
10220 &lt;/pre&gt;
10221
10222 &lt;p&gt;This might perhaps be something to include in other tools as
10223 well.&lt;/p&gt;
10224 </description>
10225 </item>
10226
10227 <item>
10228 <title>How to test if a laptop is working with Linux</title>
10229 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
10230 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
10231 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
10232 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
10233 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
10234 batch of computers will work with Linux. Every year for the last few
10235 years the university have organised shared bid of a few thousand
10236 computers, and this year HP won the bid. Two different desktops and
10237 five different laptops are on the list this year. We in the UNIX
10238 group want to know which one of these computers work well with RHEL
10239 and Ubuntu, the two Linux distributions we currently handle at the
10240 university.&lt;/p&gt;
10241
10242 &lt;p&gt;My test method is simple, and I share it here to get feedback and
10243 perhaps inspire others to test hardware as well. To test, I PXE
10244 install the OS version of choice, and log in as my normal user and run
10245 a few applications and plug in selected pieces of hardware. When
10246 something fail, I make a note about this in the test matrix and move
10247 on. If I have some spare time I try to report the bug to the OS
10248 vendor, but as I only have the machines for a short time, I rarely
10249 have the time to do this for all the problems I find.&lt;/p&gt;
10250
10251 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
10252 I perform on a new model.&lt;/p&gt;
10253
10254 &lt;ul&gt;
10255
10256 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
10257 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10258 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
10259
10260 &lt;li&gt;Is X.org working? If the graphical login screen show up after
10261 installation, X.org is working.&lt;/li&gt;
10262
10263 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
10264 package mesa-utils on Ubuntu) and writing down the frames per second
10265 reported by the program.&lt;/li&gt;
10266
10267 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
10268 logging in, and if I can hear this the test is successful. If there
10269 are several audio exits on the machine, I try them all and check if
10270 the Gnome/KDE audio mixer can control where to send the sound. I
10271 normally test this by playing
10272 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
10273 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
10274
10275 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
10276 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
10277
10278 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
10279 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
10280
10281 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
10282 picture from the v4l device show up.&lt;/li&gt;
10283
10284 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10285 any bluetooth devices are discovered. In my office, I normally see a
10286 few.&lt;/li&gt;
10287
10288 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
10289 memory modules lying around, and stick them in and see if Gnome/KDE
10290 notice this.&lt;/li&gt;
10291
10292 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
10293 special button work, and if the laptop continue to work after
10294 resume.&lt;/li&gt;
10295
10296 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
10297 adjusting background light, switching on/off external video output,
10298 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10299 laptop to laptop, so I just write down which are working and which are
10300 not.&lt;/li&gt;
10301
10302 &lt;li&gt;Some laptops have smart card readers, finger print readers,
10303 acceleration sensors etc. I rarely test these, as I do not know how
10304 to quickly test if they are working or not, so I only document their
10305 existence.&lt;/li&gt;
10306
10307 &lt;/ul&gt;
10308
10309 &lt;p&gt;By now I suspect you are really curious what the test results are
10310 for the HP machines I am testing. I&#39;m not done yet, so I will report
10311 the test results later. For now I can report that HP 8100 Elite work
10312 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
10313 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
10314 can see, I have most machines left to test. One interesting
10315 observation is that Ubuntu Lucid has almost twice the frame rate than
10316 RHEL6 with glxgears. No idea why.&lt;/p&gt;
10317 </description>
10318 </item>
10319
10320 <item>
10321 <title>Some thoughts on BitCoins</title>
10322 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
10323 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
10324 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
10325 <description>&lt;p&gt;As I continue to explore
10326 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
10327 what properties the system have, and how it will be affected by laws
10328 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
10329
10330 &lt;p&gt;One interesting thing to note is that since the transactions are
10331 verified using a peer to peer network, all details about a transaction
10332 is known to everyone. This means that if a BitCoin address has been
10333 published like I did with mine in my initial post about BitCoin, it is
10334 possible for everyone to see how many BitCoins have been transfered to
10335 that address. There is even a web service to look at the details for
10336 all transactions. There I can see that my address
10337 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
10338 have received 16.06 Bitcoin, the
10339 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
10340 address of Simon Phipps have received 181.97 BitCoin and the address
10341 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
10342 of EFF have received 2447.38 BitCoins so far. Thank you to each and
10343 every one of you that donated bitcoins to support my activity. The
10344 fact that anyone can see how much money was transfered to a given
10345 address make it more obvious why the BitCoin community recommend to
10346 generate and hand out a new address for each transaction. I&#39;m told
10347 there is no way to track which addresses belong to a given person or
10348 organisation without the person or organisation revealing it
10349 themselves, as Simon, EFF and I have done.&lt;/p&gt;
10350
10351 &lt;p&gt;In Norway, and in most other countries, there are laws and
10352 regulations limiting how much money one can transfer across the border
10353 without declaring it. There are money laundering, tax and accounting
10354 laws and regulations I would expect to apply to the use of BitCoin.
10355 If the Skolelinux foundation
10356 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
10357 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
10358 normal bank transfers like EFF is doing, how should this be accounted?
10359 Given that it is impossible to know if money can cross the border or
10360 not, should everything or nothing be declared? What exchange rate
10361 should be used when calculating taxes? Would receivers have to pay
10362 income tax if the foundation were to pay Skolelinux contributors in
10363 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
10364
10365 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
10366 accepted by a lot of users. It must be possible to get easy access to
10367 the currency (as a wage or using currency exchanges), and it must be
10368 easy to spend it. At the moment BitCoin seem fairly easy to get
10369 access to, but there are very few places to spend it. I am not really
10370 a regular user of any of the vendor types currently accepting BitCoin,
10371 so I wonder when my kind of shop would start accepting BitCoins. I
10372 would like to buy electronics, travels and subway tickets, not herbs
10373 and books. :) The currency is young, and this will improve over time
10374 if it become popular, but I suspect regular banks will start to lobby
10375 to get BitCoin declared illegal if it become popular. I&#39;m sure they
10376 will claim it is helping fund terrorism and money laundering (which
10377 probably would be true, as is any currency in existence), but I
10378 believe the problems should be solved elsewhere and not by blaming
10379 currencies.&lt;/p&gt;
10380
10381 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
10382 CPU intensive process that depend on a bit of luck as well (as one is
10383 competing against all the other miners currently spending CPU cycles
10384 to see which one get the next lump of cash). The &quot;winner&quot; get 50
10385 BitCoin when this happen. Yesterday I came across the obvious way to
10386 join forces to increase ones changes of getting at least some coins,
10387 by coordinating the work on mining BitCoins across several machines
10388 and people, and sharing the result if one is lucky and get the 50
10389 BitCoins. Check out
10390 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
10391 if this sounds interesting. I have not had time to try to set up a
10392 machine to participate there yet, but have seen that running on ones
10393 own for a few days have not yield any BitCoins througth mining
10394 yet.&lt;/p&gt;
10395
10396 &lt;p&gt;Update 2010-12-15: Found an &lt;a
10397 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
10398 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
10399 it was interesting to read. The arguments presented seem to be
10400 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
10401 </description>
10402 </item>
10403
10404 <item>
10405 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
10406 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
10407 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
10408 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
10409 <description>&lt;p&gt;With this weeks lawless
10410 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
10411 attacks&lt;/a&gt; on Wikileak and
10412 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
10413 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
10414 not be trusted to handle money transactions.
10415 A blog post from
10416 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
10417 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
10418 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
10419 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
10420 some help from my friend to get it all running, and he even handed me
10421 some bitcoins to get started. I even donated a few bitcoins to Simon
10422 for helping me remember BitCoin.&lt;/p&gt;
10423
10424 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
10425 crypto-currency, decentralised and handled using peer-to-peer
10426 networks. It allows anonymous transactions and prohibits central
10427 control over the transactions, making it impossible for governments
10428 and companies alike to block donations and other transactions. The
10429 source is free software, and while the key dependency wxWidgets 2.9
10430 for the graphical user interface is missing in Debian, the command
10431 line client builds just fine. Hopefully Jonas
10432 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
10433 Debian&lt;/a&gt; soon.&lt;/p&gt;
10434
10435 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
10436 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
10437 bitcoins&lt;/a&gt; when selling services and goods, and there are even
10438 currency &quot;stock&quot; markets where the exchange rate is decided. There
10439 are not many users so far, but the concept seems promising. If you
10440 want to get started and lack a friend with any bitcoins to spare,
10441 you can even get
10442 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
10443 bitcoin at the time of writing). Use
10444 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
10445 on the current exchange rates.&lt;/p&gt;
10446
10447 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
10448 machines. If you want to support my activity, please send Bitcoin
10449 donations to the address
10450 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
10451 </description>
10452 </item>
10453
10454 <item>
10455 <title>Why isn&#39;t Debian Edu using VLC?</title>
10456 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
10457 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
10458 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
10459 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
10460 presented, and the winner among the multimedia player were VLC.
10461 Personally, I like VLC, and it is my player of choice when I first try
10462 to play a video file or stream. Only if VLC fail will I drag out
10463 gmplayer to see if it can do better. The reason is mostly the failure
10464 model and trust. When VLC fail, it normally pop up a error message
10465 reporting the problem. When mplayer fail, it normally segfault or
10466 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
10467
10468 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
10469 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10470 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
10471 plugin to play web videos seamlessly, and the VLC browser plugin is
10472 not very good. For example, it lack in-line control buttons, so there
10473 is no way for the user to pause the video. Also, when I
10474 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
10475 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
10476 failed on several video pages where mplayer based plugins worked. If
10477 the browser plugin for VLC was as good as the gecko-mediaplayer
10478 package (which uses mplayer), we would switch.&lt;/P&gt;
10479
10480 &lt;p&gt;While VLC is a good player, its user interface is slightly
10481 annoying. The most annoying feature is its inconsistent use of
10482 keyboard shortcuts. When the player is in full screen mode, its
10483 shortcuts are different from when it is playing the video in a window.
10484 For example, space only work as pause when in full screen mode. I
10485 wish it had consisten shortcuts and that space also would work when in
10486 window mode. Another nice shortcut in gmplayer is [enter] to restart
10487 the current video. It is very nice when playing short videos from the
10488 web and want to restart it when new people arrive to have a look at
10489 what is going on.&lt;/p&gt;
10490 </description>
10491 </item>
10492
10493 <item>
10494 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
10495 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
10496 <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>
10497 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
10498 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
10499 upgrade testing of the
10500 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10501 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
10502 This seem like a very good idea, so I adjusted by test scripts and
10503 can now present the updated result from today:&lt;/p&gt;
10504
10505 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10506
10507 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10508
10509 &lt;blockquote&gt;&lt;p&gt;
10510 apache2.2-bin
10511 aptdaemon
10512 baobab
10513 binfmt-support
10514 browser-plugin-gnash
10515 cheese-common
10516 cli-common
10517 cups-pk-helper
10518 dmz-cursor-theme
10519 empathy
10520 empathy-common
10521 freedesktop-sound-theme
10522 freeglut3
10523 gconf-defaults-service
10524 gdm-themes
10525 gedit-plugins
10526 geoclue
10527 geoclue-hostip
10528 geoclue-localnet
10529 geoclue-manual
10530 geoclue-yahoo
10531 gnash
10532 gnash-common
10533 gnome
10534 gnome-backgrounds
10535 gnome-cards-data
10536 gnome-codec-install
10537 gnome-core
10538 gnome-desktop-environment
10539 gnome-disk-utility
10540 gnome-screenshot
10541 gnome-search-tool
10542 gnome-session-canberra
10543 gnome-system-log
10544 gnome-themes-extras
10545 gnome-themes-more
10546 gnome-user-share
10547 gstreamer0.10-fluendo-mp3
10548 gstreamer0.10-tools
10549 gtk2-engines
10550 gtk2-engines-pixbuf
10551 gtk2-engines-smooth
10552 hamster-applet
10553 libapache2-mod-dnssd
10554 libapr1
10555 libaprutil1
10556 libaprutil1-dbd-sqlite3
10557 libaprutil1-ldap
10558 libart2.0-cil
10559 libboost-date-time1.42.0
10560 libboost-python1.42.0
10561 libboost-thread1.42.0
10562 libchamplain-0.4-0
10563 libchamplain-gtk-0.4-0
10564 libcheese-gtk18
10565 libclutter-gtk-0.10-0
10566 libcryptui0
10567 libdiscid0
10568 libelf1
10569 libepc-1.0-2
10570 libepc-common
10571 libepc-ui-1.0-2
10572 libfreerdp-plugins-standard
10573 libfreerdp0
10574 libgconf2.0-cil
10575 libgdata-common
10576 libgdata7
10577 libgdu-gtk0
10578 libgee2
10579 libgeoclue0
10580 libgexiv2-0
10581 libgif4
10582 libglade2.0-cil
10583 libglib2.0-cil
10584 libgmime2.4-cil
10585 libgnome-vfs2.0-cil
10586 libgnome2.24-cil
10587 libgnomepanel2.24-cil
10588 libgpod-common
10589 libgpod4
10590 libgtk2.0-cil
10591 libgtkglext1
10592 libgtksourceview2.0-common
10593 libmono-addins-gui0.2-cil
10594 libmono-addins0.2-cil
10595 libmono-cairo2.0-cil
10596 libmono-corlib2.0-cil
10597 libmono-i18n-west2.0-cil
10598 libmono-posix2.0-cil
10599 libmono-security2.0-cil
10600 libmono-sharpzip2.84-cil
10601 libmono-system2.0-cil
10602 libmtp8
10603 libmusicbrainz3-6
10604 libndesk-dbus-glib1.0-cil
10605 libndesk-dbus1.0-cil
10606 libopal3.6.8
10607 libpolkit-gtk-1-0
10608 libpt2.6.7
10609 libpython2.6
10610 librpm1
10611 librpmio1
10612 libsdl1.2debian
10613 libsrtp0
10614 libssh-4
10615 libtelepathy-farsight0
10616 libtelepathy-glib0
10617 libtidy-0.99-0
10618 media-player-info
10619 mesa-utils
10620 mono-2.0-gac
10621 mono-gac
10622 mono-runtime
10623 nautilus-sendto
10624 nautilus-sendto-empathy
10625 p7zip-full
10626 pkg-config
10627 python-aptdaemon
10628 python-aptdaemon-gtk
10629 python-axiom
10630 python-beautifulsoup
10631 python-bugbuddy
10632 python-clientform
10633 python-coherence
10634 python-configobj
10635 python-crypto
10636 python-cupshelpers
10637 python-elementtree
10638 python-epsilon
10639 python-evolution
10640 python-feedparser
10641 python-gdata
10642 python-gdbm
10643 python-gst0.10
10644 python-gtkglext1
10645 python-gtksourceview2
10646 python-httplib2
10647 python-louie
10648 python-mako
10649 python-markupsafe
10650 python-mechanize
10651 python-nevow
10652 python-notify
10653 python-opengl
10654 python-openssl
10655 python-pam
10656 python-pkg-resources
10657 python-pyasn1
10658 python-pysqlite2
10659 python-rdflib
10660 python-serial
10661 python-tagpy
10662 python-twisted-bin
10663 python-twisted-conch
10664 python-twisted-core
10665 python-twisted-web
10666 python-utidylib
10667 python-webkit
10668 python-xdg
10669 python-zope.interface
10670 remmina
10671 remmina-plugin-data
10672 remmina-plugin-rdp
10673 remmina-plugin-vnc
10674 rhythmbox-plugin-cdrecorder
10675 rhythmbox-plugins
10676 rpm-common
10677 rpm2cpio
10678 seahorse-plugins
10679 shotwell
10680 software-center
10681 system-config-printer-udev
10682 telepathy-gabble
10683 telepathy-mission-control-5
10684 telepathy-salut
10685 tomboy
10686 totem
10687 totem-coherence
10688 totem-mozilla
10689 totem-plugins
10690 transmission-common
10691 xdg-user-dirs
10692 xdg-user-dirs-gtk
10693 xserver-xephyr
10694 &lt;/p&gt;&lt;/blockquote&gt;
10695
10696 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10697
10698 &lt;blockquote&gt;&lt;p&gt;
10699 cheese
10700 ekiga
10701 eog
10702 epiphany-extensions
10703 evolution-exchange
10704 fast-user-switch-applet
10705 file-roller
10706 gcalctool
10707 gconf-editor
10708 gdm
10709 gedit
10710 gedit-common
10711 gnome-games
10712 gnome-games-data
10713 gnome-nettool
10714 gnome-system-tools
10715 gnome-themes
10716 gnuchess
10717 gucharmap
10718 guile-1.8-libs
10719 libavahi-ui0
10720 libdmx1
10721 libgalago3
10722 libgtk-vnc-1.0-0
10723 libgtksourceview2.0-0
10724 liblircclient0
10725 libsdl1.2debian-alsa
10726 libspeexdsp1
10727 libsvga1
10728 rhythmbox
10729 seahorse
10730 sound-juicer
10731 system-config-printer
10732 totem-common
10733 transmission-gtk
10734 vinagre
10735 vino
10736 &lt;/p&gt;&lt;/blockquote&gt;
10737
10738 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10739
10740 &lt;blockquote&gt;&lt;p&gt;
10741 gstreamer0.10-gnomevfs
10742 &lt;/p&gt;&lt;/blockquote&gt;
10743
10744 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10745
10746 &lt;blockquote&gt;&lt;p&gt;
10747 [nothing]
10748 &lt;/p&gt;&lt;/blockquote&gt;
10749
10750 &lt;p&gt;This is for KDE:&lt;/p&gt;
10751
10752 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10753
10754 &lt;blockquote&gt;&lt;p&gt;
10755 ksmserver
10756 &lt;/p&gt;&lt;/blockquote&gt;
10757
10758 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10759
10760 &lt;blockquote&gt;&lt;p&gt;
10761 kwin
10762 network-manager-kde
10763 &lt;/p&gt;&lt;/blockquote&gt;
10764
10765 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10766
10767 &lt;blockquote&gt;&lt;p&gt;
10768 arts
10769 dolphin
10770 freespacenotifier
10771 google-gadgets-gst
10772 google-gadgets-xul
10773 kappfinder
10774 kcalc
10775 kcharselect
10776 kde-core
10777 kde-plasma-desktop
10778 kde-standard
10779 kde-window-manager
10780 kdeartwork
10781 kdeartwork-emoticons
10782 kdeartwork-style
10783 kdeartwork-theme-icon
10784 kdebase
10785 kdebase-apps
10786 kdebase-workspace
10787 kdebase-workspace-bin
10788 kdebase-workspace-data
10789 kdeeject
10790 kdelibs
10791 kdeplasma-addons
10792 kdeutils
10793 kdewallpapers
10794 kdf
10795 kfloppy
10796 kgpg
10797 khelpcenter4
10798 kinfocenter
10799 konq-plugins-l10n
10800 konqueror-nsplugins
10801 kscreensaver
10802 kscreensaver-xsavers
10803 ktimer
10804 kwrite
10805 libgle3
10806 libkde4-ruby1.8
10807 libkonq5
10808 libkonq5-templates
10809 libnetpbm10
10810 libplasma-ruby
10811 libplasma-ruby1.8
10812 libqt4-ruby1.8
10813 marble-data
10814 marble-plugins
10815 netpbm
10816 nuvola-icon-theme
10817 plasma-dataengines-workspace
10818 plasma-desktop
10819 plasma-desktopthemes-artwork
10820 plasma-runners-addons
10821 plasma-scriptengine-googlegadgets
10822 plasma-scriptengine-python
10823 plasma-scriptengine-qedje
10824 plasma-scriptengine-ruby
10825 plasma-scriptengine-webkit
10826 plasma-scriptengines
10827 plasma-wallpapers-addons
10828 plasma-widget-folderview
10829 plasma-widget-networkmanagement
10830 ruby
10831 sweeper
10832 update-notifier-kde
10833 xscreensaver-data-extra
10834 xscreensaver-gl
10835 xscreensaver-gl-extra
10836 xscreensaver-screensaver-bsod
10837 &lt;/p&gt;&lt;/blockquote&gt;
10838
10839 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10840
10841 &lt;blockquote&gt;&lt;p&gt;
10842 ark
10843 google-gadgets-common
10844 google-gadgets-qt
10845 htdig
10846 kate
10847 kdebase-bin
10848 kdebase-data
10849 kdepasswd
10850 kfind
10851 klipper
10852 konq-plugins
10853 konqueror
10854 ksysguard
10855 ksysguardd
10856 libarchive1
10857 libcln6
10858 libeet1
10859 libeina-svn-06
10860 libggadget-1.0-0b
10861 libggadget-qt-1.0-0b
10862 libgps19
10863 libkdecorations4
10864 libkephal4
10865 libkonq4
10866 libkonqsidebarplugin4a
10867 libkscreensaver5
10868 libksgrd4
10869 libksignalplotter4
10870 libkunitconversion4
10871 libkwineffects1a
10872 libmarblewidget4
10873 libntrack-qt4-1
10874 libntrack0
10875 libplasma-geolocation-interface4
10876 libplasmaclock4a
10877 libplasmagenericshell4
10878 libprocesscore4a
10879 libprocessui4a
10880 libqalculate5
10881 libqedje0a
10882 libqtruby4shared2
10883 libqzion0a
10884 libruby1.8
10885 libscim8c2a
10886 libsmokekdecore4-3
10887 libsmokekdeui4-3
10888 libsmokekfile3
10889 libsmokekhtml3
10890 libsmokekio3
10891 libsmokeknewstuff2-3
10892 libsmokeknewstuff3-3
10893 libsmokekparts3
10894 libsmokektexteditor3
10895 libsmokekutils3
10896 libsmokenepomuk3
10897 libsmokephonon3
10898 libsmokeplasma3
10899 libsmokeqtcore4-3
10900 libsmokeqtdbus4-3
10901 libsmokeqtgui4-3
10902 libsmokeqtnetwork4-3
10903 libsmokeqtopengl4-3
10904 libsmokeqtscript4-3
10905 libsmokeqtsql4-3
10906 libsmokeqtsvg4-3
10907 libsmokeqttest4-3
10908 libsmokeqtuitools4-3
10909 libsmokeqtwebkit4-3
10910 libsmokeqtxml4-3
10911 libsmokesolid3
10912 libsmokesoprano3
10913 libtaskmanager4a
10914 libtidy-0.99-0
10915 libweather-ion4a
10916 libxklavier16
10917 libxxf86misc1
10918 okteta
10919 oxygencursors
10920 plasma-dataengines-addons
10921 plasma-scriptengine-superkaramba
10922 plasma-widget-lancelot
10923 plasma-widgets-addons
10924 plasma-widgets-workspace
10925 polkit-kde-1
10926 ruby1.8
10927 systemsettings
10928 update-notifier-common
10929 &lt;/p&gt;&lt;/blockquote&gt;
10930
10931 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
10932 aptitude a bit more similar, but there are still quite a lott of
10933 differences. I have no idea what packages should be installed after
10934 the upgrade, but hope those that do can have a look.&lt;/p&gt;
10935 </description>
10936 </item>
10937
10938 <item>
10939 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
10940 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
10941 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
10942 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
10943 <description>&lt;p&gt;Most of the computers in use by the
10944 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
10945 are virtual machines. And they have been Xen machines running on a
10946 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
10947 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
10948 bit harder that it could have been, because we set up the Xen virtual
10949 machines to get the virtual partitions from LVM, which as far as I
10950 know is not supported by KVM. So to migrate, we had to convert
10951 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
10952
10953 &lt;p&gt;I found
10954 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
10955 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
10956 migration. It uses qemu-img from the qemu package to make the disk
10957 image, parted to partition it, losetup and kpartx to present the disk
10958 image partions as devices, and dd to copy the data. I NFS mounted the
10959 new servers storage area on the old server to do the migration.&lt;/p&gt;
10960
10961 &lt;pre&gt;
10962 #!/bin/sh
10963
10964 # Based on
10965 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10966
10967 set -e
10968 set -x
10969
10970 if [ -z &quot;$1&quot; ] ; then
10971 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
10972 exit 1
10973 else
10974 host=&quot;$1&quot;
10975 fi
10976
10977 if [ ! -e /dev/vg_data/$host-disk ] ; then
10978 echo &quot;error: unable to find LVM volume for $host&quot;
10979 exit 1
10980 fi
10981
10982 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10983 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10984 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10985 totalsize=$(( ( $disksize + $swapsize ) ))
10986
10987 img=$host.img
10988 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
10989 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10990
10991 parted $img mklabel msdos
10992 parted $img mkpart primary linux-swap 0 $disksize
10993 parted $img mkpart primary ext2 $disksize $totalsize
10994 parted $img set 1 boot on
10995
10996 modprobe dm-mod
10997 losetup /dev/loop0 $img
10998 kpartx -a /dev/loop0
10999
11000 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
11001 fsck.ext3 -f /dev/mapper/loop0p1 || true
11002 mkswap /dev/mapper/loop0p2
11003
11004 kpartx -d /dev/loop0
11005 losetup -d /dev/loop0
11006 &lt;/pre&gt;
11007
11008 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
11009 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
11010
11011 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
11012 the new disk image attached, installed grub-pc and linux-image-686 and
11013 set up grub to boot from the disk image. After this, the KVM machines
11014 seem to work just fine.&lt;/p&gt;
11015 </description>
11016 </item>
11017
11018 <item>
11019 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
11020 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
11021 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
11022 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
11023 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
11024 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
11025 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
11026 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
11027
11028 &lt;p&gt;I still do not know what a correct migration should look like, so I
11029 report any differences between apt and aptitude and hope someone else
11030 can see if anything should be changed.&lt;/p&gt;
11031
11032 &lt;p&gt;This is for Gnome:&lt;/p&gt;
11033
11034 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11035
11036 &lt;blockquote&gt;&lt;p&gt;
11037 apache2.2-bin aptdaemon at-spi baobab binfmt-support
11038 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
11039 dmz-cursor-theme empathy empathy-common finger
11040 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
11041 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11042 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11043 gnome-cards-data gnome-codec-install gnome-core
11044 gnome-desktop-environment gnome-disk-utility gnome-screenshot
11045 gnome-search-tool gnome-session-canberra gnome-spell
11046 gnome-system-log gnome-themes-extras gnome-themes-more
11047 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
11048 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
11049 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
11050 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
11051 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
11052 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
11053 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
11054 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
11055 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
11056 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
11057 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
11058 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
11059 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
11060 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
11061 libgtk2.0-cil libgtkglext1 libgtksourceview-common
11062 libgtksourceview2.0-common libmono-addins-gui0.2-cil
11063 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
11064 libmono-i18n-west2.0-cil libmono-posix2.0-cil
11065 libmono-security2.0-cil libmono-sharpzip2.84-cil
11066 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
11067 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
11068 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
11069 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
11070 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
11071 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
11072 libxalan2-java libxerces2-java media-player-info mesa-utils
11073 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
11074 nautilus-sendto-empathy openoffice.org-writer2latex
11075 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
11076 python-aptdaemon python-aptdaemon-gtk python-axiom
11077 python-beautifulsoup python-bugbuddy python-clientform
11078 python-coherence python-configobj python-crypto python-cupshelpers
11079 python-cupsutils python-eggtrayicon python-elementtree
11080 python-epsilon python-evolution python-feedparser python-gdata
11081 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11082 python-gtksourceview2 python-httplib2 python-louie python-mako
11083 python-markupsafe python-mechanize python-nevow python-notify
11084 python-opengl python-openssl python-pam python-pkg-resources
11085 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11086 python-tagpy python-twisted-bin python-twisted-conch
11087 python-twisted-core python-twisted-web python-utidylib python-webkit
11088 python-xdg python-zope.interface remmina remmina-plugin-data
11089 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11090 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11091 software-center svgalibg1 system-config-printer-udev
11092 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
11093 totem totem-coherence totem-mozilla totem-plugins
11094 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11095 zip
11096 &lt;/p&gt;&lt;/blockquote&gt;
11097
11098 Installed using apt-get, removed with aptitude
11099
11100 &lt;blockquote&gt;&lt;p&gt;
11101 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11102 epiphany-extensions epiphany-gecko evolution-exchange
11103 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11104 gedit-common gnome-app-install gnome-games gnome-games-data
11105 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11106 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11107 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11108 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
11109 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
11110 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
11111 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
11112 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11113 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11114 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11115 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
11116 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
11117 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11118 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11119 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11120 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11121 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
11122 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
11123 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
11124 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
11125 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
11126 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11127 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11128 sound-juicer swfdec-gnome system-config-printer totem-common
11129 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11130 &lt;/p&gt;&lt;/blockquote&gt;
11131
11132 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11133
11134 &lt;blockquote&gt;&lt;p&gt;
11135 gstreamer0.10-gnomevfs
11136 &lt;/p&gt;&lt;/blockquote&gt;
11137
11138 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11139
11140 &lt;blockquote&gt;&lt;p&gt;
11141 [nothing]
11142 &lt;/p&gt;&lt;/blockquote&gt;
11143
11144 &lt;p&gt;This is for KDE:&lt;/p&gt;
11145
11146 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11147
11148 &lt;blockquote&gt;&lt;p&gt;
11149 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
11150 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11151 ghostscript-x git gnome-audio gnugo granatier gs-common
11152 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11153 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11154 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11155 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11156 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11157 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11158 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11159 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11160 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11161 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11162 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11163 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
11164 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11165 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11166 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11167 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11168 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11169 libkrossui4 libmailtools-perl libmime-tools-perl
11170 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11171 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11172 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11173 lirc luatex marble networkstatus noatun-plugins
11174 openoffice.org-writer2latex palapeli palapeli-data parley
11175 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11176 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11177 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11178 ttf-sazanami-gothic
11179 &lt;/p&gt;&lt;/blockquote&gt;
11180
11181 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11182
11183 &lt;blockquote&gt;&lt;p&gt;
11184 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11185 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11186 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11187 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11188 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11189 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11190 kitchensync kiten kjumpingcube klatin klettres klickety klines
11191 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11192 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11193 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11194 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11195 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11196 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11197 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11198 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11199 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11200 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
11201 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
11202 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11203 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
11204 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
11205 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11206 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11207 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11208 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11209 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11210 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11211 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
11212 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
11213 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11214 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11215 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11216 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11217 &lt;/p&gt;&lt;/blockquote&gt;
11218
11219 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11220
11221 &lt;blockquote&gt;&lt;p&gt;
11222 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11223 kdeartwork kdebase kdebase-apps kdebase-workspace
11224 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11225 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11226 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11227 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11228 xscreensaver-screensaver-bsod
11229 &lt;/p&gt;&lt;/blockquote&gt;
11230
11231 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11232
11233 &lt;blockquote&gt;&lt;p&gt;
11234 kdebase-bin konq-plugins konqueror
11235 &lt;/p&gt;&lt;/blockquote&gt;
11236 </description>
11237 </item>
11238
11239 <item>
11240 <title>Gnash buildbot slave and Debian kfreebsd</title>
11241 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
11242 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
11243 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
11244 <description>&lt;p&gt;Answering
11245 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
11246 call from the Gnash project&lt;/a&gt; for
11247 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
11248 current source, I have set up a virtual KVM machine on the Debian
11249 Edu/Skolelinux virtualization host to test the git source on
11250 Debian/Squeeze. I hope this can help the developers in getting new
11251 releases out more often.&lt;/p&gt;
11252
11253 &lt;p&gt;As the developers want less main-stream build platforms tested to,
11254 I have considered setting up a &lt;a
11255 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
11256 machine as well. I have also considered using the kfreebsd
11257 architecture in Debian as a file server in NUUG to get access to the 5
11258 TB zfs volume we currently use to store DV video. Because of this, I
11259 finally got around to do a test installation of Debian/Squeeze with
11260 kfreebsd. Installation went fairly smooth, thought I noticed some
11261 visual glitches in the cdebconf dialogs (black cursor left on the
11262 screen at random locations). Have not gotten very far with the
11263 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11264 fatal problem. Have to spend some more time on it to see if it is
11265 useful as a file server for NUUG. Will try to find time to set up a
11266 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
11267 </description>
11268 </item>
11269
11270 <item>
11271 <title>Debian in 3D</title>
11272 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
11273 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
11274 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
11275 <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;
11276
11277 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
11278 3D linked in from
11279 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
11280 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
11281 </description>
11282 </item>
11283
11284 <item>
11285 <title>Software updates 2010-10-24</title>
11286 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
11287 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
11288 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
11289 <description>&lt;p&gt;Some updates.&lt;/p&gt;
11290
11291 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
11292 raise money for the project is going well. The lower limit of 10
11293 signers was reached in 24 hours, and so far 13 people have signed it.
11294 More signers and more funding is most welcome, and I am really curious
11295 how far we can get before the time limit of December 24 is reached.
11296 :)&lt;/p&gt;
11297
11298 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
11299 about what appear to be a great code coverage tool capable of
11300 generating code coverage stats without any changes to the source code.
11301 It is called
11302 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
11303 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
11304 It is missing in Debian, but the git source built just fine in Squeeze
11305 after I installed libelf-dev, libdwarf-dev, pkg-config and
11306 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11307 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
11308
11309 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
11310 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
11311 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
11312 alpha test release of the Squeeze based Debian Edu /
11313 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
11314 release. Give it a try if you need a complete linux solution for your
11315 school, including central infrastructure server, workstations, thin
11316 client servers and diskless workstations. A nice touch added
11317 yesterday is RDP support on the thin client servers, for windows
11318 clients to get a Linux desktop on request.&lt;/p&gt;
11319 </description>
11320 </item>
11321
11322 <item>
11323 <title>Some notes on Flash in Debian and Debian Edu</title>
11324 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
11325 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
11326 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
11327 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
11328 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
11329 second most popular used package that is missing in Debian. The sixth
11330 most popular is flashplayer-mozilla. This is a clear indication that
11331 working flash is important for Debian users. Around 10 percent of the
11332 users submitting data to popcon.debian.org have this package
11333 installed.&lt;/p&gt;
11334
11335 &lt;p&gt;In the report written by Lars Risan in August 2008
11336&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
11337 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11338 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
11339 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
11340 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
11341 web sites require Flash to work, and lacking working Flash support in
11342 the web browser and the problems with installing it was perceived as a
11343 good reason to stay with Windows.&lt;/p&gt;
11344
11345 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
11346 said to be the retarded cousin that did not really understand
11347 everything you told him but could work fairly well. This was a
11348 comment regarding the problems Linux have with proprietary formats and
11349 non-standard web pages, and is sad because it exposes a fairly common
11350 understanding of whose fault it is if web pages that only work in for
11351 example Internet Explorer 6 fail to work on Firefox, and funny because
11352 it explain very well how annoying it is for users when Linux
11353 distributions do not work with the documents they receive or the web
11354 pages they want to visit.&lt;/p&gt;
11355
11356 &lt;p&gt;This is part of the reason why I believe it is important for Debian
11357 and Debian Edu to have a well working Flash implementation in the
11358 distribution, to get at least popular sites as Youtube and Google
11359 Video to working out of the box. For Squeeze, Debian have the chance
11360 to include the latest version of Gnash that will make this happen, as
11361 the new release 0.8.8 was published a few weeks ago and is resting in
11362 unstable. The new version work with more sites that version 0.8.7.
11363 The Gnash maintainers have asked for a freeze exception, but the
11364 release team have not had time to reply to it yet. I hope they agree
11365 with me that Flash is important for the Debian desktop users, and thus
11366 accept the new package into Squeeze.&lt;/p&gt;
11367 </description>
11368 </item>
11369
11370 <item>
11371 <title>Circular package dependencies harms apt recovery</title>
11372 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
11373 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
11374 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
11375 <description>&lt;p&gt;I discovered this while doing
11376 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
11377 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
11378 in Debian still got circular dependencies, and it is often claimed
11379 that apt and aptitude should be able to handle this just fine, but
11380 some times these dependency loops causes apt to fail.&lt;/p&gt;
11381
11382 &lt;p&gt;An example is from todays
11383 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
11384 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
11385 causes perl-modules to fail to upgrade. The cause is simple. If a
11386 package fail to unpack, then only part of packages with the circular
11387 dependency might end up being unpacked when unpacking aborts, and the
11388 ones already unpacked will fail to configure in the recovery phase
11389 because its dependencies are unavailable.&lt;/p&gt;
11390
11391 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
11392
11393 &lt;blockquote&gt;&lt;pre&gt;
11394 dpkg: dependency problems prevent configuration of perl-modules:
11395 perl-modules depends on perl (&gt;= 5.10.1-1); however:
11396 Version of perl on system is 5.10.0-19lenny2.
11397 dpkg: error processing perl-modules (--configure):
11398 dependency problems - leaving unconfigured
11399 &lt;/pre&gt;&lt;/blockquote&gt;
11400
11401 &lt;p&gt;The perl/perl-modules circular dependency is already
11402 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
11403 hopefully be solved as soon as possible, but it is not the only one,
11404 and each one of these loops in the dependency tree can cause similar
11405 failures. Of course, they only occur when there are bugs in other
11406 packages causing the unpacking to fail, but it is rather nasty when
11407 the failure of one package causes the problem to become worse because
11408 of dependency loops.&lt;/p&gt;
11409
11410 &lt;p&gt;Thanks to
11411 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
11412 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
11413 dependencies
11414 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
11415 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
11416
11417 &lt;p&gt;Todays testing also exposed a bug in
11418 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
11419 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
11420 apt-get and aptitude, the latter possibly caused by some circular
11421 dependency. Reported both to BTS to try to get someone to look at
11422 it.&lt;/p&gt;
11423 </description>
11424 </item>
11425
11426 <item>
11427 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
11428 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
11429 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
11430 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
11431 <description>&lt;p&gt;This is a
11432 &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;
11433 on my
11434 &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
11435 work&lt;/a&gt; on
11436 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
11437 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
11438
11439 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
11440 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11441 and dhcp3-server-ldap in Debian use the LDAP server. The two
11442 implementations are quite different in how they use LDAP.&lt;/p&gt;
11443
11444 To get this information, I started slapd with debugging enabled and
11445 dumped the debug output to a file to get the LDAP searches performed
11446 on a Debian Edu main-server. Here is a summary.
11447
11448 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
11449
11450 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
11451 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
11452 the web.
11453
11454 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
11455 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
11456 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
11457 reverse entries are in two different subtrees in LDAP with a structure
11458 based on the DNS names, as in tjener.intern and
11459 2.2.0.10.in-addr.arpa.&lt;/p&gt;
11460
11461 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
11462 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
11463 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
11464 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
11465 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
11466 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
11467 forward entries, it is looking for attributes named dnsttl, arecord,
11468 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11469 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11470 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11471 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11472 spfrecord and modifytimestamp. For reverse entries it is looking for
11473 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11474 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11475 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11476 ldapsearch commands could look like this:&lt;/p&gt;
11477
11478 &lt;blockquote&gt;&lt;pre&gt;
11479 ldapsearch -h ldap \
11480 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11481 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11482 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11483 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11484 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11485 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11486
11487 ldapsearch -h ldap \
11488 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11489 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
11490 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11491 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11492 srvrecord naptrrecord modifytimestamp
11493 &lt;/pre&gt;&lt;/blockquote&gt;
11494
11495 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
11496 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11497 example LDAP objects used there. In addition to these objects, the
11498 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11499 also exist.&lt;/p&gt;
11500
11501 &lt;blockquote&gt;&lt;pre&gt;
11502 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11503 objectclass: top
11504 objectclass: dnsdomain
11505 objectclass: domainrelatedobject
11506 dc: tjener
11507 arecord: 10.0.2.2
11508 associateddomain: tjener.intern
11509
11510 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11511 objectclass: top
11512 objectclass: dnsdomain2
11513 objectclass: domainrelatedobject
11514 dc: 2
11515 ptrrecord: tjener.intern
11516 associateddomain: 2.2.0.10.in-addr.arpa
11517 &lt;/pre&gt;&lt;/blockquote&gt;
11518
11519 &lt;p&gt;In strict mode, the server behaves differently. When looking for
11520 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
11521 same base as in the tree mode for a object with filter
11522 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
11523 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11524 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11525 naptrrecord and modifytimestamp. For reverse entires it also do a
11526 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
11527 and the requested attributes are associateddomain, dnsttl and
11528 modifytimestamp. In short, in strict mode the objects with ptrrecord
11529 go away, and the arecord attribute in the forward object is used
11530 instead.&lt;/p&gt;
11531
11532 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
11533 like this:&lt;/p&gt;
11534
11535 &lt;blockquote&gt;&lt;pre&gt;
11536 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11537 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11538 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11539 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11540 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11541 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11542
11543 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11544 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
11545 &lt;/pre&gt;&lt;/blockquote&gt;
11546
11547 &lt;p&gt;In addition to the forward and reverse searches , there is also a
11548 search for SOA records, which behave similar to the forward and
11549 reverse lookups.&lt;/p&gt;
11550
11551 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
11552 specify any objectclass names, and instead look for the attributes it
11553 need to generate a DNS reply. This make it able to work with any
11554 objectclass that provide the needed attributes.&lt;/p&gt;
11555
11556 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
11557 dnsdomain2 schemas. The latter is used for reverse entries like
11558 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
11559
11560 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
11561 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11562 attributes) and domainrelatedobject (for associatedDomain). The use
11563 of structural object classes make it impossible to combine these
11564 classes with the object classes used by DHCP.&lt;/p&gt;
11565
11566 &lt;p&gt;There are other schemas that could be used too, for example the
11567 dnszone structural object class used by Gosa and bind-sdb for the DNS
11568 attributes combined with the domainrelatedobject object class, but in
11569 this case some unused attributes would have to be included as well
11570 (zonename and relativedomainname).&lt;/p&gt;
11571
11572 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
11573 mode and not use any of the existing objectclasses (dnsdomain,
11574 dnsdomain2 and dnszone) when one want to combine the DNS information
11575 with DHCP information, and instead create a auxiliary object class
11576 defined something like this (using the attributes defined for
11577 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
11578
11579 &lt;blockquote&gt;&lt;pre&gt;
11580 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
11581 SUP top
11582 AUXILIARY
11583 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11584 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11585 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11586 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11587 A6Record $ DNAMERecord
11588 ))
11589 &lt;/pre&gt;&lt;/blockquote&gt;
11590
11591 &lt;p&gt;This will allow any object to become a DNS entry when combined with
11592 the domainrelatedobject object class, and allow any entity to include
11593 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
11594 developers asking for their view on this schema and if they are
11595 interested in providing such schema with PowerDNS, and I hope my
11596 message will be accepted into their mailing list soon.&lt;/p&gt;
11597
11598 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
11599
11600 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
11601 the object attributes, and then uses the attributes it want. This
11602 make it harder to figure out exactly what attributes are used, but
11603 thanks to the working example in Debian Edu I can at least get an idea
11604 what is needed without having to read the source code.&lt;/p&gt;
11605
11606 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
11607 search filter to use to locate the correct dhcpServer entity is
11608 stored. These are the relevant entries from
11609 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
11610
11611 &lt;blockquote&gt;&lt;pre&gt;
11612 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
11613 ldap-dhcp-server-cn &quot;dhcp&quot;;
11614 &lt;/pre&gt;&lt;/blockquote&gt;
11615
11616 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
11617 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
11618 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
11619 search result is this entry:&lt;/p&gt;
11620
11621 &lt;blockquote&gt;&lt;pre&gt;
11622 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11623 cn: dhcp
11624 objectClass: top
11625 objectClass: dhcpServer
11626 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11627 &lt;/pre&gt;&lt;/blockquote&gt;
11628
11629 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
11630 subtree with DHCP configuration. The DHCP configuration subtree base
11631 is located using a base scope search with base &quot;cn=DHCP
11632 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11633 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11634 The search result is this entry:&lt;/p&gt;
11635
11636 &lt;blockquote&gt;&lt;pre&gt;
11637 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11638 cn: DHCP Config
11639 objectClass: top
11640 objectClass: dhcpService
11641 objectClass: dhcpOptions
11642 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11643 dhcpStatements: ddns-update-style none
11644 dhcpStatements: authoritative
11645 dhcpOption: smtp-server code 69 = array of ip-address
11646 dhcpOption: www-server code 72 = array of ip-address
11647 dhcpOption: wpad-url code 252 = text
11648 &lt;/pre&gt;&lt;/blockquote&gt;
11649
11650 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11651 all the DHCP configuration is loaded, it is ready to receive requests.
11652 The subtree in Debian Edu contain objects with object classes
11653 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11654 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11655 and information about netmasks, dynamic range etc. Leaving out the
11656 details here because it is not relevant for the focus of my
11657 investigation, which is to see if it is possible to merge dns and dhcp
11658 related computer objects.&lt;/p&gt;
11659
11660 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11661 of the client (00:00:00:00:00:00 in this example), using a subtree
11662 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11663 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11664 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11665 like:&lt;/p&gt;
11666
11667 &lt;blockquote&gt;&lt;pre&gt;
11668 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11669 cn: hostname
11670 objectClass: top
11671 objectClass: dhcpHost
11672 dhcpHWAddress: ethernet 00:00:00:00:00:00
11673 dhcpStatements: fixed-address hostname
11674 &lt;/pre&gt;&lt;/blockquote&gt;
11675
11676 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11677 The object classes need to have fixed names, and the configuration
11678 need to be stored in a fairly specific LDAP structure. On the
11679 positive side, the invidiual dhcpHost entires can be anywhere without
11680 the DN pointed to by the dhcpServer entries. The latter should make
11681 it possible to group all host entries in a subtree next to the
11682 configuration entries, and this subtree can also be shared with the
11683 DNS server if the schema proposed above is combined with the dhcpHost
11684 structural object class.
11685
11686 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11687
11688 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11689 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11690 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11691 allowing DNS objects to be stored anywhere under the base cn specified
11692 in the configuration.&lt;/p&gt;
11693
11694 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11695 regarding which LDAP schemas to use and which LDAP structure to use.
11696 I guess one could implement ones own schema, as long as the
11697 objectclasses and attributes have the names used, but this do not
11698 really help when the DHCP subtree need to have a fairly fixed
11699 structure.&lt;/p&gt;
11700
11701 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11702 this might work for Debian Edu:&lt;/p&gt;
11703
11704 &lt;blockquote&gt;&lt;pre&gt;
11705 ou=services
11706 cn=machine-info (dhcpService) - dhcpServiceDN points here
11707 cn=dhcp (dhcpServer)
11708 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11709 cn=10.0.2.0 (dhcpSubnet)
11710 cn=group1 (dhcpGroup/dhcpOptions)
11711 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11712 cn=192.168.0.0 (dhcpSubnet)
11713 cn=group1 (dhcpGroup/dhcpOptions)
11714 ou=machines - PowerDNS base points here
11715 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11716 &lt;/pre&gt;&lt;/blockquote&gt;
11717
11718 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11719 entries to be in the dhcpGroup subtrees, the entries can be stored
11720 there instead of a common machines subtree, and the PowerDNS base
11721 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11722
11723 &lt;p&gt;The combined object under the machines subtree would look something
11724 like this:&lt;/p&gt;
11725
11726 &lt;blockquote&gt;&lt;pre&gt;
11727 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11728 dc: hostname
11729 objectClass: top
11730 objectClass: dhcpHost
11731 objectclass: domainrelatedobject
11732 objectclass: dnsDomainAux
11733 associateddomain: hostname.intern
11734 arecord: 10.11.12.13
11735 dhcpHWAddress: ethernet 00:00:00:00:00:00
11736 dhcpStatements: fixed-address hostname.intern
11737 &lt;/pre&gt;&lt;/blockquote&gt;
11738
11739 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11740 machine, as long as the required attributes are available in a
11741 auxiliary object class.&lt;/p&gt;
11742 </description>
11743 </item>
11744
11745 <item>
11746 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11747 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11748 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11749 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11750 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11751 DHCP services in Debian Edu to use the same LDAP objects for a given
11752 computer, to avoid the possibility of having a inconsistent state for
11753 a computer in LDAP (as in DHCP but no DNS entry or the other way
11754 around) and make it easier to add computers to LDAP.&lt;/p&gt;
11755
11756 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
11757 information finally found a solution that seem to work.&lt;/p&gt;
11758
11759 &lt;p&gt;The old setup required three LDAP objects for a given computer.
11760 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11761 we switch powerdns to use its strict LDAP method (ldap-method=strict
11762 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11763 merged into one while making it impossible to transfer the reverse map
11764 to a slave DNS server.&lt;/p&gt;
11765
11766 &lt;p&gt;If we also replace the object class used to get the DNS related
11767 attributes to one allowing these attributes to be combined with the
11768 dhcphost object class, we can merge the DNS and DHCP entries into one.
11769 I&#39;ve written such object class in the dnsdomainaux.schema file (need
11770 proper OIDs, but that is a minor issue), and tested the setup. It
11771 seem to work.&lt;/p&gt;
11772
11773 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
11774 for both DNS and DHCP, and even the LTSP configuration I suggested in
11775 an earlier email. The combined LDAP object will look something like
11776 this:&lt;/p&gt;
11777
11778 &lt;blockquote&gt;&lt;pre&gt;
11779 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11780 cn: hostname
11781 objectClass: dhcphost
11782 objectclass: domainrelatedobject
11783 objectclass: dnsdomainaux
11784 associateddomain: hostname.intern
11785 arecord: 10.11.12.13
11786 dhcphwaddress: ethernet 00:00:00:00:00:00
11787 dhcpstatements: fixed-address hostname
11788 ldapconfigsound: Y
11789 &lt;/pre&gt;&lt;/blockquote&gt;
11790
11791 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
11792 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11793 before asking DNS to resolve the fixed-adddress. LTSP will use
11794 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
11795
11796 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
11797 dhcphost in a different location, to allow us to put the objects
11798 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
11799 that. If I can&#39;t figure out a way to do that, we can still get rid of
11800 the hosts subtree and move all its content into the DHCP Config tree
11801 (which probably should be renamed to be more related to the new
11802 content. I suspect cn=dnsdhcp,ou=services or something like that
11803 might be a good place to put it.&lt;/p&gt;
11804
11805 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11806 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11807 </description>
11808 </item>
11809
11810 <item>
11811 <title>Idea for storing LTSP configuration in LDAP</title>
11812 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
11813 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
11814 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
11815 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
11816 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11817 clients, and that this can be used to fetch configuration from LDAP if
11818 Debian Edu choose to store configuration there.&lt;/p&gt;
11819
11820 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
11821 to get configuration from LDAP. The idea is to look up the MAC
11822 address of the client in LDAP, and look for attributes on the form
11823 ltspconfigsetting=value, and use this to export SETTING=value to the
11824 LTSP clients.&lt;/p&gt;
11825
11826 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
11827 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
11828 allowing us to store all information about a computer in one place.&lt;/p&gt;
11829
11830 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
11831 this approach. A real LDAP schema for the ltspClientAux objectclass
11832 need to be written. Comments, suggestions, etc?&lt;/p&gt;
11833
11834 &lt;blockquote&gt;&lt;pre&gt;
11835 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11836 #
11837 # Fetch LTSP client settings from LDAP based on MAC address
11838 #
11839 # Uses ethernet address as stored in the dhcpHost objectclass using
11840 # the dhcpHWAddress attribute or ethernet address stored in the
11841 # ieee802Device objectclass with the macAddress attribute.
11842 #
11843 # This module is written to be schema agnostic, and only depend on the
11844 # existence of attribute names.
11845 #
11846 # The LTSP configuration variables are saved directly using a
11847 # ltspConfig prefix and uppercasing the rest of the attribute name.
11848 # To set the SERVER variable, set the ltspConfigServer attribute.
11849 #
11850 # Some LDAP schema should be created with all the relevant
11851 # configuration settings. Something like this should work:
11852 #
11853 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
11854 # SUP top
11855 # AUXILIARY
11856 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11857
11858 LDAPSERVER=$(debian-edu-ldapserver)
11859 if [ &quot;$LDAPSERVER&quot; ] ; then
11860 LDAPBASE=$(debian-edu-ldapserver -b)
11861 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
11862 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
11863 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
11864 grep &#39;^ltspConfig&#39; | while read attr value ; do
11865 # Remove prefix and convert to upper case
11866 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
11867 # bass value on to clients
11868 eval &quot;$attr=$value; export $attr&quot;
11869 done
11870 done
11871 fi
11872 &lt;/pre&gt;&lt;/blockquote&gt;
11873
11874 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
11875 the while block might end up in a subshell causing the variables set
11876 there to not show up in ltsp-config, but if that is the case I am sure
11877 the code can be restructured to make sure the variables are passed on.
11878 I expect that can be solved with some testing. :)&lt;/p&gt;
11879
11880 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11881 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11882
11883 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
11884 configuration in LDAP that was created around year 2000 by
11885 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
11886 Xperience, Inc., 2000&lt;/a&gt;. I found its
11887 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
11888 personal home page over at redhat.com.&lt;/p&gt;
11889 </description>
11890 </item>
11891
11892 <item>
11893 <title>jXplorer, a very nice LDAP GUI</title>
11894 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
11895 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
11896 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
11897 <description>&lt;p&gt;Since
11898 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
11899 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
11900 LDAP GUI that is even better than luma. The java application
11901 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
11902 moving LDAP objects and subtrees using drag-and-drop, and can
11903 authenticate using Kerberos. I have only tested the Kerberos
11904 authentication, but do not have a LDAP setup allowing me to rewrite
11905 LDAP with my test user yet. It is
11906 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
11907 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
11908 have with it is how it handle errors. If something go wrong, its
11909 non-intuitive behaviour require me to go through some query work list
11910 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
11911 </description>
11912 </item>
11913
11914 <item>
11915 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
11916 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
11917 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
11918 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
11919 <description>&lt;p&gt;Here is a short update on my &lt;a
11920 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
11921 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
11922 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
11923 not reporting the status for KDE, because the upgrade crashes when
11924 aptitude try because of missing conflicts
11925 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
11926 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
11927
11928 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
11929 complete list of the installed packages. Based on this I see these
11930 differences when I did a test run today. As usual, I do not really
11931 know what the correct set of packages would be, but thought it best to
11932 publish the difference.&lt;/p&gt;
11933
11934 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11935
11936 &lt;blockquote&gt;&lt;p&gt;
11937 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
11938 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
11939 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11940 libgtksourceview-common libpt-1.10.10-plugins-alsa
11941 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11942 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11943 python-4suite-xml python-eggtrayicon python-gtkhtml2
11944 python-gtkmozembed svgalibg1 xserver-xephyr zip
11945 &lt;/p&gt;&lt;/blockquote&gt;
11946
11947 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11948
11949 &lt;blockquote&gt;&lt;p&gt;
11950 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11951 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11952 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
11953 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
11954 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
11955 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
11956 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11957 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11958 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11959 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
11960 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
11961 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
11962 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11963 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
11964 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11965 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
11966 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
11967 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11968 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11969 mysql-common swfdec-gnome totem-gstreamer wodim
11970 &lt;/p&gt;&lt;/blockquote&gt;
11971
11972 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11973
11974 &lt;blockquote&gt;&lt;p&gt;
11975 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11976 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11977 xserver-xorg-input-all xserver-xorg-input-evdev
11978 xserver-xorg-input-kbd xserver-xorg-input-mouse
11979 xserver-xorg-input-synaptics xserver-xorg-video-all
11980 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11981 xserver-xorg-video-chips xserver-xorg-video-cirrus
11982 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11983 xserver-xorg-video-glint xserver-xorg-video-i128
11984 xserver-xorg-video-i740 xserver-xorg-video-mach64
11985 xserver-xorg-video-mga xserver-xorg-video-neomagic
11986 xserver-xorg-video-nouveau xserver-xorg-video-nv
11987 xserver-xorg-video-r128 xserver-xorg-video-radeon
11988 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11989 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11990 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11991 xserver-xorg-video-sis xserver-xorg-video-sisusb
11992 xserver-xorg-video-tdfx xserver-xorg-video-tga
11993 xserver-xorg-video-trident xserver-xorg-video-tseng
11994 xserver-xorg-video-vesa xserver-xorg-video-vmware
11995 xserver-xorg-video-voodoo
11996 &lt;/p&gt;&lt;/blockquote&gt;
11997
11998 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11999
12000 &lt;blockquote&gt;&lt;p&gt;
12001 deskbar-applet xserver-xorg xserver-xorg-core
12002 xserver-xorg-input-wacom xserver-xorg-video-intel
12003 xserver-xorg-video-openchrome
12004 &lt;/p&gt;&lt;/blockquote&gt;
12005
12006 &lt;p&gt;I was told on IRC that the xorg-xserver package was
12007 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
12008 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
12009 No idea when it hits Squeeze, but when it does I hope it will reduce
12010 the difference somewhat.
12011 </description>
12012 </item>
12013
12014 <item>
12015 <title>LUMA, a very nice LDAP GUI</title>
12016 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
12017 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
12018 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
12019 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
12020 directory in Debian Edu, and in the process I started to miss a GUI
12021 tool to browse the LDAP tree. The only one I was able to find in
12022 Debian/Squeeze and Lenny is
12023 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
12024 be a great tool to get a overview of the current LDAP directory
12025 populated by default in Skolelinux. Thanks to it, I have been able to
12026 find empty and obsolete subtrees, misplaced objects and duplicate
12027 objects. It will be installed by default in Debian/Squeeze. If you
12028 are working with LDAP, give it a go. :)&lt;/p&gt;
12029
12030 &lt;p&gt;I did notice one problem with it I have not had time to report to
12031 the BTS yet. There is no .desktop file in the package, so the tool do
12032 not show up in the Gnome and KDE menus, but only deep down in in the
12033 Debian submenu in KDE. I hope that can be fixed before Squeeze is
12034 released.&lt;/p&gt;
12035
12036 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
12037 like to move objects and remove subtrees directly in the GUI, but have
12038 not found a way to do that with LUMA yet. So in the mean time, I use
12039 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
12040
12041 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
12042 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12043
12044 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
12045 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
12046 useful GUI alternative. It seem like a good tool, but is unmaintained
12047 in Debian and got a RC bug keeping it out of Squeeze. Unless that
12048 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
12049 </description>
12050 </item>
12051
12052 <item>
12053 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
12054 <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>
12055 <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>
12056 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
12057 <description>&lt;p&gt;A while back, I
12058 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
12059 about the fact&lt;/a&gt; that it is not possible with the provided schemas
12060 for storing DNS and DHCP information in LDAP to combine the two sets
12061 of information into one LDAP object representing a computer.&lt;/p&gt;
12062
12063 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
12064 the dhcpHost object class auxiliary, to allow it to be combined with
12065 the dNSDomain object class, and thus forming one object for one
12066 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
12067
12068 &lt;p&gt;If I understand this correctly, it is not safe to do this change
12069 without also changing the assigned number for the object class, and I
12070 do not know enough about LDAP schema design to do that properly for
12071 Debian Edu.&lt;/p&gt;
12072
12073 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
12074 the
12075 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
12076 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
12077 available today from IETF.&lt;/p&gt;
12078
12079 &lt;pre&gt;
12080 --- dhcp.schema (revision 65192)
12081 +++ dhcp.schema (working copy)
12082 @@ -376,7 +376,7 @@
12083 objectclass ( 2.16.840.1.113719.1.203.6.6
12084 NAME &#39;dhcpHost&#39;
12085 DESC &#39;This represents information about a particular client&#39;
12086 - SUP top
12087 + SUP top AUXILIARY
12088 MUST cn
12089 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12090 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
12091 &lt;/pre&gt;
12092
12093 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
12094 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12095 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
12096
12097 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12098 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12099 </description>
12100 </item>
12101
12102 <item>
12103 <title>Calling tasksel like the installer, while still getting useful output</title>
12104 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
12105 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
12106 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
12107 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
12108 installs packages during the normal debian-installer run. Until now,
12109 I have ended up letting tasksel do the work, with the annoying problem
12110 of not getting any feedback at all when something fails (like a
12111 conffile question from dpkg or a download that fails), using code like
12112 this:
12113
12114 &lt;blockquote&gt;&lt;pre&gt;
12115 export DEBIAN_FRONTEND=noninteractive
12116 tasksel --new-install
12117 &lt;/pre&gt;&lt;/blockquote&gt;
12118
12119 This would invoke tasksel, let its automatic task selection pick the
12120 tasks to install, and continue to install the requested tasks without
12121 any output what so ever.
12122
12123 Recently I revisited this problem while working on the automatic
12124 package upgrade testing, because tasksel would some times hang without
12125 any useful feedback, and I want to see what is going on when it
12126 happen. Then it occured to me, I can parse the output from tasksel
12127 when asked to run in test mode, and use that aptitude command line
12128 printed by tasksel then to simulate the tasksel run. I ended up using
12129 code like this:
12130
12131 &lt;blockquote&gt;&lt;pre&gt;
12132 export DEBIAN_FRONTEND=noninteractive
12133 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
12134 $cmd
12135 &lt;/pre&gt;&lt;/blockquote&gt;
12136
12137 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
12138 --without-recommends -o APT::Install-Recommends=no -y install
12139 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12140 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
12141 laptop task and all packages with priority standard , required and
12142 important, just like tasksel would have done it during
12143 installation.&lt;/p&gt;
12144
12145 &lt;p&gt;A better approach is probably to extend tasksel to be able to
12146 install packages without using debconf-apt-progress, for use cases
12147 like this.&lt;/p&gt;
12148 </description>
12149 </item>
12150
12151 <item>
12152 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
12153 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
12154 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
12155 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
12156 <description>&lt;p&gt;My
12157 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
12158 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
12159 finally made the upgrade logs available from
12160 &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;.
12161 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12162 apt and aptitude, and found their differences interesting. This time
12163 I will only focus on their removal plans.&lt;/p&gt;
12164
12165 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
12166 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
12167 surprising part is that it want to remove xorg and all
12168 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12169 sure why. When asking aptitude to do the same, it want to remove 129
12170 packages, but most of them are library packages I suspect are no
12171 longer needed. Both of them want to remove bluetooth packages, which
12172 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
12173
12174 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
12175 which seem like a bad idea and xorg the same way as with Gnome. Asking
12176 aptitude for the same, it wants to remove 192 packages, none which are
12177 too surprising.&lt;/p&gt;
12178
12179 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
12180 and avoided, and perhaps others as well. Here are the complete list
12181 of planned removals. The complete logs is available from the URL
12182 above. Note if you want to repeat these tests, that the upgrade test
12183 for kde+apt-get hung in the tasksel setup because of dpkg asking
12184 conffile questions. No idea why. I worked around it by using
12185 &#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
12186 continue.&lt;/p&gt;
12187
12188 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
12189 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
12190 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12191 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
12192 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12193 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12194 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12195 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12196 xserver-xorg-input-kbd xserver-xorg-input-mouse
12197 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12198 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12199 xserver-xorg-video-ati xserver-xorg-video-chips
12200 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12201 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12202 xserver-xorg-video-glint xserver-xorg-video-i128
12203 xserver-xorg-video-i740 xserver-xorg-video-imstt
12204 xserver-xorg-video-intel xserver-xorg-video-mach64
12205 xserver-xorg-video-mga xserver-xorg-video-neomagic
12206 xserver-xorg-video-nsc xserver-xorg-video-nv
12207 xserver-xorg-video-openchrome xserver-xorg-video-r128
12208 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12209 xserver-xorg-video-rendition xserver-xorg-video-s3
12210 xserver-xorg-video-s3virge xserver-xorg-video-savage
12211 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12212 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12213 xserver-xorg-video-tga xserver-xorg-video-trident
12214 xserver-xorg-video-tseng xserver-xorg-video-v4l
12215 xserver-xorg-video-vesa xserver-xorg-video-vga
12216 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
12217 xulrunner-1.9-gnome-support&lt;/p&gt;
12218
12219 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
12220
12221 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
12222 djvulibre-desktop finger gnome-app-install gnome-mount
12223 gnome-network-admin gnome-spell gnome-vfs-obexftp
12224 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12225 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12226 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12227 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
12228 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
12229 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
12230 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
12231 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
12232 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
12233 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
12234 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
12235 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
12236 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12237 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
12238 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
12239 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
12240 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
12241 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
12242 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12243 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12244 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12245 openoffice.org-writer2latex openssl-blacklist p7zip
12246 python-4suite-xml python-eggtrayicon python-gnome2-desktop
12247 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12248 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12249 swfdec-mozilla totem-gstreamer update-manager wodim
12250 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12251 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12252 zip&lt;/p&gt;
12253
12254 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
12255
12256 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12257 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12258 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12259 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12260 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12261 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12262 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12263 xserver-xorg-input-kbd xserver-xorg-input-mouse
12264 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12265 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12266 xserver-xorg-video-ati xserver-xorg-video-chips
12267 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12268 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12269 xserver-xorg-video-glint xserver-xorg-video-i128
12270 xserver-xorg-video-i740 xserver-xorg-video-imstt
12271 xserver-xorg-video-intel xserver-xorg-video-mach64
12272 xserver-xorg-video-mga xserver-xorg-video-neomagic
12273 xserver-xorg-video-nsc xserver-xorg-video-nv
12274 xserver-xorg-video-openchrome xserver-xorg-video-r128
12275 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12276 xserver-xorg-video-rendition xserver-xorg-video-s3
12277 xserver-xorg-video-s3virge xserver-xorg-video-savage
12278 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12279 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12280 xserver-xorg-video-tga xserver-xorg-video-trident
12281 xserver-xorg-video-tseng xserver-xorg-video-v4l
12282 xserver-xorg-video-vesa xserver-xorg-video-vga
12283 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
12284
12285 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
12286 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
12287 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12288 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12289 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12290 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12291 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12292 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12293 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12294 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12295 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12296 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12297 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12298 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12299 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12300 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12301 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12302 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12303 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12304 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
12305 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12306 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12307 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
12308 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12309 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12310 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12311 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12312 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12313 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
12314 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
12315 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12316 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12317 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12318 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12319 texlive-common texlive-doc-base texlive-fonts-recommended
12320 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12321 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12322 xulrunner-1.9&lt;/p&gt;
12323
12324 </description>
12325 </item>
12326
12327 <item>
12328 <title>Automatic upgrade testing from Lenny to Squeeze</title>
12329 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
12330 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
12331 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
12332 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
12333 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12334 have been discovered and reported in the process
12335 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
12336 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
12337 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
12338 kdebase-workspace-data), and to get a more regular testing going on, I
12339 am working on a script to automate the test.&lt;/p&gt;
12340
12341 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
12342 Gnome or KDE desktop installation inside the chroot before upgrading
12343 it. To ensure no services are started in the chroot, a policy-rc.d
12344 script is inserted. To make sure tasksel believe it is to install a
12345 desktop on a laptop, the tasksel tests are replaced in the chroot
12346 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
12347
12348 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12349 currently always fail because udev refuses to upgrade with the kernel
12350 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12351 is created. The bug report
12352 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
12353 this problem do not trigger in a chroot, but I touch the file anyway
12354 to make sure the upgrade go well. Testing on virtual and real
12355 hardware have failed me because of udev so far, and creating this file
12356 do the trick in such settings anyway. This is a
12357 &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
12358 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
12359 maintainer because he lack the resources to rewrite udev to keep
12360 working with old kernels or something like that. I really wish the
12361 udev upstream would keep udev backwards compatible, to avoid such
12362 upgrade problem, but given that they fail to do so, I guess
12363 documenting the way out of this mess is the best option we got for
12364 Debian Squeeze.&lt;/p&gt;
12365
12366 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
12367 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
12368 trick:&lt;/p&gt;
12369
12370 &lt;blockquote&gt;&lt;pre&gt;
12371 #!/bin/sh
12372 set -ex
12373
12374 if [ &quot;$1&quot; ] ; then
12375 desktop=$1
12376 else
12377 desktop=gnome
12378 fi
12379
12380 from=lenny
12381 to=squeeze
12382
12383 exec &amp;lt; /dev/null
12384 unset LANG
12385 mirror=http://ftp.skolelinux.org/debian
12386 tmpdir=chroot-$from-upgrade-$to-$desktop
12387 fuser -mv .
12388 debootstrap $from $tmpdir $mirror
12389 chroot $tmpdir aptitude update
12390 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
12391 #!/bin/sh
12392 exit 101
12393 EOF
12394 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12395 exit_cleanup() {
12396 umount $tmpdir/proc
12397 }
12398 mount -t proc proc $tmpdir/proc
12399 # Make sure proc is unmounted also on failure
12400 trap exit_cleanup EXIT INT
12401
12402 chroot $tmpdir aptitude -y install debconf-utils
12403
12404 # Make sure tasksel autoselection trigger. It need the test scripts
12405 # to return the correct answers.
12406 echo tasksel tasksel/desktop multiselect $desktop | \
12407 chroot $tmpdir debconf-set-selections
12408
12409 # Include the desktop and laptop task
12410 for test in desktop laptop ; do
12411 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
12412 #!/bin/sh
12413 exit 2
12414 EOF
12415 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12416 done
12417
12418 DEBIAN_FRONTEND=noninteractive
12419 DEBIAN_PRIORITY=critical
12420 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12421 chroot $tmpdir tasksel --new-install
12422
12423 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
12424 chroot $tmpdir aptitude update
12425 touch $tmpdir/etc/udev/kernel-upgrade
12426 chroot $tmpdir aptitude -y dist-upgrade
12427 fuser -mv
12428 &lt;/pre&gt;&lt;/blockquote&gt;
12429
12430 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
12431 with aptitude, but I have not had time to look at how they behave
12432 differently so far. I hope to get a cron job running to do the test
12433 regularly and post the result on the web. The Gnome upgrade currently
12434 work, while the KDE upgrade fail because of the bug in
12435 kdebase-workspace-data&lt;/p&gt;
12436
12437 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
12438 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
12439 post, so I will refrain from trying. I can report that for Gnome,
12440 aptitude report 760 packages upgraded, 448 newly installed, 129 to
12441 remove and 1 not upgraded and 1024MB need to be downloaded while for
12442 KDE the same numbers are 702 packages upgraded, 507 newly installed,
12443 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
12444
12445 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
12446 is able to migrate to dependency based boot sequencing and parallel
12447 booting without a hitch. Was unsure if there were still bugs with
12448 packages failing to clean up their obsolete init.d script during
12449 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12450 packages.&lt;/p&gt;
12451 </description>
12452 </item>
12453
12454 <item>
12455 <title>Upstart or sysvinit - as init.d scripts see it</title>
12456 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
12457 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
12458 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
12459 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
12460 scripts to migrate (some of) their operations to upstart job while
12461 keeping the init.d for hurd and kfreebsd. The packages with such
12462 needs will need a way to get their init.d scripts to behave
12463 differently when used with sysvinit and with upstart. Because of
12464 this, I had a look at the environment variables set when a init.d
12465 script is running under upstart, and when it is not.&lt;/p&gt;
12466
12467 &lt;p&gt;With upstart, I notice these environment variables are set when a
12468 script is started from rcS.d/ (ignoring some irrelevant ones like
12469 COLUMNS):&lt;/p&gt;
12470
12471 &lt;blockquote&gt;&lt;pre&gt;
12472 DEFAULT_RUNLEVEL=2
12473 previous=N
12474 PREVLEVEL=
12475 RUNLEVEL=
12476 runlevel=S
12477 UPSTART_EVENTS=startup
12478 UPSTART_INSTANCE=
12479 UPSTART_JOB=rc-sysinit
12480 &lt;/pre&gt;&lt;/blockquote&gt;
12481
12482 &lt;p&gt;With sysvinit, these environment variables are set for the same
12483 script.&lt;/p&gt;
12484
12485 &lt;blockquote&gt;&lt;pre&gt;
12486 INIT_VERSION=sysvinit-2.88
12487 previous=N
12488 PREVLEVEL=N
12489 RUNLEVEL=S
12490 runlevel=S
12491 &lt;/pre&gt;&lt;/blockquote&gt;
12492
12493 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
12494 sysvinit are not set by upstart. Not sure if it is intentional or not
12495 to not be compatible with sysvinit in this regard.&lt;/p&gt;
12496
12497 &lt;p&gt;For scripts needing to behave differently when upstart is used,
12498 looking for the UPSTART_JOB environment variable seem to be a good
12499 choice.&lt;/p&gt;
12500 </description>
12501 </item>
12502
12503 <item>
12504 <title>A manual for standards wars...</title>
12505 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
12506 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
12507 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
12508 <description>&lt;p&gt;Via the
12509 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
12510 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
12511 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
12512 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
12513 following the standards wars of today.&lt;/p&gt;
12514 </description>
12515 </item>
12516
12517 <item>
12518 <title>Sitesummary tip: Listing computer hardware models used at site</title>
12519 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
12520 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
12521 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
12522 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
12523 to get a list of the machine types in use thanks to the DMI
12524 information extracted from each machine. The script to do so is
12525 included in the sitesummary package, and here is example output from
12526 the Skolelinux build servers:&lt;/p&gt;
12527
12528 &lt;blockquote&gt;&lt;pre&gt;
12529 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12530 vendor count
12531 Dell Computer Corporation 1
12532 PowerEdge 1750 1
12533 IBM 1
12534 eserver xSeries 345 -[8670M1X]- 1
12535 Intel 2
12536 [no-dmi-info] 3
12537 maintainer:~#
12538 &lt;/pre&gt;&lt;/blockquote&gt;
12539
12540 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
12541 provided in each machine. Here there are Intel machines without model
12542 information listed with Intel as vendor and no model, and virtual Xen
12543 machines listed as [no-dmi-info]. One can add -l as a command line
12544 option to list the individual machines.&lt;/p&gt;
12545
12546 &lt;p&gt;A larger list is
12547 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
12548 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
12549 provide the basic sitesummary report publicly. In their report there
12550 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
12551 their machines, and as sitesummary is available in both distributions,
12552 it is trivial to get all of them to report to the same central
12553 collector.&lt;/p&gt;
12554 </description>
12555 </item>
12556
12557 <item>
12558 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
12559 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
12560 <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>
12561 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
12562 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
12563 start at boot when an NVidia video card is used is handled. The
12564 problem seem to be that the nvidia X.org driver uses a long time to
12565 initialize, and this duration is longer than kdm is configured to
12566 wait.&lt;/p&gt;
12567
12568 &lt;p&gt;I came across two bugs related to this issue,
12569 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
12570 against initscripts and passed on to nvidia-glx when it became obvious
12571 that the nvidia drivers were involved, and
12572 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
12573 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
12574
12575 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
12576 problem nvidia video card owners experience and make sure the Debian
12577 distribution work out of the box for these users. The nvidia driver
12578 maintainers expect kdm to be set up to wait longer, while kdm expect
12579 the nvidia driver maintainers to fix the driver to start faster, and
12580 while they wait for each other I guess the users end up switching to a
12581 distribution that work for them. I have no idea what the solution is,
12582 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
12583
12584 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
12585 </description>
12586 </item>
12587
12588 <item>
12589 <title>Parallellized boot seem to hold up well in Debian/testing</title>
12590 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
12591 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
12592 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
12593 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
12594 The feature seem to hold up pretty well, but three fairly serious
12595 issues are known and should be solved:
12596
12597 &lt;p&gt;&lt;ul&gt;
12598
12599 &lt;li&gt;The wicd package seen to
12600 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
12601 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
12602 parallel booting is enabled. No idea why, but the wicd maintainer
12603 seem to be on the case.&lt;/li&gt;
12604
12605 &lt;li&gt;The nvidia X driver seem to
12606 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
12607 triggered more easily when parallel booting is in effect. The
12608 maintainer is on the case.&lt;/li&gt;
12609
12610 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
12611 sequencing (the shutdown is broken) when old file-rc users
12612 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
12613 sysv-rc. One way to solve it would be for file-rc to create
12614 /etc/init.d/.legacy-bootordering, and another is to try to make
12615 sysv-rc more robust. Will investigate some more and probably upload a
12616 workaround in sysv-rc to help those trying to move from file-rc to
12617 sysv-rc get a working shutdown.&lt;/li&gt;
12618
12619 &lt;/ul&gt;&lt;/p&gt;
12620
12621 &lt;p&gt;All in all not many surprising issues, and all of them seem
12622 solvable before Squeeze is released. In addition to these there are
12623 some packages with bugs in their dependencies and run level settings,
12624 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
12625
12626 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12627 the BTS, please usertag the report to get it to show up at
12628 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12629 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12630
12631 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12632 </description>
12633 </item>
12634
12635 <item>
12636 <title>More flexible firmware handling in debian-installer</title>
12637 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12638 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12639 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12640 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12641 found time today to return to the project. Having to spend less time
12642 working dependency based boot in debian, as it is almost complete now,
12643 definitely helped freeing some time.&lt;/p&gt;
12644
12645 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12646 include some firmware packages on the Debian Edu CDs, those needed to
12647 get disk and network controllers working. Without having these
12648 firmware packages available during installation, it is impossible to
12649 install Debian Edu on the given machine, and because our target group
12650 are non-technical people, asking them to provide firmware packages on
12651 an external medium is a support pain. Initially, I expected it to be
12652 enough to include the firmware packages on the CD to get
12653 debian-installer to find and use them. This proved to be wrong.
12654 Next, I hoped it was enough to symlink the relevant firmware packages
12655 to some useful location on the CD (tried /cdrom/ and
12656 /cdrom/firmware/). This also proved to not work, and at this point I
12657 found time to look at the debian-installer code to figure out what was
12658 going to work.&lt;/p&gt;
12659
12660 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12661 look revealed that it would only look for firmware packages outside
12662 the installation media, so the CD was never checked for firmware
12663 packages. It would only check USB sticks, floppies and other
12664 &quot;external&quot; media devices. Today I changed it to also look in the
12665 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12666 solve the problem I ran into with Debian edu. I also changed it to
12667 look in /firmware/, to make sure the installer also find firmware
12668 provided in the initrd when booting the installer via PXE, to allow us
12669 to provide the same feature in the PXE setup included in Debian
12670 Edu.&lt;/p&gt;
12671
12672 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12673 activated without asking if the license is accepted, I extended
12674 hw-detect to look for preinst scripts in the firmware packages, and
12675 run these before activating the firmware during installation. The
12676 license question is asked using debconf in the preinst, so this should
12677 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12678
12679 &lt;p&gt;If you want to discuss the details of these features, please
12680 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12681 </description>
12682 </item>
12683
12684 <item>
12685 <title>Parallellized boot is now the default in Debian/unstable</title>
12686 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12687 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12688 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12689 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12690 Debian/unstable for machines using dependency based boot sequencing.
12691 Apparently the testing of concurrent booting has been wider than
12692 expected, if I am to believe the
12693 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12694 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12695 with the feature this weekend, to give us some time to detect any
12696 remaining problems before Squeeze is frozen. If serious problems are
12697 detected, it is simple to change the default back to sequential boot.
12698 The upload of the new sysvinit package also activate a new upstream
12699 version.&lt;/p&gt;
12700
12701 More information about
12702 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12703 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12704 currently possible to disable parallel booting when one run into
12705 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12706
12707 &lt;blockquote&gt;&lt;pre&gt;
12708 CONCURRENCY=none
12709 &lt;/pre&gt;&lt;/blockquote&gt;
12710
12711 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12712 the BTS, please usertag the report to get it to show up at
12713 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12714 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12715 </description>
12716 </item>
12717
12718 <item>
12719 <title>Sitesummary tip: Listing MAC address of all clients</title>
12720 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12721 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12722 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12723 <description>&lt;p&gt;In the recent Debian Edu versions, the
12724 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12725 system&lt;/a&gt; is used to keep track of the machines in the school
12726 network. Each machine will automatically report its status to the
12727 central server after boot and once per night. The network setup is
12728 also reported, and using this information it is possible to get the
12729 MAC address of all network interfaces in the machines. This is useful
12730 to update the DHCP configuration.&lt;/p&gt;
12731
12732 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12733 ist all MAC addresses of all machines reporting to sitesummary. Run
12734 this on the collector host:&lt;/p&gt;
12735
12736 &lt;blockquote&gt;&lt;pre&gt;
12737 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12738 &lt;/pre&gt;&lt;/blockquote&gt;
12739
12740 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12741 line per machine and with space between the MAC addresses.&lt;/p&gt;
12742
12743 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12744 addresses for hosts, it would be possible to extend this to fetch
12745 machine information from sitesummary and update the DHCP and DNS
12746 tables in LDAP using this information. Such tool is unfortunately not
12747 written yet.&lt;/p&gt;
12748 </description>
12749 </item>
12750
12751 <item>
12752 <title>systemd, an interesting alternative to upstart</title>
12753 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
12754 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
12755 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
12756 <description>&lt;p&gt;The last few days a new boot system called
12757 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
12758 has been
12759 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
12760
12761 to the free software world. I have not yet had time to play around
12762 with it, but it seem to be a very interesting alternative to
12763 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
12764 a good alternative for Debian when we are able to switch to an event
12765 based boot system. Tollef is
12766 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
12767 systemd into Debian, and I look forward to seeing how well it work. I
12768 like the fact that systemd handles init.d scripts with dependency
12769 information natively, allowing them to run in parallel where upstart
12770 at the moment do not.&lt;/p&gt;
12771
12772 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
12773 platform support. It only work on recent Linux kernels, and also need
12774 some new kernel features enabled to function properly. This means
12775 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12776 system. Not sure how that will be handled if systemd proves to be the
12777 way forward.&lt;/p&gt;
12778
12779 &lt;p&gt;In the mean time, based on the
12780 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12781 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
12782 decided to enable full parallel booting as the default in Debian as
12783 soon as possible (probably this weekend or early next week), to see if
12784 there are any remaining serious bugs in the init.d dependencies. A
12785 new version of the sysvinit package implementing this change is
12786 already in experimental. If all go well, Squeeze will be released
12787 with parallel booting enabled by default.&lt;/p&gt;
12788 </description>
12789 </item>
12790
12791 <item>
12792 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
12793 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
12794 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
12795 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
12796 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
12797 complete, so complete that it is actually possible to run all the
12798 init.d scripts in parallell based on these dependencies. If you want
12799 to test your Squeeze system, make sure
12800 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12801 based boot sequencing&lt;/a&gt; is enabled, and add this line to
12802 /etc/default/rcS:&lt;/p&gt;
12803
12804 &lt;blockquote&gt;&lt;pre&gt;
12805 CONCURRENCY=makefile
12806 &lt;/pre&gt;&lt;/blockquote&gt;
12807
12808 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
12809 scripts in parallel using the dependency information stored in
12810 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12811 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12812 to try to start the kdm and gdm scripts as early as possible, and will
12813 start the facilities required by kdm or gdm as early as possible to
12814 make this happen.&lt;/p&gt;
12815
12816 &lt;p&gt;Give it a try, and see if you like the result. If some services
12817 fail to start properly, it is most likely because they have incomplete
12818 init.d script dependencies in their startup script (or some of their
12819 dependent scripts have incomplete dependencies). Report bugs and get
12820 the package maintainers to fix it. :)&lt;/p&gt;
12821
12822 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
12823 manage to get the init.d script dependencies complete and correct. I
12824 expect we will get there in Squeeze+1, if we get manage to test and
12825 fix the remaining issues.&lt;/p&gt;
12826
12827 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12828 the BTS, please usertag the report to get it to show up at
12829 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12830 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12831 </description>
12832 </item>
12833
12834 <item>
12835 <title>Debian has switched to dependency based boot sequencing</title>
12836 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
12837 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
12838 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
12839 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
12840 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
12841 have been migrated to using dependency based boot sequencing. This
12842 conclude work me and others have been doing for the last three days.
12843 It feels great to see this finally part of the default Debian
12844 installation. Now we just need to weed out the last few problems that
12845 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
12846
12847 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
12848 fixing the more fundamental problem of handing the event based
12849 non-predictable kernel in the early boot.&lt;/p&gt;
12850 </description>
12851 </item>
12852
12853 <item>
12854 <title>Taking over sysvinit development</title>
12855 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
12856 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
12857 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
12858 <description>&lt;p&gt;After several years of frustration with the lack of activity from
12859 the existing sysvinit upstream developer, I decided a few weeks ago to
12860 take over the package and become the new upstream. The number of
12861 patches to track for the Debian package was becoming a burden, and the
12862 lack of synchronization between the distribution made it hard to keep
12863 the package up to date.&lt;/p&gt;
12864
12865 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12866 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
12867 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
12868 and Fedora), based on the patches currently in use in these
12869 distributions. We Debian maintainers plan to move to this tarball as
12870 the new upstream as soon as we find time to do the merge. Since the
12871 new tarball was created, we agreed with Werner at SuSe to make a new
12872 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
12873 development there. The project is registered and currently waiting
12874 for approval by the Savannah administrators, and as soon as it is
12875 approved, we will import the old versions from svn and continue
12876 working on the future release.&lt;/p&gt;
12877
12878 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
12879 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
12880 </description>
12881 </item>
12882
12883 <item>
12884 <title>Debian boots quicker and quicker</title>
12885 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
12886 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
12887 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
12888 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
12889 people involved in the boot system on Debian and Ubuntu, to see if we
12890 could find more ways to speed up the boot system. This was an Ubuntu
12891 funded
12892 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
12893 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
12894 of boot systems, and ways to handle the increasing number of boot
12895 issues introduced by the Linux kernel becoming more and more
12896 asynchronous and event base. The Ubuntu approach using udev and
12897 upstart might be a good way forward. Time will show.&lt;/p&gt;
12898
12899 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
12900 process in Debian. All of these should be applied to get a quick
12901 boot:&lt;/p&gt;
12902
12903 &lt;ul&gt;
12904
12905 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
12906
12907 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
12908 clock is in UTC.&lt;/li&gt;
12909
12910 &lt;li&gt;Install and activate the insserv package to enable
12911 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12912 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
12913
12914 &lt;/ul&gt;
12915
12916 These points are based on the Google summer of code work done by
12917 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
12918 Villegas&lt;/a&gt;.
12919
12920 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
12921 unstable yesterday. When we tested it, we were able to cut 6 seconds
12922 from the boot sequence. It depend on very correct dependency
12923 declaration in all init.d scripts, so I expect us to find edge cases
12924 where the dependences in some scripts are slightly wrong when we start
12925 using this.&lt;/p&gt;
12926
12927 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12928 introduced by Raphael Geissert today, one that could affect the
12929 startup speed as well. Instead of starting some scripts concurrently
12930 from rcS.d/ and another set of scripts from rc2.d/, it would be
12931 possible to run a of them in the same process. A quick way to test
12932 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
12933 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
12934 </description>
12935 </item>
12936
12937 <item>
12938 <title>BSAs påstander om piratkopiering møter motstand</title>
12939 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
12940 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
12941 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
12942 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
12943 programvareselskapene som Microsoft og Apple, publisert en rapport der
12944 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12945 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12946 dager siden kom
12947 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
12948 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
12949 dagene. Et spesielt interessant kommentar fra Sverige,
12950 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
12951 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
12952
12953 &lt;blockquote&gt;
12954 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
12955 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12956 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
12957 exakta&quot;, säger BSAs Sverigechef John Hugosson.
12958 &lt;/blockquote&gt;
12959
12960 &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
12961 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
12962 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
12963 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
12964 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
12965
12966 &lt;p&gt;Fant lenkene via &lt;a
12967 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
12968 på Slashdot&lt;/a&gt;.&lt;/p&gt;
12969 </description>
12970 </item>
12971
12972 <item>
12973 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
12974 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
12975 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
12976 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
12977 <description>&lt;p&gt;Kom over
12978 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
12979 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12980 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12981 jobber til daglig. En rask opptelling forteller meg at vi har 490
12982 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
12983 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
12984 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
12985 </description>
12986 </item>
12987
12988 <item>
12989 <title>Kryptert harddisk - naturligvis</title>
12990 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
12991 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
12992 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
12993 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
12994 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
12995 når en tar tap av arbeidstid, fortrolige dokumenter,
12996 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12997 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12998 til at jeg har kryptert harddisken på både kontormaskinen og min
12999 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13000 komme på avveie, den første informasjon relatert til jobben min ved
13001 Universitetet i Oslo, og den andre relatert til blant annet
13002 foreningsarbeide. Kryptering av diskene gjør at det er lite
13003 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13004 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13005 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13006 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13007 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13008 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13009 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
13010 det er gjort slik jeg gjør det er minimale, og gevinstene er
13011 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
13012 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
13013
13014 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
13015 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
13016 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
13017 er for min del høyere enn gevinsten. Jeg tror oddsene for at
13018 f.eks. etteretningsorganisasjoner har glede av å titte på mine
13019 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
13020 gjøre det vanskeligere for angripere med kompetanse og ressurser er
13021 betydelige.&lt;/p&gt;
13022 </description>
13023 </item>
13024
13025 <item>
13026 <title>Two projects that have improved the quality of free software a lot</title>
13027 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
13028 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
13029 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
13030 <description>&lt;p&gt;There are two software projects that have had huge influence on the
13031 quality of free software, and I wanted to mention both in case someone
13032 do not yet know them.&lt;/p&gt;
13033
13034 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
13035 tool to detect and expose errors in the memory handling of programs.
13036 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
13037 and it will report any problems on stdout. It is even better if the
13038 program include debug information. With debug information, it is able
13039 to report the source file name and line number where the problem
13040 occurs. It can report things like &#39;reading past memory block in file
13041 X line N, the memory block was allocated in file Y, line M&#39;, and
13042 &#39;using uninitialised value in control logic&#39;. This tool has made it
13043 trivial to investigate reproducible crash bugs in programs, and have
13044 reduced the number of this kind of bugs in free software a lot.
13045
13046 &lt;p&gt;The second one is
13047 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
13048 a source code checker. It is able to process the source of a program
13049 and find problems in the logic without running the program. It
13050 started out as the Stanford Checker and became well known when it was
13051 used to find bugs in the Linux kernel. It is now a commercial tool
13052 and the company behind it is running
13053 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
13054 free software community, where a lot of free software projects get
13055 their source checked for free. Several thousand defects have been
13056 found and fixed so far. It can find errors like &#39;lock L taken in file
13057 X line N is never released if exiting in line M&#39;, or &#39;the code in file
13058 Y lines O to P can never be executed&#39;. The projects included in the
13059 community service project have managed to get rid of a lot of
13060 reliability problems thanks to Coverity.&lt;/p&gt;
13061
13062 &lt;p&gt;I believe tools like this, that are able to automatically find
13063 errors in the source, are vital to improve the quality of software and
13064 make sure we can get rid of the crashing and failing software we are
13065 surrounded by today.&lt;/p&gt;
13066 </description>
13067 </item>
13068
13069 <item>
13070 <title>No patch is not better than a useless patch</title>
13071 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
13072 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
13073 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
13074 <description>&lt;p&gt;Julien Blache
13075 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
13076 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
13077 patch allow one to discuss a concrete and proposed solution, and also
13078 prove that the issue at hand is important enough for someone to spent
13079 time on fixing it. No patch do not provide any of these positive
13080 properties.&lt;/p&gt;
13081 </description>
13082 </item>
13083
13084 <item>
13085 <title>Standardize on protocols and formats, not vendors and applications</title>
13086 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
13087 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
13088 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
13089 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
13090 very good one to form a long lived computer infrastructure. It is the
13091 simple one, lost by many in todays computer industry: Standardize on
13092 open network protocols and open exchange/storage formats, not applications.
13093 Applications come and go, while protocols and files tend to stay, and
13094 thus one want to make it easy to change application and vendor, while
13095 avoiding conversion costs and locking users to a specific platform or
13096 application.&lt;/p&gt;
13097
13098 &lt;p&gt;This approach make it possible to replace the client applications
13099 independently of the server applications. One can even allow users to
13100 use several different applications as long as they handle the selected
13101 protocol and format. In the normal case, only one client application
13102 is recommended and users only get help if they choose to use this
13103 application, but those that want to deviate from the easy path are not
13104 blocked from doing so.&lt;/p&gt;
13105
13106 &lt;p&gt;It also allow us to replace the server side without forcing the
13107 users to replace their applications, and thus allow us to select the
13108 best server implementation at any moment, when scale and resouce
13109 requirements change.&lt;/p&gt;
13110
13111 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
13112 open formats, but I would never recommend standardizing on a single
13113 application that do not use open network protocol or open formats.&lt;/p&gt;
13114 </description>
13115 </item>
13116
13117 <item>
13118 <title>Returning from Skolelinux developer gathering</title>
13119 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
13120 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
13121 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
13122 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
13123 Edu/Skolelinux development gathering. I got a bit done tuning the
13124 desktop, and looked into the dynamic service location protocol
13125 implementation avahi. It look like it could be useful for us. Almost
13126 30 people participated, and I believe it was a great environment to
13127 get to know the Skolelinux system. Walter Bender, involved in the
13128 development of the Sugar educational platform, presented his stuff and
13129 also helped me improve my OLPC installation. He also showed me that
13130 his Turtle Art application can be used in standalone mode, and we
13131 agreed that I would help getting it packaged for Debian. As a
13132 standalone application it would be great for Debian Edu. We also
13133 tried to get the video conferencing working with two OLPCs, but that
13134 proved to be too hard for us. The application seem to need more work
13135 before it is ready for me. I look forward to getting home and relax
13136 now. :)&lt;/p&gt;
13137 </description>
13138 </item>
13139
13140 <item>
13141 <title>Time for new LDAP schemas replacing RFC 2307?</title>
13142 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
13143 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
13144 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
13145 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
13146 optimal. There is RFC 2307 documenting one way to store NIS maps in
13147 LDAP, and a modified version of this normally called RFC 2307bis, with
13148 some modifications to be compatible with Active Directory. The RFC
13149 specification handle the content of a lot of system databases, but do
13150 not handle DNS zones and DHCP configuration.&lt;/p&gt;
13151
13152 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
13153 we would like to store information about users, SMB clients/hosts,
13154 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13155 and LTSP configuration in LDAP. These objects have a lot in common,
13156 but with the current LDAP schemas it is not possible to have one
13157 object per entity. For example, one need to have at least three LDAP
13158 objects for a given computer, one with the SMB related stuff, one with
13159 DNS information and another with DHCP information. The schemas
13160 provided for DNS and DHCP are impossible to combine into one LDAP
13161 object. In addition, it is impossible to implement quick queries for
13162 netgroup membership, because of the way NIS triples are implemented.
13163 It just do not scale. I believe it is time for a few RFC
13164 specifications to cleam up this mess.&lt;/p&gt;
13165
13166 &lt;p&gt;I would like to have one LDAP object representing each computer in
13167 the network, and this object can then keep the SMB (ie host key), DHCP
13168 (mac address/name) and DNS (name/IP address) settings in one place.
13169 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
13170
13171 &lt;p&gt;I would also like to have a quick way to map from a user or
13172 computer and to the net group this user or computer is a member.&lt;/p&gt;
13173
13174 &lt;p&gt;Active Directory have done a better job than unix heads like myself
13175 in this regard, and the unix side need to catch up. Time to start a
13176 new IETF work group?&lt;/p&gt;
13177 </description>
13178 </item>
13179
13180 <item>
13181 <title>Endelig er Debian Lenny gitt ut</title>
13182 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
13183 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
13184 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
13185 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
13186 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
13187 Et langt steg videre for Debian-prosjektet, og en rekke nye
13188 programpakker blir nå tilgjengelig for de av oss som bruker den
13189 stabile utgaven av Debian. Neste steg er nå å få
13190 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
13191 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
13192 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13193 slippes løs på skolene. Takk til alle debian-utviklerne som har
13194 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13195 bootsekvens tilgjengelig i stabil utgave, vha pakken
13196 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
13197 </description>
13198 </item>
13199
13200 <item>
13201 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
13202 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
13203 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
13204 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
13205 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
13206 Oslo. Most of Saturday was used for the general assemly for the
13207 member organization, but the rest of the weekend I used to tune the
13208 LTSP installation. LTSP now work out of the box on the 10-network.
13209 Acer Aspire One proved to be a very nice thin client, with both
13210 screen, mouse and keybard in a small box. Was working on getting the
13211 diskless workstation setup configured out of the box, but did not
13212 finish it before the weekend was up.&lt;/p&gt;
13213
13214 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
13215 the Brazilian group, so that will have to wait for the next
13216 development gathering. Would love to have the Debian Edu installer
13217 automatically detect and configure a multiseat setup when it find one
13218 of these cards.&lt;/p&gt;
13219 </description>
13220 </item>
13221
13222 <item>
13223 <title>The sorry state of multimedia browser plugins in Debian</title>
13224 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
13225 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
13226 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
13227 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
13228 plugins available in Debian Lenny, to see which one we should use by
13229 default in Debian Edu. We need an embedded video playing plugin with
13230 control buttons to pause or stop the video, and capable of streaming
13231 all the multimedia content available on the web. The test results and
13232 notes are available on
13233 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
13234 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
13235 fill this need. My personal video player favorite, VLC, has a really
13236 bad plugin which fail on a lot of the test pages. A lot of the MIME
13237 types I would expect to work with any free software player (like
13238 video/ogg), just do not work. And simple formats like the
13239 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
13240 totem and vlc plugins. I hope the situation will improve soon. No
13241 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
13242
13243 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
13244 be the only one fitting our needs. :/&lt;/p&gt;
13245 </description>
13246 </item>
13247
13248 </channel>
13249 </rss>