]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
68180e135ca9ed2b0c8e3d5d9cebc3c7124ca076
[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>wmbusmeters, parse data from your utility meter - nice free software</title>
11 <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</guid>
13 <pubDate>Fri, 19 May 2023 21:50:00 +0200</pubDate>
14 <description>&lt;p&gt;There is a European standard for reading utility meters like water,
15 gas, electricity or heat distribution meters. The
16 &lt;a href=&quot;https://en.wikipedia.org/wiki/Meter-Bus&quot;&gt;Meter-Bus standard
17 (EN 13757-2, EN 13757-3 and EN 137574)&lt;/a&gt; provide a cross vendor way
18 to talk to and collect meter data. I ran into this standard when I
19 wanted to monitor some heat distribution meters, and managed to find
20 free software that could do the job. The meters in question broadcast
21 encrypted messages with meter information via radio, and the hardest
22 part was to track down the encryption keys from the vendor. With this
23 in place I could set up a MQTT gateway to submit the meter data for
24 graphing.&lt;/p&gt;
25
26 &lt;p&gt;The free software systems in question,
27 &lt;a href=&quot;https://tracker.debian.org/pkg/rtl-wmbus&quot;&gt;rtl-wmbus&lt;/a&gt; to
28 read the messages from a software defined radio, and
29 &lt;a href=&quot;https://tracker.debian.org/pkg/wmbusmeters&quot;&gt;wmbusmeters&lt;/a&gt; to
30 decrypt and decode the content of the messages, is working very well
31 and allowe me to get frequent updates from my meters. I got in touch
32 with upstream last year to see if there was any interest in publishing
33 the packages via Debian. I was very happy to learn that Fredrik
34 Öhrström volunteered to maintain the packages, and I have since
35 assisted him in getting Debian package build rules in place as well as
36 sponsoring the packages into the Debian archive. Sadly we completed
37 it too late for them to become part of the next stable Debian release
38 (Bookworm). The wmbusmeters package just cleared the NEW queue. It
39 will need some work to fix a built problem, but I expect Fredrik will
40 find a solution soon.&lt;/p&gt;
41
42 &lt;p&gt;If you got a infrastructure meter supporting the Meter Bus
43 standard, I strongly recommend having a look at these nice
44 packages.&lt;/p&gt;
45
46 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
47 activities, please send Bitcoin donations to my address
48 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
49 </description>
50 </item>
51
52 <item>
53 <title>The 2023 LinuxCNC Norwegian developer gathering</title>
54 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</link>
55 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</guid>
56 <pubDate>Sun, 14 May 2023 20:30:00 +0200</pubDate>
57 <description>&lt;p&gt;The LinuxCNC project is making headway these days. A lot of
58 patches and issues have seen activity on
59 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/&quot;&gt;the project github
60 pages&lt;/a&gt; recently. A few weeks ago there was a developer gathering
61 over at the &lt;a href=&quot;https://tormach.com/&quot;&gt;Tormach&lt;/a&gt; headquarter in
62 Wisconsin, and now we are planning a new gathering in Norway. If you
63 wonder what LinuxCNC is, lets quote Wikipedia:&lt;/p&gt;
64
65 &lt;blockquote&gt;
66 &quot;LinuxCNC is a software system for numerical control of
67 machines such as milling machines, lathes, plasma cutters, routers,
68 cutting machines, robots and hexapods. It can control up to 9 axes or
69 joints of a CNC machine using G-code (RS-274NGC) as input. It has
70 several GUIs suited to specific kinds of usage (touch screen,
71 interactive development).&quot;
72 &lt;/blockquote&gt;
73
74 &lt;p&gt;The Norwegian developer gathering take place the weekend June 16th
75 to 18th this year, and is open for everyone interested in contributing
76 to LinuxCNC. Up to date information about the gathering can be found
77 in
78 &lt;a href=&quot;https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%40hjemme.reinholdtsen.name/#msg37837251&quot;&gt;the
79 developer mailing list thread&lt;/a&gt; where the gathering was announced.
80 Thanks to the good people at
81 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;,
82 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill-Linpro&lt;/a&gt; and
83 &lt;a href=&quot;https://www.nuugfoundation.no/no/&quot;&gt;NUUG Foundation&lt;/a&gt;, we
84 have enough sponsor funds to pay for food, and shelter for the people
85 traveling from afar to join us. If you would like to join the
86 gathering, get in touch.&lt;/p&gt;
87
88 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
89 activities, please send Bitcoin donations to my address
90 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
91 </description>
92 </item>
93
94 <item>
95 <title>OpenSnitch in Debian ready for prime time</title>
96 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</link>
97 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</guid>
98 <pubDate>Sat, 13 May 2023 12:10:00 +0200</pubDate>
99 <description>&lt;p&gt;A bit delayed,
100 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
101 application firewall OpenSnitch&lt;/a&gt; package in Debian now got the
102 latest fixes ready for Debian Bookworm. Because it depend on a
103 package missing on some architectures, the autopkgtest check of the
104 testing migration script did not understand that the tests were
105 actually working, so the migration was delayed. A bug in the package
106 dependencies is also fixed, so those installing the firewall package
107 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
108 installed by default. I am very grateful to Gustavo Iñiguez Goya for
109 his work on getting the package ready for Debian Bookworm.&lt;/p&gt;
110
111 &lt;p&gt;Armed with this package I have discovered some surprising
112 connections from programs I believed were able to work completly
113 offline, and it has already proven its worth, at least to me. If you
114 too want to get more familiar with the kind of programs using
115 Internett connections on your machine, I recommend testing &lt;tt&gt;apt
116 install opensnitch&lt;/tt&gt; in Bookworm and see what you think.&lt;/p&gt;
117
118 &lt;p&gt;The package is still not able to build its eBPF module within
119 Debian. Not sure how much work it would be to get it working, but
120 suspect some kernel related packages need to be extended with more
121 header files to get it working.&lt;/p&gt;
122
123 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
124 activities, please send Bitcoin donations to my address
125 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
126 </description>
127 </item>
128
129 <item>
130 <title>Speech to text, she APTly whispered, how hard can it be?</title>
131 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</link>
132 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</guid>
133 <pubDate>Sun, 23 Apr 2023 09:40:00 +0200</pubDate>
134 <description>&lt;p&gt;While visiting a convention during Easter, it occurred to me that
135 it would be great if I could have a digital Dictaphone with
136 transcribing capabilities, providing me with texts to cut-n-paste into
137 stuff I need to write. The background is that long drives often bring
138 up the urge to write on texts I am working on, which of course is out
139 of the question while driving. With the release of
140 &lt;a href=&quot;https://github.com/openai/whisper/&quot;&gt;OpenAI Whisper&lt;/a&gt;, this
141 seem to be within reach with Free Software, so I decided to give it a
142 go. OpenAI Whisper is a Linux based neural network system to read in
143 audio files and provide text representation of the speech in that
144 audio recording. It handle multiple languages and according to its
145 creators even can translate into a different language than the spoken
146 one. I have not tested the latter feature. It can either use the CPU
147 or a GPU with CUDA support. As far as I can tell, CUDA in practice
148 limit that feature to NVidia graphics cards. I have few of those, as
149 they do not work great with free software drivers, and have not tested
150 the GPU option. While looking into the matter, I did discover some
151 work to provide CUDA support on non-NVidia GPUs, and some work with
152 the library used by Whisper to port it to other GPUs, but have not
153 spent much time looking into GPU support yet. I&#39;ve so far used an old
154 X220 laptop as my test machine, and only transcribed using its
155 CPU.&lt;/p&gt;
156
157 &lt;p&gt;As it from a privacy standpoint is unthinkable to use computers
158 under control of someone else (aka a &quot;cloud&quot; service) to transcribe
159 ones thoughts and personal notes, I want to run the transcribing
160 system locally on my own computers. The only sensible approach to me
161 is to make the effort I put into this available for any Linux user and
162 to upload the needed packages into Debian. Looking at Debian Bookworm, I
163 discovered that only three packages were missing,
164 &lt;a href=&quot;https://bugs.debian.org/1034307&quot;&gt;tiktoken&lt;/a&gt;,
165 &lt;a href=&quot;https://bugs.debian.org/1034144&quot;&gt;triton&lt;/a&gt;, and
166 &lt;a href=&quot;https://bugs.debian.org/1034091&quot;&gt;openai-whisper&lt;/a&gt;. For a while
167 I also believed
168 &lt;a href=&quot;https://bugs.debian.org/1034286&quot;&gt;ffmpeg-python&lt;/a&gt; was
169 needed, but as its
170 &lt;a href=&quot;https://github.com/kkroening/ffmpeg-python/issues/760&quot;&gt;upstream
171 seem to have vanished&lt;/a&gt; I found it safer
172 &lt;a href=&quot;https://github.com/openai/whisper/pull/1242&quot;&gt;to rewrite
173 whisper&lt;/a&gt; to stop depending on in than to introduce ffmpeg-python
174 into Debian. I decided to place these packages under the umbrella of
175 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team&quot;&gt;the Debian Deep
176 Learning Team&lt;/a&gt;, which seem like the best team to look after such
177 packages. Discussing the topic within the group also made me aware
178 that the triton package was already a future dependency of newer
179 versions of the torch package being planned, and would be needed after
180 Bookworm is released.&lt;/p&gt;
181
182 &lt;p&gt;All required code packages have been now waiting in
183 &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the Debian NEW
184 queue&lt;/a&gt; since Wednesday, heading for Debian Experimental until
185 Bookworm is released. An unsolved issue is how to handle the neural
186 network models used by Whisper. The default behaviour of Whisper is
187 to require Internet connectivity and download the model requested to
188 &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt; on first invocation. This obviously would
189 fail &lt;a href=&quot;https://people.debian.org/~bap/dfsg-faq.html&quot;&gt;the
190 deserted island test of free software&lt;/a&gt; as the Debian packages would
191 be unusable for someone stranded with only the Debian archive and solar
192 powered computer on a deserted island.&lt;/p&gt;
193
194 &lt;p&gt;Because of this, I would love to include the models in the Debian
195 mirror system. This is problematic, as the models are very large
196 files, which would put a heavy strain on the Debian mirror
197 infrastructure around the globe. The strain would be even higher if
198 the models change often, which luckily as far as I can tell they do
199 not. The small model, which according to its creator is most useful
200 for English and in my experience is not doing a great job there
201 either, is 462 MiB (deb is 414 MiB). The medium model, which to me
202 seem to handle English speech fairly well is 1.5 GiB (deb is 1.3 GiB)
203 and the large model is 2.9 GiB (deb is 2.6 GiB). I would assume
204 everyone with enough resources would prefer to use the large model for
205 highest quality. I believe the models themselves would have to go
206 into the non-free part of the Debian archive, as they are not really
207 including any useful source code for updating the models. The
208 &quot;source&quot;, aka the model training set, according to the creators
209 consist of &quot;680,000 hours of multilingual and multitask supervised
210 data collected from the web&quot;, which to me reads material with both
211 unknown copyright terms, unavailable to the general public. In other
212 words, the source is not available according to the Debian Free
213 Software Guidelines and the model should be considered non-free.&lt;/p&gt;
214
215 &lt;p&gt;I asked the Debian FTP masters for advice regarding uploading a
216 model package on their IRC channel, and based on the feedback there it
217 is still unclear to me if such package would be accepted into the
218 archive. In any case I wrote build rules for a
219 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team/openai-whisper-model&quot;&gt;OpenAI
220 Whisper model package&lt;/a&gt; and
221 &lt;a href=&quot;https://github.com/openai/whisper/pull/1257&quot;&gt;modified the
222 Whisper code base&lt;/a&gt; to prefer shared files under &lt;tt&gt;/usr/&lt;/tt&gt; and
223 &lt;tt&gt;/var/&lt;/tt&gt; over user specific files in &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt;
224 to be able to use these model packages, to prepare for such
225 possibility. One solution might be to include only one of the models
226 (small or medium, I guess) in the Debian archive, and ask people to
227 download the others from the Internet. Not quite sure what to do
228 here, and advice is most welcome (use the debian-ai mailing list).&lt;/p&gt;
229
230 &lt;p&gt;To make it easier to test the new packages while I wait for them to
231 clear the NEW queue, I created an APT source targeting bookworm. I
232 selected Bookworm instead of Bullseye, even though I know the latter
233 would reach more users, is that some of the required dependencies are
234 missing from Bullseye and I during this phase of testing did not want
235 to backport a lot of packages just to get up and running.&lt;/p&gt;
236
237 &lt;p&gt;Here is a recipe to run as user root if you want to test OpenAI
238 Whisper using Debian packages on your Debian Bookworm installation,
239 first adding the APT repository GPG key to the list of trusted keys,
240 then setting up the APT repository and finally installing the packages
241 and one of the models:&lt;/p&gt;
242
243 &lt;p&gt;&lt;pre&gt;
244 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
245 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
246 mkdir -p /etc/apt/sources.list.d
247 cat &gt; /etc/apt/sources.list.d/pere-whisper.list &amp;lt;&amp;lt;EOF
248 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
249 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
250 EOF
251 apt update
252 apt install openai-whisper
253 &lt;/pre&gt;&lt;/p&gt;
254
255 &lt;p&gt;The package work for me, but have not yet been tested on any other
256 computer than my own. With it, I have been able to (badly) transcribe
257 a 2 minute 40 second Norwegian audio clip to test using the small
258 model. This took 11 minutes and around 2.2 GiB of RAM. Transcribing
259 the same file with the medium model gave a accurate text in 77 minutes
260 using around 5.2 GiB of RAM. My test machine had too little memory to
261 test the large model, which I believe require 11 GiB of RAM. In
262 short, this now work for me using Debian packages, and I hope it will
263 for you and everyone else once the packages enter Debian.&lt;/p&gt;
264
265 &lt;p&gt;Now I can start on the audio recording part of this project.&lt;/p&gt;
266
267 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
268 activities, please send Bitcoin donations to my address
269 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
270 </description>
271 </item>
272
273 <item>
274 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software</title>
275 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</link>
276 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</guid>
277 <pubDate>Fri, 7 Apr 2023 23:10:00 +0200</pubDate>
278 <description>&lt;p&gt;Today I finally found time to track down a useful radio frequency
279 scanner for my software defined radio. Just for fun I tried to locate
280 the radios used in the areas, and a good start would be to scan all
281 the frequencies to see what is in use. I&#39;ve tried to find a useful
282 program earlier, but ran out of time before I managed to find a useful
283 tool. This time I was more successful, and after a few false leads I
284 found a description of
285 &lt;a href=&quot;https://www.kali.org/tools/rtlsdr-scanner/&quot;&gt;rtlsdr-scanner
286 over at the Kali site&lt;/a&gt;, and was able to track down
287 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git&quot;&gt;the
288 Kali package git repository&lt;/a&gt; to build a deb package for the
289 scanner. Sadly the package is missing from the Debian project itself,
290 at least in Debian Bullseye. Two runtime dependencies,
291 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-visvis.git&quot;&gt;python-visvis&lt;/a&gt;
292 and
293 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-rtlsdr.git&quot;&gt;python-rtlsdr&lt;/a&gt;
294 had to be built and installed separately. Luckily &#39;&lt;tt&gt;gbp
295 buildpackage&lt;/tt&gt;&#39; handled them just fine and no further packages had
296 to be manually built. The end result worked out of the box after
297 installation.&lt;/p&gt;
298
299 &lt;p&gt;My initial scans for FM channels worked just fine, so I knew the
300 scanner was functioning. But when I tried to scan every frequency
301 from 100 to 1000 MHz, the program stopped unexpectedly near the
302 completion. After some debugging I discovered USB software radio I
303 used rejected frequencies above 948 MHz, triggering a unreported
304 exception breaking the scan. Changing the scan to end at 957 worked
305 better. I similarly found the lower limit to be around 15, and ended
306 up with the following full scan:&lt;/p&gt;
307
308 &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;
309
310 &lt;p&gt;Saving the scan did not work, but exporting it as a CSV file worked
311 just fine. I ended up with around 477k CVS lines with dB level for
312 the given frequency.&lt;/p&gt;
313
314 &lt;p&gt;The save failure seem to be a missing UTF-8 encoding issue in the
315 python code. Will see if I can find time to send a patch
316 &lt;a href=&quot;https://github.com/CdeMills/RTLSDR-Scanner/&quot;&gt;upstream&lt;/a&gt;
317 later to fix this exception:&lt;/p&gt;
318
319 &lt;pre&gt;
320 Traceback (most recent call last):
321 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
322 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
323 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
324 handle.write(json.dumps(data, indent=4))
325 TypeError: a bytes-like object is required, not &#39;str&#39;
326 Traceback (most recent call last):
327 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
328 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
329 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
330 handle.write(json.dumps(data, indent=4))
331 TypeError: a bytes-like object is required, not &#39;str&#39;
332 &lt;/pre&gt;
333
334 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
335 activities, please send Bitcoin donations to my address
336 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
337 </description>
338 </item>
339
340 <item>
341 <title>OpenSnitch available in Debian Sid and Bookworm</title>
342 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</link>
343 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</guid>
344 <pubDate>Sat, 25 Feb 2023 20:30:00 +0100</pubDate>
345 <description>&lt;p&gt;Thanks to the efforts of the OpenSnitch lead developer Gustavo
346 Iñiguez Goya allowing me to sponsor the upload,
347 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
348 application firewall OpenSnitch&lt;/a&gt; is now available in Debian
349 Testing, soon to become the next stable release of Debian.&lt;/p&gt;
350
351 &lt;p&gt;This is a package which set up a network firewall on one or more
352 machines, which is controlled by a graphical user interface that will
353 ask the user if a program should be allowed to connect to the local
354 network or the Internet. If some background daemon is trying to dial
355 home, it can be blocked from doing so with a simple mouse click, or by
356 default simply by not doing anything when the GUI question dialog pop
357 up. A list of all programs discovered using the network is provided
358 in the GUI, giving the user an overview of how the machine(s) programs
359 use the network.&lt;/p&gt;
360
361 &lt;p&gt;OpenSnitch was uploaded for NEW processing about a month ago, and I
362 had little hope of it getting accepted and shaping up in time for the
363 package freeze, but the Debian ftpmasters proved to be amazingly quick
364 at checking out the package and it was accepted into the archive about
365 week after the first upload. It is now team maintained under the Go
366 language team umbrella. A few fixes to the default setup is only in
367 Sid, and should migrate to Testing/Bookworm in a week.&lt;/p&gt;
368
369 &lt;p&gt;During testing I ran into an
370 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/813&quot;&gt;issue
371 with Minecraft server broadcasts disappearing&lt;/a&gt;, which was quickly
372 resolved by the developer with a patch and a proposed configuration
373 change. I&#39;ve been told this was caused by the Debian packages default
374 use if /proc/ information to track down kernel status, instead of the
375 newer eBPF module that can be used. The reason is simply that
376 upstream and I have failed to find a way to build the eBPF modules for
377 OpenSnitch without a complete configured Linux kernel source tree,
378 which as far as we can tell is unavailable as a build dependency in
379 Debian. We tried unsuccessfully so far to use the kernel-headers
380 package. It would be great if someone could provide some clues how to
381 build eBPF modules on build daemons in Debian, possibly without the full
382 kernel source.&lt;/p&gt;
383
384 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
385 activities, please send Bitcoin donations to my address
386 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
387 </description>
388 </item>
389
390 <item>
391 <title>Is the desktop recommending your program for opening its files?</title>
392 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</link>
393 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</guid>
394 <pubDate>Sun, 29 Jan 2023 11:00:00 +0100</pubDate>
395 <description>&lt;p&gt;Linux desktop systems
396 &lt;a href=&quot;https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html&quot;&gt;have
397 standardized&lt;/a&gt; how programs present themselves to the desktop
398 system. If a package include a .desktop file in
399 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
400 environments will pick up the file and use its content to generate the
401 menu of available programs in the system. A lesser known fact is that
402 a package can also explain to the desktop system how to recognize the
403 files created by the program in question, and use it to open these
404 files on request, for example via a GUI file browser.&lt;/p&gt;
405
406 &lt;p&gt;A while back I ran into a package that did not tell the desktop
407 system how to recognize its files and was not used to open its files
408 in the file browser and fixed it. In the process I wrote a simple
409 debian/tests/ script to ensure the setup keep working. It might be
410 useful for other packages too, to ensure any future version of the
411 package keep handling its own files.&lt;/p&gt;
412
413 &lt;p&gt;For this to work the file format need a useful MIME type that can
414 be used to identify the format. If the file format do not yet have a
415 MIME type, it should define one and preferably also
416 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;register
417 it with IANA&lt;/a&gt; to ensure the MIME type string is reserved.&lt;/p&gt;
418
419 &lt;p&gt;The script uses the &lt;tt&gt;xdg-mime&lt;/tt&gt; program from xdg-utils to
420 query the database of standardized package information and ensure it
421 return sensible values. It also need the location of an example file
422 for xdg-mime to guess the format of.&lt;/p&gt;
423
424 &lt;pre&gt;
425 #!/bin/sh
426 #
427 # Author: Petter Reinholdtsen
428 # License: GPL v2 or later at your choice.
429 #
430 # Validate the MIME setup, making sure motor types have
431 # application/vnd.openmotor+yaml associated with them and is connected
432 # to the openmotor desktop file.
433
434 retval=0
435
436 mimetype=&quot;application/vnd.openmotor+yaml&quot;
437 testfile=&quot;test/data/real/o3100/motor.ric&quot;
438 mydesktopfile=&quot;openmotor.desktop&quot;
439
440 filemime=&quot;$(xdg-mime query filetype &quot;$testfile&quot;)&quot;
441
442 if [ &quot;$mimetype&quot; != &quot;$filemime&quot; ] ; then
443 retval=1
444 echo &quot;error: xdg-mime claim motor file MIME type is $filemine, not $mimetype&quot;
445 else
446 echo &quot;success: xdg-mime report correct mime type $mimetype for motor file&quot;
447 fi
448
449 desktop=$(xdg-mime query default &quot;$mimetype&quot;)
450
451 if [ &quot;$mydesktopfile&quot; != &quot;$desktop&quot; ]; then
452 retval=1
453 echo &quot;error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile&quot;
454 else
455 echo &quot;success: xdg-mime agree motor file should be handled by $mydesktopfile&quot;
456 fi
457
458 exit $retval
459 &lt;/pre&gt;
460
461 &lt;p&gt;It is a simple way to ensure your users are not very surprised when
462 they try to open one of your file formats in their file browser.&lt;/p&gt;
463
464 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
465 activities, please send Bitcoin donations to my address
466 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
467 </description>
468 </item>
469
470 <item>
471 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive</title>
472 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</link>
473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</guid>
474 <pubDate>Sun, 22 Jan 2023 23:55:00 +0100</pubDate>
475 <description>&lt;p&gt;While reading a
476 &lt;a href=&quot;https://sneak.berlin/20230115/macos-scans-your-local-files-now/&quot;&gt;blog
477 post claiming MacOS X recently started scanning local files and
478 reporting information about them to Apple&lt;/a&gt;, even on a machine where
479 all such callback features had been disabled, I came across a
480 description of the Little Snitch application for MacOS X. It seemed
481 like a very nice tool to have in the tool box, and I decided to see if
482 something similar was available for Linux.&lt;/p&gt;
483
484 &lt;p&gt;It did not take long to find
485 &lt;a href=&quot;https://github.com/evilsocket/opensnitch&quot;&gt;the OpenSnitch
486 package&lt;/a&gt;, which has been in development since 2017, and now is in
487 version 1.5.0. It has had a
488 &lt;a href=&quot;https://bugs.debian.org/909567&quot;&gt;request for Debian
489 packaging&lt;/a&gt; since 2018, but no-one completed the job so far. Just
490 for fun, I decided to see if I could help, and I was very happy to
491 discover that
492 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/304&quot;&gt;upstream
493 want a Debian package too&lt;/a&gt;.&lt;/p&gt;
494
495 &lt;p&gt;After struggling a bit with getting the program to run, figuring
496 out building Go programs (and a little failed detour to look at eBPF
497 builds too - help needed), I am very happy to report that I am
498 sponsoring upstream to maintain the package in Debian, and it has
499 since this morning been waiting in NEW for the ftpmasters to have a
500 look. Perhaps it can get into the archive in time for the Bookworm
501 release?&lt;/p&gt;
502
503 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
504 activities, please send Bitcoin donations to my address
505 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
506 </description>
507 </item>
508
509 <item>
510 <title>LinuxCNC MQTT publisher component</title>
511 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</link>
512 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</guid>
513 <pubDate>Sun, 8 Jan 2023 19:30:00 +0100</pubDate>
514 <description>&lt;p&gt;I watched &lt;a href=&quot;https://yewtu.be/watch?v=jmKUV3aNLjk&quot;&gt;a 2015
515 video from Andreas Schiffler&lt;/a&gt; the other day, where he set up
516 &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;LinuxCNC&lt;/a&gt; to send status
517 information to the MQTT broker IBM Bluemix. As I also use MQTT for
518 graphing, it occured to me that a generic MQTT LinuxCNC component
519 would be useful and I set out to implement it. Today I got the first
520 draft limping along and submitted as
521 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/2253&quot;&gt;a patch to the
522 LinuxCNC project&lt;/a&gt;.&lt;/p&gt;
523
524 &lt;p&gt;The simple part was setting up the MQTT publishing code in Python.
525 I already have set up other parts submitting data to my Mosquito MQTT
526 broker, so I could reuse that code. Writing a LinuxCNC component in
527 Python as new to me, but using existing examples in the code
528 repository and the extensive documentation, this was fairly straight
529 forward. The hardest part was creating a automated test for the
530 component to ensure it was working. Testing it in a simulated
531 LinuxCNC machine proved very useful, as I discovered features I needed
532 that I had not thought of yet, and adjusted the code quite a bit to
533 make it easier to test without a operational MQTT broker
534 available.&lt;/p&gt;
535
536 &lt;p&gt;The draft is ready and working, but I am unsure which LinuxCNC HAL
537 pins I should collect and publish by default (in other words, the
538 default set of information pieces published), and how to get the
539 machine name from the LinuxCNC INI file. The latter is a minor
540 detail, but I expect it would be useful in a setup with several
541 machines available. I am hoping for feedback from the experienced
542 LinuxCNC developers and users, to make the component even better
543 before it can go into the mainland LinuxCNC code base.&lt;/p&gt;
544
545 &lt;p&gt;Since I started on the MQTT component, I came across
546 &lt;a href=&quot;https://yewtu.be/watch?v=Bqa2grG0XtA&quot;&gt;another video from Kent
547 VanderVelden&lt;/a&gt; where he combine LinuxCNC with a set of screen glasses
548 controlled by a Raspberry Pi, and it occured to me that it would
549 be useful for such use cases if LinuxCNC also provided a REST API for
550 querying its status. I hope to start on such component once the MQTT
551 component is working well.&lt;/p&gt;
552
553 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
554 activities, please send Bitcoin donations to my address
555 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
556 </description>
557 </item>
558
559 <item>
560 <title>ONVIF IP camera management tool finally in Debian</title>
561 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</link>
562 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</guid>
563 <pubDate>Sat, 24 Dec 2022 08:00:00 +0100</pubDate>
564 <description>&lt;p&gt;Merry Christmas to you all. Here is a small gift to all those with
565 IP cameras following the &lt;a href=&quot;https://www.onvif.org/&quot;&gt;ONVIF
566 specification&lt;/a&gt;. There is finally a nice command line and GUI tool
567 in Debian to manage ONVIF IP cameras. After working with upstream for
568 a few months and sponsoring the upload, I am very happy to report that
569 the &lt;a href=&quot;https://tracker.debian.org/libonvif&quot;&gt;libonvif package&lt;/a&gt;
570 entered Debian Sid last night.&lt;/p&gt;
571
572 &lt;p&gt;The package provide a C library to communicate with such cameras, a
573 command line tool to locate and update settings of (like password) the
574 cameras and a GUI tool to configure and control the units as well as
575 preview the video from the camera. Libonvif is available on Both
576 Linux and Windows and the GUI tool uses the Qt library. The main
577 competitors are non-free software, while libonvif is GNU GPL licensed.
578 I am very glad Debian users in the future can control their cameras
579 using a free software system provided by Debian. But the ONVIF world
580 is full of slightly broken firmware, where the cameras pretend to
581 follow the ONVIF specification but fail to set some configuration
582 values or refuse to provide video to more than one recipient at the
583 time, and the onvif project is quite young and might take a while
584 before it completely work with your camera. Upstream seem eager to
585 improve the library, so handling any broken camera might be just &lt;a
586 href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;a bug report away&lt;/a&gt;.&lt;/p&gt;
587
588 &lt;p&gt;The package just cleared NEW, and need a new source only upload
589 before it can enter testing. This will happen in the next few
590 days.&lt;/p&gt;
591
592 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
593 activities, please send Bitcoin donations to my address
594 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
595 </description>
596 </item>
597
598 <item>
599 <title>Managing and using ONVIF IP cameras with Linux</title>
600 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</link>
601 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</guid>
602 <pubDate>Wed, 19 Oct 2022 12:30:00 +0200</pubDate>
603 <description>&lt;p&gt;Recently I have been looking at how to control and collect data
604 from a handful IP cameras using Linux. I both wanted to change their
605 settings and to make their imagery available via a free software
606 service under my control. Here is a summary of the tools I found.&lt;/p&gt;
607
608 &lt;p&gt;First I had to identify the cameras and their protocols. As far as
609 I could tell, they were using some SOAP looking protocol and their
610 internal web server seem to only work with Microsoft Internet Explorer
611 with some proprietary binary plugin, which in these days of course is
612 a security disaster and also made it impossible for me to use the
613 camera web interface. Luckily I discovered that the SOAP looking
614 protocol is actually following &lt;a href=&quot;https://www.onvif.org/&quot;&gt;the
615 ONVIF specification&lt;/a&gt;, which seem to be supported by a lot of IP
616 cameras these days.&lt;/p&gt;
617
618 &lt;p&gt;Once the protocol was identified, I was able to find what appear to
619 be the most popular way to configure ONVIF cameras, the free software
620 Windows tool named
621 &lt;a href=&quot;https://sourceforge.net/projects/onvifdm/&quot;&gt;ONVIF Device
622 Manager&lt;/a&gt;. Lacking any other options at the time, I tried
623 unsuccessfully to get it running using Wine, but was missing a dotnet
624 40 library and I found no way around it to run it on Linux.&lt;/p&gt;
625
626 &lt;p&gt;The next tool I found to configure the cameras were a non-free Linux Qt
627 client &lt;a href=&quot;https://www.lingodigit.com/onvif_nvcdemo.html&quot;&gt;ONVIF
628 Device Tool&lt;/a&gt;. I did not like its terms of use, so did not spend
629 much time on it.&lt;/p&gt;
630
631 &lt;p&gt;To collect the video and make it available in a web interface, I
632 found the Zoneminder tool in Debian. A recent version was able to
633 automatically detect and configure ONVIF devices, so I could use it to
634 set up motion detection in and collection of the camera output. I had
635 initial problems getting the ONVIF autodetection to work, as both
636 Firefox and Chromium &lt;a href=&quot;https://bugs.debian.org/1001188&quot;&gt;refused
637 the inter-tab communication&lt;/a&gt; being used by the Zoneminder web
638 pages, but managed to get konqueror to work. Apparently the &quot;Enhanced
639 Tracking Protection&quot; in Firefox cause the problem. I ended up
640 upgrading to the Bookworm edition of Zoneminder in the process to try
641 to fix the issue, and believe the problem might be solved now.&lt;/p&gt;
642
643 &lt;p&gt;In the process I came across the nice Linux GUI tool
644 &lt;a href=&quot;https://gitlab.com/caspermeijn/onvifviewer/&quot;&gt;ONVIF Viewer&lt;/a&gt;
645 allowing me to preview the camera output and validate the login
646 passwords required. Sadly its author has grown tired of maintaining
647 the software, so it might not see any future updates. Which is sad,
648 as the viewer is sightly unstable and the picture tend to lock up.
649 Note, this lockup might be due to limitations in the cameras and not
650 the viewer implementation. I suspect the camera is only able to
651 provide pictures to one client at the time, and the Zoneminder feed
652 might interfere with the GUI viewer. I have
653 &lt;a href=&quot;https://bugs.debian.org/1000820&quot;&gt;asked for the tool to be
654 included in Debian&lt;/a&gt;.&lt;/p&gt;
655
656 &lt;p&gt;Finally, I found what appear to be very nice Linux free software
657 replacement for the Windows tool, named
658 &lt;a href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;libonvif&lt;/a&gt;. It
659 provide a C library to talk to ONVIF devices as well as a command line
660 and GUI tool using the library. Using the GUI tool I was able to change
661 the admin passwords and update other settings of the cameras. I have
662 &lt;a href=&quot;https://bugs.debian.org/1021980&quot;&gt;asked for the package to be
663 included in Debian&lt;/a&gt;.&lt;/p&gt;
664
665 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
666 activities, please send Bitcoin donations to my address
667 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
668
669 &lt;p&gt;&lt;strong&gt;Update 2022-10-20&lt;/strong&gt;: Since my initial publication of
670 this text, I got several suggestions for more free software Linux
671 tools. There is &lt;a href=&quot;https://github.com/quatanium/python-onvif&quot;&gt;a
672 ONVIF python library&lt;/a&gt; (already
673 &lt;a href=&quot;https://bugs.debian.org/824240&quot;&gt;requested into Debian&lt;/a&gt;) and
674 &lt;a href=&quot;https://github.com/FalkTannhaeuser/python-onvif-zeep&quot;&gt;a python 3
675 fork&lt;/a&gt; using a different SOAP dependency. There is also
676 &lt;a href=&quot;https://www.home-assistant.io/integrations/onvif/&quot;&gt;support for
677 ONVIF in Home Assistant&lt;/a&gt;, and there is an alternative to Zoneminder
678 called &lt;a href=&quot;https://www.shinobi.video/&quot;&gt;Shinobi&lt;/a&gt;. The latter
679 two are not included in Debian either. I have not tested any of these
680 so far.&lt;/p&gt;
681 </description>
682 </item>
683
684 <item>
685 <title>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
686 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
687 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
688 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
689 <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;
690
691 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
692
693 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
694 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
695 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
696 english text is updated, and it is time to start working on the
697 translations. Around 37 percent of the strings have been updated, one
698 way or another, and the translations starting from a complete Debian Buster
699 edition now need to bring their translation up from 63% to 100%. The
700 complete book is licensed using a Creative Commons license, and has
701 been published in several languages over the years. The translations
702 are done by volunteers to bring Linux in their native tongue. The
703 last time I checked, it complete text was available in English,
704 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
705 In addition, work has been started for Arabic (Morocco), Catalan,
706 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
707 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
708 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
709
710 &lt;p&gt;The translation is conducted on
711 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
712 hosted weblate project page&lt;/a&gt;. Prospective translators are
713 recommeded to subscribe to
714 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
715 translators mailing list&lt;/a&gt; and should also check out
716 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
717 contributors&lt;/a&gt;.&lt;/p&gt;
718
719 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
720 have just started. Your contribution is most welcome.&lt;/p&gt;
721
722 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
723 activities, please send Bitcoin donations to my address
724 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
725 </description>
726 </item>
727
728 <item>
729 <title>Automatic LinuxCNC servo PID tuning?</title>
730 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
731 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
732 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
733 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
734 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
735 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
736 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
737 that control such mathematical machinery that a PID controller is. It
738 proved to be a lot harder than I hoped, and I still have not succeeded
739 in getting the Z PID controller to successfully defy gravity, nor X
740 and Y to move accurately and reliably. But while climbing up this
741 rather steep learning curve, I discovered that some motor control
742 systems are able to tune their PID controllers. I got the impression
743 from the documentation that LinuxCNC were not. This proved to be not
744 true.&lt;/p&gt;
745
746 &lt;p&gt;The LinuxCNC
747 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
748 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
749 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
750 &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
751 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
752 state, and all of these need to have a sensible value for the
753 controller to behave properly. Note, there are even more values
754 involved, theser are just the most important ones. In my case I need
755 the X, Y and Z axes to follow the requested path with little error.
756 This has proved quite a challenge for someone who have never tuned a
757 PID controller before, but there is at least some help to be found.
758
759 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
760 at_pid claiming to have auto tuning capabilities. Sadly it had been
761 neglected since 2011, and could not be used as a plug in replacement
762 for the default pid component. One would have to rewriting the
763 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
764 to quickly test auto tuning to see if it did a better job than me at
765 figuring out good P, I and D values to use.&lt;/p&gt;
766
767 &lt;p&gt;I decided to have a look if the situation could be improved. This
768 involved trying to understand the code and history of the pid and
769 at_pid components. Apparently they had a common ancestor, as code
770 structure, comments and variable names were quite close to each other.
771 Sadly this was not reflected in the git history, making it hard to
772 figure out what really happened. My guess is that the author of
773 &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;
774 took a version of
775 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
776 rewrote it to follow the structure he wished pid.c to have, then added
777 support for auto tuning and finally got it included into the LinuxCNC
778 repository. The restructuring and lack of early history made it
779 harder to figure out which part of the code were relevant to the auto
780 tuning, and which part of the code needed to be updated to work the
781 same way as the current pid.c implementation. I started by trying to
782 isolate relevant changes in pid.c, and applying them to at_pid.c. My
783 aim was to make sure the at_pid component could replace the pid
784 component with a simple change in the HAL setup loadrt line, without
785 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
786 hours following this approach, I had learned quite a lot about the
787 code structure of both components, while concluding I was heading down
788 the wrong rabbit hole, and should get back to the surface and find a
789 different path.&lt;/p&gt;
790
791 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
792 related part of the original at_pid.c, and instead isolate and lift
793 the auto tuning part of the code and inject it into a copy of pid.c.
794 This ensured compatibility with the current pid component, while
795 adding auto tuning as a run time option. To make it easier to identify
796 the relevant parts in the future, I wrapped all the auto tuning code
797 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
798 pid component by default, as that part of the code is identical. The
799 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
800 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
801
802 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
803 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
804 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
805 back, and see what the auto tuning code will do. I do not know the
806 mathematical foundation of the at_pid algorithm, but from observation
807 I can tell that the algorithm will, when enabled, produce a square
808 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
809 of the PID controller. This can be seen using the HAL Scope provided
810 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
811 to the motor controller, which in turn is translated into motor speed.
812 So at_pid will ask the motor to move the axis back and forth. The
813 number of cycles in the pattern is controlled by the
814 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
815 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
816 change the direction of a physical object instantly (as in going
817 directly from a positive voltage to the equivalent negative voltage)
818 do not change velocity instantly, and it take some time for the object
819 to slow down and move in the opposite direction. This result in a
820 more smooth movement wave form, as the axis in question were vibrating
821 back and forth. When the axis reached the target speed in the
822 opposing direction, the auto tuner change direction again. After
823 several of these changes, the average time delay between the &#39;peaks&#39;
824 and &#39;valleys&#39; of this movement graph is then used to calculate
825 proposed values for Pgain, Igain and Dgain, and insert them into the
826 HAL model to use by the pid controller. The auto tuned settings are
827 not great, but htye work a lot better than the values I had been able
828 to cook up on my own, at least for the horizontal X and Y axis. But I
829 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
830 controllers error out if the voltage change too quickly. I&#39;ve been
831 less lucky with the Z axis, which is moving a heavy object up and
832 down, and seem to confuse the algorithm. The Z axis movement became a
833 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
834 gravitational drag, but I will have to work a lot more on the Z axis
835 PID values.&lt;/p&gt;
836
837 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
838 tuning. Lets say the HAL configuration in question load the PID
839 component for X, Y and Z like this:&lt;/p&gt;
840
841 &lt;blockquote&gt;&lt;pre&gt;
842 loadrt pid names=pid.x,pid.y,pid.z
843 &lt;/pre&gt;&lt;/blockquote&gt;
844
845 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
846 look like this:&lt;/p&gt;
847
848 &lt;blockquote&gt;&lt;pre&gt;
849 loadrt at_pid names=pid.x,pid.y,pid.z
850 &lt;/pre&gt;&lt;/blockquote&gt;
851
852 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
853 components are referenced by name. If the component had used count=3
854 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
855
856 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
857 range, to make sure it do not hit anything when it start moving back
858 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
859 output range. I used 0.1 as my initial value. Next, assign 1 to the
860 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
861 part and feed 0 to the output pin, which in my case initially caused a
862 lot of drift. In my case it proved to be a good idea with X and Y to
863 tune the motor driver to make sure 0 voltage stopped the motor
864 rotation. On the other hand, for the Z axis this proved to be a bad
865 idea, so it will depend on your setup. It might help to set the
866 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
867 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
868 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
869 your axis will vibrate for a few seconds and when it is done, new
870 values for Pgain, Igain and Dgain will be active. To test them,
871 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
872 machine to suddenly jerk as it bring the axis back to its commanded
873 position, which it might have drifted away from during tuning. To
874 summarize with some halcmd lines:&lt;/p&gt;
875
876 &lt;blockquote&gt;&lt;pre&gt;
877 setp pid.x.tune-effort 0.1
878 setp pid.x.tune-mode 1
879 setp pid.x.tune-start 1
880 # wait for the tuning to complete
881 setp pid.x.tune-mode 0
882 &lt;/pre&gt;&lt;/blockquote&gt;
883
884 &lt;p&gt;After doing this task quite a few times while trying to figure out
885 how to properly tune the PID controllers on the machine in, I decided
886 to figure out if this process could be automated, and wrote a script
887 to do the entire tuning process from power on. The end result will
888 ensure the machine is powered on and ready to run, home all axis if it
889 is not already done, check that the extra tuning pins are available,
890 move the axis to its mid point, run the auto tuning and re-enable the
891 pid controller when it is done. It can be run several times. Check
892 out the
893 &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;
894 script on github if you want to learn how it is done.&lt;/p&gt;
895
896 &lt;p&gt;My hope is that this little adventure can inspire someone who know
897 more about motor PID controller tuning can implement even better
898 algorithms for automatic PID tuning in LinuxCNC, making life easier
899 for both me and all the others that want to use LinuxCNC but lack the
900 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
901
902 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
903 activities, please send Bitcoin donations to my address
904 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
905 </description>
906 </item>
907
908 <item>
909 <title>LinuxCNC translators life just got a bit easier</title>
910 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
911 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
912 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
913 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
914 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
915 proposed to change the documentation build system make life easier for
916 translators. The original system consisted of independently written
917 documentation files for each language, with no automated way to track
918 changes done in other translations and no help for the translators to
919 know how much was left to translated. By using
920 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
921 files from the English documentation, this can be improved. A small
922 team of LinuxCNC contributors got together and today our labour
923 finally payed off. Since a few hours ago, it is now possible to
924 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
925 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
926
927 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
928 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
929
930 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
931 activities, please send Bitcoin donations to my address
932 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
933 </description>
934 </item>
935
936 <item>
937 <title>geteltorito make CD firmware upgrades a breeze</title>
938 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
939 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
940 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
941 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
942 located the firmware download page from Lenovo (which annoyingly do
943 not allow access via Tor, forcing me to hand them more personal
944 information that I would like). The
945 &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
946 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
947 when all I got available is a USB memory stick. I tried booting the
948 ISO as a USB stick, but this did not work. But genisoimage came to
949 the rescue.&lt;/p&gt;
950
951 &lt;P&gt;The geteltorito program in
952 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
953 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
954 USB stick using a simple command line recipe, which I then can write
955 to the most recently inserted USB stick:&lt;/p&gt;
956
957 &lt;blockquote&gt;&lt;pre&gt;
958 geteltorito -o usbstick.img lenovo-firmware.iso
959 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
960 &lt;/pre&gt;&lt;/blockquote&gt;
961
962 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
963 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
964 </description>
965 </item>
966
967 <item>
968 <title>Run your industrial metal working machine using Debian?</title>
969 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
970 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
971 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
972 <description>&lt;p&gt;After many months of hard work by the good people involved in
973 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
974 system was accepted Sunday
975 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
976 Once it was available from Debian, I was surprised to discover from
977 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
978 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
979 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
980 be a good place to check out, but sadly is not working when visiting
981 via Tor.&lt;/p&gt;
982
983 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
984 Wikipedia quote is in place?&lt;/p&gt;
985
986 &lt;blockquote&gt;
987 &quot;LinuxCNC is a software system for numerical control of
988 machines such as milling machines, lathes, plasma cutters, routers,
989 cutting machines, robots and hexapods. It can control up to 9 axes or
990 joints of a CNC machine using G-code (RS-274NGC) as input. It has
991 several GUIs suited to specific kinds of usage (touch screen,
992 interactive development).&quot;
993 &lt;/blockquote&gt;
994
995 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
996 page indicate that it can only work with hard real time kernel
997 features, it can also work with the user space soft real time features
998 provided by the Debian kernel.
999 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
1000 available from Github. The last few months I&#39;ve been involved in the
1001 translation setup for the program and documentation. Translators are
1002 most welcome to
1003 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
1004 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
1005
1006 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1007 activities, please send Bitcoin donations to my address
1008 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1009 </description>
1010 </item>
1011
1012 <item>
1013 <title>Debian still an excellent choice for Lego builders</title>
1014 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
1015 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
1016 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
1017 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
1018 the packages under the team umbrella has been updated to fix
1019 packaging, lintian issues and BTS reports. In addition, a new and
1020 inspiring team member appeared on both the
1021 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
1022 Team mailing list&lt;/a&gt; and
1023 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
1024 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
1025 Mindstorms programming, check out the
1026 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
1027 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
1028
1029 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
1030 even the first one in more than ten years, and old upstreams was
1031 released with new ones. There are still a lot of work left, and the
1032 team welcome more members to help us make sure Debian is the Linux
1033 distribution of choice for Lego builders. If you want to contribute,
1034 join us in the IRC channel and become part of
1035 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
1036 Salsa&lt;/a&gt;.&lt;/p&gt;
1037
1038 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1039 activities, please send Bitcoin donations to my address
1040 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1041 </description>
1042 </item>
1043
1044 <item>
1045 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
1046 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
1047 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
1048 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
1049 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
1050 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
1051 I am not sure which one of these are completely proof read, but the
1052 complete book is available in these languages:
1053
1054 &lt;ul&gt;
1055
1056 &lt;li&gt;English&lt;/li&gt;
1057 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
1058 &lt;li&gt;German&lt;/li&gt;
1059 &lt;li&gt;Indonesian&lt;/li&gt;
1060 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
1061 &lt;li&gt;Spanish&lt;/li&gt;
1062
1063 &lt;/ul&gt;
1064
1065 &lt;p&gt;This is the list of languages more than 70% complete, in other
1066 words with not too much left to do:&lt;/p&gt;
1067
1068 &lt;ul&gt;
1069
1070 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
1071 &lt;li&gt;French - 79%&lt;/li&gt;
1072 &lt;li&gt;Italian - 79%&lt;/li&gt;
1073 &lt;li&gt;Japanese - 77%&lt;/li&gt;
1074 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
1075 &lt;li&gt;Persian - 71%&lt;/li&gt;
1076
1077 &lt;/ul&gt;
1078
1079 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
1080
1081 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
1082
1083 &lt;ul&gt;
1084
1085 &lt;li&gt;Russian - 63%&lt;/li&gt;
1086 &lt;li&gt;Swedish - 53%&lt;/li&gt;
1087 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
1088 &lt;li&gt;Catalan - 45%&lt;/li&gt;
1089
1090 &lt;/ul&gt;
1091
1092 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
1093
1094 &lt;ul&gt;
1095
1096 &lt;li&gt;Dutch - 26%&lt;/li&gt;
1097 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
1098 &lt;li&gt;Polish - 23%&lt;/li&gt;
1099 &lt;li&gt;Czech - 22%&lt;/li&gt;
1100 &lt;li&gt;Turkish - 18%&lt;/li&gt;
1101
1102 &lt;/ul&gt;
1103
1104 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
1105
1106 &lt;ul&gt;
1107
1108 &lt;li&gt;Korean - 4%&lt;/li&gt;
1109 &lt;li&gt;Croatian - 2%&lt;/li&gt;
1110 &lt;li&gt;Greek - 2%&lt;/li&gt;
1111 &lt;li&gt;Danish - 1%&lt;/li&gt;
1112 &lt;li&gt;Romanian - 1%&lt;/li&gt;
1113
1114 &lt;/ul&gt;
1115
1116 &lt;p&gt;If you want to help provide a Debian instruction book in your own
1117 language, visit
1118 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
1119 to contribute to the translations.&lt;/p&gt;
1120
1121 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1122 activities, please send Bitcoin donations to my address
1123 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1124 </description>
1125 </item>
1126
1127 <item>
1128 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
1129 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
1130 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
1131 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
1132 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
1133 others, the decentralized communication platform
1134 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
1135 (earlier known as Ring), managed to get
1136 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
1137 into Debian Testing. Several of its dependencies has caused build and
1138 propagation problems, which all seem to be solved now.&lt;/p&gt;
1139
1140 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
1141 bittorrent is decentralized, I first of all like how it is not
1142 connected to external IDs like phone numbers. This allow me to set up
1143 computers to send me notifications using Jami without having to find
1144 get a phone number for each computer. Automatic notification via Jami
1145 is also made trivial thanks to the provided client side API (as a DBus
1146 service). Here is my bourne shell script demonstrating how to let any
1147 system send a message to any Jami address. It will create a new
1148 identity before sending the message, if no Jami identity exist
1149 already:&lt;/p&gt;
1150
1151 &lt;p&gt;&lt;pre&gt;
1152 #!/bin/sh
1153 #
1154 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
1155 #
1156 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
1157 # missing.
1158 #
1159 # License: GPL v2 or later at your choice
1160 # Author: Petter Reinholdtsen
1161
1162
1163 if [ -z &quot;$HOME&quot; ] ; then
1164 echo &quot;error: missing \$HOME, required for dbus to work&quot;
1165 exit 1
1166 fi
1167
1168 # First, get dbus running if not already running
1169 DBUSLAUNCH=/usr/bin/dbus-launch
1170 PIDFILE=/run/asterisk/dbus-session.pid
1171 if [ -e $PIDFILE ] ; then
1172 . $PIDFILE
1173 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
1174 unset DBUS_SESSION_BUS_ADDRESS
1175 fi
1176 fi
1177 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
1178 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
1179 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;
1180 DBUS_SESSION_BUS_PID=$!
1181 (
1182 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1183 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
1184 echo export DBUS_SESSION_BUS_ADDRESS
1185 ) &gt; $PIDFILE
1186 . $PIDFILE
1187 fi &amp;
1188
1189 dringop() {
1190 part=&quot;$1&quot;; shift
1191 op=&quot;$1&quot;; shift
1192 dbus-send --session \
1193 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1194 }
1195
1196 dringopreply() {
1197 part=&quot;$1&quot;; shift
1198 op=&quot;$1&quot;; shift
1199 dbus-send --session --print-reply \
1200 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1201 }
1202
1203 firstaccount() {
1204 dringopreply ConfigurationManager getAccountList | \
1205 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
1206 }
1207
1208 account=$(firstaccount)
1209
1210 if [ -z &quot;$account&quot; ] ; then
1211 echo &quot;Missing local account, trying to create it&quot;
1212 dringop ConfigurationManager addAccount \
1213 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
1214 account=$(firstaccount)
1215 if [ -z &quot;$account&quot; ] ; then
1216 echo &quot;unable to create local account&quot;
1217 exit 1
1218 fi
1219 fi
1220
1221 # Not using dringopreply to ensure $2 can contain spaces
1222 dbus-send --print-reply --session \
1223 --dest=cx.ring.Ring \
1224 /cx/ring/Ring/ConfigurationManager \
1225 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1226 string:&quot;$account&quot; string:&quot;$1&quot; \
1227 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
1228 &lt;/pre&gt;&lt;/p&gt;
1229
1230 &lt;p&gt;If you want to check it out yourself, visit the
1231 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
1232 more, and install the latest Jami client from Debian Unstable or
1233 Testing.&lt;/p&gt;
1234
1235 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1236 activities, please send Bitcoin donations to my address
1237 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1238 </description>
1239 </item>
1240
1241 <item>
1242 <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
1243 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1244 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1245 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
1246 <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;
1247
1248 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
1249 became the first translation published on paper of the new Buster
1250 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1251 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
1252 some days ago, and it looked good, so now the book is approved for
1253 general distribution. This updated paperback edition &lt;a
1254 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
1255 lulu.com&lt;/a&gt;. The book is also available for download in electronic
1256 form as PDF, EPUB and Mobipocket, and can also be
1257 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
1258
1259 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
1260 which concludes several months of work by several volunteers. The
1261 number of Linux related books published in Norwegian are few, and I
1262 really hope this one will gain many readers, as it is packed with deep
1263 knowledge on Linux and the Debian ecosystem. The book will be
1264 available for various Internet book stores like Amazon and Barnes &amp;
1265 Noble soon, but I recommend buying
1266 &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
1267 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
1268
1269 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1270 activities, please send Bitcoin donations to my address
1271 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1272 </description>
1273 </item>
1274
1275 <item>
1276 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
1277 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
1278 <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>
1279 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
1280 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
1281 of the Norwegian translation for
1282 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1283 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
1284 reading, I consider the proof reading complete enough for us to move
1285 to the next step, and have asked for the print version to be prepared
1286 and sent of to the print on demand service lulu.com. While it is
1287 still not to late if you find any incorrect translations on
1288 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1289 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
1290 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
1291 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
1292
1293 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
1294 with links available from the web site for the book linked to above.
1295 I hope a lot of readers find it useful.&lt;/p&gt;
1296
1297 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1298 activities, please send Bitcoin donations to my address
1299 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1300 </description>
1301 </item>
1302
1303 <item>
1304 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
1305 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1306 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1307 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
1308 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
1309 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1310 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
1311 new and updated version based on Buster is getting ready. Work on the
1312 updated Norwegian Bokmål edition has been going on for a few months
1313 now, and yesterday, we reached the first mile stone, with 100% of the
1314 texts being translated. A lot of proof reading remains, of course,
1315 but a major step towards a new edition has been taken.&lt;/p&gt;
1316
1317 &lt;p&gt;The book is translated by volunteers, and we would love to get some
1318 help with the proof reading. The translation uses
1319 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1320 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
1321 submit improvements and suggestions. There is also a proof readers
1322 PDF available on request, get in touch if you want to help out that
1323 way.&lt;/p&gt;
1324
1325 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1326 activities, please send Bitcoin donations to my address
1327 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1328 </description>
1329 </item>
1330
1331 <item>
1332 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
1333 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
1334 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
1335 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
1336 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
1337 User Group&lt;/a&gt;, I have the pleasure of receiving the
1338 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
1339 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
1340 several times a year. I rarely have time to read all the articles,
1341 but try to at least skim through them all as there is a lot of nice
1342 knowledge passed on there. I even carry the latest issue with me most
1343 of the time to try to get through all the articles when I have a few
1344 spare minutes.&lt;/p&gt;
1345
1346 &lt;p&gt;The other day I came across a nice article titled
1347 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
1348 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
1349 marvellous idea I hope can make it all the way into the POSIX standard.
1350 The idea is as simple as it is powerful. By introducing a new
1351 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1352 handle setting up TLS connections, one both make it trivial to add TLS
1353 support to any program currently using the POSIX socket API, and gain
1354 system wide control over certificates, TLS versions and encryption
1355 systems used. Instead of doing this:&lt;/p&gt;
1356
1357 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1358 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1359 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1360
1361 &lt;p&gt;the program code would be doing this:&lt;p&gt;
1362
1363 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1364 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1365 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1366
1367 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
1368 would normally modify only 5-10 lines in the code, which is amazing
1369 when compared to using for example the OpenSSL API.&lt;/p&gt;
1370
1371 &lt;p&gt;The project has set up the
1372 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
1373 web site to spread the idea, and the code for a kernel module and the
1374 associated system daemon is available from two github repositories:
1375 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
1376 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
1377 Unfortunately there is no explicit license information with the code,
1378 so its copyright status is unclear. A
1379 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
1380 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
1381
1382 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
1383 understand why it is an advantage to implement this as a kernel module
1384 and system wide service daemon, but can not help to think that it
1385 would be a lot easier to get projects to move to this way of setting
1386 up TLS if it was done with a user space approach where programs
1387 wanting to use this API approach could just link with a wrapper
1388 library.&lt;/p&gt;
1389
1390 &lt;p&gt;I recommend you check out this simple and powerful approach to more
1391 secure network connections. :)&lt;/p&gt;
1392
1393 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1394 activities, please send Bitcoin donations to my address
1395 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1396 </description>
1397 </item>
1398
1399 <item>
1400 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
1401 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
1402 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
1403 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
1404 <description>&lt;p&gt;Half a year ago,
1405 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
1406 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
1407 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
1408 handle both messages, audio and video. It uses distributed hash
1409 tables instead of central infrastructure to connect its users to each
1410 other, which in my book is a plus. I mentioned briefly that it could
1411 also work as a SIP client, which came in handy when the higher
1412 educational sector in Norway started to promote Zoom as its video
1413 conferencing solution. I am reluctant to use the official Zoom client
1414 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
1415 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
1416 to check the security) and benchmark it, and thus prefer to connect to
1417 Zoom meetings with free software clients.&lt;/p&gt;
1418
1419 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
1420 password set on the room. The Jami daemon leak memory like crazy
1421 (approximately 1 GiB a minute) when I am connected to the video
1422 conference, so I had to restart the client every 7-10 minutes, which
1423 is not great. I tried to get other SIP Linux clients to work
1424 without success, so I decided I would have to live with this wart
1425 until someone managed to fix the leak in the dring code base. But
1426 another problem showed up once the rooms were password protected. I
1427 could not get my dial tone signaling through from Jami to Zoom, and
1428 dial tone signaling is used to enter the password when connecting to
1429 Zoom. I tried a lot of different permutations with my Jami and
1430 Asterisk setup to try to figure out why the signaling did not get
1431 through, only to finally discover that the fundamental problem seem to
1432 be that Zoom is simply not able to receive dial tone signaling when
1433 connecting via SIP. There seem to be nothing wrong with the Jami and
1434 Asterisk end, it is simply broken in the Zoom end. I got help from a
1435 very skilled VoIP engineer figuring out this last part. And being a
1436 very skilled engineer, he was also able to locate a solution for me.
1437 Or to be exact, a workaround that solve my initial problem of
1438 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
1439
1440 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
1441 trick is already
1442 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
1443 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
1444 password. What is most surprising about this is that the
1445 automatically generated email from Zoom with instructions on how to
1446 connect via SIP do not mention this. The SIP address to use normally
1447 consist of the room ID (a number), an @ character and the IP address
1448 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1449 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
1450 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
1451 can both enter password, control the layout (full screen, active
1452 presence and gallery) and specify the host key to start the meeting.
1453 The full SIP address entered into Jami to provide the password will
1454 then look like this (all using made up numbers):&lt;/p&gt;
1455
1456 &lt;p&gt;&lt;blockquote&gt;
1457 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
1458 &lt;/blockquote&gt;&lt;/p&gt;
1459
1460 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
1461 recommend this setup to others. :)&lt;/p&gt;
1462
1463 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1464 activities, please send Bitcoin donations to my address
1465 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1466 </description>
1467 </item>
1468
1469 <item>
1470 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
1471 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
1472 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
1473 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
1474 <description>&lt;p&gt;The curiosity got the better of me when
1475 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
1476 reported&lt;/a&gt; that New Jersey was desperately looking for
1477 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
1478 and a few days later it was reported that
1479 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
1480 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
1481
1482 &lt;p&gt;I thus decided to have a look at free software alternatives to
1483 learn COBOL, and had the pleasure to find
1484 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
1485 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
1486 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
1487 transforming COBOL code to C or C++ before giving it to GCC or Visual
1488 Studio to build binaries.&lt;/p&gt;
1489
1490 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
1491 quick response, and also was happy to see a new Debian maintainer
1492 taking over when the original one recently asked to be replaced. A
1493 new Debian upload was done as recently as yesterday.&lt;/p&gt;
1494
1495 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
1496 introduction and make and run simple COBOL programs. It was fun to
1497 learn a new programming language. If you want to test for yourself,
1498 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
1499 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
1500
1501 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
1502 standard compliant it is, but it claim to pass most tests from COBOL
1503 test suite, which sound good to me. It is nice to know it is possible
1504 to learn COBOL using software without any usage restrictions, and I am
1505 very happy such nice free software project as this is available. If
1506 you as me is curious about COBOL, check it out.&lt;/p&gt;
1507
1508 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1509 activities, please send Bitcoin donations to my address
1510 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1511 </description>
1512 </item>
1513
1514 <item>
1515 <title>Jami/Ring, finally functioning peer to peer communication client</title>
1516 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
1517 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
1518 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
1519 <description>&lt;p&gt;Some years ago, in 2016, I
1520 &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
1521 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
1522 It would provide messaging without any central server coordinating the
1523 system and without requiring all users to register a phone number or
1524 own a mobile phone. Back then, I could not get it to work, and put it
1525 aside until it had seen more development. A few days ago I decided to
1526 give it another try, and am happy to report that this time I am able
1527 to not only send and receive messages, but also place audio and video
1528 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
1529
1530 &lt;p&gt;The Ring system changed name earlier this year to
1531 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
1532 tried doing web search for &#39;ring&#39; when I discovered it for the first
1533 time, and can only applaud this change as it is impossible to find
1534 something called Ring among the noise of other uses of that word. Now
1535 you can search for &#39;jami&#39; and this client and
1536 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
1537 least on duckduckgo.&lt;/p&gt;
1538
1539 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
1540 calls, and try to send them directly between the communicating parties
1541 if possible. If this proves impossible (for example if both ends are
1542 behind NAT), it will use a central SIP TURN server maintained by the
1543 Jami project. Jami can also be a normal SIP client. If the SIP
1544 server is unencrypted, the audio and video calls will also be
1545 unencrypted. This is as far as I know the only case where Jami will
1546 do anything without encryption.&lt;/p&gt;
1547
1548 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
1549 Android, iOS, and Android TV. It is included in Debian already. Jami
1550 also work for those using F-Droid without any Google connections,
1551 while Signal do not.
1552 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
1553 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
1554 distributed hash table (DHT) system (similar to BitTorrent) running
1555 over UDP. On one of the networks I use, I discovered Jami failed to
1556 work. I tracked this down to the fact that incoming UDP packages
1557 going to ports 1-49999 were blocked, and the DHT would pick a random
1558 port and end up in the low range most of the time. After talking to
1559 the developers, I solved this by enabling the dhtproxy in the
1560 settings, thus using TCP to talk to a central DHT proxy instead of
1561
1562 peering directly with others. I&#39;ve been told the developers are
1563 working on allowing DHT to use TCP to avoid this problem. I also ran
1564 into a problem when trying to talk to the version of Ring included in
1565 Debian Stable (Stretch). Apparently the protocol changed between
1566 beta2 and the current version, making these clients incompatible.
1567 Hopefully the protocol will not be made incompatible in the
1568 future.&lt;/p&gt;
1569
1570 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
1571 came across another communication platform I have not tested yet. The
1572 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
1573 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
1574 become the topic of a future blog post.&lt;/p&gt;
1575
1576 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1577 activities, please send Bitcoin donations to my address
1578 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1579 </description>
1580 </item>
1581
1582 <item>
1583 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
1584 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
1585 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
1586 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
1587 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
1588 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
1589 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
1590 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1591 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1592 nye versjonen kom på nyåret, og ble
1593 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
1594 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
1595 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1596 måtte justeres, men ikke noe alvorlig. Har oppdatert
1597 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
1598 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
1599
1600 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1601 å spille for oss som liker slikt. :)&lt;/p&gt;
1602
1603 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1604 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1605 til min adresse
1606 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
1607 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1608 </description>
1609 </item>
1610
1611 <item>
1612 <title>Debian now got everything you need to program Micro:bit</title>
1613 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
1614 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
1615 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
1616 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
1617 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
1618 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
1619 thanks to the hard work of Nick Morrott and the Debian python
1620 packaging team. The micro:bit project recommend the mu-editor to
1621 program the microcomputer, as this editor will take care of all the
1622 machinery required to injekt/flash micropython alongside the program
1623 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
1624
1625 &lt;p&gt;There are three main pieces involved. The first to enter Debian
1626 was
1627 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
1628 which was accepted into the archive 2019-01-12. The next one was
1629 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
1630 showed up 2019-01-13. The final and hardest part to to into the
1631 archive was
1632 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
1633 which needed to get its build system and dependencies into Debian
1634 before it was accepted 2019-01-20. The last one is already in Debian
1635 Unstable and should enter Debian Testing / Buster in three days. This
1636 all allow any user of the micro:bit to get going by simply running
1637 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
1638 Buster is released as stable, all the users of Debian stable will be
1639 catered for.&lt;/p&gt;
1640
1641 &lt;p&gt;As a minor final touch, I added rules to
1642 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
1643 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
1644 package. This make sure any user of the isenkram desktop daemon will
1645 get a popup suggesting to install mu-editor then the USB cable from
1646 the micro:bit is inserted for the first time.&lt;/p&gt;
1647
1648 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
1649
1650 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1651 activities, please send Bitcoin donations to my address
1652 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1653 </description>
1654 </item>
1655
1656 <item>
1657 <title>Learn to program with Minetest on Debian</title>
1658 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
1659 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
1660 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
1661 <description>&lt;p&gt;A fun way to learn how to program
1662 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
1663 instructions in the book
1664 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
1665 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
1666 who like to play with Minecraft. The book uses a Python library to
1667 talk to a TCP/IP socket with an API accepting build instructions and
1668 providing information about the current players in a Minecraft world.
1669 The TCP/IP API was first created for the Minecraft implementation for
1670 Raspberry Pi, and has since been ported to some server versions of
1671 Minecraft. The book contain recipes for those using Windows, MacOSX
1672 and Raspian. But a little known fact is that you can follow the same
1673 recipes using the free software construction game
1674 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1675
1676 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1677 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1678 use the Python programs coded to talk to Minecraft with Minetest too.
1679 I
1680 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1681 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1682 FTP masters NEW queue, learning to program Python with Minetest on
1683 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1684 maintained as part of the Debian Games team, and
1685 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1686 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1687 Salsa.&lt;/p&gt;
1688
1689 &lt;p&gt;You will most likely need to install several of the Minetest
1690 modules in Debian for the examples included with the library to work
1691 well, as there are several blocks used by the example scripts that are
1692 provided via modules in Minetest. Without the required blocks, a
1693 simple stone block is used instead. My initial testing with a analog
1694 clock did not get gold arms as instructed in the python library, but
1695 instead used stone arms.&lt;/p&gt;
1696
1697 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1698 Minecraft, but were unable to find any working recipes. The
1699 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1700 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1701 working with a standalone Minecraft server setup. Are there any
1702 options to use with the normal desktop version?&lt;/p&gt;
1703
1704 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1705 activities, please send Bitcoin donations to my address
1706 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1707 </description>
1708 </item>
1709
1710 <item>
1711 <title>Time for an official MIME type for patches?</title>
1712 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1713 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1714 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1715 <description>&lt;p&gt;As part of my involvement in
1716 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1717 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1718 emails into a test instance of the archive to see how well this would
1719 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1720 notmuch email database&lt;/a&gt;, all public emails sent to me via
1721 @lists.debian.org, giving me a set of around 216 000 emails to import.
1722 In the process, I had a look at the various attachments included in
1723 these emails, to figure out what to do with attachments, and noticed
1724 that one of the most common attachment formats do not have
1725 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1726 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1727 diff, ie the input for patch, is on the top 10 list of formats
1728 included in these emails. At the moment people seem to use either
1729 text/x-patch or text/x-diff, but neither is officially registered. It
1730 would be better if one official MIME type were registered and used
1731 everywhere.&lt;/p&gt;
1732
1733 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1734 up the topic on
1735 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1736 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1737 which MIME type to use as the official for patch files, or involved in
1738 making software using a MIME type for patches, perhaps you would like
1739 to join the discussion?&lt;/p&gt;
1740
1741 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1742 activities, please send Bitcoin donations to my address
1743 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1744 </description>
1745 </item>
1746
1747 <item>
1748 <title>Automatic Google Drive sync using grive in Debian</title>
1749 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1750 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1751 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1752 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1753 rescue the remains, I helped set up automatic sync with Google Drive.
1754 I did not find any sensible Debian package handling this
1755 automatically, so I rebuild the grive2 source from
1756 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1757 task and added a autostart desktop entry and a small shell script to
1758 run in the background while the user is logged in to do the sync.
1759 Here is a sketch of the setup for future reference.&lt;/p&gt;
1760
1761 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1762 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1763 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1764 to start the sync when the user log in:&lt;/p&gt;
1765
1766 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1767 [Desktop Entry]
1768 Name=Google drive autosync
1769 Type=Application
1770 Exec=/home/user/bin/grive-sync
1771 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1772
1773 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1774 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1775
1776 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1777 #!/bin/sh
1778 set -e
1779 cd ~/
1780 cleanup() {
1781 if [ &quot;$syncpid&quot; ] ; then
1782 kill $syncpid
1783 fi
1784 }
1785 trap cleanup EXIT INT QUIT
1786 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1787 syncpdi=$!
1788 while true; do
1789 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1790 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1791 exit 1
1792 fi
1793 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1794 /usr/lib/grive/grive-sync.sh sync googledrive
1795 fi
1796 sleep 300
1797 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
1798 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1799
1800 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
1801 GNU GPL v2 licensed (or any later version, at your leisure), but I
1802 doubt this code is possible to claim copyright on.&lt;/p&gt;
1803
1804 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1805 activities, please send Bitcoin donations to my address
1806 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1807 </description>
1808 </item>
1809
1810 <item>
1811 <title>Using the Kodi API to play Youtube videos</title>
1812 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
1813 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
1814 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
1815 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
1816 tell it to play a youtube URL I received in a chat, without having to
1817 insert search terms using the on-screen keyboard. After searching the
1818 web for API access to the Youtube plugin and testing a bit, I managed
1819 to find a recipe that worked. If you got a kodi instance with its API
1820 available from http://kodihost/jsonrpc, you can try the following to
1821 have check out a nice cover band.&lt;/p&gt;
1822
1823 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
1824 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
1825 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
1826 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
1827 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1828
1829 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
1830 first argument. It can now handle direct video links, youtube links
1831 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
1832 Chromecast. :)&lt;/p&gt;
1833
1834 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1835 activities, please send Bitcoin donations to my address
1836 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1837 </description>
1838 </item>
1839
1840 <item>
1841 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
1842 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
1843 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
1844 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
1845 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
1846 with my family using a self hosted solution, as it is unacceptable to
1847 place images from my personal life under the control of strangers
1848 working for data hoarders like Google or Dropbox. The last few days I
1849 have drafted an approach that might work out, and I would like to
1850 share it with you. I would like to publish images on a server under
1851 my control, and point some Internet connected display units using some
1852 free and open standard to the images I published. As my primary
1853 language is not limited to ASCII, I need to store metadata using
1854 UTF-8. Many years ago, I hoped to find a digital photo frame capable
1855 of reading a RSS feed with image references (aka using the
1856 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
1857 of such frames. In the end I gave up that approach.&lt;/p&gt;
1858
1859 &lt;p&gt;Some months ago, I discovered that
1860 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
1861 read images from a RSS feed, and used it to set up a screen saver on
1862 my home info screen, showing images from the Daily images feed from
1863 NASA. This proved to work well. More recently I discovered that
1864 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
1865 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
1866 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
1867 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
1868 screen saver capable of reading a RSS feed with images and news. For
1869 fun, I used it this summer to test Kodi on my parents TV by hooking up
1870 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1871 screen saver showing selected pictures from my selection.&lt;/p&gt;
1872
1873 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
1874 a RSS feed for the Kodi instance. I adjusted my &lt;a
1875 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
1876 /var/www/html/privatepictures/, wrote a small Perl script to extract
1877 title and description metadata from the photo files and generate the
1878 RSS file. I ended up using Perl instead of python, as the
1879 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1880 tags I ended up using, while python3-exif did not. The relevant EXIF
1881 tags only support ASCII, so I had to find better alternatives. XMP
1882 seem to have the support I need.&lt;/p&gt;
1883
1884 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
1885 use tags that can be easily added/updated using normal free software
1886 photo managing software. I ended up using the tags set using this
1887 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
1888
1889 &lt;blockquote&gt;&lt;pre&gt;
1890 exiftool -headline=&#39;The RSS image title&#39; \
1891 -description=&#39;The RSS image description.&#39; \
1892 -subject+=for-family photo.jpeg
1893 &lt;/pre&gt;&lt;/blockquote&gt;
1894
1895 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
1896 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
1897 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
1898 shared with my family. Images with this keyword set are located and
1899 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
1900
1901 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
1902 suggestions.&lt;/p&gt;
1903
1904 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1905 activities, please send Bitcoin donations to my address
1906 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1907 </description>
1908 </item>
1909
1910 <item>
1911 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
1912 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
1913 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
1914 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
1915 <description>&lt;p&gt;Last night, I wrote
1916 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
1917 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
1918 During the day I received valuable feedback, and thanks to the
1919 suggestions I have been able to rewrite the recipe into a much simpler
1920 approach requiring no setup at all. It is a single script that take
1921 care of it all.&lt;/p&gt;
1922
1923 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
1924 desktop and stream it to Kodi. This fixed the video quality issue I
1925 saw initially. It further removes the need to add a m3u file on the
1926 Kodi machine, as it instead connects to
1927 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
1928 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
1929 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1930 the script below, run it with the DNS name or IP address of the kodi
1931 server to stream to as the only argument, and watch your screen show
1932 up on the Kodi screen. Note, it depend on multicast on the local
1933 network, so if you need to stream outside the local network, the
1934 script must be modified. Also note, I have no idea if audio work, as
1935 I only care about the picture part.&lt;/p&gt;
1936
1937 &lt;blockquote&gt;&lt;pre&gt;
1938 #!/bin/sh
1939 #
1940 # Stream the Linux desktop view to Kodi. See
1941 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1942 # for backgorund information.
1943
1944 # Make sure the stream is stopped in Kodi and the gstreamer process is
1945 # killed if something go wrong (for example if curl is unable to find the
1946 # kodi server). Do the same when interrupting this script.
1947 kodicmd() {
1948 host=&quot;$1&quot;
1949 cmd=&quot;$2&quot;
1950 params=&quot;$3&quot;
1951 curl --silent --header &#39;Content-Type: application/json&#39; \
1952 --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; \
1953 &quot;http://$host/jsonrpc&quot;
1954 }
1955 cleanup() {
1956 if [ -n &quot;$kodihost&quot; ] ; then
1957 # Stop the playing when we end
1958 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
1959 jq .result[].playerid)
1960 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
1961 fi
1962 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
1963 kill &quot;$gstpid&quot;
1964 fi
1965 }
1966 trap cleanup EXIT INT
1967
1968 if [ -n &quot;$1&quot; ]; then
1969 kodihost=$1
1970 shift
1971 else
1972 kodihost=kodi.local
1973 fi
1974
1975 mcast=239.255.0.1
1976 mcastport=1234
1977 mcastttl=1
1978
1979 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
1980 cut -d&quot; &quot; -f2|head -1)
1981 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1982 videoconvert ! queue2 ! \
1983 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1984 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1985 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1986 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
1987 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1988 &gt; /dev/null 2&gt;&amp;1 &amp;
1989 gstpid=$!
1990
1991 # Give stream a second to get going
1992 sleep 1
1993
1994 # Ask kodi to start streaming using its JSON-RPC API
1995 kodicmd &quot;$kodihost&quot; Player.Open \
1996 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
1997
1998 # wait for gst to end
1999 wait &quot;$gstpid&quot;
2000 &lt;/pre&gt;&lt;/blockquote&gt;
2001
2002 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
2003
2004 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2005 activities, please send Bitcoin donations to my address
2006 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2007 </description>
2008 </item>
2009
2010 <item>
2011 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
2012 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
2013 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
2014 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
2015 <description>&lt;p&gt;PS: See
2016 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
2017 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
2018
2019 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
2020 my projector connected to Kodi. I sadly had to admit that I had no
2021 idea, as it was a task I never had tried. Since then, I have been
2022 looking for a way to do so, preferable without much extra software to
2023 install on either side. Today I found a way that seem to kind of
2024 work. Not great, but it is a start.&lt;/p&gt;
2025
2026 &lt;p&gt;I had a look at several approaches, for example
2027 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
2028 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
2029 local storage enough to store the stream locally. This is not going
2030 to work well for me, lacking enough free space, and it would
2031 impossible for my friend to get working.&lt;/p&gt;
2032
2033 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
2034 video stream that Kodi could play. Preferably using
2035 broadcast/multicast, to avoid having to change any setup on the Kodi
2036 side when starting such stream. Unfortunately, the only recipe I
2037 could find using multicast used the rtp protocol, and this protocol
2038 seem to not be supported by Kodi.&lt;/p&gt;
2039
2040 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
2041 have to specify the IP address of the streaming machine in both the
2042 sending command and the file on the Kodi server. But it is showing my
2043 desktop, and thus allow us to have a shared look on the big screen at
2044 the programs I work on.&lt;/p&gt;
2045
2046 &lt;p&gt;I did not spend much time investigating codeces. I combined the
2047 rtp and rtsp recipes from
2048 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
2049 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
2050 this working on the desktop/streaming end.&lt;/p&gt;
2051
2052 &lt;blockquote&gt;&lt;pre&gt;
2053 vlc screen:// --sout \
2054 &#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;
2055 &lt;/pre&gt;&lt;/blockquote&gt;
2056
2057 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
2058 same IP address:&lt;/p&gt;
2059
2060 &lt;blockquote&gt;&lt;pre&gt;
2061 echo rtsp://192.168.11.4:8080/test.sdp \
2062 &gt; /storage/videos/screenstream.m3u
2063 &lt;/pre&gt;&lt;/blockquote&gt;
2064
2065 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
2066 as I can tell the IP must be hardcoded for this to work. In other
2067 words, if someone elses machine is going to do the steaming, you have
2068 to update screenstream.m3u on the Kodi machine and adjust the vlc
2069 recipe. To get started, locate the file in Kodi and select the m3u
2070 file while the VLC stream is running. The desktop then show up in my
2071 big screen. :)&lt;/p&gt;
2072
2073 &lt;p&gt;When using the same technique to stream a video file with audio,
2074 the audio quality is really bad. No idea if the problem is package
2075 loss or bad parameters for the transcode. I do not know VLC nor Kodi
2076 enough to tell.&lt;/p&gt;
2077
2078 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
2079 succestions and reminded me about an important step. The &quot;screen:&quot;
2080 input source is only available once the vlc-plugin-access-extra
2081 package is installed on Debian. Without it, you will see this error
2082 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
2083 for details.&quot; He further found that it is possible to drop some parts
2084 of the VLC command line to reduce the amount of hardcoded information.
2085 It is also useful to consider using cvlc to avoid having the VLC
2086 window in the desktop view. In sum, this give us this command line on
2087 the source end
2088
2089 &lt;blockquote&gt;&lt;pre&gt;
2090 cvlc screen:// --sout \
2091 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
2092 &lt;/pre&gt;&lt;/blockquote&gt;
2093
2094 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2095
2096 &lt;blockquote&gt;&lt;pre&gt;
2097 echo rtsp://192.168.11.4:8080/ \
2098 &gt; /storage/videos/screenstream.m3u
2099 &lt;/pre&gt;&lt;/blockquote&gt;
2100
2101 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
2102 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
2103 audio quality, so I guess the issue is in the input or transcoding
2104 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
2105 parameters to use more bandwidth, but it did not make a
2106 difference.&lt;/p&gt;
2107
2108 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
2109 gstreamer instead of VLC, and this proved to work great! He also
2110 provided me with the trick to get Kodi to use a multicast stream as
2111 its source. By using this monstrous oneliner, I can stream my desktop
2112 with good video quality in reasonable framerate to the 239.255.0.1
2113 multicast address on port 1234:
2114
2115 &lt;blockquote&gt;&lt;pre&gt;
2116 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
2117 videoconvert ! queue2 ! \
2118 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
2119 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
2120 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
2121 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
2122 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
2123 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
2124 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2125 &lt;/pre&gt;&lt;/blockquote&gt;
2126
2127 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2128
2129 &lt;blockquote&gt;&lt;pre&gt;
2130 echo udp://@239.255.0.1:1234 \
2131 &gt; /storage/videos/screenstream.m3u
2132 &lt;/pre&gt;&lt;/blockquote&gt;
2133
2134 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
2135 pick the one you need. This approach will of course lead to trouble
2136 if more than one source uses the same multicast port and address.
2137 Note the ttl-mc=1 setting, which limit the multicast packages to the
2138 local network. If the value is increased, your screen will be
2139 broadcasted further, one network &quot;hop&quot; for each increase (read up on
2140 multicast to learn more. :)!&lt;/p&gt;
2141
2142 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
2143 could use this VLC command to stream to the same multicast address.
2144 The image quality is way better than the rtsp approach, but gstreamer
2145 seem to be doing a better job.&lt;/p&gt;
2146
2147 &lt;blockquote&gt;&lt;pre&gt;
2148 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;
2149 &lt;/pre&gt;&lt;/blockquote&gt;
2150
2151 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2152 activities, please send Bitcoin donations to my address
2153 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2154 </description>
2155 </item>
2156
2157 <item>
2158 <title>What is the most supported MIME type in Debian in 2018?</title>
2159 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
2160 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
2161 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
2162 <description>&lt;p&gt;Five years ago,
2163 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
2164 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
2165 analysing the desktop files in all packages in the archive. Since
2166 then, the DEP-11 AppStream system has been put into production, making
2167 the task a lot easier. This made me want to repeat the measurement,
2168 to see how much things changed. Here are the new numbers, for
2169 unstable only this time:
2170
2171 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2172
2173 &lt;pre&gt;
2174 count MIME type
2175 ----- -----------------------
2176 56 image/jpeg
2177 55 image/png
2178 49 image/tiff
2179 48 image/gif
2180 39 image/bmp
2181 38 text/plain
2182 37 audio/mpeg
2183 34 application/ogg
2184 33 audio/x-flac
2185 32 audio/x-mp3
2186 30 audio/x-wav
2187 30 audio/x-vorbis+ogg
2188 29 image/x-portable-pixmap
2189 27 inode/directory
2190 27 image/x-portable-bitmap
2191 27 audio/x-mpeg
2192 26 application/x-ogg
2193 25 audio/x-mpegurl
2194 25 audio/ogg
2195 24 text/html
2196 &lt;/pre&gt;
2197
2198 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
2199 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
2200 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
2201
2202 &lt;p&gt;It is interesting to see how image formats have passed text/plain
2203 as the most announced supported MIME type. These days, thanks to the
2204 AppStream system, if you run into a file format you do not know, and
2205 want to figure out which packages support the format, you can find the
2206 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
2207 look up all packages announcing support for this format in their
2208 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
2209 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
2210 me, want to know which packages support inode/directory, you can get a
2211 list like this:&lt;/p&gt;
2212
2213 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2214 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2215 Package: anjuta
2216 Package: audacious
2217 Package: baobab
2218 Package: cervisia
2219 Package: chirp
2220 Package: dolphin
2221 Package: doublecmd-common
2222 Package: easytag
2223 Package: enlightenment
2224 Package: ephoto
2225 Package: filelight
2226 Package: gwenview
2227 Package: k4dirstat
2228 Package: kaffeine
2229 Package: kdesvn
2230 Package: kid3
2231 Package: kid3-qt
2232 Package: nautilus
2233 Package: nemo
2234 Package: pcmanfm
2235 Package: pcmanfm-qt
2236 Package: qweborf
2237 Package: ranger
2238 Package: sirikali
2239 Package: spacefm
2240 Package: spacefm
2241 Package: vifm
2242 %
2243 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2244
2245 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
2246 format is not yet supported by any package in Debian:&lt;/p&gt;
2247
2248 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2249 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2250 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
2251 %
2252 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2253
2254 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
2255 format:&lt;/p&gt;
2256
2257 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2258 % appstreamcli what-provides mimetype application/sla|grep Package
2259 Package: cura
2260 Package: meshlab
2261 Package: printrun
2262 %
2263 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2264
2265 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
2266
2267 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2268 activities, please send Bitcoin donations to my address
2269 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2270 </description>
2271 </item>
2272
2273 <item>
2274 <title>Debian APT upgrade without enough free space on the disk...</title>
2275 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
2276 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
2277 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
2278 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2279 for a while, and when I need to update it there is not enough free
2280 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
2281 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
2282 upgrade only some of the packages in one batch, until the amount of
2283 packages to download fall below the amount of free space available.
2284 Today, I had about 500 packages to upgrade, and after a while I got
2285 tired of trying to install chunks of packages manually. I concluded
2286 that I did not have the spare hours required to complete the task, and
2287 decided to see if I could automate it. I came up with this small
2288 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
2289
2290 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2291 #!/bin/sh
2292 #
2293 # Upgrade packages when the disk is too full to upgrade every
2294 # upgradable package in one lump. Fetching packages to upgrade using
2295 # apt, and then installing using dpkg, to avoid changing the package
2296 # flag for manual/automatic.
2297
2298 set -e
2299
2300 ignore() {
2301 if [ &quot;$1&quot; ]; then
2302 grep -v &quot;$1&quot;
2303 else
2304 cat
2305 fi
2306 }
2307
2308 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
2309 echo &quot;Upgrading $p&quot;
2310 apt clean
2311 apt install --download-only -y $p
2312 for f in /var/cache/apt/archives/*.deb; do
2313 if [ -e &quot;$f&quot; ]; then
2314 dpkg -i /var/cache/apt/archives/*.deb
2315 break
2316 fi
2317 done
2318 done
2319 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2320
2321 &lt;p&gt;The script will extract the list of packages to upgrade, try to
2322 download the packages needed to upgrade one package, install the
2323 downloaded packages using dpkg. The idea is to upgrade packages
2324 without changing the APT mark for the package (ie the one recording of
2325 the package was manually requested or pulled in as a dependency). To
2326 use it, simply run it as root from the command line. If it fail, try
2327 &#39;apt install -f&#39; to clean up the mess and run the script again. This
2328 might happen if the new packages conflict with one of the old
2329 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
2330
2331 &lt;p&gt;It take one option, a package to ignore in the list of packages to
2332 upgrade. The option to ignore a package is there to be able to skip
2333 the packages that are simply too large to unpack. Today this was
2334 &#39;ghc&#39;, but I have run into other large packages causing similar
2335 problems earlier (like TeX).&lt;/p&gt;
2336
2337 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
2338 alternative ways to handle this. The &quot;unattended-upgrades
2339 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
2340 each package to upgrade, and then upgrade them in order, smallest set
2341 first. It might be a better option than my above mentioned script.
2342 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
2343 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
2344
2345 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2346 activities, please send Bitcoin donations to my address
2347 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2348 </description>
2349 </item>
2350
2351 <item>
2352 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
2353 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
2354 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
2355 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
2356 <description>&lt;p&gt;A new version of the
2357 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
2358 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
2359 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2360 useful. It was uploaded the last few days, and the last update will
2361 enter testing tomorrow. See the
2362 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
2363 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
2364 was announced 6 days ago. We will try to get it into Debian as
2365 well.&lt;/p&gt;
2366
2367 &lt;p&gt;More information related to 3D printing is available on the
2368 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
2369 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
2370 in Debian.&lt;/p&gt;
2371
2372 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2373 activities, please send Bitcoin donations to my address
2374 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2375 </description>
2376 </item>
2377
2378 <item>
2379 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
2380 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
2381 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
2382 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
2383 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
2384 that the nice and user friendly 3D printer slicer software Cura just
2385 entered Debian Unstable. It consist of five packages,
2386 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
2387 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
2388 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
2389 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
2390 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
2391 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
2392 two, uranium and cura, entered Unstable yesterday. This should make
2393 it easier for Debian users to print on at least the Ultimaker class of
2394 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
2395 make life easier for at least me. :)&lt;/p&gt;
2396
2397 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
2398 happy to assist him in sponsoring the packages. With the introduction
2399 of Cura, Debian is up to three 3D printer slicers at your service,
2400 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
2401 printer, give it a go. :)&lt;/p&gt;
2402
2403 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
2404 team, flocking together on the
2405 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
2406 mailing list and the
2407 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
2408 IRC channel.&lt;/p&gt;
2409
2410 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
2411 version 3.0.3 and then update the entire set of packages to version
2412 3.1.0 which showed up the last few days.&lt;/p&gt;
2413 </description>
2414 </item>
2415
2416 <item>
2417 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
2418 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
2419 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
2420 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
2421 <description>&lt;p&gt;At my nearby maker space,
2422 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
2423 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
2424 on Windows and MacOS X than Linux, because the software involved had
2425 to be manually compiled and set up on Linux while premade packages
2426 worked out of the box on Windows and MacOS X. I found this annoying,
2427 as the software involved,
2428 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
2429 and should be trivial to get up and running on Linux if someone took
2430 the time to package it for the relevant distributions. I even found
2431 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
2432 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
2433 never resulted in the software showing up in Debian. So a few days
2434 ago I offered my help to try to improve the situation.&lt;/p&gt;
2435
2436 &lt;p&gt;Now I am very happy to see that all the packages required by a
2437 working Cura in Debian are uploaded into Debian and waiting in the NEW
2438 queue for the ftpmasters to have a look. You can track the progress
2439 on
2440 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
2441 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
2442
2443 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
2444 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
2445 queue&lt;/a&gt; while we work up updating the packages to the latest
2446 upstream version.&lt;/p&gt;
2447
2448 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
2449 to use and was unable to configure correctly for Ultimaker 2+ in the
2450 short time I spent on it, are already in Debian. If you are looking
2451 for 3D printer &quot;slicers&quot; and want something already available in
2452 Debian, check out
2453 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
2454 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
2455 The latter is a fork of the former.&lt;/p&gt;
2456
2457 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2458 activities, please send Bitcoin donations to my address
2459 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2460 </description>
2461 </item>
2462
2463 <item>
2464 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
2465 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
2466 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
2467 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
2468 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
2469 mobile cell towers. And this radio chatter is available for anyone
2470 with a radio receiver capable of receiving them. Details about the
2471 mobile phones with very good accuracy is of course collected by the
2472 phone companies, but this is not the topic of this blog post. The
2473 mobile phone radio chatter make it possible to figure out when a cell
2474 phone is nearby, as it include the SIM card ID (IMSI). By paying
2475 attention over time, one can see when a phone arrive and when it leave
2476 an area. I believe it would be nice to make this information more
2477 available to the general public, to make more people aware of how
2478 their phones are announcing their whereabouts to anyone that care to
2479 listen.&lt;/p&gt;
2480
2481 &lt;p&gt;I am very happy to report that we managed to get something
2482 visualizing this information up and running for
2483 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
2484 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2485 library. The solution is based on the
2486 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
2487 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
2488 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
2489 Sone from the Computer Science department of the University of
2490 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
2491 IMSIs) as dots in a web browser graph, with lines to the dot
2492 representing mobile base station it is talking to. It was working in
2493 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
2494
2495 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
2496 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2497 connected and visualize the visible cell phone towers using an
2498 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
2499 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
2500 grgsm_livemon_headless processes from
2501 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
2502 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
2503
2504 &lt;p&gt;The frequencies to listen to, are identified using a slightly
2505 patched scan-and-livemon (to set the --args values for each receiver),
2506 and the Hopglass data is generated using the
2507 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
2508 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
2509 more than four SDRs working. There is also a geographical map trying
2510 to show the location of the base stations, but I believe their
2511 coordinates are hardcoded to some random location in Germany, I
2512 believe. The code should be replaced with code to look up location in
2513 a text file, a sqlite database or one of the online databases
2514 mentioned in
2515 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
2516 issue for the topic&lt;/a&gt;.
2517
2518 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
2519 </description>
2520 </item>
2521
2522 <item>
2523 <title>Easier recipe to observe the cell phones around you</title>
2524 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
2525 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
2526 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
2527 <description>&lt;p&gt;A little more than a month ago I wrote
2528 &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
2529 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2530 to nearby mobile phone base stations using Debian GNU/Linux and a
2531 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
2532 the location of people and equipment (like cars and trains) with an
2533 accuracy of a few kilometer. Since then we have worked to make the
2534 procedure even simpler, and it is now possible to do this without any
2535 manual frequency tuning and without building your own packages.&lt;/p&gt;
2536
2537 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
2538 package is now included in Debian testing and unstable, and the
2539 IMSI-catcher code no longer require root access to fetch and decode
2540 the GSM data collected using gr-gsm.&lt;/p&gt;
2541
2542 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
2543 clone of two python scripts:&lt;/p&gt;
2544
2545 &lt;ol&gt;
2546
2547 &lt;li&gt;Start with a Debian machine running the Buster version (aka
2548 testing).&lt;/li&gt;
2549
2550 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
2551 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
2552
2553 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
2554 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
2555
2556 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
2557
2558 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2559 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
2560 stations and start listening for GSM packages on one of them.&lt;/li&gt;
2561
2562 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2563 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
2564
2565 &lt;/ol&gt;
2566
2567 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
2568 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
2569 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
2570 work with RTL 8232 and other similar USB radio receivers you can get
2571 very cheaply
2572 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
2573 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
2574 and only use HackRF for fetching GSM data.&lt;/p&gt;
2575
2576 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
2577 frequencies at the time, so if you are going to track and count every
2578 cell phone around you, you need to listen to all the frequencies used.
2579 To listen to several frequencies, use the --numrecv argument to
2580 scan-and-livemon to use several receivers. Further, I am not sure if
2581 phones using 3G or 4G will show as talking GSM to base stations, so
2582 this approach might not see all phones around you. I typically see
2583 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
2584
2585 &lt;p&gt;I&#39;ve tried to run the scanner on a
2586 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
2587 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
2588 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
2589 stdout, I am told there it is caused by a buffer overflow between the
2590 radio and GNU Radio, caused by the program being unable to read the
2591 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
2592 where you started scan-and-livemon, you need a give the process more
2593 CPU power. Perhaps someone are able to optimize the code to a point
2594 where it become possible to set up RPi3 based GSM sniffers? I tried
2595 using Raspbian instead of Debian, but there seem to be something wrong
2596 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
2597 </description>
2598 </item>
2599
2600 <item>
2601 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
2602 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
2603 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
2604 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
2605 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
2606 web based ICT news magazine digi.no on
2607 &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
2608 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
2609 DVB-T software defined radios. The article refered to instructions
2610 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
2611 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;
2612
2613 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
2614 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2615 and the ask pybombs to fetch and build everything you need from
2616 scratch. I wanted to see if I could do the same on the most recent
2617 Debian packages, but this did not work because pybombs tried to build
2618 stuff that no longer build with the most recent openssl library or
2619 some other version skew problem. While trying to get this recipe
2620 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
2621 and the only piece of software dependency missing in Debian was the
2622 gr-gsm package. I also found out that the lead upstream developer of
2623 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2624 Debian packages provided in an Ubuntu PPA repository. All I needed to
2625 do was to dget the Debian source package and built it.&lt;/p&gt;
2626
2627 &lt;p&gt;The IMSI collector is a python script listening for packages on the
2628 loopback network device and printing to the terminal some specific GSM
2629 packages with IMSI numbers in them. The code is fairly short and easy
2630 to understand. The reason this work is because gr-gsm include a tool
2631 to read GSM data from a software defined radio like a DVB-T USB stick
2632 and other software defined radios, decode them and inject them into a
2633 network device on your Linux machine (using the loopback device by
2634 default). This proved to work just fine, and I&#39;ve been testing the
2635 collector for a few days now.&lt;/p&gt;
2636
2637 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
2638
2639 &lt;ol&gt;
2640
2641 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
2642
2643 &lt;li&gt;build and install the gr-gsm package available from
2644 &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;
2645
2646 &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;
2647
2648 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
2649 where it was started is filled with a stream of text (meaning you
2650 found a GSM station).&lt;/li&gt;
2651
2652 &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;
2653
2654 &lt;/ol&gt;
2655
2656 &lt;p&gt;To make it even easier in the future to get this sniffer up and
2657 running, I decided to package
2658 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
2659 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
2660 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
2661 Luckily the gnuradio maintainer has promised to help me, as I do not
2662 know much about gnuradio stuff yet.&lt;/p&gt;
2663
2664 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
2665 commercial tools like
2666 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
2667 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
2668 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
2669 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
2670 more people realise how their whereabouts when carrying a cell phone
2671 is easily tracked. Seeing the data flow on the screen, realizing that
2672 I live close to a police station and knowing that the police is also
2673 wearing cell phones, I wonder how hard it would be for criminals to
2674 track the position of the police officers to discover when there are
2675 police near by, or for foreign military forces to track the location
2676 of the Norwegian military forces, or for anyone to track the location
2677 of government officials...&lt;/p&gt;
2678
2679 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2680 script mentioned above is only a fraction of the data broadcasted on
2681 the GSM network. It will only collect one frequency at the time,
2682 while a typical phone will be using several frequencies, and not all
2683 phones will be using the frequencies tracked by the grgsm_livemod
2684 program. Also, there is a lot of radio chatter being ignored by the
2685 simple_IMSI-catcher script, which would be collected by extending the
2686 parser code. I wonder if gr-gsm can be set up to listen to more than
2687 one frequency?&lt;/p&gt;
2688 </description>
2689 </item>
2690
2691 <item>
2692 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2693 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2694 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2695 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2696 <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;
2697
2698 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2699 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2700 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2701 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2702 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2703 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2704 price. The book is also available for download in electronic form as
2705 PDF, EPUB and Mobipocket, as can be
2706 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2707 as a web page&lt;/a&gt;.&lt;/p&gt;
2708
2709 &lt;p&gt;This is the second book I publish (the first was the book
2710 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2711 in
2712 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2713 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2714 and
2715 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2716 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2717 project. I hope
2718 &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
2719 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2720 </description>
2721 </item>
2722
2723 <item>
2724 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2725 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2726 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2727 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2728 <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
2729 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2730 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2731 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2732 på om den fri oversetterløsningen
2733 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2734 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2735
2736 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2737
2738 &lt;blockquote&gt;
2739 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2740 rolle og muligheter til å håndtere internasjonale utfordringer, som
2741 for eksempel flykningekrisen.&lt;/p&gt;
2742
2743 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2744 på temaet:&lt;/p&gt;
2745 &lt;ol&gt;
2746 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2747 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2748 &lt;/ol&gt;
2749
2750 &lt;/blockquote&gt;
2751
2752 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2753
2754 &lt;blockquote&gt;
2755 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2756 andre aktørar og høve til å handtera internasjonale utfordringar, som
2757 til dømes *flykningekrisen.&lt;/p&gt;
2758
2759 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2760 temaet:&lt;/p&gt;
2761
2762 &lt;ol&gt;
2763 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2764 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2765 &lt;/ol&gt;
2766
2767 &lt;/blockquote&gt;
2768
2769 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2770 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2771 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2772 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2773 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2774 det er kanskje flisespikking. Det understreker vel bare at det alltid
2775 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2776 </description>
2777 </item>
2778
2779 <item>
2780 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2781 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2782 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2783 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2784 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2785 computers at the time, I often needed a way to detect if the machine
2786 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2787 file or directory affected by the hang, the process (and possibly the
2788 shell) will hang too. So you want to be able to detect this without
2789 risking the detection process getting stuck too. It has not been
2790 obvious how to do this. When the hang has lasted a while, it is
2791 possible to find messages like these in dmesg:&lt;/p&gt;
2792
2793 &lt;p&gt;&lt;blockquote&gt;
2794 nfs: server nfsserver not responding, still trying
2795 &lt;br&gt;nfs: server nfsserver OK
2796 &lt;/blockquote&gt;&lt;/p&gt;
2797
2798 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
2799 be sure looking in dmesg is going to work. If there are lots of other
2800 messages in dmesg the lines might have rotated out of site before they
2801 are noticed.&lt;/p&gt;
2802
2803 &lt;p&gt;While reading through the nfs client implementation in linux kernel
2804 code, I came across some statistics that seem to give a way to detect
2805 it. The om_timeouts sunrpc value in the kernel will increase every
2806 time the above log entry is inserted into dmesg. And after digging a
2807 bit further, I discovered that this value show up in
2808 /proc/self/mountstats on Linux.&lt;/p&gt;
2809
2810 &lt;p&gt;The mountstats content seem to be shared between files using the
2811 same file system context, so it is enough to check one of the
2812 mountstats files to get the state of the mount point for the machine.
2813 I assume this will not show lazy umounted NFS points, nor NFS mount
2814 points in a different process context (ie with a different filesystem
2815 view), but that does not worry me.&lt;/p&gt;
2816
2817 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
2818
2819 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2820 [...]
2821 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2822 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
2823 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
2824 age: 7863311
2825 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
2826 sec: flavor=1,pseudoflavor=1
2827 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
2828 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2829 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
2830 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2831 per-op statistics
2832 NULL: 0 0 0 0 0 0 0 0
2833 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2834 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
2835 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2836 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2837 READLINK: 125 125 0 20472 18620 0 1112 1118
2838 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2839 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2840 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
2841 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
2842 SYMLINK: 903 903 0 233428 245488 6 5865 5917
2843 MKNOD: 80 80 0 20148 21760 0 299 304
2844 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
2845 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
2846 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
2847 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
2848 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2849 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2850 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
2851 FSINFO: 2 2 0 232 328 0 1 1
2852 PATHCONF: 1 1 0 116 140 0 0 0
2853 COMMIT: 0 0 0 0 0 0 0 0
2854
2855 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2856 [...]
2857 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2858
2859 &lt;p&gt;The key number to look at is the third number in the per-op list.
2860 It is the number of NFS timeouts experiences per file system
2861 operation. Here 22 write timeouts and 5 access timeouts. If these
2862 numbers are increasing, I believe the machine is experiencing NFS
2863 hang. Unfortunately the timeout value do not start to increase right
2864 away. The NFS operations need to time out first, and this can take a
2865 while. The exact timeout value depend on the setup. For example the
2866 defaults for TCP and UDP mount points are quite different, and the
2867 timeout value is affected by the soft, hard, timeo and retrans NFS
2868 mount options.&lt;/p&gt;
2869
2870 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
2871 Enterprise Linux for getting the timeout count is to peek in /proc/.
2872 But according to
2873 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
2874 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
2875 command can be used to get these timeout values. But this do not work
2876 on Linux, as far as I can tell. I
2877 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
2878 but have not seen any replies yet.&lt;/p&gt;
2879
2880 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
2881 experiencing NFS hangs? Is there a way to detect which processes are
2882 affected? Is there a way to get the NFS mount going quickly once the
2883 network problem causing the NFS hang has been cleared? I would very
2884 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
2885 </description>
2886 </item>
2887
2888 <item>
2889 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
2890 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
2891 <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>
2892 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
2893 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
2894 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
2895 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
2896 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2897 we are working on the proof reading to ensure consistent language and
2898 use of correct computer science terms. The plan is to make the book
2899 available on paper, as well as in electronic form. For that to
2900 happen, the proof reading must be completed and all the figures need
2901 to be translated. If you want to help out, get in touch.&lt;/p&gt;
2902
2903 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
2904
2905 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
2906 pages) of the book created every morning is available for
2907 proofreading. If you find any errors, please
2908 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
2909 Weblate and correct the error&lt;/a&gt;. The
2910 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
2911 of the translation including figures&lt;/a&gt; is a useful source for those
2912 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
2913 </description>
2914 </item>
2915
2916 <item>
2917 <title>Unlimited randomness with the ChaosKey?</title>
2918 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
2919 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
2920 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
2921 <description>&lt;p&gt;A few days ago I ordered a small batch of
2922 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
2923 USB dongle for generating entropy created by Bdale Garbee and Keith
2924 Packard. Yesterday it arrived, and I am very happy to report that it
2925 work great! According to its designers, to get it to work out of the
2926 box, you need the Linux kernel version 4.1 or later. I tested on a
2927 Debian Stretch machine (kernel version 4.9), and there it worked just
2928 fine, increasing the available entropy very quickly. I wrote a small
2929 test oneliner to test. It first print the current entropy level,
2930 drain /dev/random, and then print the entropy level for five seconds.
2931 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
2932
2933 &lt;blockquote&gt;&lt;pre&gt;
2934 % cat /proc/sys/kernel/random/entropy_avail; \
2935 dd bs=1M if=/dev/random of=/dev/null count=1; \
2936 for n in $(seq 1 5); do \
2937 cat /proc/sys/kernel/random/entropy_avail; \
2938 sleep 1; \
2939 done
2940 300
2941 0+1 oppføringer inn
2942 0+1 oppføringer ut
2943 28 byte kopiert, 0,000264565 s, 106 kB/s
2944 4
2945 8
2946 12
2947 17
2948 21
2949 %
2950 &lt;/pre&gt;&lt;/blockquote&gt;
2951
2952 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
2953 application requiring random bits (like a HTTPS enabled web server)
2954 will halt and wait for more entrpy. And here is the situation with
2955 the ChaosKey inserted:&lt;/p&gt;
2956
2957 &lt;blockquote&gt;&lt;pre&gt;
2958 % cat /proc/sys/kernel/random/entropy_avail; \
2959 dd bs=1M if=/dev/random of=/dev/null count=1; \
2960 for n in $(seq 1 5); do \
2961 cat /proc/sys/kernel/random/entropy_avail; \
2962 sleep 1; \
2963 done
2964 1079
2965 0+1 oppføringer inn
2966 0+1 oppføringer ut
2967 104 byte kopiert, 0,000487647 s, 213 kB/s
2968 433
2969 1028
2970 1031
2971 1035
2972 1038
2973 %
2974 &lt;/pre&gt;&lt;/blockquote&gt;
2975
2976 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
2977 someone want to buy one here in Norway. :)&lt;/p&gt;
2978
2979 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
2980 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
2981 recording illuminating&lt;/a&gt;. It explains exactly what the source of
2982 randomness is, if you are unable to spot it from the schema drawing
2983 available from the ChaosKey web site linked at the start of this blog
2984 post.&lt;/p&gt;
2985 </description>
2986 </item>
2987
2988 <item>
2989 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
2990 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
2991 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
2992 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
2993 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
2994 web servers, and who own the network equipment it is flowing through?
2995 It is possible to get a glimpse of this from using traceroute, but it
2996 is hard to find all the details. Many years ago, I wrote a system to
2997 map the Norwegian Internet (trying to figure out if our plans for a
2998 network game service would get low enough latency, and who we needed
2999 to talk to about setting up game servers close to the users. Back
3000 then I used traceroute output from many locations (I asked my friends
3001 to run a script and send me their traceroute output) to create the
3002 graph and the map. The output from traceroute typically look like
3003 this:
3004
3005 &lt;p&gt;&lt;pre&gt;
3006 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
3007 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
3008 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
3009 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
3010 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
3011 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
3012 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
3013 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
3014 8 * * *
3015 9 * * *
3016 [...]
3017 &lt;/pre&gt;&lt;/p&gt;
3018
3019 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
3020 network equipment involved in getting the data traffic from me to the
3021 www.stortinget.no server, and how long it took in milliseconds for a
3022 package to reach the equipment and return to me. Three packages are
3023 sent, and some times the packages do not follow the same path. This
3024 is shown for hop 5, where three different IP addresses replied to the
3025 traceroute request.&lt;/p&gt;
3026
3027 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
3028 implementations I use are traceroute (using ICMP packages) mtr (can do
3029 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
3030 traceroute and a lot of other capabilities). All of them are easily
3031 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
3032
3033 &lt;p&gt;This time around, I wanted to know the geographic location of
3034 different route points, to visualize how visiting a web page spread
3035 information about the visit to a lot of servers around the globe. The
3036 background is that a web site today often will ask the browser to get
3037 from many servers the parts (for example HTML, JSON, fonts,
3038 JavaScript, CSS, video) required to display the content. This will
3039 leak information about the visit to those controlling these servers
3040 and anyone able to peek at the data traffic passing by (like your ISP,
3041 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
3042
3043 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
3044 www.stortinget.no. It is read daily by all members of parliament and
3045 their staff, as well as political journalists, activits and many other
3046 citizens of Norway. A visit to the www.stortinget.no web site will
3047 ask your browser to contact 8 other servers: ajax.googleapis.com,
3048 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3049 stats.g.doubleclick.net, www.google-analytics.com,
3050 www.googletagmanager.com and www.netigate.se. I extracted this by
3051 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
3052 Stortinget web page and tell me all the URLs PhantomJS downloaded to
3053 render the page (in HAR format using
3054 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
3055 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
3056 to do this). My goal is to visualize network traces to all IP
3057 addresses behind these DNS names, do show where visitors personal
3058 information is spread when visiting the page.&lt;/p&gt;
3059
3060 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
3061 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;
3062
3063 &lt;p&gt;When I had a look around for options, I could not find any good
3064 free software tools to do this, and decided I needed my own traceroute
3065 wrapper outputting KML based on locations looked up using GeoIP. KML
3066 is easy to work with and easy to generate, and understood by several
3067 of the GIS tools I have available. I got good help from by NUUG
3068 colleague Anders Einar with this, and the result can be seen in
3069 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
3070 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
3071 free GeoIP databases I could find (and the for-pay databases my
3072 friends had access to) is not up to the task. The IP addresses of
3073 central Internet infrastructure would typically be placed near the
3074 controlling companies main office, and not where the router is really
3075 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
3076 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
3077
3078 &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
3079 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;
3080
3081 &lt;p&gt;I also had a look at the visual traceroute graph created by
3082 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
3083 showing IP network ownership (aka AS owner) for the IP address in
3084 question.
3085 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
3086 graph display a lot of useful information about the traceroute in SVG
3087 format&lt;/a&gt;, and give a good indication on who control the network
3088 equipment involved, but it do not include geolocation. This graph
3089 make it possible to see the information is made available at least for
3090 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
3091 3 Communications and NetDNA.&lt;/p&gt;
3092
3093 &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
3094 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;
3095
3096 &lt;p&gt;In the process, I came across the
3097 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
3098 Salim Gasmi. Its methology of combining guesses based on DNS names,
3099 various location databases and finally use latecy times to rule out
3100 candidate locations seemed to do a very good job of guessing correct
3101 geolocation. But it could only do one trace at the time, did not have
3102 a sensor in Norway and did not make the geolocations easily available
3103 for postprocessing. So I contacted the developer and asked if he
3104 would be willing to share the code (he refused until he had time to
3105 clean it up), but he was interested in providing the geolocations in a
3106 machine readable format, and willing to set up a sensor in Norway. So
3107 since yesterday, it is possible to run traces from Norway in this
3108 service thanks to a sensor node set up by
3109 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
3110 trace in KML format for further processing.&lt;/p&gt;
3111
3112 &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
3113 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;
3114
3115 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
3116 Denmark, Germany, Holland and Ireland. Plenty of places where the
3117 Snowden confirmations verified the traffic is read by various actors
3118 without your best interest as their top priority.&lt;/p&gt;
3119
3120 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
3121 over all the hosts behind the urls imported by www.stortinget.no and
3122 ask for the KML file from GeoTraceroute, and create a combined KML
3123 file with all the traces (unfortunately only one of the IP addresses
3124 behind the DNS name is traced this time. To get them all, one would
3125 have to request traces using IP number instead of DNS names from
3126 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
3127
3128 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
3129 the IP traffic moves and who control the boxes involved in moving it.
3130 And every time the link crosses for example the Swedish border, we can
3131 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3132 Britain and NSA in USA and cables around the globe. (Hm, what should
3133 we tell them? :) Keep that in mind if you ever send anything
3134 unencrypted over the Internet.&lt;/p&gt;
3135
3136 &lt;p&gt;PS: KML files are drawn using
3137 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
3138 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
3139 Marble. There are heaps of other options too.&lt;/p&gt;
3140
3141 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3142 activities, please send Bitcoin donations to my address
3143 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3144 </description>
3145 </item>
3146
3147 <item>
3148 <title>Appstream just learned how to map hardware to packages too!</title>
3149 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
3150 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
3151 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
3152 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
3153 readers probably know, I have been working on the
3154 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
3155 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
3156 it easier for users to figure out what to install to get a given piece
3157 of hardware to work in Debian, and a key part of this system is a way
3158 to map hardware to packages. Isenkram have its own mapping database,
3159 and also uses data provided by each package using the AppStream
3160 metadata format. And today,
3161 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
3162 Debian learned to look up hardware the same way Isenkram is doing it,
3163 ie using fnmatch():&lt;/p&gt;
3164
3165 &lt;p&gt;&lt;pre&gt;
3166 % appstreamcli what-provides modalias \
3167 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3168 Identifier: pymissile [generic]
3169 Name: pymissile
3170 Summary: Control original Striker USB Missile Launcher
3171 Package: pymissile
3172 % appstreamcli what-provides modalias usb:v0694p0002d0000
3173 Identifier: libnxt [generic]
3174 Name: libnxt
3175 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3176 Package: libnxt
3177 ---
3178 Identifier: t2n [generic]
3179 Name: t2n
3180 Summary: Simple command-line tool for Lego NXT
3181 Package: t2n
3182 ---
3183 Identifier: python-nxt [generic]
3184 Name: python-nxt
3185 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3186 Package: python-nxt
3187 ---
3188 Identifier: nbc [generic]
3189 Name: nbc
3190 Summary: C compiler for LEGO Mindstorms NXT bricks
3191 Package: nbc
3192 %
3193 &lt;/pre&gt;&lt;/p&gt;
3194
3195 &lt;p&gt;A similar query can be done using the combined AppStream and
3196 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
3197
3198 &lt;p&gt;&lt;pre&gt;
3199 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3200 pymissile
3201 % isenkram-lookup usb:v0694p0002d0000
3202 libnxt
3203 nbc
3204 python-nxt
3205 t2n
3206 %
3207 &lt;/pre&gt;&lt;/p&gt;
3208
3209 &lt;p&gt;You can find modalias values relevant for your machine using
3210 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
3211
3212 &lt;p&gt;If you want to make this system a success and help Debian users
3213 make the most of the hardware they have, please
3214 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
3215 AppStream metadata for your package following the guidelines&lt;/a&gt;
3216 documented in the wiki. So far only 11 packages provide such
3217 information, among the several hundred hardware specific packages in
3218 Debian. The Isenkram database on the other hand contain 101 packages,
3219 mostly related to USB dongles. Most of the packages with hardware
3220 mapping in AppStream are LEGO Mindstorms related, because I have, as
3221 part of my involvement in
3222 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
3223 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
3224 complete set of packages in Debian for that particular hardware. The
3225 team also got a nice Christmas present today. The
3226 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
3227 package&lt;/a&gt; made it into Debian. With this package in place, it is
3228 now possible to use the LEGO Mindstorms NXT unit with only free
3229 software, as the nxt-firmware package contain the source and firmware
3230 binaries for the NXT brick.&lt;/p&gt;
3231
3232 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3233 activities, please send Bitcoin donations to my address
3234 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3235 </description>
3236 </item>
3237
3238 <item>
3239 <title>Isenkram updated with a lot more hardware-package mappings</title>
3240 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
3241 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
3242 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
3243 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3244 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
3245 and install packages to get your hardware dongles to work, is still
3246 going strong. It is a system to look up the hardware present on or
3247 connected to the current system, and map the hardware to Debian
3248 packages. It can either be done using the tools in isenkram-cli or
3249 using the user space daemon in the isenkram package. The latter will
3250 notify you, when inserting new hardware, about what packages to
3251 install to get the dongle working. It will even provide a button to
3252 click on to ask packagekit to install the packages.&lt;/p&gt;
3253
3254 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
3255
3256 &lt;p&gt;&lt;pre&gt;
3257 % isenkram-lookup
3258 bluez
3259 cheese
3260 ethtool
3261 fprintd
3262 fprintd-demo
3263 gkrellm-thinkbat
3264 hdapsd
3265 libpam-fprintd
3266 pidgin-blinklight
3267 thinkfan
3268 tlp
3269 tp-smapi-dkms
3270 tp-smapi-source
3271 tpb
3272 %
3273 &lt;/pre&gt;&lt;/p&gt;
3274
3275 &lt;p&gt;It can also list the firware package providing firmware requested
3276 by the load kernel modules, which in my case is an empty list because
3277 I have all the firmware my machine need:
3278
3279 &lt;p&gt;&lt;pre&gt;
3280 % /usr/sbin/isenkram-autoinstall-firmware -l
3281 info: did not find any firmware files requested by loaded kernel modules. exiting
3282 %
3283 &lt;/pre&gt;&lt;/p&gt;
3284
3285 &lt;p&gt;The last few days I had a look at several of the around 250
3286 packages in Debian with udev rules. These seem like good candidates
3287 to install when a given hardware dongle is inserted, and I found
3288 several that should be proposed by isenkram. I have not had time to
3289 check all of them, but am happy to report that now there are 97
3290 packages packages mapped to hardware by Isenkram. 11 of these
3291 packages provide hardware mapping using AppStream, while the rest are
3292 listed in the modaliases file provided in isenkram.&lt;/p&gt;
3293
3294 &lt;p&gt;These are the packages with hardware mappings at the moment. The
3295 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
3296 support using AppStream, for everyone to use:&lt;/p&gt;
3297
3298 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
3299 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
3300 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
3301 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
3302 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
3303 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3304 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
3305 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3306 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3307 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3308 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
3309 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3310 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
3311 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3312 pcscd, pidgin-blinklight, printer-driver-splix,
3313 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
3314 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3315 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3316 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3317 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3318 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3319 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3320 xserver-xorg-video-vmware, yubikey-personalization and
3321 zd1211-firmware&lt;/p&gt;
3322
3323 &lt;p&gt;If you know of other packages, please let me know with a wishlist
3324 bug report against the isenkram-cli package, and ask the package
3325 maintainer to
3326 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
3327 metadata according to the guidelines&lt;/a&gt; to provide the information
3328 for everyone. In time, I hope to get rid of the isenkram specific
3329 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
3330
3331 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
3332 much hardware, and suggest that the package with with any ethernet
3333 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
3334 the details. I hope the maintainer find time to address it soon. In
3335 the mean time I provide an override in isenkram.&lt;/p&gt;
3336 </description>
3337 </item>
3338
3339 <item>
3340 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
3341 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
3342 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
3343 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
3344 <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;
3345
3346 &lt;p&gt;In my early years, I played
3347 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
3348 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
3349 space, and reached the &#39;elite&#39; fighting status before I moved on. The
3350 original Elite game was available on Commodore 64 and the IBM PC
3351 edition I played had a 64 KB executable. I am still impressed today
3352 that the authors managed to squeeze both a 3D engine and details about
3353 more than 2000 planet systems across 7 galaxies into a binary so
3354 small.&lt;/p&gt;
3355
3356 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
3357 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
3358 really have time to test it properly until a few days ago. It was
3359 great to discover that my old knowledge about trading routes were
3360 still valid. But my fighting and flying abilities were gone, so I had
3361 to retrain to be able to dock on a space station. And I am still not
3362 able to make much resistance when I am attacked by pirates, so I
3363 bougth and mounted the most powerful laser in the rear to be able to
3364 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
3365
3366 &lt;p&gt;When playing Elite in the late eighties, I had to discover
3367 everything on my own, and I had long lists of prices seen on different
3368 planets to be able to decide where to trade what. This time I had the
3369 advantages of the
3370 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
3371 where information about each planet is easily available with common
3372 price ranges and suggested trading routes. This improved my ability
3373 to earn money and I have been able to earn enough to buy a lot of
3374 useful equipent in a few days. I believe I originally played for
3375 months before I could get a docking computer, while now I could get it
3376 after less then a week.&lt;/p&gt;
3377
3378 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
3379 space, you should try out Oolite. It is available for Linux, MacOSX
3380 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
3381
3382 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3383 activities, please send Bitcoin donations to my address
3384 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3385 </description>
3386 </item>
3387
3388 <item>
3389 <title>Quicker Debian installations using eatmydata</title>
3390 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
3391 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
3392 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
3393 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
3394 installation system, observing how using
3395 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
3396 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
3397 speedup around 20-40 percent for Debian Edu, where we install around
3398 1000 packages from within the installer. The eatmydata package
3399 provide a way to disable/delay file system flushing. This is a bit
3400 risky in the general case, as files that should be stored on disk will
3401 stay only in memory a bit longer than expected, causing problems if a
3402 machine crashes at an inconvenient time. But for an installation, if
3403 the machine crashes during installation the process is normally
3404 restarted, and avoiding disk operations as much as possible to speed
3405 up the process make perfect sense.
3406
3407 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
3408 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
3409 but did not have time to push it any further. But a few months ago I
3410 picked it up again and worked with the libeatmydata package maintainer
3411 Mattia Rizzolo to make it easier for everyone to get this installation
3412 speedup in Debian. Thanks to our cooperation There is now an
3413 eatmydata-udeb package in Debian testing and unstable, and simply
3414 enabling/installing it in debian-installer (d-i) is enough to get the
3415 quicker installations. It can be enabled using preseeding. The
3416 following untested kernel argument should do the trick:&lt;/p&gt;
3417
3418 &lt;blockquote&gt;&lt;pre&gt;
3419 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
3420 &lt;/pre&gt;&lt;/blockquote&gt;
3421
3422 &lt;p&gt;This should ask d-i to install the package inside the d-i
3423 environment early in the installation sequence. Having it installed
3424 in d-i in turn will make sure the relevant scripts are called just
3425 after debootstrap filled /target/ with the freshly installed Debian
3426 system to configure apt to run dpkg with eatmydata. This is enough to
3427 speed up the installation process. There is a proposal to
3428 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
3429 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
3430 tested its impact.&lt;/p&gt;
3431
3432 </description>
3433 </item>
3434
3435 <item>
3436 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
3437 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
3438 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
3439 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
3440 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3441 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3442 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3443 elever over det ganske land skal levere inn hvert år. Det mange ikke
3444 vet er at selv om de kommersielle alternativene
3445 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
3446 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
3447 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3448 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3449 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3450 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3451 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3452 nynorsk, og få den automatoversatt til det andre skriftspråket.
3453 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3454 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3455 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3456 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3457 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
3458 teksten din i webskjemaet der.
3459
3460 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
3461 teknologien kan du enten installere pakken
3462 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
3463 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3464 api.apertium.org. Se
3465 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
3466 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3467 denne teksten som ble skrevet på bokmål over maskinoversatt til
3468 nynorsk.&lt;/p&gt;
3469
3470 &lt;hr/&gt;
3471
3472 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3473 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3474 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3475 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3476 veit er at sjølv om dei kommersielle alternativa
3477 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
3478 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
3479 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3480 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3481 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3482 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3483 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3484 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3485 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3486 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3487 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3488 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3489 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
3490 teksta di i *webskjemaet der.
3491
3492 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
3493 teknologien kan du anten installera pakken
3494 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
3495 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3496 *api.*apertium.org. Sjå
3497 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
3498 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3499 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3500 nynorsk.&lt;/p&gt;
3501 </description>
3502 </item>
3503
3504 <item>
3505 <title>Coz profiler for multi-threaded software is now in Debian</title>
3506 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
3507 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
3508 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
3509 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
3510 profiler able to run benchmarking experiments on the instrumented
3511 multi-threaded program, finally
3512 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
3513 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
3514 months since
3515 &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
3516 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
3517 it suitable for Debian. There are still issues with clang
3518 compatibility, inline assembly only working x86 and minimized
3519 JavaScript libraries.&lt;/p&gt;
3520
3521 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
3522
3523 &lt;p&gt;&lt;blockquote&gt;
3524 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
3525 &lt;/blockquote&gt;&lt;/p&gt;
3526
3527 &lt;p&gt;This will produce a profile.coz file in the current working
3528 directory with the profiling information. This is then given to a
3529 JavaScript application provided in the package and available from
3530 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
3531 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
3532
3533 &lt;p&gt;&lt;blockquote&gt;
3534 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
3535 &lt;/blockquote&gt;&lt;/p&gt;
3536
3537 &lt;p&gt;See the project home page and the
3538 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
3539 ;login: article on Coz&lt;/a&gt; for more information on how it is
3540 working.&lt;/p&gt;
3541 </description>
3542 </item>
3543
3544 <item>
3545 <title>My own self balancing Lego Segway</title>
3546 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
3547 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
3548 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
3549 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
3550 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
3551 present. It had been on my wishlist for a while, because I wanted to
3552 build a Segway like balancing lego robot. I had already built
3553 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
3554 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
3555 NXT kit as the balance sensor, but it was not working very well. It
3556 could balance for a while, but was very sensitive to the light
3557 condition in the room and the reflective properties of the surface and
3558 would fall over after a short while. I wanted something more robust,
3559 and had
3560 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
3561 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
3562 wishlist for some years before it suddenly showed up as a gift from my
3563 loved ones. :)&lt;/p&gt;
3564
3565 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
3566 since then. But that changed some days ago, when I was searching for
3567 lego segway information and came across a recipe from HiTechnic for
3568 building
3569 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
3570 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
3571 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
3572 code&lt;/a&gt; was included, so it was just a question of putting it all
3573 together. And thanks to the great work of many Debian developers, the
3574 compiler needed to build the source for the NXT is already included in
3575 Debian, so I was read to go in less than an hour. The resulting robot
3576 do not look very impressive in its simplicity:&lt;/p&gt;
3577
3578 &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;
3579
3580 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
3581 design from HiTechnic, I had to comment out the last task
3582 (taskControl). I simply placed /* and */ around it get the program
3583 working without that sensor present. Now it balances just fine until
3584 the battery status run low:&lt;/p&gt;
3585
3586 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
3587 &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;
3588 &lt;/video&gt;&lt;/p&gt;
3589
3590 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
3591 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
3592
3593 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
3594 they need to work with LEGO in Debian and all our derivative
3595 distributions like Ubuntu, check out
3596 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
3597 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
3598 RCX and NXT controller (no EV3), and would like to make sure the
3599 Debian tools needed to program the systems I own work as they
3600 should.&lt;/p&gt;
3601 </description>
3602 </item>
3603
3604 <item>
3605 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
3606 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
3607 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
3608 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
3609 <description>&lt;p&gt;In July
3610 &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
3611 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
3612 the ability to receive SMS messages (aka without a cell phone). It is
3613 time to share some experiences and provide an updated setup.&lt;/p&gt;
3614
3615 &lt;p&gt;The Signal app have worked fine for several months now, and I use
3616 it regularly to chat with my loved ones. I had a major snag at the
3617 end of my summer vacation, when the the app completely forgot my
3618 setup, identity and keys. The reason behind this major mess was
3619 running out of disk space. To avoid that ever happening again I have
3620 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
3621 roll back to an earlier version if the files are wiped by mistake. I
3622 had to use it once after introducing the git backup. When rolling
3623 back to an earlier version, one need to use the &#39;reset session&#39; option
3624 in Signal to get going, and notify the people you talk with about the
3625 problem. I assume there is some sequence number tracking in the
3626 protocol to detect rollback attacks. The git repository is rather big
3627 (674 MiB so far), but I have not tried to figure out if some of the
3628 content can be added to a .gitignore file due to lack of spare
3629 time.&lt;/p&gt;
3630
3631 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
3632 make it impossible to send messages using Signal. I could still
3633 receive them, but had to patch the code with a new timestamp to send.
3634 I believe the timeout is added by the developers to force people to
3635 upgrade to the latest version of the app, even when there is no
3636 protocol changes, to reduce the version skew among the user base and
3637 thus try to keep the number of support requests down.&lt;/p&gt;
3638
3639 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
3640 making the old patch fail to apply cleanly. Below is an updated
3641 patch, including the shell wrapper I use to start Signal. The
3642 original version required a new user to locate the JavaScript console
3643 and call a function from there. I got help from a friend with more
3644 JavaScript knowledge than me to modify the code to provide a GUI
3645 button instead. This mean that to get started you just need to run
3646 the wrapper and click the &#39;Register without mobile phone&#39; to get going
3647 now. I&#39;ve also modified the timeout code to always set it to 90 days
3648 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
3649
3650 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
3651
3652 &lt;ol&gt;
3653
3654 &lt;li&gt;First, install required packages to get the source code and the
3655 browser you need. Signal only work with Chrome/Chromium, as far as I
3656 know, so you need to install it.
3657
3658 &lt;pre&gt;
3659 apt install git tor chromium
3660 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3661 &lt;/pre&gt;&lt;/li&gt;
3662
3663 &lt;li&gt;Modify the source code using command listed in the the patch
3664 block below.&lt;/li&gt;
3665
3666 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
3667 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
3668
3669 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
3670 number you can receive calls to the next minute, receive the
3671 verification code and enter it into the form field and press
3672 &#39;Register&#39;. Note, the phone number you use will be user Signal
3673 username, ie the way others can find you on Signal.&lt;/li&gt;
3674
3675 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3676 not show up in the contact list until you restart Signal, and there is
3677 no way to assign names to Contacts. There is also no way to create or
3678 update chat groups. I suspect this is because the web app do not have
3679 a associated contact database.&lt;/li&gt;
3680
3681 &lt;/ol&gt;
3682
3683 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3684 main author moxie0 reject federation and accept dependencies to major
3685 corporations like Google (part of the code is fetched from Google) and
3686 Amazon (the central coordination point is owned by Amazon). See for
3687 example
3688 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3689 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3690 view on these issues. But the network effect is strong in this case,
3691 and several of the people I want to communicate with already use
3692 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3693 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3694 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3695 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3696 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3697 working on Debian Stable.&lt;/p&gt;
3698
3699 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3700 working. It switch to the production servers, disable to timeout,
3701 make registration easier and add the shell wrapper:&lt;/p&gt;
3702
3703 &lt;pre&gt;
3704 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3705 diff --git a/js/background.js b/js/background.js
3706 index 24b4c1d..579345f 100644
3707 --- a/js/background.js
3708 +++ b/js/background.js
3709 @@ -33,9 +33,9 @@
3710 });
3711 });
3712
3713 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3714 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3715 var SERVER_PORTS = [80, 4433, 8443];
3716 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3717 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3718 var messageReceiver;
3719 window.getSocketStatus = function() {
3720 if (messageReceiver) {
3721 diff --git a/js/expire.js b/js/expire.js
3722 index 639aeae..beb91c3 100644
3723 --- a/js/expire.js
3724 +++ b/js/expire.js
3725 @@ -1,6 +1,6 @@
3726 ;(function() {
3727 &#39;use strict&#39;;
3728 - var BUILD_EXPIRATION = 0;
3729 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3730
3731 window.extension = window.extension || {};
3732
3733 diff --git a/js/views/install_view.js b/js/views/install_view.js
3734 index 7816f4f..1d6233b 100644
3735 --- a/js/views/install_view.js
3736 +++ b/js/views/install_view.js
3737 @@ -38,7 +38,8 @@
3738 return {
3739 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3740 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3741 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3742 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3743 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3744 };
3745 },
3746 clearQR: function() {
3747 diff --git a/options.html b/options.html
3748 index dc0f28e..8d709f6 100644
3749 --- a/options.html
3750 +++ b/options.html
3751 @@ -14,7 +14,10 @@
3752 &amp;lt;div class=&#39;nav&#39;&gt;
3753 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3754 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3755 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3756 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3757 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3758 +
3759 + &amp;lt;/div&gt;
3760 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3761 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3762 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3763 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3764 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3765 @@ -0,0 +1,12 @@
3766 +#!/bin/sh
3767 +set -e
3768 +cd $(dirname $0)
3769 +mkdir -p userdata
3770 +userdata=&quot;`pwd`/userdata&quot;
3771 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3772 + (cd $userdata &amp;&amp; git init)
3773 +fi
3774 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3775 +exec chromium \
3776 + --proxy-server=&quot;socks://localhost:9050&quot; \
3777 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3778 EOF
3779 chmod a+rx run-signal-app
3780 &lt;/pre&gt;
3781
3782 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3783 activities, please send Bitcoin donations to my address
3784 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3785 </description>
3786 </item>
3787
3788 <item>
3789 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3790 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3791 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3792 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3793 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3794 system&lt;/a&gt; provide a practical and easy way to figure out which
3795 packages support the hardware in a given machine. The command line
3796 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
3797 convenient way to list and install packages relevant for the current
3798 hardware during system installation, both user space packages and
3799 firmware packages. The GUI background daemon on the other hand provide
3800 a pop-up proposing to install packages when a new dongle is inserted
3801 while using the computer. For example, if you plug in a smart card
3802 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
3803 that package isn&#39;t already installed, and if you plug in a USB video
3804 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
3805 cheese is currently missing. This already work just fine.&lt;/p&gt;
3806
3807 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
3808 package names. When I started no such database existed in Debian, so
3809 I made my own data set and included it with the isenkram package and
3810 made isenkram fetch the latest version of this database from git using
3811 http. This way the isenkram users would get updated package proposals
3812 as soon as I learned more about hardware related packages.&lt;/p&gt;
3813
3814 &lt;p&gt;The hardware is identified using modalias strings. The modalias
3815 design is from the Linux kernel where most hardware descriptors are
3816 made available as a strings that can be matched using filename style
3817 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3818 identifiers.&lt;/p&gt;
3819
3820 &lt;p&gt;The downside to the Isenkram specific database is that there is no
3821 information about relevant distribution / Debian version, making
3822 isenkram propose obsolete packages too. But along came AppStream, a
3823 cross distribution mechanism to store and collect metadata about
3824 software packages. When I heard about the proposal, I contacted the
3825 people involved and suggested to add a hardware matching rule using
3826 modalias strings in the specification, to be able to use AppStream for
3827 mapping hardware to packages. This idea was accepted and AppStream is
3828 now a great way for a package to announce the hardware it support in a
3829 distribution neutral way. I wrote
3830 &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
3831 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
3832 December. If you have a hardware related package in Debian, please
3833 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
3834
3835 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
3836 RCX or NXT unit, announce this support using AppStream. The effect is
3837 that when you insert such LEGO robot controller into your Debian
3838 machine, Isenkram will propose to install the packages needed to get
3839 it working. The intention is that this should allow the local user to
3840 start programming his robot controller right away without having to
3841 guess what packages to use or which permissions to fix.&lt;/p&gt;
3842
3843 &lt;p&gt;But when I sat down with my son the other day to program our NXT
3844 unit using his Debian Stretch computer, I discovered something
3845 annoying. The local console user (ie my son) did not get access to
3846 the USB device for programming the unit. This used to work, but no
3847 longer in Jessie and Stretch. After some investigation and asking
3848 around on #debian-devel, I discovered that this was because udev had
3849 changed the mechanism used to grant access to local devices. The
3850 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
3851 no longer applied, because LDAP users no longer was added to the
3852 plugdev group during login. Michael Biebl told me that this method
3853 was obsolete and the new method used ACLs instead. This was good
3854 news, as the plugdev mechanism is a mess when using a remote user
3855 directory like LDAP. Using ACLs would make sure a user lost device
3856 access when she logged out, even if the user left behind a background
3857 process which would retain the plugdev membership with the ConsoleKit
3858 setup. Armed with this knowledge I moved on to fix the access problem
3859 for the LEGO Mindstorms related packages.&lt;/p&gt;
3860
3861 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
3862 applied directly for a device, or is applied in
3863 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
3864 LEGO Mindstorms udev rules did not have a class, I decided to add the
3865 tag directly in the udev rules files included in the packages. Here
3866 is one example. For the nqc C compiler for the RCX, the
3867 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
3868
3869 &lt;p&gt;&lt;pre&gt;
3870 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
3871 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
3872 &lt;/pre&gt;&lt;/p&gt;
3873
3874 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
3875 packages using plugdev in their /lib/udev/rules.d/ files should be
3876 changed to use this tag (either directly or indirectly via
3877 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
3878 to detect this?&lt;/p&gt;
3879
3880 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
3881 It is unclear to me if the uaccess tag is an internal implementation
3882 detail like the udev-acl tag used by
3883 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
3884 indirect method is the preferred way. Michael
3885 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
3886 documentation from the systemd project&lt;/a&gt; and I hope it will make
3887 this clearer. For now I use the generic classes when they exist and
3888 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
3889 directly if no such class exist.&lt;/p&gt;
3890
3891 &lt;p&gt;To learn more about the isenkram system, please check out
3892 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3893 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3894
3895 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
3896 please join us on our IRC channel
3897 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
3898 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
3899 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
3900 list is not yet created, but we are working on it. :)&lt;/p&gt;
3901
3902 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3903 activities, please send Bitcoin donations to my address
3904 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3905 </description>
3906 </item>
3907
3908 <item>
3909 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
3910 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
3911 <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>
3912 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
3913 <description>&lt;p&gt;In April we
3914 &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
3915 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
3916 how to set up and administrate a Debian system. Today I am happy to
3917 report that the first draft is now publicly available. You can find
3918 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
3919 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
3920 eight chapters have a first draft translation, and we are working on
3921 proofreading the content. If you want to help out, please start
3922 contributing using
3923 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3924 hosted weblate project page&lt;/a&gt;, and get in touch using
3925 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3926 translators mailing list&lt;/a&gt;. Please also check out
3927 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3928 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
3929 and update weblate if you find errors.&lt;/p&gt;
3930
3931 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
3932 electronic form.&lt;/p&gt;
3933 </description>
3934 </item>
3935
3936 <item>
3937 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
3938 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
3939 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
3940 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
3941 <description>&lt;p&gt;This summer, I read a great article
3942 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
3943 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
3944 how to profile multi-threaded programs. It presented a system for
3945 profiling software by running experiences in the running program,
3946 testing how run time performance is affected by &quot;speeding up&quot; parts of
3947 the code to various degrees compared to a normal run. It does this by
3948 slowing down parallel threads while the &quot;faster up&quot; code is running
3949 and measure how this affect processing time. The processing time is
3950 measured using probes inserted into the code, either using progress
3951 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3952 can also measure unmodified code by measuring complete the program
3953 runtime and running the program several times instead.&lt;/p&gt;
3954
3955 &lt;p&gt;The project and presentation was so inspiring that I would like to
3956 get the system into Debian. I
3957 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
3958 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
3959 system ready for Debian by sending patches. The build process need to
3960 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
3961 to include the JavaScript web page used to visualize the collected
3962 profiling information included in the source package.
3963 But I expect that should work out fairly soon.&lt;/p&gt;
3964
3965 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
3966 on a binary with debug symbols available, start the program like this:
3967
3968 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3969 coz run --- program-to-run
3970 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3971
3972 &lt;p&gt;This will create a text file profile.coz with the instrumentation
3973 information. To show what part of the code affect the performance
3974 most, use a web browser and either point it to
3975 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
3976 or use the copy from git (in the gh-pages branch). Check out this web
3977 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
3978 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
3979 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3980 code, rebuild and run the profiler. This allow coz to do more
3981 targeted experiments.&lt;/p&gt;
3982
3983 &lt;p&gt;A video published by ACM
3984 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
3985 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
3986 from the 25th Symposium on Operating Systems Principles available
3987 titled
3988 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
3989 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
3990
3991 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
3992 for Coz is available from github. It will only build with clang
3993 because it uses a
3994 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
3995 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
3996 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
3997 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
3998
3999 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
4000 of software in Debian. I would very much like some help with the
4001 packaging effort, as I lack the in depth knowledge on how to package
4002 C++ libraries.&lt;/p&gt;
4003 </description>
4004 </item>
4005
4006 <item>
4007 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
4008 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
4009 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
4010 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
4011 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
4012 to be a slight challenge. Here is the recipe if I ever need to do it
4013 again. It all started by me wanting to try the recipe to set up
4014 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
4015 hardened Android installation&lt;/a&gt; from the Tor project blog on a
4016 device I had access to. It is a old mobile phone with a broken
4017 microphone The initial idea had been to just
4018 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
4019 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
4020 until a few days ago.&lt;/p&gt;
4021
4022 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
4023 loader (press volume down and power at the same time), (2) select
4024 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
4025 machine, (4) request the device identifier token by running &#39;fastboot
4026 oem get_identifier_token&#39;, (5) request the device unlocking key using
4027 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
4028 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
4029
4030 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
4031 or newer, and the device I was working on had 2.00.0027. This
4032 apparently can be easily fixed by downloading a Windows program and
4033 running it on your Windows machine, if you accept the terms Microsoft
4034 require you to accept to use Windows - which I do not. So I had to
4035 come up with a different approach. I got a lot of help from AndyCap
4036 on #nuug, and would not have been able to get this working without
4037 him.&lt;/p&gt;
4038
4039 &lt;p&gt;First I needed to extract the hboot firmware from
4040 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
4041 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
4042 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
4043 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
4044 recognise the file format, but unruu worked and extracted rom.zip,
4045 containing the new hboot firmware and a text file describing which
4046 devices it would work for.&lt;/p&gt;
4047
4048 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
4049 followed some instructions
4050 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
4051 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
4052 machine with Debian testing:&lt;/p&gt;
4053
4054 &lt;p&gt;&lt;pre&gt;
4055 adb reboot-bootloader
4056 fastboot oem rebootRUU
4057 fastboot flash zip rom.zip
4058 fastboot flash zip rom.zip
4059 fastboot reboot
4060 &lt;/pre&gt;&lt;/p&gt;
4061
4062 &lt;p&gt;The flash command apparently need to be done twice to take effect,
4063 as the first is just preparations and the second one do the flashing.
4064 The adb command is just to get to the boot loader menu, so turning the
4065 device on while holding volume down and the power button should work
4066 too.&lt;/p&gt;
4067
4068 &lt;p&gt;With the new hboot version in place I could start following the
4069 instructions on the HTC developer web site. I got the device token
4070 like this:&lt;/p&gt;
4071
4072 &lt;p&gt;&lt;pre&gt;
4073 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
4074 &lt;/pre&gt;
4075
4076 &lt;p&gt;And once I got the unlock code via email, I could use it like
4077 this:&lt;/p&gt;
4078
4079 &lt;p&gt;&lt;pre&gt;
4080 fastboot flash unlocktoken Unlock_code.bin
4081 &lt;/pre&gt;&lt;/p&gt;
4082
4083 &lt;p&gt;And with that final step in place, the phone was unlocked and I
4084 could start stuffing the software of my own choosing into the device.
4085 So far I only inserted a replacement recovery image to wipe the phone
4086 before I start. We will see what happen next. Perhaps I should
4087 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
4088 </description>
4089 </item>
4090
4091 <item>
4092 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
4093 <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>
4094 <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>
4095 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
4096 <description>&lt;p&gt;For a while now, I have wanted to test
4097 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
4098 said to provide end to end encrypted communication and several of my
4099 friends and family are already using it. As I by choice do not own a
4100 mobile phone, this proved to be harder than expected. And I wanted to
4101 have the source of the client and know that it was the code used on my
4102 machine. But yesterday I managed to get it working. I used the
4103 Github source, compared it to the source in
4104 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
4105 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
4106 patches to use the production Signal servers, started the app and
4107 asked for the hidden &quot;register without a smart phone&quot; form. Here is
4108 the recipe how I did it.&lt;/p&gt;
4109
4110 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
4111
4112 &lt;pre&gt;
4113 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4114 &lt;/pre&gt;
4115
4116 &lt;p&gt;Next, I patched the source to use the production servers, to be
4117 able to talk to other Signal users:&lt;/p&gt;
4118
4119 &lt;pre&gt;
4120 cat &amp;lt;&amp;lt;EOF | patch -p0
4121 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
4122 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
4123 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
4124 @@ -47,8 +47,8 @@
4125 });
4126 });
4127
4128 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
4129 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
4130 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
4131 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
4132 var messageReceiver;
4133 window.getSocketStatus = function() {
4134 if (messageReceiver) {
4135 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
4136 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
4137 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
4138 @@ -1,6 +1,6 @@
4139 ;(function() {
4140 &#39;use strict&#39;;
4141 - var BUILD_EXPIRATION = 0;
4142 + var BUILD_EXPIRATION = 1474492690000;
4143
4144 window.extension = window.extension || {};
4145
4146 EOF
4147 &lt;/pre&gt;
4148
4149 &lt;p&gt;The first part is changing the servers, and the second is updating
4150 an expiration timestamp. This timestamp need to be updated regularly.
4151 It is set 90 days in the future by the build process (Gruntfile.js).
4152 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
4153
4154 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
4155 script to launch Signal in Chromium.&lt;/p&gt;
4156
4157 &lt;pre&gt;
4158 #!/bin/sh
4159 cd $(dirname $0)
4160 mkdir -p userdata
4161 exec chromium \
4162 --proxy-server=&quot;socks://localhost:9050&quot; \
4163 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4164 &lt;/pre&gt;
4165
4166 &lt;p&gt; The script start the app and configure Chromium to use the Tor
4167 SOCKS5 proxy to make sure those controlling the Signal servers (today
4168 Amazon and Whisper Systems) as well as those listening on the lines
4169 will have a harder time location my laptop based on the Signal
4170 connections if they use source IP address.&lt;/p&gt;
4171
4172 &lt;p&gt;When the script starts, one need to follow the instructions under
4173 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
4174 repository. I right clicked on the Signal window to get up the
4175 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
4176 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
4177 registration form. Then I entered by land line phone number and
4178 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
4179 repeated the verification code three times. After entering the number
4180 into the verification code field in the form, I could start using
4181 Signal from my laptop.
4182
4183 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
4184 whom and thus who know who to those controlling the central server,
4185 but such leakage is hard to avoid with a centrally controlled server
4186 setup. It is something to keep in mind when using Signal - the
4187 content of your chats are harder to intercept, but the meta data
4188 exposing your contact network is available to people you do not know.
4189 So better than many options, but not great. And sadly the usage is
4190 connected to my land line, thus allowing those controlling the server
4191 to associate it to my home and person. I would prefer it if only
4192 those I knew could tell who I was on Signal. There are options
4193 avoiding such information leakage, but most of my friends are not
4194 using them, so I am stuck with Signal for now.&lt;/p&gt;
4195
4196 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
4197 on this topic in
4198 &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
4199 and updated recipe for using the Signal app without a mobile
4200 phone&lt;/a&gt;.&lt;/p&gt;
4201 </description>
4202 </item>
4203
4204 <item>
4205 <title>The new &quot;best&quot; multimedia player in Debian?</title>
4206 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
4207 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
4208 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
4209 <description>&lt;p&gt;When I set out a few weeks ago to figure out
4210 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
4211 multimedia player in Debian claimed to support most file formats /
4212 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
4213 the various players claimed support for. The range was from 55 to 130
4214 MIME types. I suspect most media formats are supported by all
4215 players, but this is not really reflected in the MimeTypes values in
4216 their desktop files. There are probably also some bogus MIME types
4217 listed, but it is hard to identify which one this is.&lt;/p&gt;
4218
4219 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
4220 the players suggesting to add more MIME types to their desktop files,
4221 and decided to spend some time myself improving the situation for my
4222 favorite media player VLC. The fixes for VLC entered Debian unstable
4223 yesterday. The complete list of MIME types can be seen on the
4224 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
4225 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
4226
4227 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
4228 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4229 kmplayer. I am sure some of the other players desktop files support
4230 several of the formats currently listed as working only with vlc,
4231 toten and parole.&lt;/p&gt;
4232
4233 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
4234 supported by all the tested multimedia players in Debian in their
4235 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4236 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4237 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4238 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4239 it sad that video/ogg and video/webm is not supported by all the media
4240 players in Debian. As far as I can tell, all of them can handle both
4241 formats.&lt;/p&gt;
4242 </description>
4243 </item>
4244
4245 <item>
4246 <title>A program should be able to open its own files on Linux</title>
4247 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
4248 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
4249 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
4250 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
4251 decided to test its presentation tool when making the slides for a
4252 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4253 wrote the first draft of the slides, saved the result and went to bed
4254 the day before I would give the talk. The next day I took a plane to
4255 the location where the meeting should take place, and on the plane I
4256 started up koffice again to polish the talk a bit, only to discover
4257 that kpresenter refused to load its own data file. I cursed a bit and
4258 started making the slides again from memory, to have something to
4259 present when I arrived. I tested that the saved files could be
4260 loaded, and the day seemed to be rescued. I continued to polish the
4261 slides until I suddenly discovered that the saved file could no longer
4262 be loaded into kpresenter. In the end I had to rewrite the slides
4263 three times, condensing the content until the talk became shorter and
4264 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
4265 kpresenter wrote inline images in a way itself could not understand.
4266 Eventually that bug was fixed and kpresenter ended up being a great
4267 program to make slides. The point I&#39;m trying to make is that we
4268 expect a program to be able to load its own data files, and it is
4269 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
4270
4271 &lt;p&gt;Did you ever experience a program failing to load its own data
4272 files from the desktop file browser? It is not a uncommon problem. A
4273 while back I discovered that the screencast recorder
4274 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4275 browser would refuse to open. No video player claimed to understand
4276 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
4277 returning the application/ogg MIME type, which no video player I had
4278 installed listed as a MIME type they would understand. I asked for
4279 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
4280 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
4281 several video players to add video/ogg to their desktop files, to give
4282 the file browser an idea what to do about Ogg Theora files. After a
4283 while, the desktop file browsers in Debian started to handle the
4284 output from gtk-recordmydesktop properly.&lt;/p&gt;
4285
4286 &lt;p&gt;But history repeats itself. A few days ago I tested the music
4287 system Rosegarden again, and I discovered that the KDE and xfce file
4288 browsers did not know what to do with the Rosegarden project files
4289 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
4290 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
4291 included in the next upload. To increase the chance of me remembering
4292 how to fix the problem next time some program fail to load its files
4293 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
4294
4295 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
4296 There are two sources for the MIME type of a given file. The output from
4297 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
4298 shared MIME type registry (under /usr/share/mime/). The file MIME
4299 type is mapped to programs supporting the MIME type, and this
4300 information is collected from
4301 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
4302 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
4303 one desktop file claiming support for the MIME type of the file, it is
4304 activated when asking to open a given file. If there are more, one
4305 can normally select which one to use by right-clicking on the file and
4306 selecting the wanted one using &#39;Open with&#39; or similar. In general
4307 this work well. But it depend on each program picking a good MIME
4308 type (preferably
4309 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
4310 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
4311 registry recognizing the file and the desktop file to list the MIME
4312 type in its list of supported MIME types.&lt;/p&gt;
4313
4314 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
4315 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
4316 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4319 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4320 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
4321 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
4322 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
4323 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
4324 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
4325 &amp;lt;/mime-type&amp;gt;
4326 &amp;lt;/mime-info&amp;gt;
4327 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4328
4329 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
4330 (it is a gzipped XML file). Note, it is much better to use an
4331 official MIME type registered with IANA than it is to make up ones own
4332 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
4333
4334 &lt;p&gt;The desktop file of the rosegarden program failed to list
4335 audio/x-rosegarden in its list of supported MIME types, causing the
4336 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
4337
4338 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4339 % grep Mime /usr/share/applications/rosegarden.desktop
4340 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4341 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4342 %
4343 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4344
4345 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
4346 MimeType= line.&lt;/p&gt;
4347
4348 &lt;p&gt;If you run into a file which fail to open the correct program when
4349 selected from the file browser, please check out the output from
4350 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
4351 MIME type is registered somewhere under /usr/share/mime/ and check
4352 that some desktop file under /usr/share/applications/ is claiming
4353 support for this MIME type. If not, please report a bug to have it
4354 fixed. :)&lt;/p&gt;
4355 </description>
4356 </item>
4357
4358 <item>
4359 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
4360 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
4361 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
4362 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
4363 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
4364 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
4365 related packages. The idea is to have a database of mappings between
4366 hardware and packages, and pop up a dialog suggesting for the user to
4367 install the packages to use a given hardware dongle. Some use cases
4368 are when you insert a Yubikey, it proposes to install the software
4369 needed to control it; when you insert a braille reader list it
4370 proposes to install the packages needed to send text to the reader;
4371 and when you insert a ColorHug screen calibrator it suggests to
4372 install the driver for it. The system work well, and even have a few
4373 command line tools to install firmware packages and packages for the
4374 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
4375
4376 &lt;p&gt;The system was initially written using aptdaemon, because I found
4377 good documentation and example code on how to use it. But aptdaemon
4378 is going away and is generally being replaced by
4379 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
4380 so Isenkram needed a rewrite. And today, thanks to the great patch
4381 from my college Sunil Mohan Adapa in the FreedomBox project, the
4382 rewrite finally took place. I&#39;ve just uploaded a new version of
4383 Isenkram into Debian Unstable with the patch included, and the default
4384 for the background daemon is now to use PackageKit. To check it out,
4385 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
4386 and see if it is recognised.&lt;/p&gt;
4387
4388 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
4389 the machine it is running on, you can check out the isenkram-lookup
4390 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
4391
4392 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4393 % isenkram-lookup
4394 bluez
4395 cheese
4396 fprintd
4397 fprintd-demo
4398 gkrellm-thinkbat
4399 hdapsd
4400 libpam-fprintd
4401 pidgin-blinklight
4402 thinkfan
4403 tleds
4404 tp-smapi-dkms
4405 tp-smapi-source
4406 tpb
4407 %p
4408 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4409
4410 &lt;p&gt;The hardware mappings come from several places. The preferred way
4411 is for packages to announce their hardware support using
4412 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4413 cross distribution appstream system&lt;/a&gt;.
4414 See
4415 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
4416 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
4417 </description>
4418 </item>
4419
4420 <item>
4421 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
4422 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
4423 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
4424 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
4425 <description>&lt;p&gt;Yesterday I updated the
4426 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
4427 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
4428 enterprising users. There were some nice user and visible changes.
4429 First of all, both desktop menu entries now work. A design flaw in
4430 one of the script made the history graph fail to show up (its PNG was
4431 dumped in ~/.xsession-errors) if no controlling TTY was available.
4432 The script worked when called from the command line, but not when
4433 called from the desktop menu. I changed this to look for a DISPLAY
4434 variable or a TTY before deciding where to draw the graph, and now the
4435 graph window pop up as expected.&lt;/p&gt;
4436
4437 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
4438 graphs (the one showing the last few hours). New is also the user of
4439 colours showing charging in blue and discharge in red. The percentages
4440 of this graph is relative to last full charge, not battery design
4441 capacity.&lt;/p&gt;
4442
4443 &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;
4444
4445 &lt;p&gt;The other graph show the entire history of the collected battery
4446 statistics, comparing it to the design capacity of the battery to
4447 visualise how the battery life time get shorter over time. The red
4448 line in this graph is what the previous graph considers 100 percent:
4449
4450 &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;
4451
4452 &lt;p&gt;In this graph you can see that I only charge the battery to 80
4453 percent of last full capacity, and how the capacity of the battery is
4454 shrinking. :(&lt;/p&gt;
4455
4456 &lt;p&gt;The last new feature is in the collector, which now will handle
4457 more hardware models. On some hardware, Linux power supply
4458 information is stored in /sys/class/power_supply/ACAD/, while the
4459 collector previously only looked in /sys/class/power_supply/AC/. Now
4460 both are checked to figure if there is power connected to the
4461 machine.&lt;/p&gt;
4462
4463 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4464 check out the
4465 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4466 in Debian unstable, or rebuild it on Jessie to get it working on
4467 Debian stable. :) The upstream source is available from &lt;a
4468 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4469 Patches are very welcome.&lt;/p&gt;
4470
4471 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4472 activities, please send Bitcoin donations to my address
4473 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4474 </description>
4475 </item>
4476
4477 <item>
4478 <title>Debian now with ZFS on Linux included</title>
4479 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
4480 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
4481 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
4482 <description>&lt;p&gt;Today, after many years of hard work from many people,
4483 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
4484 Debian. The package status can be seen on
4485 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
4486 for zfs-linux&lt;/a&gt;. and
4487 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4488 team status page&lt;/a&gt;. If you want to help out, please join us.
4489 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
4490 source code&lt;/a&gt; is available via git on Alioth. It would also be
4491 great if you could help out with
4492 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
4493 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
4494 </description>
4495 </item>
4496
4497 <item>
4498 <title>What is the best multimedia player in Debian?</title>
4499 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
4500 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
4501 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
4502 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
4503 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
4504
4505 &lt;p&gt;A few years ago, I had a look at the media support for Browser
4506 plugins in Debian, to get an idea which plugins to include in Debian
4507 Edu. I created a script to extract the set of supported MIME types
4508 for each plugin, and used this to find out which multimedia browser
4509 plugin supported most file formats / media types.
4510 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
4511 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
4512 not been updated for a while. But browser plugins are less relevant
4513 these days, so I thought it was time to look at standalone
4514 players.&lt;/p&gt;
4515
4516 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
4517 player when I wanted to play videos from the Norwegian National
4518 Broadcasting Company, and decided to investigate why. The cause is a
4519 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
4520 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
4521 of MIME types announced in the desktop file and the browser plugin,
4522 only to discover that there is quite a large difference between the
4523 two for VLC. This discovery made me dig up the script I used to
4524 compare browser plugins, and adjust it to compare desktop files
4525 instead, to try to figure out which multimedia player in Debian
4526 support most file formats.&lt;/p&gt;
4527
4528 &lt;p&gt;The result can be seen on the Debian Wiki, as
4529 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
4530 table listing all MIME types supported by one of the packages included
4531 in the table&lt;/a&gt;, with the package supporting most MIME types being
4532 listed first in the table.&lt;/p&gt;
4533
4534 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
4535 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4536 kmplayer. Time for the other players to update their announced MIME
4537 support?&lt;/p&gt;
4538 </description>
4539 </item>
4540
4541 <item>
4542 <title>The Pyra - handheld computer with Debian preinstalled</title>
4543 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
4544 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
4545 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
4546 <description>A friend of mine made me aware of
4547 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
4548 handheld computer which will be delivered with Debian preinstalled. I
4549 would love to get one of those for my birthday. :)&lt;/p&gt;
4550
4551 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4552 plugs and many others connectors, and include a full keyboard and a 5&quot;
4553 LCD touch screen. The 6000mAh battery is claimed to provide a whole
4554 day of battery life time, but I have not seen any independent tests
4555 confirming this. The vendor is still collecting preorders, and the
4556 last I heard last night was that 22 more orders were needed before
4557 production started.&lt;/p&gt;
4558
4559 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
4560 Debian. Please let me know if you know of any others. Is it the
4561 first computer being sold with Debian preinstalled?&lt;/p&gt;
4562 </description>
4563 </item>
4564
4565 <item>
4566 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
4567 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
4568 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
4569 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
4570 <description>&lt;p&gt;During this weekends
4571 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
4572 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
4573 to make sure there are good books about Debian available in Norwegian
4574 Bokmål, and got in touch with the people behind the
4575 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
4576 project&lt;/a&gt; to get started. If you want to help out, please start
4577 contributing using
4578 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
4579 hosted weblate project page&lt;/a&gt;, and get in touch using
4580 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
4581 translators mailing list&lt;/a&gt;. Please also check out
4582 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
4583 contributors&lt;/a&gt;.&lt;/p&gt;
4584
4585 &lt;p&gt;The book is already available on paper in English, French and
4586 Japanese, and our goal is to get it available on paper in Norwegian
4587 Bokmål too. In addition to the paper edition, there are also EPUB and
4588 Mobi versions available. And there are incomplete translations
4589 available for many more languages.&lt;/p&gt;
4590 </description>
4591 </item>
4592
4593 <item>
4594 <title>One in two hundred Debian users using ZFS on Linux?</title>
4595 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
4596 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
4597 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
4598 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
4599 packages in Debian, and was quite surprised with what I found. I use
4600 ZFS myself at home, but did not really expect many others to do so.
4601 But I might be wrong.&lt;/p&gt;
4602
4603 &lt;p&gt;According to
4604 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
4605 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
4606 0.53% of the population, with the package installed. As far as I know
4607 the only use of the spl-linux package is as a support library for ZFS
4608 on Linux, so I use it here as proxy for measuring the number of ZFS
4609 installation on Linux in Debian. In the kFreeBSD variant of Debian
4610 the ZFS feature is already available, and there
4611 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
4612 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
4613 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
4614
4615 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
4616 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
4617 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
4618 cleared, the package is still not in Debian. The package is again in
4619 the NEW queue. Several uploads have been rejected so far because the
4620 debian/copyright file was incomplete or wrong, but there is no reason
4621 to give up. The current status can be seen on
4622 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4623 team status page&lt;/a&gt;, and
4624 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
4625 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
4626
4627 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
4628 my home server can function in the future using only official Debian
4629 packages, and the current blocker is to get the debian/copyright file
4630 accepted by the FTP masters in Debian, I decided a while back to try
4631 to help out the team. This was the background for my blog post about
4632 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
4633 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
4634 used the techniques I explored there to try to find any errors in the
4635 copyright file. It is not very easy to check every one of the around
4636 2000 files in the source package, but I hope we this time got it
4637 right. If you want to help out, check out the git source and try to
4638 find missing entries in the debian/copyright file.&lt;/p&gt;
4639 </description>
4640 </item>
4641
4642 <item>
4643 <title>Full battery stats collector is now available in Debian</title>
4644 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
4645 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
4646 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
4647 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
4648 extended collector that will collect the complete battery history for
4649 later processing and graphing. The original collector store the
4650 battery level as percentage of last full level, while the new
4651 collector also record battery vendor, model, serial number, design
4652 full level, last full level and current battery level. This make it
4653 possible to predict the lifetime of the battery as well as visualise
4654 the energy flow when the battery is charging or discharging.&lt;/p&gt;
4655
4656 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
4657 in the version 0.5.1 package in unstable. Get the new battery level graph
4658 and lifetime prediction by running:
4659
4660 &lt;p&gt;&lt;pre&gt;
4661 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4662 &lt;/pre&gt;&lt;/p&gt;
4663
4664 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
4665
4666 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
4667 entry yet):&lt;/p&gt;
4668
4669 &lt;p&gt;&lt;pre&gt;
4670 /usr/share/battery-stats/battery-stats-graph-flow
4671 &lt;/pre&gt;&lt;/p&gt;
4672
4673 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
4674 when there are few data points. The graphs look a bit better with a
4675 few years of data.&lt;/p&gt;
4676
4677 &lt;p&gt;A while back one important feature I use in the battery stats
4678 collector broke in Debian. The scripts in
4679 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4680 suspect it happened when Jessie started using systemd, but I do not
4681 know. The issue is reported as
4682 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4683 pm-utils. I managed to work around it by adding an udev rule to call
4684 the collector script every time the power connector is connected and
4685 disconnected. With this fix in place it was finally time to make a
4686 new release of the package, and get it into Debian.&lt;/p&gt;
4687
4688 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4689 check out the
4690 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4691 in Debian unstable, or rebuild it on Jessie to get it working on
4692 Debian stable. :) The upstream source is available from
4693 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4694 As always, patches are very welcome.&lt;/p&gt;
4695 </description>
4696 </item>
4697
4698 <item>
4699 <title>Making battery measurements a little easier in Debian</title>
4700 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4701 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4702 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4703 <description>&lt;p&gt;Back in September, I blogged about
4704 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4705 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4706 how it showed the decay and death of this battery (now replaced). I
4707 created a simple deb package to handle the collection and graphing,
4708 but did not want to upload it to Debian as there were already
4709 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4710 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4711 a point of uploading a competing package when battery-stats could be
4712 fixed instead. I reported a few bugs about its non-function, and
4713 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4714
4715 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4716 hands. The end result is that I am now the new upstream developer of
4717 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
4718 battery-stats in Debian, and the package in Debian unstable is finally
4719 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4720 information provided by the Linux kernel. If you install the
4721 battery-stats package from unstable now, you will be able to get a
4722 graph of the current battery fill level, to get some idea about the
4723 status of the battery. The source package build and work just fine in
4724 Debian testing and stable (and probably oldstable too, but I have not
4725 tested). The default graph you get for that system look like this:&lt;/p&gt;
4726
4727 &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;
4728
4729 &lt;p&gt;My plans for the future is to merge my old scripts into the
4730 battery-stats package, as my old scripts collected a lot more details
4731 about the battery. The scripts are merged into the upstream
4732 battery-stats git repository already, but I am not convinced they work
4733 yet, as I changed a lot of paths along the way. Will have to test a
4734 bit more before I make a new release.&lt;/p&gt;
4735
4736 &lt;p&gt;I will also consider changing the file format slightly, as I
4737 suspect the way I combine several values into one field might make it
4738 impossible to know the type of the value when using it for processing
4739 and graphing.&lt;/p&gt;
4740
4741 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4742 battery, check out the battery-stats package in
4743 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4744 on
4745 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4746 I would love some help to improve the system further.&lt;/p&gt;
4747 </description>
4748 </item>
4749
4750 <item>
4751 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4752 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4753 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4754 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4755 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4756 details. And one of the details is the content of the
4757 debian/copyright file, which should list all relevant licenses used by
4758 the code in the package in question, preferably in
4759 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4760 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4761
4762 &lt;p&gt;For large packages with lots of contributors it is hard to write
4763 and update this file manually, and if you get some detail wrong, the
4764 package is normally rejected by the ftpmasters. So getting it right
4765 the first time around get the package into Debian faster, and save
4766 both you and the ftpmasters some work.. Today, while trying to figure
4767 out what was wrong with
4768 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4769 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4770 figuring out the options for doing this job automatically, or at least
4771 semi-automatically.&lt;/p&gt;
4772
4773 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4774 file based on the code in the source package,
4775 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4776 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
4777 not sure which one of them came first, but both seem to be able to
4778 create a sensible draft file. As far as I can tell, none of them can
4779 be trusted to get the result just right, so the content need to be
4780 polished a bit before the file is OK to upload. I found the debmake
4781 option in
4782 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4783 blog posts from 2014&lt;/a&gt;.
4784
4785 &lt;p&gt;To generate using debmake, use the -cc option:
4786
4787 &lt;p&gt;&lt;pre&gt;
4788 debmake -cc &gt; debian/copyright
4789 &lt;/pre&gt;&lt;/p&gt;
4790
4791 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4792 this might not be the best option.&lt;/p&gt;
4793
4794 &lt;p&gt;The cme option is based on a config parsing library, and I found
4795 this approach in
4796 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
4797 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
4798 dpkg-copyright&#39; option:
4799
4800 &lt;p&gt;&lt;pre&gt;
4801 cme update dpkg-copyright
4802 &lt;/pre&gt;&lt;/p&gt;
4803
4804 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
4805 handle UTF-8 names better than debmake.&lt;/p&gt;
4806
4807 &lt;p&gt;When the copyright file is created, I would also like some help to
4808 check if the file is correct. For this I found two good options,
4809 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
4810 to focus on license types and file matching, and is able to detect
4811 ineffective blocks in the copyright file. The latter reports missing
4812 copyright holders and years, but was confused by inconsistent license
4813 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
4814 fix all issues reported by them before uploading. But I do not know
4815 if the tools and the ftpmasters agree on what is important to fix in a
4816 copyright file, so the package might still be rejected.&lt;/p&gt;
4817
4818 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
4819 will read through the source and try to find all copyright statements.
4820 It is not comparing the result to the content of debian/copyright, but
4821 can be useful when verifying the content of the copyright file.&lt;/p&gt;
4822
4823 &lt;p&gt;Are you aware of better tools in Debian to create and update
4824 debian/copyright file. Please let me know, or blog about it on
4825 planet.debian.org.&lt;/p&gt;
4826
4827 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4828 activities, please send Bitcoin donations to my address
4829 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4830
4831 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
4832 on how to use licensecheck and cdbs to create a draft copyright file
4833
4834 &lt;p&gt;&lt;pre&gt;
4835 licensecheck --copyright -r `find * -type f` | \
4836 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
4837 &lt;/pre&gt;&lt;/p&gt;
4838
4839 &lt;p&gt;He mentioned that he normally check the generated file into the
4840 version control system to make it easier to discover license and
4841 copyright changes in the upstream source. I will try to do the same
4842 with my packages in the future.&lt;/p&gt;
4843
4844 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
4845 against using -quiet for new users, so I removed it from the proposed
4846 command line.&lt;/p&gt;
4847 </description>
4848 </item>
4849
4850 <item>
4851 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
4852 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
4853 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
4854 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
4855 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
4856 is taking shape in Debian, and one provided feature is a very
4857 convenient way to tell you which package to install to make a given
4858 firmware file available when the kernel is looking for it. This can
4859 be done using apt-file too, but that is for someone else to blog
4860 about. :)&lt;/p&gt;
4861
4862 &lt;p&gt;Here is a small recipe to find the package with a given firmware
4863 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
4864 picked from the set of firmware announced using appstream in Debian
4865 unstable. In general you would be looking for the firmware requested
4866 by the kernel during kernel module loading. To find the package
4867 providing the example file, do like this:&lt;/p&gt;
4868
4869 &lt;blockquote&gt;&lt;pre&gt;
4870 % apt install appstream
4871 [...]
4872 % apt update
4873 [...]
4874 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
4875 awk &#39;/Package:/ {print $2}&#39;
4876 firmware-qlogic
4877 %
4878 &lt;/pre&gt;&lt;/blockquote&gt;
4879
4880 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
4881 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
4882 a way appstream can use.&lt;/p&gt;
4883
4884 &lt;p&gt;This same approach can be used to find any package supporting a
4885 given MIME type. This is very useful when you get a file you do not
4886 know how to handle. First find the mime type using &lt;tt&gt;file
4887 --mime-type&lt;/tt&gt;, and next look up the package providing support for
4888 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4889 and you can find all packages handling this type like this:&lt;/p&gt;
4890
4891 &lt;blockquote&gt;&lt;pre&gt;
4892 % apt install appstream
4893 [...]
4894 % apt update
4895 [...]
4896 % appstreamcli what-provides mimetype image/svg+xml | \
4897 awk &#39;/Package:/ {print $2}&#39;
4898 bkchem
4899 phototonic
4900 inkscape
4901 shutter
4902 tetzle
4903 geeqie
4904 xia
4905 pinta
4906 gthumb
4907 karbon
4908 comix
4909 mirage
4910 viewnior
4911 postr
4912 ristretto
4913 kolourpaint4
4914 eog
4915 eom
4916 gimagereader
4917 midori
4918 %
4919 &lt;/pre&gt;&lt;/blockquote&gt;
4920
4921 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
4922 packages providing appstream metadata.&lt;/p&gt;
4923 </description>
4924 </item>
4925
4926 <item>
4927 <title>Creepy, visualise geotagged social media information - nice free software</title>
4928 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
4929 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
4930 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
4931 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
4932 with the computerised radio beacon known as a mobile phone their
4933 position is tracked by the phone company and often stored for a long
4934 time (like every time a SMS is received or sent). And if their
4935 computerised radio beacon is capable of running programs (often called
4936 mobile apps) downloaded from the Internet, these programs are often
4937 also capable of tracking their location (if the app requested access
4938 during installation). And when these programs send out information to
4939 central collection points, the location is often included, unless
4940 extra care is taken to not send the location. The provided
4941 information is used by several entities, for good and bad (what is
4942 good and bad, depend on your point of view). What is certain, is that
4943 the private sphere and the right to free movement is challenged and
4944 perhaps even eradicated for those announcing their location this way,
4945 when they share their whereabouts with private and public
4946 entities.&lt;/p&gt;
4947
4948 &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;
4949
4950 &lt;p&gt;The phone company logs provide a register of locations to check out
4951 when one want to figure out what the tracked person was doing. It is
4952 unavailable for most of us, but provided to selected government
4953 officials, company staff, those illegally buying information from
4954 unfaithful servants and crackers stealing the information. But the
4955 public information can be collected and analysed, and a free software
4956 tool to do so is called
4957 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
4958 discovered it when I read
4959 &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
4960 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
4961 November 2014, and decided to check if it was available in Debian.
4962 The python program was in Debian, but
4963 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
4964 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
4965 uploaded a new version which did not work quite right, but did not
4966 have time to fix it then. This Christmas I decided to finally try to
4967 get Creepy operational in Debian. Now a fixed version is available in
4968 Debian unstable and testing, and almost all Debian specific patches
4969 are now included
4970 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
4971
4972 &lt;p&gt;The Creepy program visualises geolocation information fetched from
4973 Twitter, Instagram, Flickr and Google+, and allow one to get a
4974 complete picture of every social media message posted recently in a
4975 given area, or track the movement of a given individual across all
4976 these services. Earlier it was possible to use the search API of at
4977 least some of these services without identifying oneself, but these
4978 days it is impossible. This mean that to use Creepy, you need to
4979 configure it to log in as yourself on these services, and provide
4980 information to them about your search interests. This should be taken
4981 into account when using Creepy, as it will also share information
4982 about yourself with the services.&lt;/p&gt;
4983
4984 &lt;p&gt;The picture above show the twitter messages sent from (or at least
4985 geotagged with a position from) the city centre of Oslo, the capital
4986 of Norway. One useful way to use Creepy is to first look at
4987 information tagged with an area of interest, and next look at all the
4988 information provided by one or more individuals who was in the area.
4989 I tested it by checking out which celebrity provide their location in
4990 twitter messages by checkout out who sent twitter messages near a
4991 Norwegian TV station, and next could track their position over time,
4992 making it possible to locate their home and work place, among other
4993 things. A similar technique have been
4994 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
4995 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
4996 tool to discover lying governments, and a useful tool to help people
4997 understand the value of the private information they provide to the
4998 public.&lt;/p&gt;
4999
5000 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
5001 it depend on several python modules currently missing in Jessie (at
5002 least python-instagram, python-flickrapi and
5003 python-requests-toolbelt).&lt;/p&gt;
5004
5005 &lt;p&gt;(I have uploaded
5006 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
5007 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
5008 Creepy program in Debian.)&lt;/p&gt;
5009 </description>
5010 </item>
5011
5012 <item>
5013 <title>Always download Debian packages using Tor - the simple recipe</title>
5014 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
5015 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
5016 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
5017 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
5018 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
5019 that those listening on the Internet lines would have good reason to
5020 believe a computer have a given security hole&lt;/a&gt; if it download a
5021 security fix from a Debian mirror. This is a good reason to always
5022 use encrypted connections to the Debian mirror, to make sure those
5023 listening do not know which IP address to attack. In August, Richard
5024 Hartmann observed that encryption was not enough, when it was possible
5025 to interfere download size to security patches or the fact that
5026 download took place shortly after a security fix was released, and
5027 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
5028 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
5029 was not the first to propose this, as the
5030 &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;
5031 package by Tim Retout already existed to make it easy to convince apt
5032 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
5033 aware of that package when I read the blog post from Richard.&lt;/p&gt;
5034
5035 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
5036 sysadmins, and he set up a Tor hidden service on one of the central
5037 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
5038 it possible to download packages directly between two tor nodes,
5039 making sure the network traffic always were encrypted.&lt;/p&gt;
5040
5041 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
5042 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
5043 urls with tor+http and tor+https, and using the hidden service instead
5044 of the official Debian mirror site. I recommend installing
5045 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
5046 done in /etc/.&lt;/p&gt;
5047
5048 &lt;blockquote&gt;&lt;pre&gt;
5049 apt install apt-transport-tor
5050 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
5051 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
5052 &lt;/pre&gt;&lt;/blockquote&gt;
5053
5054 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
5055 the sed commands for these too. The sed command is assuming your are
5056 using the ftp.debian.org Debian mirror. Adjust the command (or just
5057 edit the file manually) to match your mirror.&lt;/p&gt;
5058
5059 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
5060 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
5061 system, and do not work with these tor+http URLs. For
5062 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
5063 which need a recent apt version currently only in unstable. So if you
5064 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
5065
5066 &lt;p&gt;Another advantage from this change is that your machine will start
5067 using Tor regularly and at fairly random intervals (every time you
5068 update the package lists or upgrade or install a new package), thus
5069 masking other Tor traffic done from the same machine. Using Tor will
5070 become normal for the machine in question.&lt;/p&gt;
5071
5072 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
5073 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
5074 enabled. It would be great if it was the default on any Debian
5075 system.&lt;/p&gt;
5076 </description>
5077 </item>
5078
5079 <item>
5080 <title>OpenALPR, find car license plates in video streams - nice free software</title>
5081 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
5082 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
5083 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
5084 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
5085 call the car license plate numbers in those days. I would write the
5086 numbers down in my little book and compare notes with the other kids
5087 to see how many region codes we had seen and if we had seen some
5088 exotic or special region codes and numbers. It was a fun game to pass
5089 time, as we kids have plenty of it.&lt;/p&gt;
5090
5091 &lt;p&gt;A few days I came across
5092 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
5093 project&lt;/a&gt;, a free software project to automatically discover and
5094 report license plates in images and video streams, and provide the
5095 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
5096 such system for a while now, because I believe it is a bad idea that the
5097 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
5098 number plate recognition&lt;/a&gt; tool only is available in the hands of
5099 the powerful, and want it to be available also for the powerless to
5100 even the score when it comes to surveillance and sousveillance. I
5101 discovered the developer
5102 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
5103 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
5104 help him get it into shape to get the package uploaded into the Debian
5105 archive.&lt;/p&gt;
5106
5107 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
5108 it into Debian, where it currently
5109 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
5110 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
5111
5112 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
5113 for the common folks, ie those not running a large government
5114 surveillance system? Well, I plan to put it in a computer on my bike
5115 and in my car, tracking the cars nearby and allowing me to be notified
5116 when number plates on my watch list are discovered. Another use case
5117 was suggested by a friend of mine, who wanted to set it up at his home
5118 to open the car port automatically when it discovered the plate on his
5119 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5120 capable of placing his license plate number of a piece of cardboard to
5121 open his car port, men replied that it was always unlocked anyway. I
5122 guess for such use case it make sense. I am sure there are other use
5123 cases too, for those with imagination and a vision.&lt;/p&gt;
5124
5125 &lt;p&gt;If you want to build your own version of the Debian package, check
5126 out the upstream git source and symlink ./distros/debian to ./debian/
5127 before running &quot;debuild&quot; to build the source. Or wait a bit until the
5128 package show up in unstable.&lt;/p&gt;
5129 </description>
5130 </item>
5131
5132 <item>
5133 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
5134 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
5135 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
5136 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
5137 <description>&lt;p&gt;Around three years ago, I created
5138 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
5139 system&lt;/a&gt; to get a more practical solution in Debian for handing
5140 hardware related packages. A GUI system in the isenkram package will
5141 present a pop-up dialog when some hardware dongle supported by
5142 relevant packages in Debian is inserted into the machine. The same
5143 lookup mechanism to detect packages is available as command line
5144 tools in the isenkram-cli package. In addition to mapping hardware,
5145 it will also map kernel firmware files to packages and make it easy to
5146 install needed firmware packages automatically. The key for this
5147 system to work is a good way to map hardware to packages, in other
5148 words, allow packages to announce what hardware they will work
5149 with.&lt;/p&gt;
5150
5151 &lt;p&gt;I started by providing data files in the isenkram source, and
5152 adding code to download the latest version of these data files at run
5153 time, to ensure every user had the most up to date mapping available.
5154 I also added support for storing the mapping in the Packages file in
5155 the apt repositories, but did not push this approach because while I
5156 was trying to figure out how to best store hardware/package mappings,
5157 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
5158 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
5159 add the hardware mapping into that data set to be able to use
5160 appstream as a data source, and this was accepted at least for the
5161 Debian version of appstream.&lt;/p&gt;
5162
5163 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
5164 and today I uploaded a new version 0.20 of isenkram adding support for
5165 appstream as a data source for mapping hardware to packages. The only
5166 package so far using appstream to announce its hardware support is my
5167 pymissile package. I got help from Matthias Klumpp with figuring out
5168 how do add the required
5169 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
5170 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
5171 this content:&lt;/p&gt;
5172
5173 &lt;blockquote&gt;&lt;pre&gt;
5174 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
5175 &amp;lt;component&amp;gt;
5176 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
5177 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
5178 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
5179 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
5180 &amp;lt;description&amp;gt;
5181 &amp;lt;p&amp;gt;
5182 Pymissile provides a curses interface to control an original
5183 Marks and Spencer / Striker USB Missile Launcher, as well as a
5184 motion control script to allow a webcamera to control the
5185 launcher.
5186 &amp;lt;/p&amp;gt;
5187 &amp;lt;/description&amp;gt;
5188 &amp;lt;provides&amp;gt;
5189 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
5190 &amp;lt;/provides&amp;gt;
5191 &amp;lt;/component&amp;gt;
5192 &lt;/pre&gt;&lt;/blockquote&gt;
5193
5194 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
5195 which is a glob style match rule for hardware specific strings
5196 (modalias strings) provided by the Linux kernel. In this case, it
5197 will map to all USB devices with vendor code 1130 and product code
5198 0202.&lt;/p&gt;
5199
5200 &lt;p&gt;Note, it is important that the license of all the metadata files
5201 are compatible to have permissions to aggregate them into archive wide
5202 appstream files. Matthias suggested to use MIT or BSD licenses for
5203 these files. A challenge is figuring out a good id for the data, as
5204 it is supposed to be globally unique and shared across distributions
5205 (in other words, best to coordinate with upstream what to use). But
5206 it can be changed later or, so we went with the package name as
5207 upstream for this project is dormant.&lt;/p&gt;
5208
5209 &lt;p&gt;To get the metadata file installed in the correct location for the
5210 mirror update scripts to pick it up and include its content the
5211 appstream data source, the file must be installed in the binary
5212 package under /usr/share/appdata/. I did this by adding the following
5213 line to debian/pymissile.install:&lt;/p&gt;
5214
5215 &lt;blockquote&gt;&lt;pre&gt;
5216 debian/pymissile.metainfo.xml usr/share/appdata
5217 &lt;/pre&gt;&lt;/blockquote&gt;
5218
5219 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
5220 all packages useful on the current computer automatically, and the GUI
5221 pop-up handler will propose to install the package not already
5222 installed if a hardware dongle is inserted into the machine in
5223 question.&lt;/p&gt;
5224
5225 &lt;p&gt;Details of the modalias field in appstream is available from the
5226 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
5227
5228 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
5229 try running this command on the command line:&lt;/p&gt;
5230
5231 &lt;blockquote&gt;&lt;pre&gt;
5232 cat $(find /sys/devices/|grep modalias)
5233 &lt;/pre&gt;&lt;/blockquote&gt;
5234
5235 &lt;p&gt;To learn more about the isenkram system, please check out
5236 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
5237 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
5238 </description>
5239 </item>
5240
5241 <item>
5242 <title>The GNU General Public License is not magic pixie dust</title>
5243 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
5244 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
5245 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
5246 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
5247 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
5248 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
5249 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
5250 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
5251
5252 &lt;blockquote&gt;
5253
5254 &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;
5255
5256 &lt;blockquote&gt;
5257 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
5258
5259 The first step is to choose a
5260 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
5261 code.&lt;br/&gt;
5262
5263 The next step is, when someone fails to follow that copyleft license,
5264 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
5265
5266 and its a simple fact of our modern society that such type of
5267 work&lt;br/&gt;
5268
5269 is incredibly expensive to do and incredibly difficult to do.
5270 &lt;/blockquote&gt;
5271
5272 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
5273 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
5274 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
5275 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
5276
5277 &lt;p&gt;As the Debian Website
5278 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
5279 &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;
5280 imply, public domain and permissively licensed software can lead to
5281 the production of more proprietary software as people discover useful
5282 software, extend it and or incorporate it into their hardware or
5283 software products. Copyleft licenses such as the GNU GPL were created
5284 to close off this avenue to the production of proprietary software but
5285 such licenses are not enough. With the ongoing adoption of Free
5286 Software by individuals and groups, inevitably the community&#39;s
5287 expectations of license compliance are violated, usually out of
5288 ignorance of the way Free Software works, but not always. As Karen
5289 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
5290 Freedom&quot;&gt;FaiF&lt;/a&gt;
5291 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
5292 copyleft is nothing if no-one is willing and able to stand up in court
5293 to protect it. The reality of today&#39;s world is that legal
5294 representation is expensive, difficult and time consuming. With
5295 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
5296 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
5297 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
5298 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
5299 of the Linux project, Debian and other groups against GPL violations.
5300 In March the SFC supported a
5301 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
5302 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
5303 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
5304 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
5305 kernel. Since then two of their sponsors pulled corporate funding and
5306 conferences
5307 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
5308 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
5309 less on corporate funding and more on the broad community of
5310 individuals who support Free Software and copyleft. So the SFC has
5311 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
5312 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
5313 a community of folks who stand up for copyleft and the GPL by
5314 supporting their work on promoting and supporting copyleft and Free
5315 Software.&lt;/p&gt;
5316
5317 &lt;p&gt;If you support Free Software,
5318 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
5319 what the SFC do, agree with their
5320 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
5321 principles&lt;/a&gt;, are happy about their
5322 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
5323 work on a project that is an SFC
5324 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
5325 just want to stand up for copyleft, please join
5326 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
5327 Allan Webber&lt;/a&gt;,
5328 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
5329 Smith&lt;/a&gt;,
5330 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
5331 Bacon&lt;/a&gt;, myself and
5332 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
5333 becoming a
5334 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
5335 next week your donation will be
5336 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
5337 by an anonymous donor. Please also consider asking your employer to
5338 match your donation or become a sponsor of SFC. Don&#39;t forget to
5339 spread the word about your support for SFC via email, your blog and or
5340 social media accounts.&lt;/p&gt;
5341
5342 &lt;/blockquote&gt;
5343
5344 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
5345 of Software Freedom Conservancy myself. Perhaps you should be a
5346 supporter too?&lt;/p&gt;
5347 </description>
5348 </item>
5349
5350 <item>
5351 <title>PGP key transition statement for key EE4E02F9</title>
5352 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
5353 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
5354 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
5355 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
5356 set it up properly. I wanted to generate it offline and have it
5357 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
5358 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
5359 time to sit down with an offline machine almost took forever. But
5360 finally I&#39;ve been able to complete the process, and have now moved
5361 from my old GPG key to a new GPG key. See
5362 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
5363 full transition statement, signed with both my old and new key&lt;/a&gt; for
5364 the details. This is my new key:&lt;/p&gt;
5365
5366 &lt;pre&gt;
5367 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]
5368 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
5369 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
5370 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
5371 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
5372 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
5373 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
5374 &lt;/pre&gt;
5375
5376 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
5377 my old key.&lt;/p&gt;
5378
5379 &lt;p&gt;If you signed my old key
5380 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
5381 I&#39;d very much appreciate a signature on my new key, details and
5382 instructions in the transition statement. I m happy to reciprocate if
5383 you have a similarly signed transition statement to present.&lt;/p&gt;
5384 </description>
5385 </item>
5386
5387 <item>
5388 <title>The life and death of a laptop battery</title>
5389 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
5390 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
5391 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
5392 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
5393 But this do not last. The last few laptops gave me a feeling that
5394 within a year, the life time is just a fraction of what it used to be,
5395 and it slowly become painful to use the laptop without power connected
5396 all the time. Because of this, when I got a new Thinkpad X230 laptop
5397 about two years ago, I decided to monitor its battery state to have
5398 more hard facts when the battery started to fail.&lt;/p&gt;
5399
5400 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
5401
5402 &lt;p&gt;First I tried to find a sensible Debian package to record the
5403 battery status, assuming that this must be a problem already handled
5404 by someone else. I found
5405 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
5406 which collects statistics from the battery, but it was completely
5407 broken. I sent a few suggestions to the maintainer, but decided to
5408 write my own collector as a shell script while I waited for feedback
5409 from him. Via
5410 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
5411 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
5412 discovered
5413 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
5414 available in Debian.&lt;/p&gt;
5415
5416 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
5417 battery stats ever since. Now my
5418 /var/log/hjemmenett-battery-status.log file contain around 115,000
5419 measurements, from the time the battery was working great until now,
5420 when it is unable to charge above 7% of original capacity. My
5421 collector shell script is quite simple and look like this:&lt;/p&gt;
5422
5423 &lt;pre&gt;
5424 #!/bin/sh
5425 # Inspired by
5426 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
5427 # See also
5428 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
5429 logfile=/var/log/hjemmenett-battery-status.log
5430
5431 files=&quot;manufacturer model_name technology serial_number \
5432 energy_full energy_full_design energy_now cycle_count status&quot;
5433
5434 if [ ! -e &quot;$logfile&quot; ] ; then
5435 (
5436 printf &quot;timestamp,&quot;
5437 for f in $files; do
5438 printf &quot;%s,&quot; $f
5439 done
5440 echo
5441 ) &gt; &quot;$logfile&quot;
5442 fi
5443
5444 log_battery() {
5445 # Print complete message in one echo call, to avoid race condition
5446 # when several log processes run in parallel.
5447 msg=$(printf &quot;%s,&quot; $(date +%s); \
5448 for f in $files; do \
5449 printf &quot;%s,&quot; $(cat $f); \
5450 done)
5451 echo &quot;$msg&quot;
5452 }
5453
5454 cd /sys/class/power_supply
5455
5456 for bat in BAT*; do
5457 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
5458 done
5459 &lt;/pre&gt;
5460
5461 &lt;p&gt;The script is called when the power management system detect a
5462 change in the power status (power plug in or out), and when going into
5463 and out of hibernation and suspend. In addition, it collect a value
5464 every 10 minutes. This make it possible for me know when the battery
5465 is discharging, charging and how the maximum charge change over time.
5466 The code for the Debian package
5467 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
5468 available on github&lt;/a&gt;.&lt;/p&gt;
5469
5470 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
5471
5472 &lt;pre&gt;
5473 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5474 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
5475 [...]
5476 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5477 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5478 &lt;/pre&gt;
5479
5480 &lt;p&gt;I wrote a small script to create a graph of the charge development
5481 over time. This graph depicted above show the slow death of my laptop
5482 battery.&lt;/p&gt;
5483
5484 &lt;p&gt;But why is this happening? Why are my laptop batteries always
5485 dying in a year or two, while the batteries of space probes and
5486 satellites keep working year after year. If we are to believe
5487 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
5488 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
5489 chance, and the fix is to not charge the Lithium-ion batteries to 100%
5490 all the time, but to stay below 90% of full charge most of the time.
5491 I&#39;ve been told that the Tesla electric cars
5492 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
5493 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
5494 100% when preparing for a longer trip (not that I would want a car
5495 like Tesla where rights to privacy is abandoned, but that is another
5496 story), which I guess is the option we should have for laptops on
5497 Linux too.&lt;/p&gt;
5498
5499 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
5500 stop charging at 80%, unless requested to charge to 100% once in
5501 preparation for a longer trip? I found
5502 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
5503 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5504 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
5505 load).&lt;/p&gt;
5506
5507 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
5508 at the start. I also wonder why the &quot;full capacity&quot; increases some
5509 times, and if it is possible to repeat the process to get the battery
5510 back to design capacity. And I wonder if the discharge and charge
5511 speed change over time, or if this stay the same. I did not yet try
5512 to write a tool to calculate the derivative values of the battery
5513 level, but suspect some interesting insights might be learned from
5514 those.&lt;/p&gt;
5515
5516 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
5517 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5518 packages instead of the tp-smapi-dkms package I had tried to use
5519 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
5520 and stop. I&#39;ve done so now, but expect my existing battery is toast
5521 and need to be replaced. The proposal is unfortunately Thinkpad
5522 specific.&lt;/p&gt;
5523 </description>
5524 </item>
5525
5526 <item>
5527 <title>New laptop - some more clues and ideas based on feedback</title>
5528 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
5529 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
5530 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
5531 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
5532 need for a new laptop, and provided very useful feedback. I wish to
5533 thank every one of these. Several pointed me to the possibility of
5534 fixing my X230, and I am already in the process of getting Lenovo to
5535 do so thanks to the on site, next day support contract covering the
5536 machine. But the battery is almost useless (I expect to replace it
5537 with a non-official battery) and I do not expect the machine to live
5538 for many more years, so it is time to plan its replacement. If I did
5539 not have a support contract, it was suggested to find replacement parts
5540 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
5541 might present a language barrier as I do not understand French.&lt;/p&gt;
5542
5543 &lt;p&gt;One tip I got was to use the
5544 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
5545 compare laptop models. It seem to have more models available than
5546 prisjakt.no. Another tip I got from someone I know have similar
5547 keyboard preferences was that the HP EliteBook 840 keyboard is not
5548 very good, and this matches my experience with earlier EliteBook
5549 keyboards I tested. Because of this, I will not consider it any further.
5550
5551 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
5552 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5553 (which is missing from the X240), and is working fairly well with
5554 Debian Sid/Unstable according to
5555 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
5556 got on the keyboard quality are not consistent. Some say the keyboard
5557 is good, others say it is ok, while others say it is not very good.
5558 Those with experience from X41 and and X60 agree that the X250
5559 keyboard is not as good as those trusty old laptops, and suggest I
5560 keep and fix my X230 instead of upgrading, or get a used X230 to
5561 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
5562 activity and battery status, which is very convenient on my X230. I&#39;m
5563 also told that the CPU fan is running very often, making it a bit
5564 noisy. In any case, the X250 do not work out of the box with Debian
5565 Stable/Jessie, one of my requirements.&lt;/p&gt;
5566
5567 &lt;p&gt;I have also gotten a few vendor proposals, one was
5568 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
5569 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
5570 The latter look very attractive to me.&lt;/p&gt;
5571
5572 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
5573 as I keep looking for a replacement.&lt;/p&gt;
5574
5575 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
5576 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
5577 different
5578 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
5579 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
5580 </description>
5581 </item>
5582
5583 <item>
5584 <title>Time to find a new laptop, as the old one is broken after only two years</title>
5585 <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>
5586 <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>
5587 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
5588 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
5589 replacement soon. The left 5 cm of the screen on my Thinkpad X230
5590 started flickering yesterday, and I suspect the cause is a broken
5591 cable, as changing the angle of the screen some times get rid of the
5592 flickering.&lt;/p&gt;
5593
5594 &lt;p&gt;My requirements have not really changed since I bought it, and is
5595 still as
5596 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
5597 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
5598 good help from
5599 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
5600 where I could select at least a few of the requirements (mouse pin,
5601 wifi, weight) and go through the rest manually. Three button mouse
5602 and a good keyboard is not available as an option, and all the three
5603 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
5604 G2) lack three mouse buttons). It is also unclear to me how good the
5605 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5606 the keyboard, even if the quality and robustness in the X series have
5607 deteriorated since X41.&lt;/p&gt;
5608
5609 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
5610 seem sensible to me? Are there better services around to search the
5611 set of available laptops for features? Please send me an email if you
5612 have suggestions.&lt;/p&gt;
5613
5614 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
5615 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
5616 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
5617 </description>
5618 </item>
5619
5620 <item>
5621 <title>How to stay with sysvinit in Debian Jessie</title>
5622 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
5623 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
5624 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
5625 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
5626 sysvinit as its boot system by default. But how can one keep using
5627 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5628 courtesy of
5629 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
5630 Schubert&lt;/a&gt; and
5631 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
5632 McVittie&lt;/a&gt;.
5633
5634 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
5635 keep sysvinit as your boot system, create a file
5636 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
5637 you upgrade:&lt;/p&gt;
5638
5639 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5640 Package: systemd-sysv
5641 Pin: release o=Debian
5642 Pin-Priority: -1
5643 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5644
5645 &lt;p&gt;This file content will tell apt and aptitude to not consider
5646 installing systemd-sysv as part of any installation and upgrade
5647 solution when resolving dependencies, and thus tell it to avoid
5648 systemd as a default boot system. The end result should be that the
5649 upgraded system keep using sysvinit.&lt;/p&gt;
5650
5651 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
5652 get sysvinit installed by default (debootstrap used by
5653 debian-installer have no option for this), but one can tell the
5654 installer to switch to sysvinit before the first boot. Either by
5655 using a kernel argument to the installer, or by adding a line to the
5656 preseed file used. First, the kernel command line argument:
5657
5658 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5659 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
5660 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5661
5662 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
5663
5664 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5665 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5666 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5667
5668 &lt;p&gt;One can of course also do this after the first boot by installing
5669 the sysvinit-core package.&lt;/p&gt;
5670
5671 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
5672 sysvinit boot sequence in Debian have several hardware specific bugs
5673 on Linux caused by the fact that it is unpredictable when hardware
5674 devices show up during boot. But on the other hand, the new default
5675 boot system still have a few rough edges I hope will be fixed before
5676 Jessie is released.&lt;/p&gt;
5677
5678 &lt;p&gt;Update 2014-11-26: Inspired by
5679 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5680 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5681 line.&lt;/p&gt;
5682 </description>
5683 </item>
5684
5685 <item>
5686 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5687 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5688 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5689 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5690 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5691 without anyone snooping, is a right every citicen have in a liberal
5692 democracy. But this right is under serious attack these days.&lt;/p&gt;
5693
5694 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5695 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5696 the whisleblower Snowden) more expensive for Internet email,
5697 is to deliver all email using SMTP via Tor. Such SMTP option would be
5698 a nice addition to the FreedomBox project if we could send email
5699 between FreedomBox machines without leaking metadata about the emails
5700 to the people peeking on the wire. I
5701 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5702 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5703 lot of useful feedback and suggestions. It also became obvious to me
5704 that this was not a novel idea, as the same idea was tested and
5705 documented by Johannes Berg as early as 2006, and both
5706 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5707 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5708 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5709
5710 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5711 providing the SMTP protocol on port 25, and use email addresses
5712 looking like username@hidden-service-name.onion. With such addresses
5713 the connections to port 25 on hidden-service-name.onion using Tor will
5714 go to the correct SMTP server. To do this, one need to configure the
5715 Tor daemon to provide the hidden service and the mail server to accept
5716 emails for this .onion domain. To learn more about Exim configuration
5717 in Debian and test the design provided by Johannes Berg in his FAQ, I
5718 set out yesterday to create a Debian package for making it trivial to
5719 set up such SMTP over Tor service based on Debian. Getting it to work
5720 were fairly easy, and
5721 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5722 source code for the Debian package&lt;/a&gt; is available from github. I
5723 plan to move it into Debian if further testing prove this to be a
5724 useful approach.&lt;/p&gt;
5725
5726 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5727 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5728 get rid of exim4). Install tor, clone the git repository mentioned
5729 above, build the deb and install it on the machine. Next, run
5730 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5731 the instructions to get the service up and running. Restart tor and
5732 exim when it is done, and test mail delivery using swaks like
5733 this:&lt;/p&gt;
5734
5735 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5736 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5737 --to fbx@dutlqrrmjhtfa3vp.onion
5738 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5739
5740 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5741 address with your own address to test your server. :)&lt;/p&gt;
5742
5743 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5744 easier and more automatic. Especially the tor setup need more work.
5745 Also, the package include a tor-smtp tool written in C, but its task
5746 should probably be rewritten in some script language to make the deb
5747 architecture independent. It would probably also make the code easier
5748 to review. The tor-smtp tool currently need to listen on a socket for
5749 exim to talk to it and is started using xinetd. It would be better if
5750 no daemon and no socket is needed. I suspect it is possible to get
5751 exim to run a command line tool for delivery instead of talking to a
5752 socket, and hope to figure out how in a future version of this
5753 system.&lt;/p&gt;
5754
5755 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5756 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5757 SMTorP. :)&lt;/p&gt;
5758 </description>
5759 </item>
5760
5761 <item>
5762 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5763 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5764 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5765 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5766 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5767 alioth.debian.org, you know the web interface is fairly slow to
5768 operate. First you visit one web page, enter the moderation password
5769 and get a new page shown with a list of all the messages to moderate
5770 and various options for each email address. This take a while for
5771 every list you moderate, and you need to do it regularly to do a good
5772 job as a list moderator. But there is a quick alternative,
5773 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5774 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5775 to moderate in a fraction of a second. Here is a test run on two
5776 lists I recently took over:&lt;/p&gt;
5777
5778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5779 % time listadmin xiph
5780 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5781 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5782
5783 real 0m1.709s
5784 user 0m0.232s
5785 sys 0m0.012s
5786 %
5787 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5788
5789 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5790 there are no message in the moderation queue. Every morning I
5791 currently moderate 68 mailman lists, and it normally take around two
5792 minutes. When I took over the two pkg-xiph lists above a few days
5793 ago, there were 400 emails waiting in the moderator queue. It took me
5794 less than 15 minutes to process them all using the listadmin
5795 program.&lt;/p&gt;
5796
5797 &lt;p&gt;If you install
5798 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
5799 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
5800 with content like this, the moderation task is a breeze:&lt;/p&gt;
5801
5802 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5803 username username@example.org
5804 spamlevel 23
5805 default discard
5806 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
5807
5808 password secret
5809 adminurl https://{domain}/mailman/admindb/{list}
5810 mailman-list@lists.example.com
5811
5812 password hidden
5813 other-list@otherserver.example.org
5814 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5815
5816 &lt;p&gt;There are other options to set as well. Check the manual page to
5817 learn the details.&lt;/p&gt;
5818
5819 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
5820 the SSL certificate is self signed or not properly signed by a
5821 generally accepted signing authority, you can set a environment
5822 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
5823
5824 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5825 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
5826 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5827
5828 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
5829 can provide an argument to the listadmin script like I do in the
5830 initial screen dump (the xiph argument). Using an argument, only
5831 lists matching the argument string will be processed. This make it
5832 quick to accept messages if you notice the moderation request in your
5833 email.&lt;/p&gt;
5834
5835 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
5836 mailing lists, as I simply do not have time to spend on that if the
5837 process was any slower. The listadmin program have saved me hours of
5838 time I could spend elsewhere over the years. It truly is nice free
5839 software.&lt;/p&gt;
5840
5841 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5842 activities, please send Bitcoin donations to my address
5843 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5844
5845 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
5846 configuration example. Also, I&#39;ve been told that the
5847 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
5848 sure why.&lt;/p&gt;
5849 </description>
5850 </item>
5851
5852 <item>
5853 <title>Debian Jessie, PXE and automatic firmware installation</title>
5854 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
5855 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
5856 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
5857 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
5858 problem that the WiFi card require some firmware to work properly.
5859 And it has been a pain to fix this using preseeding in Debian.
5860 Normally something more is needed. But thanks to
5861 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
5862 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
5863 to do this using simple preseeding.&lt;/p&gt;
5864
5865 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
5866 firmware for the hardware found in the machine (actually, requested by
5867 the kernel modules for the hardware). (It can also install user space
5868 programs supporting the hardware detected, but that is not the focus
5869 of this story.)&lt;/p&gt;
5870
5871 &lt;p&gt;To get this working in the default installation, two preeseding
5872 values are needed. First, the isenkram-cli package must be installed
5873 into the target chroot (aka the hard drive) before tasksel is executed
5874 in the pkgsel step of the debian-installer system. This is done by
5875 preseeding the base-installer/includes debconf value to include the
5876 isenkram-cli package. The package name is next passed to debootstrap
5877 for installation. With the isenkram-cli package in place, tasksel
5878 will automatically use the isenkram tasks to detect hardware specific
5879 packages for the machine being installed and install them, because
5880 isenkram-cli contain tasksel tasks.&lt;/p&gt;
5881
5882 &lt;p&gt;Second, one need to enable the non-free APT repository, because
5883 most firmware unfortunately is non-free. This is done by preseeding
5884 the apt-mirror-setup step. This is unfortunate, but for a lot of
5885 hardware it is the only option in Debian.&lt;/p&gt;
5886
5887 &lt;p&gt;The end result is two lines needed in your preseeding file to get
5888 firmware installed automatically by the installer:&lt;/p&gt;
5889
5890 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5891 base-installer base-installer/includes string isenkram-cli
5892 apt-mirror-setup apt-setup/non-free boolean true
5893 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5894
5895 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
5896 both firmware and user space packages when using this method. It also
5897 do not work well, so use version 0.15 or later. Installing both
5898 firmware and user space packages might give you a bit more than you
5899 want, so I decided to split the tasksel task in two, one for firmware
5900 and one for user space programs. The firmware task is enabled by
5901 default, while the one for user space programs is not. This split is
5902 implemented in the package currently in unstable.&lt;/p&gt;
5903
5904 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
5905 this recipe work for you. :)&lt;/p&gt;
5906
5907 &lt;p&gt;So, I bet you are wondering, how can this work. First and
5908 foremost, it work because tasksel is modular, and driven by whatever
5909 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5910 isenkram-cli package place two files for tasksel to find. First there
5911 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
5912
5913 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5914 Task: isenkram-packages
5915 Section: hardware
5916 Description: Hardware specific packages (autodetected by isenkram)
5917 Based on the detected hardware various hardware specific packages are
5918 proposed.
5919 Test-new-install: show show
5920 Relevance: 8
5921 Packages: for-current-hardware
5922
5923 Task: isenkram-firmware
5924 Section: hardware
5925 Description: Hardware specific firmware packages (autodetected by isenkram)
5926 Based on the detected hardware various hardware specific firmware
5927 packages are proposed.
5928 Test-new-install: mark show
5929 Relevance: 8
5930 Packages: for-current-hardware-firmware
5931 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5932
5933 &lt;p&gt;The key parts are Test-new-install which indicate how the task
5934 should be handled and the Packages line referencing to a script in
5935 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5936 list of packages to install. The for-current-hardware-firmware script
5937 look like this to list relevant firmware for the machine:
5938
5939 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5940 #!/bin/sh
5941 #
5942 PATH=/usr/sbin:$PATH
5943 export PATH
5944 isenkram-autoinstall-firmware -l
5945 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5946
5947 &lt;p&gt;With those two pieces in place, the firmware is installed by
5948 tasksel during the normal d-i run. :)&lt;/p&gt;
5949
5950 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
5951 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
5952 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
5953 install.&lt;/p&gt;
5954
5955 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
5956 pilots in testing this feature, as isenkram is used there now to
5957 install firmware, replacing the earlier scripts.&lt;/p&gt;
5958 </description>
5959 </item>
5960
5961 <item>
5962 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
5963 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
5964 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
5965 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
5966 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
5967 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5968 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
5969 on a screen normally showing the bread types and prizes:&lt;/p&gt;
5970
5971 &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;
5972
5973 &lt;p&gt;If it had booted as it was supposed to, I would never had known
5974 about this hidden Linux installation. It is interesting what
5975 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
5976 </description>
5977 </item>
5978
5979 <item>
5980 <title>New lsdvd release version 0.17 is ready</title>
5981 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
5982 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
5983 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
5984 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
5985 got a new set of developers a few weeks ago, after the original
5986 developer decided to step down and pass the project to fresh blood.
5987 This project is now maintained by Petter Reinholdtsen and Steve
5988 Dibb.&lt;/p&gt;
5989
5990 &lt;p&gt;I just wrapped up
5991 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
5992 new lsdvd release&lt;/a&gt;, available in git or from
5993 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
5994 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
5995 0.17.&lt;/p&gt;
5996
5997 &lt;ul&gt;
5998
5999 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
6000 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
6001 non-existant, to work around additional copy protection&lt;/li&gt;
6002 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
6003 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
6004 &lt;li&gt;Fix include orders&lt;/li&gt;
6005 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
6006 &lt;li&gt;Fix the chapter count&lt;/li&gt;
6007 &lt;li&gt;Make sure the array size and the array limit used when initialising
6008 the palette size is the same.&lt;/li&gt;
6009 &lt;li&gt;Fix array printing.&lt;/li&gt;
6010 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
6011 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
6012 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
6013 with more GCC compiler warnings.&lt;/li&gt;
6014
6015 &lt;/ul&gt;
6016
6017 &lt;p&gt;This change bring together patches for lsdvd in use in various
6018 Linux and Unix distributions, as well as patches submitted to the
6019 project the last nine years. Please check it out. :)&lt;/p&gt;
6020 </description>
6021 </item>
6022
6023 <item>
6024 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
6025 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
6026 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
6027 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
6028 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6029 project&lt;/a&gt; provide a Linux solution for schools, including a
6030 powerful desktop with education software, a central server providing
6031 web pages, user database, user home directories, central login and PXE
6032 boot of both clients without disk and the installation to install Debian
6033 Edu on machines with disk (and a few other services perhaps to small
6034 to mention here). We in the Debian Edu team are currently working on
6035 the Jessie based version, trying to get everything in shape before the
6036 freeze, to avoid having to maintain our own package repository in the
6037 future. The
6038 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
6039 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
6040 work left. Some fatal problems block testing, breaking the installer,
6041 but it is possible to work around these to get anyway. Here is a
6042 recipe on how to get the installation limping along.&lt;/p&gt;
6043
6044 &lt;p&gt;First, download the test ISO via
6045 &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;,
6046 &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;
6047 or rsync (use
6048 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
6049 The ISO build was broken on Tuesday, so we do not get a new ISO every
6050 12 hours or so, but thankfully the ISO we already got we are able to
6051 install with some tweaking.&lt;/p&gt;
6052
6053 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
6054 (use Alt-Ctrl-F2), run&lt;/p&gt;
6055
6056 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6057 nano /usr/bin/edu-eatmydata-install
6058 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6059
6060 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
6061 optimization. Return to the installation, select the profile you want
6062 and continue. Without this change, exim4-config will fail to install
6063 due to a known bug in eatmydata.&lt;/p&gt;
6064
6065 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
6066 this do not work, figure out what your correct value would be. All my
6067 test machines need /dev/sda, so I have no advice if it do not fit
6068 your need.&lt;/p&gt;
6069
6070 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
6071 root after the initial boot from hard drive, and install the
6072 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
6073 or mate. If you want several desktop options, install more than one
6074 metapackage. Once this is done, reboot and you should have a working
6075 graphical login screen. This workaround should no longer be needed
6076 once the education-tasks package version 1.801 enter testing in two
6077 days.&lt;/p&gt;
6078
6079 &lt;p&gt;I believe the ISO build will start working on two days when the new
6080 tasksel package enter testing and Steve McIntyre get a chance to
6081 update the debian-cd git repository. The eatmydata, grub and desktop
6082 issues are already fixed in unstable and testing, and should show up
6083 on the ISO as soon as the ISO build start working again. Well the
6084 eatmydata optimization is really just disabled. The proper fix
6085 require an upload by the eatmydata maintainer applying the patch
6086 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
6087 The rest have proper fixes in unstable.&lt;/p&gt;
6088
6089 &lt;p&gt;I hope this get you going with the installation testing, as we are
6090 quickly running out of time trying to get our Jessie based
6091 installation ready before the distribution freeze in a month.&lt;/p&gt;
6092 </description>
6093 </item>
6094
6095 <item>
6096 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
6097 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
6098 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
6099 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
6100 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
6101 to handle my fairly large DVD collection. It is a nice command line
6102 tool to get details about a DVD, like title, tracks, track length,
6103 etc, in XML, Perl or human readable format. But lsdvd have not seen
6104 any new development since 2006 and had a few irritating bugs affecting
6105 its use with some DVDs. Upstream seemed to be dead, and in January I
6106 sent a small probe asking for a version control repository for the
6107 project, without any reply. But I use it regularly and would like to
6108 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
6109 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
6110 the project admin, and after getting a reply from him explaining that
6111 he was no longer interested in the project, I asked if I could take
6112 over. And yesterday, I became project admin.&lt;/p&gt;
6113
6114 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
6115 maintainer interested in joining forces to maintain the upstream
6116 project, and I hope we can get a new release out fairly quickly,
6117 collecting the patches spread around on the internet into on place.
6118 I&#39;ve added the relevant Debian patches to the freshly created git
6119 repository, and expect the Gentoo patches to make it too. If you got
6120 a DVD collection and care about command line tools, check out
6121 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
6122 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
6123 list&lt;/a&gt;. :)&lt;/p&gt;
6124 </description>
6125 </item>
6126
6127 <item>
6128 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
6129 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
6130 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
6131 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
6132 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
6133 a lot quicker. When we install more than 2000 packages in
6134 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
6135 tasksel in the installer, unpacking the binary packages take forever.
6136 A part of the slow I/O issue was discussed in
6137 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
6138 much file system sync-ing done by dpkg, which is the package
6139 responsible for unpacking the binary packages. Other parts (like code
6140 executed by postinst scripts) might also sync to disk during
6141 installation. All this sync-ing to disk do not really make sense to
6142 me. If the machine crash half-way through, I start over, I do not try
6143 to salvage the half installed system. So the failure sync-ing is
6144 supposed to protect against, hardware or system crash, is not really
6145 relevant while the installer is running.&lt;/p&gt;
6146
6147 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
6148 system sync()-ing in a fairly non-intrusive way, without the need to
6149 change the code in several packages. The idea is not new, but I have
6150 not heard anyone propose the approach using dpkg-divert before. It
6151 depend on the small and clever package
6152 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
6153 uses LD_PRELOAD to replace the system functions for syncing data to
6154 disk with functions doing nothing, thus allowing programs to live
6155 dangerous while speeding up disk I/O significantly. Instead of
6156 modifying the implementation of dpkg, apt and tasksel (which are the
6157 packages responsible for selecting, fetching and installing packages),
6158 it occurred to me that we could just divert the programs away, replace
6159 them with a simple shell wrapper calling
6160 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
6161 Two days ago I decided to test the idea, and wrapped up a simple
6162 implementation for the Debian Edu udeb.&lt;/p&gt;
6163
6164 &lt;p&gt;The effect was stunning. In my first test it reduced the running
6165 time of the pkgsel step (installing tasks) from 64 to less than 44
6166 minutes (20 minutes shaved off the installation) on an old Dell
6167 Latitude D505 machine. I am not quite sure what the optimised time
6168 would have been, as I messed up the testing a bit, causing the debconf
6169 priority to get low enough for two questions to pop up during
6170 installation. As soon as I saw the questions I moved the installation
6171 along, but do not know how long the question were holding up the
6172 installation. I did some more measurements using Debian Edu Jessie,
6173 and got these results. The time measured is the time stamp in
6174 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
6175 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
6176 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6177 timing thus do not depend on how quickly the user handle the tasksel
6178 dialog.&lt;/p&gt;
6179
6180 &lt;p&gt;&lt;table&gt;
6181
6182 &lt;tr&gt;
6183 &lt;th&gt;Machine/setup&lt;/th&gt;
6184 &lt;th&gt;Original tasksel&lt;/th&gt;
6185 &lt;th&gt;Optimised tasksel&lt;/th&gt;
6186 &lt;th&gt;Reduction&lt;/th&gt;
6187 &lt;/tr&gt;
6188
6189 &lt;tr&gt;
6190 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
6191 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
6192 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
6193 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
6194 &lt;/tr&gt;
6195
6196 &lt;tr&gt;
6197 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
6198 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
6199 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
6200 &lt;td&gt;23 min 40%&lt;/td&gt;
6201 &lt;/tr&gt;
6202
6203 &lt;tr&gt;
6204 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
6205 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
6206 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
6207 &lt;td&gt;11 min 50%&lt;/td&gt;
6208 &lt;/tr&gt;
6209
6210 &lt;tr&gt;
6211 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
6212 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
6213 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
6214 &lt;td&gt;2 min 33%&lt;/td&gt;
6215 &lt;/tr&gt;
6216
6217 &lt;tr&gt;
6218 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
6219 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
6220 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
6221 &lt;td&gt;4 min 21%&lt;/td&gt;
6222 &lt;/tr&gt;
6223
6224 &lt;/table&gt;&lt;/p&gt;
6225
6226 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
6227 time is spent downloading packages. The connection to the Internet
6228 was 100Mbit/s during testing, so downloading should not be a
6229 significant factor in the measurement. Download typically took a few
6230 seconds to a few minutes, depending on the amount of packages being
6231 installed.&lt;/p&gt;
6232
6233 &lt;p&gt;The speedup is implemented by using two hooks in
6234 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
6235 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
6236 finish-install.d hook to remove the divert at the end of the
6237 installation. I picked the pre-pkgsel.d hook instead of the
6238 post-base-installer.d hook because I test using an ISO without the
6239 eatmydata package included, and the post-base-installer.d hook in
6240 Debian Edu can only operate on packages included in the ISO. The
6241 negative effect of this is that I am unable to activate this
6242 optimization for the kernel installation step in d-i. If the code is
6243 moved to the post-base-installer.d hook, the speedup would be larger
6244 for the entire installation.&lt;/p&gt;
6245
6246 &lt;p&gt;I&#39;ve implemented this in the
6247 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
6248 git repository, and plan to provide the optimization as part of the
6249 Debian Edu installation. If you want to test this yourself, you can
6250 create two files in the installer (or in an udeb). One shell script
6251 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
6252
6253 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6254 #!/bin/sh
6255 set -e
6256 . /usr/share/debconf/confmodule
6257 info() {
6258 logger -t my-pkgsel &quot;info: $*&quot;
6259 }
6260 error() {
6261 logger -t my-pkgsel &quot;error: $*&quot;
6262 }
6263 override_install() {
6264 apt-install eatmydata || true
6265 if [ -x /target/usr/bin/eatmydata ] ; then
6266 for bin in dpkg apt-get aptitude tasksel ; do
6267 file=/usr/bin/$bin
6268 # Test that the file exist and have not been diverted already.
6269 if [ -f /target$file ] ; then
6270 info &quot;diverting $file using eatmydata&quot;
6271 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
6272 &gt; /target$file.edu
6273 chmod 755 /target$file.edu
6274 in-target dpkg-divert --package debian-edu-config \
6275 --rename --quiet --add $file
6276 ln -sf ./$bin.edu /target$file
6277 else
6278 error &quot;unable to divert $file, as it is missing.&quot;
6279 fi
6280 done
6281 else
6282 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
6283 fi
6284 }
6285
6286 override_install
6287 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6288
6289 &lt;p&gt;To clean up, another shell script should go into
6290 /usr/lib/finish-install.d/ with code like this:
6291
6292 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6293 #! /bin/sh -e
6294 . /usr/share/debconf/confmodule
6295 error() {
6296 logger -t my-finish-install &quot;error: $@&quot;
6297 }
6298 remove_install_override() {
6299 for bin in dpkg apt-get aptitude tasksel ; do
6300 file=/usr/bin/$bin
6301 if [ -x /target$file.edu ] ; then
6302 rm /target$file
6303 in-target dpkg-divert --package debian-edu-config \
6304 --rename --quiet --remove $file
6305 rm /target$file.edu
6306 else
6307 error &quot;Missing divert for $file.&quot;
6308 fi
6309 done
6310 sync # Flush file buffers before continuing
6311 }
6312
6313 remove_install_override
6314 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6315
6316 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
6317 edu-eatmydata-install and call it from the pre-pkgsel.d and
6318 finish-install.d scripts.&lt;/p&gt;
6319
6320 &lt;p&gt;By now you might ask if this change should get into the normal
6321 Debian installer too? I suspect it should, but am not sure the
6322 current debian-installer coordinators find it useful enough. It also
6323 depend on the side effects of the change. I&#39;m not aware of any, but I
6324 guess we will see if the change is safe after some more testing.
6325 Perhaps there is some package in Debian depending on sync() and
6326 fsync() having effect? Perhaps it should go into its own udeb, to
6327 allow those of us wanting to enable it to do so without affecting
6328 everyone.&lt;/p&gt;
6329
6330 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
6331 will break installation of all programs using gnutls because of
6332 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
6333 eatmydata package in Debian will solve it.&lt;/p&gt;
6334
6335 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
6336 the optimization work again. And I have discovered that the
6337 dpkg-divert trick is not really needed and implemented a slightly
6338 simpler approach as part of the debian-edu-install package. See
6339 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
6340
6341 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
6342 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
6343 triggering on i386 made it into testing, and broke this installation
6344 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
6345 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
6346 </description>
6347 </item>
6348
6349 <item>
6350 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
6351 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
6352 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
6353 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
6354 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
6355 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
6356 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
6357 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
6358 learn that there is a large set of publicly available key servers to
6359 use when looking for peoples public key. So far I have used
6360 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6361 were misbehaving, but those days are ended. The servers I have used
6362 up until yesterday have been slow and some times unavailable. I hope
6363 those problems are gone now.&lt;/p&gt;
6364
6365 &lt;p&gt;Behind the round robin DNS entry of the
6366 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
6367 there is a pool of more than 100 keyservers which are checked every
6368 day to ensure they are well connected and up to date. It must be
6369 better than what I have used so far. :)&lt;/p&gt;
6370
6371 &lt;p&gt;Yesterdays speaker told me that the service is the default
6372 keyserver provided by the default configuration in GnuPG, but this do
6373 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
6374
6375 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
6376 line:&lt;/p&gt;
6377
6378 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6379 keyserver pool.sks-keyservers.net
6380 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6381
6382 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
6383 entries in DNS. Just for fun, I did just that at work, so now every
6384 user of GnuPG at the University of Oslo should find a OpenGPG
6385 keyserver automatically should their need it:&lt;/p&gt;
6386
6387 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6388 % host -t srv _pgpkey-http._tcp.uio.no
6389 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
6390 %
6391 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6392
6393 &lt;p&gt;Now if only
6394 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
6395 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
6396 very happy. It can look up a given key or search for a user ID, but I
6397 normally do not want that, but to find a trust path from my key to
6398 another key. Given a user ID or key ID, I would like to find (and
6399 download) the keys representing a signature path from my key to the
6400 key in question, to be able to get a trust path between the two keys.
6401 This is as far as I can tell not possible today. Perhaps something
6402 for a future version of the protocol?&lt;/p&gt;
6403 </description>
6404 </item>
6405
6406 <item>
6407 <title>From English wiki to translated PDF and epub via Docbook</title>
6408 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
6409 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
6410 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
6411 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6412 project&lt;/a&gt; provide an instruction manual for teachers, system
6413 administrators and other users that contain useful tips for setting up
6414 and maintaining a Debian Edu installation. This text is about how the
6415 text processing of this manual is handled in the project.&lt;/p&gt;
6416
6417 &lt;p&gt;One goal of the project is to provide information in the native
6418 language of its users, and for this we need to handle translations.
6419 But we also want to make sure each language contain the same
6420 information, so for this we need a good way to keep the translations
6421 in sync. And we want it to be easy for our users to improve the
6422 documentation, avoiding the need to learn special formats or tools to
6423 contribute, and the obvious way to do this is to make it possible to
6424 edit the documentation using a web browser. We also want it to be
6425 easy for translators to keep the translation up to date, and give them
6426 help in figuring out what need to be translated. Here is the list of
6427 tools and the process we have found trying to reach all these
6428 goals.&lt;/p&gt;
6429
6430 &lt;p&gt;We maintain the authoritative source of our manual in the
6431 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
6432 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
6433 front page with references to the different chapters, several pages
6434 for each chapter, and finally one &quot;collection page&quot; gluing all the
6435 chapters together into one large web page (aka
6436 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
6437 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
6438 processing and translations. Thanks to the fact that the
6439 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
6440 wiki.debian.org support exporting pages in
6441 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
6442 the list of pages to export using the raw version of the AllInOne
6443 page, loop over each of them to generate a Docbook XML version of the
6444 manual. This process also download images and transform image
6445 references to use the locally downloaded images. The generated
6446 Docbook XML files are slightly broken, so some post-processing is done
6447 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
6448 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6449 a handfull of images. The XML file can now be used to generate PDF, HTML
6450 and epub versions of the English manual. This is the basic step of
6451 our process, making PDF (using dblatex), HTML (using xsltproc) and
6452 epub (using dbtoepub) version from Docbook XML, and the resulting files
6453 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
6454
6455 &lt;p&gt;But English documentation is not enough for us. We want translated
6456 documentation too, and we want to make it easy for translators to
6457 track the English original. For this we use the
6458 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
6459 which allow us to transform the English Docbook XML file into a
6460 translation file (a .pot file), usable with the normal gettext based
6461 translation tools used by those translating free software. The pot
6462 file is used to create and maintain translation files (several .po
6463 files), which the translations update with the native language
6464 translations of all titles, paragraphs and blocks of text in the
6465 original. The next step is combining the original English Docbook XML
6466 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6467 create a translated Docbook XML file (in this case
6468 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6469 translated, if the translation is not complete) Docbook XML file can
6470 then be used like the original to create a PDF, HTML and epub version
6471 of the documentation.&lt;/p&gt;
6472
6473 &lt;p&gt;The translators use different tools to edit the .po files. We
6474 recommend using
6475 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
6476 while some use emacs and vi, others can use web based editors like
6477 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
6478 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
6479 is where the .po file end up, in our git repository. Updated
6480 translations can either be committed directly to git, or submitted as
6481 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
6482 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
6483
6484 &lt;p&gt;One challenge is images, which both might need to be translated (if
6485 they show translated user applications), and are needed in different
6486 formats when creating PDF and HTML versions (epub is a HTML version in
6487 this regard). For this we transform the original PNG images to the
6488 needed density and format during build, and have a way to provide
6489 translated images by storing translated versions in
6490 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6491 package maintainers know more.&lt;/p&gt;
6492
6493 &lt;p&gt;If you wonder what the result look like, we provide
6494 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
6495 of the documentation packages on the web&lt;/a&gt;. See for example the
6496 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
6497 PDF version&lt;/a&gt; or the
6498 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
6499 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
6500 but perhaps it will be done in the future.&lt;/p&gt;
6501
6502 &lt;p&gt;To learn more, check out
6503 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
6504 debian-edu-doc package&lt;/a&gt;,
6505 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
6506 manual on the wiki&lt;/a&gt; and
6507 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
6508 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
6509 </description>
6510 </item>
6511
6512 <item>
6513 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
6514 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
6515 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
6516 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
6517 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
6518 related packages relevant for the computer installed automatically.
6519 So I implemented one, using
6520 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
6521 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
6522 run tasksel as user root. You should be presented with a new option,
6523 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
6524 select it, tasksel will install the packages isenkram claim is fit for
6525 the current hardware, hot pluggable or not.&lt;p&gt;
6526
6527 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
6528 description, and the other is the script used to extract the list of
6529 packages to install. The first part is in
6530 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
6531 this:&lt;/p&gt;
6532
6533 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6534 Task: isenkram
6535 Section: hardware
6536 Description: Hardware specific packages (autodetected by isenkram)
6537 Based on the detected hardware various hardware specific packages are
6538 proposed.
6539 Test-new-install: mark show
6540 Relevance: 8
6541 Packages: for-current-hardware
6542 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6543
6544 &lt;p&gt;The second part is in
6545 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
6546 this:&lt;/p&gt;
6547
6548 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6549 #!/bin/sh
6550 #
6551 (
6552 isenkram-lookup
6553 isenkram-autoinstall-firmware -l
6554 ) | sort -u
6555 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6556
6557 &lt;p&gt;All in all, a very short and simple implementation making it
6558 trivial to install the hardware dependent package we all may want to
6559 have installed on our machines. I&#39;ve not been able to find a way to
6560 get tasksel to tell you exactly which packages it plan to install
6561 before doing the installation. So if you are curious or careful,
6562 check the output from the isenkram-* command line tools first.&lt;/p&gt;
6563
6564 &lt;p&gt;The information about which packages are handling which hardware is
6565 fetched either from the isenkram package itself in
6566 /usr/share/isenkram/, from git.debian.org or from the APT package
6567 database (using the Modaliases header). The APT package database
6568 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6569 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
6570 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
6571 the python-apt code (bug
6572 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
6573 workaround I was able to get rid of the file descriptor leak and
6574 reduce the memory leak from ~30 MiB per hardware detection down to
6575 around 2 MiB per hardware detection. It should make the desktop
6576 daemon a lot more useful. The fix is in version 0.7 uploaded to
6577 unstable today.&lt;/p&gt;
6578
6579 &lt;p&gt;I believe the current way of mapping hardware to packages in
6580 Isenkram is is a good draft, but in the future I expect isenkram to
6581 use the AppStream data source for this. A proposal for getting proper
6582 AppStream support into Debian is floating around as
6583 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
6584 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
6585 project&lt;/a&gt; will take place this summer to improve the situation. I
6586 look forward to seeing the result, and welcome patches for isenkram to
6587 start using the information when it is ready.&lt;/p&gt;
6588
6589 &lt;p&gt;If you want your package to map to some specific hardware, either
6590 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
6591 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
6592 package&lt;/a&gt; or submit a bug report with the details to the isenkram
6593 package. See also
6594 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
6595 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
6596 the information will be migrated to AppStream eventually, but for the
6597 moment I got no better place to store it.&lt;/p&gt;
6598 </description>
6599 </item>
6600
6601 <item>
6602 <title>FreedomBox milestone - all packages now in Debian Sid</title>
6603 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
6604 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
6605 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
6606 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6607 project&lt;/a&gt; is working on providing the software and hardware to make
6608 it easy for non-technical people to host their data and communication
6609 at home, and being able to communicate with their friends and family
6610 encrypted and away from prying eyes. It is still going strong, and
6611 today a major mile stone was reached.&lt;/p&gt;
6612
6613 &lt;p&gt;Today, the last of the packages currently used by the project to
6614 created the system images were accepted into Debian Unstable. It was
6615 the freedombox-setup package, which is used to configure the images
6616 during build and on the first boot. Now all one need to get going is
6617 the build code from the freedom-maker git repository and packages from
6618 Debian. And once the freedombox-setup package enter testing, we can
6619 build everything directly from Debian. :)&lt;/p&gt;
6620
6621 &lt;p&gt;Some key packages used by Freedombox are
6622 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
6623 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
6624 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
6625 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
6626 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
6627 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
6628 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
6629 are plans to integrate more packages into the setup. User
6630 documentation is maintained on the Debian wiki. Please
6631 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
6632 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
6633
6634 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
6635 setup, run this on a Debian machine using a user with sudo rights to
6636 become root:&lt;/p&gt;
6637
6638 &lt;p&gt;&lt;pre&gt;
6639 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6640 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6641 u-boot-tools
6642 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6643 freedom-maker
6644 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6645 &lt;/pre&gt;&lt;/p&gt;
6646
6647 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6648 devices. See the README in the freedom-maker git repo for more
6649 details on the build. If you do not want all three images, trim the
6650 make line. Note that the virtualbox-image target is not really
6651 virtualbox specific. It create a x86 image usable in kvm, qemu,
6652 vmware and any other x86 virtual machine environment. You might need
6653 the version of vmdebootstrap in Jessie to get the build working, as it
6654 include fixes for a race condition with kpartx.&lt;/p&gt;
6655
6656 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6657 method, boot a Debian Wheezy ISO and use this boot argument to load
6658 the preseed values:&lt;/p&gt;
6659
6660 &lt;p&gt;&lt;pre&gt;
6661 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;
6662 &lt;/pre&gt;&lt;/p&gt;
6663
6664 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
6665 it still work.&lt;/p&gt;
6666
6667 &lt;p&gt;If you wonder how to help, one task you could look at is using
6668 systemd as the boot system. It will become the default for Linux in
6669 Jessie, so we need to make sure it is usable on the Freedombox. I did
6670 a simple test a few weeks ago, and noticed dnsmasq failed to start
6671 during boot when using systemd. I suspect there are other problems
6672 too. :) To detect problems, there is a test suite included, which can
6673 be run from the plinth web interface.&lt;/p&gt;
6674
6675 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6676 us get the new release published. :) Please join us on
6677 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6678 irc.debian.org)&lt;/a&gt; and
6679 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6680 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6681 </description>
6682 </item>
6683
6684 <item>
6685 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6686 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6687 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6688 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6689 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6690 solution for use at home. My requirements are simple, it must be
6691 cheap and locally encrypted (in other words, I keep the encryption
6692 keys, the storage provider do not have access to my private files).
6693 One idea me and my friends had many years ago, before the cloud
6694 storage providers showed up, was to use Google mail as storage,
6695 writing a Linux block device storing blocks as emails in the mail
6696 service provided by Google, and thus get heaps of free space. On top
6697 of this one can add encryption, RAID and volume management to have
6698 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6699 I never found time to implement such system. But the last few weeks I
6700 have looked at a system called
6701 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6702 mounted network backed file system with the features I need.&lt;/p&gt;
6703
6704 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6705 handling several different storage providers, any with Amazon S3,
6706 Google Drive or OpenStack API. There are heaps of such storage
6707 providers. S3QL can also use a local directory as storage, which
6708 combined with sshfs allow for file storage on any ssh server. S3QL
6709 include support for encryption, compression, de-duplication, snapshots
6710 and immutable file systems, allowing me to mount the remote storage as
6711 a local mount point, look at and use the files as if they were local,
6712 while the content is stored in the cloud as well. This allow me to
6713 have a backup that should survive fire. The file system can not be
6714 shared between several machines at the same time, as only one can
6715 mount it at the time, but any machine with the encryption key and
6716 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6717
6718 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6719 package is included already. So to get started, run &lt;tt&gt;apt-get
6720 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6721 Greenqloud, after reading their nice recipe on
6722 &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
6723 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6724 in Iceland more than those in USA when it come to keeping my personal
6725 data safe and private, and thus would rather spend money on a company
6726 in Iceland. Another nice recipe is available from the article
6727 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6728 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6729 Admin magazine. When the provider is picked, figure out how to get
6730 the API key needed to connect to the storage API. With Greencloud,
6731 the key did not show up until I had added payment details to my
6732 account.&lt;/p&gt;
6733
6734 &lt;p&gt;Armed with the API access details, it is time to create the file
6735 system. First, create a new bucket in the cloud. This bucket is the
6736 file system storage area. I picked a bucket name reflecting the
6737 machine that was going to store data there, but any name will do.
6738 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6739 the API login and password, and a locally created password. Store it
6740 all in ~root/.s3ql/authinfo2 like this:
6741
6742 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6743 [s3c]
6744 storage-url: s3c://s.greenqloud.com:443/bucket-name
6745 backend-login: API-login
6746 backend-password: API-password
6747 fs-passphrase: local-password
6748 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6749
6750 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6751 but any sensible way to create a fairly random password should do it.
6752 Armed with these details, it is now time to run mkfs, entering the API
6753 details and password to create it:&lt;/p&gt;
6754
6755 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6756 # mkdir -m 700 /var/lib/s3ql-cache
6757 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6758 --ssl s3c://s.greenqloud.com:443/bucket-name
6759 Enter backend login:
6760 Enter backend password:
6761 Before using S3QL, make sure to read the user&#39;s guide, especially
6762 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6763 Enter encryption password:
6764 Confirm encryption password:
6765 Generating random encryption key...
6766 Creating metadata tables...
6767 Dumping metadata...
6768 ..objects..
6769 ..blocks..
6770 ..inodes..
6771 ..inode_blocks..
6772 ..symlink_targets..
6773 ..names..
6774 ..contents..
6775 ..ext_attributes..
6776 Compressing and uploading metadata...
6777 Wrote 0.00 MB of compressed metadata.
6778 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6779
6780 &lt;p&gt;The next step is mounting the file system to make the storage available.
6781
6782 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6783 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6784 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6785 Using 4 upload threads.
6786 Downloading and decompressing metadata...
6787 Reading metadata...
6788 ..objects..
6789 ..blocks..
6790 ..inodes..
6791 ..inode_blocks..
6792 ..symlink_targets..
6793 ..names..
6794 ..contents..
6795 ..ext_attributes..
6796 Mounting filesystem...
6797 # df -h /s3ql
6798 Filesystem Size Used Avail Use% Mounted on
6799 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
6800 #
6801 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6802
6803 &lt;p&gt;The file system is now ready for use. I use rsync to store my
6804 backups in it, and as the metadata used by rsync is downloaded at
6805 mount time, no network traffic (and storage cost) is triggered by
6806 running rsync. To unmount, one should not use the normal umount
6807 command, as this will not flush the cache to the cloud storage, but
6808 instead running the umount.s3ql command like this:
6809
6810 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6811 # umount.s3ql /s3ql
6812 #
6813 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6814
6815 &lt;p&gt;There is a fsck command available to check the file system and
6816 correct any problems detected. This can be used if the local server
6817 crashes while the file system is mounted, to reset the &quot;already
6818 mounted&quot; flag. This is what it look like when processing a working
6819 file system:&lt;/p&gt;
6820
6821 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6822 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
6823 Using cached metadata.
6824 File system seems clean, checking anyway.
6825 Checking DB integrity...
6826 Creating temporary extra indices...
6827 Checking lost+found...
6828 Checking cached objects...
6829 Checking names (refcounts)...
6830 Checking contents (names)...
6831 Checking contents (inodes)...
6832 Checking contents (parent inodes)...
6833 Checking objects (reference counts)...
6834 Checking objects (backend)...
6835 ..processed 5000 objects so far..
6836 ..processed 10000 objects so far..
6837 ..processed 15000 objects so far..
6838 Checking objects (sizes)...
6839 Checking blocks (referenced objects)...
6840 Checking blocks (refcounts)...
6841 Checking inode-block mapping (blocks)...
6842 Checking inode-block mapping (inodes)...
6843 Checking inodes (refcounts)...
6844 Checking inodes (sizes)...
6845 Checking extended attributes (names)...
6846 Checking extended attributes (inodes)...
6847 Checking symlinks (inodes)...
6848 Checking directory reachability...
6849 Checking unix conventions...
6850 Checking referential integrity...
6851 Dropping temporary indices...
6852 Backing up old metadata...
6853 Dumping metadata...
6854 ..objects..
6855 ..blocks..
6856 ..inodes..
6857 ..inode_blocks..
6858 ..symlink_targets..
6859 ..names..
6860 ..contents..
6861 ..ext_attributes..
6862 Compressing and uploading metadata...
6863 Wrote 0.89 MB of compressed metadata.
6864 #
6865 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6866
6867 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
6868 quick, about the same speed as local file access. Uploading large
6869 amount of data is to me limited by the bandwidth out of and into my
6870 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
6871 which is very close to my upload speed, and downloading the same
6872 Debian installation ISO gave me 610 kiB/s, close to my download speed.
6873 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
6874 network, not the file system code. I do not know what a good cache
6875 size would be, but suspect that the cache should e larger than your
6876 working set.&lt;/p&gt;
6877
6878 &lt;p&gt;I mentioned that only one machine can mount the file system at the
6879 time. If another machine try, it is told that the file system is
6880 busy:&lt;/p&gt;
6881
6882 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6883 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6884 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6885 Using 8 upload threads.
6886 Backend reports that fs is still mounted elsewhere, aborting.
6887 #
6888 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6889
6890 &lt;p&gt;The file content is uploaded when the cache is full, while the
6891 metadata is uploaded once every 24 hour by default. To ensure the
6892 file system content is flushed to the cloud, one can either umount the
6893 file system, or ask S3QL to flush the cache and metadata using
6894 s3qlctrl:
6895
6896 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6897 # s3qlctrl upload-meta /s3ql
6898 # s3qlctrl flushcache /s3ql
6899 #
6900 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6901
6902 &lt;p&gt;If you are curious about how much space your data uses in the
6903 cloud, and how much compression and deduplication cut down on the
6904 storage usage, you can use s3qlstat on the mounted file system to get
6905 a report:&lt;/p&gt;
6906
6907 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6908 # s3qlstat /s3ql
6909 Directory entries: 9141
6910 Inodes: 9143
6911 Data blocks: 8851
6912 Total data size: 22049.38 MB
6913 After de-duplication: 21955.46 MB (99.57% of total)
6914 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
6915 Database size: 2.39 MB (uncompressed)
6916 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6917 #
6918 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6919
6920 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
6921 storage. I did not try to locate them all, but am aware of at least
6922 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
6923 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
6924 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
6925 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
6926 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
6927 accept payment in Bitcoin. Pick one that suit your need. Some of
6928 them provide several GiB of free storage, but the prize models are
6929 quite different and you will have to figure out what suits you
6930 best.&lt;/p&gt;
6931
6932 &lt;p&gt;While researching this blog post, I had a look at research papers
6933 and posters discussing the S3QL file system. There are several, which
6934 told me that the file system is getting a critical check by the
6935 science community and increased my confidence in using it. One nice
6936 poster is titled
6937 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
6938 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6939 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
6940 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6941 and Pamela Smith. Please have a look.&lt;/p&gt;
6942
6943 &lt;p&gt;Given my problems with different file systems earlier, I decided to
6944 check out the mounted S3QL file system to see if it would be usable as
6945 a home directory (in other word, that it provided POSIX semantics when
6946 it come to locking and umask handling etc). Running
6947 &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
6948 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
6949 no error was found. So the file system can be used for home
6950 directories, if one chooses to do so.&lt;/p&gt;
6951
6952 &lt;p&gt;If you do not want a locally file system, and want something that
6953 work without the Linux fuse file system, I would like to mention the
6954 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
6955 provide locally encrypted backup using a command line client. It have
6956 a nicer access control system, where one can split out read and write
6957 access, allowing some systems to write to the backup and others to
6958 only read from it.&lt;/p&gt;
6959
6960 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6961 activities, please send Bitcoin donations to my address
6962 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6963 </description>
6964 </item>
6965
6966 <item>
6967 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
6968 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
6969 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
6970 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
6971 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6972 project&lt;/a&gt; is working on providing the software and hardware for
6973 making it easy for non-technical people to host their data and
6974 communication at home, and being able to communicate with their
6975 friends and family encrypted and away from prying eyes. It has been
6976 going on for a while, and is slowly progressing towards a new test
6977 release (0.2).&lt;/p&gt;
6978
6979 &lt;p&gt;And what day could be better than the Pi day to announce that the
6980 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
6981 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6982 system), and can also be installed using a Debian installer preseed
6983 file. The Debian based Freedombox is now based on Debian Jessie,
6984 where most of the needed packages used are already present. Only one,
6985 the freedombox-setup package, is missing. To try to build your own
6986 boot image to test the current status, fetch the freedom-maker scripts
6987 and build using
6988 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
6989 with a user with sudo access to become root:
6990
6991 &lt;pre&gt;
6992 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6993 freedom-maker
6994 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6995 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6996 u-boot-tools
6997 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6998 &lt;/pre&gt;
6999
7000 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
7001 devices. See the README for more details on the build. If you do not
7002 want all three images, trim the make line. But note that thanks to &lt;a
7003 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
7004 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
7005 kpartx call.&lt;/p&gt;
7006
7007 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
7008 method, boot a Debian Wheezy ISO and use this boot argument to load
7009 the preseed values:&lt;/p&gt;
7010
7011 &lt;pre&gt;
7012 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;
7013 &lt;/pre&gt;
7014
7015 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
7016 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
7017 currently hang while setting up APT sources. Killing the
7018 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
7019 installation will get the installation going. This affect all
7020 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
7021
7022 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
7023 us get the new release published. :) Please join us on
7024 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
7025 irc.debian.org)&lt;/a&gt; and
7026 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7027 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7028 </description>
7029 </item>
7030
7031 <item>
7032 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
7033 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
7034 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
7035 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
7036 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
7037 innetgr tools, because I needed them in
7038 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
7039 ng-utils, and it has served me well. I placed the project under the
7040 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
7041 repository. But many years ago, the CVS repository was dropped (lost,
7042 not migrated to new hardware, not sure), and the project have lacked a
7043 proper home since then.&lt;/p&gt;
7044
7045 &lt;p&gt;Last summer, I had a look at the package and made a new release
7046 fixing a irritating crash bug, but was unable to store the changes in
7047 a proper source control system. I applied for a project on
7048 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
7049 to follow up on it. Until today. :)&lt;/p&gt;
7050
7051 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
7052 now have a new home, and a git repository with the highlight of the
7053 history of the project. I published all release tarballs and imported
7054 them into the git repository. As the project is really stable and not
7055 expected to gain new features any time soon, I decided to make a new
7056 release and call it 1.0. Visit the new project home on
7057 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
7058 if you want to check it out. The new version is also uploaded into
7059 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
7060 </description>
7061 </item>
7062
7063 <item>
7064 <title>Testing sysvinit from experimental in Debian Hurd</title>
7065 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
7066 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
7067 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
7068 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
7069 their changes into sysvinit, to allow them to use the normal sysvinit
7070 boot system instead of their old one. This follow up on the
7071 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
7072 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
7073 get Debian on Hurd working more like Debian on Linux. To get started,
7074 I downloaded a prebuilt hard disk image from
7075 &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;,
7076 and started it using virt-manager.&lt;/p&gt;
7077
7078 &lt;p&gt;The first think I had to do after logging in (root without any
7079 password) was to get the network operational. I followed
7080 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
7081 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
7082 commands as root to get the machine to accept a IP address from the
7083 kvm internal DHCP server:&lt;/p&gt;
7084
7085 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7086 settrans -fgap /dev/netdde /hurd/netdde
7087 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
7088 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
7089 dhclient /dev/eth0
7090 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7091
7092 &lt;p&gt;After this, the machine had internet connectivity, and I could
7093 upgrade it and install the sysvinit packages from experimental and
7094 enable it as the default boot system in Hurd.&lt;/p&gt;
7095
7096 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
7097 running on the machine it for ssh login to work a password need to be
7098 set. Also, note that a bug somewhere in openssh on Hurd block
7099 compression from working. Remember to turn that off on the client
7100 side.&lt;/p&gt;
7101
7102 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
7103 stuff:&lt;/p&gt;
7104
7105 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7106 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
7107 deb http://http.debian.net/debian/ experimental main
7108 EOF
7109 apt-get update
7110 apt-get dist-upgrade
7111 apt-get install -t experimental initscripts sysv-rc sysvinit \
7112 sysvinit-core sysvinit-utils
7113 update-alternatives --config runsystem
7114 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7115
7116 &lt;p&gt;To reboot after switching boot system, you have to use
7117 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
7118 yet a sysvinit process able to receive the signals from the normal
7119 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
7120 upgrading every package and rebooting, the network come up with DHCP
7121 after boot as it should, and the settrans/pkill hack mentioned at the
7122 start is no longer needed. But for some strange reason, there are no
7123 longer any login prompt in the virtual console, so I logged in using
7124 ssh instead.
7125
7126 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
7127 fail some times. No idea what the cause is, but hope the Hurd porters
7128 figure it out. At least Justus said on IRC (#debian-hurd on
7129 irc.debian.org) that they are aware of the problem. A way to reduce
7130 the impact is to upgrade to the Hurd packages built by Justus by
7131 adding this repository to the machine:&lt;/p&gt;
7132
7133 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7134 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
7135 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7136 EOF
7137 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7138
7139 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
7140 http://ftp.debian-ports.org/debian, because some of the packages in
7141 unstable do not yet include the required patches that are lingering in
7142 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
7143
7144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7145 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
7146 i emacs - GNU Emacs editor (metapackage)
7147 i gdb - GNU Debugger
7148 i hurd-recommended - Miscellaneous translators
7149 i isc-dhcp-client - ISC DHCP client
7150 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7151 i libc-bin - Embedded GNU C Library: Binaries
7152 i libc-dev-bin - Embedded GNU C Library: Development binaries
7153 i libc0.3 - Embedded GNU C Library: Shared libraries
7154 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7155 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7156 i multiarch-support - Transitional package to ensure multiarch compatibilit
7157 i A x11-common - X Window System (X.Org) infrastructure
7158 i xorg - X.Org X Window System
7159 i A xserver-xorg - X.Org X server
7160 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7161 #
7162 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7163
7164 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
7165 X.org did not work out of the box and I never took the time to follow
7166 the porters instructions to fix it. This time I was interested in the
7167 command line stuff.&lt;p&gt;
7168 </description>
7169 </item>
7170
7171 <item>
7172 <title>New chrpath release 0.16</title>
7173 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
7174 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
7175 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
7176 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
7177 find problems in C, C++ and Java code using static source code
7178 analysis. It can detect a lot of different problems, and is very
7179 useful to find memory and locking bugs in the error handling part of
7180 the source. The company behind it provide
7181 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
7182 a community service&lt;/a&gt;, and many hundred free software projects are
7183 already checked. A few days ago I decided to have a closer look at
7184 the Coverity system, and discovered that the
7185 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
7186 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
7187 projects I am involved with was already registered. But these are
7188 fairly big, and I would also like to have a small and easy project to
7189 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
7190 checking of the chrpath project&lt;/a&gt;. It was
7191 added to the checker and discovered seven potential defects. Six of
7192 these were real, mostly resource &quot;leak&quot; when the program detected an
7193 error. Nothing serious, as the resources would be released a fraction
7194 of a second later when the program exited because of the error, but it
7195 is nice to do it right in case the source of the program some time in
7196 the future end up in a library. Having fixed all defects and added
7197 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
7198 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
7199 publish a new release. These are the release notes:&lt;/p&gt;
7200
7201 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
7202
7203 &lt;ul&gt;
7204
7205 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
7206 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
7207 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
7208
7209 &lt;/ul&gt;
7210
7211 &lt;p&gt;You can
7212 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7213 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
7214 project if something is wrong with the new release. The test suite
7215 did not discover any old errors, so if you find a new one, please also
7216 include a test suite check.&lt;/p&gt;
7217 </description>
7218 </item>
7219
7220 <item>
7221 <title>New chrpath release 0.15</title>
7222 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
7223 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
7224 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
7225 <description>&lt;p&gt;After many years break from the package and a vain hope that
7226 development would be continued by someone else, I finally pulled my
7227 acts together this morning and wrapped up a new release of chrpath,
7228 the command line tool to modify the rpath and runpath of already
7229 compiled ELF programs. The update was triggered by the persistence of
7230 Isha Vishnoi at IBM, which needed a new config.guess file to get
7231 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
7232 is working on. I checked the
7233 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
7234 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
7235 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
7236 packages for interesting patches (failed to find the source from
7237 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7238 These are the release notes:&lt;/p&gt;
7239
7240 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
7241
7242 &lt;ul&gt;
7243
7244 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
7245 with newer architectures. Thanks to isha vishnoi for the heads
7246 up.&lt;/li&gt;
7247
7248 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
7249
7250 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7251 Matthias Klose.&lt;/li&gt;
7252
7253 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
7254 Petr Machata found in Fedora.&lt;/li&gt;
7255
7256 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
7257 .dynamic is a NULL terminated string. Based on patch found in
7258 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
7259
7260 &lt;/ul&gt;
7261
7262 &lt;p&gt;You can
7263 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7264 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
7265 project if something is wrong with the new release. The test suite
7266 did not discover any old errors, so if you find a new one, please also
7267 include a testsuite check.&lt;/p&gt;
7268 </description>
7269 </item>
7270
7271 <item>
7272 <title>Debian init.d boot script example for rsyslog</title>
7273 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
7274 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
7275 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
7276 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
7277 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
7278 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
7279 init.d scripts at all. Here is an example init.d script, ie a rewrite
7280 of /etc/init.d/rsyslog:&lt;/p&gt;
7281
7282 &lt;p&gt;&lt;pre&gt;
7283 #!/lib/init/init-d-script
7284 ### BEGIN INIT INFO
7285 # Provides: rsyslog
7286 # Required-Start: $remote_fs $time
7287 # Required-Stop: umountnfs $time
7288 # X-Stop-After: sendsigs
7289 # Default-Start: 2 3 4 5
7290 # Default-Stop: 0 1 6
7291 # Short-Description: enhanced syslogd
7292 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7293 # It is quite compatible to stock sysklogd and can be
7294 # used as a drop-in replacement.
7295 ### END INIT INFO
7296 DESC=&quot;enhanced syslogd&quot;
7297 DAEMON=/usr/sbin/rsyslogd
7298 &lt;/pre&gt;&lt;/p&gt;
7299
7300 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
7301 script was 137 lines, and the above is just 15 lines, most of it meta
7302 info/comments.&lt;/p&gt;
7303
7304 &lt;p&gt;How to do this, you ask? Well, one create a new script
7305 /lib/init/init-d-script looking something like this:
7306
7307 &lt;p&gt;&lt;pre&gt;
7308 #!/bin/sh
7309
7310 # Define LSB log_* functions.
7311 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
7312 # and status_of_proc is working.
7313 . /lib/lsb/init-functions
7314
7315 #
7316 # Function that starts the daemon/service
7317
7318 #
7319 do_start()
7320 {
7321 # Return
7322 # 0 if daemon has been started
7323 # 1 if daemon was already running
7324 # 2 if daemon could not be started
7325 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
7326 || return 1
7327 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7328 $DAEMON_ARGS \
7329 || return 2
7330 # Add code here, if necessary, that waits for the process to be ready
7331 # to handle requests from services started subsequently which depend
7332 # on this one. As a last resort, sleep for some time.
7333 }
7334
7335 #
7336 # Function that stops the daemon/service
7337 #
7338 do_stop()
7339 {
7340 # Return
7341 # 0 if daemon has been stopped
7342 # 1 if daemon was already stopped
7343 # 2 if daemon could not be stopped
7344 # other if a failure occurred
7345 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
7346 RETVAL=&quot;$?&quot;
7347 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
7348 # Wait for children to finish too if this is a daemon that forks
7349 # and if the daemon is only ever run from this initscript.
7350 # If the above conditions are not satisfied then add some other code
7351 # that waits for the process to drop all resources that could be
7352 # needed by services started subsequently. A last resort is to
7353 # sleep for some time.
7354 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
7355 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
7356 # Many daemons don&#39;t delete their pidfiles when they exit.
7357 rm -f $PIDFILE
7358 return &quot;$RETVAL&quot;
7359 }
7360
7361 #
7362 # Function that sends a SIGHUP to the daemon/service
7363 #
7364 do_reload() {
7365 #
7366 # If the daemon can reload its configuration without
7367 # restarting (for example, when it is sent a SIGHUP),
7368 # then implement that here.
7369 #
7370 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
7371 return 0
7372 }
7373
7374 SCRIPTNAME=$1
7375 scriptbasename=&quot;$(basename $1)&quot;
7376 echo &quot;SN: $scriptbasename&quot;
7377 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
7378 script=&quot;$1&quot;
7379 shift
7380 . $script
7381 else
7382 exit 0
7383 fi
7384
7385 NAME=$(basename $DAEMON)
7386 PIDFILE=/var/run/$NAME.pid
7387
7388 # Exit if the package is not installed
7389 #[ -x &quot;$DAEMON&quot; ] || exit 0
7390
7391 # Read configuration variable file if it is present
7392 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
7393
7394 # Load the VERBOSE setting and other rcS variables
7395 . /lib/init/vars.sh
7396
7397 case &quot;$1&quot; in
7398 start)
7399 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
7400 do_start
7401 case &quot;$?&quot; in
7402 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7403 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7404 esac
7405 ;;
7406 stop)
7407 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
7408 do_stop
7409 case &quot;$?&quot; in
7410 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7411 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7412 esac
7413 ;;
7414 status)
7415 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
7416 ;;
7417 #reload|force-reload)
7418 #
7419 # If do_reload() is not implemented then leave this commented out
7420 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
7421 #
7422 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
7423 #do_reload
7424 #log_end_msg $?
7425 #;;
7426 restart|force-reload)
7427 #
7428 # If the &quot;reload&quot; option is implemented then remove the
7429 # &#39;force-reload&#39; alias
7430 #
7431 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
7432 do_stop
7433 case &quot;$?&quot; in
7434 0|1)
7435 do_start
7436 case &quot;$?&quot; in
7437 0) log_end_msg 0 ;;
7438 1) log_end_msg 1 ;; # Old process is still running
7439 *) log_end_msg 1 ;; # Failed to start
7440 esac
7441 ;;
7442 *)
7443 # Failed to stop
7444 log_end_msg 1
7445 ;;
7446 esac
7447 ;;
7448 *)
7449 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
7450 exit 3
7451 ;;
7452 esac
7453
7454 :
7455 &lt;/pre&gt;&lt;/p&gt;
7456
7457 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
7458 lot. I did not really polish the approach, so it might not always
7459 work out of the box, but you get the idea. I did not try very hard to
7460 optimize it nor make it more robust either.&lt;/p&gt;
7461
7462 &lt;p&gt;A better argument for switching init system in Debian than reducing
7463 the size of init scripts (which is a good thing to do anyway), is to
7464 get boot system that is able to handle the kernel events sensibly and
7465 robustly, and do not depend on the boot to run sequentially. The boot
7466 and the kernel have not behaved sequentially in years.&lt;/p&gt;
7467 </description>
7468 </item>
7469
7470 <item>
7471 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
7472 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
7473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
7474 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
7475 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
7476 remote display access is the preferred solution with oVirt and RedHat
7477 Enterprise Virtualization, and I was sad to discover the other day
7478 that the browser plugin needed to use these systems seamlessly was
7479 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
7480 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
7481 2013-04-01, so I decided to wrap up a package based on the great work
7482 from Cajus Pollmeier and put it in a collab-maint maintained git
7483 repository to get a package I could use. I would very much like
7484 others to help me maintain the package (or just take over, I do not
7485 mind), but as no-one had volunteered so far, I just uploaded it to
7486 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
7487
7488 &lt;p&gt;The source is now available from
7489 &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;
7490 </description>
7491 </item>
7492
7493 <item>
7494 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
7495 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
7496 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
7497 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
7498 <description>&lt;p&gt;The
7499 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
7500 program is a a very nice system to create virtual machine images. It
7501 create a image file, add a partition table, mount it and run
7502 debootstrap in the mounted directory to create a Debian system on a
7503 stick. Yesterday, I decided to try to teach it how to make images for
7504 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
7505 of a plan to simplify the build system for
7506 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
7507 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
7508 the virtualbox images, but its current build system made multistrap
7509 based system for Dreamplug images, and it is lacking support for
7510 Raspberry Pi.&lt;/p&gt;
7511
7512 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
7513 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7514 code and adjusted it to be able to build armel images on my amd64
7515 Debian laptop. I ended up giving vmdebootstrap five new options,
7516 allowing me to replicate the image creation process I use to make
7517 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
7518 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
7519 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
7520 call debootstrap with --foreign and to copy the handler into the
7521 generated chroot before running the second stage. This allow
7522 vmdebootstrap to create armel images on an amd64 host. Next I added
7523 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
7524 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
7525 given file system type, allowing me to create an image with a vfat
7526 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
7527 variant&lt;/tt&gt; option to allow me to create smaller images without the
7528 Debian base system packages installed. Finally, I added an option
7529 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
7530 as a boot loader. It is not needed on the Raspberry Pi and probably
7531 most other non-x86 architectures. The changes were accepted by the
7532 upstream author of vmdebootstrap yesterday and today, and is now
7533 available from
7534 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
7535 upstream project page&lt;/a&gt;.&lt;/p&gt;
7536
7537 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
7538 create a small script (the customize script) to add the non-free
7539 binary blob needed to boot the Raspberry Pi and the APT source
7540 list:&lt;/p&gt;
7541
7542 &lt;p&gt;&lt;pre&gt;
7543 #!/bin/sh
7544 set -e # Exit on first error
7545 rootdir=&quot;$1&quot;
7546 cd &quot;$rootdir&quot;
7547 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
7548 deb http://http.debian.net/debian/ jessie main contrib non-free
7549 EOF
7550 # Install non-free binary blob needed to boot Raspberry Pi. This
7551 # install a kernel somewhere too.
7552 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7553 -O $rootdir/usr/bin/rpi-update
7554 chmod a+x $rootdir/usr/bin/rpi-update
7555 mkdir -p $rootdir/lib/modules
7556 touch $rootdir/boot/start.elf
7557 chroot $rootdir rpi-update
7558 &lt;/pre&gt;&lt;/p&gt;
7559
7560 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
7561 to build the image:&lt;/p&gt;
7562
7563 &lt;pre&gt;
7564 sudo ./vmdebootstrap \
7565 --variant minbase \
7566 --arch armel \
7567 --distribution jessie \
7568 --mirror http://http.debian.net/debian \
7569 --image test.img \
7570 --size 600M \
7571 --bootsize 64M \
7572 --boottype vfat \
7573 --log-level debug \
7574 --verbose \
7575 --no-kernel \
7576 --no-extlinux \
7577 --root-password raspberry \
7578 --hostname raspberrypi \
7579 --foreign /usr/bin/qemu-arm-static \
7580 --customize `pwd`/customize \
7581 --package netbase \
7582 --package git-core \
7583 --package binutils \
7584 --package ca-certificates \
7585 --package wget \
7586 --package kmod
7587 &lt;/pre&gt;&lt;/p&gt;
7588
7589 &lt;p&gt;The list of packages being installed are the ones needed by
7590 rpi-update to make the image bootable on the Raspberry Pi, with the
7591 exception of netbase, which is needed by debootstrap to find
7592 /etc/hosts with the minbase variant. I really wish there was a way to
7593 set up an Raspberry Pi using only packages in the Debian archive, but
7594 that is not possible as far as I know, because it boots from the GPU
7595 using a non-free binary blob.&lt;/p&gt;
7596
7597 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
7598 probably a few others installed. I have not checked the complete
7599 build dependency list.&lt;/p&gt;
7600
7601 &lt;p&gt;The resulting image will not use the hardware floating point unit
7602 on the Raspberry PI, because the armel architecture in Debian is not
7603 optimized for that use. So the images created will be a bit slower
7604 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
7605 </description>
7606 </item>
7607
7608 <item>
7609 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
7610 <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>
7611 <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>
7612 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
7613 <description>&lt;p&gt;The last few days I came across a few good causes that should get
7614 wider attention. I recommend signing and donating to each one of
7615 these. :)&lt;/p&gt;
7616
7617 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
7618 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
7619 Women program which is a Google Summer of Code like initiative to get
7620 more women involved in free software. One debian sponsor has offered
7621 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
7622 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
7623 hope you will to. :)&lt;/p&gt;
7624
7625 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
7626 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
7627 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
7628 take place these days, and their need to fund the work. I&#39;ve already
7629 donated. Are you next?&lt;/p&gt;
7630
7631 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
7632 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7633 statement under the heading
7634 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
7635 Access&lt;/a&gt; for those of us asking for more focus on open access in the
7636 Norwegian government. So far 499 signatures. I hope you will sign it
7637 too.&lt;/p&gt;
7638 </description>
7639 </item>
7640
7641 <item>
7642 <title>Videos about the Freedombox project - for inspiration and learning</title>
7643 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
7644 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
7645 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
7646 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
7647 project&lt;/a&gt; have been going on for a while, and have presented the
7648 vision, ideas and solution several places. Here is a little
7649 collection of videos of talks and presentation of the project.&lt;/p&gt;
7650
7651 &lt;ul&gt;
7652
7653 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
7654 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
7655
7656 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
7657 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7658
7659 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
7660 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7661 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
7662 (Youtube)&lt;/li&gt;
7663
7664 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
7665 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
7666
7667 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
7668 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7669
7670 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
7671 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7672 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
7673
7674 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7675 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7676 (Youtube)&lt;/li&gt;
7677
7678 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7679 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7680
7681 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7682 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7683
7684 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7685 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7686 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7687
7688 &lt;/ul&gt;
7689
7690 &lt;p&gt;A larger list is available from
7691 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7692 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7693
7694 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7695 Jessie is coming along quite well, and soon both Owncloud and using
7696 Tor should be available for testers of the Freedombox solution. :) In
7697 a few weeks I hope everything needed to test it is included in Debian.
7698 The withsqlite package is already in Debian, and the plinth package is
7699 pending in NEW. The third and vital part of that puzzle is the
7700 metapackage/setup framework, which is still pending an upload. Join
7701 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7702 (#freedombox on irc.debian.org)&lt;/a&gt; and
7703 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7704 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7705 </description>
7706 </item>
7707
7708 <item>
7709 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7710 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7711 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7712 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7713 <description>&lt;p&gt;I was introduced to the
7714 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7715 in 2010, when Eben Moglen presented his vision about serving the need
7716 of non-technical people to keep their personal information private and
7717 within the legal protection of their own homes. The idea is to give
7718 people back the power over their network and machines, and return
7719 Internet back to its intended peer-to-peer architecture. Instead of
7720 depending on a central service, the Freedombox will give everyone
7721 control over their own basic infrastructure.&lt;/p&gt;
7722
7723 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7724 taken priority. But this summers nasty news about the misuse of trust
7725 and privilege exercised by the &quot;western&quot; intelligence gathering
7726 communities increased my eagerness to contribute to a point where I
7727 actually started working on the project a while back.&lt;/p&gt;
7728
7729 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7730 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7731 create a simple and cheap Debian based appliance that anyone can hook
7732 up in their home and get access to secure and private services and
7733 communication. The initial deployment platform have been the
7734 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7735 which is a piece of hardware I do not own. So to be able to test what
7736 the current Freedombox setup look like, I had to come up with a way to install
7737 it on some hardware I do have access to. I have rewritten the
7738 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7739 image build framework to use .deb packages instead of only copying
7740 setup into the boot images, and thanks to this rewrite I am able to
7741 set up any machine supported by Debian Wheezy as a Freedombox, using
7742 the previously mentioned deb (and a few support debs for packages
7743 missing in Debian).&lt;/p&gt;
7744
7745 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7746 scripts
7747 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7748 and a administrative web interface
7749 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7750 withsqlite), as well as a privacy enhancing proxy based on
7751 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7752 (freedombox-privoxy). There is also a web/javascript based XMPP
7753 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7754 trying (unsuccessfully so far) to talk to the XMPP server
7755 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7756 web interface is pluggable, and the goal is to use it to enable OpenID
7757 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7758 this is really working yet, see
7759 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7760 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7761 on github at the moment. The HTTP proxy is operational out of the
7762 box, and the admin web interface can be used to add/remove plinth
7763 users. I&#39;ve not been able to do anything else with it so far, but
7764 know there are several branches spread around github and other places
7765 with lots of half baked features.&lt;/p&gt;
7766
7767 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7768 following recipes should work to give you a test machine to poke
7769 at.&lt;/p&gt;
7770
7771 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7772
7773 &lt;ol&gt;
7774
7775 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7776 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7777 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7778 to the Debian installer:&lt;p&gt;
7779 &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;
7780
7781 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7782 install on.&lt;/li&gt;
7783
7784 &lt;li&gt;When the installation is finished and the machine have rebooted a
7785 few times, your Freedombox is ready for testing.&lt;/li&gt;
7786
7787 &lt;/ol&gt;
7788
7789 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7790
7791 &lt;ol&gt;
7792
7793 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7794 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
7795 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
7796 &lt;pre&gt;
7797 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
7798 &lt;/pre&gt;&lt;/li&gt;
7799 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
7800 &lt;pre&gt;
7801 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7802 apt-key add -
7803 apt-get update
7804 apt-get install freedombox-setup
7805 /usr/lib/freedombox/setup
7806 &lt;/pre&gt;&lt;/li&gt;
7807 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
7808
7809 &lt;/ol&gt;
7810
7811 &lt;p&gt;You can test it on other architectures too, but because the
7812 freedombox-privoxy package is binary, it will only work as intended on
7813 the architectures where I have had time to build the binary and put it
7814 in my APT repository. But do not let this stop you. It is only a
7815 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
7816
7817 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
7818 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
7819 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
7820 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
7821
7822 &lt;p&gt;Please let me know if this works for you, or if you have any
7823 problems. We gather on the IRC channel
7824 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
7825 irc.debian.org and the
7826 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
7827 mailing list&lt;/a&gt;.&lt;/p&gt;
7828
7829 &lt;p&gt;Once you get your freedombox operational, you can visit
7830 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
7831 welcome screen (dead end - do not be surprised if you are unable to
7832 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
7833 to look at the rest of plinth. The default user is &#39;admin&#39; and the
7834 default password is &#39;secret&#39;.&lt;/p&gt;
7835 </description>
7836 </item>
7837
7838 <item>
7839 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
7840 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
7841 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
7842 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
7843 <description>&lt;p&gt;Earlier, I reported about
7844 &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
7845 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
7846 told by IBM that the original disk should be thrown away. And as
7847 there no longer was a problem if I bricked the firmware, I decided
7848 today to try to install Intel firmware to replace the Lenovo firmware
7849 currently on the disk.&lt;/p&gt;
7850
7851 &lt;p&gt;I searched the Intel site for firmware, and found
7852 &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;
7853 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7854 according to the site should contain the latest firmware for SSD
7855 disks. I inserted the broken disk in one of my spare laptops and
7856 booted the ISO from a USB stick. The disk was recognized, but the
7857 program claimed the newest firmware already were installed and refused
7858 to insert any Intel firmware. So no change, and the disk is still
7859 unable to handle write load. :( I guess the only way to get them
7860 working would be if Lenovo releases new firmware. No idea how likely
7861 that is. Anyway, just blogging about this test for completeness. I
7862 got a working Samsung disk, and see no point in spending more time on
7863 the broken disks.&lt;/p&gt;
7864 </description>
7865 </item>
7866
7867 <item>
7868 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
7869 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
7870 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
7871 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
7872 <description>&lt;p&gt;Today I switched to
7873 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
7874 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
7875 my new Thinkpad X230, which was delivered with an
7876 &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
7877 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
7878 sustained writes. My hardware supplier have been very forthcoming in
7879 trying to find a solution, and after first trying with another
7880 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
7881 disk instead to fix it once and for all. The Samsung disk survived
7882 the installation of Debian with encrypted disks (filling the disk with
7883 random data during installation killed the first two), and I thus
7884 decided to trust it with my data. I have installed it as a Debian Edu
7885 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7886 server at home using Kerberos and LDAP, and will use it as my work
7887 station from now on.&lt;/p&gt;
7888
7889 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
7890 Debian Wheezy default installation need to be tuned a bit to increase
7891 performance and increase life time of the disk. The Linux kernel and
7892 user space applications do not yet adjust automatically to such
7893 environment. To make it easier for my self, I created a draft Debian
7894 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
7895 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
7896 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
7897 is set up to adjust the setup of the machine by just installing the
7898 package. If there is any non-SSD disk in the machine, the package
7899 will refuse to install, as I did not try to write any logic to sort
7900 file systems in SSD and non-SSD file systems.&lt;/p&gt;
7901
7902 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
7903 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7904 where I set up the machine with one large encrypted partition (in
7905 addition to /boot), put LVM on top of this and set up partitions on
7906 top of this again. See the README file in the package source for the
7907 references I used to pick the settings. At the moment these
7908 parameters are tuned:&lt;/p&gt;
7909
7910 &lt;ul&gt;
7911
7912 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
7913 (adding discard to /etc/crypttab)&lt;/li&gt;
7914
7915 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
7916 this case a cryptsetup partition) by changing issue_discards from
7917 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
7918
7919 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
7920 systems.&lt;/li&gt;
7921
7922 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
7923 /etc/fstab.&lt;/li&gt;
7924
7925 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
7926
7927 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
7928 cron.daily).&lt;/li&gt;
7929
7930 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
7931 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
7932
7933 &lt;/ul&gt;
7934
7935 &lt;p&gt;During installation, I cancelled the part where the installer fill
7936 the disk with random data, as this would kill the SSD performance for
7937 little gain. My goal with the encrypted file system is to ensure
7938 those stealing my laptop end up with a brick and not a working
7939 computer. I have no hope in keeping the really resourceful people
7940 from getting the data on the disk (see
7941 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
7942 Thus I concluded that adding the discard option to crypttab is the
7943 right thing to do.&lt;/p&gt;
7944
7945 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
7946 it for SSD, but others recommended deadline and a benchmark I found
7947 indicated that deadline might be better for interactive use.&lt;/p&gt;
7948
7949 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
7950 and ext4, but read that it would give a performance hit ever time a
7951 file is removed, and thought it best to that that slowdown once a day
7952 instead of during my work.&lt;/p&gt;
7953
7954 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7955 this is already done by Debian Edu.&lt;/p&gt;
7956
7957 &lt;p&gt;I have not yet started on the user space tuning. I expect
7958 iceweasel need some tuning, and perhaps other applications too, but
7959 have not yet had time to investigate those parts.&lt;/p&gt;
7960
7961 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
7962 there.&lt;/p&gt;
7963
7964 &lt;p&gt;As for the answer to the question in the title of this blog post,
7965 as far as I know, the only solution I know about is to replace the
7966 disk. It might be possible to flash it with Intel firmware instead of
7967 the Lenovo firmware. But I have not tried and did not want to do so
7968 without approval from Lenovo as I wanted to keep the warranty on the
7969 disk until a solution was found and they wanted the broken disks
7970 back.&lt;/p&gt;
7971 </description>
7972 </item>
7973
7974 <item>
7975 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
7976 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
7977 <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>
7978 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
7979 <description>&lt;p&gt;A few days ago, I wrote about
7980 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
7981 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
7982 was dying during installation because it is unable to cope with
7983 sustained write. My supplier is in contact with
7984 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
7985 replacement disk to try to fix the problem. They decided to send an
7986 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
7987
7988 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
7989 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7990 same firmware version as the original. This time my hope raised
7991 slightly as the installation progressed, as the original disk used to
7992 die after 4-7% of the disk was written to, while this time it kept
7993 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
7994 died again and I was back on square one. I still do not have a new
7995 laptop with a disk I can trust. I can not live with a disk that might
7996 lock up when I download a new
7997 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
7998 other large files. I look forward to hearing from my supplier with
7999 the next proposal from Lenovo.&lt;/p&gt;
8000
8001 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
8002 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
8003 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
8004 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
8005 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
8006 P/N 45N8295, P0C38732.&lt;/p&gt;
8007
8008 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
8009 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
8010 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
8011 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
8012 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
8013 P/N 45N8295, P0C38732.&lt;/p&gt;
8014
8015 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
8016 SA, date and WNPP values. Mentioning all the details here in case
8017 someone is able to use the information to find a way to identify the
8018 failing disk among working ones (if any such working disk actually
8019 exist).&lt;/p&gt;
8020 </description>
8021 </item>
8022
8023 <item>
8024 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
8025 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
8026 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
8027 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
8028 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
8029 Debian Edu developer gathering and Debian and Ubuntu bug squashing
8030 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
8031 member assosiation NUUG&lt;/a&gt; and
8032 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
8033 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
8034 Bitraf&lt;/a&gt;.&lt;/p&gt;
8035
8036 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
8037 welcome, and there is no fee to participate. There is on the other
8038 hand limited space, and only room for 30 people. Please put your name
8039 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
8040 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
8041 </description>
8042 </item>
8043
8044 <item>
8045 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
8046 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
8047 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
8048 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
8049 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
8050 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
8051 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
8052 time to spend on it, and it took a while to find a model I believe
8053 will do the job, but two days ago the replacement finally arrived. I
8054 ended up picking a
8055 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
8056 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
8057 a roaming workstation, and it seemed to work flawlessly. But my
8058 second installation with encrypted disk was not as successful. More
8059 on that below.&lt;/p&gt;
8060
8061 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8062 important requirements (robust and with a good keyboard) are never
8063 listed in the feature list. But I did get good help from the search
8064 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8065 allowed me to limit the list of interesting laptops based on my other
8066 requirements. A bit surprising that SSD disk are not disks according
8067 to that search interface, so I had to drop specifying the number of
8068 disks from my search parameters. I also asked around among friends to
8069 get their impression on keyboards and robustness.&lt;/p&gt;
8070
8071 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
8072 X41. I am not quite convinced about the keyboard, as it is
8073 significantly wider than my old keyboard, and I have to stretch my
8074 hand a lot more to reach the edges. But the key response is fairly
8075 good and the individual key shape is fairly easy to handle, so I hope
8076 I will get used to it. My old X40 was starting to fail, and I really
8077 needed a new laptop now. :)&lt;/p&gt;
8078
8079 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
8080 visit to the BIOS during boot it disable it.&lt;/p&gt;
8081
8082 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
8083 lock up during load. And this happen when installing Debian Wheezy
8084 with encrypted disk, while the disk is being filled with random data.
8085 I also tested to install Ubuntu Raring, and it happen there too if I
8086 reenable the code to fill the disk with random data (it is disabled by
8087 default in Ubuntu). And the bug with is already known. It was
8088 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
8089 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
8090 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
8091 kernel developers as
8092 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
8093 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
8094 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
8095 Lenovo forums, both for
8096 &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
8097 2012-11-10&lt;/a&gt; and for
8098 &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
8099 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
8100 reports state that the disk lock up during use if many writes are done
8101 on the disk, so it is much no use to work around the installation
8102 problem and end up with a computer that can lock up at any moment.
8103 There is even a
8104 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
8105 available&lt;/a&gt; that will lock up the hard drive after running a few
8106 minutes by writing to a file.&lt;/p&gt;
8107
8108 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
8109 contacting PCHELP Norway (request 01D1FDP) which handle support
8110 requests for Lenovo, his first suggestion was to upgrade the disk
8111 firmware. Unfortunately there is no newer firmware available from
8112 Lenovo, as my disk already have the most recent one (version LF1i). I
8113 hope to hear more from him today and hope the problem can be
8114 fixed. :)&lt;/p&gt;
8115 </description>
8116 </item>
8117
8118 <item>
8119 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
8120 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
8121 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
8122 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
8123 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
8124 trusty old Thinkpad X41. Unfortunately I did not have much time to
8125 spend on it, but today the replacement finally arrived. I ended up
8126 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
8127 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
8128 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8129 this, it is installing what I hope will be a more final installation,
8130 with a encrypted hard drive to ensure any dope head stealing it end up
8131 with an expencive door stop.&lt;/p&gt;
8132
8133 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8134 important requirements (robust and with a good keyboard) are never
8135 listed in the feature list. But I did get good help from the search
8136 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8137 allowed me to limit the list of interesting laptops based on my other
8138 requirements. A bit surprising that SSD disk are not disks, so I had
8139 to drop number of disks from my search parameters.&lt;/p&gt;
8140
8141 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
8142 wider than my old keyboard, and I have to stretch my hand a lot more
8143 to reach the edges. But the key response is fairly good and the
8144 individual key shape is fairly easy to handle, so I hope I will get
8145 used to it. My old X40 was starting to fail, and I really needed a
8146 new laptop now. :)&lt;/p&gt;
8147
8148 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
8149 </description>
8150 </item>
8151
8152 <item>
8153 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
8154 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
8155 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
8156 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
8157 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
8158 perfectly capable of, and I have to do it manually to get things
8159 working. One such task is to find out what firmware packages are
8160 needed to get the hardware on my computer working. Most often this
8161 affect the wifi card, but some times it even affect the RAID
8162 controller or the ethernet card. Today I pushed version 0.4 of the
8163 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
8164 including a new script isenkram-autoinstall-firmware handling the
8165 process of asking all the loaded kernel modules what firmware files
8166 they want, find debian packages providing these files and install the
8167 debian packages. Here is a test run on my laptop:&lt;/p&gt;
8168
8169 &lt;p&gt;&lt;pre&gt;
8170 # isenkram-autoinstall-firmware
8171 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8172 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8173 info: locating packages with the requested firmware files
8174 info: Updating APT sources after adding non-free APT source
8175 info: trying to install firmware-ipw2x00
8176 firmware-ipw2x00
8177 firmware-ipw2x00
8178 Preconfiguring packages ...
8179 Selecting previously deselected package firmware-ipw2x00.
8180 (Reading database ... 259727 files and directories currently installed.)
8181 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8182 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
8183 #
8184 &lt;/pre&gt;&lt;/p&gt;
8185
8186 &lt;p&gt;When all the requested firmware is present, a simple message is
8187 printed instead:&lt;/p&gt;
8188
8189 &lt;p&gt;&lt;pre&gt;
8190 # isenkram-autoinstall-firmware
8191 info: did not find any firmware files requested by loaded kernel modules. exiting
8192 #
8193 &lt;/pre&gt;&lt;/p&gt;
8194
8195 &lt;p&gt;It could use some polish, but it is already working well and saving
8196 me some time when setting up new machines. :)&lt;/p&gt;
8197
8198 &lt;p&gt;So, how does it work? It look at the set of currently loaded
8199 kernel modules, and look up each one of them using modinfo, to find
8200 the firmware files listed in the module meta-information. Next, it
8201 download the Contents file from a nearby APT mirror, and search for
8202 the firmware files in this file to locate the package with the
8203 requested firmware file. If the package is in the non-free section, a
8204 non-free APT source is added and the package is installed using
8205 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
8206 machine.&lt;/p&gt;
8207
8208 &lt;p&gt;I hope someone find time to implement a more polished version of
8209 this script as part of the hw-detect debian-installer module, to
8210 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
8211 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
8212 firmware during a PXE install when the packages already are available
8213 from the nearby Debian mirror.&lt;/p&gt;
8214 </description>
8215 </item>
8216
8217 <item>
8218 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
8219 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
8220 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
8221 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
8222 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8223 the screen just turn black when Linux boot, either during installation
8224 or on first boot from the hard disk. I&#39;ve seen it once in a while the
8225 last few years, but only recently understood the cause. I&#39;ve seen it
8226 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8227 The reason seem to be in the wiring of some laptops. The system to
8228 control the screen background light is inverted, so when Linux try to
8229 turn the brightness fully on, it end up turning it off instead. I do
8230 not know which Linux drivers are affected, but this post is about the
8231 i915 driver used by the
8232 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8233 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
8234
8235 &lt;p&gt;The problem can be worked around two ways. Either by adding
8236 i915.invert_brightness=1 as a kernel option, or by adding a file in
8237 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
8238 option when it load the i915 kernel module. On Debian and Ubuntu, it
8239 can be done by running these commands as root:&lt;/p&gt;
8240
8241 &lt;pre&gt;
8242 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
8243 update-initramfs -u -k all
8244 &lt;/pre&gt;
8245
8246 &lt;p&gt;Since March 2012 there is
8247 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
8248 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
8249 hardware have this problem, and get the driver to invert the
8250 brightness setting automatically. To use it, one need to add a row in
8251 &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
8252 intel_quirks array&lt;/a&gt; in the driver source
8253 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
8254 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
8255 number (vendor number 8086 is assumed) and subdevice vendor and device
8256 number.&lt;/p&gt;
8257
8258 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
8259 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
8260
8261 &lt;p&gt;&lt;pre&gt;
8262 00:02.0 VGA compatible controller [0300]: Intel Corporation \
8263 3rd Gen Core processor Graphics Controller [8086:0156] \
8264 (rev 09) (prog-if 00 [VGA controller])
8265 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
8266 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8267 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8268 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
8269 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
8270 Latency: 0
8271 Interrupt: pin A routed to IRQ 42
8272 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
8273 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
8274 Region 4: I/O ports at 4000 [size=64]
8275 Expansion ROM at &lt;unassigned&gt; [disabled]
8276 Capabilities: &lt;access denied&gt;
8277 Kernel driver in use: i915
8278 &lt;/pre&gt;&lt;/p&gt;
8279
8280 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
8281
8282 &lt;p&gt;&lt;pre&gt;
8283 struct intel_quirk intel_quirks[] = {
8284 ...
8285 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8286 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
8287 ...
8288 }
8289 &lt;/pre&gt;&lt;/p&gt;
8290
8291 &lt;p&gt;According to the kernel module instructions (as seen using
8292 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
8293 invert_brightness flag should be sent to the
8294 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
8295 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
8296 developers. But my email about the laptop sent 2013-06-03 have not
8297 yet shown up in
8298 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
8299 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
8300 emails from non-subscribers. Because of this, I sent my patch also to
8301 the Debian bug tracking system instead as
8302 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
8303 sure the patch is not lost.&lt;/p&gt;
8304
8305 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
8306 with this problem working properly with Linux. If you use Gnome, your
8307 worries should be over at this point. But if you use KDE, there is
8308 something in KDE ignoring the invert_brightness setting and turning on
8309 the screen during login. I&#39;ve reported it to Debian as
8310 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
8311 have no idea yet how to figure out exactly what subsystem is doing
8312 this. Perhaps you can help? Perhaps you know what the Gnome
8313 developers did to handle this, and this can give a clue to the KDE
8314 developers? Or you know where in KDE the screen brightness is changed
8315 during login? If so, please update the BTS report (or get in touch if
8316 you do not know how to update BTS).&lt;/p&gt;
8317
8318 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
8319 acpi_backlight=vendor, to disable ACPI backlight support completely,
8320 as the ACPI information on the machine is trash and it is better to
8321 leave it to the intel video driver to control the screen
8322 backlight.&lt;/p&gt;
8323 </description>
8324 </item>
8325
8326 <item>
8327 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
8328 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
8329 <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>
8330 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
8331 <description>&lt;p&gt;Two days ago, I asked
8332 &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
8333 I could install Linux on a Packard Bell EasyNote LV computer
8334 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
8335 with the obstacles put in the way of Linux users on a laptop with UEFI
8336 and Windows 8.&lt;/p&gt;
8337
8338 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
8339 secure booting or fast boot. I suspect fast boot was the problem,
8340 causing the firmware to boot directly from HD without considering any
8341 key presses and alternative devices, but do not know UEFI settings
8342 enough to tell.&lt;/p&gt;
8343
8344 &lt;p&gt;There is no way to install Linux on the machine in question without
8345 opening the box and disconnecting the hard drive! This is as far as I
8346 can tell, the only way to get access to the firmware setup menu
8347 without accepting the Windows 8 license agreement. I am told (and
8348 found description on how to) that it is possible to configure the
8349 firmware setup once booted into Windows 8. But as I believe the terms
8350 of that agreement are completely unacceptable, accepting the license
8351 was never an alternative. I do not enter agreements I do not intend
8352 to follow.&lt;/p&gt;
8353
8354 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
8355 waste many hours on this, but luckily there was a way to get it to
8356 work. But I would not recommend it to anyone planning to run Linux on
8357 it, and I have become sceptical to Windows 8 certified laptops. Is
8358 this the way Linux will be forced out of the market place, by making
8359 it close to impossible for &quot;normal&quot; users to install Linux without
8360 accepting the Microsoft Windows license terms? Or at least not
8361 without risking to loose the warranty?&lt;/p&gt;
8362
8363 &lt;p&gt;I&#39;ve updated the
8364 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
8365 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
8366 do not have to struggle as much as I did to get Linux into the
8367 machine.&lt;/p&gt;
8368
8369 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8370 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
8371 </description>
8372 </item>
8373
8374 <item>
8375 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
8376 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
8377 <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>
8378 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
8379 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
8380 new laptops for my parents and a few others. I bought Packard Bell
8381 Easynote LV to run Kubuntu on and use as their home computer. But I
8382 am completely unable to figure out how to install Linux on it. The
8383 computer is preinstalled with Windows 8, and I suspect it uses UEFI
8384 instead of a BIOS to boot.&lt;/p&gt;
8385
8386 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
8387 to get it to boot the Linux installer from my USB stick. I have yet
8388 to try the DVD install, and still hope it will work. when I turn on
8389 the computer, there is no information on what buttons to press to get
8390 the normal boot menu. I expect to get some boot menu to select PXE or
8391 USB stick booting. When booting, it first ask for the language to
8392 use, then for some regional settings, and finally if I will accept the
8393 Windows 8 terms of use. As these terms are completely unacceptable to
8394 me, I have no other choice but to turn off the computer and try again
8395 to get it to boot the Linux installer.&lt;/p&gt;
8396
8397 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
8398 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8399 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
8400 installed on this machine, please get in touch or update that wiki
8401 page. If I can&#39;t find a way to install Linux, I will have to return
8402 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
8403
8404 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
8405 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
8406 on new Laptops?&lt;/p&gt;
8407 </description>
8408 </item>
8409
8410 <item>
8411 <title>How to transform a Debian based system to a Debian Edu installation</title>
8412 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
8413 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
8414 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
8415 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
8416 an operating system based on Debian intended for use in schools. It
8417 contain a turn-key solution for the computer network provided to
8418 pupils in the primary schools. It provide both the central server,
8419 network boot servers and desktop environments with heaps of
8420 educational software. The project was founded almost 12 years ago,
8421 2001-07-02. If you want to support the project, which is in need for
8422 cash to fund developer gatherings and other project related activity,
8423 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
8424 donate some money&lt;/a&gt;.
8425
8426 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
8427 lists and elsewhere, is the question on how to transform a Debian or
8428 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
8429 hard, and last week I wrote a script to replicate the steps done by
8430 the Debian Edu installer.&lt;/p&gt;
8431
8432 &lt;p&gt;The script,
8433 &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;
8434 in the debian-edu-config package, will go through these six steps and
8435 transform an existing Debian Wheezy or Ubuntu (untested) installation
8436 into a Debian Edu Workstation:&lt;/p&gt;
8437
8438 &lt;ol&gt;
8439
8440 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
8441 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
8442 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
8443 our configuration.&lt;/li&gt;
8444 &lt;li&gt;Preseed debconf database with profile setup in
8445 /etc/debian-edu/config, and run tasksel to install packages
8446 according to the profile specified in the config above,
8447 overriding some of the Debian automation machinery.&lt;/li&gt;
8448 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
8449 that could not be done using preseeding.&lt;/li&gt;
8450 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
8451
8452 &lt;/ol&gt;
8453
8454 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
8455 replicated like this. Disk partitioning and LVM setup, for example.
8456 So this script just assume there is enough disk space to install all
8457 the needed packages.&lt;/p&gt;
8458
8459 &lt;p&gt;The script was created to help a Debian Edu student working on
8460 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
8461 Debian Edu client, and using it he can take the existing
8462 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
8463 transform it into a fully functioning Debian Edu Workstation (or
8464 Roaming Workstation, or whatever :).&lt;/p&gt;
8465
8466 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
8467 If a LXDE based Roaming workstation is wanted instead, modify the
8468 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
8469
8470 &lt;p&gt;&lt;pre&gt;
8471 PROFILE=&quot;Roaming-Workstation&quot;
8472 DESKTOP=&quot;lxde&quot;
8473 &lt;/pre&gt;&lt;/p&gt;
8474
8475 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
8476 the cloud, by starting with a virtual Debian installation at some
8477 virtual hosting service and setting up all the services on first
8478 boot.&lt;/p&gt;
8479 </description>
8480 </item>
8481
8482 <item>
8483 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
8484 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
8485 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
8486 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
8487 <description>&lt;P&gt;In January,
8488 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
8489 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
8490 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
8491 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
8492 marvellous construction system from Denmark. We also created
8493 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
8494 a place to take notes and write down our plans and hopes. And several
8495 people showed up to help. I was very happy to see the effect of my
8496 call. Since the small start, we have a debtags tag
8497 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
8498 tag for LEGO related packages, and now count 10 packages related to
8499 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
8500
8501 &lt;p&gt;&lt;table&gt;
8502 &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;
8503 &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;
8504 &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;
8505 &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;
8506 &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;
8507 &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;
8508 &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;
8509 &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;
8510 &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;
8511 &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;
8512 &lt;/table&gt;&lt;/p&gt;
8513
8514 &lt;p&gt;Some of these are available in Wheezy, and all but one are
8515 currently available in Jessie/testing. leocad is so far only
8516 available in experimental.&lt;/p&gt;
8517
8518 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
8519 adding the rest of the great free software tools available on Linux
8520 for LEGO designers.&lt;/p&gt;
8521 </description>
8522 </item>
8523
8524 <item>
8525 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
8526 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
8527 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
8528 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
8529 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
8530 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
8531 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
8532 Debian release, and I expect to move my machines at home over to it fairly
8533 soon.&lt;/p&gt;
8534
8535 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
8536 in particular make me very happy to see included. The
8537 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
8538 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
8539 included for the first time. Alongside similar programs like
8540 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
8541 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
8542 it allow for visual programming where syntax errors can not happen,
8543 and a friendly programming environment for learning to control the
8544 computer. Scratch will also be included in the next release of Debian
8545 Edu.&lt;/a&gt;
8546
8547 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
8548 Edu/Skolelinux release too. The
8549 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
8550 alpha release&lt;/a&gt; went out last week, and the next should soon
8551 follow.&lt;p&gt;
8552 </description>
8553 </item>
8554
8555 <item>
8556 <title>Isenkram 0.2 finally in the Debian archive</title>
8557 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
8558 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
8559 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
8560 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
8561 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
8562 for many months. I uploaded it to the Debian experimental suite
8563 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
8564
8565 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
8566 install to work with a pluggable hardware device. The suggestion pop
8567 up when the device is plugged in. For example if a Lego Mindstorm NXT
8568 is inserted, it will suggest to install the program needed to program
8569 the NXT controller. Give it a go, and report bugs and suggestions to
8570 BTS. :)&lt;/p&gt;
8571 </description>
8572 </item>
8573
8574 <item>
8575 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
8576 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
8577 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
8578 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
8579 <description>&lt;p&gt;My
8580 &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
8581 bitcoin related blog post&lt;/a&gt; mentioned that the new
8582 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
8583 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8584 2013-01-19, and have been available in unstable since then. It was
8585 automatically copied to Ubuntu, and is available in their Raring
8586 version too.&lt;/p&gt;
8587
8588 &lt;p&gt;But there is a strange problem with the build that block this new
8589 version from being available on the i386 and kfreebsd-i386
8590 architectures. For some strange reason, the autobuilders in Debian
8591 for these architectures fail to run the test suite on these
8592 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
8593 We are so far unable to reproduce it when building it manually, and
8594 no-one have been able to propose a fix. If you got an idea what is
8595 failing, please let us know via the BTS.&lt;/p&gt;
8596
8597 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
8598 I often run low on disk space, is the fact that the client will exit
8599 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
8600 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
8601 it. :)&lt;/p&gt;
8602
8603 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8604 activities, please send Bitcoin donations to my address
8605 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8606 </description>
8607 </item>
8608
8609 <item>
8610 <title>Welcome to the world, Isenkram!</title>
8611 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
8612 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
8613 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
8614 <description>&lt;p&gt;Yesterday, I
8615 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
8616 for testers&lt;/a&gt; for my prototype for making Debian better at handling
8617 pluggable hardware devices, which I
8618 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
8619 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
8620 up, and caused me to really want to to open up the development to more
8621 people. But before I did this, I want to come up with a sensible name
8622 for this project. Today I finally decided on a new name, and I have
8623 renamed the project from hw-support-handler to this new name. In the
8624 process, I moved the source to git and made it available as a
8625 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
8626 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
8627 To fetch and build the latest version of the source, use&lt;/p&gt;
8628
8629 &lt;pre&gt;
8630 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8631 cd isenkram &amp;&amp; git-buildpackage -us -uc
8632 &lt;/pre&gt;
8633
8634 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
8635 want to hack on the source or improve the package, please go ahead.
8636 But please talk to me first on IRC or via email before you do major
8637 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
8638
8639 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
8640 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8641 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
8642 the German word eisenkram, for those that are familiar with that
8643 word.&lt;/p&gt;
8644
8645 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
8646 instructions, to avoid confusing people with an error from the signing
8647 process.&lt;/p&gt;
8648
8649 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
8650 clone argument to avoid the need for authentication.&lt;/p&gt;
8651 </description>
8652 </item>
8653
8654 <item>
8655 <title>First prototype ready making hardware easier to use in Debian</title>
8656 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
8657 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
8658 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
8659 <description>&lt;p&gt;Early this month I set out to try to
8660 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
8661 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
8662 prototype is working, and it is ready for a larger audience. To test
8663 it, fetch the
8664 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
8665 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
8666 package. You might have to log out and in again activate the
8667 autostart script.&lt;/p&gt;
8668
8669 &lt;p&gt;The design is simple:&lt;/p&gt;
8670
8671 &lt;ul&gt;
8672
8673 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
8674 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8675
8676 &lt;li&gt;This program listen for kernel events about new hardware (directly
8677 from the kernel like udev does), not using HAL dbus events as I
8678 initially did.&lt;/li&gt;
8679
8680 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8681 the APT database, a database
8682 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8683 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8684
8685 &lt;li&gt;If a package is mapped to the hardware in question, the package
8686 isn&#39;t installed yet and this is the first time the hardware was
8687 plugged in, show a desktop notification suggesting to install the
8688 package or packages.&lt;/li&gt;
8689
8690 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8691 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8692
8693 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8694 package while showing progress information in a window.&lt;/li&gt;
8695
8696 &lt;/ul&gt;
8697
8698 &lt;p&gt;I still need to come up with a better name for the system. Here
8699 are some screen shots showing the prototype in action. First the
8700 notification, then the password request, and finally the request to
8701 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8702
8703 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8704 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8705 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8706 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8707 &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;
8708
8709 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8710 is already useful. The database of hardware to package mappings also
8711 need more work. It is currently compatible with the Ubuntu way of
8712 storing such information in the package control file, but could be
8713 changed to use other formats instead or in addition to the current
8714 method. I&#39;ve dropped the use of discover for this mapping, as the
8715 modalias approach is more flexible and easier to use on Linux as long
8716 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8717
8718 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8719 here is the command required to check out and build the source: Use
8720 &#39;&lt;tt&gt;svn checkout
8721 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8722 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8723 devscripts package.&lt;/p&gt;
8724
8725 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8726 renamed to Isenkram and the source moved from the Debian Edu
8727 subversion repository to a Debian collab-maint git repository. See
8728 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8729 instructions&lt;/a&gt; for details.&lt;/p&gt;
8730 </description>
8731 </item>
8732
8733 <item>
8734 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8735 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8736 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8737 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8738 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8739 suddenly in bed. With a quiet whimper, it went completely quiet and
8740 black. The power button was no longer able to turn it on. It was a
8741 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8742 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8743 Compaq I had before that. Now I need to find a replacement. To keep
8744 going during Christmas, I moved the one year old SSD disk to my old
8745 X40 where it fitted (only one I had left that could use it), but it is
8746 not a durable solution.
8747
8748 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8749 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8750
8751 &lt;ul&gt;
8752
8753 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8754 than A4).&lt;/li&gt;
8755 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8756 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8757 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8758 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8759 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8760 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8761 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8762 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8763 size).&lt;/li&gt;
8764 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8765 X.org packages.&lt;/li&gt;
8766 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8767 the time).
8768
8769 &lt;/ul&gt;
8770
8771 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8772 list. The reason is simply that the specifications on laptops the
8773 last 10-15 years have been sufficient for my needs, and I have to look
8774 at other features to choose my laptop. But are there still made as
8775 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8776 robust, and Thinkpads seem to be heading in the wrong direction since
8777 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8778 still be useful.&lt;/p&gt;
8779
8780 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8781 external keyboard? I&#39;ll have to check the
8782 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8783 well-supported laptops, or perhaps just buy one preinstalled from one
8784 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8785 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8786 </description>
8787 </item>
8788
8789 <item>
8790 <title>How to find a browser plugin supporting a given MIME type</title>
8791 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8792 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8793 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8794 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
8795 install to get support for a given MIME type. Thanks to
8796 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
8797 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
8798 Unfortunately, not very many packages provide the needed meta
8799 information, Anyway, here is a small script to look up all browser
8800 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
8801
8802 &lt;pre&gt;
8803 #!/usr/bin/python
8804 import sys
8805 import apt
8806 def pkgs_handling_mimetype(mimetype):
8807 cache = apt.Cache()
8808 cache.open(None)
8809 thepkgs = []
8810 for pkg in cache:
8811 version = pkg.candidate
8812 if version is None:
8813 version = pkg.installed
8814 if version is None:
8815 continue
8816 record = version.record
8817 if not record.has_key(&#39;Npp-MimeType&#39;):
8818 continue
8819 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
8820 for t in mime_types:
8821 t = t.rstrip().strip()
8822 if t == mimetype:
8823 thepkgs.append(pkg.name)
8824 return thepkgs
8825 mimetype = &quot;audio/ogg&quot;
8826 if 1 &lt; len(sys.argv):
8827 mimetype = sys.argv[1]
8828 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
8829 for pkg in pkgs_handling_mimetype(mimetype):
8830 print &quot; %s&quot; %pkg
8831 &lt;/pre&gt;
8832
8833 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
8834
8835 &lt;pre&gt;
8836 % ./apt-find-browserplug-for-mimetype
8837 Browser plugin packages supporting audio/ogg:
8838 gecko-mediaplayer
8839 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8840 Browser plugin packages supporting application/x-shockwave-flash:
8841 browser-plugin-gnash
8842 %
8843 &lt;/pre&gt;
8844
8845 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
8846 itself to query for plugins and propose to install the needed
8847 packages. It would be great if Debian supported such feature too. Is
8848 anyone working on adding it?&lt;/p&gt;
8849
8850 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
8851 request for icweasel support for this feature is
8852 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
8853 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
8854 of manpower and wish for a different design is the reason thus feature
8855 is not yet in iceweasel from Debian.&lt;/p&gt;
8856 </description>
8857 </item>
8858
8859 <item>
8860 <title>What is the most supported MIME type in Debian?</title>
8861 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
8862 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
8863 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
8864 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
8865 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
8866 proposal to make it possible for a Desktop application to propose to
8867 the user some package to install to gain support for a given MIME
8868 type, font, library etc. that is currently missing. With such
8869 mechanism in place, it would be possible for the desktop to
8870 automatically propose and install leocad if some LDraw file is
8871 downloaded by the browser.&lt;/p&gt;
8872
8873 &lt;p&gt;To get some idea about the current content of the archive, I decided
8874 to write a simple program to extract all .desktop files from the
8875 Debian archive and look up the claimed MIME support there. The result
8876 can be found on the
8877 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
8878 site&lt;/a&gt;. Using the collected information, it become possible to
8879 answer the question in the title. Here are the 20 most supported MIME
8880 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8881 The complete list is available from the link above.&lt;/p&gt;
8882
8883 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
8884
8885 &lt;pre&gt;
8886 count MIME type
8887 ----- -----------------------
8888 32 text/plain
8889 30 audio/mpeg
8890 29 image/png
8891 28 image/jpeg
8892 27 application/ogg
8893 26 audio/x-mp3
8894 25 image/tiff
8895 25 image/gif
8896 22 image/bmp
8897 22 audio/x-wav
8898 20 audio/x-flac
8899 19 audio/x-mpegurl
8900 18 video/x-ms-asf
8901 18 audio/x-musepack
8902 18 audio/x-mpeg
8903 18 application/x-ogg
8904 17 video/mpeg
8905 17 audio/x-scpls
8906 17 audio/ogg
8907 16 video/x-ms-wmv
8908 &lt;/pre&gt;
8909
8910 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
8911
8912 &lt;pre&gt;
8913 count MIME type
8914 ----- -----------------------
8915 33 text/plain
8916 32 image/png
8917 32 image/jpeg
8918 29 audio/mpeg
8919 27 image/gif
8920 26 image/tiff
8921 26 application/ogg
8922 25 audio/x-mp3
8923 22 image/bmp
8924 21 audio/x-wav
8925 19 audio/x-mpegurl
8926 19 audio/x-mpeg
8927 18 video/mpeg
8928 18 audio/x-scpls
8929 18 audio/x-flac
8930 18 application/x-ogg
8931 17 video/x-ms-asf
8932 17 text/html
8933 17 audio/x-musepack
8934 16 image/x-xbitmap
8935 &lt;/pre&gt;
8936
8937 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
8938
8939 &lt;pre&gt;
8940 count MIME type
8941 ----- -----------------------
8942 31 text/plain
8943 31 image/png
8944 31 image/jpeg
8945 29 audio/mpeg
8946 28 application/ogg
8947 27 image/gif
8948 26 image/tiff
8949 26 audio/x-mp3
8950 23 audio/x-wav
8951 22 image/bmp
8952 21 audio/x-flac
8953 20 audio/x-mpegurl
8954 19 audio/x-mpeg
8955 18 video/x-ms-asf
8956 18 video/mpeg
8957 18 audio/x-scpls
8958 18 application/x-ogg
8959 17 audio/x-musepack
8960 16 video/x-ms-wmv
8961 16 video/x-msvideo
8962 &lt;/pre&gt;
8963
8964 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
8965 information mentioned in DEP-11. I have not yet had time to look at
8966 it, but hope the PackageKit people in Debian are on top of these
8967 issues.&lt;/p&gt;
8968
8969 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
8970 discovering a typo in my script.&lt;/p&gt;
8971 </description>
8972 </item>
8973
8974 <item>
8975 <title>Using modalias info to find packages handling my hardware</title>
8976 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
8977 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
8978 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
8979 <description>&lt;p&gt;Yesterday, I wrote about the
8980 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
8981 values provided by the Linux kernel&lt;/a&gt; following my hope for
8982 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
8983 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
8984 modalias values attached to package names can be used to map packages
8985 to hardware. This allow the system to look up and suggest relevant
8986 packages when I plug in some new hardware into my machine, and replace
8987 discover and discover-data as the database used to map hardware to
8988 packages.&lt;/p&gt;
8989
8990 &lt;p&gt;I create a modaliases file with entries like the following,
8991 containing package name, kernel module name (if relevant, otherwise
8992 the package name) and globs matching the relevant hardware
8993 modalias.&lt;/p&gt;
8994
8995 &lt;p&gt;&lt;blockquote&gt;
8996 Package: package-name
8997 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
8998 &lt;/blockquote&gt;&lt;/p&gt;
8999
9000 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
9001 for a given modalias value using this file.&lt;/p&gt;
9002
9003 &lt;p&gt;An entry like this would suggest the video and picture application
9004 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
9005
9006 &lt;p&gt;&lt;blockquote&gt;
9007 Package: cheese
9008 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
9009 &lt;/blockquote&gt;&lt;/p&gt;
9010
9011 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
9012 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
9013
9014 &lt;p&gt;&lt;blockquote&gt;
9015 Package: pcmciautils
9016 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
9017 &lt;/blockquote&gt;&lt;/p&gt;
9018
9019 &lt;p&gt;An entry like this would suggest the package colorhug-client when
9020 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
9021
9022 &lt;p&gt;&lt;blockquote&gt;
9023 Package: colorhug-client
9024 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
9025 &lt;/blockquote&gt;&lt;/p&gt;
9026
9027 &lt;p&gt;I believe the format is compatible with the format of the Packages
9028 file in the Debian archive. Ubuntu already uses their Packages file
9029 to store their mappings from packages to hardware.&lt;/p&gt;
9030
9031 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
9032 announce the hardware it support in a way my prototype understand.
9033 This allow those publishing packages in an APT source outside the
9034 Debian archive as well as those backporting packages to make sure the
9035 hardware mapping are included in the package meta information. I&#39;ve
9036 tested such header in the pymissile package, and its modalias mapping
9037 is working as it should with my prototype. It even made it to Ubuntu
9038 Raring.&lt;/p&gt;
9039
9040 &lt;p&gt;To test if it was possible to look up supported hardware using only
9041 the shell tools available in the Debian installer, I wrote a shell
9042 implementation of the lookup code. The idea is to create files for
9043 each modalias and let the shell do the matching. Please check out and
9044 try the
9045 &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;
9046 shell script. It run without any extra dependencies and fetch the
9047 hardware mappings from the Debian archive and the subversion
9048 repository where I currently work on my prototype.&lt;/p&gt;
9049
9050 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
9051 install yubikey-personalization:&lt;/p&gt;
9052
9053 &lt;p&gt;&lt;blockquote&gt;
9054 % ./hw-support-lookup
9055 &lt;br&gt;yubikey-personalization
9056 &lt;br&gt;%
9057 &lt;/blockquote&gt;&lt;/p&gt;
9058
9059 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
9060 propose to install the pcmciautils package:&lt;/p&gt;
9061
9062 &lt;p&gt;&lt;blockquote&gt;
9063 % ./hw-support-lookup
9064 &lt;br&gt;pcmciautils
9065 &lt;br&gt;%
9066 &lt;/blockquote&gt;&lt;/p&gt;
9067
9068 &lt;p&gt;If you know of any hardware-package mapping that should be added to
9069 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
9070 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
9071
9072 &lt;p&gt;It could be possible to generate several of the mappings between
9073 packages and hardware. One source would be to look at packages with
9074 kernel modules, ie packages with *.ko files in /lib/modules/, and
9075 extract their modalias information. Another would be to look at
9076 packages with udev rules, ie packages with files in
9077 /lib/udev/rules.d/, and extract their vendor/model information to
9078 generate a modalias matching rule. I have not tested any of these to
9079 see if it work.&lt;/p&gt;
9080
9081 &lt;p&gt;If you want to help implementing a system to let us propose what
9082 packages to install when new hardware is plugged into a Debian
9083 machine, please send me an email or talk to me on
9084 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9085 </description>
9086 </item>
9087
9088 <item>
9089 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
9090 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
9091 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
9092 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
9093 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
9094 information, to find the packages that support a given piece of
9095 hardware, I refreshed my memory regarding modalias values, and decided
9096 to document the details. Here are my findings so far, also available
9097 in
9098 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9099 Debian Edu subversion repository&lt;/a&gt;:
9100
9101 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
9102
9103 &lt;p&gt;This document try to explain what the different types of modalias
9104 values stands for. It is in part based on information from
9105 &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;,
9106 &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;,
9107 &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
9108 &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;.
9109
9110 &lt;p&gt;The modalias entries for a given Linux machine can be found using
9111 this shell script:&lt;/p&gt;
9112
9113 &lt;pre&gt;
9114 find /sys -name modalias -print0 | xargs -0 cat | sort -u
9115 &lt;/pre&gt;
9116
9117 &lt;p&gt;The supported modalias globs for a given kernel module can be found
9118 using modinfo:&lt;/p&gt;
9119
9120 &lt;pre&gt;
9121 % /sbin/modinfo psmouse | grep alias:
9122 alias: serio:ty05pr*id*ex*
9123 alias: serio:ty01pr*id*ex*
9124 %
9125 &lt;/pre&gt;
9126
9127 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
9128
9129 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
9130 Bridge memory controller:&lt;/p&gt;
9131
9132 &lt;p&gt;&lt;blockquote&gt;
9133 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9134 &lt;/blockquote&gt;&lt;/p&gt;
9135
9136 &lt;p&gt;This represent these values:&lt;/p&gt;
9137
9138 &lt;pre&gt;
9139 v 00008086 (vendor)
9140 d 00002770 (device)
9141 sv 00001028 (subvendor)
9142 sd 000001AD (subdevice)
9143 bc 06 (bus class)
9144 sc 00 (bus subclass)
9145 i 00 (interface)
9146 &lt;/pre&gt;
9147
9148 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
9149 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
9150 0600. The 0600 class is a host bridge. Other useful bus values are
9151 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
9152
9153 &lt;p&gt;Not sure how to figure out the interface value, nor what it
9154 means.&lt;/p&gt;
9155
9156 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
9157
9158 &lt;p&gt;Some typical USB entries can look like this. This is an internal
9159 USB hub in a laptop:&lt;/p&gt;
9160
9161 &lt;p&gt;&lt;blockquote&gt;
9162 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9163 &lt;/blockquote&gt;&lt;/p&gt;
9164
9165 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
9166
9167 &lt;pre&gt;
9168 v 1D6B (device vendor)
9169 p 0001 (device product)
9170 d 0206 (bcddevice)
9171 dc 09 (device class)
9172 dsc 00 (device subclass)
9173 dp 00 (device protocol)
9174 ic 09 (interface class)
9175 isc 00 (interface subclass)
9176 ip 00 (interface protocol)
9177 &lt;/pre&gt;
9178
9179 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
9180 class is in the interface class section. For a simple USB web camera,
9181 these alias entries show up:&lt;/p&gt;
9182
9183 &lt;p&gt;&lt;blockquote&gt;
9184 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9185 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9186 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9187 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9188 &lt;/blockquote&gt;&lt;/p&gt;
9189
9190 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
9191 camera), 0101 is audio control device and 0102 is audio streaming (aka
9192 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
9193
9194 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
9195
9196 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
9197 receiver in a Thinkpad X40:&lt;/p&gt;
9198
9199 &lt;p&gt;&lt;blockquote&gt;
9200 acpi:IBM0071:PNP0511:
9201 &lt;/blockquote&gt;&lt;/p&gt;
9202
9203 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
9204
9205 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
9206
9207 &lt;p&gt;The DMI table contain lots of information about the computer case
9208 and model. This is an entry for a IBM Thinkpad X40, fetched from
9209 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
9210
9211 &lt;p&gt;&lt;blockquote&gt;
9212 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9213 &lt;/blockquote&gt;&lt;/p&gt;
9214
9215 &lt;p&gt;The values present are&lt;/p&gt;
9216
9217 &lt;pre&gt;
9218 bvn IBM (BIOS vendor)
9219 bvr 1UETB6WW(1.66) (BIOS version)
9220 bd 06/15/2005 (BIOS date)
9221 svn IBM (system vendor)
9222 pn 2371H4G (product name)
9223 pvr ThinkPadX40 (product version)
9224 rvn IBM (board vendor)
9225 rn 2371H4G (board name)
9226 rvr NotAvailable (board version)
9227 cvn IBM (chassis vendor)
9228 ct 10 (chassis type)
9229 cvr NotAvailable (chassis version)
9230 &lt;/pre&gt;
9231
9232 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
9233 found in the dmidecode source:&lt;/p&gt;
9234
9235 &lt;pre&gt;
9236 3 Desktop
9237 4 Low Profile Desktop
9238 5 Pizza Box
9239 6 Mini Tower
9240 7 Tower
9241 8 Portable
9242 9 Laptop
9243 10 Notebook
9244 11 Hand Held
9245 12 Docking Station
9246 13 All In One
9247 14 Sub Notebook
9248 15 Space-saving
9249 16 Lunch Box
9250 17 Main Server Chassis
9251 18 Expansion Chassis
9252 19 Sub Chassis
9253 20 Bus Expansion Chassis
9254 21 Peripheral Chassis
9255 22 RAID Chassis
9256 23 Rack Mount Chassis
9257 24 Sealed-case PC
9258 25 Multi-system
9259 26 CompactPCI
9260 27 AdvancedTCA
9261 28 Blade
9262 29 Blade Enclosing
9263 &lt;/pre&gt;
9264
9265 &lt;p&gt;The chassis type values are not always accurately set in the DMI
9266 table. For example my home server is a tower, but the DMI modalias
9267 claim it is a desktop.&lt;/p&gt;
9268
9269 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
9270
9271 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
9272 test machine:&lt;/p&gt;
9273
9274 &lt;p&gt;&lt;blockquote&gt;
9275 serio:ty01pr00id00ex00
9276 &lt;/blockquote&gt;&lt;/p&gt;
9277
9278 &lt;p&gt;The values present are&lt;/p&gt;
9279
9280 &lt;pre&gt;
9281 ty 01 (type)
9282 pr 00 (prototype)
9283 id 00 (id)
9284 ex 00 (extra)
9285 &lt;/pre&gt;
9286
9287 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
9288 the valid values are.&lt;/p&gt;
9289
9290 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
9291
9292 &lt;p&gt;There are heaps of other modalias subtypes according to
9293 file2alias.c. There is the rest of the list from that source: amba,
9294 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9295 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9296 vmbus, x86cpu and zorro. I did not spend time documenting all of
9297 these, as they do not seem relevant for my intended use with mapping
9298 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
9299
9300 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
9301
9302 &lt;p&gt;To check which kernel modules provide support for a given modalias,
9303 one can use the following shell script:&lt;/p&gt;
9304
9305 &lt;pre&gt;
9306 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
9307 echo &quot;$id&quot; ; \
9308 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
9309 done
9310 &lt;/pre&gt;
9311
9312 &lt;p&gt;The output can look like this (only the first few entries as the
9313 list is very long on my test machine):&lt;/p&gt;
9314
9315 &lt;pre&gt;
9316 acpi:ACPI0003:
9317 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
9318 acpi:device:
9319 FATAL: Module acpi:device: not found.
9320 acpi:IBM0068:
9321 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
9322 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
9323 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
9324 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9325 acpi:IBM0071:PNP0511:
9326 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
9327 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
9328 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
9329 [...]
9330 &lt;/pre&gt;
9331
9332 &lt;p&gt;If you want to help implementing a system to let us propose what
9333 packages to install when new hardware is plugged into a Debian
9334 machine, please send me an email or talk to me on
9335 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9336
9337 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
9338 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
9339 in /sys/ with space in them.&lt;/p&gt;
9340 </description>
9341 </item>
9342
9343 <item>
9344 <title>Moved the pymissile Debian packaging to collab-maint</title>
9345 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
9346 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
9347 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
9348 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
9349 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9350 Launcher and updated the Debian package
9351 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
9352 sure udev will fix the device permissions when it is plugged in. I
9353 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
9354 hopefully make the package be proposed by jockey in Ubuntu when a user
9355 plug in his rocket launcher. In the process I moved the source to a
9356 git repository under collab-maint, to make it easier for any DD to
9357 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
9358 is not very active, but the software still work for me even after five
9359 years of relative silence. The new git repository is not listed in
9360 the uploaded package yet, because I want to test the other changes a
9361 bit more before I upload the new version. If you want to check out
9362 the new version with a .desktop file included, visit the
9363 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
9364 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
9365 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
9366 </description>
9367 </item>
9368
9369 <item>
9370 <title>Lets make hardware dongles easier to use in Debian</title>
9371 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
9372 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
9373 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
9374 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
9375 general, is that there is a great package management system with the
9376 ability to automatically install software packages by downloading them
9377 from the distribution mirrors, but no way to get it to automatically
9378 install the packages I need to use the hardware I plug into my
9379 machine. Even if the package to use it is easily available from the
9380 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9381 suggest to automatically install the python-nxt, nbc and t2n packages
9382 I need to talk to it. When I plug in a Yubikey, it could propose the
9383 yubikey-personalization package. The information required to do this
9384 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
9385
9386 &lt;p&gt;Some years ago, I proposed to
9387 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
9388 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
9389 simple:
9390
9391 &lt;ul&gt;
9392
9393 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
9394 starting when a user log in.&lt;/li&gt;
9395
9396 &lt;li&gt;Set this program up to listen for kernel events emitted when new
9397 hardware is inserted into the computer.&lt;/li&gt;
9398
9399 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
9400 database mapping to packages, and take note of any non-installed
9401 packages.&lt;/li&gt;
9402
9403 &lt;li&gt;Show a message to the user proposing to install the discovered
9404 package, and make it easy to install it.&lt;/li&gt;
9405
9406 &lt;/ul&gt;
9407
9408 &lt;p&gt;I am not sure what the best way to implement this is, but my
9409 initial idea was to use dbus events to discover new hardware, the
9410 discover database to find packages and
9411 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
9412 packages.&lt;/p&gt;
9413
9414 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
9415 draft package is now checked into
9416 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9417 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
9418 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
9419 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9420 the relevant packages in Debian, and uploaded a new version
9421 2.2013.01.09 to unstable. I also discovered that the current
9422 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
9423 package in Debian no longer discovered any USB devices, because
9424 /proc/bus/usb/devices is no longer present. I ported it to use
9425 libusb as a fall back option to get it working. The fixed package
9426 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
9427 because of the freeze).&lt;/p&gt;
9428
9429 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
9430 desktop notification to show up (only once, the first time it is
9431 inserted):&lt;/p&gt;
9432
9433 &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;
9434
9435 &lt;p&gt;For this prototype to be really useful, some way to automatically
9436 install the proposed packages by pressing the &quot;Please install
9437 program(s)&quot; button should to be implemented.&lt;/p&gt;
9438
9439 &lt;p&gt;If this idea seem useful to you, and you want to help make it
9440 happen, please help me update the discover-data database with mappings
9441 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
9442 list the package you would like to have installed when a given
9443 hardware device is inserted into your computer, and report bugs using
9444 reportbug if it isn&#39;t. Or, if you know of a better way to provide
9445 such mapping, please let me know.&lt;/p&gt;
9446
9447 &lt;p&gt;This prototype need more work, and there are several questions that
9448 should be considered before it is ready for production use. Is dbus
9449 the correct way to detect new hardware? At the moment I look for HAL
9450 dbus events on the system bus, because that is the events I could see
9451 on my Debian Squeeze KDE desktop. Are there better events to use?
9452 How should the user be notified? Is the desktop notification
9453 mechanism the best option, or should the background daemon raise a
9454 popup instead? How should packages be installed? When should they
9455 not be installed?&lt;/p&gt;
9456
9457 &lt;p&gt;If you want to help getting such feature implemented in Debian,
9458 please send me an email. :)&lt;/p&gt;
9459 </description>
9460 </item>
9461
9462 <item>
9463 <title>New IRC channel for LEGO designers using Debian</title>
9464 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
9465 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
9466 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
9467 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
9468 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
9469 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
9470 discovered I had to build all the tools myself because none were
9471 already in Debian Squeeze. If Debian support for LEGO is something
9472 you care about, please join me on the IRC channel
9473 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
9474 irc.debian.org). There is a lot that could be done to improve the
9475 Debian support for LEGO designers. For example both CAD software
9476 and Mindstorm compilers are missing. :)&lt;/p&gt;
9477
9478 &lt;p&gt;Update 2012-01-03: A
9479 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
9480 including links to Lego related packages is now available.&lt;/p&gt;
9481 </description>
9482 </item>
9483
9484 <item>
9485 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
9486 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
9487 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
9488 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
9489 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
9490 year! I hope next year will prove to be a good year.&lt;/p&gt;
9491
9492 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
9493 decentralised &quot;currency&quot; that allow people to transfer bitcoins
9494 between each other with minimal overhead, is a very interesting
9495 experiment. And as I wrote a few days ago, the bitcoin situation in
9496 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
9497 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
9498 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
9499 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
9500 for one of the ftpmasters to approve the new bitcoin-qt package
9501 name.&lt;/p&gt;
9502
9503 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
9504 team in Debian, you can easily test the package in Debian Squeeze
9505 using the following steps to get a set of working packages:&lt;/p&gt;
9506
9507 &lt;blockquote&gt;&lt;pre&gt;
9508 git clone git://git.debian.org/git/collab-maint/bitcoin
9509 cd bitcoin
9510 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9511 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9512 &lt;/pre&gt;&lt;/blockquote&gt;
9513
9514 &lt;p&gt;You might have to install some build dependencies as well. The
9515 list of commands should give you two packages, bitcoind and
9516 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9517 client will download the complete set of bitcoin &quot;blocks&quot;, which need
9518 around 5.6 GiB of data on my machine at the moment. Make sure your
9519 ~/.bitcoin/ directory have lots of spare room if you want to download
9520 all the blocks. The client will warn if the disk is getting full, so
9521 there is not really a problem if you got too little room, but you will
9522 not be able to get all the features out of the client.&lt;/p&gt;
9523
9524 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
9525 activities, please send Bitcoin donations to my address
9526 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9527 </description>
9528 </item>
9529
9530 <item>
9531 <title>A word on bitcoin support in Debian</title>
9532 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
9533 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
9534 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
9535 <description>&lt;p&gt;It has been a while since I wrote about
9536 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
9537 peer-to-peer based crypto-currency, and the reason is simply that I
9538 have been busy elsewhere. But two days ago, I started looking at the
9539 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
9540 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
9541 is now maintained by a
9542 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
9543 people&lt;/a&gt;, and the grunt work had already been done by this team. We
9544 owe a huge thank you to all these team members. :)
9545 But I was sad to discover that the bitcoin client is missing in
9546 Wheezy. It is only available in Sid (and an outdated client from
9547 backports). The client had several RC bugs registered in BTS blocking
9548 it from entering testing. To try to help the team and improve the
9549 situation, I spent some time providing patches and triaging the bug
9550 reports. I also had a look at the bitcoin package available from Matt
9551 Corallo in a
9552 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
9553 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
9554 Debian package.&lt;/p&gt;
9555
9556 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
9557 IRC, I pushed several patches into the collab-maint git repository to
9558 improve the package. It now contains fixes for the RC issues (not from
9559 me, but fixed by Scott Howard), build rules for a Qt GUI client
9560 package, konqueror support for the bitcoin: URI and bash completion
9561 setup. As I work on Debian Squeeze, I also created
9562 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
9563 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
9564 it and try to integrate it into the git repository before uploading a
9565 new version to unstable.
9566
9567 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
9568 centralized control currently exercised in the monetary system. I
9569 find it completely unacceptable that the USA government is collecting
9570 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9571 that the major credit card companies can block legal money
9572 transactions to Wikileaks. But for bitcoin to succeed, more people
9573 need to use bitcoins, and more people need to accept bitcoins when
9574 they sell products and services. Improving the bitcoin support in
9575 Debian is a small step in the right direction, but not enough.
9576 Unfortunately the user experience when browsing the web and wanting to
9577 pay with bitcoin is still not very good. The bitcoin: URI is a step
9578 in the right direction, but need to work in most or every browser in
9579 use. Also the bitcoin-qt client is too heavy to fire up to do a
9580 quick transaction. I believe there are other clients available, but
9581 have not tested them.&lt;/p&gt;
9582
9583 &lt;p&gt;My
9584 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
9585 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
9586 I received 20.15 BTC so far on the address I provided in my blog two
9587 years ago, as can be
9588 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
9589 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
9590 donation. The blockexplorer service demonstrates quite well that
9591 bitcoin is not quite anonymous and untracked. :) I wonder if the
9592 number of users have gone up since then. If you use bitcoin and want
9593 to show your support of my activity, please send Bitcoin donations to
9594 the same address as last time,
9595 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9596 </description>
9597 </item>
9598
9599 <item>
9600 <title>Git repository for song book for Computer Scientists</title>
9601 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
9602 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
9603 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
9604 <description>&lt;p&gt;As I
9605 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
9606 this summer&lt;/a&gt;, I have created a Computer Science song book a few
9607 years ago, and today I finally found time to create a public
9608 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
9609 repository for the project&lt;/a&gt;.&lt;/p&gt;
9610
9611 &lt;p&gt;If you want to help out, please clone the source and submit patches
9612 to the HTML version. To generate the PDF and PostScript version,
9613 please use prince XML, or let me know about a useful free software
9614 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
9615
9616 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
9617 PostScript formats at
9618 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
9619 Science Songbook&lt;/a&gt;.&lt;/p&gt;
9620 </description>
9621 </item>
9622
9623 <item>
9624 <title>Gratulerer med 19-årsdagen, Debian!</title>
9625 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
9626 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
9627 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
9628 <description>&lt;p&gt;I dag fyller
9629 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
9630 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
9631 si gratulerer med dagen, Debian!&lt;/p&gt;
9632 </description>
9633 </item>
9634
9635 <item>
9636 <title>Song book for Computer Scientists</title>
9637 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
9638 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
9639 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
9640 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
9641 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
9642 collecting computer related songs for use at parties. The original
9643 version was written in LaTeX, but a few years ago I got help from
9644 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9645 while keeping the ability to create a nice book in PDF format. I have
9646 not had time to maintain the book for a while now, and guess I should
9647 put it up on some public version control repository where others can
9648 help me extend and update the book. If anyone is volunteering to help
9649 me with this, send me an email. Also let me know if there are songs
9650 missing in my book.&lt;/p&gt;
9651
9652 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
9653 me today that I really should let all my readers share the joys of
9654 singing out load about programming, computers and computer networks.
9655 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
9656 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
9657 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
9658 Computer Science Songbook&lt;/a&gt;.
9659 </description>
9660 </item>
9661
9662 <item>
9663 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
9664 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
9665 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
9666 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
9667 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
9668 around 1000 at the moment. To be able to get help from the vendors
9669 when something go wrong, we want to keep the firmware on the servers
9670 up to date. If the firmware isn&#39;t the latest and greatest, the
9671 vendors typically refuse to start debugging any problems until the
9672 firmware is upgraded. So before every reboot, we want to upgrade the
9673 firmware, and we would really like everyone handling servers at the
9674 university to do this themselves when they plan to reboot a machine.
9675 For that to happen we at the unix server admin group need to provide
9676 the tools to do so.&lt;/p&gt;
9677
9678 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9679 fetch and install the latest firmware for the servers we got. Most of
9680 our hardware are from Dell and HP, so I have focused on these servers
9681 so far. This blog post is about the Dell part.&lt;/P&gt;
9682
9683 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9684 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9685 with firmware information for all 11th generation servers, listing
9686 which firmware should be used on a given model and where on the FTP
9687 site I can find it. Using a simple perl XML parser I can then
9688 download the shell scripts Dell provides to do firmware upgrades from
9689 within Linux and reboot when all the firmware is primed and ready to
9690 be activated on the first reboot.&lt;/p&gt;
9691
9692 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9693 Are there anyone working on similar tools for firmware upgrading all
9694 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9695
9696 &lt;p&gt;&lt;pre&gt;
9697 #!/usr/bin/perl
9698 use strict;
9699 use warnings;
9700 use File::Temp qw(tempdir);
9701 BEGIN {
9702 # Install needed RHEL packages if missing
9703 my %rhelmodules = (
9704 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9705 );
9706 for my $module (keys %rhelmodules) {
9707 eval &quot;use $module;&quot;;
9708 if ($@) {
9709 my $pkg = $rhelmodules{$module};
9710 system(&quot;yum install -y $pkg&quot;);
9711 eval &quot;use $module;&quot;;
9712 }
9713 }
9714 }
9715 my $errorsto = &#39;pere@hungry.com&#39;;
9716
9717 upgrade_dell();
9718
9719 exit 0;
9720
9721 sub run_firmware_script {
9722 my ($opts, $script) = @_;
9723 unless ($script) {
9724 print STDERR &quot;fail: missing script name\n&quot;;
9725 exit 1
9726 }
9727 print STDERR &quot;Running $script\n\n&quot;;
9728
9729 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9730 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9731 } else {
9732 print STDERR &quot;fail: firmware script returned error\n&quot;;
9733 }
9734 }
9735
9736 sub run_firmware_scripts {
9737 my ($opts, @dirs) = @_;
9738 # Run firmware packages
9739 for my $dir (@dirs) {
9740 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9741 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9742 while (my $s = readdir $dh) {
9743 next if $s =~ m/^\.\.?/;
9744 run_firmware_script($opts, &quot;$dir/$s&quot;);
9745 }
9746 closedir $dh;
9747 }
9748 }
9749
9750 sub download {
9751 my $url = shift;
9752 print STDERR &quot;info: Downloading $url\n&quot;;
9753 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9754 }
9755
9756 sub upgrade_dell {
9757 my @dirs;
9758 my $product = `dmidecode -s system-product-name`;
9759 chomp $product;
9760
9761 if ($product =~ m/PowerEdge/) {
9762
9763 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9764 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9765
9766 my $tmpdir = tempdir(
9767 CLEANUP =&gt; 1
9768 );
9769 chdir($tmpdir);
9770 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9771 system(&#39;gunzip Catalog.xml.gz&#39;);
9772 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9773 # -q is quiet, disabling interactivity and reducing console output
9774 my $fwopts = &quot;-q&quot;;
9775 if (@paths) {
9776 for my $url (@paths) {
9777 fetch_dell_fw($url);
9778 }
9779 run_firmware_scripts($fwopts, $tmpdir);
9780 } else {
9781 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9782 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9783 }
9784 chdir(&#39;/&#39;);
9785 } else {
9786 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9787 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9788 }
9789 }
9790
9791 sub fetch_dell_fw {
9792 my $path = shift;
9793 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9794 download($url);
9795 }
9796
9797 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9798 # firmware packages to download from Dell. Only work for Linux
9799 # machines and 11th generation Dell servers.
9800 sub fetch_dell_fw_list {
9801 my $filename = shift;
9802
9803 my $product = `dmidecode -s system-product-name`;
9804 chomp $product;
9805 my ($mybrand, $mymodel) = split(/\s+/, $product);
9806
9807 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
9808
9809 my $xml = XMLin($filename);
9810 my @paths;
9811 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
9812 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
9813 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
9814 my $oscode;
9815 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
9816 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
9817 } else {
9818 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
9819 }
9820 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
9821 {
9822 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
9823 }
9824 }
9825 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
9826 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
9827
9828 # Drop application packages, only firmware and BIOS
9829 next if &#39;APAC&#39; eq $componenttype;
9830
9831 my $cpath = $component-&gt;{path};
9832 for my $path (@paths) {
9833 if ($cpath =~ m%/$path$%) {
9834 push(@paths, $cpath);
9835 }
9836 }
9837 }
9838 return @paths;
9839 }
9840 &lt;/pre&gt;
9841
9842 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
9843 it could work on other platforms with some tweaking. Anyone know a
9844 index like Catalog.xml is available from HP for HP servers? At the
9845 moment I maintain a similar list manually and it is quickly getting
9846 outdated.&lt;/p&gt;
9847 </description>
9848 </item>
9849
9850 <item>
9851 <title>How is booting into runlevel 1 different from single user boots?</title>
9852 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
9853 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
9854 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
9855 <description>&lt;p&gt;Wouter Verhelst have some
9856 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
9857 comments and opinions&lt;/a&gt; on my blog post on
9858 &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
9859 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
9860 &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
9861 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
9862 small piece of his comment now, and though it best to address the
9863 misunderstanding he bring forward:&lt;/p&gt;
9864
9865 &lt;p&gt;&lt;blockquote&gt;
9866 Currently, a system admin has four options: [...] boot to a
9867 single-user system (by adding &#39;single&#39; to the kernel command line;
9868 this runs rcS and rc1 scripts)
9869 &lt;/blockquote&gt;&lt;/p&gt;
9870
9871 &lt;p&gt;This make me believe Wouter believe booting into single user mode
9872 and booting into runlevel 1 is the same. I am not surprised he
9873 believe this, because it would make sense and is a quite sensible
9874 thing to believe. But because the boot in Debian is slightly broken,
9875 runlevel 1 do not work properly and it isn&#39;t the same as single user
9876 mode. I&#39;ll try to explain what is actually happing, but it is a bit
9877 hard to explain.&lt;/p&gt;
9878
9879 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
9880 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
9881 executed in single user mode is sulogin. Single user mode is a boot
9882 state &quot;between&quot; the runlevels, and when booting into single user mode,
9883 only the scripts in /etc/rcS.d/ are executed before the init process
9884 enters the single user state. When switching to runlevel 1, the state
9885 is in fact not ending in runlevel 1, but it passes through runlevel 1
9886 and end up in the single user mode (see /etc/rc1.d/S03single, which
9887 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
9888 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
9889 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9890 mode).&lt;/p&gt;
9891
9892 &lt;p&gt;This summary might make it clearer. When booting for the first
9893 time into single user mode, the following commands are executed:
9894 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
9895 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
9896 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
9897 trying to continue after visiting single user mode. Not all services
9898 are started again as they should, causing the machine to end up in an
9899 unpredicatble state. This is why Debian admins recommend rebooting
9900 after visiting single user mode.&lt;/p&gt;
9901
9902 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
9903 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
9904 to runlevel 1, the services started from /etc/rcS.d/ are not properly
9905 stopped when passing through the scripts in /etc/rc1.d/, and not
9906 started again when switching away from runlevel 1 to the runlevels
9907 2-5. I believe the problem is best fixed by moving all the scripts
9908 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
9909 functioning single user mode during boot.&lt;/p&gt;
9910
9911 &lt;p&gt;I have spent several years investigating the Debian boot system,
9912 and discovered this problem a few years ago. I suspect it originates
9913 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
9914 </description>
9915 </item>
9916
9917 <item>
9918 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
9919 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
9920 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
9921 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
9922 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
9923 are started from /etc/rcS.d/. In fact, there is a bite more of them
9924 than make sense, and this causes a few problems. What kind of
9925 problems, you might ask. There are at least two problems. The first
9926 is that it is not possible to recover a machine after switching to
9927 runlevel 1. One need to actually reboot to get the machine back to
9928 the expected state. The other is that single user boot will sometimes
9929 run into problems because some of the subsystems are activated before
9930 the root login is presented, causing problems when trying to recover a
9931 machine from a problem in that subsystem. A minor additional point is
9932 that moving more scripts out of rcS.d/ and into the other rc#.d/
9933 directories will increase the amount of scripts that can run in
9934 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
9935
9936 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
9937 scripts that _have_ to execute before the root login prompt is
9938 presented during a single user boot should go there. Everything else
9939 should go into the numeric runlevels. This means things like
9940 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9941 the numeric runlevels. Today in Debian, there are around 115 init.d
9942 scripts that are started from rcS.d/, and most of them should be moved
9943 out. Do your package have one of them? Please help us make single
9944 user and runlevel 1 better by moving it.&lt;/p&gt;
9945
9946 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
9947 etc. should still be started from rcS.d/, but there is for example no
9948 need to have the network enabled before the single user login prompt
9949 is presented.&lt;/p&gt;
9950
9951 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
9952 Debian systems working while scripts migrate and during upgrades, the
9953 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9954 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9955 and the next ones can only be moved when their dependencies have been
9956 moved first. This migration must be done sequentially while we ensure
9957 that the package system upgrade packages in the right order to keep
9958 the system state correct. This will require some coordination when it
9959 comes to network related packages, but most of the packages with
9960 scripts that should migrate do not have anything in rcS.d/ depending
9961 on them. Some packages have already been updated, like the sudo
9962 package, while others are still left to do. I wish I had time to work
9963 on this myself, but real live constrains make it unlikely that I will
9964 find time to push this forward.&lt;/p&gt;
9965 </description>
9966 </item>
9967
9968 <item>
9969 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
9970 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
9971 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
9972 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
9973 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
9974 mentioned the issues I believe should be improved in Debian for its
9975 desktop to be useful for more people. The use case for this is my
9976 parents, which are currently running Kubuntu which solve the
9977 issues.&lt;/p&gt;
9978
9979 &lt;p&gt;I suspect these four missing features are not very hard to
9980 implement. After all, they are present in Ubuntu, so if we wanted to
9981 do this in Debian we would have a source.&lt;/p&gt;
9982
9983 &lt;ol&gt;
9984
9985 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
9986 are new packages available for upgrades, a icon in the KDE status bar
9987 indicate this, and clicking on it will activate the simple upgrade
9988 tool to handle it. I have no problem guiding both of my parents
9989 through the process over the phone. If a kernel reboot is required,
9990 this too is indicated by the status bars and the upgrade tool. Last
9991 time I checked, nothing with the same features was working in KDE in
9992 Debian.&lt;/li&gt;
9993
9994 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
9995 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
9996 currently have a handler for, it will ask the user if the system
9997 should search for a package that would add support for this MIME type,
9998 and if the user say yes, the APT sources will be searched for packages
9999 advertising the MIME type in their control file (visible in the
10000 Packages file in the APT archive). If one or more packages are found,
10001 it is a simple click of the mouse to add support for the missing mime
10002 type. If the package require the user to accept some non-free
10003 license, this is explained to the user. The entire process make it
10004 more clear to the user why something do not work in the browser, and
10005 make the chances higher for the user to blame the web page authors and
10006 not the browser for any missing features.&lt;/li&gt;
10007
10008 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
10009 handlers.&lt;/strong&gt; When the media players encounter a format or codec
10010 it is not supporting, a dialog pop up asking the user if the system
10011 should search for a package that would add support for it. This
10012 happen with things like MP3, Windows Media or H.264. The selection
10013 and installation procedure is very similar to the Firefox browser
10014 plugin handling. This is as far as I know implemented using a
10015 gstreamer hook. The end result is that the user easily get access to
10016 the codecs that are present from the APT archives available, while
10017 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
10018
10019 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
10020 displaying a text/plain file in my Debian browser, it will propose to
10021 start emacs to show it. If I remember correctly, when doing the same
10022 in Kunbutu it show the file as a text file in the browser. At least I
10023 know Opera will show text files within the browser. I much prefer the
10024 latter behaviour.&lt;/li&gt;
10025
10026 &lt;/ol&gt;
10027
10028 &lt;p&gt;There are other nice features as well, like the simplified suite
10029 upgrader, but given that I am the one mostly doing the dist-upgrade,
10030 it do not matter much.&lt;/p&gt;
10031
10032 &lt;p&gt;I really hope we could get these features in place for the next
10033 Debian release. It would require the coordinated effort of several
10034 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
10035 </description>
10036 </item>
10037
10038 <item>
10039 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
10040 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
10041 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
10042 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
10043 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
10044 site is build on Debian/Squeeze, and this platform was chosen because
10045 I am most familiar with Debian (being a Debian Developer for around 10
10046 years) because it is the latest stable Debian release which should get
10047 security support for a few years.&lt;/p&gt;
10048
10049 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
10050 that are missing in Debian at the moment. It would be great if these
10051 modules were added to the Debian archive, allowing anyone to set up
10052 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
10053 in their own country using only Debian packages. The list of modules
10054 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
10055 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
10056 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
10057 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
10058 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
10059 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
10060 easier in the future.&lt;/p&gt;
10061
10062 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
10063 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
10064 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
10065 with the responsibility of tracking security problems, which I really
10066 do not have time for.&lt;/p&gt;
10067 </description>
10068 </item>
10069
10070 <item>
10071 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
10072 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
10073 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
10074 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
10075 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
10076 posts have been in Norwegian the last few weeks, so here is a short
10077 update in English.&lt;/p&gt;
10078
10079 &lt;p&gt;The kids still keep me too busy to get much free software work
10080 done, but I did manage to organise a project to get a Norwegian port
10081 of the British service
10082 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
10083 and it has been running for a month now. The entire project has been
10084 organised by me and two others. Around Christmas we gathered sponsors
10085 to fund the development work. In January I drafted a contract with
10086 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
10087 and in February the development took place. Most of it involved
10088 converting the source to use GPS coordinates instead of British
10089 easting/northing, and the resulting code should be a lot easier to get
10090 running in any country by now. The Norwegian
10091 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
10092 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
10093 source and the source for administrative borders in Norway, and
10094 support for this had to be added/fixed.&lt;/p&gt;
10095
10096 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
10097 polishing the system before we announced it March 7th. The system is
10098 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
10099 problem reports in a few weeks. Soon we hope to announce the Android
10100 and iPhone versions making it even easier to report problems with the
10101 public infrastructure.&lt;/p&gt;
10102
10103 &lt;p&gt;Perhaps something to consider for those of you in countries without
10104 such service?&lt;/p&gt;
10105 </description>
10106 </item>
10107
10108 <item>
10109 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
10110 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
10111 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
10112 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
10113 <description>&lt;p&gt;The last few days I have looked at ways to track open security
10114 issues here at my work with the University of Oslo. My idea is that
10115 it should be possible to use the information about security issues
10116 available on the Internet, and check our locally
10117 maintained/distributed software against this information. It should
10118 allow us to verify that no known security issues are forgotten. The
10119 CVE database listing vulnerabilities seem like a great central point,
10120 and by using the package lists from Debian mapped to CVEs provided by
10121 the testing security team, I believed it should be possible to figure
10122 out which security holes were present in our free software
10123 collection.&lt;/p&gt;
10124
10125 &lt;p&gt;After reading up on the topic, it became obvious that the first
10126 building block is to be able to name software packages in a unique and
10127 consistent way across data sources. I considered several ways to do
10128 this, for example coming up with my own naming scheme like using URLs
10129 to project home pages or URLs to the Freshmeat entries, or using some
10130 existing naming scheme. And it seem like I am not the first one to
10131 come across this problem, as MITRE already proposed and implemented a
10132 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
10133 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
10134 software, hardware and other platform components. The CPE ids are
10135 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
10136 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
10137 issues for any CPE name. With this in place, all I need to do is to
10138 locate the CPE id for the software packages we use at the university.
10139 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
10140 NVD entry if a CVE for the package exist).&lt;/p&gt;
10141
10142 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
10143 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
10144 check out, one could look up
10145 &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
10146 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
10147 The most recent one is
10148 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
10149 and at the bottom of the NVD page for this vulnerability the complete
10150 list of affected versions is provided.&lt;/p&gt;
10151
10152 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
10153 for offline processing of issues. Using this dump, I&#39;ve written a
10154 small script taking a list of CPEs as input and list all CVEs
10155 affecting the packages represented by these CPEs. One give it CPEs
10156 with version numbers as specified above and get a list of open
10157 security issues out.&lt;/p&gt;
10158
10159 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
10160 information need to be high. For that to happen, I believe as many as
10161 possible need to use and contribute to the NVD database. I notice
10162 RHEL is providing
10163 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
10164 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
10165 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
10166
10167 &lt;p&gt;To get an idea about the quality for free software, I spent some
10168 time making it possible to compare the CVE database from Debian with
10169 the CVE database in NVD. The result look fairly good, but there are
10170 some inconsistencies in NVD (same software package having several
10171 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10172 Debian believe are affected by a CVE). Hope to find time to improve
10173 the quality of NVD, but that require being able to get in touch with
10174 someone maintaining it. So far my three emails with questions and
10175 corrections have not seen any reply, but I hope contact can be
10176 established soon.&lt;/p&gt;
10177
10178 &lt;p&gt;An interesting application for CPEs is cross platform package
10179 mapping. It would be useful to know which packages in for example
10180 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10181 this would be trivial if all linux distributions provided CPE entries
10182 for their packages.&lt;/p&gt;
10183 </description>
10184 </item>
10185
10186 <item>
10187 <title>Which module is loaded for a given PCI and USB device?</title>
10188 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
10189 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
10190 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
10191 <description>&lt;p&gt;In the
10192 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
10193 package in Debian, there is a script to report useful information
10194 about the running hardware for use when people report missing
10195 information. One part of this script that I find very useful when
10196 debugging hardware problems, is the part mapping loaded kernel module
10197 to the PCI device it claims. It allow me to quickly see if the kernel
10198 module I expect is driving the hardware I am struggling with. To see
10199 the output, make sure discover-data is installed and run
10200 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
10201 one of my machines like this:&lt;/p&gt;
10202
10203 &lt;pre&gt;
10204 loaded modules:
10205 10de:03eb i2c_nforce2
10206 10de:03f1 ohci_hcd
10207 10de:03f2 ehci_hcd
10208 10de:03f0 snd_hda_intel
10209 10de:03ec pata_amd
10210 10de:03f6 sata_nv
10211 1022:1103 k8temp
10212 109e:036e bttv
10213 109e:0878 snd_bt87x
10214 11ab:4364 sky2
10215 &lt;/pre&gt;
10216
10217 &lt;p&gt;The code in question look like this, slightly modified for
10218 readability and to drop the output to file descriptor 3:&lt;/p&gt;
10219
10220 &lt;pre&gt;
10221 if [ -d /sys/bus/pci/devices/ ] ; then
10222 echo loaded pci modules:
10223 (
10224 cd /sys/bus/pci/devices/
10225 for address in * ; do
10226 if [ -d &quot;$address/driver/module&quot; ] ; then
10227 module=`cd $address/driver/module ; pwd -P | xargs basename`
10228 if grep -q &quot;^$module &quot; /proc/modules ; then
10229 address=$(echo $address |sed s/0000://)
10230 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
10231 echo &quot;$id $module&quot;
10232 fi
10233 fi
10234 done
10235 )
10236 echo
10237 fi
10238 &lt;/pre&gt;
10239
10240 &lt;p&gt;Similar code could be used to extract USB device module
10241 mappings:&lt;/p&gt;
10242
10243 &lt;pre&gt;
10244 if [ -d /sys/bus/usb/devices/ ] ; then
10245 echo loaded usb modules:
10246 (
10247 cd /sys/bus/usb/devices/
10248 for address in * ; do
10249 if [ -d &quot;$address/driver/module&quot; ] ; then
10250 module=`cd $address/driver/module ; pwd -P | xargs basename`
10251 if grep -q &quot;^$module &quot; /proc/modules ; then
10252 address=$(echo $address |sed s/0000://)
10253 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
10254 if [ &quot;$id&quot; ] ; then
10255 echo &quot;$id $module&quot;
10256 fi
10257 fi
10258 fi
10259 done
10260 )
10261 echo
10262 fi
10263 &lt;/pre&gt;
10264
10265 &lt;p&gt;This might perhaps be something to include in other tools as
10266 well.&lt;/p&gt;
10267 </description>
10268 </item>
10269
10270 <item>
10271 <title>How to test if a laptop is working with Linux</title>
10272 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
10273 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
10274 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
10275 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
10276 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
10277 batch of computers will work with Linux. Every year for the last few
10278 years the university have organised shared bid of a few thousand
10279 computers, and this year HP won the bid. Two different desktops and
10280 five different laptops are on the list this year. We in the UNIX
10281 group want to know which one of these computers work well with RHEL
10282 and Ubuntu, the two Linux distributions we currently handle at the
10283 university.&lt;/p&gt;
10284
10285 &lt;p&gt;My test method is simple, and I share it here to get feedback and
10286 perhaps inspire others to test hardware as well. To test, I PXE
10287 install the OS version of choice, and log in as my normal user and run
10288 a few applications and plug in selected pieces of hardware. When
10289 something fail, I make a note about this in the test matrix and move
10290 on. If I have some spare time I try to report the bug to the OS
10291 vendor, but as I only have the machines for a short time, I rarely
10292 have the time to do this for all the problems I find.&lt;/p&gt;
10293
10294 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
10295 I perform on a new model.&lt;/p&gt;
10296
10297 &lt;ul&gt;
10298
10299 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
10300 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10301 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
10302
10303 &lt;li&gt;Is X.org working? If the graphical login screen show up after
10304 installation, X.org is working.&lt;/li&gt;
10305
10306 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
10307 package mesa-utils on Ubuntu) and writing down the frames per second
10308 reported by the program.&lt;/li&gt;
10309
10310 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
10311 logging in, and if I can hear this the test is successful. If there
10312 are several audio exits on the machine, I try them all and check if
10313 the Gnome/KDE audio mixer can control where to send the sound. I
10314 normally test this by playing
10315 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
10316 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
10317
10318 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
10319 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
10320
10321 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
10322 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
10323
10324 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
10325 picture from the v4l device show up.&lt;/li&gt;
10326
10327 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10328 any bluetooth devices are discovered. In my office, I normally see a
10329 few.&lt;/li&gt;
10330
10331 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
10332 memory modules lying around, and stick them in and see if Gnome/KDE
10333 notice this.&lt;/li&gt;
10334
10335 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
10336 special button work, and if the laptop continue to work after
10337 resume.&lt;/li&gt;
10338
10339 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
10340 adjusting background light, switching on/off external video output,
10341 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10342 laptop to laptop, so I just write down which are working and which are
10343 not.&lt;/li&gt;
10344
10345 &lt;li&gt;Some laptops have smart card readers, finger print readers,
10346 acceleration sensors etc. I rarely test these, as I do not know how
10347 to quickly test if they are working or not, so I only document their
10348 existence.&lt;/li&gt;
10349
10350 &lt;/ul&gt;
10351
10352 &lt;p&gt;By now I suspect you are really curious what the test results are
10353 for the HP machines I am testing. I&#39;m not done yet, so I will report
10354 the test results later. For now I can report that HP 8100 Elite work
10355 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
10356 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
10357 can see, I have most machines left to test. One interesting
10358 observation is that Ubuntu Lucid has almost twice the frame rate than
10359 RHEL6 with glxgears. No idea why.&lt;/p&gt;
10360 </description>
10361 </item>
10362
10363 <item>
10364 <title>Some thoughts on BitCoins</title>
10365 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
10366 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
10367 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
10368 <description>&lt;p&gt;As I continue to explore
10369 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
10370 what properties the system have, and how it will be affected by laws
10371 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
10372
10373 &lt;p&gt;One interesting thing to note is that since the transactions are
10374 verified using a peer to peer network, all details about a transaction
10375 is known to everyone. This means that if a BitCoin address has been
10376 published like I did with mine in my initial post about BitCoin, it is
10377 possible for everyone to see how many BitCoins have been transfered to
10378 that address. There is even a web service to look at the details for
10379 all transactions. There I can see that my address
10380 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
10381 have received 16.06 Bitcoin, the
10382 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
10383 address of Simon Phipps have received 181.97 BitCoin and the address
10384 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
10385 of EFF have received 2447.38 BitCoins so far. Thank you to each and
10386 every one of you that donated bitcoins to support my activity. The
10387 fact that anyone can see how much money was transfered to a given
10388 address make it more obvious why the BitCoin community recommend to
10389 generate and hand out a new address for each transaction. I&#39;m told
10390 there is no way to track which addresses belong to a given person or
10391 organisation without the person or organisation revealing it
10392 themselves, as Simon, EFF and I have done.&lt;/p&gt;
10393
10394 &lt;p&gt;In Norway, and in most other countries, there are laws and
10395 regulations limiting how much money one can transfer across the border
10396 without declaring it. There are money laundering, tax and accounting
10397 laws and regulations I would expect to apply to the use of BitCoin.
10398 If the Skolelinux foundation
10399 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
10400 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
10401 normal bank transfers like EFF is doing, how should this be accounted?
10402 Given that it is impossible to know if money can cross the border or
10403 not, should everything or nothing be declared? What exchange rate
10404 should be used when calculating taxes? Would receivers have to pay
10405 income tax if the foundation were to pay Skolelinux contributors in
10406 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
10407
10408 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
10409 accepted by a lot of users. It must be possible to get easy access to
10410 the currency (as a wage or using currency exchanges), and it must be
10411 easy to spend it. At the moment BitCoin seem fairly easy to get
10412 access to, but there are very few places to spend it. I am not really
10413 a regular user of any of the vendor types currently accepting BitCoin,
10414 so I wonder when my kind of shop would start accepting BitCoins. I
10415 would like to buy electronics, travels and subway tickets, not herbs
10416 and books. :) The currency is young, and this will improve over time
10417 if it become popular, but I suspect regular banks will start to lobby
10418 to get BitCoin declared illegal if it become popular. I&#39;m sure they
10419 will claim it is helping fund terrorism and money laundering (which
10420 probably would be true, as is any currency in existence), but I
10421 believe the problems should be solved elsewhere and not by blaming
10422 currencies.&lt;/p&gt;
10423
10424 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
10425 CPU intensive process that depend on a bit of luck as well (as one is
10426 competing against all the other miners currently spending CPU cycles
10427 to see which one get the next lump of cash). The &quot;winner&quot; get 50
10428 BitCoin when this happen. Yesterday I came across the obvious way to
10429 join forces to increase ones changes of getting at least some coins,
10430 by coordinating the work on mining BitCoins across several machines
10431 and people, and sharing the result if one is lucky and get the 50
10432 BitCoins. Check out
10433 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
10434 if this sounds interesting. I have not had time to try to set up a
10435 machine to participate there yet, but have seen that running on ones
10436 own for a few days have not yield any BitCoins througth mining
10437 yet.&lt;/p&gt;
10438
10439 &lt;p&gt;Update 2010-12-15: Found an &lt;a
10440 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
10441 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
10442 it was interesting to read. The arguments presented seem to be
10443 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
10444 </description>
10445 </item>
10446
10447 <item>
10448 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
10449 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
10450 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
10451 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
10452 <description>&lt;p&gt;With this weeks lawless
10453 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
10454 attacks&lt;/a&gt; on Wikileak and
10455 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
10456 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
10457 not be trusted to handle money transactions.
10458 A blog post from
10459 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
10460 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
10461 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
10462 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
10463 some help from my friend to get it all running, and he even handed me
10464 some bitcoins to get started. I even donated a few bitcoins to Simon
10465 for helping me remember BitCoin.&lt;/p&gt;
10466
10467 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
10468 crypto-currency, decentralised and handled using peer-to-peer
10469 networks. It allows anonymous transactions and prohibits central
10470 control over the transactions, making it impossible for governments
10471 and companies alike to block donations and other transactions. The
10472 source is free software, and while the key dependency wxWidgets 2.9
10473 for the graphical user interface is missing in Debian, the command
10474 line client builds just fine. Hopefully Jonas
10475 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
10476 Debian&lt;/a&gt; soon.&lt;/p&gt;
10477
10478 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
10479 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
10480 bitcoins&lt;/a&gt; when selling services and goods, and there are even
10481 currency &quot;stock&quot; markets where the exchange rate is decided. There
10482 are not many users so far, but the concept seems promising. If you
10483 want to get started and lack a friend with any bitcoins to spare,
10484 you can even get
10485 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
10486 bitcoin at the time of writing). Use
10487 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
10488 on the current exchange rates.&lt;/p&gt;
10489
10490 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
10491 machines. If you want to support my activity, please send Bitcoin
10492 donations to the address
10493 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
10494 </description>
10495 </item>
10496
10497 <item>
10498 <title>Why isn&#39;t Debian Edu using VLC?</title>
10499 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
10500 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
10501 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
10502 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
10503 presented, and the winner among the multimedia player were VLC.
10504 Personally, I like VLC, and it is my player of choice when I first try
10505 to play a video file or stream. Only if VLC fail will I drag out
10506 gmplayer to see if it can do better. The reason is mostly the failure
10507 model and trust. When VLC fail, it normally pop up a error message
10508 reporting the problem. When mplayer fail, it normally segfault or
10509 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
10510
10511 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
10512 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10513 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
10514 plugin to play web videos seamlessly, and the VLC browser plugin is
10515 not very good. For example, it lack in-line control buttons, so there
10516 is no way for the user to pause the video. Also, when I
10517 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
10518 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
10519 failed on several video pages where mplayer based plugins worked. If
10520 the browser plugin for VLC was as good as the gecko-mediaplayer
10521 package (which uses mplayer), we would switch.&lt;/P&gt;
10522
10523 &lt;p&gt;While VLC is a good player, its user interface is slightly
10524 annoying. The most annoying feature is its inconsistent use of
10525 keyboard shortcuts. When the player is in full screen mode, its
10526 shortcuts are different from when it is playing the video in a window.
10527 For example, space only work as pause when in full screen mode. I
10528 wish it had consisten shortcuts and that space also would work when in
10529 window mode. Another nice shortcut in gmplayer is [enter] to restart
10530 the current video. It is very nice when playing short videos from the
10531 web and want to restart it when new people arrive to have a look at
10532 what is going on.&lt;/p&gt;
10533 </description>
10534 </item>
10535
10536 <item>
10537 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
10538 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
10539 <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>
10540 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
10541 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
10542 upgrade testing of the
10543 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10544 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
10545 This seem like a very good idea, so I adjusted by test scripts and
10546 can now present the updated result from today:&lt;/p&gt;
10547
10548 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10549
10550 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10551
10552 &lt;blockquote&gt;&lt;p&gt;
10553 apache2.2-bin
10554 aptdaemon
10555 baobab
10556 binfmt-support
10557 browser-plugin-gnash
10558 cheese-common
10559 cli-common
10560 cups-pk-helper
10561 dmz-cursor-theme
10562 empathy
10563 empathy-common
10564 freedesktop-sound-theme
10565 freeglut3
10566 gconf-defaults-service
10567 gdm-themes
10568 gedit-plugins
10569 geoclue
10570 geoclue-hostip
10571 geoclue-localnet
10572 geoclue-manual
10573 geoclue-yahoo
10574 gnash
10575 gnash-common
10576 gnome
10577 gnome-backgrounds
10578 gnome-cards-data
10579 gnome-codec-install
10580 gnome-core
10581 gnome-desktop-environment
10582 gnome-disk-utility
10583 gnome-screenshot
10584 gnome-search-tool
10585 gnome-session-canberra
10586 gnome-system-log
10587 gnome-themes-extras
10588 gnome-themes-more
10589 gnome-user-share
10590 gstreamer0.10-fluendo-mp3
10591 gstreamer0.10-tools
10592 gtk2-engines
10593 gtk2-engines-pixbuf
10594 gtk2-engines-smooth
10595 hamster-applet
10596 libapache2-mod-dnssd
10597 libapr1
10598 libaprutil1
10599 libaprutil1-dbd-sqlite3
10600 libaprutil1-ldap
10601 libart2.0-cil
10602 libboost-date-time1.42.0
10603 libboost-python1.42.0
10604 libboost-thread1.42.0
10605 libchamplain-0.4-0
10606 libchamplain-gtk-0.4-0
10607 libcheese-gtk18
10608 libclutter-gtk-0.10-0
10609 libcryptui0
10610 libdiscid0
10611 libelf1
10612 libepc-1.0-2
10613 libepc-common
10614 libepc-ui-1.0-2
10615 libfreerdp-plugins-standard
10616 libfreerdp0
10617 libgconf2.0-cil
10618 libgdata-common
10619 libgdata7
10620 libgdu-gtk0
10621 libgee2
10622 libgeoclue0
10623 libgexiv2-0
10624 libgif4
10625 libglade2.0-cil
10626 libglib2.0-cil
10627 libgmime2.4-cil
10628 libgnome-vfs2.0-cil
10629 libgnome2.24-cil
10630 libgnomepanel2.24-cil
10631 libgpod-common
10632 libgpod4
10633 libgtk2.0-cil
10634 libgtkglext1
10635 libgtksourceview2.0-common
10636 libmono-addins-gui0.2-cil
10637 libmono-addins0.2-cil
10638 libmono-cairo2.0-cil
10639 libmono-corlib2.0-cil
10640 libmono-i18n-west2.0-cil
10641 libmono-posix2.0-cil
10642 libmono-security2.0-cil
10643 libmono-sharpzip2.84-cil
10644 libmono-system2.0-cil
10645 libmtp8
10646 libmusicbrainz3-6
10647 libndesk-dbus-glib1.0-cil
10648 libndesk-dbus1.0-cil
10649 libopal3.6.8
10650 libpolkit-gtk-1-0
10651 libpt2.6.7
10652 libpython2.6
10653 librpm1
10654 librpmio1
10655 libsdl1.2debian
10656 libsrtp0
10657 libssh-4
10658 libtelepathy-farsight0
10659 libtelepathy-glib0
10660 libtidy-0.99-0
10661 media-player-info
10662 mesa-utils
10663 mono-2.0-gac
10664 mono-gac
10665 mono-runtime
10666 nautilus-sendto
10667 nautilus-sendto-empathy
10668 p7zip-full
10669 pkg-config
10670 python-aptdaemon
10671 python-aptdaemon-gtk
10672 python-axiom
10673 python-beautifulsoup
10674 python-bugbuddy
10675 python-clientform
10676 python-coherence
10677 python-configobj
10678 python-crypto
10679 python-cupshelpers
10680 python-elementtree
10681 python-epsilon
10682 python-evolution
10683 python-feedparser
10684 python-gdata
10685 python-gdbm
10686 python-gst0.10
10687 python-gtkglext1
10688 python-gtksourceview2
10689 python-httplib2
10690 python-louie
10691 python-mako
10692 python-markupsafe
10693 python-mechanize
10694 python-nevow
10695 python-notify
10696 python-opengl
10697 python-openssl
10698 python-pam
10699 python-pkg-resources
10700 python-pyasn1
10701 python-pysqlite2
10702 python-rdflib
10703 python-serial
10704 python-tagpy
10705 python-twisted-bin
10706 python-twisted-conch
10707 python-twisted-core
10708 python-twisted-web
10709 python-utidylib
10710 python-webkit
10711 python-xdg
10712 python-zope.interface
10713 remmina
10714 remmina-plugin-data
10715 remmina-plugin-rdp
10716 remmina-plugin-vnc
10717 rhythmbox-plugin-cdrecorder
10718 rhythmbox-plugins
10719 rpm-common
10720 rpm2cpio
10721 seahorse-plugins
10722 shotwell
10723 software-center
10724 system-config-printer-udev
10725 telepathy-gabble
10726 telepathy-mission-control-5
10727 telepathy-salut
10728 tomboy
10729 totem
10730 totem-coherence
10731 totem-mozilla
10732 totem-plugins
10733 transmission-common
10734 xdg-user-dirs
10735 xdg-user-dirs-gtk
10736 xserver-xephyr
10737 &lt;/p&gt;&lt;/blockquote&gt;
10738
10739 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10740
10741 &lt;blockquote&gt;&lt;p&gt;
10742 cheese
10743 ekiga
10744 eog
10745 epiphany-extensions
10746 evolution-exchange
10747 fast-user-switch-applet
10748 file-roller
10749 gcalctool
10750 gconf-editor
10751 gdm
10752 gedit
10753 gedit-common
10754 gnome-games
10755 gnome-games-data
10756 gnome-nettool
10757 gnome-system-tools
10758 gnome-themes
10759 gnuchess
10760 gucharmap
10761 guile-1.8-libs
10762 libavahi-ui0
10763 libdmx1
10764 libgalago3
10765 libgtk-vnc-1.0-0
10766 libgtksourceview2.0-0
10767 liblircclient0
10768 libsdl1.2debian-alsa
10769 libspeexdsp1
10770 libsvga1
10771 rhythmbox
10772 seahorse
10773 sound-juicer
10774 system-config-printer
10775 totem-common
10776 transmission-gtk
10777 vinagre
10778 vino
10779 &lt;/p&gt;&lt;/blockquote&gt;
10780
10781 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10782
10783 &lt;blockquote&gt;&lt;p&gt;
10784 gstreamer0.10-gnomevfs
10785 &lt;/p&gt;&lt;/blockquote&gt;
10786
10787 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10788
10789 &lt;blockquote&gt;&lt;p&gt;
10790 [nothing]
10791 &lt;/p&gt;&lt;/blockquote&gt;
10792
10793 &lt;p&gt;This is for KDE:&lt;/p&gt;
10794
10795 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10796
10797 &lt;blockquote&gt;&lt;p&gt;
10798 ksmserver
10799 &lt;/p&gt;&lt;/blockquote&gt;
10800
10801 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10802
10803 &lt;blockquote&gt;&lt;p&gt;
10804 kwin
10805 network-manager-kde
10806 &lt;/p&gt;&lt;/blockquote&gt;
10807
10808 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10809
10810 &lt;blockquote&gt;&lt;p&gt;
10811 arts
10812 dolphin
10813 freespacenotifier
10814 google-gadgets-gst
10815 google-gadgets-xul
10816 kappfinder
10817 kcalc
10818 kcharselect
10819 kde-core
10820 kde-plasma-desktop
10821 kde-standard
10822 kde-window-manager
10823 kdeartwork
10824 kdeartwork-emoticons
10825 kdeartwork-style
10826 kdeartwork-theme-icon
10827 kdebase
10828 kdebase-apps
10829 kdebase-workspace
10830 kdebase-workspace-bin
10831 kdebase-workspace-data
10832 kdeeject
10833 kdelibs
10834 kdeplasma-addons
10835 kdeutils
10836 kdewallpapers
10837 kdf
10838 kfloppy
10839 kgpg
10840 khelpcenter4
10841 kinfocenter
10842 konq-plugins-l10n
10843 konqueror-nsplugins
10844 kscreensaver
10845 kscreensaver-xsavers
10846 ktimer
10847 kwrite
10848 libgle3
10849 libkde4-ruby1.8
10850 libkonq5
10851 libkonq5-templates
10852 libnetpbm10
10853 libplasma-ruby
10854 libplasma-ruby1.8
10855 libqt4-ruby1.8
10856 marble-data
10857 marble-plugins
10858 netpbm
10859 nuvola-icon-theme
10860 plasma-dataengines-workspace
10861 plasma-desktop
10862 plasma-desktopthemes-artwork
10863 plasma-runners-addons
10864 plasma-scriptengine-googlegadgets
10865 plasma-scriptengine-python
10866 plasma-scriptengine-qedje
10867 plasma-scriptengine-ruby
10868 plasma-scriptengine-webkit
10869 plasma-scriptengines
10870 plasma-wallpapers-addons
10871 plasma-widget-folderview
10872 plasma-widget-networkmanagement
10873 ruby
10874 sweeper
10875 update-notifier-kde
10876 xscreensaver-data-extra
10877 xscreensaver-gl
10878 xscreensaver-gl-extra
10879 xscreensaver-screensaver-bsod
10880 &lt;/p&gt;&lt;/blockquote&gt;
10881
10882 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10883
10884 &lt;blockquote&gt;&lt;p&gt;
10885 ark
10886 google-gadgets-common
10887 google-gadgets-qt
10888 htdig
10889 kate
10890 kdebase-bin
10891 kdebase-data
10892 kdepasswd
10893 kfind
10894 klipper
10895 konq-plugins
10896 konqueror
10897 ksysguard
10898 ksysguardd
10899 libarchive1
10900 libcln6
10901 libeet1
10902 libeina-svn-06
10903 libggadget-1.0-0b
10904 libggadget-qt-1.0-0b
10905 libgps19
10906 libkdecorations4
10907 libkephal4
10908 libkonq4
10909 libkonqsidebarplugin4a
10910 libkscreensaver5
10911 libksgrd4
10912 libksignalplotter4
10913 libkunitconversion4
10914 libkwineffects1a
10915 libmarblewidget4
10916 libntrack-qt4-1
10917 libntrack0
10918 libplasma-geolocation-interface4
10919 libplasmaclock4a
10920 libplasmagenericshell4
10921 libprocesscore4a
10922 libprocessui4a
10923 libqalculate5
10924 libqedje0a
10925 libqtruby4shared2
10926 libqzion0a
10927 libruby1.8
10928 libscim8c2a
10929 libsmokekdecore4-3
10930 libsmokekdeui4-3
10931 libsmokekfile3
10932 libsmokekhtml3
10933 libsmokekio3
10934 libsmokeknewstuff2-3
10935 libsmokeknewstuff3-3
10936 libsmokekparts3
10937 libsmokektexteditor3
10938 libsmokekutils3
10939 libsmokenepomuk3
10940 libsmokephonon3
10941 libsmokeplasma3
10942 libsmokeqtcore4-3
10943 libsmokeqtdbus4-3
10944 libsmokeqtgui4-3
10945 libsmokeqtnetwork4-3
10946 libsmokeqtopengl4-3
10947 libsmokeqtscript4-3
10948 libsmokeqtsql4-3
10949 libsmokeqtsvg4-3
10950 libsmokeqttest4-3
10951 libsmokeqtuitools4-3
10952 libsmokeqtwebkit4-3
10953 libsmokeqtxml4-3
10954 libsmokesolid3
10955 libsmokesoprano3
10956 libtaskmanager4a
10957 libtidy-0.99-0
10958 libweather-ion4a
10959 libxklavier16
10960 libxxf86misc1
10961 okteta
10962 oxygencursors
10963 plasma-dataengines-addons
10964 plasma-scriptengine-superkaramba
10965 plasma-widget-lancelot
10966 plasma-widgets-addons
10967 plasma-widgets-workspace
10968 polkit-kde-1
10969 ruby1.8
10970 systemsettings
10971 update-notifier-common
10972 &lt;/p&gt;&lt;/blockquote&gt;
10973
10974 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
10975 aptitude a bit more similar, but there are still quite a lott of
10976 differences. I have no idea what packages should be installed after
10977 the upgrade, but hope those that do can have a look.&lt;/p&gt;
10978 </description>
10979 </item>
10980
10981 <item>
10982 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
10983 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
10984 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
10985 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
10986 <description>&lt;p&gt;Most of the computers in use by the
10987 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
10988 are virtual machines. And they have been Xen machines running on a
10989 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
10990 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
10991 bit harder that it could have been, because we set up the Xen virtual
10992 machines to get the virtual partitions from LVM, which as far as I
10993 know is not supported by KVM. So to migrate, we had to convert
10994 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
10995
10996 &lt;p&gt;I found
10997 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
10998 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
10999 migration. It uses qemu-img from the qemu package to make the disk
11000 image, parted to partition it, losetup and kpartx to present the disk
11001 image partions as devices, and dd to copy the data. I NFS mounted the
11002 new servers storage area on the old server to do the migration.&lt;/p&gt;
11003
11004 &lt;pre&gt;
11005 #!/bin/sh
11006
11007 # Based on
11008 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
11009
11010 set -e
11011 set -x
11012
11013 if [ -z &quot;$1&quot; ] ; then
11014 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
11015 exit 1
11016 else
11017 host=&quot;$1&quot;
11018 fi
11019
11020 if [ ! -e /dev/vg_data/$host-disk ] ; then
11021 echo &quot;error: unable to find LVM volume for $host&quot;
11022 exit 1
11023 fi
11024
11025 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
11026 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
11027 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
11028 totalsize=$(( ( $disksize + $swapsize ) ))
11029
11030 img=$host.img
11031 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
11032 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
11033
11034 parted $img mklabel msdos
11035 parted $img mkpart primary linux-swap 0 $disksize
11036 parted $img mkpart primary ext2 $disksize $totalsize
11037 parted $img set 1 boot on
11038
11039 modprobe dm-mod
11040 losetup /dev/loop0 $img
11041 kpartx -a /dev/loop0
11042
11043 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
11044 fsck.ext3 -f /dev/mapper/loop0p1 || true
11045 mkswap /dev/mapper/loop0p2
11046
11047 kpartx -d /dev/loop0
11048 losetup -d /dev/loop0
11049 &lt;/pre&gt;
11050
11051 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
11052 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
11053
11054 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
11055 the new disk image attached, installed grub-pc and linux-image-686 and
11056 set up grub to boot from the disk image. After this, the KVM machines
11057 seem to work just fine.&lt;/p&gt;
11058 </description>
11059 </item>
11060
11061 <item>
11062 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
11063 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
11064 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
11065 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
11066 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
11067 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
11068 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
11069 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
11070
11071 &lt;p&gt;I still do not know what a correct migration should look like, so I
11072 report any differences between apt and aptitude and hope someone else
11073 can see if anything should be changed.&lt;/p&gt;
11074
11075 &lt;p&gt;This is for Gnome:&lt;/p&gt;
11076
11077 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11078
11079 &lt;blockquote&gt;&lt;p&gt;
11080 apache2.2-bin aptdaemon at-spi baobab binfmt-support
11081 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
11082 dmz-cursor-theme empathy empathy-common finger
11083 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
11084 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11085 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11086 gnome-cards-data gnome-codec-install gnome-core
11087 gnome-desktop-environment gnome-disk-utility gnome-screenshot
11088 gnome-search-tool gnome-session-canberra gnome-spell
11089 gnome-system-log gnome-themes-extras gnome-themes-more
11090 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
11091 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
11092 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
11093 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
11094 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
11095 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
11096 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
11097 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
11098 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
11099 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
11100 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
11101 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
11102 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
11103 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
11104 libgtk2.0-cil libgtkglext1 libgtksourceview-common
11105 libgtksourceview2.0-common libmono-addins-gui0.2-cil
11106 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
11107 libmono-i18n-west2.0-cil libmono-posix2.0-cil
11108 libmono-security2.0-cil libmono-sharpzip2.84-cil
11109 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
11110 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
11111 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
11112 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
11113 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
11114 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
11115 libxalan2-java libxerces2-java media-player-info mesa-utils
11116 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
11117 nautilus-sendto-empathy openoffice.org-writer2latex
11118 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
11119 python-aptdaemon python-aptdaemon-gtk python-axiom
11120 python-beautifulsoup python-bugbuddy python-clientform
11121 python-coherence python-configobj python-crypto python-cupshelpers
11122 python-cupsutils python-eggtrayicon python-elementtree
11123 python-epsilon python-evolution python-feedparser python-gdata
11124 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11125 python-gtksourceview2 python-httplib2 python-louie python-mako
11126 python-markupsafe python-mechanize python-nevow python-notify
11127 python-opengl python-openssl python-pam python-pkg-resources
11128 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11129 python-tagpy python-twisted-bin python-twisted-conch
11130 python-twisted-core python-twisted-web python-utidylib python-webkit
11131 python-xdg python-zope.interface remmina remmina-plugin-data
11132 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11133 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11134 software-center svgalibg1 system-config-printer-udev
11135 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
11136 totem totem-coherence totem-mozilla totem-plugins
11137 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11138 zip
11139 &lt;/p&gt;&lt;/blockquote&gt;
11140
11141 Installed using apt-get, removed with aptitude
11142
11143 &lt;blockquote&gt;&lt;p&gt;
11144 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11145 epiphany-extensions epiphany-gecko evolution-exchange
11146 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11147 gedit-common gnome-app-install gnome-games gnome-games-data
11148 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11149 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11150 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11151 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
11152 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
11153 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
11154 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
11155 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11156 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11157 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11158 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
11159 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
11160 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11161 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11162 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11163 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11164 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
11165 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
11166 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
11167 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
11168 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
11169 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11170 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11171 sound-juicer swfdec-gnome system-config-printer totem-common
11172 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11173 &lt;/p&gt;&lt;/blockquote&gt;
11174
11175 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11176
11177 &lt;blockquote&gt;&lt;p&gt;
11178 gstreamer0.10-gnomevfs
11179 &lt;/p&gt;&lt;/blockquote&gt;
11180
11181 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11182
11183 &lt;blockquote&gt;&lt;p&gt;
11184 [nothing]
11185 &lt;/p&gt;&lt;/blockquote&gt;
11186
11187 &lt;p&gt;This is for KDE:&lt;/p&gt;
11188
11189 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11190
11191 &lt;blockquote&gt;&lt;p&gt;
11192 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
11193 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11194 ghostscript-x git gnome-audio gnugo granatier gs-common
11195 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11196 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11197 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11198 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11199 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11200 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11201 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11202 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11203 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11204 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11205 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11206 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
11207 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11208 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11209 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11210 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11211 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11212 libkrossui4 libmailtools-perl libmime-tools-perl
11213 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11214 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11215 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11216 lirc luatex marble networkstatus noatun-plugins
11217 openoffice.org-writer2latex palapeli palapeli-data parley
11218 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11219 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11220 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11221 ttf-sazanami-gothic
11222 &lt;/p&gt;&lt;/blockquote&gt;
11223
11224 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11225
11226 &lt;blockquote&gt;&lt;p&gt;
11227 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11228 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11229 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11230 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11231 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11232 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11233 kitchensync kiten kjumpingcube klatin klettres klickety klines
11234 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11235 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11236 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11237 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11238 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11239 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11240 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11241 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11242 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11243 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
11244 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
11245 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11246 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
11247 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
11248 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11249 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11250 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11251 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11252 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11253 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11254 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
11255 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
11256 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11257 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11258 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11259 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11260 &lt;/p&gt;&lt;/blockquote&gt;
11261
11262 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11263
11264 &lt;blockquote&gt;&lt;p&gt;
11265 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11266 kdeartwork kdebase kdebase-apps kdebase-workspace
11267 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11268 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11269 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11270 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11271 xscreensaver-screensaver-bsod
11272 &lt;/p&gt;&lt;/blockquote&gt;
11273
11274 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11275
11276 &lt;blockquote&gt;&lt;p&gt;
11277 kdebase-bin konq-plugins konqueror
11278 &lt;/p&gt;&lt;/blockquote&gt;
11279 </description>
11280 </item>
11281
11282 <item>
11283 <title>Gnash buildbot slave and Debian kfreebsd</title>
11284 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
11285 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
11286 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
11287 <description>&lt;p&gt;Answering
11288 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
11289 call from the Gnash project&lt;/a&gt; for
11290 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
11291 current source, I have set up a virtual KVM machine on the Debian
11292 Edu/Skolelinux virtualization host to test the git source on
11293 Debian/Squeeze. I hope this can help the developers in getting new
11294 releases out more often.&lt;/p&gt;
11295
11296 &lt;p&gt;As the developers want less main-stream build platforms tested to,
11297 I have considered setting up a &lt;a
11298 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
11299 machine as well. I have also considered using the kfreebsd
11300 architecture in Debian as a file server in NUUG to get access to the 5
11301 TB zfs volume we currently use to store DV video. Because of this, I
11302 finally got around to do a test installation of Debian/Squeeze with
11303 kfreebsd. Installation went fairly smooth, thought I noticed some
11304 visual glitches in the cdebconf dialogs (black cursor left on the
11305 screen at random locations). Have not gotten very far with the
11306 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11307 fatal problem. Have to spend some more time on it to see if it is
11308 useful as a file server for NUUG. Will try to find time to set up a
11309 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
11310 </description>
11311 </item>
11312
11313 <item>
11314 <title>Debian in 3D</title>
11315 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
11316 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
11317 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
11318 <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;
11319
11320 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
11321 3D linked in from
11322 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
11323 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
11324 </description>
11325 </item>
11326
11327 <item>
11328 <title>Software updates 2010-10-24</title>
11329 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
11330 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
11331 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
11332 <description>&lt;p&gt;Some updates.&lt;/p&gt;
11333
11334 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
11335 raise money for the project is going well. The lower limit of 10
11336 signers was reached in 24 hours, and so far 13 people have signed it.
11337 More signers and more funding is most welcome, and I am really curious
11338 how far we can get before the time limit of December 24 is reached.
11339 :)&lt;/p&gt;
11340
11341 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
11342 about what appear to be a great code coverage tool capable of
11343 generating code coverage stats without any changes to the source code.
11344 It is called
11345 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
11346 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
11347 It is missing in Debian, but the git source built just fine in Squeeze
11348 after I installed libelf-dev, libdwarf-dev, pkg-config and
11349 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11350 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
11351
11352 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
11353 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
11354 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
11355 alpha test release of the Squeeze based Debian Edu /
11356 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
11357 release. Give it a try if you need a complete linux solution for your
11358 school, including central infrastructure server, workstations, thin
11359 client servers and diskless workstations. A nice touch added
11360 yesterday is RDP support on the thin client servers, for windows
11361 clients to get a Linux desktop on request.&lt;/p&gt;
11362 </description>
11363 </item>
11364
11365 <item>
11366 <title>Some notes on Flash in Debian and Debian Edu</title>
11367 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
11368 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
11369 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
11370 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
11371 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
11372 second most popular used package that is missing in Debian. The sixth
11373 most popular is flashplayer-mozilla. This is a clear indication that
11374 working flash is important for Debian users. Around 10 percent of the
11375 users submitting data to popcon.debian.org have this package
11376 installed.&lt;/p&gt;
11377
11378 &lt;p&gt;In the report written by Lars Risan in August 2008
11379&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
11380 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11381 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
11382 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
11383 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
11384 web sites require Flash to work, and lacking working Flash support in
11385 the web browser and the problems with installing it was perceived as a
11386 good reason to stay with Windows.&lt;/p&gt;
11387
11388 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
11389 said to be the retarded cousin that did not really understand
11390 everything you told him but could work fairly well. This was a
11391 comment regarding the problems Linux have with proprietary formats and
11392 non-standard web pages, and is sad because it exposes a fairly common
11393 understanding of whose fault it is if web pages that only work in for
11394 example Internet Explorer 6 fail to work on Firefox, and funny because
11395 it explain very well how annoying it is for users when Linux
11396 distributions do not work with the documents they receive or the web
11397 pages they want to visit.&lt;/p&gt;
11398
11399 &lt;p&gt;This is part of the reason why I believe it is important for Debian
11400 and Debian Edu to have a well working Flash implementation in the
11401 distribution, to get at least popular sites as Youtube and Google
11402 Video to working out of the box. For Squeeze, Debian have the chance
11403 to include the latest version of Gnash that will make this happen, as
11404 the new release 0.8.8 was published a few weeks ago and is resting in
11405 unstable. The new version work with more sites that version 0.8.7.
11406 The Gnash maintainers have asked for a freeze exception, but the
11407 release team have not had time to reply to it yet. I hope they agree
11408 with me that Flash is important for the Debian desktop users, and thus
11409 accept the new package into Squeeze.&lt;/p&gt;
11410 </description>
11411 </item>
11412
11413 <item>
11414 <title>Circular package dependencies harms apt recovery</title>
11415 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
11416 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
11417 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
11418 <description>&lt;p&gt;I discovered this while doing
11419 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
11420 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
11421 in Debian still got circular dependencies, and it is often claimed
11422 that apt and aptitude should be able to handle this just fine, but
11423 some times these dependency loops causes apt to fail.&lt;/p&gt;
11424
11425 &lt;p&gt;An example is from todays
11426 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
11427 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
11428 causes perl-modules to fail to upgrade. The cause is simple. If a
11429 package fail to unpack, then only part of packages with the circular
11430 dependency might end up being unpacked when unpacking aborts, and the
11431 ones already unpacked will fail to configure in the recovery phase
11432 because its dependencies are unavailable.&lt;/p&gt;
11433
11434 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
11435
11436 &lt;blockquote&gt;&lt;pre&gt;
11437 dpkg: dependency problems prevent configuration of perl-modules:
11438 perl-modules depends on perl (&gt;= 5.10.1-1); however:
11439 Version of perl on system is 5.10.0-19lenny2.
11440 dpkg: error processing perl-modules (--configure):
11441 dependency problems - leaving unconfigured
11442 &lt;/pre&gt;&lt;/blockquote&gt;
11443
11444 &lt;p&gt;The perl/perl-modules circular dependency is already
11445 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
11446 hopefully be solved as soon as possible, but it is not the only one,
11447 and each one of these loops in the dependency tree can cause similar
11448 failures. Of course, they only occur when there are bugs in other
11449 packages causing the unpacking to fail, but it is rather nasty when
11450 the failure of one package causes the problem to become worse because
11451 of dependency loops.&lt;/p&gt;
11452
11453 &lt;p&gt;Thanks to
11454 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
11455 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
11456 dependencies
11457 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
11458 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
11459
11460 &lt;p&gt;Todays testing also exposed a bug in
11461 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
11462 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
11463 apt-get and aptitude, the latter possibly caused by some circular
11464 dependency. Reported both to BTS to try to get someone to look at
11465 it.&lt;/p&gt;
11466 </description>
11467 </item>
11468
11469 <item>
11470 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
11471 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
11472 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
11473 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
11474 <description>&lt;p&gt;This is a
11475 &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;
11476 on my
11477 &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
11478 work&lt;/a&gt; on
11479 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
11480 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
11481
11482 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
11483 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11484 and dhcp3-server-ldap in Debian use the LDAP server. The two
11485 implementations are quite different in how they use LDAP.&lt;/p&gt;
11486
11487 To get this information, I started slapd with debugging enabled and
11488 dumped the debug output to a file to get the LDAP searches performed
11489 on a Debian Edu main-server. Here is a summary.
11490
11491 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
11492
11493 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
11494 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
11495 the web.
11496
11497 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
11498 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
11499 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
11500 reverse entries are in two different subtrees in LDAP with a structure
11501 based on the DNS names, as in tjener.intern and
11502 2.2.0.10.in-addr.arpa.&lt;/p&gt;
11503
11504 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
11505 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
11506 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
11507 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
11508 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
11509 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
11510 forward entries, it is looking for attributes named dnsttl, arecord,
11511 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11512 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11513 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11514 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11515 spfrecord and modifytimestamp. For reverse entries it is looking for
11516 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11517 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11518 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11519 ldapsearch commands could look like this:&lt;/p&gt;
11520
11521 &lt;blockquote&gt;&lt;pre&gt;
11522 ldapsearch -h ldap \
11523 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11524 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11525 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11526 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11527 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11528 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11529
11530 ldapsearch -h ldap \
11531 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11532 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
11533 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11534 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11535 srvrecord naptrrecord modifytimestamp
11536 &lt;/pre&gt;&lt;/blockquote&gt;
11537
11538 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
11539 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11540 example LDAP objects used there. In addition to these objects, the
11541 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11542 also exist.&lt;/p&gt;
11543
11544 &lt;blockquote&gt;&lt;pre&gt;
11545 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11546 objectclass: top
11547 objectclass: dnsdomain
11548 objectclass: domainrelatedobject
11549 dc: tjener
11550 arecord: 10.0.2.2
11551 associateddomain: tjener.intern
11552
11553 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11554 objectclass: top
11555 objectclass: dnsdomain2
11556 objectclass: domainrelatedobject
11557 dc: 2
11558 ptrrecord: tjener.intern
11559 associateddomain: 2.2.0.10.in-addr.arpa
11560 &lt;/pre&gt;&lt;/blockquote&gt;
11561
11562 &lt;p&gt;In strict mode, the server behaves differently. When looking for
11563 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
11564 same base as in the tree mode for a object with filter
11565 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
11566 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11567 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11568 naptrrecord and modifytimestamp. For reverse entires it also do a
11569 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
11570 and the requested attributes are associateddomain, dnsttl and
11571 modifytimestamp. In short, in strict mode the objects with ptrrecord
11572 go away, and the arecord attribute in the forward object is used
11573 instead.&lt;/p&gt;
11574
11575 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
11576 like this:&lt;/p&gt;
11577
11578 &lt;blockquote&gt;&lt;pre&gt;
11579 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11580 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11581 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11582 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11583 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11584 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11585
11586 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11587 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
11588 &lt;/pre&gt;&lt;/blockquote&gt;
11589
11590 &lt;p&gt;In addition to the forward and reverse searches , there is also a
11591 search for SOA records, which behave similar to the forward and
11592 reverse lookups.&lt;/p&gt;
11593
11594 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
11595 specify any objectclass names, and instead look for the attributes it
11596 need to generate a DNS reply. This make it able to work with any
11597 objectclass that provide the needed attributes.&lt;/p&gt;
11598
11599 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
11600 dnsdomain2 schemas. The latter is used for reverse entries like
11601 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
11602
11603 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
11604 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11605 attributes) and domainrelatedobject (for associatedDomain). The use
11606 of structural object classes make it impossible to combine these
11607 classes with the object classes used by DHCP.&lt;/p&gt;
11608
11609 &lt;p&gt;There are other schemas that could be used too, for example the
11610 dnszone structural object class used by Gosa and bind-sdb for the DNS
11611 attributes combined with the domainrelatedobject object class, but in
11612 this case some unused attributes would have to be included as well
11613 (zonename and relativedomainname).&lt;/p&gt;
11614
11615 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
11616 mode and not use any of the existing objectclasses (dnsdomain,
11617 dnsdomain2 and dnszone) when one want to combine the DNS information
11618 with DHCP information, and instead create a auxiliary object class
11619 defined something like this (using the attributes defined for
11620 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
11621
11622 &lt;blockquote&gt;&lt;pre&gt;
11623 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
11624 SUP top
11625 AUXILIARY
11626 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11627 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11628 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11629 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11630 A6Record $ DNAMERecord
11631 ))
11632 &lt;/pre&gt;&lt;/blockquote&gt;
11633
11634 &lt;p&gt;This will allow any object to become a DNS entry when combined with
11635 the domainrelatedobject object class, and allow any entity to include
11636 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
11637 developers asking for their view on this schema and if they are
11638 interested in providing such schema with PowerDNS, and I hope my
11639 message will be accepted into their mailing list soon.&lt;/p&gt;
11640
11641 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
11642
11643 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
11644 the object attributes, and then uses the attributes it want. This
11645 make it harder to figure out exactly what attributes are used, but
11646 thanks to the working example in Debian Edu I can at least get an idea
11647 what is needed without having to read the source code.&lt;/p&gt;
11648
11649 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
11650 search filter to use to locate the correct dhcpServer entity is
11651 stored. These are the relevant entries from
11652 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
11653
11654 &lt;blockquote&gt;&lt;pre&gt;
11655 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
11656 ldap-dhcp-server-cn &quot;dhcp&quot;;
11657 &lt;/pre&gt;&lt;/blockquote&gt;
11658
11659 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
11660 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
11661 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
11662 search result is this entry:&lt;/p&gt;
11663
11664 &lt;blockquote&gt;&lt;pre&gt;
11665 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11666 cn: dhcp
11667 objectClass: top
11668 objectClass: dhcpServer
11669 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11670 &lt;/pre&gt;&lt;/blockquote&gt;
11671
11672 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
11673 subtree with DHCP configuration. The DHCP configuration subtree base
11674 is located using a base scope search with base &quot;cn=DHCP
11675 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11676 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11677 The search result is this entry:&lt;/p&gt;
11678
11679 &lt;blockquote&gt;&lt;pre&gt;
11680 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11681 cn: DHCP Config
11682 objectClass: top
11683 objectClass: dhcpService
11684 objectClass: dhcpOptions
11685 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11686 dhcpStatements: ddns-update-style none
11687 dhcpStatements: authoritative
11688 dhcpOption: smtp-server code 69 = array of ip-address
11689 dhcpOption: www-server code 72 = array of ip-address
11690 dhcpOption: wpad-url code 252 = text
11691 &lt;/pre&gt;&lt;/blockquote&gt;
11692
11693 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11694 all the DHCP configuration is loaded, it is ready to receive requests.
11695 The subtree in Debian Edu contain objects with object classes
11696 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11697 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11698 and information about netmasks, dynamic range etc. Leaving out the
11699 details here because it is not relevant for the focus of my
11700 investigation, which is to see if it is possible to merge dns and dhcp
11701 related computer objects.&lt;/p&gt;
11702
11703 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11704 of the client (00:00:00:00:00:00 in this example), using a subtree
11705 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11706 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11707 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11708 like:&lt;/p&gt;
11709
11710 &lt;blockquote&gt;&lt;pre&gt;
11711 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11712 cn: hostname
11713 objectClass: top
11714 objectClass: dhcpHost
11715 dhcpHWAddress: ethernet 00:00:00:00:00:00
11716 dhcpStatements: fixed-address hostname
11717 &lt;/pre&gt;&lt;/blockquote&gt;
11718
11719 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11720 The object classes need to have fixed names, and the configuration
11721 need to be stored in a fairly specific LDAP structure. On the
11722 positive side, the invidiual dhcpHost entires can be anywhere without
11723 the DN pointed to by the dhcpServer entries. The latter should make
11724 it possible to group all host entries in a subtree next to the
11725 configuration entries, and this subtree can also be shared with the
11726 DNS server if the schema proposed above is combined with the dhcpHost
11727 structural object class.
11728
11729 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11730
11731 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11732 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11733 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11734 allowing DNS objects to be stored anywhere under the base cn specified
11735 in the configuration.&lt;/p&gt;
11736
11737 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11738 regarding which LDAP schemas to use and which LDAP structure to use.
11739 I guess one could implement ones own schema, as long as the
11740 objectclasses and attributes have the names used, but this do not
11741 really help when the DHCP subtree need to have a fairly fixed
11742 structure.&lt;/p&gt;
11743
11744 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11745 this might work for Debian Edu:&lt;/p&gt;
11746
11747 &lt;blockquote&gt;&lt;pre&gt;
11748 ou=services
11749 cn=machine-info (dhcpService) - dhcpServiceDN points here
11750 cn=dhcp (dhcpServer)
11751 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11752 cn=10.0.2.0 (dhcpSubnet)
11753 cn=group1 (dhcpGroup/dhcpOptions)
11754 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11755 cn=192.168.0.0 (dhcpSubnet)
11756 cn=group1 (dhcpGroup/dhcpOptions)
11757 ou=machines - PowerDNS base points here
11758 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11759 &lt;/pre&gt;&lt;/blockquote&gt;
11760
11761 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11762 entries to be in the dhcpGroup subtrees, the entries can be stored
11763 there instead of a common machines subtree, and the PowerDNS base
11764 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11765
11766 &lt;p&gt;The combined object under the machines subtree would look something
11767 like this:&lt;/p&gt;
11768
11769 &lt;blockquote&gt;&lt;pre&gt;
11770 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11771 dc: hostname
11772 objectClass: top
11773 objectClass: dhcpHost
11774 objectclass: domainrelatedobject
11775 objectclass: dnsDomainAux
11776 associateddomain: hostname.intern
11777 arecord: 10.11.12.13
11778 dhcpHWAddress: ethernet 00:00:00:00:00:00
11779 dhcpStatements: fixed-address hostname.intern
11780 &lt;/pre&gt;&lt;/blockquote&gt;
11781
11782 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11783 machine, as long as the required attributes are available in a
11784 auxiliary object class.&lt;/p&gt;
11785 </description>
11786 </item>
11787
11788 <item>
11789 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11790 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11791 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11792 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11793 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11794 DHCP services in Debian Edu to use the same LDAP objects for a given
11795 computer, to avoid the possibility of having a inconsistent state for
11796 a computer in LDAP (as in DHCP but no DNS entry or the other way
11797 around) and make it easier to add computers to LDAP.&lt;/p&gt;
11798
11799 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
11800 information finally found a solution that seem to work.&lt;/p&gt;
11801
11802 &lt;p&gt;The old setup required three LDAP objects for a given computer.
11803 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11804 we switch powerdns to use its strict LDAP method (ldap-method=strict
11805 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11806 merged into one while making it impossible to transfer the reverse map
11807 to a slave DNS server.&lt;/p&gt;
11808
11809 &lt;p&gt;If we also replace the object class used to get the DNS related
11810 attributes to one allowing these attributes to be combined with the
11811 dhcphost object class, we can merge the DNS and DHCP entries into one.
11812 I&#39;ve written such object class in the dnsdomainaux.schema file (need
11813 proper OIDs, but that is a minor issue), and tested the setup. It
11814 seem to work.&lt;/p&gt;
11815
11816 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
11817 for both DNS and DHCP, and even the LTSP configuration I suggested in
11818 an earlier email. The combined LDAP object will look something like
11819 this:&lt;/p&gt;
11820
11821 &lt;blockquote&gt;&lt;pre&gt;
11822 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11823 cn: hostname
11824 objectClass: dhcphost
11825 objectclass: domainrelatedobject
11826 objectclass: dnsdomainaux
11827 associateddomain: hostname.intern
11828 arecord: 10.11.12.13
11829 dhcphwaddress: ethernet 00:00:00:00:00:00
11830 dhcpstatements: fixed-address hostname
11831 ldapconfigsound: Y
11832 &lt;/pre&gt;&lt;/blockquote&gt;
11833
11834 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
11835 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11836 before asking DNS to resolve the fixed-adddress. LTSP will use
11837 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
11838
11839 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
11840 dhcphost in a different location, to allow us to put the objects
11841 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
11842 that. If I can&#39;t figure out a way to do that, we can still get rid of
11843 the hosts subtree and move all its content into the DHCP Config tree
11844 (which probably should be renamed to be more related to the new
11845 content. I suspect cn=dnsdhcp,ou=services or something like that
11846 might be a good place to put it.&lt;/p&gt;
11847
11848 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11849 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11850 </description>
11851 </item>
11852
11853 <item>
11854 <title>Idea for storing LTSP configuration in LDAP</title>
11855 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
11856 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
11857 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
11858 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
11859 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11860 clients, and that this can be used to fetch configuration from LDAP if
11861 Debian Edu choose to store configuration there.&lt;/p&gt;
11862
11863 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
11864 to get configuration from LDAP. The idea is to look up the MAC
11865 address of the client in LDAP, and look for attributes on the form
11866 ltspconfigsetting=value, and use this to export SETTING=value to the
11867 LTSP clients.&lt;/p&gt;
11868
11869 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
11870 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
11871 allowing us to store all information about a computer in one place.&lt;/p&gt;
11872
11873 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
11874 this approach. A real LDAP schema for the ltspClientAux objectclass
11875 need to be written. Comments, suggestions, etc?&lt;/p&gt;
11876
11877 &lt;blockquote&gt;&lt;pre&gt;
11878 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11879 #
11880 # Fetch LTSP client settings from LDAP based on MAC address
11881 #
11882 # Uses ethernet address as stored in the dhcpHost objectclass using
11883 # the dhcpHWAddress attribute or ethernet address stored in the
11884 # ieee802Device objectclass with the macAddress attribute.
11885 #
11886 # This module is written to be schema agnostic, and only depend on the
11887 # existence of attribute names.
11888 #
11889 # The LTSP configuration variables are saved directly using a
11890 # ltspConfig prefix and uppercasing the rest of the attribute name.
11891 # To set the SERVER variable, set the ltspConfigServer attribute.
11892 #
11893 # Some LDAP schema should be created with all the relevant
11894 # configuration settings. Something like this should work:
11895 #
11896 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
11897 # SUP top
11898 # AUXILIARY
11899 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11900
11901 LDAPSERVER=$(debian-edu-ldapserver)
11902 if [ &quot;$LDAPSERVER&quot; ] ; then
11903 LDAPBASE=$(debian-edu-ldapserver -b)
11904 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
11905 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
11906 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
11907 grep &#39;^ltspConfig&#39; | while read attr value ; do
11908 # Remove prefix and convert to upper case
11909 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
11910 # bass value on to clients
11911 eval &quot;$attr=$value; export $attr&quot;
11912 done
11913 done
11914 fi
11915 &lt;/pre&gt;&lt;/blockquote&gt;
11916
11917 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
11918 the while block might end up in a subshell causing the variables set
11919 there to not show up in ltsp-config, but if that is the case I am sure
11920 the code can be restructured to make sure the variables are passed on.
11921 I expect that can be solved with some testing. :)&lt;/p&gt;
11922
11923 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11924 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11925
11926 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
11927 configuration in LDAP that was created around year 2000 by
11928 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
11929 Xperience, Inc., 2000&lt;/a&gt;. I found its
11930 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
11931 personal home page over at redhat.com.&lt;/p&gt;
11932 </description>
11933 </item>
11934
11935 <item>
11936 <title>jXplorer, a very nice LDAP GUI</title>
11937 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
11938 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
11939 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
11940 <description>&lt;p&gt;Since
11941 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
11942 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
11943 LDAP GUI that is even better than luma. The java application
11944 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
11945 moving LDAP objects and subtrees using drag-and-drop, and can
11946 authenticate using Kerberos. I have only tested the Kerberos
11947 authentication, but do not have a LDAP setup allowing me to rewrite
11948 LDAP with my test user yet. It is
11949 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
11950 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
11951 have with it is how it handle errors. If something go wrong, its
11952 non-intuitive behaviour require me to go through some query work list
11953 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
11954 </description>
11955 </item>
11956
11957 <item>
11958 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
11959 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
11960 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
11961 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
11962 <description>&lt;p&gt;Here is a short update on my &lt;a
11963 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
11964 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
11965 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
11966 not reporting the status for KDE, because the upgrade crashes when
11967 aptitude try because of missing conflicts
11968 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
11969 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
11970
11971 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
11972 complete list of the installed packages. Based on this I see these
11973 differences when I did a test run today. As usual, I do not really
11974 know what the correct set of packages would be, but thought it best to
11975 publish the difference.&lt;/p&gt;
11976
11977 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11978
11979 &lt;blockquote&gt;&lt;p&gt;
11980 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
11981 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
11982 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11983 libgtksourceview-common libpt-1.10.10-plugins-alsa
11984 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11985 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11986 python-4suite-xml python-eggtrayicon python-gtkhtml2
11987 python-gtkmozembed svgalibg1 xserver-xephyr zip
11988 &lt;/p&gt;&lt;/blockquote&gt;
11989
11990 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11991
11992 &lt;blockquote&gt;&lt;p&gt;
11993 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11994 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11995 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
11996 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
11997 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
11998 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
11999 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
12000 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
12001 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
12002 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
12003 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
12004 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
12005 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
12006 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
12007 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
12008 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
12009 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
12010 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
12011 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
12012 mysql-common swfdec-gnome totem-gstreamer wodim
12013 &lt;/p&gt;&lt;/blockquote&gt;
12014
12015 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
12016
12017 &lt;blockquote&gt;&lt;p&gt;
12018 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
12019 python-gnomekeyring python-wnck rhythmbox-plugins xorg
12020 xserver-xorg-input-all xserver-xorg-input-evdev
12021 xserver-xorg-input-kbd xserver-xorg-input-mouse
12022 xserver-xorg-input-synaptics xserver-xorg-video-all
12023 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
12024 xserver-xorg-video-chips xserver-xorg-video-cirrus
12025 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12026 xserver-xorg-video-glint xserver-xorg-video-i128
12027 xserver-xorg-video-i740 xserver-xorg-video-mach64
12028 xserver-xorg-video-mga xserver-xorg-video-neomagic
12029 xserver-xorg-video-nouveau xserver-xorg-video-nv
12030 xserver-xorg-video-r128 xserver-xorg-video-radeon
12031 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
12032 xserver-xorg-video-s3 xserver-xorg-video-s3virge
12033 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
12034 xserver-xorg-video-sis xserver-xorg-video-sisusb
12035 xserver-xorg-video-tdfx xserver-xorg-video-tga
12036 xserver-xorg-video-trident xserver-xorg-video-tseng
12037 xserver-xorg-video-vesa xserver-xorg-video-vmware
12038 xserver-xorg-video-voodoo
12039 &lt;/p&gt;&lt;/blockquote&gt;
12040
12041 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
12042
12043 &lt;blockquote&gt;&lt;p&gt;
12044 deskbar-applet xserver-xorg xserver-xorg-core
12045 xserver-xorg-input-wacom xserver-xorg-video-intel
12046 xserver-xorg-video-openchrome
12047 &lt;/p&gt;&lt;/blockquote&gt;
12048
12049 &lt;p&gt;I was told on IRC that the xorg-xserver package was
12050 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
12051 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
12052 No idea when it hits Squeeze, but when it does I hope it will reduce
12053 the difference somewhat.
12054 </description>
12055 </item>
12056
12057 <item>
12058 <title>LUMA, a very nice LDAP GUI</title>
12059 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
12060 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
12061 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
12062 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
12063 directory in Debian Edu, and in the process I started to miss a GUI
12064 tool to browse the LDAP tree. The only one I was able to find in
12065 Debian/Squeeze and Lenny is
12066 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
12067 be a great tool to get a overview of the current LDAP directory
12068 populated by default in Skolelinux. Thanks to it, I have been able to
12069 find empty and obsolete subtrees, misplaced objects and duplicate
12070 objects. It will be installed by default in Debian/Squeeze. If you
12071 are working with LDAP, give it a go. :)&lt;/p&gt;
12072
12073 &lt;p&gt;I did notice one problem with it I have not had time to report to
12074 the BTS yet. There is no .desktop file in the package, so the tool do
12075 not show up in the Gnome and KDE menus, but only deep down in in the
12076 Debian submenu in KDE. I hope that can be fixed before Squeeze is
12077 released.&lt;/p&gt;
12078
12079 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
12080 like to move objects and remove subtrees directly in the GUI, but have
12081 not found a way to do that with LUMA yet. So in the mean time, I use
12082 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
12083
12084 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
12085 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12086
12087 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
12088 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
12089 useful GUI alternative. It seem like a good tool, but is unmaintained
12090 in Debian and got a RC bug keeping it out of Squeeze. Unless that
12091 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
12092 </description>
12093 </item>
12094
12095 <item>
12096 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
12097 <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>
12098 <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>
12099 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
12100 <description>&lt;p&gt;A while back, I
12101 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
12102 about the fact&lt;/a&gt; that it is not possible with the provided schemas
12103 for storing DNS and DHCP information in LDAP to combine the two sets
12104 of information into one LDAP object representing a computer.&lt;/p&gt;
12105
12106 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
12107 the dhcpHost object class auxiliary, to allow it to be combined with
12108 the dNSDomain object class, and thus forming one object for one
12109 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
12110
12111 &lt;p&gt;If I understand this correctly, it is not safe to do this change
12112 without also changing the assigned number for the object class, and I
12113 do not know enough about LDAP schema design to do that properly for
12114 Debian Edu.&lt;/p&gt;
12115
12116 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
12117 the
12118 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
12119 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
12120 available today from IETF.&lt;/p&gt;
12121
12122 &lt;pre&gt;
12123 --- dhcp.schema (revision 65192)
12124 +++ dhcp.schema (working copy)
12125 @@ -376,7 +376,7 @@
12126 objectclass ( 2.16.840.1.113719.1.203.6.6
12127 NAME &#39;dhcpHost&#39;
12128 DESC &#39;This represents information about a particular client&#39;
12129 - SUP top
12130 + SUP top AUXILIARY
12131 MUST cn
12132 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12133 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
12134 &lt;/pre&gt;
12135
12136 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
12137 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12138 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
12139
12140 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12141 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12142 </description>
12143 </item>
12144
12145 <item>
12146 <title>Calling tasksel like the installer, while still getting useful output</title>
12147 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
12148 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
12149 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
12150 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
12151 installs packages during the normal debian-installer run. Until now,
12152 I have ended up letting tasksel do the work, with the annoying problem
12153 of not getting any feedback at all when something fails (like a
12154 conffile question from dpkg or a download that fails), using code like
12155 this:
12156
12157 &lt;blockquote&gt;&lt;pre&gt;
12158 export DEBIAN_FRONTEND=noninteractive
12159 tasksel --new-install
12160 &lt;/pre&gt;&lt;/blockquote&gt;
12161
12162 This would invoke tasksel, let its automatic task selection pick the
12163 tasks to install, and continue to install the requested tasks without
12164 any output what so ever.
12165
12166 Recently I revisited this problem while working on the automatic
12167 package upgrade testing, because tasksel would some times hang without
12168 any useful feedback, and I want to see what is going on when it
12169 happen. Then it occured to me, I can parse the output from tasksel
12170 when asked to run in test mode, and use that aptitude command line
12171 printed by tasksel then to simulate the tasksel run. I ended up using
12172 code like this:
12173
12174 &lt;blockquote&gt;&lt;pre&gt;
12175 export DEBIAN_FRONTEND=noninteractive
12176 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
12177 $cmd
12178 &lt;/pre&gt;&lt;/blockquote&gt;
12179
12180 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
12181 --without-recommends -o APT::Install-Recommends=no -y install
12182 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12183 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
12184 laptop task and all packages with priority standard , required and
12185 important, just like tasksel would have done it during
12186 installation.&lt;/p&gt;
12187
12188 &lt;p&gt;A better approach is probably to extend tasksel to be able to
12189 install packages without using debconf-apt-progress, for use cases
12190 like this.&lt;/p&gt;
12191 </description>
12192 </item>
12193
12194 <item>
12195 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
12196 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
12197 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
12198 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
12199 <description>&lt;p&gt;My
12200 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
12201 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
12202 finally made the upgrade logs available from
12203 &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;.
12204 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12205 apt and aptitude, and found their differences interesting. This time
12206 I will only focus on their removal plans.&lt;/p&gt;
12207
12208 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
12209 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
12210 surprising part is that it want to remove xorg and all
12211 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12212 sure why. When asking aptitude to do the same, it want to remove 129
12213 packages, but most of them are library packages I suspect are no
12214 longer needed. Both of them want to remove bluetooth packages, which
12215 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
12216
12217 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
12218 which seem like a bad idea and xorg the same way as with Gnome. Asking
12219 aptitude for the same, it wants to remove 192 packages, none which are
12220 too surprising.&lt;/p&gt;
12221
12222 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
12223 and avoided, and perhaps others as well. Here are the complete list
12224 of planned removals. The complete logs is available from the URL
12225 above. Note if you want to repeat these tests, that the upgrade test
12226 for kde+apt-get hung in the tasksel setup because of dpkg asking
12227 conffile questions. No idea why. I worked around it by using
12228 &#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
12229 continue.&lt;/p&gt;
12230
12231 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
12232 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
12233 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12234 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
12235 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12236 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12237 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12238 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12239 xserver-xorg-input-kbd xserver-xorg-input-mouse
12240 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12241 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12242 xserver-xorg-video-ati xserver-xorg-video-chips
12243 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12244 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12245 xserver-xorg-video-glint xserver-xorg-video-i128
12246 xserver-xorg-video-i740 xserver-xorg-video-imstt
12247 xserver-xorg-video-intel xserver-xorg-video-mach64
12248 xserver-xorg-video-mga xserver-xorg-video-neomagic
12249 xserver-xorg-video-nsc xserver-xorg-video-nv
12250 xserver-xorg-video-openchrome xserver-xorg-video-r128
12251 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12252 xserver-xorg-video-rendition xserver-xorg-video-s3
12253 xserver-xorg-video-s3virge xserver-xorg-video-savage
12254 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12255 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12256 xserver-xorg-video-tga xserver-xorg-video-trident
12257 xserver-xorg-video-tseng xserver-xorg-video-v4l
12258 xserver-xorg-video-vesa xserver-xorg-video-vga
12259 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
12260 xulrunner-1.9-gnome-support&lt;/p&gt;
12261
12262 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
12263
12264 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
12265 djvulibre-desktop finger gnome-app-install gnome-mount
12266 gnome-network-admin gnome-spell gnome-vfs-obexftp
12267 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12268 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12269 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12270 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
12271 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
12272 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
12273 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
12274 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
12275 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
12276 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
12277 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
12278 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
12279 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12280 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
12281 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
12282 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
12283 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
12284 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
12285 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12286 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12287 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12288 openoffice.org-writer2latex openssl-blacklist p7zip
12289 python-4suite-xml python-eggtrayicon python-gnome2-desktop
12290 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12291 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12292 swfdec-mozilla totem-gstreamer update-manager wodim
12293 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12294 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12295 zip&lt;/p&gt;
12296
12297 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
12298
12299 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12300 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12301 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12302 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12303 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12304 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12305 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12306 xserver-xorg-input-kbd xserver-xorg-input-mouse
12307 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12308 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12309 xserver-xorg-video-ati xserver-xorg-video-chips
12310 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12311 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12312 xserver-xorg-video-glint xserver-xorg-video-i128
12313 xserver-xorg-video-i740 xserver-xorg-video-imstt
12314 xserver-xorg-video-intel xserver-xorg-video-mach64
12315 xserver-xorg-video-mga xserver-xorg-video-neomagic
12316 xserver-xorg-video-nsc xserver-xorg-video-nv
12317 xserver-xorg-video-openchrome xserver-xorg-video-r128
12318 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12319 xserver-xorg-video-rendition xserver-xorg-video-s3
12320 xserver-xorg-video-s3virge xserver-xorg-video-savage
12321 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12322 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12323 xserver-xorg-video-tga xserver-xorg-video-trident
12324 xserver-xorg-video-tseng xserver-xorg-video-v4l
12325 xserver-xorg-video-vesa xserver-xorg-video-vga
12326 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
12327
12328 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
12329 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
12330 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12331 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12332 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12333 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12334 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12335 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12336 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12337 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12338 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12339 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12340 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12341 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12342 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12343 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12344 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12345 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12346 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12347 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
12348 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12349 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12350 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
12351 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12352 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12353 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12354 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12355 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12356 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
12357 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
12358 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12359 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12360 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12361 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12362 texlive-common texlive-doc-base texlive-fonts-recommended
12363 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12364 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12365 xulrunner-1.9&lt;/p&gt;
12366
12367 </description>
12368 </item>
12369
12370 <item>
12371 <title>Automatic upgrade testing from Lenny to Squeeze</title>
12372 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
12373 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
12374 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
12375 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
12376 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12377 have been discovered and reported in the process
12378 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
12379 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
12380 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
12381 kdebase-workspace-data), and to get a more regular testing going on, I
12382 am working on a script to automate the test.&lt;/p&gt;
12383
12384 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
12385 Gnome or KDE desktop installation inside the chroot before upgrading
12386 it. To ensure no services are started in the chroot, a policy-rc.d
12387 script is inserted. To make sure tasksel believe it is to install a
12388 desktop on a laptop, the tasksel tests are replaced in the chroot
12389 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
12390
12391 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12392 currently always fail because udev refuses to upgrade with the kernel
12393 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12394 is created. The bug report
12395 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
12396 this problem do not trigger in a chroot, but I touch the file anyway
12397 to make sure the upgrade go well. Testing on virtual and real
12398 hardware have failed me because of udev so far, and creating this file
12399 do the trick in such settings anyway. This is a
12400 &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
12401 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
12402 maintainer because he lack the resources to rewrite udev to keep
12403 working with old kernels or something like that. I really wish the
12404 udev upstream would keep udev backwards compatible, to avoid such
12405 upgrade problem, but given that they fail to do so, I guess
12406 documenting the way out of this mess is the best option we got for
12407 Debian Squeeze.&lt;/p&gt;
12408
12409 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
12410 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
12411 trick:&lt;/p&gt;
12412
12413 &lt;blockquote&gt;&lt;pre&gt;
12414 #!/bin/sh
12415 set -ex
12416
12417 if [ &quot;$1&quot; ] ; then
12418 desktop=$1
12419 else
12420 desktop=gnome
12421 fi
12422
12423 from=lenny
12424 to=squeeze
12425
12426 exec &amp;lt; /dev/null
12427 unset LANG
12428 mirror=http://ftp.skolelinux.org/debian
12429 tmpdir=chroot-$from-upgrade-$to-$desktop
12430 fuser -mv .
12431 debootstrap $from $tmpdir $mirror
12432 chroot $tmpdir aptitude update
12433 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
12434 #!/bin/sh
12435 exit 101
12436 EOF
12437 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12438 exit_cleanup() {
12439 umount $tmpdir/proc
12440 }
12441 mount -t proc proc $tmpdir/proc
12442 # Make sure proc is unmounted also on failure
12443 trap exit_cleanup EXIT INT
12444
12445 chroot $tmpdir aptitude -y install debconf-utils
12446
12447 # Make sure tasksel autoselection trigger. It need the test scripts
12448 # to return the correct answers.
12449 echo tasksel tasksel/desktop multiselect $desktop | \
12450 chroot $tmpdir debconf-set-selections
12451
12452 # Include the desktop and laptop task
12453 for test in desktop laptop ; do
12454 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
12455 #!/bin/sh
12456 exit 2
12457 EOF
12458 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12459 done
12460
12461 DEBIAN_FRONTEND=noninteractive
12462 DEBIAN_PRIORITY=critical
12463 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12464 chroot $tmpdir tasksel --new-install
12465
12466 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
12467 chroot $tmpdir aptitude update
12468 touch $tmpdir/etc/udev/kernel-upgrade
12469 chroot $tmpdir aptitude -y dist-upgrade
12470 fuser -mv
12471 &lt;/pre&gt;&lt;/blockquote&gt;
12472
12473 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
12474 with aptitude, but I have not had time to look at how they behave
12475 differently so far. I hope to get a cron job running to do the test
12476 regularly and post the result on the web. The Gnome upgrade currently
12477 work, while the KDE upgrade fail because of the bug in
12478 kdebase-workspace-data&lt;/p&gt;
12479
12480 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
12481 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
12482 post, so I will refrain from trying. I can report that for Gnome,
12483 aptitude report 760 packages upgraded, 448 newly installed, 129 to
12484 remove and 1 not upgraded and 1024MB need to be downloaded while for
12485 KDE the same numbers are 702 packages upgraded, 507 newly installed,
12486 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
12487
12488 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
12489 is able to migrate to dependency based boot sequencing and parallel
12490 booting without a hitch. Was unsure if there were still bugs with
12491 packages failing to clean up their obsolete init.d script during
12492 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12493 packages.&lt;/p&gt;
12494 </description>
12495 </item>
12496
12497 <item>
12498 <title>Upstart or sysvinit - as init.d scripts see it</title>
12499 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
12500 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
12501 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
12502 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
12503 scripts to migrate (some of) their operations to upstart job while
12504 keeping the init.d for hurd and kfreebsd. The packages with such
12505 needs will need a way to get their init.d scripts to behave
12506 differently when used with sysvinit and with upstart. Because of
12507 this, I had a look at the environment variables set when a init.d
12508 script is running under upstart, and when it is not.&lt;/p&gt;
12509
12510 &lt;p&gt;With upstart, I notice these environment variables are set when a
12511 script is started from rcS.d/ (ignoring some irrelevant ones like
12512 COLUMNS):&lt;/p&gt;
12513
12514 &lt;blockquote&gt;&lt;pre&gt;
12515 DEFAULT_RUNLEVEL=2
12516 previous=N
12517 PREVLEVEL=
12518 RUNLEVEL=
12519 runlevel=S
12520 UPSTART_EVENTS=startup
12521 UPSTART_INSTANCE=
12522 UPSTART_JOB=rc-sysinit
12523 &lt;/pre&gt;&lt;/blockquote&gt;
12524
12525 &lt;p&gt;With sysvinit, these environment variables are set for the same
12526 script.&lt;/p&gt;
12527
12528 &lt;blockquote&gt;&lt;pre&gt;
12529 INIT_VERSION=sysvinit-2.88
12530 previous=N
12531 PREVLEVEL=N
12532 RUNLEVEL=S
12533 runlevel=S
12534 &lt;/pre&gt;&lt;/blockquote&gt;
12535
12536 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
12537 sysvinit are not set by upstart. Not sure if it is intentional or not
12538 to not be compatible with sysvinit in this regard.&lt;/p&gt;
12539
12540 &lt;p&gt;For scripts needing to behave differently when upstart is used,
12541 looking for the UPSTART_JOB environment variable seem to be a good
12542 choice.&lt;/p&gt;
12543 </description>
12544 </item>
12545
12546 <item>
12547 <title>A manual for standards wars...</title>
12548 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
12549 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
12550 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
12551 <description>&lt;p&gt;Via the
12552 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
12553 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
12554 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
12555 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
12556 following the standards wars of today.&lt;/p&gt;
12557 </description>
12558 </item>
12559
12560 <item>
12561 <title>Sitesummary tip: Listing computer hardware models used at site</title>
12562 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
12563 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
12564 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
12565 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
12566 to get a list of the machine types in use thanks to the DMI
12567 information extracted from each machine. The script to do so is
12568 included in the sitesummary package, and here is example output from
12569 the Skolelinux build servers:&lt;/p&gt;
12570
12571 &lt;blockquote&gt;&lt;pre&gt;
12572 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12573 vendor count
12574 Dell Computer Corporation 1
12575 PowerEdge 1750 1
12576 IBM 1
12577 eserver xSeries 345 -[8670M1X]- 1
12578 Intel 2
12579 [no-dmi-info] 3
12580 maintainer:~#
12581 &lt;/pre&gt;&lt;/blockquote&gt;
12582
12583 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
12584 provided in each machine. Here there are Intel machines without model
12585 information listed with Intel as vendor and no model, and virtual Xen
12586 machines listed as [no-dmi-info]. One can add -l as a command line
12587 option to list the individual machines.&lt;/p&gt;
12588
12589 &lt;p&gt;A larger list is
12590 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
12591 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
12592 provide the basic sitesummary report publicly. In their report there
12593 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
12594 their machines, and as sitesummary is available in both distributions,
12595 it is trivial to get all of them to report to the same central
12596 collector.&lt;/p&gt;
12597 </description>
12598 </item>
12599
12600 <item>
12601 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
12602 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
12603 <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>
12604 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
12605 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
12606 start at boot when an NVidia video card is used is handled. The
12607 problem seem to be that the nvidia X.org driver uses a long time to
12608 initialize, and this duration is longer than kdm is configured to
12609 wait.&lt;/p&gt;
12610
12611 &lt;p&gt;I came across two bugs related to this issue,
12612 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
12613 against initscripts and passed on to nvidia-glx when it became obvious
12614 that the nvidia drivers were involved, and
12615 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
12616 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
12617
12618 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
12619 problem nvidia video card owners experience and make sure the Debian
12620 distribution work out of the box for these users. The nvidia driver
12621 maintainers expect kdm to be set up to wait longer, while kdm expect
12622 the nvidia driver maintainers to fix the driver to start faster, and
12623 while they wait for each other I guess the users end up switching to a
12624 distribution that work for them. I have no idea what the solution is,
12625 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
12626
12627 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
12628 </description>
12629 </item>
12630
12631 <item>
12632 <title>Parallellized boot seem to hold up well in Debian/testing</title>
12633 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
12634 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
12635 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
12636 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
12637 The feature seem to hold up pretty well, but three fairly serious
12638 issues are known and should be solved:
12639
12640 &lt;p&gt;&lt;ul&gt;
12641
12642 &lt;li&gt;The wicd package seen to
12643 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
12644 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
12645 parallel booting is enabled. No idea why, but the wicd maintainer
12646 seem to be on the case.&lt;/li&gt;
12647
12648 &lt;li&gt;The nvidia X driver seem to
12649 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
12650 triggered more easily when parallel booting is in effect. The
12651 maintainer is on the case.&lt;/li&gt;
12652
12653 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
12654 sequencing (the shutdown is broken) when old file-rc users
12655 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
12656 sysv-rc. One way to solve it would be for file-rc to create
12657 /etc/init.d/.legacy-bootordering, and another is to try to make
12658 sysv-rc more robust. Will investigate some more and probably upload a
12659 workaround in sysv-rc to help those trying to move from file-rc to
12660 sysv-rc get a working shutdown.&lt;/li&gt;
12661
12662 &lt;/ul&gt;&lt;/p&gt;
12663
12664 &lt;p&gt;All in all not many surprising issues, and all of them seem
12665 solvable before Squeeze is released. In addition to these there are
12666 some packages with bugs in their dependencies and run level settings,
12667 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
12668
12669 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12670 the BTS, please usertag the report to get it to show up at
12671 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12672 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12673
12674 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12675 </description>
12676 </item>
12677
12678 <item>
12679 <title>More flexible firmware handling in debian-installer</title>
12680 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12681 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12682 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12683 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12684 found time today to return to the project. Having to spend less time
12685 working dependency based boot in debian, as it is almost complete now,
12686 definitely helped freeing some time.&lt;/p&gt;
12687
12688 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12689 include some firmware packages on the Debian Edu CDs, those needed to
12690 get disk and network controllers working. Without having these
12691 firmware packages available during installation, it is impossible to
12692 install Debian Edu on the given machine, and because our target group
12693 are non-technical people, asking them to provide firmware packages on
12694 an external medium is a support pain. Initially, I expected it to be
12695 enough to include the firmware packages on the CD to get
12696 debian-installer to find and use them. This proved to be wrong.
12697 Next, I hoped it was enough to symlink the relevant firmware packages
12698 to some useful location on the CD (tried /cdrom/ and
12699 /cdrom/firmware/). This also proved to not work, and at this point I
12700 found time to look at the debian-installer code to figure out what was
12701 going to work.&lt;/p&gt;
12702
12703 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12704 look revealed that it would only look for firmware packages outside
12705 the installation media, so the CD was never checked for firmware
12706 packages. It would only check USB sticks, floppies and other
12707 &quot;external&quot; media devices. Today I changed it to also look in the
12708 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12709 solve the problem I ran into with Debian edu. I also changed it to
12710 look in /firmware/, to make sure the installer also find firmware
12711 provided in the initrd when booting the installer via PXE, to allow us
12712 to provide the same feature in the PXE setup included in Debian
12713 Edu.&lt;/p&gt;
12714
12715 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12716 activated without asking if the license is accepted, I extended
12717 hw-detect to look for preinst scripts in the firmware packages, and
12718 run these before activating the firmware during installation. The
12719 license question is asked using debconf in the preinst, so this should
12720 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12721
12722 &lt;p&gt;If you want to discuss the details of these features, please
12723 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12724 </description>
12725 </item>
12726
12727 <item>
12728 <title>Parallellized boot is now the default in Debian/unstable</title>
12729 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12730 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12731 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12732 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12733 Debian/unstable for machines using dependency based boot sequencing.
12734 Apparently the testing of concurrent booting has been wider than
12735 expected, if I am to believe the
12736 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12737 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12738 with the feature this weekend, to give us some time to detect any
12739 remaining problems before Squeeze is frozen. If serious problems are
12740 detected, it is simple to change the default back to sequential boot.
12741 The upload of the new sysvinit package also activate a new upstream
12742 version.&lt;/p&gt;
12743
12744 More information about
12745 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12746 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12747 currently possible to disable parallel booting when one run into
12748 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12749
12750 &lt;blockquote&gt;&lt;pre&gt;
12751 CONCURRENCY=none
12752 &lt;/pre&gt;&lt;/blockquote&gt;
12753
12754 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12755 the BTS, please usertag the report to get it to show up at
12756 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12757 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12758 </description>
12759 </item>
12760
12761 <item>
12762 <title>Sitesummary tip: Listing MAC address of all clients</title>
12763 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12764 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12765 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12766 <description>&lt;p&gt;In the recent Debian Edu versions, the
12767 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12768 system&lt;/a&gt; is used to keep track of the machines in the school
12769 network. Each machine will automatically report its status to the
12770 central server after boot and once per night. The network setup is
12771 also reported, and using this information it is possible to get the
12772 MAC address of all network interfaces in the machines. This is useful
12773 to update the DHCP configuration.&lt;/p&gt;
12774
12775 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12776 ist all MAC addresses of all machines reporting to sitesummary. Run
12777 this on the collector host:&lt;/p&gt;
12778
12779 &lt;blockquote&gt;&lt;pre&gt;
12780 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12781 &lt;/pre&gt;&lt;/blockquote&gt;
12782
12783 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12784 line per machine and with space between the MAC addresses.&lt;/p&gt;
12785
12786 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12787 addresses for hosts, it would be possible to extend this to fetch
12788 machine information from sitesummary and update the DHCP and DNS
12789 tables in LDAP using this information. Such tool is unfortunately not
12790 written yet.&lt;/p&gt;
12791 </description>
12792 </item>
12793
12794 <item>
12795 <title>systemd, an interesting alternative to upstart</title>
12796 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
12797 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
12798 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
12799 <description>&lt;p&gt;The last few days a new boot system called
12800 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
12801 has been
12802 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
12803
12804 to the free software world. I have not yet had time to play around
12805 with it, but it seem to be a very interesting alternative to
12806 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
12807 a good alternative for Debian when we are able to switch to an event
12808 based boot system. Tollef is
12809 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
12810 systemd into Debian, and I look forward to seeing how well it work. I
12811 like the fact that systemd handles init.d scripts with dependency
12812 information natively, allowing them to run in parallel where upstart
12813 at the moment do not.&lt;/p&gt;
12814
12815 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
12816 platform support. It only work on recent Linux kernels, and also need
12817 some new kernel features enabled to function properly. This means
12818 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12819 system. Not sure how that will be handled if systemd proves to be the
12820 way forward.&lt;/p&gt;
12821
12822 &lt;p&gt;In the mean time, based on the
12823 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12824 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
12825 decided to enable full parallel booting as the default in Debian as
12826 soon as possible (probably this weekend or early next week), to see if
12827 there are any remaining serious bugs in the init.d dependencies. A
12828 new version of the sysvinit package implementing this change is
12829 already in experimental. If all go well, Squeeze will be released
12830 with parallel booting enabled by default.&lt;/p&gt;
12831 </description>
12832 </item>
12833
12834 <item>
12835 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
12836 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
12837 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
12838 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
12839 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
12840 complete, so complete that it is actually possible to run all the
12841 init.d scripts in parallell based on these dependencies. If you want
12842 to test your Squeeze system, make sure
12843 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12844 based boot sequencing&lt;/a&gt; is enabled, and add this line to
12845 /etc/default/rcS:&lt;/p&gt;
12846
12847 &lt;blockquote&gt;&lt;pre&gt;
12848 CONCURRENCY=makefile
12849 &lt;/pre&gt;&lt;/blockquote&gt;
12850
12851 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
12852 scripts in parallel using the dependency information stored in
12853 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12854 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12855 to try to start the kdm and gdm scripts as early as possible, and will
12856 start the facilities required by kdm or gdm as early as possible to
12857 make this happen.&lt;/p&gt;
12858
12859 &lt;p&gt;Give it a try, and see if you like the result. If some services
12860 fail to start properly, it is most likely because they have incomplete
12861 init.d script dependencies in their startup script (or some of their
12862 dependent scripts have incomplete dependencies). Report bugs and get
12863 the package maintainers to fix it. :)&lt;/p&gt;
12864
12865 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
12866 manage to get the init.d script dependencies complete and correct. I
12867 expect we will get there in Squeeze+1, if we get manage to test and
12868 fix the remaining issues.&lt;/p&gt;
12869
12870 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12871 the BTS, please usertag the report to get it to show up at
12872 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12873 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12874 </description>
12875 </item>
12876
12877 <item>
12878 <title>Debian has switched to dependency based boot sequencing</title>
12879 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
12880 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
12881 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
12882 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
12883 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
12884 have been migrated to using dependency based boot sequencing. This
12885 conclude work me and others have been doing for the last three days.
12886 It feels great to see this finally part of the default Debian
12887 installation. Now we just need to weed out the last few problems that
12888 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
12889
12890 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
12891 fixing the more fundamental problem of handing the event based
12892 non-predictable kernel in the early boot.&lt;/p&gt;
12893 </description>
12894 </item>
12895
12896 <item>
12897 <title>Taking over sysvinit development</title>
12898 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
12899 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
12900 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
12901 <description>&lt;p&gt;After several years of frustration with the lack of activity from
12902 the existing sysvinit upstream developer, I decided a few weeks ago to
12903 take over the package and become the new upstream. The number of
12904 patches to track for the Debian package was becoming a burden, and the
12905 lack of synchronization between the distribution made it hard to keep
12906 the package up to date.&lt;/p&gt;
12907
12908 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12909 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
12910 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
12911 and Fedora), based on the patches currently in use in these
12912 distributions. We Debian maintainers plan to move to this tarball as
12913 the new upstream as soon as we find time to do the merge. Since the
12914 new tarball was created, we agreed with Werner at SuSe to make a new
12915 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
12916 development there. The project is registered and currently waiting
12917 for approval by the Savannah administrators, and as soon as it is
12918 approved, we will import the old versions from svn and continue
12919 working on the future release.&lt;/p&gt;
12920
12921 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
12922 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
12923 </description>
12924 </item>
12925
12926 <item>
12927 <title>Debian boots quicker and quicker</title>
12928 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
12929 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
12930 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
12931 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
12932 people involved in the boot system on Debian and Ubuntu, to see if we
12933 could find more ways to speed up the boot system. This was an Ubuntu
12934 funded
12935 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
12936 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
12937 of boot systems, and ways to handle the increasing number of boot
12938 issues introduced by the Linux kernel becoming more and more
12939 asynchronous and event base. The Ubuntu approach using udev and
12940 upstart might be a good way forward. Time will show.&lt;/p&gt;
12941
12942 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
12943 process in Debian. All of these should be applied to get a quick
12944 boot:&lt;/p&gt;
12945
12946 &lt;ul&gt;
12947
12948 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
12949
12950 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
12951 clock is in UTC.&lt;/li&gt;
12952
12953 &lt;li&gt;Install and activate the insserv package to enable
12954 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12955 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
12956
12957 &lt;/ul&gt;
12958
12959 These points are based on the Google summer of code work done by
12960 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
12961 Villegas&lt;/a&gt;.
12962
12963 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
12964 unstable yesterday. When we tested it, we were able to cut 6 seconds
12965 from the boot sequence. It depend on very correct dependency
12966 declaration in all init.d scripts, so I expect us to find edge cases
12967 where the dependences in some scripts are slightly wrong when we start
12968 using this.&lt;/p&gt;
12969
12970 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12971 introduced by Raphael Geissert today, one that could affect the
12972 startup speed as well. Instead of starting some scripts concurrently
12973 from rcS.d/ and another set of scripts from rc2.d/, it would be
12974 possible to run a of them in the same process. A quick way to test
12975 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
12976 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
12977 </description>
12978 </item>
12979
12980 <item>
12981 <title>BSAs påstander om piratkopiering møter motstand</title>
12982 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
12983 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
12984 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
12985 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
12986 programvareselskapene som Microsoft og Apple, publisert en rapport der
12987 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12988 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12989 dager siden kom
12990 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
12991 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
12992 dagene. Et spesielt interessant kommentar fra Sverige,
12993 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
12994 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
12995
12996 &lt;blockquote&gt;
12997 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
12998 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12999 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
13000 exakta&quot;, säger BSAs Sverigechef John Hugosson.
13001 &lt;/blockquote&gt;
13002
13003 &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
13004 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
13005 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
13006 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
13007 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
13008
13009 &lt;p&gt;Fant lenkene via &lt;a
13010 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
13011 på Slashdot&lt;/a&gt;.&lt;/p&gt;
13012 </description>
13013 </item>
13014
13015 <item>
13016 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
13017 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
13018 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
13019 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
13020 <description>&lt;p&gt;Kom over
13021 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
13022 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
13023 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
13024 jobber til daglig. En rask opptelling forteller meg at vi har 490
13025 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
13026 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
13027 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
13028 </description>
13029 </item>
13030
13031 <item>
13032 <title>Kryptert harddisk - naturligvis</title>
13033 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
13034 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
13035 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
13036 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
13037 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
13038 når en tar tap av arbeidstid, fortrolige dokumenter,
13039 personopplysninger og alt annet det innebærer. Det er ingen tvil om
13040 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
13041 til at jeg har kryptert harddisken på både kontormaskinen og min
13042 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13043 komme på avveie, den første informasjon relatert til jobben min ved
13044 Universitetet i Oslo, og den andre relatert til blant annet
13045 foreningsarbeide. Kryptering av diskene gjør at det er lite
13046 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13047 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13048 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13049 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13050 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13051 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13052 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
13053 det er gjort slik jeg gjør det er minimale, og gevinstene er
13054 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
13055 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
13056
13057 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
13058 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
13059 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
13060 er for min del høyere enn gevinsten. Jeg tror oddsene for at
13061 f.eks. etteretningsorganisasjoner har glede av å titte på mine
13062 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
13063 gjøre det vanskeligere for angripere med kompetanse og ressurser er
13064 betydelige.&lt;/p&gt;
13065 </description>
13066 </item>
13067
13068 <item>
13069 <title>Two projects that have improved the quality of free software a lot</title>
13070 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
13071 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
13072 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
13073 <description>&lt;p&gt;There are two software projects that have had huge influence on the
13074 quality of free software, and I wanted to mention both in case someone
13075 do not yet know them.&lt;/p&gt;
13076
13077 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
13078 tool to detect and expose errors in the memory handling of programs.
13079 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
13080 and it will report any problems on stdout. It is even better if the
13081 program include debug information. With debug information, it is able
13082 to report the source file name and line number where the problem
13083 occurs. It can report things like &#39;reading past memory block in file
13084 X line N, the memory block was allocated in file Y, line M&#39;, and
13085 &#39;using uninitialised value in control logic&#39;. This tool has made it
13086 trivial to investigate reproducible crash bugs in programs, and have
13087 reduced the number of this kind of bugs in free software a lot.
13088
13089 &lt;p&gt;The second one is
13090 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
13091 a source code checker. It is able to process the source of a program
13092 and find problems in the logic without running the program. It
13093 started out as the Stanford Checker and became well known when it was
13094 used to find bugs in the Linux kernel. It is now a commercial tool
13095 and the company behind it is running
13096 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
13097 free software community, where a lot of free software projects get
13098 their source checked for free. Several thousand defects have been
13099 found and fixed so far. It can find errors like &#39;lock L taken in file
13100 X line N is never released if exiting in line M&#39;, or &#39;the code in file
13101 Y lines O to P can never be executed&#39;. The projects included in the
13102 community service project have managed to get rid of a lot of
13103 reliability problems thanks to Coverity.&lt;/p&gt;
13104
13105 &lt;p&gt;I believe tools like this, that are able to automatically find
13106 errors in the source, are vital to improve the quality of software and
13107 make sure we can get rid of the crashing and failing software we are
13108 surrounded by today.&lt;/p&gt;
13109 </description>
13110 </item>
13111
13112 <item>
13113 <title>No patch is not better than a useless patch</title>
13114 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
13115 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
13116 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
13117 <description>&lt;p&gt;Julien Blache
13118 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
13119 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
13120 patch allow one to discuss a concrete and proposed solution, and also
13121 prove that the issue at hand is important enough for someone to spent
13122 time on fixing it. No patch do not provide any of these positive
13123 properties.&lt;/p&gt;
13124 </description>
13125 </item>
13126
13127 <item>
13128 <title>Standardize on protocols and formats, not vendors and applications</title>
13129 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
13130 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
13131 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
13132 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
13133 very good one to form a long lived computer infrastructure. It is the
13134 simple one, lost by many in todays computer industry: Standardize on
13135 open network protocols and open exchange/storage formats, not applications.
13136 Applications come and go, while protocols and files tend to stay, and
13137 thus one want to make it easy to change application and vendor, while
13138 avoiding conversion costs and locking users to a specific platform or
13139 application.&lt;/p&gt;
13140
13141 &lt;p&gt;This approach make it possible to replace the client applications
13142 independently of the server applications. One can even allow users to
13143 use several different applications as long as they handle the selected
13144 protocol and format. In the normal case, only one client application
13145 is recommended and users only get help if they choose to use this
13146 application, but those that want to deviate from the easy path are not
13147 blocked from doing so.&lt;/p&gt;
13148
13149 &lt;p&gt;It also allow us to replace the server side without forcing the
13150 users to replace their applications, and thus allow us to select the
13151 best server implementation at any moment, when scale and resouce
13152 requirements change.&lt;/p&gt;
13153
13154 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
13155 open formats, but I would never recommend standardizing on a single
13156 application that do not use open network protocol or open formats.&lt;/p&gt;
13157 </description>
13158 </item>
13159
13160 <item>
13161 <title>Returning from Skolelinux developer gathering</title>
13162 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
13163 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
13164 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
13165 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
13166 Edu/Skolelinux development gathering. I got a bit done tuning the
13167 desktop, and looked into the dynamic service location protocol
13168 implementation avahi. It look like it could be useful for us. Almost
13169 30 people participated, and I believe it was a great environment to
13170 get to know the Skolelinux system. Walter Bender, involved in the
13171 development of the Sugar educational platform, presented his stuff and
13172 also helped me improve my OLPC installation. He also showed me that
13173 his Turtle Art application can be used in standalone mode, and we
13174 agreed that I would help getting it packaged for Debian. As a
13175 standalone application it would be great for Debian Edu. We also
13176 tried to get the video conferencing working with two OLPCs, but that
13177 proved to be too hard for us. The application seem to need more work
13178 before it is ready for me. I look forward to getting home and relax
13179 now. :)&lt;/p&gt;
13180 </description>
13181 </item>
13182
13183 <item>
13184 <title>Time for new LDAP schemas replacing RFC 2307?</title>
13185 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
13186 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
13187 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
13188 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
13189 optimal. There is RFC 2307 documenting one way to store NIS maps in
13190 LDAP, and a modified version of this normally called RFC 2307bis, with
13191 some modifications to be compatible with Active Directory. The RFC
13192 specification handle the content of a lot of system databases, but do
13193 not handle DNS zones and DHCP configuration.&lt;/p&gt;
13194
13195 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
13196 we would like to store information about users, SMB clients/hosts,
13197 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13198 and LTSP configuration in LDAP. These objects have a lot in common,
13199 but with the current LDAP schemas it is not possible to have one
13200 object per entity. For example, one need to have at least three LDAP
13201 objects for a given computer, one with the SMB related stuff, one with
13202 DNS information and another with DHCP information. The schemas
13203 provided for DNS and DHCP are impossible to combine into one LDAP
13204 object. In addition, it is impossible to implement quick queries for
13205 netgroup membership, because of the way NIS triples are implemented.
13206 It just do not scale. I believe it is time for a few RFC
13207 specifications to cleam up this mess.&lt;/p&gt;
13208
13209 &lt;p&gt;I would like to have one LDAP object representing each computer in
13210 the network, and this object can then keep the SMB (ie host key), DHCP
13211 (mac address/name) and DNS (name/IP address) settings in one place.
13212 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
13213
13214 &lt;p&gt;I would also like to have a quick way to map from a user or
13215 computer and to the net group this user or computer is a member.&lt;/p&gt;
13216
13217 &lt;p&gt;Active Directory have done a better job than unix heads like myself
13218 in this regard, and the unix side need to catch up. Time to start a
13219 new IETF work group?&lt;/p&gt;
13220 </description>
13221 </item>
13222
13223 <item>
13224 <title>Endelig er Debian Lenny gitt ut</title>
13225 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
13226 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
13227 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
13228 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
13229 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
13230 Et langt steg videre for Debian-prosjektet, og en rekke nye
13231 programpakker blir nå tilgjengelig for de av oss som bruker den
13232 stabile utgaven av Debian. Neste steg er nå å få
13233 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
13234 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
13235 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13236 slippes løs på skolene. Takk til alle debian-utviklerne som har
13237 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13238 bootsekvens tilgjengelig i stabil utgave, vha pakken
13239 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
13240 </description>
13241 </item>
13242
13243 <item>
13244 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
13245 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
13246 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
13247 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
13248 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
13249 Oslo. Most of Saturday was used for the general assemly for the
13250 member organization, but the rest of the weekend I used to tune the
13251 LTSP installation. LTSP now work out of the box on the 10-network.
13252 Acer Aspire One proved to be a very nice thin client, with both
13253 screen, mouse and keybard in a small box. Was working on getting the
13254 diskless workstation setup configured out of the box, but did not
13255 finish it before the weekend was up.&lt;/p&gt;
13256
13257 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
13258 the Brazilian group, so that will have to wait for the next
13259 development gathering. Would love to have the Debian Edu installer
13260 automatically detect and configure a multiseat setup when it find one
13261 of these cards.&lt;/p&gt;
13262 </description>
13263 </item>
13264
13265 <item>
13266 <title>The sorry state of multimedia browser plugins in Debian</title>
13267 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
13268 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
13269 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
13270 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
13271 plugins available in Debian Lenny, to see which one we should use by
13272 default in Debian Edu. We need an embedded video playing plugin with
13273 control buttons to pause or stop the video, and capable of streaming
13274 all the multimedia content available on the web. The test results and
13275 notes are available on
13276 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
13277 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
13278 fill this need. My personal video player favorite, VLC, has a really
13279 bad plugin which fail on a lot of the test pages. A lot of the MIME
13280 types I would expect to work with any free software player (like
13281 video/ogg), just do not work. And simple formats like the
13282 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
13283 totem and vlc plugins. I hope the situation will improve soon. No
13284 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
13285
13286 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
13287 be the only one fitting our needs. :/&lt;/p&gt;
13288 </description>
13289 </item>
13290
13291 </channel>
13292 </rss>