]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
627f5bc24cf6b98c268fd71e9147127ede9e2b73
[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>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Using the Kodi API to play Youtube videos</title>
11 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
13 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
14 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
15 tell it to play a youtube URL I received in a chat, without having to
16 insert search terms using the on-screen keyboard. After searching the
17 web for API access to the Youtube plugin and testing a bit, I managed
18 to find a recipe that worked. If you got a kodi instance with its API
19 available from http://kodihost/jsonrpc, you can try the following to
20 have check out a nice cover band.&lt;/p&gt;
21
22 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
23 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
24 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
25 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
26 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
27
28 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
29 first argument. It can now handle direct video links, youtube links
30 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
31 Chromecast. :)&lt;/p&gt;
32
33 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
34 activities, please send Bitcoin donations to my address
35 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
36 </description>
37 </item>
38
39 <item>
40 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
41 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
42 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
43 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
44 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
45 with my family using a self hosted solution, as it is unacceptable to
46 place images from my personal life under the control of strangers
47 working for data hoarders like Google or Dropbox. The last few days I
48 have drafted an approach that might work out, and I would like to
49 share it with you. I would like to publish images on a server under
50 my control, and point some Internet connected display units using some
51 free and open standard to the images I published. As my primary
52 language is not limited to ASCII, I need to store metadata using
53 UTF-8. Many years ago, I hoped to find a digital photo frame capable
54 of reading a RSS feed with image references (aka using the
55 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
56 of such frames. In the end I gave up that approach.&lt;/p&gt;
57
58 &lt;p&gt;Some months ago, I discovered that
59 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
60 read images from a RSS feed, and used it to set up a screen saver on
61 my home info screen, showing images from the Daily images feed from
62 NASA. This proved to work well. More recently I discovered that
63 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
64 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
65 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
66 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
67 screen saver capable of reading a RSS feed with images and news. For
68 fun, I used it this summer to test Kodi on my parents TV by hooking up
69 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
70 screen saver showing selected pictures from my selection.&lt;/p&gt;
71
72 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
73 a RSS feed for the Kodi instance. I adjusted my &lt;a
74 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
75 /var/www/html/privatepictures/, wrote a small Perl script to extract
76 title and description metadata from the photo files and generate the
77 RSS file. I ended up using Perl instead of python, as the
78 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
79 tags I ended up using, while python3-exif did not. The relevant EXIF
80 tags only support ASCII, so I had to find better alternatives. XMP
81 seem to have the support I need.&lt;/p&gt;
82
83 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
84 use tags that can be easily added/updated using normal free software
85 photo managing software. I ended up using the tags set using this
86 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
87
88 &lt;blockquote&gt;&lt;pre&gt;
89 exiftool -headline=&#39;The RSS image title&#39; \
90 -description=&#39;The RSS image description.&#39; \
91 -subject+=for-family photo.jpeg
92 &lt;/pre&gt;&lt;/blockquote&gt;
93
94 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
95 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
96 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
97 shared with my family. Images with this keyword set are located and
98 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
99
100 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
101 suggestions.&lt;/p&gt;
102
103 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
104 activities, please send Bitcoin donations to my address
105 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
106 </description>
107 </item>
108
109 <item>
110 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
111 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
112 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
113 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
114 <description>&lt;p&gt;Last night, I wrote
115 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
116 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
117 During the day I received valuable feedback, and thanks to the
118 suggestions I have been able to rewrite the recipe into a much simpler
119 approach requiring no setup at all. It is a single script that take
120 care of it all.&lt;/p&gt;
121
122 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
123 desktop and stream it to Kodi. This fixed the video quality issue I
124 saw initially. It further removes the need to add a m3u file on the
125 Kodi machine, as it instead connects to
126 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
127 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
128 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
129 the script below, run it with the DNS name or IP address of the kodi
130 server to stream to as the only argument, and watch your screen show
131 up on the Kodi screen. Note, it depend on multicast on the local
132 network, so if you need to stream outside the local network, the
133 script must be modified. Also note, I have no idea if audio work, as
134 I only care about the picture part.&lt;/p&gt;
135
136 &lt;blockquote&gt;&lt;pre&gt;
137 #!/bin/sh
138 #
139 # Stream the Linux desktop view to Kodi. See
140 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
141 # for backgorund information.
142
143 # Make sure the stream is stopped in Kodi and the gstreamer process is
144 # killed if something go wrong (for example if curl is unable to find the
145 # kodi server). Do the same when interrupting this script.
146 kodicmd() {
147 host=&quot;$1&quot;
148 cmd=&quot;$2&quot;
149 params=&quot;$3&quot;
150 curl --silent --header &#39;Content-Type: application/json&#39; \
151 --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; \
152 &quot;http://$host/jsonrpc&quot;
153 }
154 cleanup() {
155 if [ -n &quot;$kodihost&quot; ] ; then
156 # Stop the playing when we end
157 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
158 jq .result[].playerid)
159 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
160 fi
161 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
162 kill &quot;$gstpid&quot;
163 fi
164 }
165 trap cleanup EXIT INT
166
167 if [ -n &quot;$1&quot; ]; then
168 kodihost=$1
169 shift
170 else
171 kodihost=kodi.local
172 fi
173
174 mcast=239.255.0.1
175 mcastport=1234
176 mcastttl=1
177
178 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
179 cut -d&quot; &quot; -f2|head -1)
180 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
181 videoconvert ! queue2 ! \
182 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
183 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
184 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
185 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
186 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
187 &gt; /dev/null 2&gt;&amp;1 &amp;
188 gstpid=$!
189
190 # Give stream a second to get going
191 sleep 1
192
193 # Ask kodi to start streaming using its JSON-RPC API
194 kodicmd &quot;$kodihost&quot; Player.Open \
195 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
196
197 # wait for gst to end
198 wait &quot;$gstpid&quot;
199 &lt;/pre&gt;&lt;/blockquote&gt;
200
201 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
202
203 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
204 activities, please send Bitcoin donations to my address
205 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
206 </description>
207 </item>
208
209 <item>
210 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
211 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
212 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
213 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
214 <description>&lt;p&gt;PS: See
215 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
216 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
217
218 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
219 my projector connected to Kodi. I sadly had to admit that I had no
220 idea, as it was a task I never had tried. Since then, I have been
221 looking for a way to do so, preferable without much extra software to
222 install on either side. Today I found a way that seem to kind of
223 work. Not great, but it is a start.&lt;/p&gt;
224
225 &lt;p&gt;I had a look at several approaches, for example
226 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
227 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
228 local storage enough to store the stream locally. This is not going
229 to work well for me, lacking enough free space, and it would
230 impossible for my friend to get working.&lt;/p&gt;
231
232 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
233 video stream that Kodi could play. Preferably using
234 broadcast/multicast, to avoid having to change any setup on the Kodi
235 side when starting such stream. Unfortunately, the only recipe I
236 could find using multicast used the rtp protocol, and this protocol
237 seem to not be supported by Kodi.&lt;/p&gt;
238
239 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
240 have to specify the IP address of the streaming machine in both the
241 sending command and the file on the Kodi server. But it is showing my
242 desktop, and thus allow us to have a shared look on the big screen at
243 the programs I work on.&lt;/p&gt;
244
245 &lt;p&gt;I did not spend much time investigating codeces. I combined the
246 rtp and rtsp recipes from
247 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
248 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
249 this working on the desktop/streaming end.&lt;/p&gt;
250
251 &lt;blockquote&gt;&lt;pre&gt;
252 vlc screen:// --sout \
253 &#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;
254 &lt;/pre&gt;&lt;/blockquote&gt;
255
256 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
257 same IP address:&lt;/p&gt;
258
259 &lt;blockquote&gt;&lt;pre&gt;
260 echo rtsp://192.168.11.4:8080/test.sdp \
261 &gt; /storage/videos/screenstream.m3u
262 &lt;/pre&gt;&lt;/blockquote&gt;
263
264 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
265 as I can tell the IP must be hardcoded for this to work. In other
266 words, if someone elses machine is going to do the steaming, you have
267 to update screenstream.m3u on the Kodi machine and adjust the vlc
268 recipe. To get started, locate the file in Kodi and select the m3u
269 file while the VLC stream is running. The desktop then show up in my
270 big screen. :)&lt;/p&gt;
271
272 &lt;p&gt;When using the same technique to stream a video file with audio,
273 the audio quality is really bad. No idea if the problem is package
274 loss or bad parameters for the transcode. I do not know VLC nor Kodi
275 enough to tell.&lt;/p&gt;
276
277 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
278 succestions and reminded me about an important step. The &quot;screen:&quot;
279 input source is only available once the vlc-plugin-access-extra
280 package is installed on Debian. Without it, you will see this error
281 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
282 for details.&quot; He further found that it is possible to drop some parts
283 of the VLC command line to reduce the amount of hardcoded information.
284 It is also useful to consider using cvlc to avoid having the VLC
285 window in the desktop view. In sum, this give us this command line on
286 the source end
287
288 &lt;blockquote&gt;&lt;pre&gt;
289 cvlc screen:// --sout \
290 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
291 &lt;/pre&gt;&lt;/blockquote&gt;
292
293 &lt;p&gt;and this on the Kodi end&lt;p&gt;
294
295 &lt;blockquote&gt;&lt;pre&gt;
296 echo rtsp://192.168.11.4:8080/ \
297 &gt; /storage/videos/screenstream.m3u
298 &lt;/pre&gt;&lt;/blockquote&gt;
299
300 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
301 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
302 audio quality, so I guess the issue is in the input or transcoding
303 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
304 parameters to use more bandwidth, but it did not make a
305 difference.&lt;/p&gt;
306
307 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
308 gstreamer instead of VLC, and this proved to work great! He also
309 provided me with the trick to get Kodi to use a multicast stream as
310 its source. By using this monstrous oneliner, I can stream my desktop
311 with good video quality in reasonable framerate to the 239.255.0.1
312 multicast address on port 1234:
313
314 &lt;blockquote&gt;&lt;pre&gt;
315 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
316 videoconvert ! queue2 ! \
317 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
318 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
319 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
320 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
321 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
322 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
323 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
324 &lt;/pre&gt;&lt;/blockquote&gt;
325
326 &lt;p&gt;and this on the Kodi end&lt;p&gt;
327
328 &lt;blockquote&gt;&lt;pre&gt;
329 echo udp://@239.255.0.1:1234 \
330 &gt; /storage/videos/screenstream.m3u
331 &lt;/pre&gt;&lt;/blockquote&gt;
332
333 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
334 pick the one you need. This approach will of course lead to trouble
335 if more than one source uses the same multicast port and address.
336 Note the ttl-mc=1 setting, which limit the multicast packages to the
337 local network. If the value is increased, your screen will be
338 broadcasted further, one network &quot;hop&quot; for each increase (read up on
339 multicast to learn more. :)!&lt;/p&gt;
340
341 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
342 could use this VLC command to stream to the same multicast address.
343 The image quality is way better than the rtsp approach, but gstreamer
344 seem to be doing a better job.&lt;/p&gt;
345
346 &lt;blockquote&gt;&lt;pre&gt;
347 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;
348 &lt;/pre&gt;&lt;/blockquote&gt;
349
350 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
351 activities, please send Bitcoin donations to my address
352 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
353 </description>
354 </item>
355
356 <item>
357 <title>What is the most supported MIME type in Debian in 2018?</title>
358 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
359 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
360 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
361 <description>&lt;p&gt;Five years ago,
362 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
363 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
364 analysing the desktop files in all packages in the archive. Since
365 then, the DEP-11 AppStream system has been put into production, making
366 the task a lot easier. This made me want to repeat the measurement,
367 to see how much things changed. Here are the new numbers, for
368 unstable only this time:
369
370 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
371
372 &lt;pre&gt;
373 count MIME type
374 ----- -----------------------
375 56 image/jpeg
376 55 image/png
377 49 image/tiff
378 48 image/gif
379 39 image/bmp
380 38 text/plain
381 37 audio/mpeg
382 34 application/ogg
383 33 audio/x-flac
384 32 audio/x-mp3
385 30 audio/x-wav
386 30 audio/x-vorbis+ogg
387 29 image/x-portable-pixmap
388 27 inode/directory
389 27 image/x-portable-bitmap
390 27 audio/x-mpeg
391 26 application/x-ogg
392 25 audio/x-mpegurl
393 25 audio/ogg
394 24 text/html
395 &lt;/pre&gt;
396
397 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
398 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
399 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
400
401 &lt;p&gt;It is interesting to see how image formats have passed text/plain
402 as the most announced supported MIME type. These days, thanks to the
403 AppStream system, if you run into a file format you do not know, and
404 want to figure out which packages support the format, you can find the
405 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
406 look up all packages announcing support for this format in their
407 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
408 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
409 me, want to know which packages support inode/directory, you can get a
410 list like this:&lt;/p&gt;
411
412 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
413 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
414 Package: anjuta
415 Package: audacious
416 Package: baobab
417 Package: cervisia
418 Package: chirp
419 Package: dolphin
420 Package: doublecmd-common
421 Package: easytag
422 Package: enlightenment
423 Package: ephoto
424 Package: filelight
425 Package: gwenview
426 Package: k4dirstat
427 Package: kaffeine
428 Package: kdesvn
429 Package: kid3
430 Package: kid3-qt
431 Package: nautilus
432 Package: nemo
433 Package: pcmanfm
434 Package: pcmanfm-qt
435 Package: qweborf
436 Package: ranger
437 Package: sirikali
438 Package: spacefm
439 Package: spacefm
440 Package: vifm
441 %
442 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
443
444 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
445 format is not yet supported by any package in Debian:&lt;/p&gt;
446
447 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
448 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
449 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
450 %
451 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
452
453 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
454 format:&lt;/p&gt;
455
456 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
457 % appstreamcli what-provides mimetype application/sla|grep Package
458 Package: cura
459 Package: meshlab
460 Package: printrun
461 %
462 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
463
464 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
465
466 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
467 activities, please send Bitcoin donations to my address
468 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
469 </description>
470 </item>
471
472 <item>
473 <title>Debian APT upgrade without enough free space on the disk...</title>
474 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
476 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
477 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
478 for a while, and when I need to update it there is not enough free
479 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
480 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
481 upgrade only some of the packages in one batch, until the amount of
482 packages to download fall below the amount of free space available.
483 Today, I had about 500 packages to upgrade, and after a while I got
484 tired of trying to install chunks of packages manually. I concluded
485 that I did not have the spare hours required to complete the task, and
486 decided to see if I could automate it. I came up with this small
487 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
488
489 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
490 #!/bin/sh
491 #
492 # Upgrade packages when the disk is too full to upgrade every
493 # upgradable package in one lump. Fetching packages to upgrade using
494 # apt, and then installing using dpkg, to avoid changing the package
495 # flag for manual/automatic.
496
497 set -e
498
499 ignore() {
500 if [ &quot;$1&quot; ]; then
501 grep -v &quot;$1&quot;
502 else
503 cat
504 fi
505 }
506
507 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
508 echo &quot;Upgrading $p&quot;
509 apt clean
510 apt install --download-only -y $p
511 for f in /var/cache/apt/archives/*.deb; do
512 if [ -e &quot;$f&quot; ]; then
513 dpkg -i /var/cache/apt/archives/*.deb
514 break
515 fi
516 done
517 done
518 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
519
520 &lt;p&gt;The script will extract the list of packages to upgrade, try to
521 download the packages needed to upgrade one package, install the
522 downloaded packages using dpkg. The idea is to upgrade packages
523 without changing the APT mark for the package (ie the one recording of
524 the package was manually requested or pulled in as a dependency). To
525 use it, simply run it as root from the command line. If it fail, try
526 &#39;apt install -f&#39; to clean up the mess and run the script again. This
527 might happen if the new packages conflict with one of the old
528 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
529
530 &lt;p&gt;It take one option, a package to ignore in the list of packages to
531 upgrade. The option to ignore a package is there to be able to skip
532 the packages that are simply too large to unpack. Today this was
533 &#39;ghc&#39;, but I have run into other large packages causing similar
534 problems earlier (like TeX).&lt;/p&gt;
535
536 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
537 alternative ways to handle this. The &quot;unattended-upgrades
538 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
539 each package to upgrade, and then upgrade them in order, smallest set
540 first. It might be a better option than my above mentioned script.
541 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
542 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
543
544 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
545 activities, please send Bitcoin donations to my address
546 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
547 </description>
548 </item>
549
550 <item>
551 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
552 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
553 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
554 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
555 <description>&lt;p&gt;A new version of the
556 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
557 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
558 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
559 useful. It was uploaded the last few days, and the last update will
560 enter testing tomorrow. See the
561 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
562 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
563 was announced 6 days ago. We will try to get it into Debian as
564 well.&lt;/p&gt;
565
566 &lt;p&gt;More information related to 3D printing is available on the
567 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
568 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
569 in Debian.&lt;/p&gt;
570
571 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
572 activities, please send Bitcoin donations to my address
573 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
574 </description>
575 </item>
576
577 <item>
578 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
579 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
580 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
581 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
582 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
583 that the nice and user friendly 3D printer slicer software Cura just
584 entered Debian Unstable. It consist of five packages,
585 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
586 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
587 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
588 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
589 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
590 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
591 two, uranium and cura, entered Unstable yesterday. This should make
592 it easier for Debian users to print on at least the Ultimaker class of
593 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
594 make life easier for at least me. :)&lt;/p&gt;
595
596 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
597 happy to assist him in sponsoring the packages. With the introduction
598 of Cura, Debian is up to three 3D printer slicers at your service,
599 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
600 printer, give it a go. :)&lt;/p&gt;
601
602 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
603 team, flocking together on the
604 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
605 mailing list and the
606 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
607 IRC channel.&lt;/p&gt;
608
609 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
610 version 3.0.3 and then update the entire set of packages to version
611 3.1.0 which showed up the last few days.&lt;/p&gt;
612 </description>
613 </item>
614
615 <item>
616 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
617 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
619 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
620 <description>&lt;p&gt;At my nearby maker space,
621 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
622 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
623 on Windows and MacOS X than Linux, because the software involved had
624 to be manually compiled and set up on Linux while premade packages
625 worked out of the box on Windows and MacOS X. I found this annoying,
626 as the software involved,
627 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
628 and should be trivial to get up and running on Linux if someone took
629 the time to package it for the relevant distributions. I even found
630 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
631 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
632 never resulted in the software showing up in Debian. So a few days
633 ago I offered my help to try to improve the situation.&lt;/p&gt;
634
635 &lt;p&gt;Now I am very happy to see that all the packages required by a
636 working Cura in Debian are uploaded into Debian and waiting in the NEW
637 queue for the ftpmasters to have a look. You can track the progress
638 on
639 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
640 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
641
642 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
643 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
644 queue&lt;/a&gt; while we work up updating the packages to the latest
645 upstream version.&lt;/p&gt;
646
647 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
648 to use and was unable to configure correctly for Ultimaker 2+ in the
649 short time I spent on it, are already in Debian. If you are looking
650 for 3D printer &quot;slicers&quot; and want something already available in
651 Debian, check out
652 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
653 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
654 The latter is a fork of the former.&lt;/p&gt;
655
656 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
657 activities, please send Bitcoin donations to my address
658 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
659 </description>
660 </item>
661
662 <item>
663 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
664 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
665 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
666 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
667 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
668 mobile cell towers. And this radio chatter is available for anyone
669 with a radio receiver capable of receiving them. Details about the
670 mobile phones with very good accuracy is of course collected by the
671 phone companies, but this is not the topic of this blog post. The
672 mobile phone radio chatter make it possible to figure out when a cell
673 phone is nearby, as it include the SIM card ID (IMSI). By paying
674 attention over time, one can see when a phone arrive and when it leave
675 an area. I believe it would be nice to make this information more
676 available to the general public, to make more people aware of how
677 their phones are announcing their whereabouts to anyone that care to
678 listen.&lt;/p&gt;
679
680 &lt;p&gt;I am very happy to report that we managed to get something
681 visualizing this information up and running for
682 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
683 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
684 library. The solution is based on the
685 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
686 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
687 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
688 Sone from the Computer Science department of the University of
689 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
690 IMSIs) as dots in a web browser graph, with lines to the dot
691 representing mobile base station it is talking to. It was working in
692 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
693
694 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
695 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
696 connected and visualize the visible cell phone towers using an
697 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
698 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
699 grgsm_livemon_headless processes from
700 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
701 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
702
703 &lt;p&gt;The frequencies to listen to, are identified using a slightly
704 patched scan-and-livemon (to set the --args values for each receiver),
705 and the Hopglass data is generated using the
706 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
707 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
708 more than four SDRs working. There is also a geographical map trying
709 to show the location of the base stations, but I believe their
710 coordinates are hardcoded to some random location in Germany, I
711 believe. The code should be replaced with code to look up location in
712 a text file, a sqlite database or one of the online databases
713 mentioned in
714 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
715 issue for the topic&lt;/a&gt;.
716
717 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
718 </description>
719 </item>
720
721 <item>
722 <title>Easier recipe to observe the cell phones around you</title>
723 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
724 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
725 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
726 <description>&lt;p&gt;A little more than a month ago I wrote
727 &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
728 to observe the SIM card ID (aka IMSI number) of mobile phones talking
729 to nearby mobile phone base stations using Debian GNU/Linux and a
730 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
731 the location of people and equipment (like cars and trains) with an
732 accuracy of a few kilometer. Since then we have worked to make the
733 procedure even simpler, and it is now possible to do this without any
734 manual frequency tuning and without building your own packages.&lt;/p&gt;
735
736 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
737 package is now included in Debian testing and unstable, and the
738 IMSI-catcher code no longer require root access to fetch and decode
739 the GSM data collected using gr-gsm.&lt;/p&gt;
740
741 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
742 clone of two python scripts:&lt;/p&gt;
743
744 &lt;ol&gt;
745
746 &lt;li&gt;Start with a Debian machine running the Buster version (aka
747 testing).&lt;/li&gt;
748
749 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
750 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
751
752 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
753 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
754
755 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
756
757 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
758 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
759 stations and start listening for GSM packages on one of them.&lt;/li&gt;
760
761 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
762 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
763
764 &lt;/ol&gt;
765
766 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
767 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
768 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
769 work with RTL 8232 and other similar USB radio receivers you can get
770 very cheaply
771 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
772 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
773 and only use HackRF for fetching GSM data.&lt;/p&gt;
774
775 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
776 frequencies at the time, so if you are going to track and count every
777 cell phone around you, you need to listen to all the frequencies used.
778 To listen to several frequencies, use the --numrecv argument to
779 scan-and-livemon to use several receivers. Further, I am not sure if
780 phones using 3G or 4G will show as talking GSM to base stations, so
781 this approach might not see all phones around you. I typically see
782 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
783
784 &lt;p&gt;I&#39;ve tried to run the scanner on a
785 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
786 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
787 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
788 stdout, I am told there it is caused by a buffer overflow between the
789 radio and GNU Radio, caused by the program being unable to read the
790 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
791 where you started scan-and-livemon, you need a give the process more
792 CPU power. Perhaps someone are able to optimize the code to a point
793 where it become possible to set up RPi3 based GSM sniffers? I tried
794 using Raspbian instead of Debian, but there seem to be something wrong
795 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
796 </description>
797 </item>
798
799 <item>
800 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
801 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
803 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
804 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
805 web based ICT news magazine digi.no on
806 &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
807 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
808 DVB-T software defined radios. The article refered to instructions
809 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
810 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;
811
812 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
813 bypass apt), use pip to install pybombs (to bypass both apt and pip),
814 and the ask pybombs to fetch and build everything you need from
815 scratch. I wanted to see if I could do the same on the most recent
816 Debian packages, but this did not work because pybombs tried to build
817 stuff that no longer build with the most recent openssl library or
818 some other version skew problem. While trying to get this recipe
819 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
820 and the only piece of software dependency missing in Debian was the
821 gr-gsm package. I also found out that the lead upstream developer of
822 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
823 Debian packages provided in an Ubuntu PPA repository. All I needed to
824 do was to dget the Debian source package and built it.&lt;/p&gt;
825
826 &lt;p&gt;The IMSI collector is a python script listening for packages on the
827 loopback network device and printing to the terminal some specific GSM
828 packages with IMSI numbers in them. The code is fairly short and easy
829 to understand. The reason this work is because gr-gsm include a tool
830 to read GSM data from a software defined radio like a DVB-T USB stick
831 and other software defined radios, decode them and inject them into a
832 network device on your Linux machine (using the loopback device by
833 default). This proved to work just fine, and I&#39;ve been testing the
834 collector for a few days now.&lt;/p&gt;
835
836 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
837
838 &lt;ol&gt;
839
840 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
841
842 &lt;li&gt;build and install the gr-gsm package available from
843 &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;
844
845 &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;
846
847 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
848 where it was started is filled with a stream of text (meaning you
849 found a GSM station).&lt;/li&gt;
850
851 &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;
852
853 &lt;/ol&gt;
854
855 &lt;p&gt;To make it even easier in the future to get this sniffer up and
856 running, I decided to package
857 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
858 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
859 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
860 Luckily the gnuradio maintainer has promised to help me, as I do not
861 know much about gnuradio stuff yet.&lt;/p&gt;
862
863 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
864 commercial tools like
865 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
866 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
867 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
868 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
869 more people realise how their whereabouts when carrying a cell phone
870 is easily tracked. Seeing the data flow on the screen, realizing that
871 I live close to a police station and knowing that the police is also
872 wearing cell phones, I wonder how hard it would be for criminals to
873 track the position of the police officers to discover when there are
874 police near by, or for foreign military forces to track the location
875 of the Norwegian military forces, or for anyone to track the location
876 of government officials...&lt;/p&gt;
877
878 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
879 script mentioned above is only a fraction of the data broadcasted on
880 the GSM network. It will only collect one frequency at the time,
881 while a typical phone will be using several frequencies, and not all
882 phones will be using the frequencies tracked by the grgsm_livemod
883 program. Also, there is a lot of radio chatter being ignored by the
884 simple_IMSI-catcher script, which would be collected by extending the
885 parser code. I wonder if gr-gsm can be set up to listen to more than
886 one frequency?&lt;/p&gt;
887 </description>
888 </item>
889
890 <item>
891 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
892 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
893 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
894 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
895 <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;
896
897 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
898 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
899 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
900 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
901 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
902 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
903 price. The book is also available for download in electronic form as
904 PDF, EPUB and Mobipocket, as can be
905 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
906 as a web page&lt;/a&gt;.&lt;/p&gt;
907
908 &lt;p&gt;This is the second book I publish (the first was the book
909 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
910 in
911 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
912 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
913 and
914 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
915 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
916 project. I hope
917 &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
918 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
919 </description>
920 </item>
921
922 <item>
923 <title>Når nynorskoversettelsen svikter til eksamen...</title>
924 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
925 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
926 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
927 <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
928 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
929 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
930 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
931 på om den fri oversetterløsningen
932 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
933 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
934
935 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
936
937 &lt;blockquote&gt;
938 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
939 rolle og muligheter til å håndtere internasjonale utfordringer, som
940 for eksempel flykningekrisen.&lt;/p&gt;
941
942 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
943 på temaet:&lt;/p&gt;
944 &lt;ol&gt;
945 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
946 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
947 &lt;/ol&gt;
948
949 &lt;/blockquote&gt;
950
951 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
952
953 &lt;blockquote&gt;
954 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
955 andre aktørar og høve til å handtera internasjonale utfordringar, som
956 til dømes *flykningekrisen.&lt;/p&gt;
957
958 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
959 temaet:&lt;/p&gt;
960
961 &lt;ol&gt;
962 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
963 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
964 &lt;/ol&gt;
965
966 &lt;/blockquote&gt;
967
968 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
969 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
970 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
971 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
972 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
973 det er kanskje flisespikking. Det understreker vel bare at det alltid
974 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
975 </description>
976 </item>
977
978 <item>
979 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
980 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
981 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
982 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
983 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
984 computers at the time, I often needed a way to detect if the machine
985 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
986 file or directory affected by the hang, the process (and possibly the
987 shell) will hang too. So you want to be able to detect this without
988 risking the detection process getting stuck too. It has not been
989 obvious how to do this. When the hang has lasted a while, it is
990 possible to find messages like these in dmesg:&lt;/p&gt;
991
992 &lt;p&gt;&lt;blockquote&gt;
993 nfs: server nfsserver not responding, still trying
994 &lt;br&gt;nfs: server nfsserver OK
995 &lt;/blockquote&gt;&lt;/p&gt;
996
997 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
998 be sure looking in dmesg is going to work. If there are lots of other
999 messages in dmesg the lines might have rotated out of site before they
1000 are noticed.&lt;/p&gt;
1001
1002 &lt;p&gt;While reading through the nfs client implementation in linux kernel
1003 code, I came across some statistics that seem to give a way to detect
1004 it. The om_timeouts sunrpc value in the kernel will increase every
1005 time the above log entry is inserted into dmesg. And after digging a
1006 bit further, I discovered that this value show up in
1007 /proc/self/mountstats on Linux.&lt;/p&gt;
1008
1009 &lt;p&gt;The mountstats content seem to be shared between files using the
1010 same file system context, so it is enough to check one of the
1011 mountstats files to get the state of the mount point for the machine.
1012 I assume this will not show lazy umounted NFS points, nor NFS mount
1013 points in a different process context (ie with a different filesystem
1014 view), but that does not worry me.&lt;/p&gt;
1015
1016 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
1017
1018 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1019 [...]
1020 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1021 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
1022 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
1023 age: 7863311
1024 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
1025 sec: flavor=1,pseudoflavor=1
1026 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
1027 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1028 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
1029 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1030 per-op statistics
1031 NULL: 0 0 0 0 0 0 0 0
1032 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1033 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
1034 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1035 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1036 READLINK: 125 125 0 20472 18620 0 1112 1118
1037 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1038 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1039 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
1040 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
1041 SYMLINK: 903 903 0 233428 245488 6 5865 5917
1042 MKNOD: 80 80 0 20148 21760 0 299 304
1043 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
1044 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
1045 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
1046 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
1047 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1048 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1049 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
1050 FSINFO: 2 2 0 232 328 0 1 1
1051 PATHCONF: 1 1 0 116 140 0 0 0
1052 COMMIT: 0 0 0 0 0 0 0 0
1053
1054 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1055 [...]
1056 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1057
1058 &lt;p&gt;The key number to look at is the third number in the per-op list.
1059 It is the number of NFS timeouts experiences per file system
1060 operation. Here 22 write timeouts and 5 access timeouts. If these
1061 numbers are increasing, I believe the machine is experiencing NFS
1062 hang. Unfortunately the timeout value do not start to increase right
1063 away. The NFS operations need to time out first, and this can take a
1064 while. The exact timeout value depend on the setup. For example the
1065 defaults for TCP and UDP mount points are quite different, and the
1066 timeout value is affected by the soft, hard, timeo and retrans NFS
1067 mount options.&lt;/p&gt;
1068
1069 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
1070 Enterprise Linux for getting the timeout count is to peek in /proc/.
1071 But according to
1072 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
1073 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
1074 command can be used to get these timeout values. But this do not work
1075 on Linux, as far as I can tell. I
1076 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
1077 but have not seen any replies yet.&lt;/p&gt;
1078
1079 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
1080 experiencing NFS hangs? Is there a way to detect which processes are
1081 affected? Is there a way to get the NFS mount going quickly once the
1082 network problem causing the NFS hang has been cleared? I would very
1083 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
1084 </description>
1085 </item>
1086
1087 <item>
1088 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
1089 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
1090 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
1091 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
1092 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
1093 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1094 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
1095 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1096 we are working on the proof reading to ensure consistent language and
1097 use of correct computer science terms. The plan is to make the book
1098 available on paper, as well as in electronic form. For that to
1099 happen, the proof reading must be completed and all the figures need
1100 to be translated. If you want to help out, get in touch.&lt;/p&gt;
1101
1102 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
1103
1104 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
1105 pages) of the book created every morning is available for
1106 proofreading. If you find any errors, please
1107 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
1108 Weblate and correct the error&lt;/a&gt;. The
1109 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
1110 of the translation including figures&lt;/a&gt; is a useful source for those
1111 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
1112 </description>
1113 </item>
1114
1115 <item>
1116 <title>Unlimited randomness with the ChaosKey?</title>
1117 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
1118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
1119 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
1120 <description>&lt;p&gt;A few days ago I ordered a small batch of
1121 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
1122 USB dongle for generating entropy created by Bdale Garbee and Keith
1123 Packard. Yesterday it arrived, and I am very happy to report that it
1124 work great! According to its designers, to get it to work out of the
1125 box, you need the Linux kernel version 4.1 or later. I tested on a
1126 Debian Stretch machine (kernel version 4.9), and there it worked just
1127 fine, increasing the available entropy very quickly. I wrote a small
1128 test oneliner to test. It first print the current entropy level,
1129 drain /dev/random, and then print the entropy level for five seconds.
1130 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
1131
1132 &lt;blockquote&gt;&lt;pre&gt;
1133 % cat /proc/sys/kernel/random/entropy_avail; \
1134 dd bs=1M if=/dev/random of=/dev/null count=1; \
1135 for n in $(seq 1 5); do \
1136 cat /proc/sys/kernel/random/entropy_avail; \
1137 sleep 1; \
1138 done
1139 300
1140 0+1 oppføringer inn
1141 0+1 oppføringer ut
1142 28 byte kopiert, 0,000264565 s, 106 kB/s
1143 4
1144 8
1145 12
1146 17
1147 21
1148 %
1149 &lt;/pre&gt;&lt;/blockquote&gt;
1150
1151 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
1152 application requiring random bits (like a HTTPS enabled web server)
1153 will halt and wait for more entrpy. And here is the situation with
1154 the ChaosKey inserted:&lt;/p&gt;
1155
1156 &lt;blockquote&gt;&lt;pre&gt;
1157 % cat /proc/sys/kernel/random/entropy_avail; \
1158 dd bs=1M if=/dev/random of=/dev/null count=1; \
1159 for n in $(seq 1 5); do \
1160 cat /proc/sys/kernel/random/entropy_avail; \
1161 sleep 1; \
1162 done
1163 1079
1164 0+1 oppføringer inn
1165 0+1 oppføringer ut
1166 104 byte kopiert, 0,000487647 s, 213 kB/s
1167 433
1168 1028
1169 1031
1170 1035
1171 1038
1172 %
1173 &lt;/pre&gt;&lt;/blockquote&gt;
1174
1175 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
1176 someone want to buy one here in Norway. :)&lt;/p&gt;
1177
1178 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
1179 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
1180 recording illuminating&lt;/a&gt;. It explains exactly what the source of
1181 randomness is, if you are unable to spot it from the schema drawing
1182 available from the ChaosKey web site linked at the start of this blog
1183 post.&lt;/p&gt;
1184 </description>
1185 </item>
1186
1187 <item>
1188 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
1189 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
1190 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
1191 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
1192 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
1193 web servers, and who own the network equipment it is flowing through?
1194 It is possible to get a glimpse of this from using traceroute, but it
1195 is hard to find all the details. Many years ago, I wrote a system to
1196 map the Norwegian Internet (trying to figure out if our plans for a
1197 network game service would get low enough latency, and who we needed
1198 to talk to about setting up game servers close to the users. Back
1199 then I used traceroute output from many locations (I asked my friends
1200 to run a script and send me their traceroute output) to create the
1201 graph and the map. The output from traceroute typically look like
1202 this:
1203
1204 &lt;p&gt;&lt;pre&gt;
1205 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
1206 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
1207 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
1208 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
1209 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
1210 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
1211 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
1212 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
1213 8 * * *
1214 9 * * *
1215 [...]
1216 &lt;/pre&gt;&lt;/p&gt;
1217
1218 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
1219 network equipment involved in getting the data traffic from me to the
1220 www.stortinget.no server, and how long it took in milliseconds for a
1221 package to reach the equipment and return to me. Three packages are
1222 sent, and some times the packages do not follow the same path. This
1223 is shown for hop 5, where three different IP addresses replied to the
1224 traceroute request.&lt;/p&gt;
1225
1226 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
1227 implementations I use are traceroute (using ICMP packages) mtr (can do
1228 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1229 traceroute and a lot of other capabilities). All of them are easily
1230 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
1231
1232 &lt;p&gt;This time around, I wanted to know the geographic location of
1233 different route points, to visualize how visiting a web page spread
1234 information about the visit to a lot of servers around the globe. The
1235 background is that a web site today often will ask the browser to get
1236 from many servers the parts (for example HTML, JSON, fonts,
1237 JavaScript, CSS, video) required to display the content. This will
1238 leak information about the visit to those controlling these servers
1239 and anyone able to peek at the data traffic passing by (like your ISP,
1240 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
1241
1242 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
1243 www.stortinget.no. It is read daily by all members of parliament and
1244 their staff, as well as political journalists, activits and many other
1245 citizens of Norway. A visit to the www.stortinget.no web site will
1246 ask your browser to contact 8 other servers: ajax.googleapis.com,
1247 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1248 stats.g.doubleclick.net, www.google-analytics.com,
1249 www.googletagmanager.com and www.netigate.se. I extracted this by
1250 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
1251 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1252 render the page (in HAR format using
1253 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
1254 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
1255 to do this). My goal is to visualize network traces to all IP
1256 addresses behind these DNS names, do show where visitors personal
1257 information is spread when visiting the page.&lt;/p&gt;
1258
1259 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
1260 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;
1261
1262 &lt;p&gt;When I had a look around for options, I could not find any good
1263 free software tools to do this, and decided I needed my own traceroute
1264 wrapper outputting KML based on locations looked up using GeoIP. KML
1265 is easy to work with and easy to generate, and understood by several
1266 of the GIS tools I have available. I got good help from by NUUG
1267 colleague Anders Einar with this, and the result can be seen in
1268 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
1269 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
1270 free GeoIP databases I could find (and the for-pay databases my
1271 friends had access to) is not up to the task. The IP addresses of
1272 central Internet infrastructure would typically be placed near the
1273 controlling companies main office, and not where the router is really
1274 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
1275 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
1276
1277 &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
1278 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;
1279
1280 &lt;p&gt;I also had a look at the visual traceroute graph created by
1281 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1282 showing IP network ownership (aka AS owner) for the IP address in
1283 question.
1284 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1285 graph display a lot of useful information about the traceroute in SVG
1286 format&lt;/a&gt;, and give a good indication on who control the network
1287 equipment involved, but it do not include geolocation. This graph
1288 make it possible to see the information is made available at least for
1289 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1290 3 Communications and NetDNA.&lt;/p&gt;
1291
1292 &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
1293 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;
1294
1295 &lt;p&gt;In the process, I came across the
1296 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1297 Salim Gasmi. Its methology of combining guesses based on DNS names,
1298 various location databases and finally use latecy times to rule out
1299 candidate locations seemed to do a very good job of guessing correct
1300 geolocation. But it could only do one trace at the time, did not have
1301 a sensor in Norway and did not make the geolocations easily available
1302 for postprocessing. So I contacted the developer and asked if he
1303 would be willing to share the code (he refused until he had time to
1304 clean it up), but he was interested in providing the geolocations in a
1305 machine readable format, and willing to set up a sensor in Norway. So
1306 since yesterday, it is possible to run traces from Norway in this
1307 service thanks to a sensor node set up by
1308 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1309 trace in KML format for further processing.&lt;/p&gt;
1310
1311 &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
1312 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;
1313
1314 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1315 Denmark, Germany, Holland and Ireland. Plenty of places where the
1316 Snowden confirmations verified the traffic is read by various actors
1317 without your best interest as their top priority.&lt;/p&gt;
1318
1319 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1320 over all the hosts behind the urls imported by www.stortinget.no and
1321 ask for the KML file from GeoTraceroute, and create a combined KML
1322 file with all the traces (unfortunately only one of the IP addresses
1323 behind the DNS name is traced this time. To get them all, one would
1324 have to request traces using IP number instead of DNS names from
1325 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1326
1327 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1328 the IP traffic moves and who control the boxes involved in moving it.
1329 And every time the link crosses for example the Swedish border, we can
1330 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1331 Britain and NSA in USA and cables around the globe. (Hm, what should
1332 we tell them? :) Keep that in mind if you ever send anything
1333 unencrypted over the Internet.&lt;/p&gt;
1334
1335 &lt;p&gt;PS: KML files are drawn using
1336 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1337 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1338 Marble. There are heaps of other options too.&lt;/p&gt;
1339
1340 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1341 activities, please send Bitcoin donations to my address
1342 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1343 </description>
1344 </item>
1345
1346 <item>
1347 <title>Appstream just learned how to map hardware to packages too!</title>
1348 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1349 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1350 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1351 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1352 readers probably know, I have been working on the
1353 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1354 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1355 it easier for users to figure out what to install to get a given piece
1356 of hardware to work in Debian, and a key part of this system is a way
1357 to map hardware to packages. Isenkram have its own mapping database,
1358 and also uses data provided by each package using the AppStream
1359 metadata format. And today,
1360 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1361 Debian learned to look up hardware the same way Isenkram is doing it,
1362 ie using fnmatch():&lt;/p&gt;
1363
1364 &lt;p&gt;&lt;pre&gt;
1365 % appstreamcli what-provides modalias \
1366 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1367 Identifier: pymissile [generic]
1368 Name: pymissile
1369 Summary: Control original Striker USB Missile Launcher
1370 Package: pymissile
1371 % appstreamcli what-provides modalias usb:v0694p0002d0000
1372 Identifier: libnxt [generic]
1373 Name: libnxt
1374 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1375 Package: libnxt
1376 ---
1377 Identifier: t2n [generic]
1378 Name: t2n
1379 Summary: Simple command-line tool for Lego NXT
1380 Package: t2n
1381 ---
1382 Identifier: python-nxt [generic]
1383 Name: python-nxt
1384 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1385 Package: python-nxt
1386 ---
1387 Identifier: nbc [generic]
1388 Name: nbc
1389 Summary: C compiler for LEGO Mindstorms NXT bricks
1390 Package: nbc
1391 %
1392 &lt;/pre&gt;&lt;/p&gt;
1393
1394 &lt;p&gt;A similar query can be done using the combined AppStream and
1395 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1396
1397 &lt;p&gt;&lt;pre&gt;
1398 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1399 pymissile
1400 % isenkram-lookup usb:v0694p0002d0000
1401 libnxt
1402 nbc
1403 python-nxt
1404 t2n
1405 %
1406 &lt;/pre&gt;&lt;/p&gt;
1407
1408 &lt;p&gt;You can find modalias values relevant for your machine using
1409 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1410
1411 &lt;p&gt;If you want to make this system a success and help Debian users
1412 make the most of the hardware they have, please
1413 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1414 AppStream metadata for your package following the guidelines&lt;/a&gt;
1415 documented in the wiki. So far only 11 packages provide such
1416 information, among the several hundred hardware specific packages in
1417 Debian. The Isenkram database on the other hand contain 101 packages,
1418 mostly related to USB dongles. Most of the packages with hardware
1419 mapping in AppStream are LEGO Mindstorms related, because I have, as
1420 part of my involvement in
1421 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1422 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1423 complete set of packages in Debian for that particular hardware. The
1424 team also got a nice Christmas present today. The
1425 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1426 package&lt;/a&gt; made it into Debian. With this package in place, it is
1427 now possible to use the LEGO Mindstorms NXT unit with only free
1428 software, as the nxt-firmware package contain the source and firmware
1429 binaries for the NXT brick.&lt;/p&gt;
1430
1431 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1432 activities, please send Bitcoin donations to my address
1433 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1434 </description>
1435 </item>
1436
1437 <item>
1438 <title>Isenkram updated with a lot more hardware-package mappings</title>
1439 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1440 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1441 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1442 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1443 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1444 and install packages to get your hardware dongles to work, is still
1445 going strong. It is a system to look up the hardware present on or
1446 connected to the current system, and map the hardware to Debian
1447 packages. It can either be done using the tools in isenkram-cli or
1448 using the user space daemon in the isenkram package. The latter will
1449 notify you, when inserting new hardware, about what packages to
1450 install to get the dongle working. It will even provide a button to
1451 click on to ask packagekit to install the packages.&lt;/p&gt;
1452
1453 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1454
1455 &lt;p&gt;&lt;pre&gt;
1456 % isenkram-lookup
1457 bluez
1458 cheese
1459 ethtool
1460 fprintd
1461 fprintd-demo
1462 gkrellm-thinkbat
1463 hdapsd
1464 libpam-fprintd
1465 pidgin-blinklight
1466 thinkfan
1467 tlp
1468 tp-smapi-dkms
1469 tp-smapi-source
1470 tpb
1471 %
1472 &lt;/pre&gt;&lt;/p&gt;
1473
1474 &lt;p&gt;It can also list the firware package providing firmware requested
1475 by the load kernel modules, which in my case is an empty list because
1476 I have all the firmware my machine need:
1477
1478 &lt;p&gt;&lt;pre&gt;
1479 % /usr/sbin/isenkram-autoinstall-firmware -l
1480 info: did not find any firmware files requested by loaded kernel modules. exiting
1481 %
1482 &lt;/pre&gt;&lt;/p&gt;
1483
1484 &lt;p&gt;The last few days I had a look at several of the around 250
1485 packages in Debian with udev rules. These seem like good candidates
1486 to install when a given hardware dongle is inserted, and I found
1487 several that should be proposed by isenkram. I have not had time to
1488 check all of them, but am happy to report that now there are 97
1489 packages packages mapped to hardware by Isenkram. 11 of these
1490 packages provide hardware mapping using AppStream, while the rest are
1491 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1492
1493 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1494 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1495 support using AppStream, for everyone to use:&lt;/p&gt;
1496
1497 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1498 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1499 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1500 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1501 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1502 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1503 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1504 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1505 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1506 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1507 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1508 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1509 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1510 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1511 pcscd, pidgin-blinklight, printer-driver-splix,
1512 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1513 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1514 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1515 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1516 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1517 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1518 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1519 xserver-xorg-video-vmware, yubikey-personalization and
1520 zd1211-firmware&lt;/p&gt;
1521
1522 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1523 bug report against the isenkram-cli package, and ask the package
1524 maintainer to
1525 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1526 metadata according to the guidelines&lt;/a&gt; to provide the information
1527 for everyone. In time, I hope to get rid of the isenkram specific
1528 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1529
1530 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1531 much hardware, and suggest that the package with with any ethernet
1532 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1533 the details. I hope the maintainer find time to address it soon. In
1534 the mean time I provide an override in isenkram.&lt;/p&gt;
1535 </description>
1536 </item>
1537
1538 <item>
1539 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1540 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1541 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1542 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1543 <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;
1544
1545 &lt;p&gt;In my early years, I played
1546 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1547 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1548 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1549 original Elite game was available on Commodore 64 and the IBM PC
1550 edition I played had a 64 KB executable. I am still impressed today
1551 that the authors managed to squeeze both a 3D engine and details about
1552 more than 2000 planet systems across 7 galaxies into a binary so
1553 small.&lt;/p&gt;
1554
1555 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1556 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1557 really have time to test it properly until a few days ago. It was
1558 great to discover that my old knowledge about trading routes were
1559 still valid. But my fighting and flying abilities were gone, so I had
1560 to retrain to be able to dock on a space station. And I am still not
1561 able to make much resistance when I am attacked by pirates, so I
1562 bougth and mounted the most powerful laser in the rear to be able to
1563 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1564
1565 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1566 everything on my own, and I had long lists of prices seen on different
1567 planets to be able to decide where to trade what. This time I had the
1568 advantages of the
1569 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1570 where information about each planet is easily available with common
1571 price ranges and suggested trading routes. This improved my ability
1572 to earn money and I have been able to earn enough to buy a lot of
1573 useful equipent in a few days. I believe I originally played for
1574 months before I could get a docking computer, while now I could get it
1575 after less then a week.&lt;/p&gt;
1576
1577 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1578 space, you should try out Oolite. It is available for Linux, MacOSX
1579 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1580
1581 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1582 activities, please send Bitcoin donations to my address
1583 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1584 </description>
1585 </item>
1586
1587 <item>
1588 <title>Quicker Debian installations using eatmydata</title>
1589 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1590 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1591 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1592 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1593 installation system, observing how using
1594 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1595 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1596 speedup around 20-40 percent for Debian Edu, where we install around
1597 1000 packages from within the installer. The eatmydata package
1598 provide a way to disable/delay file system flushing. This is a bit
1599 risky in the general case, as files that should be stored on disk will
1600 stay only in memory a bit longer than expected, causing problems if a
1601 machine crashes at an inconvenient time. But for an installation, if
1602 the machine crashes during installation the process is normally
1603 restarted, and avoiding disk operations as much as possible to speed
1604 up the process make perfect sense.
1605
1606 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1607 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1608 but did not have time to push it any further. But a few months ago I
1609 picked it up again and worked with the libeatmydata package maintainer
1610 Mattia Rizzolo to make it easier for everyone to get this installation
1611 speedup in Debian. Thanks to our cooperation There is now an
1612 eatmydata-udeb package in Debian testing and unstable, and simply
1613 enabling/installing it in debian-installer (d-i) is enough to get the
1614 quicker installations. It can be enabled using preseeding. The
1615 following untested kernel argument should do the trick:&lt;/p&gt;
1616
1617 &lt;blockquote&gt;&lt;pre&gt;
1618 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1619 &lt;/pre&gt;&lt;/blockquote&gt;
1620
1621 &lt;p&gt;This should ask d-i to install the package inside the d-i
1622 environment early in the installation sequence. Having it installed
1623 in d-i in turn will make sure the relevant scripts are called just
1624 after debootstrap filled /target/ with the freshly installed Debian
1625 system to configure apt to run dpkg with eatmydata. This is enough to
1626 speed up the installation process. There is a proposal to
1627 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1628 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1629 tested its impact.&lt;/p&gt;
1630
1631 </description>
1632 </item>
1633
1634 <item>
1635 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1636 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1637 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1638 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1639 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1640 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1641 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1642 elever over det ganske land skal levere inn hvert år. Det mange ikke
1643 vet er at selv om de kommersielle alternativene
1644 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1645 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1646 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1647 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1648 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1649 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1650 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1651 nynorsk, og få den automatoversatt til det andre skriftspråket.
1652 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1653 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1654 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1655 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1656 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1657 teksten din i webskjemaet der.
1658
1659 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1660 teknologien kan du enten installere pakken
1661 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1662 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1663 api.apertium.org. Se
1664 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1665 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1666 denne teksten som ble skrevet på bokmål over maskinoversatt til
1667 nynorsk.&lt;/p&gt;
1668
1669 &lt;hr/&gt;
1670
1671 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1672 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1673 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1674 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1675 veit er at sjølv om dei kommersielle alternativa
1676 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1677 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1678 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1679 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1680 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1681 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1682 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1683 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1684 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1685 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1686 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1687 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1688 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1689 teksta di i *webskjemaet der.
1690
1691 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1692 teknologien kan du anten installera pakken
1693 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1694 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1695 *api.*apertium.org. Sjå
1696 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1697 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1698 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1699 nynorsk.&lt;/p&gt;
1700 </description>
1701 </item>
1702
1703 <item>
1704 <title>Coz profiler for multi-threaded software is now in Debian</title>
1705 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1707 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1708 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1709 profiler able to run benchmarking experiments on the instrumented
1710 multi-threaded program, finally
1711 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1712 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1713 months since
1714 &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
1715 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1716 it suitable for Debian. There are still issues with clang
1717 compatibility, inline assembly only working x86 and minimized
1718 JavaScript libraries.&lt;/p&gt;
1719
1720 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1721
1722 &lt;p&gt;&lt;blockquote&gt;
1723 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1724 &lt;/blockquote&gt;&lt;/p&gt;
1725
1726 &lt;p&gt;This will produce a profile.coz file in the current working
1727 directory with the profiling information. This is then given to a
1728 JavaScript application provided in the package and available from
1729 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1730 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1731
1732 &lt;p&gt;&lt;blockquote&gt;
1733 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1734 &lt;/blockquote&gt;&lt;/p&gt;
1735
1736 &lt;p&gt;See the project home page and the
1737 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1738 ;login: article on Coz&lt;/a&gt; for more information on how it is
1739 working.&lt;/p&gt;
1740 </description>
1741 </item>
1742
1743 <item>
1744 <title>My own self balancing Lego Segway</title>
1745 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1746 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1747 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1748 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1749 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1750 present. It had been on my wishlist for a while, because I wanted to
1751 build a Segway like balancing lego robot. I had already built
1752 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1753 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1754 NXT kit as the balance sensor, but it was not working very well. It
1755 could balance for a while, but was very sensitive to the light
1756 condition in the room and the reflective properties of the surface and
1757 would fall over after a short while. I wanted something more robust,
1758 and had
1759 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1760 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1761 wishlist for some years before it suddenly showed up as a gift from my
1762 loved ones. :)&lt;/p&gt;
1763
1764 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1765 since then. But that changed some days ago, when I was searching for
1766 lego segway information and came across a recipe from HiTechnic for
1767 building
1768 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1769 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1770 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1771 code&lt;/a&gt; was included, so it was just a question of putting it all
1772 together. And thanks to the great work of many Debian developers, the
1773 compiler needed to build the source for the NXT is already included in
1774 Debian, so I was read to go in less than an hour. The resulting robot
1775 do not look very impressive in its simplicity:&lt;/p&gt;
1776
1777 &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;
1778
1779 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
1780 design from HiTechnic, I had to comment out the last task
1781 (taskControl). I simply placed /* and */ around it get the program
1782 working without that sensor present. Now it balances just fine until
1783 the battery status run low:&lt;/p&gt;
1784
1785 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
1786 &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;
1787 &lt;/video&gt;&lt;/p&gt;
1788
1789 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
1790 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
1791
1792 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
1793 they need to work with LEGO in Debian and all our derivative
1794 distributions like Ubuntu, check out
1795 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
1796 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
1797 RCX and NXT controller (no EV3), and would like to make sure the
1798 Debian tools needed to program the systems I own work as they
1799 should.&lt;/p&gt;
1800 </description>
1801 </item>
1802
1803 <item>
1804 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
1805 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
1806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
1807 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
1808 <description>&lt;p&gt;In July
1809 &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
1810 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
1811 the ability to receive SMS messages (aka without a cell phone). It is
1812 time to share some experiences and provide an updated setup.&lt;/p&gt;
1813
1814 &lt;p&gt;The Signal app have worked fine for several months now, and I use
1815 it regularly to chat with my loved ones. I had a major snag at the
1816 end of my summer vacation, when the the app completely forgot my
1817 setup, identity and keys. The reason behind this major mess was
1818 running out of disk space. To avoid that ever happening again I have
1819 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
1820 roll back to an earlier version if the files are wiped by mistake. I
1821 had to use it once after introducing the git backup. When rolling
1822 back to an earlier version, one need to use the &#39;reset session&#39; option
1823 in Signal to get going, and notify the people you talk with about the
1824 problem. I assume there is some sequence number tracking in the
1825 protocol to detect rollback attacks. The git repository is rather big
1826 (674 MiB so far), but I have not tried to figure out if some of the
1827 content can be added to a .gitignore file due to lack of spare
1828 time.&lt;/p&gt;
1829
1830 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
1831 make it impossible to send messages using Signal. I could still
1832 receive them, but had to patch the code with a new timestamp to send.
1833 I believe the timeout is added by the developers to force people to
1834 upgrade to the latest version of the app, even when there is no
1835 protocol changes, to reduce the version skew among the user base and
1836 thus try to keep the number of support requests down.&lt;/p&gt;
1837
1838 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
1839 making the old patch fail to apply cleanly. Below is an updated
1840 patch, including the shell wrapper I use to start Signal. The
1841 original version required a new user to locate the JavaScript console
1842 and call a function from there. I got help from a friend with more
1843 JavaScript knowledge than me to modify the code to provide a GUI
1844 button instead. This mean that to get started you just need to run
1845 the wrapper and click the &#39;Register without mobile phone&#39; to get going
1846 now. I&#39;ve also modified the timeout code to always set it to 90 days
1847 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
1848
1849 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
1850
1851 &lt;ol&gt;
1852
1853 &lt;li&gt;First, install required packages to get the source code and the
1854 browser you need. Signal only work with Chrome/Chromium, as far as I
1855 know, so you need to install it.
1856
1857 &lt;pre&gt;
1858 apt install git tor chromium
1859 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1860 &lt;/pre&gt;&lt;/li&gt;
1861
1862 &lt;li&gt;Modify the source code using command listed in the the patch
1863 block below.&lt;/li&gt;
1864
1865 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
1866 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
1867
1868 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
1869 number you can receive calls to the next minute, receive the
1870 verification code and enter it into the form field and press
1871 &#39;Register&#39;. Note, the phone number you use will be user Signal
1872 username, ie the way others can find you on Signal.&lt;/li&gt;
1873
1874 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
1875 not show up in the contact list until you restart Signal, and there is
1876 no way to assign names to Contacts. There is also no way to create or
1877 update chat groups. I suspect this is because the web app do not have
1878 a associated contact database.&lt;/li&gt;
1879
1880 &lt;/ol&gt;
1881
1882 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
1883 main author moxie0 reject federation and accept dependencies to major
1884 corporations like Google (part of the code is fetched from Google) and
1885 Amazon (the central coordination point is owned by Amazon). See for
1886 example
1887 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
1888 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
1889 view on these issues. But the network effect is strong in this case,
1890 and several of the people I want to communicate with already use
1891 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
1892 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
1893 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
1894 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
1895 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
1896 working on Debian Stable.&lt;/p&gt;
1897
1898 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
1899 working. It switch to the production servers, disable to timeout,
1900 make registration easier and add the shell wrapper:&lt;/p&gt;
1901
1902 &lt;pre&gt;
1903 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
1904 diff --git a/js/background.js b/js/background.js
1905 index 24b4c1d..579345f 100644
1906 --- a/js/background.js
1907 +++ b/js/background.js
1908 @@ -33,9 +33,9 @@
1909 });
1910 });
1911
1912 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1913 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
1914 var SERVER_PORTS = [80, 4433, 8443];
1915 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1916 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1917 var messageReceiver;
1918 window.getSocketStatus = function() {
1919 if (messageReceiver) {
1920 diff --git a/js/expire.js b/js/expire.js
1921 index 639aeae..beb91c3 100644
1922 --- a/js/expire.js
1923 +++ b/js/expire.js
1924 @@ -1,6 +1,6 @@
1925 ;(function() {
1926 &#39;use strict&#39;;
1927 - var BUILD_EXPIRATION = 0;
1928 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
1929
1930 window.extension = window.extension || {};
1931
1932 diff --git a/js/views/install_view.js b/js/views/install_view.js
1933 index 7816f4f..1d6233b 100644
1934 --- a/js/views/install_view.js
1935 +++ b/js/views/install_view.js
1936 @@ -38,7 +38,8 @@
1937 return {
1938 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
1939 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
1940 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
1941 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
1942 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
1943 };
1944 },
1945 clearQR: function() {
1946 diff --git a/options.html b/options.html
1947 index dc0f28e..8d709f6 100644
1948 --- a/options.html
1949 +++ b/options.html
1950 @@ -14,7 +14,10 @@
1951 &amp;lt;div class=&#39;nav&#39;&gt;
1952 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
1953 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
1954 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
1955 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
1956 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
1957 +
1958 + &amp;lt;/div&gt;
1959 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
1960 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
1961 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
1962 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
1963 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
1964 @@ -0,0 +1,12 @@
1965 +#!/bin/sh
1966 +set -e
1967 +cd $(dirname $0)
1968 +mkdir -p userdata
1969 +userdata=&quot;`pwd`/userdata&quot;
1970 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
1971 + (cd $userdata &amp;&amp; git init)
1972 +fi
1973 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
1974 +exec chromium \
1975 + --proxy-server=&quot;socks://localhost:9050&quot; \
1976 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1977 EOF
1978 chmod a+rx run-signal-app
1979 &lt;/pre&gt;
1980
1981 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1982 activities, please send Bitcoin donations to my address
1983 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1984 </description>
1985 </item>
1986
1987 <item>
1988 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
1989 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
1990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
1991 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
1992 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1993 system&lt;/a&gt; provide a practical and easy way to figure out which
1994 packages support the hardware in a given machine. The command line
1995 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
1996 convenient way to list and install packages relevant for the current
1997 hardware during system installation, both user space packages and
1998 firmware packages. The GUI background daemon on the other hand provide
1999 a pop-up proposing to install packages when a new dongle is inserted
2000 while using the computer. For example, if you plug in a smart card
2001 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
2002 that package isn&#39;t already installed, and if you plug in a USB video
2003 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
2004 cheese is currently missing. This already work just fine.&lt;/p&gt;
2005
2006 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
2007 package names. When I started no such database existed in Debian, so
2008 I made my own data set and included it with the isenkram package and
2009 made isenkram fetch the latest version of this database from git using
2010 http. This way the isenkram users would get updated package proposals
2011 as soon as I learned more about hardware related packages.&lt;/p&gt;
2012
2013 &lt;p&gt;The hardware is identified using modalias strings. The modalias
2014 design is from the Linux kernel where most hardware descriptors are
2015 made available as a strings that can be matched using filename style
2016 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2017 identifiers.&lt;/p&gt;
2018
2019 &lt;p&gt;The downside to the Isenkram specific database is that there is no
2020 information about relevant distribution / Debian version, making
2021 isenkram propose obsolete packages too. But along came AppStream, a
2022 cross distribution mechanism to store and collect metadata about
2023 software packages. When I heard about the proposal, I contacted the
2024 people involved and suggested to add a hardware matching rule using
2025 modalias strings in the specification, to be able to use AppStream for
2026 mapping hardware to packages. This idea was accepted and AppStream is
2027 now a great way for a package to announce the hardware it support in a
2028 distribution neutral way. I wrote
2029 &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
2030 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
2031 December. If you have a hardware related package in Debian, please
2032 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
2033
2034 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
2035 RCX or NXT unit, announce this support using AppStream. The effect is
2036 that when you insert such LEGO robot controller into your Debian
2037 machine, Isenkram will propose to install the packages needed to get
2038 it working. The intention is that this should allow the local user to
2039 start programming his robot controller right away without having to
2040 guess what packages to use or which permissions to fix.&lt;/p&gt;
2041
2042 &lt;p&gt;But when I sat down with my son the other day to program our NXT
2043 unit using his Debian Stretch computer, I discovered something
2044 annoying. The local console user (ie my son) did not get access to
2045 the USB device for programming the unit. This used to work, but no
2046 longer in Jessie and Stretch. After some investigation and asking
2047 around on #debian-devel, I discovered that this was because udev had
2048 changed the mechanism used to grant access to local devices. The
2049 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
2050 no longer applied, because LDAP users no longer was added to the
2051 plugdev group during login. Michael Biebl told me that this method
2052 was obsolete and the new method used ACLs instead. This was good
2053 news, as the plugdev mechanism is a mess when using a remote user
2054 directory like LDAP. Using ACLs would make sure a user lost device
2055 access when she logged out, even if the user left behind a background
2056 process which would retain the plugdev membership with the ConsoleKit
2057 setup. Armed with this knowledge I moved on to fix the access problem
2058 for the LEGO Mindstorms related packages.&lt;/p&gt;
2059
2060 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
2061 applied directly for a device, or is applied in
2062 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
2063 LEGO Mindstorms udev rules did not have a class, I decided to add the
2064 tag directly in the udev rules files included in the packages. Here
2065 is one example. For the nqc C compiler for the RCX, the
2066 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
2067
2068 &lt;p&gt;&lt;pre&gt;
2069 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
2070 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
2071 &lt;/pre&gt;&lt;/p&gt;
2072
2073 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
2074 packages using plugdev in their /lib/udev/rules.d/ files should be
2075 changed to use this tag (either directly or indirectly via
2076 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
2077 to detect this?&lt;/p&gt;
2078
2079 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
2080 It is unclear to me if the uaccess tag is an internal implementation
2081 detail like the udev-acl tag used by
2082 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
2083 indirect method is the preferred way. Michael
2084 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
2085 documentation from the systemd project&lt;/a&gt; and I hope it will make
2086 this clearer. For now I use the generic classes when they exist and
2087 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
2088 directly if no such class exist.&lt;/p&gt;
2089
2090 &lt;p&gt;To learn more about the isenkram system, please check out
2091 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2092 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2093
2094 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
2095 please join us on our IRC channel
2096 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
2097 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
2098 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
2099 list is not yet created, but we are working on it. :)&lt;/p&gt;
2100
2101 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2102 activities, please send Bitcoin donations to my address
2103 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2104 </description>
2105 </item>
2106
2107 <item>
2108 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
2109 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
2110 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
2111 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
2112 <description>&lt;p&gt;In April we
2113 &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
2114 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
2115 how to set up and administrate a Debian system. Today I am happy to
2116 report that the first draft is now publicly available. You can find
2117 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
2118 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
2119 eight chapters have a first draft translation, and we are working on
2120 proofreading the content. If you want to help out, please start
2121 contributing using
2122 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2123 hosted weblate project page&lt;/a&gt;, and get in touch using
2124 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2125 translators mailing list&lt;/a&gt;. Please also check out
2126 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2127 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
2128 and update weblate if you find errors.&lt;/p&gt;
2129
2130 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
2131 electronic form.&lt;/p&gt;
2132 </description>
2133 </item>
2134
2135 <item>
2136 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
2137 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
2138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
2139 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
2140 <description>&lt;p&gt;This summer, I read a great article
2141 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
2142 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
2143 how to profile multi-threaded programs. It presented a system for
2144 profiling software by running experiences in the running program,
2145 testing how run time performance is affected by &quot;speeding up&quot; parts of
2146 the code to various degrees compared to a normal run. It does this by
2147 slowing down parallel threads while the &quot;faster up&quot; code is running
2148 and measure how this affect processing time. The processing time is
2149 measured using probes inserted into the code, either using progress
2150 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2151 can also measure unmodified code by measuring complete the program
2152 runtime and running the program several times instead.&lt;/p&gt;
2153
2154 &lt;p&gt;The project and presentation was so inspiring that I would like to
2155 get the system into Debian. I
2156 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
2157 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
2158 system ready for Debian by sending patches. The build process need to
2159 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
2160 to include the JavaScript web page used to visualize the collected
2161 profiling information included in the source package.
2162 But I expect that should work out fairly soon.&lt;/p&gt;
2163
2164 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
2165 on a binary with debug symbols available, start the program like this:
2166
2167 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2168 coz run --- program-to-run
2169 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2170
2171 &lt;p&gt;This will create a text file profile.coz with the instrumentation
2172 information. To show what part of the code affect the performance
2173 most, use a web browser and either point it to
2174 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
2175 or use the copy from git (in the gh-pages branch). Check out this web
2176 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
2177 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
2178 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2179 code, rebuild and run the profiler. This allow coz to do more
2180 targeted experiments.&lt;/p&gt;
2181
2182 &lt;p&gt;A video published by ACM
2183 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
2184 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
2185 from the 25th Symposium on Operating Systems Principles available
2186 titled
2187 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
2188 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
2189
2190 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
2191 for Coz is available from github. It will only build with clang
2192 because it uses a
2193 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
2194 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
2195 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
2196 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
2197
2198 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
2199 of software in Debian. I would very much like some help with the
2200 packaging effort, as I lack the in depth knowledge on how to package
2201 C++ libraries.&lt;/p&gt;
2202 </description>
2203 </item>
2204
2205 <item>
2206 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
2207 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
2208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
2209 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
2210 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2211 to be a slight challenge. Here is the recipe if I ever need to do it
2212 again. It all started by me wanting to try the recipe to set up
2213 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
2214 hardened Android installation&lt;/a&gt; from the Tor project blog on a
2215 device I had access to. It is a old mobile phone with a broken
2216 microphone The initial idea had been to just
2217 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
2218 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
2219 until a few days ago.&lt;/p&gt;
2220
2221 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
2222 loader (press volume down and power at the same time), (2) select
2223 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
2224 machine, (4) request the device identifier token by running &#39;fastboot
2225 oem get_identifier_token&#39;, (5) request the device unlocking key using
2226 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
2227 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
2228
2229 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
2230 or newer, and the device I was working on had 2.00.0027. This
2231 apparently can be easily fixed by downloading a Windows program and
2232 running it on your Windows machine, if you accept the terms Microsoft
2233 require you to accept to use Windows - which I do not. So I had to
2234 come up with a different approach. I got a lot of help from AndyCap
2235 on #nuug, and would not have been able to get this working without
2236 him.&lt;/p&gt;
2237
2238 &lt;p&gt;First I needed to extract the hboot firmware from
2239 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
2240 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
2241 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
2242 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
2243 recognise the file format, but unruu worked and extracted rom.zip,
2244 containing the new hboot firmware and a text file describing which
2245 devices it would work for.&lt;/p&gt;
2246
2247 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
2248 followed some instructions
2249 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
2250 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
2251 machine with Debian testing:&lt;/p&gt;
2252
2253 &lt;p&gt;&lt;pre&gt;
2254 adb reboot-bootloader
2255 fastboot oem rebootRUU
2256 fastboot flash zip rom.zip
2257 fastboot flash zip rom.zip
2258 fastboot reboot
2259 &lt;/pre&gt;&lt;/p&gt;
2260
2261 &lt;p&gt;The flash command apparently need to be done twice to take effect,
2262 as the first is just preparations and the second one do the flashing.
2263 The adb command is just to get to the boot loader menu, so turning the
2264 device on while holding volume down and the power button should work
2265 too.&lt;/p&gt;
2266
2267 &lt;p&gt;With the new hboot version in place I could start following the
2268 instructions on the HTC developer web site. I got the device token
2269 like this:&lt;/p&gt;
2270
2271 &lt;p&gt;&lt;pre&gt;
2272 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
2273 &lt;/pre&gt;
2274
2275 &lt;p&gt;And once I got the unlock code via email, I could use it like
2276 this:&lt;/p&gt;
2277
2278 &lt;p&gt;&lt;pre&gt;
2279 fastboot flash unlocktoken Unlock_code.bin
2280 &lt;/pre&gt;&lt;/p&gt;
2281
2282 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2283 could start stuffing the software of my own choosing into the device.
2284 So far I only inserted a replacement recovery image to wipe the phone
2285 before I start. We will see what happen next. Perhaps I should
2286 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2287 </description>
2288 </item>
2289
2290 <item>
2291 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2292 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
2293 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
2294 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2295 <description>&lt;p&gt;For a while now, I have wanted to test
2296 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2297 said to provide end to end encrypted communication and several of my
2298 friends and family are already using it. As I by choice do not own a
2299 mobile phone, this proved to be harder than expected. And I wanted to
2300 have the source of the client and know that it was the code used on my
2301 machine. But yesterday I managed to get it working. I used the
2302 Github source, compared it to the source in
2303 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2304 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2305 patches to use the production Signal servers, started the app and
2306 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2307 the recipe how I did it.&lt;/p&gt;
2308
2309 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2310
2311 &lt;pre&gt;
2312 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2313 &lt;/pre&gt;
2314
2315 &lt;p&gt;Next, I patched the source to use the production servers, to be
2316 able to talk to other Signal users:&lt;/p&gt;
2317
2318 &lt;pre&gt;
2319 cat &amp;lt;&amp;lt;EOF | patch -p0
2320 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2321 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2322 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2323 @@ -47,8 +47,8 @@
2324 });
2325 });
2326
2327 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2328 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2329 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2330 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2331 var messageReceiver;
2332 window.getSocketStatus = function() {
2333 if (messageReceiver) {
2334 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2335 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2336 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2337 @@ -1,6 +1,6 @@
2338 ;(function() {
2339 &#39;use strict&#39;;
2340 - var BUILD_EXPIRATION = 0;
2341 + var BUILD_EXPIRATION = 1474492690000;
2342
2343 window.extension = window.extension || {};
2344
2345 EOF
2346 &lt;/pre&gt;
2347
2348 &lt;p&gt;The first part is changing the servers, and the second is updating
2349 an expiration timestamp. This timestamp need to be updated regularly.
2350 It is set 90 days in the future by the build process (Gruntfile.js).
2351 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2352
2353 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2354 script to launch Signal in Chromium.&lt;/p&gt;
2355
2356 &lt;pre&gt;
2357 #!/bin/sh
2358 cd $(dirname $0)
2359 mkdir -p userdata
2360 exec chromium \
2361 --proxy-server=&quot;socks://localhost:9050&quot; \
2362 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2363 &lt;/pre&gt;
2364
2365 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2366 SOCKS5 proxy to make sure those controlling the Signal servers (today
2367 Amazon and Whisper Systems) as well as those listening on the lines
2368 will have a harder time location my laptop based on the Signal
2369 connections if they use source IP address.&lt;/p&gt;
2370
2371 &lt;p&gt;When the script starts, one need to follow the instructions under
2372 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2373 repository. I right clicked on the Signal window to get up the
2374 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2375 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2376 registration form. Then I entered by land line phone number and
2377 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2378 repeated the verification code three times. After entering the number
2379 into the verification code field in the form, I could start using
2380 Signal from my laptop.
2381
2382 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2383 whom and thus who know who to those controlling the central server,
2384 but such leakage is hard to avoid with a centrally controlled server
2385 setup. It is something to keep in mind when using Signal - the
2386 content of your chats are harder to intercept, but the meta data
2387 exposing your contact network is available to people you do not know.
2388 So better than many options, but not great. And sadly the usage is
2389 connected to my land line, thus allowing those controlling the server
2390 to associate it to my home and person. I would prefer it if only
2391 those I knew could tell who I was on Signal. There are options
2392 avoiding such information leakage, but most of my friends are not
2393 using them, so I am stuck with Signal for now.&lt;/p&gt;
2394
2395 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2396 on this topic in
2397 &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
2398 and updated recipe for using the Signal app without a mobile
2399 phone&lt;/a&gt;.&lt;/p&gt;
2400 </description>
2401 </item>
2402
2403 <item>
2404 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2405 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2406 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2407 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2408 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2409 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2410 multimedia player in Debian claimed to support most file formats /
2411 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2412 the various players claimed support for. The range was from 55 to 130
2413 MIME types. I suspect most media formats are supported by all
2414 players, but this is not really reflected in the MimeTypes values in
2415 their desktop files. There are probably also some bogus MIME types
2416 listed, but it is hard to identify which one this is.&lt;/p&gt;
2417
2418 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2419 the players suggesting to add more MIME types to their desktop files,
2420 and decided to spend some time myself improving the situation for my
2421 favorite media player VLC. The fixes for VLC entered Debian unstable
2422 yesterday. The complete list of MIME types can be seen on the
2423 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2424 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2425
2426 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2427 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2428 kmplayer. I am sure some of the other players desktop files support
2429 several of the formats currently listed as working only with vlc,
2430 toten and parole.&lt;/p&gt;
2431
2432 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2433 supported by all the tested multimedia players in Debian in their
2434 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2435 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2436 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2437 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2438 it sad that video/ogg and video/webm is not supported by all the media
2439 players in Debian. As far as I can tell, all of them can handle both
2440 formats.&lt;/p&gt;
2441 </description>
2442 </item>
2443
2444 <item>
2445 <title>A program should be able to open its own files on Linux</title>
2446 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2447 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2448 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2449 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2450 decided to test its presentation tool when making the slides for a
2451 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2452 wrote the first draft of the slides, saved the result and went to bed
2453 the day before I would give the talk. The next day I took a plane to
2454 the location where the meeting should take place, and on the plane I
2455 started up koffice again to polish the talk a bit, only to discover
2456 that kpresenter refused to load its own data file. I cursed a bit and
2457 started making the slides again from memory, to have something to
2458 present when I arrived. I tested that the saved files could be
2459 loaded, and the day seemed to be rescued. I continued to polish the
2460 slides until I suddenly discovered that the saved file could no longer
2461 be loaded into kpresenter. In the end I had to rewrite the slides
2462 three times, condensing the content until the talk became shorter and
2463 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2464 kpresenter wrote inline images in a way itself could not understand.
2465 Eventually that bug was fixed and kpresenter ended up being a great
2466 program to make slides. The point I&#39;m trying to make is that we
2467 expect a program to be able to load its own data files, and it is
2468 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2469
2470 &lt;p&gt;Did you ever experience a program failing to load its own data
2471 files from the desktop file browser? It is not a uncommon problem. A
2472 while back I discovered that the screencast recorder
2473 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2474 browser would refuse to open. No video player claimed to understand
2475 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2476 returning the application/ogg MIME type, which no video player I had
2477 installed listed as a MIME type they would understand. I asked for
2478 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2479 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2480 several video players to add video/ogg to their desktop files, to give
2481 the file browser an idea what to do about Ogg Theora files. After a
2482 while, the desktop file browsers in Debian started to handle the
2483 output from gtk-recordmydesktop properly.&lt;/p&gt;
2484
2485 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2486 system Rosegarden again, and I discovered that the KDE and xfce file
2487 browsers did not know what to do with the Rosegarden project files
2488 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2489 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2490 included in the next upload. To increase the chance of me remembering
2491 how to fix the problem next time some program fail to load its files
2492 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2493
2494 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2495 There are two sources for the MIME type of a given file. The output from
2496 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2497 shared MIME type registry (under /usr/share/mime/). The file MIME
2498 type is mapped to programs supporting the MIME type, and this
2499 information is collected from
2500 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2501 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2502 one desktop file claiming support for the MIME type of the file, it is
2503 activated when asking to open a given file. If there are more, one
2504 can normally select which one to use by right-clicking on the file and
2505 selecting the wanted one using &#39;Open with&#39; or similar. In general
2506 this work well. But it depend on each program picking a good MIME
2507 type (preferably
2508 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2509 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2510 registry recognizing the file and the desktop file to list the MIME
2511 type in its list of supported MIME types.&lt;/p&gt;
2512
2513 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2514 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2515 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2516
2517 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2518 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2519 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2520 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2521 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2522 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2523 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2524 &amp;lt;/mime-type&amp;gt;
2525 &amp;lt;/mime-info&amp;gt;
2526 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2527
2528 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2529 (it is a gzipped XML file). Note, it is much better to use an
2530 official MIME type registered with IANA than it is to make up ones own
2531 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2532
2533 &lt;p&gt;The desktop file of the rosegarden program failed to list
2534 audio/x-rosegarden in its list of supported MIME types, causing the
2535 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2536
2537 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2538 % grep Mime /usr/share/applications/rosegarden.desktop
2539 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2540 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2541 %
2542 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2543
2544 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2545 MimeType= line.&lt;/p&gt;
2546
2547 &lt;p&gt;If you run into a file which fail to open the correct program when
2548 selected from the file browser, please check out the output from
2549 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2550 MIME type is registered somewhere under /usr/share/mime/ and check
2551 that some desktop file under /usr/share/applications/ is claiming
2552 support for this MIME type. If not, please report a bug to have it
2553 fixed. :)&lt;/p&gt;
2554 </description>
2555 </item>
2556
2557 <item>
2558 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2559 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2561 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2562 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2563 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2564 related packages. The idea is to have a database of mappings between
2565 hardware and packages, and pop up a dialog suggesting for the user to
2566 install the packages to use a given hardware dongle. Some use cases
2567 are when you insert a Yubikey, it proposes to install the software
2568 needed to control it; when you insert a braille reader list it
2569 proposes to install the packages needed to send text to the reader;
2570 and when you insert a ColorHug screen calibrator it suggests to
2571 install the driver for it. The system work well, and even have a few
2572 command line tools to install firmware packages and packages for the
2573 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2574
2575 &lt;p&gt;The system was initially written using aptdaemon, because I found
2576 good documentation and example code on how to use it. But aptdaemon
2577 is going away and is generally being replaced by
2578 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2579 so Isenkram needed a rewrite. And today, thanks to the great patch
2580 from my college Sunil Mohan Adapa in the FreedomBox project, the
2581 rewrite finally took place. I&#39;ve just uploaded a new version of
2582 Isenkram into Debian Unstable with the patch included, and the default
2583 for the background daemon is now to use PackageKit. To check it out,
2584 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2585 and see if it is recognised.&lt;/p&gt;
2586
2587 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2588 the machine it is running on, you can check out the isenkram-lookup
2589 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2590
2591 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2592 % isenkram-lookup
2593 bluez
2594 cheese
2595 fprintd
2596 fprintd-demo
2597 gkrellm-thinkbat
2598 hdapsd
2599 libpam-fprintd
2600 pidgin-blinklight
2601 thinkfan
2602 tleds
2603 tp-smapi-dkms
2604 tp-smapi-source
2605 tpb
2606 %p
2607 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2608
2609 &lt;p&gt;The hardware mappings come from several places. The preferred way
2610 is for packages to announce their hardware support using
2611 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2612 cross distribution appstream system&lt;/a&gt;.
2613 See
2614 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2615 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2616 </description>
2617 </item>
2618
2619 <item>
2620 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2621 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2623 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2624 <description>&lt;p&gt;Yesterday I updated the
2625 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2626 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2627 enterprising users. There were some nice user and visible changes.
2628 First of all, both desktop menu entries now work. A design flaw in
2629 one of the script made the history graph fail to show up (its PNG was
2630 dumped in ~/.xsession-errors) if no controlling TTY was available.
2631 The script worked when called from the command line, but not when
2632 called from the desktop menu. I changed this to look for a DISPLAY
2633 variable or a TTY before deciding where to draw the graph, and now the
2634 graph window pop up as expected.&lt;/p&gt;
2635
2636 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2637 graphs (the one showing the last few hours). New is also the user of
2638 colours showing charging in blue and discharge in red. The percentages
2639 of this graph is relative to last full charge, not battery design
2640 capacity.&lt;/p&gt;
2641
2642 &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;
2643
2644 &lt;p&gt;The other graph show the entire history of the collected battery
2645 statistics, comparing it to the design capacity of the battery to
2646 visualise how the battery life time get shorter over time. The red
2647 line in this graph is what the previous graph considers 100 percent:
2648
2649 &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;
2650
2651 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2652 percent of last full capacity, and how the capacity of the battery is
2653 shrinking. :(&lt;/p&gt;
2654
2655 &lt;p&gt;The last new feature is in the collector, which now will handle
2656 more hardware models. On some hardware, Linux power supply
2657 information is stored in /sys/class/power_supply/ACAD/, while the
2658 collector previously only looked in /sys/class/power_supply/AC/. Now
2659 both are checked to figure if there is power connected to the
2660 machine.&lt;/p&gt;
2661
2662 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2663 check out the
2664 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2665 in Debian unstable, or rebuild it on Jessie to get it working on
2666 Debian stable. :) The upstream source is available from &lt;a
2667 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2668 Patches are very welcome.&lt;/p&gt;
2669
2670 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2671 activities, please send Bitcoin donations to my address
2672 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2673 </description>
2674 </item>
2675
2676 <item>
2677 <title>Debian now with ZFS on Linux included</title>
2678 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2679 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2680 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2681 <description>&lt;p&gt;Today, after many years of hard work from many people,
2682 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2683 Debian. The package status can be seen on
2684 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2685 for zfs-linux&lt;/a&gt;. and
2686 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2687 team status page&lt;/a&gt;. If you want to help out, please join us.
2688 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2689 source code&lt;/a&gt; is available via git on Alioth. It would also be
2690 great if you could help out with
2691 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2692 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2693 </description>
2694 </item>
2695
2696 <item>
2697 <title>What is the best multimedia player in Debian?</title>
2698 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2700 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2701 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2702 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2703
2704 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2705 plugins in Debian, to get an idea which plugins to include in Debian
2706 Edu. I created a script to extract the set of supported MIME types
2707 for each plugin, and used this to find out which multimedia browser
2708 plugin supported most file formats / media types.
2709 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2710 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2711 not been updated for a while. But browser plugins are less relevant
2712 these days, so I thought it was time to look at standalone
2713 players.&lt;/p&gt;
2714
2715 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2716 player when I wanted to play videos from the Norwegian National
2717 Broadcasting Company, and decided to investigate why. The cause is a
2718 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2719 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2720 of MIME types announced in the desktop file and the browser plugin,
2721 only to discover that there is quite a large difference between the
2722 two for VLC. This discovery made me dig up the script I used to
2723 compare browser plugins, and adjust it to compare desktop files
2724 instead, to try to figure out which multimedia player in Debian
2725 support most file formats.&lt;/p&gt;
2726
2727 &lt;p&gt;The result can be seen on the Debian Wiki, as
2728 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2729 table listing all MIME types supported by one of the packages included
2730 in the table&lt;/a&gt;, with the package supporting most MIME types being
2731 listed first in the table.&lt;/p&gt;
2732
2733 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2734 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2735 kmplayer. Time for the other players to update their announced MIME
2736 support?&lt;/p&gt;
2737 </description>
2738 </item>
2739
2740 <item>
2741 <title>The Pyra - handheld computer with Debian preinstalled</title>
2742 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2744 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2745 <description>A friend of mine made me aware of
2746 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2747 handheld computer which will be delivered with Debian preinstalled. I
2748 would love to get one of those for my birthday. :)&lt;/p&gt;
2749
2750 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2751 plugs and many others connectors, and include a full keyboard and a 5&quot;
2752 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2753 day of battery life time, but I have not seen any independent tests
2754 confirming this. The vendor is still collecting preorders, and the
2755 last I heard last night was that 22 more orders were needed before
2756 production started.&lt;/p&gt;
2757
2758 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2759 Debian. Please let me know if you know of any others. Is it the
2760 first computer being sold with Debian preinstalled?&lt;/p&gt;
2761 </description>
2762 </item>
2763
2764 <item>
2765 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2766 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2767 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2768 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2769 <description>&lt;p&gt;During this weekends
2770 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2771 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
2772 to make sure there are good books about Debian available in Norwegian
2773 Bokmål, and got in touch with the people behind the
2774 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
2775 project&lt;/a&gt; to get started. If you want to help out, please start
2776 contributing using
2777 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2778 hosted weblate project page&lt;/a&gt;, and get in touch using
2779 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2780 translators mailing list&lt;/a&gt;. Please also check out
2781 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2782 contributors&lt;/a&gt;.&lt;/p&gt;
2783
2784 &lt;p&gt;The book is already available on paper in English, French and
2785 Japanese, and our goal is to get it available on paper in Norwegian
2786 Bokmål too. In addition to the paper edition, there are also EPUB and
2787 Mobi versions available. And there are incomplete translations
2788 available for many more languages.&lt;/p&gt;
2789 </description>
2790 </item>
2791
2792 <item>
2793 <title>One in two hundred Debian users using ZFS on Linux?</title>
2794 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
2795 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
2796 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
2797 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
2798 packages in Debian, and was quite surprised with what I found. I use
2799 ZFS myself at home, but did not really expect many others to do so.
2800 But I might be wrong.&lt;/p&gt;
2801
2802 &lt;p&gt;According to
2803 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
2804 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
2805 0.53% of the population, with the package installed. As far as I know
2806 the only use of the spl-linux package is as a support library for ZFS
2807 on Linux, so I use it here as proxy for measuring the number of ZFS
2808 installation on Linux in Debian. In the kFreeBSD variant of Debian
2809 the ZFS feature is already available, and there
2810 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
2811 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
2812 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
2813
2814 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
2815 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
2816 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
2817 cleared, the package is still not in Debian. The package is again in
2818 the NEW queue. Several uploads have been rejected so far because the
2819 debian/copyright file was incomplete or wrong, but there is no reason
2820 to give up. The current status can be seen on
2821 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2822 team status page&lt;/a&gt;, and
2823 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
2824 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
2825
2826 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
2827 my home server can function in the future using only official Debian
2828 packages, and the current blocker is to get the debian/copyright file
2829 accepted by the FTP masters in Debian, I decided a while back to try
2830 to help out the team. This was the background for my blog post about
2831 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
2832 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
2833 used the techniques I explored there to try to find any errors in the
2834 copyright file. It is not very easy to check every one of the around
2835 2000 files in the source package, but I hope we this time got it
2836 right. If you want to help out, check out the git source and try to
2837 find missing entries in the debian/copyright file.&lt;/p&gt;
2838 </description>
2839 </item>
2840
2841 <item>
2842 <title>Full battery stats collector is now available in Debian</title>
2843 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
2844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
2845 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
2846 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
2847 extended collector that will collect the complete battery history for
2848 later processing and graphing. The original collector store the
2849 battery level as percentage of last full level, while the new
2850 collector also record battery vendor, model, serial number, design
2851 full level, last full level and current battery level. This make it
2852 possible to predict the lifetime of the battery as well as visualise
2853 the energy flow when the battery is charging or discharging.&lt;/p&gt;
2854
2855 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
2856 in the version 0.5.1 package in unstable. Get the new battery level graph
2857 and lifetime prediction by running:
2858
2859 &lt;p&gt;&lt;pre&gt;
2860 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2861 &lt;/pre&gt;&lt;/p&gt;
2862
2863 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
2864
2865 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
2866 entry yet):&lt;/p&gt;
2867
2868 &lt;p&gt;&lt;pre&gt;
2869 /usr/share/battery-stats/battery-stats-graph-flow
2870 &lt;/pre&gt;&lt;/p&gt;
2871
2872 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
2873 when there are few data points. The graphs look a bit better with a
2874 few years of data.&lt;/p&gt;
2875
2876 &lt;p&gt;A while back one important feature I use in the battery stats
2877 collector broke in Debian. The scripts in
2878 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
2879 suspect it happened when Jessie started using systemd, but I do not
2880 know. The issue is reported as
2881 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
2882 pm-utils. I managed to work around it by adding an udev rule to call
2883 the collector script every time the power connector is connected and
2884 disconnected. With this fix in place it was finally time to make a
2885 new release of the package, and get it into Debian.&lt;/p&gt;
2886
2887 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2888 check out the
2889 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2890 in Debian unstable, or rebuild it on Jessie to get it working on
2891 Debian stable. :) The upstream source is available from
2892 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2893 As always, patches are very welcome.&lt;/p&gt;
2894 </description>
2895 </item>
2896
2897 <item>
2898 <title>Making battery measurements a little easier in Debian</title>
2899 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
2900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
2901 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
2902 <description>&lt;p&gt;Back in September, I blogged about
2903 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
2904 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
2905 how it showed the decay and death of this battery (now replaced). I
2906 created a simple deb package to handle the collection and graphing,
2907 but did not want to upload it to Debian as there were already
2908 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
2909 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
2910 a point of uploading a competing package when battery-stats could be
2911 fixed instead. I reported a few bugs about its non-function, and
2912 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
2913
2914 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
2915 hands. The end result is that I am now the new upstream developer of
2916 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
2917 battery-stats in Debian, and the package in Debian unstable is finally
2918 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
2919 information provided by the Linux kernel. If you install the
2920 battery-stats package from unstable now, you will be able to get a
2921 graph of the current battery fill level, to get some idea about the
2922 status of the battery. The source package build and work just fine in
2923 Debian testing and stable (and probably oldstable too, but I have not
2924 tested). The default graph you get for that system look like this:&lt;/p&gt;
2925
2926 &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;
2927
2928 &lt;p&gt;My plans for the future is to merge my old scripts into the
2929 battery-stats package, as my old scripts collected a lot more details
2930 about the battery. The scripts are merged into the upstream
2931 battery-stats git repository already, but I am not convinced they work
2932 yet, as I changed a lot of paths along the way. Will have to test a
2933 bit more before I make a new release.&lt;/p&gt;
2934
2935 &lt;p&gt;I will also consider changing the file format slightly, as I
2936 suspect the way I combine several values into one field might make it
2937 impossible to know the type of the value when using it for processing
2938 and graphing.&lt;/p&gt;
2939
2940 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
2941 battery, check out the battery-stats package in
2942 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
2943 on
2944 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2945 I would love some help to improve the system further.&lt;/p&gt;
2946 </description>
2947 </item>
2948
2949 <item>
2950 <title>Creating, updating and checking debian/copyright semi-automatically</title>
2951 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
2952 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
2953 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
2954 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
2955 details. And one of the details is the content of the
2956 debian/copyright file, which should list all relevant licenses used by
2957 the code in the package in question, preferably in
2958 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
2959 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
2960
2961 &lt;p&gt;For large packages with lots of contributors it is hard to write
2962 and update this file manually, and if you get some detail wrong, the
2963 package is normally rejected by the ftpmasters. So getting it right
2964 the first time around get the package into Debian faster, and save
2965 both you and the ftpmasters some work.. Today, while trying to figure
2966 out what was wrong with
2967 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
2968 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
2969 figuring out the options for doing this job automatically, or at least
2970 semi-automatically.&lt;/p&gt;
2971
2972 &lt;p&gt;Lucikly, there are at least two tools available for generating the
2973 file based on the code in the source package,
2974 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
2975 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
2976 not sure which one of them came first, but both seem to be able to
2977 create a sensible draft file. As far as I can tell, none of them can
2978 be trusted to get the result just right, so the content need to be
2979 polished a bit before the file is OK to upload. I found the debmake
2980 option in
2981 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
2982 blog posts from 2014&lt;/a&gt;.
2983
2984 &lt;p&gt;To generate using debmake, use the -cc option:
2985
2986 &lt;p&gt;&lt;pre&gt;
2987 debmake -cc &gt; debian/copyright
2988 &lt;/pre&gt;&lt;/p&gt;
2989
2990 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
2991 this might not be the best option.&lt;/p&gt;
2992
2993 &lt;p&gt;The cme option is based on a config parsing library, and I found
2994 this approach in
2995 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
2996 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
2997 dpkg-copyright&#39; option:
2998
2999 &lt;p&gt;&lt;pre&gt;
3000 cme update dpkg-copyright
3001 &lt;/pre&gt;&lt;/p&gt;
3002
3003 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
3004 handle UTF-8 names better than debmake.&lt;/p&gt;
3005
3006 &lt;p&gt;When the copyright file is created, I would also like some help to
3007 check if the file is correct. For this I found two good options,
3008 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
3009 to focus on license types and file matching, and is able to detect
3010 ineffective blocks in the copyright file. The latter reports missing
3011 copyright holders and years, but was confused by inconsistent license
3012 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
3013 fix all issues reported by them before uploading. But I do not know
3014 if the tools and the ftpmasters agree on what is important to fix in a
3015 copyright file, so the package might still be rejected.&lt;/p&gt;
3016
3017 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
3018 will read through the source and try to find all copyright statements.
3019 It is not comparing the result to the content of debian/copyright, but
3020 can be useful when verifying the content of the copyright file.&lt;/p&gt;
3021
3022 &lt;p&gt;Are you aware of better tools in Debian to create and update
3023 debian/copyright file. Please let me know, or blog about it on
3024 planet.debian.org.&lt;/p&gt;
3025
3026 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3027 activities, please send Bitcoin donations to my address
3028 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3029
3030 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
3031 on how to use licensecheck and cdbs to create a draft copyright file
3032
3033 &lt;p&gt;&lt;pre&gt;
3034 licensecheck --copyright -r `find * -type f` | \
3035 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
3036 &lt;/pre&gt;&lt;/p&gt;
3037
3038 &lt;p&gt;He mentioned that he normally check the generated file into the
3039 version control system to make it easier to discover license and
3040 copyright changes in the upstream source. I will try to do the same
3041 with my packages in the future.&lt;/p&gt;
3042
3043 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
3044 against using -quiet for new users, so I removed it from the proposed
3045 command line.&lt;/p&gt;
3046 </description>
3047 </item>
3048
3049 <item>
3050 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
3051 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
3052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
3053 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
3054 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
3055 is taking shape in Debian, and one provided feature is a very
3056 convenient way to tell you which package to install to make a given
3057 firmware file available when the kernel is looking for it. This can
3058 be done using apt-file too, but that is for someone else to blog
3059 about. :)&lt;/p&gt;
3060
3061 &lt;p&gt;Here is a small recipe to find the package with a given firmware
3062 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
3063 picked from the set of firmware announced using appstream in Debian
3064 unstable. In general you would be looking for the firmware requested
3065 by the kernel during kernel module loading. To find the package
3066 providing the example file, do like this:&lt;/p&gt;
3067
3068 &lt;blockquote&gt;&lt;pre&gt;
3069 % apt install appstream
3070 [...]
3071 % apt update
3072 [...]
3073 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
3074 awk &#39;/Package:/ {print $2}&#39;
3075 firmware-qlogic
3076 %
3077 &lt;/pre&gt;&lt;/blockquote&gt;
3078
3079 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
3080 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
3081 a way appstream can use.&lt;/p&gt;
3082
3083 &lt;p&gt;This same approach can be used to find any package supporting a
3084 given MIME type. This is very useful when you get a file you do not
3085 know how to handle. First find the mime type using &lt;tt&gt;file
3086 --mime-type&lt;/tt&gt;, and next look up the package providing support for
3087 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3088 and you can find all packages handling this type like this:&lt;/p&gt;
3089
3090 &lt;blockquote&gt;&lt;pre&gt;
3091 % apt install appstream
3092 [...]
3093 % apt update
3094 [...]
3095 % appstreamcli what-provides mimetype image/svg+xml | \
3096 awk &#39;/Package:/ {print $2}&#39;
3097 bkchem
3098 phototonic
3099 inkscape
3100 shutter
3101 tetzle
3102 geeqie
3103 xia
3104 pinta
3105 gthumb
3106 karbon
3107 comix
3108 mirage
3109 viewnior
3110 postr
3111 ristretto
3112 kolourpaint4
3113 eog
3114 eom
3115 gimagereader
3116 midori
3117 %
3118 &lt;/pre&gt;&lt;/blockquote&gt;
3119
3120 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
3121 packages providing appstream metadata.&lt;/p&gt;
3122 </description>
3123 </item>
3124
3125 <item>
3126 <title>Creepy, visualise geotagged social media information - nice free software</title>
3127 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
3128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
3129 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
3130 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
3131 with the computerised radio beacon known as a mobile phone their
3132 position is tracked by the phone company and often stored for a long
3133 time (like every time a SMS is received or sent). And if their
3134 computerised radio beacon is capable of running programs (often called
3135 mobile apps) downloaded from the Internet, these programs are often
3136 also capable of tracking their location (if the app requested access
3137 during installation). And when these programs send out information to
3138 central collection points, the location is often included, unless
3139 extra care is taken to not send the location. The provided
3140 information is used by several entities, for good and bad (what is
3141 good and bad, depend on your point of view). What is certain, is that
3142 the private sphere and the right to free movement is challenged and
3143 perhaps even eradicated for those announcing their location this way,
3144 when they share their whereabouts with private and public
3145 entities.&lt;/p&gt;
3146
3147 &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;
3148
3149 &lt;p&gt;The phone company logs provide a register of locations to check out
3150 when one want to figure out what the tracked person was doing. It is
3151 unavailable for most of us, but provided to selected government
3152 officials, company staff, those illegally buying information from
3153 unfaithful servants and crackers stealing the information. But the
3154 public information can be collected and analysed, and a free software
3155 tool to do so is called
3156 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
3157 discovered it when I read
3158 &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
3159 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
3160 November 2014, and decided to check if it was available in Debian.
3161 The python program was in Debian, but
3162 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
3163 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
3164 uploaded a new version which did not work quite right, but did not
3165 have time to fix it then. This Christmas I decided to finally try to
3166 get Creepy operational in Debian. Now a fixed version is available in
3167 Debian unstable and testing, and almost all Debian specific patches
3168 are now included
3169 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
3170
3171 &lt;p&gt;The Creepy program visualises geolocation information fetched from
3172 Twitter, Instagram, Flickr and Google+, and allow one to get a
3173 complete picture of every social media message posted recently in a
3174 given area, or track the movement of a given individual across all
3175 these services. Earlier it was possible to use the search API of at
3176 least some of these services without identifying oneself, but these
3177 days it is impossible. This mean that to use Creepy, you need to
3178 configure it to log in as yourself on these services, and provide
3179 information to them about your search interests. This should be taken
3180 into account when using Creepy, as it will also share information
3181 about yourself with the services.&lt;/p&gt;
3182
3183 &lt;p&gt;The picture above show the twitter messages sent from (or at least
3184 geotagged with a position from) the city centre of Oslo, the capital
3185 of Norway. One useful way to use Creepy is to first look at
3186 information tagged with an area of interest, and next look at all the
3187 information provided by one or more individuals who was in the area.
3188 I tested it by checking out which celebrity provide their location in
3189 twitter messages by checkout out who sent twitter messages near a
3190 Norwegian TV station, and next could track their position over time,
3191 making it possible to locate their home and work place, among other
3192 things. A similar technique have been
3193 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
3194 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
3195 tool to discover lying governments, and a useful tool to help people
3196 understand the value of the private information they provide to the
3197 public.&lt;/p&gt;
3198
3199 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
3200 it depend on several python modules currently missing in Jessie (at
3201 least python-instagram, python-flickrapi and
3202 python-requests-toolbelt).&lt;/p&gt;
3203
3204 &lt;p&gt;(I have uploaded
3205 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
3206 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
3207 Creepy program in Debian.)&lt;/p&gt;
3208 </description>
3209 </item>
3210
3211 <item>
3212 <title>Always download Debian packages using Tor - the simple recipe</title>
3213 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
3214 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
3215 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
3216 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
3217 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
3218 that those listening on the Internet lines would have good reason to
3219 believe a computer have a given security hole&lt;/a&gt; if it download a
3220 security fix from a Debian mirror. This is a good reason to always
3221 use encrypted connections to the Debian mirror, to make sure those
3222 listening do not know which IP address to attack. In August, Richard
3223 Hartmann observed that encryption was not enough, when it was possible
3224 to interfere download size to security patches or the fact that
3225 download took place shortly after a security fix was released, and
3226 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
3227 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
3228 was not the first to propose this, as the
3229 &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;
3230 package by Tim Retout already existed to make it easy to convince apt
3231 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
3232 aware of that package when I read the blog post from Richard.&lt;/p&gt;
3233
3234 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
3235 sysadmins, and he set up a Tor hidden service on one of the central
3236 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3237 it possible to download packages directly between two tor nodes,
3238 making sure the network traffic always were encrypted.&lt;/p&gt;
3239
3240 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
3241 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
3242 urls with tor+http and tor+https, and using the hidden service instead
3243 of the official Debian mirror site. I recommend installing
3244 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
3245 done in /etc/.&lt;/p&gt;
3246
3247 &lt;blockquote&gt;&lt;pre&gt;
3248 apt install apt-transport-tor
3249 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
3250 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
3251 &lt;/pre&gt;&lt;/blockquote&gt;
3252
3253 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
3254 the sed commands for these too. The sed command is assuming your are
3255 using the ftp.debian.org Debian mirror. Adjust the command (or just
3256 edit the file manually) to match your mirror.&lt;/p&gt;
3257
3258 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
3259 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
3260 system, and do not work with these tor+http URLs. For
3261 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
3262 which need a recent apt version currently only in unstable. So if you
3263 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
3264
3265 &lt;p&gt;Another advantage from this change is that your machine will start
3266 using Tor regularly and at fairly random intervals (every time you
3267 update the package lists or upgrade or install a new package), thus
3268 masking other Tor traffic done from the same machine. Using Tor will
3269 become normal for the machine in question.&lt;/p&gt;
3270
3271 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
3272 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
3273 enabled. It would be great if it was the default on any Debian
3274 system.&lt;/p&gt;
3275 </description>
3276 </item>
3277
3278 <item>
3279 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3280 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3282 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3283 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3284 call the car license plate numbers in those days. I would write the
3285 numbers down in my little book and compare notes with the other kids
3286 to see how many region codes we had seen and if we had seen some
3287 exotic or special region codes and numbers. It was a fun game to pass
3288 time, as we kids have plenty of it.&lt;/p&gt;
3289
3290 &lt;p&gt;A few days I came across
3291 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3292 project&lt;/a&gt;, a free software project to automatically discover and
3293 report license plates in images and video streams, and provide the
3294 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3295 such system for a while now, because I believe it is a bad idea that the
3296 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3297 number plate recognition&lt;/a&gt; tool only is available in the hands of
3298 the powerful, and want it to be available also for the powerless to
3299 even the score when it comes to surveillance and sousveillance. I
3300 discovered the developer
3301 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3302 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3303 help him get it into shape to get the package uploaded into the Debian
3304 archive.&lt;/p&gt;
3305
3306 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3307 it into Debian, where it currently
3308 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3309 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3310
3311 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3312 for the common folks, ie those not running a large government
3313 surveillance system? Well, I plan to put it in a computer on my bike
3314 and in my car, tracking the cars nearby and allowing me to be notified
3315 when number plates on my watch list are discovered. Another use case
3316 was suggested by a friend of mine, who wanted to set it up at his home
3317 to open the car port automatically when it discovered the plate on his
3318 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3319 capable of placing his license plate number of a piece of cardboard to
3320 open his car port, men replied that it was always unlocked anyway. I
3321 guess for such use case it make sense. I am sure there are other use
3322 cases too, for those with imagination and a vision.&lt;/p&gt;
3323
3324 &lt;p&gt;If you want to build your own version of the Debian package, check
3325 out the upstream git source and symlink ./distros/debian to ./debian/
3326 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3327 package show up in unstable.&lt;/p&gt;
3328 </description>
3329 </item>
3330
3331 <item>
3332 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3333 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3334 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3335 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3336 <description>&lt;p&gt;Around three years ago, I created
3337 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3338 system&lt;/a&gt; to get a more practical solution in Debian for handing
3339 hardware related packages. A GUI system in the isenkram package will
3340 present a pop-up dialog when some hardware dongle supported by
3341 relevant packages in Debian is inserted into the machine. The same
3342 lookup mechanism to detect packages is available as command line
3343 tools in the isenkram-cli package. In addition to mapping hardware,
3344 it will also map kernel firmware files to packages and make it easy to
3345 install needed firmware packages automatically. The key for this
3346 system to work is a good way to map hardware to packages, in other
3347 words, allow packages to announce what hardware they will work
3348 with.&lt;/p&gt;
3349
3350 &lt;p&gt;I started by providing data files in the isenkram source, and
3351 adding code to download the latest version of these data files at run
3352 time, to ensure every user had the most up to date mapping available.
3353 I also added support for storing the mapping in the Packages file in
3354 the apt repositories, but did not push this approach because while I
3355 was trying to figure out how to best store hardware/package mappings,
3356 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3357 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3358 add the hardware mapping into that data set to be able to use
3359 appstream as a data source, and this was accepted at least for the
3360 Debian version of appstream.&lt;/p&gt;
3361
3362 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3363 and today I uploaded a new version 0.20 of isenkram adding support for
3364 appstream as a data source for mapping hardware to packages. The only
3365 package so far using appstream to announce its hardware support is my
3366 pymissile package. I got help from Matthias Klumpp with figuring out
3367 how do add the required
3368 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3369 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3370 this content:&lt;/p&gt;
3371
3372 &lt;blockquote&gt;&lt;pre&gt;
3373 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3374 &amp;lt;component&amp;gt;
3375 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3376 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3377 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3378 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3379 &amp;lt;description&amp;gt;
3380 &amp;lt;p&amp;gt;
3381 Pymissile provides a curses interface to control an original
3382 Marks and Spencer / Striker USB Missile Launcher, as well as a
3383 motion control script to allow a webcamera to control the
3384 launcher.
3385 &amp;lt;/p&amp;gt;
3386 &amp;lt;/description&amp;gt;
3387 &amp;lt;provides&amp;gt;
3388 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3389 &amp;lt;/provides&amp;gt;
3390 &amp;lt;/component&amp;gt;
3391 &lt;/pre&gt;&lt;/blockquote&gt;
3392
3393 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3394 which is a glob style match rule for hardware specific strings
3395 (modalias strings) provided by the Linux kernel. In this case, it
3396 will map to all USB devices with vendor code 1130 and product code
3397 0202.&lt;/p&gt;
3398
3399 &lt;p&gt;Note, it is important that the license of all the metadata files
3400 are compatible to have permissions to aggregate them into archive wide
3401 appstream files. Matthias suggested to use MIT or BSD licenses for
3402 these files. A challenge is figuring out a good id for the data, as
3403 it is supposed to be globally unique and shared across distributions
3404 (in other words, best to coordinate with upstream what to use). But
3405 it can be changed later or, so we went with the package name as
3406 upstream for this project is dormant.&lt;/p&gt;
3407
3408 &lt;p&gt;To get the metadata file installed in the correct location for the
3409 mirror update scripts to pick it up and include its content the
3410 appstream data source, the file must be installed in the binary
3411 package under /usr/share/appdata/. I did this by adding the following
3412 line to debian/pymissile.install:&lt;/p&gt;
3413
3414 &lt;blockquote&gt;&lt;pre&gt;
3415 debian/pymissile.metainfo.xml usr/share/appdata
3416 &lt;/pre&gt;&lt;/blockquote&gt;
3417
3418 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3419 all packages useful on the current computer automatically, and the GUI
3420 pop-up handler will propose to install the package not already
3421 installed if a hardware dongle is inserted into the machine in
3422 question.&lt;/p&gt;
3423
3424 &lt;p&gt;Details of the modalias field in appstream is available from the
3425 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3426
3427 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3428 try running this command on the command line:&lt;/p&gt;
3429
3430 &lt;blockquote&gt;&lt;pre&gt;
3431 cat $(find /sys/devices/|grep modalias)
3432 &lt;/pre&gt;&lt;/blockquote&gt;
3433
3434 &lt;p&gt;To learn more about the isenkram system, please check out
3435 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3436 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3437 </description>
3438 </item>
3439
3440 <item>
3441 <title>The GNU General Public License is not magic pixie dust</title>
3442 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3443 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3444 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3445 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3446 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3447 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3448 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3449 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3450
3451 &lt;blockquote&gt;
3452
3453 &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;
3454
3455 &lt;blockquote&gt;
3456 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3457
3458 The first step is to choose a
3459 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3460 code.&lt;br/&gt;
3461
3462 The next step is, when someone fails to follow that copyleft license,
3463 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3464
3465 and its a simple fact of our modern society that such type of
3466 work&lt;br/&gt;
3467
3468 is incredibly expensive to do and incredibly difficult to do.
3469 &lt;/blockquote&gt;
3470
3471 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3472 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3473 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3474 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3475
3476 &lt;p&gt;As the Debian Website
3477 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3478 &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;
3479 imply, public domain and permissively licensed software can lead to
3480 the production of more proprietary software as people discover useful
3481 software, extend it and or incorporate it into their hardware or
3482 software products. Copyleft licenses such as the GNU GPL were created
3483 to close off this avenue to the production of proprietary software but
3484 such licenses are not enough. With the ongoing adoption of Free
3485 Software by individuals and groups, inevitably the community&#39;s
3486 expectations of license compliance are violated, usually out of
3487 ignorance of the way Free Software works, but not always. As Karen
3488 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3489 Freedom&quot;&gt;FaiF&lt;/a&gt;
3490 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3491 copyleft is nothing if no-one is willing and able to stand up in court
3492 to protect it. The reality of today&#39;s world is that legal
3493 representation is expensive, difficult and time consuming. With
3494 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3495 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3496 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3497 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3498 of the Linux project, Debian and other groups against GPL violations.
3499 In March the SFC supported a
3500 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3501 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3502 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3503 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3504 kernel. Since then two of their sponsors pulled corporate funding and
3505 conferences
3506 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3507 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3508 less on corporate funding and more on the broad community of
3509 individuals who support Free Software and copyleft. So the SFC has
3510 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3511 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3512 a community of folks who stand up for copyleft and the GPL by
3513 supporting their work on promoting and supporting copyleft and Free
3514 Software.&lt;/p&gt;
3515
3516 &lt;p&gt;If you support Free Software,
3517 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3518 what the SFC do, agree with their
3519 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3520 principles&lt;/a&gt;, are happy about their
3521 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3522 work on a project that is an SFC
3523 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3524 just want to stand up for copyleft, please join
3525 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3526 Allan Webber&lt;/a&gt;,
3527 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3528 Smith&lt;/a&gt;,
3529 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3530 Bacon&lt;/a&gt;, myself and
3531 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3532 becoming a
3533 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3534 next week your donation will be
3535 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3536 by an anonymous donor. Please also consider asking your employer to
3537 match your donation or become a sponsor of SFC. Don&#39;t forget to
3538 spread the word about your support for SFC via email, your blog and or
3539 social media accounts.&lt;/p&gt;
3540
3541 &lt;/blockquote&gt;
3542
3543 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3544 of Software Freedom Conservancy myself. Perhaps you should be a
3545 supporter too?&lt;/p&gt;
3546 </description>
3547 </item>
3548
3549 <item>
3550 <title>PGP key transition statement for key EE4E02F9</title>
3551 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3552 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3553 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3554 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3555 set it up properly. I wanted to generate it offline and have it
3556 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3557 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3558 time to sit down with an offline machine almost took forever. But
3559 finally I&#39;ve been able to complete the process, and have now moved
3560 from my old GPG key to a new GPG key. See
3561 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3562 full transition statement, signed with both my old and new key&lt;/a&gt; for
3563 the details. This is my new key:&lt;/p&gt;
3564
3565 &lt;pre&gt;
3566 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]
3567 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3568 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3569 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3570 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3571 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3572 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3573 &lt;/pre&gt;
3574
3575 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3576 my old key.&lt;/p&gt;
3577
3578 &lt;p&gt;If you signed my old key
3579 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3580 I&#39;d very much appreciate a signature on my new key, details and
3581 instructions in the transition statement. I m happy to reciprocate if
3582 you have a similarly signed transition statement to present.&lt;/p&gt;
3583 </description>
3584 </item>
3585
3586 <item>
3587 <title>The life and death of a laptop battery</title>
3588 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3590 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3591 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3592 But this do not last. The last few laptops gave me a feeling that
3593 within a year, the life time is just a fraction of what it used to be,
3594 and it slowly become painful to use the laptop without power connected
3595 all the time. Because of this, when I got a new Thinkpad X230 laptop
3596 about two years ago, I decided to monitor its battery state to have
3597 more hard facts when the battery started to fail.&lt;/p&gt;
3598
3599 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3600
3601 &lt;p&gt;First I tried to find a sensible Debian package to record the
3602 battery status, assuming that this must be a problem already handled
3603 by someone else. I found
3604 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3605 which collects statistics from the battery, but it was completely
3606 broken. I sent a few suggestions to the maintainer, but decided to
3607 write my own collector as a shell script while I waited for feedback
3608 from him. Via
3609 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3610 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3611 discovered
3612 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3613 available in Debian.&lt;/p&gt;
3614
3615 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3616 battery stats ever since. Now my
3617 /var/log/hjemmenett-battery-status.log file contain around 115,000
3618 measurements, from the time the battery was working great until now,
3619 when it is unable to charge above 7% of original capacity. My
3620 collector shell script is quite simple and look like this:&lt;/p&gt;
3621
3622 &lt;pre&gt;
3623 #!/bin/sh
3624 # Inspired by
3625 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3626 # See also
3627 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3628 logfile=/var/log/hjemmenett-battery-status.log
3629
3630 files=&quot;manufacturer model_name technology serial_number \
3631 energy_full energy_full_design energy_now cycle_count status&quot;
3632
3633 if [ ! -e &quot;$logfile&quot; ] ; then
3634 (
3635 printf &quot;timestamp,&quot;
3636 for f in $files; do
3637 printf &quot;%s,&quot; $f
3638 done
3639 echo
3640 ) &gt; &quot;$logfile&quot;
3641 fi
3642
3643 log_battery() {
3644 # Print complete message in one echo call, to avoid race condition
3645 # when several log processes run in parallel.
3646 msg=$(printf &quot;%s,&quot; $(date +%s); \
3647 for f in $files; do \
3648 printf &quot;%s,&quot; $(cat $f); \
3649 done)
3650 echo &quot;$msg&quot;
3651 }
3652
3653 cd /sys/class/power_supply
3654
3655 for bat in BAT*; do
3656 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3657 done
3658 &lt;/pre&gt;
3659
3660 &lt;p&gt;The script is called when the power management system detect a
3661 change in the power status (power plug in or out), and when going into
3662 and out of hibernation and suspend. In addition, it collect a value
3663 every 10 minutes. This make it possible for me know when the battery
3664 is discharging, charging and how the maximum charge change over time.
3665 The code for the Debian package
3666 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3667 available on github&lt;/a&gt;.&lt;/p&gt;
3668
3669 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3670
3671 &lt;pre&gt;
3672 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3673 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3674 [...]
3675 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3676 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3677 &lt;/pre&gt;
3678
3679 &lt;p&gt;I wrote a small script to create a graph of the charge development
3680 over time. This graph depicted above show the slow death of my laptop
3681 battery.&lt;/p&gt;
3682
3683 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3684 dying in a year or two, while the batteries of space probes and
3685 satellites keep working year after year. If we are to believe
3686 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3687 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3688 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3689 all the time, but to stay below 90% of full charge most of the time.
3690 I&#39;ve been told that the Tesla electric cars
3691 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3692 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3693 100% when preparing for a longer trip (not that I would want a car
3694 like Tesla where rights to privacy is abandoned, but that is another
3695 story), which I guess is the option we should have for laptops on
3696 Linux too.&lt;/p&gt;
3697
3698 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3699 stop charging at 80%, unless requested to charge to 100% once in
3700 preparation for a longer trip? I found
3701 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3702 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3703 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3704 load).&lt;/p&gt;
3705
3706 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3707 at the start. I also wonder why the &quot;full capacity&quot; increases some
3708 times, and if it is possible to repeat the process to get the battery
3709 back to design capacity. And I wonder if the discharge and charge
3710 speed change over time, or if this stay the same. I did not yet try
3711 to write a tool to calculate the derivative values of the battery
3712 level, but suspect some interesting insights might be learned from
3713 those.&lt;/p&gt;
3714
3715 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3716 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3717 packages instead of the tp-smapi-dkms package I had tried to use
3718 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3719 and stop. I&#39;ve done so now, but expect my existing battery is toast
3720 and need to be replaced. The proposal is unfortunately Thinkpad
3721 specific.&lt;/p&gt;
3722 </description>
3723 </item>
3724
3725 <item>
3726 <title>New laptop - some more clues and ideas based on feedback</title>
3727 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3728 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3729 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3730 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3731 need for a new laptop, and provided very useful feedback. I wish to
3732 thank every one of these. Several pointed me to the possibility of
3733 fixing my X230, and I am already in the process of getting Lenovo to
3734 do so thanks to the on site, next day support contract covering the
3735 machine. But the battery is almost useless (I expect to replace it
3736 with a non-official battery) and I do not expect the machine to live
3737 for many more years, so it is time to plan its replacement. If I did
3738 not have a support contract, it was suggested to find replacement parts
3739 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3740 might present a language barrier as I do not understand French.&lt;/p&gt;
3741
3742 &lt;p&gt;One tip I got was to use the
3743 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3744 compare laptop models. It seem to have more models available than
3745 prisjakt.no. Another tip I got from someone I know have similar
3746 keyboard preferences was that the HP EliteBook 840 keyboard is not
3747 very good, and this matches my experience with earlier EliteBook
3748 keyboards I tested. Because of this, I will not consider it any further.
3749
3750 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3751 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3752 (which is missing from the X240), and is working fairly well with
3753 Debian Sid/Unstable according to
3754 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3755 got on the keyboard quality are not consistent. Some say the keyboard
3756 is good, others say it is ok, while others say it is not very good.
3757 Those with experience from X41 and and X60 agree that the X250
3758 keyboard is not as good as those trusty old laptops, and suggest I
3759 keep and fix my X230 instead of upgrading, or get a used X230 to
3760 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3761 activity and battery status, which is very convenient on my X230. I&#39;m
3762 also told that the CPU fan is running very often, making it a bit
3763 noisy. In any case, the X250 do not work out of the box with Debian
3764 Stable/Jessie, one of my requirements.&lt;/p&gt;
3765
3766 &lt;p&gt;I have also gotten a few vendor proposals, one was
3767 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3768 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3769 The latter look very attractive to me.&lt;/p&gt;
3770
3771 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
3772 as I keep looking for a replacement.&lt;/p&gt;
3773
3774 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
3775 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
3776 different
3777 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
3778 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
3779 </description>
3780 </item>
3781
3782 <item>
3783 <title>Time to find a new laptop, as the old one is broken after only two years</title>
3784 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
3785 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
3786 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
3787 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
3788 replacement soon. The left 5 cm of the screen on my Thinkpad X230
3789 started flickering yesterday, and I suspect the cause is a broken
3790 cable, as changing the angle of the screen some times get rid of the
3791 flickering.&lt;/p&gt;
3792
3793 &lt;p&gt;My requirements have not really changed since I bought it, and is
3794 still as
3795 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
3796 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
3797 good help from
3798 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
3799 where I could select at least a few of the requirements (mouse pin,
3800 wifi, weight) and go through the rest manually. Three button mouse
3801 and a good keyboard is not available as an option, and all the three
3802 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
3803 G2) lack three mouse buttons). It is also unclear to me how good the
3804 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3805 the keyboard, even if the quality and robustness in the X series have
3806 deteriorated since X41.&lt;/p&gt;
3807
3808 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
3809 seem sensible to me? Are there better services around to search the
3810 set of available laptops for features? Please send me an email if you
3811 have suggestions.&lt;/p&gt;
3812
3813 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
3814 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
3815 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
3816 </description>
3817 </item>
3818
3819 <item>
3820 <title>How to stay with sysvinit in Debian Jessie</title>
3821 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
3822 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
3823 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
3824 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
3825 sysvinit as its boot system by default. But how can one keep using
3826 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3827 courtesy of
3828 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
3829 Schubert&lt;/a&gt; and
3830 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
3831 McVittie&lt;/a&gt;.
3832
3833 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
3834 keep sysvinit as your boot system, create a file
3835 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
3836 you upgrade:&lt;/p&gt;
3837
3838 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3839 Package: systemd-sysv
3840 Pin: release o=Debian
3841 Pin-Priority: -1
3842 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3843
3844 &lt;p&gt;This file content will tell apt and aptitude to not consider
3845 installing systemd-sysv as part of any installation and upgrade
3846 solution when resolving dependencies, and thus tell it to avoid
3847 systemd as a default boot system. The end result should be that the
3848 upgraded system keep using sysvinit.&lt;/p&gt;
3849
3850 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
3851 get sysvinit installed by default (debootstrap used by
3852 debian-installer have no option for this), but one can tell the
3853 installer to switch to sysvinit before the first boot. Either by
3854 using a kernel argument to the installer, or by adding a line to the
3855 preseed file used. First, the kernel command line argument:
3856
3857 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3858 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
3859 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3860
3861 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
3862
3863 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3864 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3865 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3866
3867 &lt;p&gt;One can of course also do this after the first boot by installing
3868 the sysvinit-core package.&lt;/p&gt;
3869
3870 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
3871 sysvinit boot sequence in Debian have several hardware specific bugs
3872 on Linux caused by the fact that it is unpredictable when hardware
3873 devices show up during boot. But on the other hand, the new default
3874 boot system still have a few rough edges I hope will be fixed before
3875 Jessie is released.&lt;/p&gt;
3876
3877 &lt;p&gt;Update 2014-11-26: Inspired by
3878 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
3879 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
3880 line.&lt;/p&gt;
3881 </description>
3882 </item>
3883
3884 <item>
3885 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
3886 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
3887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
3888 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
3889 <description>&lt;p&gt;The right to communicate with your friends and family in private,
3890 without anyone snooping, is a right every citicen have in a liberal
3891 democracy. But this right is under serious attack these days.&lt;/p&gt;
3892
3893 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
3894 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3895 the whisleblower Snowden) more expensive for Internet email,
3896 is to deliver all email using SMTP via Tor. Such SMTP option would be
3897 a nice addition to the FreedomBox project if we could send email
3898 between FreedomBox machines without leaking metadata about the emails
3899 to the people peeking on the wire. I
3900 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
3901 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
3902 lot of useful feedback and suggestions. It also became obvious to me
3903 that this was not a novel idea, as the same idea was tested and
3904 documented by Johannes Berg as early as 2006, and both
3905 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
3906 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
3907 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
3908
3909 &lt;p&gt;To implement such system one need to set up a Tor hidden service
3910 providing the SMTP protocol on port 25, and use email addresses
3911 looking like username@hidden-service-name.onion. With such addresses
3912 the connections to port 25 on hidden-service-name.onion using Tor will
3913 go to the correct SMTP server. To do this, one need to configure the
3914 Tor daemon to provide the hidden service and the mail server to accept
3915 emails for this .onion domain. To learn more about Exim configuration
3916 in Debian and test the design provided by Johannes Berg in his FAQ, I
3917 set out yesterday to create a Debian package for making it trivial to
3918 set up such SMTP over Tor service based on Debian. Getting it to work
3919 were fairly easy, and
3920 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
3921 source code for the Debian package&lt;/a&gt; is available from github. I
3922 plan to move it into Debian if further testing prove this to be a
3923 useful approach.&lt;/p&gt;
3924
3925 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
3926 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
3927 get rid of exim4). Install tor, clone the git repository mentioned
3928 above, build the deb and install it on the machine. Next, run
3929 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
3930 the instructions to get the service up and running. Restart tor and
3931 exim when it is done, and test mail delivery using swaks like
3932 this:&lt;/p&gt;
3933
3934 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3935 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3936 --to fbx@dutlqrrmjhtfa3vp.onion
3937 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3938
3939 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
3940 address with your own address to test your server. :)&lt;/p&gt;
3941
3942 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
3943 easier and more automatic. Especially the tor setup need more work.
3944 Also, the package include a tor-smtp tool written in C, but its task
3945 should probably be rewritten in some script language to make the deb
3946 architecture independent. It would probably also make the code easier
3947 to review. The tor-smtp tool currently need to listen on a socket for
3948 exim to talk to it and is started using xinetd. It would be better if
3949 no daemon and no socket is needed. I suspect it is possible to get
3950 exim to run a command line tool for delivery instead of talking to a
3951 socket, and hope to figure out how in a future version of this
3952 system.&lt;/p&gt;
3953
3954 &lt;p&gt;Until I wipe my test machine, I can be reached using the
3955 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
3956 SMTorP. :)&lt;/p&gt;
3957 </description>
3958 </item>
3959
3960 <item>
3961 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
3962 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
3963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
3964 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
3965 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
3966 alioth.debian.org, you know the web interface is fairly slow to
3967 operate. First you visit one web page, enter the moderation password
3968 and get a new page shown with a list of all the messages to moderate
3969 and various options for each email address. This take a while for
3970 every list you moderate, and you need to do it regularly to do a good
3971 job as a list moderator. But there is a quick alternative,
3972 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
3973 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
3974 to moderate in a fraction of a second. Here is a test run on two
3975 lists I recently took over:&lt;/p&gt;
3976
3977 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3978 % time listadmin xiph
3979 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3980 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3981
3982 real 0m1.709s
3983 user 0m0.232s
3984 sys 0m0.012s
3985 %
3986 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3987
3988 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
3989 there are no message in the moderation queue. Every morning I
3990 currently moderate 68 mailman lists, and it normally take around two
3991 minutes. When I took over the two pkg-xiph lists above a few days
3992 ago, there were 400 emails waiting in the moderator queue. It took me
3993 less than 15 minutes to process them all using the listadmin
3994 program.&lt;/p&gt;
3995
3996 &lt;p&gt;If you install
3997 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
3998 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
3999 with content like this, the moderation task is a breeze:&lt;/p&gt;
4000
4001 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4002 username username@example.org
4003 spamlevel 23
4004 default discard
4005 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
4006
4007 password secret
4008 adminurl https://{domain}/mailman/admindb/{list}
4009 mailman-list@lists.example.com
4010
4011 password hidden
4012 other-list@otherserver.example.org
4013 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4014
4015 &lt;p&gt;There are other options to set as well. Check the manual page to
4016 learn the details.&lt;/p&gt;
4017
4018 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
4019 the SSL certificate is self signed or not properly signed by a
4020 generally accepted signing authority, you can set a environment
4021 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
4022
4023 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4024 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
4025 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4026
4027 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
4028 can provide an argument to the listadmin script like I do in the
4029 initial screen dump (the xiph argument). Using an argument, only
4030 lists matching the argument string will be processed. This make it
4031 quick to accept messages if you notice the moderation request in your
4032 email.&lt;/p&gt;
4033
4034 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
4035 mailing lists, as I simply do not have time to spend on that if the
4036 process was any slower. The listadmin program have saved me hours of
4037 time I could spend elsewhere over the years. It truly is nice free
4038 software.&lt;/p&gt;
4039
4040 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4041 activities, please send Bitcoin donations to my address
4042 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4043
4044 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
4045 configuration example. Also, I&#39;ve been told that the
4046 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
4047 sure why.&lt;/p&gt;
4048 </description>
4049 </item>
4050
4051 <item>
4052 <title>Debian Jessie, PXE and automatic firmware installation</title>
4053 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
4054 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
4055 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
4056 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
4057 problem that the WiFi card require some firmware to work properly.
4058 And it has been a pain to fix this using preseeding in Debian.
4059 Normally something more is needed. But thanks to
4060 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
4061 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
4062 to do this using simple preseeding.&lt;/p&gt;
4063
4064 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
4065 firmware for the hardware found in the machine (actually, requested by
4066 the kernel modules for the hardware). (It can also install user space
4067 programs supporting the hardware detected, but that is not the focus
4068 of this story.)&lt;/p&gt;
4069
4070 &lt;p&gt;To get this working in the default installation, two preeseding
4071 values are needed. First, the isenkram-cli package must be installed
4072 into the target chroot (aka the hard drive) before tasksel is executed
4073 in the pkgsel step of the debian-installer system. This is done by
4074 preseeding the base-installer/includes debconf value to include the
4075 isenkram-cli package. The package name is next passed to debootstrap
4076 for installation. With the isenkram-cli package in place, tasksel
4077 will automatically use the isenkram tasks to detect hardware specific
4078 packages for the machine being installed and install them, because
4079 isenkram-cli contain tasksel tasks.&lt;/p&gt;
4080
4081 &lt;p&gt;Second, one need to enable the non-free APT repository, because
4082 most firmware unfortunately is non-free. This is done by preseeding
4083 the apt-mirror-setup step. This is unfortunate, but for a lot of
4084 hardware it is the only option in Debian.&lt;/p&gt;
4085
4086 &lt;p&gt;The end result is two lines needed in your preseeding file to get
4087 firmware installed automatically by the installer:&lt;/p&gt;
4088
4089 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4090 base-installer base-installer/includes string isenkram-cli
4091 apt-mirror-setup apt-setup/non-free boolean true
4092 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4093
4094 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
4095 both firmware and user space packages when using this method. It also
4096 do not work well, so use version 0.15 or later. Installing both
4097 firmware and user space packages might give you a bit more than you
4098 want, so I decided to split the tasksel task in two, one for firmware
4099 and one for user space programs. The firmware task is enabled by
4100 default, while the one for user space programs is not. This split is
4101 implemented in the package currently in unstable.&lt;/p&gt;
4102
4103 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
4104 this recipe work for you. :)&lt;/p&gt;
4105
4106 &lt;p&gt;So, I bet you are wondering, how can this work. First and
4107 foremost, it work because tasksel is modular, and driven by whatever
4108 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4109 isenkram-cli package place two files for tasksel to find. First there
4110 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
4111
4112 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4113 Task: isenkram-packages
4114 Section: hardware
4115 Description: Hardware specific packages (autodetected by isenkram)
4116 Based on the detected hardware various hardware specific packages are
4117 proposed.
4118 Test-new-install: show show
4119 Relevance: 8
4120 Packages: for-current-hardware
4121
4122 Task: isenkram-firmware
4123 Section: hardware
4124 Description: Hardware specific firmware packages (autodetected by isenkram)
4125 Based on the detected hardware various hardware specific firmware
4126 packages are proposed.
4127 Test-new-install: mark show
4128 Relevance: 8
4129 Packages: for-current-hardware-firmware
4130 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4131
4132 &lt;p&gt;The key parts are Test-new-install which indicate how the task
4133 should be handled and the Packages line referencing to a script in
4134 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4135 list of packages to install. The for-current-hardware-firmware script
4136 look like this to list relevant firmware for the machine:
4137
4138 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4139 #!/bin/sh
4140 #
4141 PATH=/usr/sbin:$PATH
4142 export PATH
4143 isenkram-autoinstall-firmware -l
4144 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4145
4146 &lt;p&gt;With those two pieces in place, the firmware is installed by
4147 tasksel during the normal d-i run. :)&lt;/p&gt;
4148
4149 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
4150 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
4151 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
4152 install.&lt;/p&gt;
4153
4154 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
4155 pilots in testing this feature, as isenkram is used there now to
4156 install firmware, replacing the earlier scripts.&lt;/p&gt;
4157 </description>
4158 </item>
4159
4160 <item>
4161 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
4162 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
4163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
4164 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
4165 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
4166 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4167 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
4168 on a screen normally showing the bread types and prizes:&lt;/p&gt;
4169
4170 &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;
4171
4172 &lt;p&gt;If it had booted as it was supposed to, I would never had known
4173 about this hidden Linux installation. It is interesting what
4174 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
4175 </description>
4176 </item>
4177
4178 <item>
4179 <title>New lsdvd release version 0.17 is ready</title>
4180 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
4181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
4182 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
4183 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
4184 got a new set of developers a few weeks ago, after the original
4185 developer decided to step down and pass the project to fresh blood.
4186 This project is now maintained by Petter Reinholdtsen and Steve
4187 Dibb.&lt;/p&gt;
4188
4189 &lt;p&gt;I just wrapped up
4190 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
4191 new lsdvd release&lt;/a&gt;, available in git or from
4192 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
4193 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
4194 0.17.&lt;/p&gt;
4195
4196 &lt;ul&gt;
4197
4198 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
4199 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
4200 non-existant, to work around additional copy protection&lt;/li&gt;
4201 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
4202 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
4203 &lt;li&gt;Fix include orders&lt;/li&gt;
4204 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
4205 &lt;li&gt;Fix the chapter count&lt;/li&gt;
4206 &lt;li&gt;Make sure the array size and the array limit used when initialising
4207 the palette size is the same.&lt;/li&gt;
4208 &lt;li&gt;Fix array printing.&lt;/li&gt;
4209 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
4210 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
4211 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
4212 with more GCC compiler warnings.&lt;/li&gt;
4213
4214 &lt;/ul&gt;
4215
4216 &lt;p&gt;This change bring together patches for lsdvd in use in various
4217 Linux and Unix distributions, as well as patches submitted to the
4218 project the last nine years. Please check it out. :)&lt;/p&gt;
4219 </description>
4220 </item>
4221
4222 <item>
4223 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
4224 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
4225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
4226 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
4227 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4228 project&lt;/a&gt; provide a Linux solution for schools, including a
4229 powerful desktop with education software, a central server providing
4230 web pages, user database, user home directories, central login and PXE
4231 boot of both clients without disk and the installation to install Debian
4232 Edu on machines with disk (and a few other services perhaps to small
4233 to mention here). We in the Debian Edu team are currently working on
4234 the Jessie based version, trying to get everything in shape before the
4235 freeze, to avoid having to maintain our own package repository in the
4236 future. The
4237 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
4238 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
4239 work left. Some fatal problems block testing, breaking the installer,
4240 but it is possible to work around these to get anyway. Here is a
4241 recipe on how to get the installation limping along.&lt;/p&gt;
4242
4243 &lt;p&gt;First, download the test ISO via
4244 &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;,
4245 &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;
4246 or rsync (use
4247 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
4248 The ISO build was broken on Tuesday, so we do not get a new ISO every
4249 12 hours or so, but thankfully the ISO we already got we are able to
4250 install with some tweaking.&lt;/p&gt;
4251
4252 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
4253 (use Alt-Ctrl-F2), run&lt;/p&gt;
4254
4255 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4256 nano /usr/bin/edu-eatmydata-install
4257 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4258
4259 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
4260 optimization. Return to the installation, select the profile you want
4261 and continue. Without this change, exim4-config will fail to install
4262 due to a known bug in eatmydata.&lt;/p&gt;
4263
4264 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
4265 this do not work, figure out what your correct value would be. All my
4266 test machines need /dev/sda, so I have no advice if it do not fit
4267 your need.&lt;/p&gt;
4268
4269 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
4270 root after the initial boot from hard drive, and install the
4271 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4272 or mate. If you want several desktop options, install more than one
4273 metapackage. Once this is done, reboot and you should have a working
4274 graphical login screen. This workaround should no longer be needed
4275 once the education-tasks package version 1.801 enter testing in two
4276 days.&lt;/p&gt;
4277
4278 &lt;p&gt;I believe the ISO build will start working on two days when the new
4279 tasksel package enter testing and Steve McIntyre get a chance to
4280 update the debian-cd git repository. The eatmydata, grub and desktop
4281 issues are already fixed in unstable and testing, and should show up
4282 on the ISO as soon as the ISO build start working again. Well the
4283 eatmydata optimization is really just disabled. The proper fix
4284 require an upload by the eatmydata maintainer applying the patch
4285 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4286 The rest have proper fixes in unstable.&lt;/p&gt;
4287
4288 &lt;p&gt;I hope this get you going with the installation testing, as we are
4289 quickly running out of time trying to get our Jessie based
4290 installation ready before the distribution freeze in a month.&lt;/p&gt;
4291 </description>
4292 </item>
4293
4294 <item>
4295 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4296 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4298 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4299 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4300 to handle my fairly large DVD collection. It is a nice command line
4301 tool to get details about a DVD, like title, tracks, track length,
4302 etc, in XML, Perl or human readable format. But lsdvd have not seen
4303 any new development since 2006 and had a few irritating bugs affecting
4304 its use with some DVDs. Upstream seemed to be dead, and in January I
4305 sent a small probe asking for a version control repository for the
4306 project, without any reply. But I use it regularly and would like to
4307 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4308 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4309 the project admin, and after getting a reply from him explaining that
4310 he was no longer interested in the project, I asked if I could take
4311 over. And yesterday, I became project admin.&lt;/p&gt;
4312
4313 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4314 maintainer interested in joining forces to maintain the upstream
4315 project, and I hope we can get a new release out fairly quickly,
4316 collecting the patches spread around on the internet into on place.
4317 I&#39;ve added the relevant Debian patches to the freshly created git
4318 repository, and expect the Gentoo patches to make it too. If you got
4319 a DVD collection and care about command line tools, check out
4320 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4321 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4322 list&lt;/a&gt;. :)&lt;/p&gt;
4323 </description>
4324 </item>
4325
4326 <item>
4327 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4328 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4330 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4331 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4332 a lot quicker. When we install more than 2000 packages in
4333 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4334 tasksel in the installer, unpacking the binary packages take forever.
4335 A part of the slow I/O issue was discussed in
4336 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4337 much file system sync-ing done by dpkg, which is the package
4338 responsible for unpacking the binary packages. Other parts (like code
4339 executed by postinst scripts) might also sync to disk during
4340 installation. All this sync-ing to disk do not really make sense to
4341 me. If the machine crash half-way through, I start over, I do not try
4342 to salvage the half installed system. So the failure sync-ing is
4343 supposed to protect against, hardware or system crash, is not really
4344 relevant while the installer is running.&lt;/p&gt;
4345
4346 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4347 system sync()-ing in a fairly non-intrusive way, without the need to
4348 change the code in several packages. The idea is not new, but I have
4349 not heard anyone propose the approach using dpkg-divert before. It
4350 depend on the small and clever package
4351 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4352 uses LD_PRELOAD to replace the system functions for syncing data to
4353 disk with functions doing nothing, thus allowing programs to live
4354 dangerous while speeding up disk I/O significantly. Instead of
4355 modifying the implementation of dpkg, apt and tasksel (which are the
4356 packages responsible for selecting, fetching and installing packages),
4357 it occurred to me that we could just divert the programs away, replace
4358 them with a simple shell wrapper calling
4359 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4360 Two days ago I decided to test the idea, and wrapped up a simple
4361 implementation for the Debian Edu udeb.&lt;/p&gt;
4362
4363 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4364 time of the pkgsel step (installing tasks) from 64 to less than 44
4365 minutes (20 minutes shaved off the installation) on an old Dell
4366 Latitude D505 machine. I am not quite sure what the optimised time
4367 would have been, as I messed up the testing a bit, causing the debconf
4368 priority to get low enough for two questions to pop up during
4369 installation. As soon as I saw the questions I moved the installation
4370 along, but do not know how long the question were holding up the
4371 installation. I did some more measurements using Debian Edu Jessie,
4372 and got these results. The time measured is the time stamp in
4373 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4374 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4375 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4376 timing thus do not depend on how quickly the user handle the tasksel
4377 dialog.&lt;/p&gt;
4378
4379 &lt;p&gt;&lt;table&gt;
4380
4381 &lt;tr&gt;
4382 &lt;th&gt;Machine/setup&lt;/th&gt;
4383 &lt;th&gt;Original tasksel&lt;/th&gt;
4384 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4385 &lt;th&gt;Reduction&lt;/th&gt;
4386 &lt;/tr&gt;
4387
4388 &lt;tr&gt;
4389 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4390 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4391 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4392 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4393 &lt;/tr&gt;
4394
4395 &lt;tr&gt;
4396 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4397 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4398 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4399 &lt;td&gt;23 min 40%&lt;/td&gt;
4400 &lt;/tr&gt;
4401
4402 &lt;tr&gt;
4403 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4404 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4405 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4406 &lt;td&gt;11 min 50%&lt;/td&gt;
4407 &lt;/tr&gt;
4408
4409 &lt;tr&gt;
4410 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4411 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4412 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4413 &lt;td&gt;2 min 33%&lt;/td&gt;
4414 &lt;/tr&gt;
4415
4416 &lt;tr&gt;
4417 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4418 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4419 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4420 &lt;td&gt;4 min 21%&lt;/td&gt;
4421 &lt;/tr&gt;
4422
4423 &lt;/table&gt;&lt;/p&gt;
4424
4425 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4426 time is spent downloading packages. The connection to the Internet
4427 was 100Mbit/s during testing, so downloading should not be a
4428 significant factor in the measurement. Download typically took a few
4429 seconds to a few minutes, depending on the amount of packages being
4430 installed.&lt;/p&gt;
4431
4432 &lt;p&gt;The speedup is implemented by using two hooks in
4433 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4434 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4435 finish-install.d hook to remove the divert at the end of the
4436 installation. I picked the pre-pkgsel.d hook instead of the
4437 post-base-installer.d hook because I test using an ISO without the
4438 eatmydata package included, and the post-base-installer.d hook in
4439 Debian Edu can only operate on packages included in the ISO. The
4440 negative effect of this is that I am unable to activate this
4441 optimization for the kernel installation step in d-i. If the code is
4442 moved to the post-base-installer.d hook, the speedup would be larger
4443 for the entire installation.&lt;/p&gt;
4444
4445 &lt;p&gt;I&#39;ve implemented this in the
4446 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4447 git repository, and plan to provide the optimization as part of the
4448 Debian Edu installation. If you want to test this yourself, you can
4449 create two files in the installer (or in an udeb). One shell script
4450 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4451
4452 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4453 #!/bin/sh
4454 set -e
4455 . /usr/share/debconf/confmodule
4456 info() {
4457 logger -t my-pkgsel &quot;info: $*&quot;
4458 }
4459 error() {
4460 logger -t my-pkgsel &quot;error: $*&quot;
4461 }
4462 override_install() {
4463 apt-install eatmydata || true
4464 if [ -x /target/usr/bin/eatmydata ] ; then
4465 for bin in dpkg apt-get aptitude tasksel ; do
4466 file=/usr/bin/$bin
4467 # Test that the file exist and have not been diverted already.
4468 if [ -f /target$file ] ; then
4469 info &quot;diverting $file using eatmydata&quot;
4470 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4471 &gt; /target$file.edu
4472 chmod 755 /target$file.edu
4473 in-target dpkg-divert --package debian-edu-config \
4474 --rename --quiet --add $file
4475 ln -sf ./$bin.edu /target$file
4476 else
4477 error &quot;unable to divert $file, as it is missing.&quot;
4478 fi
4479 done
4480 else
4481 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4482 fi
4483 }
4484
4485 override_install
4486 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4487
4488 &lt;p&gt;To clean up, another shell script should go into
4489 /usr/lib/finish-install.d/ with code like this:
4490
4491 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4492 #! /bin/sh -e
4493 . /usr/share/debconf/confmodule
4494 error() {
4495 logger -t my-finish-install &quot;error: $@&quot;
4496 }
4497 remove_install_override() {
4498 for bin in dpkg apt-get aptitude tasksel ; do
4499 file=/usr/bin/$bin
4500 if [ -x /target$file.edu ] ; then
4501 rm /target$file
4502 in-target dpkg-divert --package debian-edu-config \
4503 --rename --quiet --remove $file
4504 rm /target$file.edu
4505 else
4506 error &quot;Missing divert for $file.&quot;
4507 fi
4508 done
4509 sync # Flush file buffers before continuing
4510 }
4511
4512 remove_install_override
4513 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4514
4515 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4516 edu-eatmydata-install and call it from the pre-pkgsel.d and
4517 finish-install.d scripts.&lt;/p&gt;
4518
4519 &lt;p&gt;By now you might ask if this change should get into the normal
4520 Debian installer too? I suspect it should, but am not sure the
4521 current debian-installer coordinators find it useful enough. It also
4522 depend on the side effects of the change. I&#39;m not aware of any, but I
4523 guess we will see if the change is safe after some more testing.
4524 Perhaps there is some package in Debian depending on sync() and
4525 fsync() having effect? Perhaps it should go into its own udeb, to
4526 allow those of us wanting to enable it to do so without affecting
4527 everyone.&lt;/p&gt;
4528
4529 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4530 will break installation of all programs using gnutls because of
4531 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4532 eatmydata package in Debian will solve it.&lt;/p&gt;
4533
4534 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4535 the optimization work again. And I have discovered that the
4536 dpkg-divert trick is not really needed and implemented a slightly
4537 simpler approach as part of the debian-edu-install package. See
4538 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4539
4540 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4541 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4542 triggering on i386 made it into testing, and broke this installation
4543 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4544 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4545 </description>
4546 </item>
4547
4548 <item>
4549 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4550 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4551 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4552 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4553 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4554 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4555 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4556 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4557 learn that there is a large set of publicly available key servers to
4558 use when looking for peoples public key. So far I have used
4559 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4560 were misbehaving, but those days are ended. The servers I have used
4561 up until yesterday have been slow and some times unavailable. I hope
4562 those problems are gone now.&lt;/p&gt;
4563
4564 &lt;p&gt;Behind the round robin DNS entry of the
4565 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4566 there is a pool of more than 100 keyservers which are checked every
4567 day to ensure they are well connected and up to date. It must be
4568 better than what I have used so far. :)&lt;/p&gt;
4569
4570 &lt;p&gt;Yesterdays speaker told me that the service is the default
4571 keyserver provided by the default configuration in GnuPG, but this do
4572 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4573
4574 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4575 line:&lt;/p&gt;
4576
4577 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4578 keyserver pool.sks-keyservers.net
4579 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4580
4581 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4582 entries in DNS. Just for fun, I did just that at work, so now every
4583 user of GnuPG at the University of Oslo should find a OpenGPG
4584 keyserver automatically should their need it:&lt;/p&gt;
4585
4586 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4587 % host -t srv _pgpkey-http._tcp.uio.no
4588 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4589 %
4590 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4591
4592 &lt;p&gt;Now if only
4593 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4594 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4595 very happy. It can look up a given key or search for a user ID, but I
4596 normally do not want that, but to find a trust path from my key to
4597 another key. Given a user ID or key ID, I would like to find (and
4598 download) the keys representing a signature path from my key to the
4599 key in question, to be able to get a trust path between the two keys.
4600 This is as far as I can tell not possible today. Perhaps something
4601 for a future version of the protocol?&lt;/p&gt;
4602 </description>
4603 </item>
4604
4605 <item>
4606 <title>From English wiki to translated PDF and epub via Docbook</title>
4607 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4609 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4610 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4611 project&lt;/a&gt; provide an instruction manual for teachers, system
4612 administrators and other users that contain useful tips for setting up
4613 and maintaining a Debian Edu installation. This text is about how the
4614 text processing of this manual is handled in the project.&lt;/p&gt;
4615
4616 &lt;p&gt;One goal of the project is to provide information in the native
4617 language of its users, and for this we need to handle translations.
4618 But we also want to make sure each language contain the same
4619 information, so for this we need a good way to keep the translations
4620 in sync. And we want it to be easy for our users to improve the
4621 documentation, avoiding the need to learn special formats or tools to
4622 contribute, and the obvious way to do this is to make it possible to
4623 edit the documentation using a web browser. We also want it to be
4624 easy for translators to keep the translation up to date, and give them
4625 help in figuring out what need to be translated. Here is the list of
4626 tools and the process we have found trying to reach all these
4627 goals.&lt;/p&gt;
4628
4629 &lt;p&gt;We maintain the authoritative source of our manual in the
4630 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4631 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4632 front page with references to the different chapters, several pages
4633 for each chapter, and finally one &quot;collection page&quot; gluing all the
4634 chapters together into one large web page (aka
4635 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4636 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4637 processing and translations. Thanks to the fact that the
4638 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4639 wiki.debian.org support exporting pages in
4640 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4641 the list of pages to export using the raw version of the AllInOne
4642 page, loop over each of them to generate a Docbook XML version of the
4643 manual. This process also download images and transform image
4644 references to use the locally downloaded images. The generated
4645 Docbook XML files are slightly broken, so some post-processing is done
4646 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4647 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4648 a handfull of images. The XML file can now be used to generate PDF, HTML
4649 and epub versions of the English manual. This is the basic step of
4650 our process, making PDF (using dblatex), HTML (using xsltproc) and
4651 epub (using dbtoepub) version from Docbook XML, and the resulting files
4652 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4653
4654 &lt;p&gt;But English documentation is not enough for us. We want translated
4655 documentation too, and we want to make it easy for translators to
4656 track the English original. For this we use the
4657 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4658 which allow us to transform the English Docbook XML file into a
4659 translation file (a .pot file), usable with the normal gettext based
4660 translation tools used by those translating free software. The pot
4661 file is used to create and maintain translation files (several .po
4662 files), which the translations update with the native language
4663 translations of all titles, paragraphs and blocks of text in the
4664 original. The next step is combining the original English Docbook XML
4665 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4666 create a translated Docbook XML file (in this case
4667 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4668 translated, if the translation is not complete) Docbook XML file can
4669 then be used like the original to create a PDF, HTML and epub version
4670 of the documentation.&lt;/p&gt;
4671
4672 &lt;p&gt;The translators use different tools to edit the .po files. We
4673 recommend using
4674 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4675 while some use emacs and vi, others can use web based editors like
4676 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4677 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4678 is where the .po file end up, in our git repository. Updated
4679 translations can either be committed directly to git, or submitted as
4680 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4681 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4682
4683 &lt;p&gt;One challenge is images, which both might need to be translated (if
4684 they show translated user applications), and are needed in different
4685 formats when creating PDF and HTML versions (epub is a HTML version in
4686 this regard). For this we transform the original PNG images to the
4687 needed density and format during build, and have a way to provide
4688 translated images by storing translated versions in
4689 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4690 package maintainers know more.&lt;/p&gt;
4691
4692 &lt;p&gt;If you wonder what the result look like, we provide
4693 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4694 of the documentation packages on the web&lt;/a&gt;. See for example the
4695 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4696 PDF version&lt;/a&gt; or the
4697 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4698 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4699 but perhaps it will be done in the future.&lt;/p&gt;
4700
4701 &lt;p&gt;To learn more, check out
4702 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4703 debian-edu-doc package&lt;/a&gt;,
4704 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4705 manual on the wiki&lt;/a&gt; and
4706 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4707 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4708 </description>
4709 </item>
4710
4711 <item>
4712 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4713 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4715 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4716 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4717 related packages relevant for the computer installed automatically.
4718 So I implemented one, using
4719 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4720 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4721 run tasksel as user root. You should be presented with a new option,
4722 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4723 select it, tasksel will install the packages isenkram claim is fit for
4724 the current hardware, hot pluggable or not.&lt;p&gt;
4725
4726 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4727 description, and the other is the script used to extract the list of
4728 packages to install. The first part is in
4729 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4730 this:&lt;/p&gt;
4731
4732 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4733 Task: isenkram
4734 Section: hardware
4735 Description: Hardware specific packages (autodetected by isenkram)
4736 Based on the detected hardware various hardware specific packages are
4737 proposed.
4738 Test-new-install: mark show
4739 Relevance: 8
4740 Packages: for-current-hardware
4741 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4742
4743 &lt;p&gt;The second part is in
4744 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4745 this:&lt;/p&gt;
4746
4747 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4748 #!/bin/sh
4749 #
4750 (
4751 isenkram-lookup
4752 isenkram-autoinstall-firmware -l
4753 ) | sort -u
4754 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4755
4756 &lt;p&gt;All in all, a very short and simple implementation making it
4757 trivial to install the hardware dependent package we all may want to
4758 have installed on our machines. I&#39;ve not been able to find a way to
4759 get tasksel to tell you exactly which packages it plan to install
4760 before doing the installation. So if you are curious or careful,
4761 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4762
4763 &lt;p&gt;The information about which packages are handling which hardware is
4764 fetched either from the isenkram package itself in
4765 /usr/share/isenkram/, from git.debian.org or from the APT package
4766 database (using the Modaliases header). The APT package database
4767 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4768 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4769 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4770 the python-apt code (bug
4771 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
4772 workaround I was able to get rid of the file descriptor leak and
4773 reduce the memory leak from ~30 MiB per hardware detection down to
4774 around 2 MiB per hardware detection. It should make the desktop
4775 daemon a lot more useful. The fix is in version 0.7 uploaded to
4776 unstable today.&lt;/p&gt;
4777
4778 &lt;p&gt;I believe the current way of mapping hardware to packages in
4779 Isenkram is is a good draft, but in the future I expect isenkram to
4780 use the AppStream data source for this. A proposal for getting proper
4781 AppStream support into Debian is floating around as
4782 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
4783 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
4784 project&lt;/a&gt; will take place this summer to improve the situation. I
4785 look forward to seeing the result, and welcome patches for isenkram to
4786 start using the information when it is ready.&lt;/p&gt;
4787
4788 &lt;p&gt;If you want your package to map to some specific hardware, either
4789 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
4790 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
4791 package&lt;/a&gt; or submit a bug report with the details to the isenkram
4792 package. See also
4793 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
4794 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
4795 the information will be migrated to AppStream eventually, but for the
4796 moment I got no better place to store it.&lt;/p&gt;
4797 </description>
4798 </item>
4799
4800 <item>
4801 <title>FreedomBox milestone - all packages now in Debian Sid</title>
4802 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
4803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
4804 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
4805 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4806 project&lt;/a&gt; is working on providing the software and hardware to make
4807 it easy for non-technical people to host their data and communication
4808 at home, and being able to communicate with their friends and family
4809 encrypted and away from prying eyes. It is still going strong, and
4810 today a major mile stone was reached.&lt;/p&gt;
4811
4812 &lt;p&gt;Today, the last of the packages currently used by the project to
4813 created the system images were accepted into Debian Unstable. It was
4814 the freedombox-setup package, which is used to configure the images
4815 during build and on the first boot. Now all one need to get going is
4816 the build code from the freedom-maker git repository and packages from
4817 Debian. And once the freedombox-setup package enter testing, we can
4818 build everything directly from Debian. :)&lt;/p&gt;
4819
4820 &lt;p&gt;Some key packages used by Freedombox are
4821 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
4822 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
4823 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
4824 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
4825 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
4826 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
4827 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
4828 are plans to integrate more packages into the setup. User
4829 documentation is maintained on the Debian wiki. Please
4830 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
4831 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
4832
4833 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
4834 setup, run this on a Debian machine using a user with sudo rights to
4835 become root:&lt;/p&gt;
4836
4837 &lt;p&gt;&lt;pre&gt;
4838 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4839 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4840 u-boot-tools
4841 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4842 freedom-maker
4843 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4844 &lt;/pre&gt;&lt;/p&gt;
4845
4846 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4847 devices. See the README in the freedom-maker git repo for more
4848 details on the build. If you do not want all three images, trim the
4849 make line. Note that the virtualbox-image target is not really
4850 virtualbox specific. It create a x86 image usable in kvm, qemu,
4851 vmware and any other x86 virtual machine environment. You might need
4852 the version of vmdebootstrap in Jessie to get the build working, as it
4853 include fixes for a race condition with kpartx.&lt;/p&gt;
4854
4855 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4856 method, boot a Debian Wheezy ISO and use this boot argument to load
4857 the preseed values:&lt;/p&gt;
4858
4859 &lt;p&gt;&lt;pre&gt;
4860 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;
4861 &lt;/pre&gt;&lt;/p&gt;
4862
4863 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
4864 it still work.&lt;/p&gt;
4865
4866 &lt;p&gt;If you wonder how to help, one task you could look at is using
4867 systemd as the boot system. It will become the default for Linux in
4868 Jessie, so we need to make sure it is usable on the Freedombox. I did
4869 a simple test a few weeks ago, and noticed dnsmasq failed to start
4870 during boot when using systemd. I suspect there are other problems
4871 too. :) To detect problems, there is a test suite included, which can
4872 be run from the plinth web interface.&lt;/p&gt;
4873
4874 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4875 us get the new release published. :) Please join us on
4876 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4877 irc.debian.org)&lt;/a&gt; and
4878 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4879 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4880 </description>
4881 </item>
4882
4883 <item>
4884 <title>S3QL, a locally mounted cloud file system - nice free software</title>
4885 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
4886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
4887 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
4888 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
4889 solution for use at home. My requirements are simple, it must be
4890 cheap and locally encrypted (in other words, I keep the encryption
4891 keys, the storage provider do not have access to my private files).
4892 One idea me and my friends had many years ago, before the cloud
4893 storage providers showed up, was to use Google mail as storage,
4894 writing a Linux block device storing blocks as emails in the mail
4895 service provided by Google, and thus get heaps of free space. On top
4896 of this one can add encryption, RAID and volume management to have
4897 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4898 I never found time to implement such system. But the last few weeks I
4899 have looked at a system called
4900 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
4901 mounted network backed file system with the features I need.&lt;/p&gt;
4902
4903 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
4904 handling several different storage providers, any with Amazon S3,
4905 Google Drive or OpenStack API. There are heaps of such storage
4906 providers. S3QL can also use a local directory as storage, which
4907 combined with sshfs allow for file storage on any ssh server. S3QL
4908 include support for encryption, compression, de-duplication, snapshots
4909 and immutable file systems, allowing me to mount the remote storage as
4910 a local mount point, look at and use the files as if they were local,
4911 while the content is stored in the cloud as well. This allow me to
4912 have a backup that should survive fire. The file system can not be
4913 shared between several machines at the same time, as only one can
4914 mount it at the time, but any machine with the encryption key and
4915 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
4916
4917 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
4918 package is included already. So to get started, run &lt;tt&gt;apt-get
4919 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
4920 Greenqloud, after reading their nice recipe on
4921 &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
4922 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
4923 in Iceland more than those in USA when it come to keeping my personal
4924 data safe and private, and thus would rather spend money on a company
4925 in Iceland. Another nice recipe is available from the article
4926 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
4927 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
4928 Admin magazine. When the provider is picked, figure out how to get
4929 the API key needed to connect to the storage API. With Greencloud,
4930 the key did not show up until I had added payment details to my
4931 account.&lt;/p&gt;
4932
4933 &lt;p&gt;Armed with the API access details, it is time to create the file
4934 system. First, create a new bucket in the cloud. This bucket is the
4935 file system storage area. I picked a bucket name reflecting the
4936 machine that was going to store data there, but any name will do.
4937 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
4938 the API login and password, and a locally created password. Store it
4939 all in ~root/.s3ql/authinfo2 like this:
4940
4941 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4942 [s3c]
4943 storage-url: s3c://s.greenqloud.com:443/bucket-name
4944 backend-login: API-login
4945 backend-password: API-password
4946 fs-passphrase: local-password
4947 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4948
4949 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
4950 but any sensible way to create a fairly random password should do it.
4951 Armed with these details, it is now time to run mkfs, entering the API
4952 details and password to create it:&lt;/p&gt;
4953
4954 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4955 # mkdir -m 700 /var/lib/s3ql-cache
4956 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4957 --ssl s3c://s.greenqloud.com:443/bucket-name
4958 Enter backend login:
4959 Enter backend password:
4960 Before using S3QL, make sure to read the user&#39;s guide, especially
4961 the &#39;Important Rules to Avoid Loosing Data&#39; section.
4962 Enter encryption password:
4963 Confirm encryption password:
4964 Generating random encryption key...
4965 Creating metadata tables...
4966 Dumping metadata...
4967 ..objects..
4968 ..blocks..
4969 ..inodes..
4970 ..inode_blocks..
4971 ..symlink_targets..
4972 ..names..
4973 ..contents..
4974 ..ext_attributes..
4975 Compressing and uploading metadata...
4976 Wrote 0.00 MB of compressed metadata.
4977 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4978
4979 &lt;p&gt;The next step is mounting the file system to make the storage available.
4980
4981 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4982 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4983 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4984 Using 4 upload threads.
4985 Downloading and decompressing metadata...
4986 Reading metadata...
4987 ..objects..
4988 ..blocks..
4989 ..inodes..
4990 ..inode_blocks..
4991 ..symlink_targets..
4992 ..names..
4993 ..contents..
4994 ..ext_attributes..
4995 Mounting filesystem...
4996 # df -h /s3ql
4997 Filesystem Size Used Avail Use% Mounted on
4998 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
4999 #
5000 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5001
5002 &lt;p&gt;The file system is now ready for use. I use rsync to store my
5003 backups in it, and as the metadata used by rsync is downloaded at
5004 mount time, no network traffic (and storage cost) is triggered by
5005 running rsync. To unmount, one should not use the normal umount
5006 command, as this will not flush the cache to the cloud storage, but
5007 instead running the umount.s3ql command like this:
5008
5009 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5010 # umount.s3ql /s3ql
5011 #
5012 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5013
5014 &lt;p&gt;There is a fsck command available to check the file system and
5015 correct any problems detected. This can be used if the local server
5016 crashes while the file system is mounted, to reset the &quot;already
5017 mounted&quot; flag. This is what it look like when processing a working
5018 file system:&lt;/p&gt;
5019
5020 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5021 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
5022 Using cached metadata.
5023 File system seems clean, checking anyway.
5024 Checking DB integrity...
5025 Creating temporary extra indices...
5026 Checking lost+found...
5027 Checking cached objects...
5028 Checking names (refcounts)...
5029 Checking contents (names)...
5030 Checking contents (inodes)...
5031 Checking contents (parent inodes)...
5032 Checking objects (reference counts)...
5033 Checking objects (backend)...
5034 ..processed 5000 objects so far..
5035 ..processed 10000 objects so far..
5036 ..processed 15000 objects so far..
5037 Checking objects (sizes)...
5038 Checking blocks (referenced objects)...
5039 Checking blocks (refcounts)...
5040 Checking inode-block mapping (blocks)...
5041 Checking inode-block mapping (inodes)...
5042 Checking inodes (refcounts)...
5043 Checking inodes (sizes)...
5044 Checking extended attributes (names)...
5045 Checking extended attributes (inodes)...
5046 Checking symlinks (inodes)...
5047 Checking directory reachability...
5048 Checking unix conventions...
5049 Checking referential integrity...
5050 Dropping temporary indices...
5051 Backing up old metadata...
5052 Dumping metadata...
5053 ..objects..
5054 ..blocks..
5055 ..inodes..
5056 ..inode_blocks..
5057 ..symlink_targets..
5058 ..names..
5059 ..contents..
5060 ..ext_attributes..
5061 Compressing and uploading metadata...
5062 Wrote 0.89 MB of compressed metadata.
5063 #
5064 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5065
5066 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
5067 quick, about the same speed as local file access. Uploading large
5068 amount of data is to me limited by the bandwidth out of and into my
5069 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
5070 which is very close to my upload speed, and downloading the same
5071 Debian installation ISO gave me 610 kiB/s, close to my download speed.
5072 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
5073 network, not the file system code. I do not know what a good cache
5074 size would be, but suspect that the cache should e larger than your
5075 working set.&lt;/p&gt;
5076
5077 &lt;p&gt;I mentioned that only one machine can mount the file system at the
5078 time. If another machine try, it is told that the file system is
5079 busy:&lt;/p&gt;
5080
5081 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5082 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5083 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5084 Using 8 upload threads.
5085 Backend reports that fs is still mounted elsewhere, aborting.
5086 #
5087 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5088
5089 &lt;p&gt;The file content is uploaded when the cache is full, while the
5090 metadata is uploaded once every 24 hour by default. To ensure the
5091 file system content is flushed to the cloud, one can either umount the
5092 file system, or ask S3QL to flush the cache and metadata using
5093 s3qlctrl:
5094
5095 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5096 # s3qlctrl upload-meta /s3ql
5097 # s3qlctrl flushcache /s3ql
5098 #
5099 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5100
5101 &lt;p&gt;If you are curious about how much space your data uses in the
5102 cloud, and how much compression and deduplication cut down on the
5103 storage usage, you can use s3qlstat on the mounted file system to get
5104 a report:&lt;/p&gt;
5105
5106 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5107 # s3qlstat /s3ql
5108 Directory entries: 9141
5109 Inodes: 9143
5110 Data blocks: 8851
5111 Total data size: 22049.38 MB
5112 After de-duplication: 21955.46 MB (99.57% of total)
5113 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
5114 Database size: 2.39 MB (uncompressed)
5115 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5116 #
5117 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5118
5119 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
5120 storage. I did not try to locate them all, but am aware of at least
5121 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
5122 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
5123 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
5124 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
5125 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
5126 accept payment in Bitcoin. Pick one that suit your need. Some of
5127 them provide several GiB of free storage, but the prize models are
5128 quite different and you will have to figure out what suits you
5129 best.&lt;/p&gt;
5130
5131 &lt;p&gt;While researching this blog post, I had a look at research papers
5132 and posters discussing the S3QL file system. There are several, which
5133 told me that the file system is getting a critical check by the
5134 science community and increased my confidence in using it. One nice
5135 poster is titled
5136 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
5137 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5138 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
5139 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5140 and Pamela Smith. Please have a look.&lt;/p&gt;
5141
5142 &lt;p&gt;Given my problems with different file systems earlier, I decided to
5143 check out the mounted S3QL file system to see if it would be usable as
5144 a home directory (in other word, that it provided POSIX semantics when
5145 it come to locking and umask handling etc). Running
5146 &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
5147 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
5148 no error was found. So the file system can be used for home
5149 directories, if one chooses to do so.&lt;/p&gt;
5150
5151 &lt;p&gt;If you do not want a locally file system, and want something that
5152 work without the Linux fuse file system, I would like to mention the
5153 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
5154 provide locally encrypted backup using a command line client. It have
5155 a nicer access control system, where one can split out read and write
5156 access, allowing some systems to write to the backup and others to
5157 only read from it.&lt;/p&gt;
5158
5159 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5160 activities, please send Bitcoin donations to my address
5161 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5162 </description>
5163 </item>
5164
5165 <item>
5166 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
5167 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
5168 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
5169 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
5170 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5171 project&lt;/a&gt; is working on providing the software and hardware for
5172 making it easy for non-technical people to host their data and
5173 communication at home, and being able to communicate with their
5174 friends and family encrypted and away from prying eyes. It has been
5175 going on for a while, and is slowly progressing towards a new test
5176 release (0.2).&lt;/p&gt;
5177
5178 &lt;p&gt;And what day could be better than the Pi day to announce that the
5179 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
5180 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5181 system), and can also be installed using a Debian installer preseed
5182 file. The Debian based Freedombox is now based on Debian Jessie,
5183 where most of the needed packages used are already present. Only one,
5184 the freedombox-setup package, is missing. To try to build your own
5185 boot image to test the current status, fetch the freedom-maker scripts
5186 and build using
5187 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
5188 with a user with sudo access to become root:
5189
5190 &lt;pre&gt;
5191 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5192 freedom-maker
5193 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5194 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5195 u-boot-tools
5196 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5197 &lt;/pre&gt;
5198
5199 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5200 devices. See the README for more details on the build. If you do not
5201 want all three images, trim the make line. But note that thanks to &lt;a
5202 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
5203 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
5204 kpartx call.&lt;/p&gt;
5205
5206 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5207 method, boot a Debian Wheezy ISO and use this boot argument to load
5208 the preseed values:&lt;/p&gt;
5209
5210 &lt;pre&gt;
5211 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;
5212 &lt;/pre&gt;
5213
5214 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
5215 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
5216 currently hang while setting up APT sources. Killing the
5217 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
5218 installation will get the installation going. This affect all
5219 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
5220
5221 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5222 us get the new release published. :) Please join us on
5223 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5224 irc.debian.org)&lt;/a&gt; and
5225 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5226 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5227 </description>
5228 </item>
5229
5230 <item>
5231 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
5232 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
5233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
5234 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
5235 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
5236 innetgr tools, because I needed them in
5237 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
5238 ng-utils, and it has served me well. I placed the project under the
5239 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
5240 repository. But many years ago, the CVS repository was dropped (lost,
5241 not migrated to new hardware, not sure), and the project have lacked a
5242 proper home since then.&lt;/p&gt;
5243
5244 &lt;p&gt;Last summer, I had a look at the package and made a new release
5245 fixing a irritating crash bug, but was unable to store the changes in
5246 a proper source control system. I applied for a project on
5247 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
5248 to follow up on it. Until today. :)&lt;/p&gt;
5249
5250 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
5251 now have a new home, and a git repository with the highlight of the
5252 history of the project. I published all release tarballs and imported
5253 them into the git repository. As the project is really stable and not
5254 expected to gain new features any time soon, I decided to make a new
5255 release and call it 1.0. Visit the new project home on
5256 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
5257 if you want to check it out. The new version is also uploaded into
5258 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
5259 </description>
5260 </item>
5261
5262 <item>
5263 <title>Testing sysvinit from experimental in Debian Hurd</title>
5264 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
5265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
5266 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
5267 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
5268 their changes into sysvinit, to allow them to use the normal sysvinit
5269 boot system instead of their old one. This follow up on the
5270 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
5271 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
5272 get Debian on Hurd working more like Debian on Linux. To get started,
5273 I downloaded a prebuilt hard disk image from
5274 &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;,
5275 and started it using virt-manager.&lt;/p&gt;
5276
5277 &lt;p&gt;The first think I had to do after logging in (root without any
5278 password) was to get the network operational. I followed
5279 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5280 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5281 commands as root to get the machine to accept a IP address from the
5282 kvm internal DHCP server:&lt;/p&gt;
5283
5284 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5285 settrans -fgap /dev/netdde /hurd/netdde
5286 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5287 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5288 dhclient /dev/eth0
5289 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5290
5291 &lt;p&gt;After this, the machine had internet connectivity, and I could
5292 upgrade it and install the sysvinit packages from experimental and
5293 enable it as the default boot system in Hurd.&lt;/p&gt;
5294
5295 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5296 running on the machine it for ssh login to work a password need to be
5297 set. Also, note that a bug somewhere in openssh on Hurd block
5298 compression from working. Remember to turn that off on the client
5299 side.&lt;/p&gt;
5300
5301 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5302 stuff:&lt;/p&gt;
5303
5304 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5305 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5306 deb http://http.debian.net/debian/ experimental main
5307 EOF
5308 apt-get update
5309 apt-get dist-upgrade
5310 apt-get install -t experimental initscripts sysv-rc sysvinit \
5311 sysvinit-core sysvinit-utils
5312 update-alternatives --config runsystem
5313 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5314
5315 &lt;p&gt;To reboot after switching boot system, you have to use
5316 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5317 yet a sysvinit process able to receive the signals from the normal
5318 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5319 upgrading every package and rebooting, the network come up with DHCP
5320 after boot as it should, and the settrans/pkill hack mentioned at the
5321 start is no longer needed. But for some strange reason, there are no
5322 longer any login prompt in the virtual console, so I logged in using
5323 ssh instead.
5324
5325 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5326 fail some times. No idea what the cause is, but hope the Hurd porters
5327 figure it out. At least Justus said on IRC (#debian-hurd on
5328 irc.debian.org) that they are aware of the problem. A way to reduce
5329 the impact is to upgrade to the Hurd packages built by Justus by
5330 adding this repository to the machine:&lt;/p&gt;
5331
5332 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5333 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5334 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5335 EOF
5336 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5337
5338 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5339 http://ftp.debian-ports.org/debian, because some of the packages in
5340 unstable do not yet include the required patches that are lingering in
5341 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5342
5343 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5344 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5345 i emacs - GNU Emacs editor (metapackage)
5346 i gdb - GNU Debugger
5347 i hurd-recommended - Miscellaneous translators
5348 i isc-dhcp-client - ISC DHCP client
5349 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5350 i libc-bin - Embedded GNU C Library: Binaries
5351 i libc-dev-bin - Embedded GNU C Library: Development binaries
5352 i libc0.3 - Embedded GNU C Library: Shared libraries
5353 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5354 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5355 i multiarch-support - Transitional package to ensure multiarch compatibilit
5356 i A x11-common - X Window System (X.Org) infrastructure
5357 i xorg - X.Org X Window System
5358 i A xserver-xorg - X.Org X server
5359 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5360 #
5361 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5362
5363 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5364 X.org did not work out of the box and I never took the time to follow
5365 the porters instructions to fix it. This time I was interested in the
5366 command line stuff.&lt;p&gt;
5367 </description>
5368 </item>
5369
5370 <item>
5371 <title>New chrpath release 0.16</title>
5372 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5374 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5375 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5376 find problems in C, C++ and Java code using static source code
5377 analysis. It can detect a lot of different problems, and is very
5378 useful to find memory and locking bugs in the error handling part of
5379 the source. The company behind it provide
5380 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5381 a community service&lt;/a&gt;, and many hundred free software projects are
5382 already checked. A few days ago I decided to have a closer look at
5383 the Coverity system, and discovered that the
5384 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5385 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5386 projects I am involved with was already registered. But these are
5387 fairly big, and I would also like to have a small and easy project to
5388 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5389 checking of the chrpath project&lt;/a&gt;. It was
5390 added to the checker and discovered seven potential defects. Six of
5391 these were real, mostly resource &quot;leak&quot; when the program detected an
5392 error. Nothing serious, as the resources would be released a fraction
5393 of a second later when the program exited because of the error, but it
5394 is nice to do it right in case the source of the program some time in
5395 the future end up in a library. Having fixed all defects and added
5396 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5397 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5398 publish a new release. These are the release notes:&lt;/p&gt;
5399
5400 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5401
5402 &lt;ul&gt;
5403
5404 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5405 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5406 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5407
5408 &lt;/ul&gt;
5409
5410 &lt;p&gt;You can
5411 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5412 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5413 project if something is wrong with the new release. The test suite
5414 did not discover any old errors, so if you find a new one, please also
5415 include a test suite check.&lt;/p&gt;
5416 </description>
5417 </item>
5418
5419 <item>
5420 <title>New chrpath release 0.15</title>
5421 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5423 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5424 <description>&lt;p&gt;After many years break from the package and a vain hope that
5425 development would be continued by someone else, I finally pulled my
5426 acts together this morning and wrapped up a new release of chrpath,
5427 the command line tool to modify the rpath and runpath of already
5428 compiled ELF programs. The update was triggered by the persistence of
5429 Isha Vishnoi at IBM, which needed a new config.guess file to get
5430 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5431 is working on. I checked the
5432 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5433 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5434 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5435 packages for interesting patches (failed to find the source from
5436 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5437 These are the release notes:&lt;/p&gt;
5438
5439 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5440
5441 &lt;ul&gt;
5442
5443 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5444 with newer architectures. Thanks to isha vishnoi for the heads
5445 up.&lt;/li&gt;
5446
5447 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5448
5449 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5450 Matthias Klose.&lt;/li&gt;
5451
5452 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5453 Petr Machata found in Fedora.&lt;/li&gt;
5454
5455 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5456 .dynamic is a NULL terminated string. Based on patch found in
5457 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5458
5459 &lt;/ul&gt;
5460
5461 &lt;p&gt;You can
5462 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5463 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5464 project if something is wrong with the new release. The test suite
5465 did not discover any old errors, so if you find a new one, please also
5466 include a testsuite check.&lt;/p&gt;
5467 </description>
5468 </item>
5469
5470 <item>
5471 <title>Debian init.d boot script example for rsyslog</title>
5472 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5473 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5474 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5475 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5476 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5477 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5478 init.d scripts at all. Here is an example init.d script, ie a rewrite
5479 of /etc/init.d/rsyslog:&lt;/p&gt;
5480
5481 &lt;p&gt;&lt;pre&gt;
5482 #!/lib/init/init-d-script
5483 ### BEGIN INIT INFO
5484 # Provides: rsyslog
5485 # Required-Start: $remote_fs $time
5486 # Required-Stop: umountnfs $time
5487 # X-Stop-After: sendsigs
5488 # Default-Start: 2 3 4 5
5489 # Default-Stop: 0 1 6
5490 # Short-Description: enhanced syslogd
5491 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5492 # It is quite compatible to stock sysklogd and can be
5493 # used as a drop-in replacement.
5494 ### END INIT INFO
5495 DESC=&quot;enhanced syslogd&quot;
5496 DAEMON=/usr/sbin/rsyslogd
5497 &lt;/pre&gt;&lt;/p&gt;
5498
5499 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5500 script was 137 lines, and the above is just 15 lines, most of it meta
5501 info/comments.&lt;/p&gt;
5502
5503 &lt;p&gt;How to do this, you ask? Well, one create a new script
5504 /lib/init/init-d-script looking something like this:
5505
5506 &lt;p&gt;&lt;pre&gt;
5507 #!/bin/sh
5508
5509 # Define LSB log_* functions.
5510 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5511 # and status_of_proc is working.
5512 . /lib/lsb/init-functions
5513
5514 #
5515 # Function that starts the daemon/service
5516
5517 #
5518 do_start()
5519 {
5520 # Return
5521 # 0 if daemon has been started
5522 # 1 if daemon was already running
5523 # 2 if daemon could not be started
5524 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5525 || return 1
5526 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5527 $DAEMON_ARGS \
5528 || return 2
5529 # Add code here, if necessary, that waits for the process to be ready
5530 # to handle requests from services started subsequently which depend
5531 # on this one. As a last resort, sleep for some time.
5532 }
5533
5534 #
5535 # Function that stops the daemon/service
5536 #
5537 do_stop()
5538 {
5539 # Return
5540 # 0 if daemon has been stopped
5541 # 1 if daemon was already stopped
5542 # 2 if daemon could not be stopped
5543 # other if a failure occurred
5544 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5545 RETVAL=&quot;$?&quot;
5546 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5547 # Wait for children to finish too if this is a daemon that forks
5548 # and if the daemon is only ever run from this initscript.
5549 # If the above conditions are not satisfied then add some other code
5550 # that waits for the process to drop all resources that could be
5551 # needed by services started subsequently. A last resort is to
5552 # sleep for some time.
5553 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5554 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5555 # Many daemons don&#39;t delete their pidfiles when they exit.
5556 rm -f $PIDFILE
5557 return &quot;$RETVAL&quot;
5558 }
5559
5560 #
5561 # Function that sends a SIGHUP to the daemon/service
5562 #
5563 do_reload() {
5564 #
5565 # If the daemon can reload its configuration without
5566 # restarting (for example, when it is sent a SIGHUP),
5567 # then implement that here.
5568 #
5569 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5570 return 0
5571 }
5572
5573 SCRIPTNAME=$1
5574 scriptbasename=&quot;$(basename $1)&quot;
5575 echo &quot;SN: $scriptbasename&quot;
5576 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5577 script=&quot;$1&quot;
5578 shift
5579 . $script
5580 else
5581 exit 0
5582 fi
5583
5584 NAME=$(basename $DAEMON)
5585 PIDFILE=/var/run/$NAME.pid
5586
5587 # Exit if the package is not installed
5588 #[ -x &quot;$DAEMON&quot; ] || exit 0
5589
5590 # Read configuration variable file if it is present
5591 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5592
5593 # Load the VERBOSE setting and other rcS variables
5594 . /lib/init/vars.sh
5595
5596 case &quot;$1&quot; in
5597 start)
5598 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5599 do_start
5600 case &quot;$?&quot; in
5601 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5602 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5603 esac
5604 ;;
5605 stop)
5606 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5607 do_stop
5608 case &quot;$?&quot; in
5609 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5610 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5611 esac
5612 ;;
5613 status)
5614 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5615 ;;
5616 #reload|force-reload)
5617 #
5618 # If do_reload() is not implemented then leave this commented out
5619 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5620 #
5621 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5622 #do_reload
5623 #log_end_msg $?
5624 #;;
5625 restart|force-reload)
5626 #
5627 # If the &quot;reload&quot; option is implemented then remove the
5628 # &#39;force-reload&#39; alias
5629 #
5630 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5631 do_stop
5632 case &quot;$?&quot; in
5633 0|1)
5634 do_start
5635 case &quot;$?&quot; in
5636 0) log_end_msg 0 ;;
5637 1) log_end_msg 1 ;; # Old process is still running
5638 *) log_end_msg 1 ;; # Failed to start
5639 esac
5640 ;;
5641 *)
5642 # Failed to stop
5643 log_end_msg 1
5644 ;;
5645 esac
5646 ;;
5647 *)
5648 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5649 exit 3
5650 ;;
5651 esac
5652
5653 :
5654 &lt;/pre&gt;&lt;/p&gt;
5655
5656 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5657 lot. I did not really polish the approach, so it might not always
5658 work out of the box, but you get the idea. I did not try very hard to
5659 optimize it nor make it more robust either.&lt;/p&gt;
5660
5661 &lt;p&gt;A better argument for switching init system in Debian than reducing
5662 the size of init scripts (which is a good thing to do anyway), is to
5663 get boot system that is able to handle the kernel events sensibly and
5664 robustly, and do not depend on the boot to run sequentially. The boot
5665 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5666 </description>
5667 </item>
5668
5669 <item>
5670 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5671 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5672 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5673 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5674 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5675 remote display access is the preferred solution with oVirt and RedHat
5676 Enterprise Virtualization, and I was sad to discover the other day
5677 that the browser plugin needed to use these systems seamlessly was
5678 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5679 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5680 2013-04-01, so I decided to wrap up a package based on the great work
5681 from Cajus Pollmeier and put it in a collab-maint maintained git
5682 repository to get a package I could use. I would very much like
5683 others to help me maintain the package (or just take over, I do not
5684 mind), but as no-one had volunteered so far, I just uploaded it to
5685 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5686
5687 &lt;p&gt;The source is now available from
5688 &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;
5689 </description>
5690 </item>
5691
5692 <item>
5693 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5694 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5696 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5697 <description>&lt;p&gt;The
5698 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5699 program is a a very nice system to create virtual machine images. It
5700 create a image file, add a partition table, mount it and run
5701 debootstrap in the mounted directory to create a Debian system on a
5702 stick. Yesterday, I decided to try to teach it how to make images for
5703 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5704 of a plan to simplify the build system for
5705 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5706 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5707 the virtualbox images, but its current build system made multistrap
5708 based system for Dreamplug images, and it is lacking support for
5709 Raspberry Pi.&lt;/p&gt;
5710
5711 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5712 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5713 code and adjusted it to be able to build armel images on my amd64
5714 Debian laptop. I ended up giving vmdebootstrap five new options,
5715 allowing me to replicate the image creation process I use to make
5716 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5717 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5718 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5719 call debootstrap with --foreign and to copy the handler into the
5720 generated chroot before running the second stage. This allow
5721 vmdebootstrap to create armel images on an amd64 host. Next I added
5722 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5723 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5724 given file system type, allowing me to create an image with a vfat
5725 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5726 variant&lt;/tt&gt; option to allow me to create smaller images without the
5727 Debian base system packages installed. Finally, I added an option
5728 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5729 as a boot loader. It is not needed on the Raspberry Pi and probably
5730 most other non-x86 architectures. The changes were accepted by the
5731 upstream author of vmdebootstrap yesterday and today, and is now
5732 available from
5733 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5734 upstream project page&lt;/a&gt;.&lt;/p&gt;
5735
5736 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5737 create a small script (the customize script) to add the non-free
5738 binary blob needed to boot the Raspberry Pi and the APT source
5739 list:&lt;/p&gt;
5740
5741 &lt;p&gt;&lt;pre&gt;
5742 #!/bin/sh
5743 set -e # Exit on first error
5744 rootdir=&quot;$1&quot;
5745 cd &quot;$rootdir&quot;
5746 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5747 deb http://http.debian.net/debian/ jessie main contrib non-free
5748 EOF
5749 # Install non-free binary blob needed to boot Raspberry Pi. This
5750 # install a kernel somewhere too.
5751 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5752 -O $rootdir/usr/bin/rpi-update
5753 chmod a+x $rootdir/usr/bin/rpi-update
5754 mkdir -p $rootdir/lib/modules
5755 touch $rootdir/boot/start.elf
5756 chroot $rootdir rpi-update
5757 &lt;/pre&gt;&lt;/p&gt;
5758
5759 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5760 to build the image:&lt;/p&gt;
5761
5762 &lt;pre&gt;
5763 sudo ./vmdebootstrap \
5764 --variant minbase \
5765 --arch armel \
5766 --distribution jessie \
5767 --mirror http://http.debian.net/debian \
5768 --image test.img \
5769 --size 600M \
5770 --bootsize 64M \
5771 --boottype vfat \
5772 --log-level debug \
5773 --verbose \
5774 --no-kernel \
5775 --no-extlinux \
5776 --root-password raspberry \
5777 --hostname raspberrypi \
5778 --foreign /usr/bin/qemu-arm-static \
5779 --customize `pwd`/customize \
5780 --package netbase \
5781 --package git-core \
5782 --package binutils \
5783 --package ca-certificates \
5784 --package wget \
5785 --package kmod
5786 &lt;/pre&gt;&lt;/p&gt;
5787
5788 &lt;p&gt;The list of packages being installed are the ones needed by
5789 rpi-update to make the image bootable on the Raspberry Pi, with the
5790 exception of netbase, which is needed by debootstrap to find
5791 /etc/hosts with the minbase variant. I really wish there was a way to
5792 set up an Raspberry Pi using only packages in the Debian archive, but
5793 that is not possible as far as I know, because it boots from the GPU
5794 using a non-free binary blob.&lt;/p&gt;
5795
5796 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
5797 probably a few others installed. I have not checked the complete
5798 build dependency list.&lt;/p&gt;
5799
5800 &lt;p&gt;The resulting image will not use the hardware floating point unit
5801 on the Raspberry PI, because the armel architecture in Debian is not
5802 optimized for that use. So the images created will be a bit slower
5803 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
5804 </description>
5805 </item>
5806
5807 <item>
5808 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
5809 <link>http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</link>
5810 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</guid>
5811 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
5812 <description>&lt;p&gt;The last few days I came across a few good causes that should get
5813 wider attention. I recommend signing and donating to each one of
5814 these. :)&lt;/p&gt;
5815
5816 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
5817 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
5818 Women program which is a Google Summer of Code like initiative to get
5819 more women involved in free software. One debian sponsor has offered
5820 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
5821 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
5822 hope you will to. :)&lt;/p&gt;
5823
5824 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
5825 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
5826 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
5827 take place these days, and their need to fund the work. I&#39;ve already
5828 donated. Are you next?&lt;/p&gt;
5829
5830 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
5831 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5832 statement under the heading
5833 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
5834 Access&lt;/a&gt; for those of us asking for more focus on open access in the
5835 Norwegian government. So far 499 signatures. I hope you will sign it
5836 too.&lt;/p&gt;
5837 </description>
5838 </item>
5839
5840 <item>
5841 <title>Videos about the Freedombox project - for inspiration and learning</title>
5842 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
5843 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
5844 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
5845 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
5846 project&lt;/a&gt; have been going on for a while, and have presented the
5847 vision, ideas and solution several places. Here is a little
5848 collection of videos of talks and presentation of the project.&lt;/p&gt;
5849
5850 &lt;ul&gt;
5851
5852 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
5853 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
5854
5855 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
5856 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5857
5858 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
5859 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5860 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
5861 (Youtube)&lt;/li&gt;
5862
5863 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
5864 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
5865
5866 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
5867 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5868
5869 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
5870 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5871 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
5872
5873 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
5874 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
5875 (Youtube)&lt;/li&gt;
5876
5877 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
5878 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
5879
5880 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
5881 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
5882
5883 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
5884 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5885 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
5886
5887 &lt;/ul&gt;
5888
5889 &lt;p&gt;A larger list is available from
5890 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
5891 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
5892
5893 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
5894 Jessie is coming along quite well, and soon both Owncloud and using
5895 Tor should be available for testers of the Freedombox solution. :) In
5896 a few weeks I hope everything needed to test it is included in Debian.
5897 The withsqlite package is already in Debian, and the plinth package is
5898 pending in NEW. The third and vital part of that puzzle is the
5899 metapackage/setup framework, which is still pending an upload. Join
5900 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
5901 (#freedombox on irc.debian.org)&lt;/a&gt; and
5902 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5903 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5904 </description>
5905 </item>
5906
5907 <item>
5908 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
5909 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
5910 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
5911 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
5912 <description>&lt;p&gt;I was introduced to the
5913 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
5914 in 2010, when Eben Moglen presented his vision about serving the need
5915 of non-technical people to keep their personal information private and
5916 within the legal protection of their own homes. The idea is to give
5917 people back the power over their network and machines, and return
5918 Internet back to its intended peer-to-peer architecture. Instead of
5919 depending on a central service, the Freedombox will give everyone
5920 control over their own basic infrastructure.&lt;/p&gt;
5921
5922 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
5923 taken priority. But this summers nasty news about the misuse of trust
5924 and privilege exercised by the &quot;western&quot; intelligence gathering
5925 communities increased my eagerness to contribute to a point where I
5926 actually started working on the project a while back.&lt;/p&gt;
5927
5928 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
5929 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
5930 create a simple and cheap Debian based appliance that anyone can hook
5931 up in their home and get access to secure and private services and
5932 communication. The initial deployment platform have been the
5933 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
5934 which is a piece of hardware I do not own. So to be able to test what
5935 the current Freedombox setup look like, I had to come up with a way to install
5936 it on some hardware I do have access to. I have rewritten the
5937 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
5938 image build framework to use .deb packages instead of only copying
5939 setup into the boot images, and thanks to this rewrite I am able to
5940 set up any machine supported by Debian Wheezy as a Freedombox, using
5941 the previously mentioned deb (and a few support debs for packages
5942 missing in Debian).&lt;/p&gt;
5943
5944 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
5945 scripts
5946 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
5947 and a administrative web interface
5948 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
5949 withsqlite), as well as a privacy enhancing proxy based on
5950 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
5951 (freedombox-privoxy). There is also a web/javascript based XMPP
5952 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
5953 trying (unsuccessfully so far) to talk to the XMPP server
5954 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
5955 web interface is pluggable, and the goal is to use it to enable OpenID
5956 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5957 this is really working yet, see
5958 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
5959 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
5960 on github at the moment. The HTTP proxy is operational out of the
5961 box, and the admin web interface can be used to add/remove plinth
5962 users. I&#39;ve not been able to do anything else with it so far, but
5963 know there are several branches spread around github and other places
5964 with lots of half baked features.&lt;/p&gt;
5965
5966 &lt;p&gt;Anyway, if you want to have a look at the current state, the
5967 following recipes should work to give you a test machine to poke
5968 at.&lt;/p&gt;
5969
5970 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
5971
5972 &lt;ol&gt;
5973
5974 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
5975 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
5976 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
5977 to the Debian installer:&lt;p&gt;
5978 &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;
5979
5980 &lt;li&gt;Answer the few language/region/password questions and pick disk to
5981 install on.&lt;/li&gt;
5982
5983 &lt;li&gt;When the installation is finished and the machine have rebooted a
5984 few times, your Freedombox is ready for testing.&lt;/li&gt;
5985
5986 &lt;/ol&gt;
5987
5988 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
5989
5990 &lt;ol&gt;
5991
5992 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
5993 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
5994 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
5995 &lt;pre&gt;
5996 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
5997 &lt;/pre&gt;&lt;/li&gt;
5998 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
5999 &lt;pre&gt;
6000 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6001 apt-key add -
6002 apt-get update
6003 apt-get install freedombox-setup
6004 /usr/lib/freedombox/setup
6005 &lt;/pre&gt;&lt;/li&gt;
6006 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
6007
6008 &lt;/ol&gt;
6009
6010 &lt;p&gt;You can test it on other architectures too, but because the
6011 freedombox-privoxy package is binary, it will only work as intended on
6012 the architectures where I have had time to build the binary and put it
6013 in my APT repository. But do not let this stop you. It is only a
6014 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
6015
6016 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
6017 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
6018 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
6019 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
6020
6021 &lt;p&gt;Please let me know if this works for you, or if you have any
6022 problems. We gather on the IRC channel
6023 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
6024 irc.debian.org and the
6025 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
6026 mailing list&lt;/a&gt;.&lt;/p&gt;
6027
6028 &lt;p&gt;Once you get your freedombox operational, you can visit
6029 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
6030 welcome screen (dead end - do not be surprised if you are unable to
6031 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
6032 to look at the rest of plinth. The default user is &#39;admin&#39; and the
6033 default password is &#39;secret&#39;.&lt;/p&gt;
6034 </description>
6035 </item>
6036
6037 <item>
6038 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
6039 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
6040 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
6041 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
6042 <description>&lt;p&gt;Earlier, I reported about
6043 &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
6044 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
6045 told by IBM that the original disk should be thrown away. And as
6046 there no longer was a problem if I bricked the firmware, I decided
6047 today to try to install Intel firmware to replace the Lenovo firmware
6048 currently on the disk.&lt;/p&gt;
6049
6050 &lt;p&gt;I searched the Intel site for firmware, and found
6051 &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;
6052 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6053 according to the site should contain the latest firmware for SSD
6054 disks. I inserted the broken disk in one of my spare laptops and
6055 booted the ISO from a USB stick. The disk was recognized, but the
6056 program claimed the newest firmware already were installed and refused
6057 to insert any Intel firmware. So no change, and the disk is still
6058 unable to handle write load. :( I guess the only way to get them
6059 working would be if Lenovo releases new firmware. No idea how likely
6060 that is. Anyway, just blogging about this test for completeness. I
6061 got a working Samsung disk, and see no point in spending more time on
6062 the broken disks.&lt;/p&gt;
6063 </description>
6064 </item>
6065
6066 <item>
6067 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
6068 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
6069 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
6070 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
6071 <description>&lt;p&gt;Today I switched to
6072 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
6073 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
6074 my new Thinkpad X230, which was delivered with an
6075 &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
6076 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
6077 sustained writes. My hardware supplier have been very forthcoming in
6078 trying to find a solution, and after first trying with another
6079 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
6080 disk instead to fix it once and for all. The Samsung disk survived
6081 the installation of Debian with encrypted disks (filling the disk with
6082 random data during installation killed the first two), and I thus
6083 decided to trust it with my data. I have installed it as a Debian Edu
6084 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6085 server at home using Kerberos and LDAP, and will use it as my work
6086 station from now on.&lt;/p&gt;
6087
6088 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
6089 Debian Wheezy default installation need to be tuned a bit to increase
6090 performance and increase life time of the disk. The Linux kernel and
6091 user space applications do not yet adjust automatically to such
6092 environment. To make it easier for my self, I created a draft Debian
6093 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
6094 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
6095 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
6096 is set up to adjust the setup of the machine by just installing the
6097 package. If there is any non-SSD disk in the machine, the package
6098 will refuse to install, as I did not try to write any logic to sort
6099 file systems in SSD and non-SSD file systems.&lt;/p&gt;
6100
6101 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
6102 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6103 where I set up the machine with one large encrypted partition (in
6104 addition to /boot), put LVM on top of this and set up partitions on
6105 top of this again. See the README file in the package source for the
6106 references I used to pick the settings. At the moment these
6107 parameters are tuned:&lt;/p&gt;
6108
6109 &lt;ul&gt;
6110
6111 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
6112 (adding discard to /etc/crypttab)&lt;/li&gt;
6113
6114 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
6115 this case a cryptsetup partition) by changing issue_discards from
6116 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
6117
6118 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
6119 systems.&lt;/li&gt;
6120
6121 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
6122 /etc/fstab.&lt;/li&gt;
6123
6124 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
6125
6126 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
6127 cron.daily).&lt;/li&gt;
6128
6129 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
6130 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
6131
6132 &lt;/ul&gt;
6133
6134 &lt;p&gt;During installation, I cancelled the part where the installer fill
6135 the disk with random data, as this would kill the SSD performance for
6136 little gain. My goal with the encrypted file system is to ensure
6137 those stealing my laptop end up with a brick and not a working
6138 computer. I have no hope in keeping the really resourceful people
6139 from getting the data on the disk (see
6140 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
6141 Thus I concluded that adding the discard option to crypttab is the
6142 right thing to do.&lt;/p&gt;
6143
6144 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
6145 it for SSD, but others recommended deadline and a benchmark I found
6146 indicated that deadline might be better for interactive use.&lt;/p&gt;
6147
6148 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
6149 and ext4, but read that it would give a performance hit ever time a
6150 file is removed, and thought it best to that that slowdown once a day
6151 instead of during my work.&lt;/p&gt;
6152
6153 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6154 this is already done by Debian Edu.&lt;/p&gt;
6155
6156 &lt;p&gt;I have not yet started on the user space tuning. I expect
6157 iceweasel need some tuning, and perhaps other applications too, but
6158 have not yet had time to investigate those parts.&lt;/p&gt;
6159
6160 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
6161 there.&lt;/p&gt;
6162
6163 &lt;p&gt;As for the answer to the question in the title of this blog post,
6164 as far as I know, the only solution I know about is to replace the
6165 disk. It might be possible to flash it with Intel firmware instead of
6166 the Lenovo firmware. But I have not tried and did not want to do so
6167 without approval from Lenovo as I wanted to keep the warranty on the
6168 disk until a solution was found and they wanted the broken disks
6169 back.&lt;/p&gt;
6170 </description>
6171 </item>
6172
6173 <item>
6174 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
6175 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
6176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</guid>
6177 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
6178 <description>&lt;p&gt;A few days ago, I wrote about
6179 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
6180 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
6181 was dying during installation because it is unable to cope with
6182 sustained write. My supplier is in contact with
6183 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
6184 replacement disk to try to fix the problem. They decided to send an
6185 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
6186
6187 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
6188 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6189 same firmware version as the original. This time my hope raised
6190 slightly as the installation progressed, as the original disk used to
6191 die after 4-7% of the disk was written to, while this time it kept
6192 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
6193 died again and I was back on square one. I still do not have a new
6194 laptop with a disk I can trust. I can not live with a disk that might
6195 lock up when I download a new
6196 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
6197 other large files. I look forward to hearing from my supplier with
6198 the next proposal from Lenovo.&lt;/p&gt;
6199
6200 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
6201 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6202 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6203 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
6204 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6205 P/N 45N8295, P0C38732.&lt;/p&gt;
6206
6207 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
6208 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
6209 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6210 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
6211 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6212 P/N 45N8295, P0C38732.&lt;/p&gt;
6213
6214 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
6215 SA, date and WNPP values. Mentioning all the details here in case
6216 someone is able to use the information to find a way to identify the
6217 failing disk among working ones (if any such working disk actually
6218 exist).&lt;/p&gt;
6219 </description>
6220 </item>
6221
6222 <item>
6223 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
6224 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
6225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
6226 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
6227 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
6228 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6229 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
6230 member assosiation NUUG&lt;/a&gt; and
6231 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
6232 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
6233 Bitraf&lt;/a&gt;.&lt;/p&gt;
6234
6235 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
6236 welcome, and there is no fee to participate. There is on the other
6237 hand limited space, and only room for 30 people. Please put your name
6238 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
6239 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
6240 </description>
6241 </item>
6242
6243 <item>
6244 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
6245 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
6246 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
6247 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
6248 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
6249 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
6250 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
6251 time to spend on it, and it took a while to find a model I believe
6252 will do the job, but two days ago the replacement finally arrived. I
6253 ended up picking a
6254 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
6255 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6256 a roaming workstation, and it seemed to work flawlessly. But my
6257 second installation with encrypted disk was not as successful. More
6258 on that below.&lt;/p&gt;
6259
6260 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6261 important requirements (robust and with a good keyboard) are never
6262 listed in the feature list. But I did get good help from the search
6263 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6264 allowed me to limit the list of interesting laptops based on my other
6265 requirements. A bit surprising that SSD disk are not disks according
6266 to that search interface, so I had to drop specifying the number of
6267 disks from my search parameters. I also asked around among friends to
6268 get their impression on keyboards and robustness.&lt;/p&gt;
6269
6270 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
6271 X41. I am not quite convinced about the keyboard, as it is
6272 significantly wider than my old keyboard, and I have to stretch my
6273 hand a lot more to reach the edges. But the key response is fairly
6274 good and the individual key shape is fairly easy to handle, so I hope
6275 I will get used to it. My old X40 was starting to fail, and I really
6276 needed a new laptop now. :)&lt;/p&gt;
6277
6278 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6279 visit to the BIOS during boot it disable it.&lt;/p&gt;
6280
6281 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6282 lock up during load. And this happen when installing Debian Wheezy
6283 with encrypted disk, while the disk is being filled with random data.
6284 I also tested to install Ubuntu Raring, and it happen there too if I
6285 reenable the code to fill the disk with random data (it is disabled by
6286 default in Ubuntu). And the bug with is already known. It was
6287 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6288 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6289 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6290 kernel developers as
6291 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6292 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6293 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6294 Lenovo forums, both for
6295 &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
6296 2012-11-10&lt;/a&gt; and for
6297 &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
6298 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6299 reports state that the disk lock up during use if many writes are done
6300 on the disk, so it is much no use to work around the installation
6301 problem and end up with a computer that can lock up at any moment.
6302 There is even a
6303 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6304 available&lt;/a&gt; that will lock up the hard drive after running a few
6305 minutes by writing to a file.&lt;/p&gt;
6306
6307 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6308 contacting PCHELP Norway (request 01D1FDP) which handle support
6309 requests for Lenovo, his first suggestion was to upgrade the disk
6310 firmware. Unfortunately there is no newer firmware available from
6311 Lenovo, as my disk already have the most recent one (version LF1i). I
6312 hope to hear more from him today and hope the problem can be
6313 fixed. :)&lt;/p&gt;
6314 </description>
6315 </item>
6316
6317 <item>
6318 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6319 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6320 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6321 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6322 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6323 trusty old Thinkpad X41. Unfortunately I did not have much time to
6324 spend on it, but today the replacement finally arrived. I ended up
6325 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6326 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6327 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6328 this, it is installing what I hope will be a more final installation,
6329 with a encrypted hard drive to ensure any dope head stealing it end up
6330 with an expencive door stop.&lt;/p&gt;
6331
6332 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6333 important requirements (robust and with a good keyboard) are never
6334 listed in the feature list. But I did get good help from the search
6335 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6336 allowed me to limit the list of interesting laptops based on my other
6337 requirements. A bit surprising that SSD disk are not disks, so I had
6338 to drop number of disks from my search parameters.&lt;/p&gt;
6339
6340 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6341 wider than my old keyboard, and I have to stretch my hand a lot more
6342 to reach the edges. But the key response is fairly good and the
6343 individual key shape is fairly easy to handle, so I hope I will get
6344 used to it. My old X40 was starting to fail, and I really needed a
6345 new laptop now. :)&lt;/p&gt;
6346
6347 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6348 </description>
6349 </item>
6350
6351 <item>
6352 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6353 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6354 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6355 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6356 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6357 perfectly capable of, and I have to do it manually to get things
6358 working. One such task is to find out what firmware packages are
6359 needed to get the hardware on my computer working. Most often this
6360 affect the wifi card, but some times it even affect the RAID
6361 controller or the ethernet card. Today I pushed version 0.4 of the
6362 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6363 including a new script isenkram-autoinstall-firmware handling the
6364 process of asking all the loaded kernel modules what firmware files
6365 they want, find debian packages providing these files and install the
6366 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6367
6368 &lt;p&gt;&lt;pre&gt;
6369 # isenkram-autoinstall-firmware
6370 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6371 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6372 info: locating packages with the requested firmware files
6373 info: Updating APT sources after adding non-free APT source
6374 info: trying to install firmware-ipw2x00
6375 firmware-ipw2x00
6376 firmware-ipw2x00
6377 Preconfiguring packages ...
6378 Selecting previously deselected package firmware-ipw2x00.
6379 (Reading database ... 259727 files and directories currently installed.)
6380 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6381 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6382 #
6383 &lt;/pre&gt;&lt;/p&gt;
6384
6385 &lt;p&gt;When all the requested firmware is present, a simple message is
6386 printed instead:&lt;/p&gt;
6387
6388 &lt;p&gt;&lt;pre&gt;
6389 # isenkram-autoinstall-firmware
6390 info: did not find any firmware files requested by loaded kernel modules. exiting
6391 #
6392 &lt;/pre&gt;&lt;/p&gt;
6393
6394 &lt;p&gt;It could use some polish, but it is already working well and saving
6395 me some time when setting up new machines. :)&lt;/p&gt;
6396
6397 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6398 kernel modules, and look up each one of them using modinfo, to find
6399 the firmware files listed in the module meta-information. Next, it
6400 download the Contents file from a nearby APT mirror, and search for
6401 the firmware files in this file to locate the package with the
6402 requested firmware file. If the package is in the non-free section, a
6403 non-free APT source is added and the package is installed using
6404 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6405 machine.&lt;/p&gt;
6406
6407 &lt;p&gt;I hope someone find time to implement a more polished version of
6408 this script as part of the hw-detect debian-installer module, to
6409 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6410 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6411 firmware during a PXE install when the packages already are available
6412 from the nearby Debian mirror.&lt;/p&gt;
6413 </description>
6414 </item>
6415
6416 <item>
6417 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6418 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6420 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6421 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6422 the screen just turn black when Linux boot, either during installation
6423 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6424 last few years, but only recently understood the cause. I&#39;ve seen it
6425 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6426 The reason seem to be in the wiring of some laptops. The system to
6427 control the screen background light is inverted, so when Linux try to
6428 turn the brightness fully on, it end up turning it off instead. I do
6429 not know which Linux drivers are affected, but this post is about the
6430 i915 driver used by the
6431 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6432 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6433
6434 &lt;p&gt;The problem can be worked around two ways. Either by adding
6435 i915.invert_brightness=1 as a kernel option, or by adding a file in
6436 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6437 option when it load the i915 kernel module. On Debian and Ubuntu, it
6438 can be done by running these commands as root:&lt;/p&gt;
6439
6440 &lt;pre&gt;
6441 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6442 update-initramfs -u -k all
6443 &lt;/pre&gt;
6444
6445 &lt;p&gt;Since March 2012 there is
6446 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6447 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6448 hardware have this problem, and get the driver to invert the
6449 brightness setting automatically. To use it, one need to add a row in
6450 &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
6451 intel_quirks array&lt;/a&gt; in the driver source
6452 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6453 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6454 number (vendor number 8086 is assumed) and subdevice vendor and device
6455 number.&lt;/p&gt;
6456
6457 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6458 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6459
6460 &lt;p&gt;&lt;pre&gt;
6461 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6462 3rd Gen Core processor Graphics Controller [8086:0156] \
6463 (rev 09) (prog-if 00 [VGA controller])
6464 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6465 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6466 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6467 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6468 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6469 Latency: 0
6470 Interrupt: pin A routed to IRQ 42
6471 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6472 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6473 Region 4: I/O ports at 4000 [size=64]
6474 Expansion ROM at &lt;unassigned&gt; [disabled]
6475 Capabilities: &lt;access denied&gt;
6476 Kernel driver in use: i915
6477 &lt;/pre&gt;&lt;/p&gt;
6478
6479 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6480
6481 &lt;p&gt;&lt;pre&gt;
6482 struct intel_quirk intel_quirks[] = {
6483 ...
6484 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6485 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6486 ...
6487 }
6488 &lt;/pre&gt;&lt;/p&gt;
6489
6490 &lt;p&gt;According to the kernel module instructions (as seen using
6491 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6492 invert_brightness flag should be sent to the
6493 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6494 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6495 developers. But my email about the laptop sent 2013-06-03 have not
6496 yet shown up in
6497 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6498 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6499 emails from non-subscribers. Because of this, I sent my patch also to
6500 the Debian bug tracking system instead as
6501 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6502 sure the patch is not lost.&lt;/p&gt;
6503
6504 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6505 with this problem working properly with Linux. If you use Gnome, your
6506 worries should be over at this point. But if you use KDE, there is
6507 something in KDE ignoring the invert_brightness setting and turning on
6508 the screen during login. I&#39;ve reported it to Debian as
6509 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6510 have no idea yet how to figure out exactly what subsystem is doing
6511 this. Perhaps you can help? Perhaps you know what the Gnome
6512 developers did to handle this, and this can give a clue to the KDE
6513 developers? Or you know where in KDE the screen brightness is changed
6514 during login? If so, please update the BTS report (or get in touch if
6515 you do not know how to update BTS).&lt;/p&gt;
6516
6517 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6518 acpi_backlight=vendor, to disable ACPI backlight support completely,
6519 as the ACPI information on the machine is trash and it is better to
6520 leave it to the intel video driver to control the screen
6521 backlight.&lt;/p&gt;
6522 </description>
6523 </item>
6524
6525 <item>
6526 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6527 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</guid>
6529 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6530 <description>&lt;p&gt;Two days ago, I asked
6531 &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
6532 I could install Linux on a Packard Bell EasyNote LV computer
6533 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6534 with the obstacles put in the way of Linux users on a laptop with UEFI
6535 and Windows 8.&lt;/p&gt;
6536
6537 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6538 secure booting or fast boot. I suspect fast boot was the problem,
6539 causing the firmware to boot directly from HD without considering any
6540 key presses and alternative devices, but do not know UEFI settings
6541 enough to tell.&lt;/p&gt;
6542
6543 &lt;p&gt;There is no way to install Linux on the machine in question without
6544 opening the box and disconnecting the hard drive! This is as far as I
6545 can tell, the only way to get access to the firmware setup menu
6546 without accepting the Windows 8 license agreement. I am told (and
6547 found description on how to) that it is possible to configure the
6548 firmware setup once booted into Windows 8. But as I believe the terms
6549 of that agreement are completely unacceptable, accepting the license
6550 was never an alternative. I do not enter agreements I do not intend
6551 to follow.&lt;/p&gt;
6552
6553 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6554 waste many hours on this, but luckily there was a way to get it to
6555 work. But I would not recommend it to anyone planning to run Linux on
6556 it, and I have become sceptical to Windows 8 certified laptops. Is
6557 this the way Linux will be forced out of the market place, by making
6558 it close to impossible for &quot;normal&quot; users to install Linux without
6559 accepting the Microsoft Windows license terms? Or at least not
6560 without risking to loose the warranty?&lt;/p&gt;
6561
6562 &lt;p&gt;I&#39;ve updated the
6563 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6564 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6565 do not have to struggle as much as I did to get Linux into the
6566 machine.&lt;/p&gt;
6567
6568 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6569 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6570 </description>
6571 </item>
6572
6573 <item>
6574 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6575 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6576 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</guid>
6577 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6578 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6579 new laptops for my parents and a few others. I bought Packard Bell
6580 Easynote LV to run Kubuntu on and use as their home computer. But I
6581 am completely unable to figure out how to install Linux on it. The
6582 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6583 instead of a BIOS to boot.&lt;/p&gt;
6584
6585 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6586 to get it to boot the Linux installer from my USB stick. I have yet
6587 to try the DVD install, and still hope it will work. when I turn on
6588 the computer, there is no information on what buttons to press to get
6589 the normal boot menu. I expect to get some boot menu to select PXE or
6590 USB stick booting. When booting, it first ask for the language to
6591 use, then for some regional settings, and finally if I will accept the
6592 Windows 8 terms of use. As these terms are completely unacceptable to
6593 me, I have no other choice but to turn off the computer and try again
6594 to get it to boot the Linux installer.&lt;/p&gt;
6595
6596 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6597 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6598 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6599 installed on this machine, please get in touch or update that wiki
6600 page. If I can&#39;t find a way to install Linux, I will have to return
6601 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6602
6603 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6604 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6605 on new Laptops?&lt;/p&gt;
6606 </description>
6607 </item>
6608
6609 <item>
6610 <title>How to transform a Debian based system to a Debian Edu installation</title>
6611 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6612 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6613 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6614 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6615 an operating system based on Debian intended for use in schools. It
6616 contain a turn-key solution for the computer network provided to
6617 pupils in the primary schools. It provide both the central server,
6618 network boot servers and desktop environments with heaps of
6619 educational software. The project was founded almost 12 years ago,
6620 2001-07-02. If you want to support the project, which is in need for
6621 cash to fund developer gatherings and other project related activity,
6622 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6623 donate some money&lt;/a&gt;.
6624
6625 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6626 lists and elsewhere, is the question on how to transform a Debian or
6627 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6628 hard, and last week I wrote a script to replicate the steps done by
6629 the Debian Edu installer.&lt;/p&gt;
6630
6631 &lt;p&gt;The script,
6632 &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;
6633 in the debian-edu-config package, will go through these six steps and
6634 transform an existing Debian Wheezy or Ubuntu (untested) installation
6635 into a Debian Edu Workstation:&lt;/p&gt;
6636
6637 &lt;ol&gt;
6638
6639 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6640 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6641 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6642 our configuration.&lt;/li&gt;
6643 &lt;li&gt;Preseed debconf database with profile setup in
6644 /etc/debian-edu/config, and run tasksel to install packages
6645 according to the profile specified in the config above,
6646 overriding some of the Debian automation machinery.&lt;/li&gt;
6647 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6648 that could not be done using preseeding.&lt;/li&gt;
6649 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6650
6651 &lt;/ol&gt;
6652
6653 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6654 replicated like this. Disk partitioning and LVM setup, for example.
6655 So this script just assume there is enough disk space to install all
6656 the needed packages.&lt;/p&gt;
6657
6658 &lt;p&gt;The script was created to help a Debian Edu student working on
6659 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6660 Debian Edu client, and using it he can take the existing
6661 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6662 transform it into a fully functioning Debian Edu Workstation (or
6663 Roaming Workstation, or whatever :).&lt;/p&gt;
6664
6665 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6666 If a LXDE based Roaming workstation is wanted instead, modify the
6667 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6668
6669 &lt;p&gt;&lt;pre&gt;
6670 PROFILE=&quot;Roaming-Workstation&quot;
6671 DESKTOP=&quot;lxde&quot;
6672 &lt;/pre&gt;&lt;/p&gt;
6673
6674 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6675 the cloud, by starting with a virtual Debian installation at some
6676 virtual hosting service and setting up all the services on first
6677 boot.&lt;/p&gt;
6678 </description>
6679 </item>
6680
6681 <item>
6682 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6683 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6685 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6686 <description>&lt;P&gt;In January,
6687 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6688 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6689 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6690 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6691 marvellous construction system from Denmark. We also created
6692 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6693 a place to take notes and write down our plans and hopes. And several
6694 people showed up to help. I was very happy to see the effect of my
6695 call. Since the small start, we have a debtags tag
6696 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6697 tag for LEGO related packages, and now count 10 packages related to
6698 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6699
6700 &lt;p&gt;&lt;table&gt;
6701 &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;
6702 &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;
6703 &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;
6704 &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;
6705 &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;
6706 &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;
6707 &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;
6708 &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;
6709 &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;
6710 &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;
6711 &lt;/table&gt;&lt;/p&gt;
6712
6713 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6714 currently available in Jessie/testing. leocad is so far only
6715 available in experimental.&lt;/p&gt;
6716
6717 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6718 adding the rest of the great free software tools available on Linux
6719 for LEGO designers.&lt;/p&gt;
6720 </description>
6721 </item>
6722
6723 <item>
6724 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6725 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6726 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6727 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6728 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6729 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6730 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6731 Debian release, and I expect to move my machines at home over to it fairly
6732 soon.&lt;/p&gt;
6733
6734 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6735 in particular make me very happy to see included. The
6736 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6737 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6738 included for the first time. Alongside similar programs like
6739 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6740 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6741 it allow for visual programming where syntax errors can not happen,
6742 and a friendly programming environment for learning to control the
6743 computer. Scratch will also be included in the next release of Debian
6744 Edu.&lt;/a&gt;
6745
6746 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6747 Edu/Skolelinux release too. The
6748 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6749 alpha release&lt;/a&gt; went out last week, and the next should soon
6750 follow.&lt;p&gt;
6751 </description>
6752 </item>
6753
6754 <item>
6755 <title>Isenkram 0.2 finally in the Debian archive</title>
6756 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6758 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6759 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6760 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6761 for many months. I uploaded it to the Debian experimental suite
6762 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6763
6764 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6765 install to work with a pluggable hardware device. The suggestion pop
6766 up when the device is plugged in. For example if a Lego Mindstorm NXT
6767 is inserted, it will suggest to install the program needed to program
6768 the NXT controller. Give it a go, and report bugs and suggestions to
6769 BTS. :)&lt;/p&gt;
6770 </description>
6771 </item>
6772
6773 <item>
6774 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
6775 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
6776 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
6777 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
6778 <description>&lt;p&gt;My
6779 &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
6780 bitcoin related blog post&lt;/a&gt; mentioned that the new
6781 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
6782 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6783 2013-01-19, and have been available in unstable since then. It was
6784 automatically copied to Ubuntu, and is available in their Raring
6785 version too.&lt;/p&gt;
6786
6787 &lt;p&gt;But there is a strange problem with the build that block this new
6788 version from being available on the i386 and kfreebsd-i386
6789 architectures. For some strange reason, the autobuilders in Debian
6790 for these architectures fail to run the test suite on these
6791 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
6792 We are so far unable to reproduce it when building it manually, and
6793 no-one have been able to propose a fix. If you got an idea what is
6794 failing, please let us know via the BTS.&lt;/p&gt;
6795
6796 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
6797 I often run low on disk space, is the fact that the client will exit
6798 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
6799 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
6800 it. :)&lt;/p&gt;
6801
6802 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6803 activities, please send Bitcoin donations to my address
6804 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6805 </description>
6806 </item>
6807
6808 <item>
6809 <title>Welcome to the world, Isenkram!</title>
6810 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
6811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
6812 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
6813 <description>&lt;p&gt;Yesterday, I
6814 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
6815 for testers&lt;/a&gt; for my prototype for making Debian better at handling
6816 pluggable hardware devices, which I
6817 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
6818 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
6819 up, and caused me to really want to to open up the development to more
6820 people. But before I did this, I want to come up with a sensible name
6821 for this project. Today I finally decided on a new name, and I have
6822 renamed the project from hw-support-handler to this new name. In the
6823 process, I moved the source to git and made it available as a
6824 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
6825 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
6826 To fetch and build the latest version of the source, use&lt;/p&gt;
6827
6828 &lt;pre&gt;
6829 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6830 cd isenkram &amp;&amp; git-buildpackage -us -uc
6831 &lt;/pre&gt;
6832
6833 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
6834 want to hack on the source or improve the package, please go ahead.
6835 But please talk to me first on IRC or via email before you do major
6836 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
6837
6838 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
6839 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6840 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
6841 the German word eisenkram, for those that are familiar with that
6842 word.&lt;/p&gt;
6843
6844 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
6845 instructions, to avoid confusing people with an error from the signing
6846 process.&lt;/p&gt;
6847
6848 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
6849 clone argument to avoid the need for authentication.&lt;/p&gt;
6850 </description>
6851 </item>
6852
6853 <item>
6854 <title>First prototype ready making hardware easier to use in Debian</title>
6855 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
6856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
6857 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
6858 <description>&lt;p&gt;Early this month I set out to try to
6859 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
6860 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
6861 prototype is working, and it is ready for a larger audience. To test
6862 it, fetch the
6863 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
6864 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
6865 package. You might have to log out and in again activate the
6866 autostart script.&lt;/p&gt;
6867
6868 &lt;p&gt;The design is simple:&lt;/p&gt;
6869
6870 &lt;ul&gt;
6871
6872 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
6873 hw-support-handlerd to start when the user log in.&lt;/li&gt;
6874
6875 &lt;li&gt;This program listen for kernel events about new hardware (directly
6876 from the kernel like udev does), not using HAL dbus events as I
6877 initially did.&lt;/li&gt;
6878
6879 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
6880 the APT database, a database
6881 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
6882 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
6883
6884 &lt;li&gt;If a package is mapped to the hardware in question, the package
6885 isn&#39;t installed yet and this is the first time the hardware was
6886 plugged in, show a desktop notification suggesting to install the
6887 package or packages.&lt;/li&gt;
6888
6889 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
6890 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
6891
6892 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
6893 package while showing progress information in a window.&lt;/li&gt;
6894
6895 &lt;/ul&gt;
6896
6897 &lt;p&gt;I still need to come up with a better name for the system. Here
6898 are some screen shots showing the prototype in action. First the
6899 notification, then the password request, and finally the request to
6900 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
6901
6902 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
6903 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
6904 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
6905 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
6906 &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;
6907
6908 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
6909 is already useful. The database of hardware to package mappings also
6910 need more work. It is currently compatible with the Ubuntu way of
6911 storing such information in the package control file, but could be
6912 changed to use other formats instead or in addition to the current
6913 method. I&#39;ve dropped the use of discover for this mapping, as the
6914 modalias approach is more flexible and easier to use on Linux as long
6915 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
6916
6917 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
6918 here is the command required to check out and build the source: Use
6919 &#39;&lt;tt&gt;svn checkout
6920 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6921 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
6922 devscripts package.&lt;/p&gt;
6923
6924 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
6925 renamed to Isenkram and the source moved from the Debian Edu
6926 subversion repository to a Debian collab-maint git repository. See
6927 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
6928 instructions&lt;/a&gt; for details.&lt;/p&gt;
6929 </description>
6930 </item>
6931
6932 <item>
6933 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
6934 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
6935 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
6936 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
6937 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
6938 suddenly in bed. With a quiet whimper, it went completely quiet and
6939 black. The power button was no longer able to turn it on. It was a
6940 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6941 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6942 Compaq I had before that. Now I need to find a replacement. To keep
6943 going during Christmas, I moved the one year old SSD disk to my old
6944 X40 where it fitted (only one I had left that could use it), but it is
6945 not a durable solution.
6946
6947 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
6948 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
6949
6950 &lt;ul&gt;
6951
6952 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
6953 than A4).&lt;/li&gt;
6954 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
6955 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
6956 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
6957 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
6958 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
6959 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
6960 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
6961 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
6962 size).&lt;/li&gt;
6963 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
6964 X.org packages.&lt;/li&gt;
6965 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
6966 the time).
6967
6968 &lt;/ul&gt;
6969
6970 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
6971 list. The reason is simply that the specifications on laptops the
6972 last 10-15 years have been sufficient for my needs, and I have to look
6973 at other features to choose my laptop. But are there still made as
6974 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6975 robust, and Thinkpads seem to be heading in the wrong direction since
6976 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
6977 still be useful.&lt;/p&gt;
6978
6979 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
6980 external keyboard? I&#39;ll have to check the
6981 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
6982 well-supported laptops, or perhaps just buy one preinstalled from one
6983 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
6984 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
6985 </description>
6986 </item>
6987
6988 <item>
6989 <title>How to find a browser plugin supporting a given MIME type</title>
6990 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
6991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
6992 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
6993 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
6994 install to get support for a given MIME type. Thanks to
6995 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
6996 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
6997 Unfortunately, not very many packages provide the needed meta
6998 information, Anyway, here is a small script to look up all browser
6999 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
7000
7001 &lt;pre&gt;
7002 #!/usr/bin/python
7003 import sys
7004 import apt
7005 def pkgs_handling_mimetype(mimetype):
7006 cache = apt.Cache()
7007 cache.open(None)
7008 thepkgs = []
7009 for pkg in cache:
7010 version = pkg.candidate
7011 if version is None:
7012 version = pkg.installed
7013 if version is None:
7014 continue
7015 record = version.record
7016 if not record.has_key(&#39;Npp-MimeType&#39;):
7017 continue
7018 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
7019 for t in mime_types:
7020 t = t.rstrip().strip()
7021 if t == mimetype:
7022 thepkgs.append(pkg.name)
7023 return thepkgs
7024 mimetype = &quot;audio/ogg&quot;
7025 if 1 &lt; len(sys.argv):
7026 mimetype = sys.argv[1]
7027 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
7028 for pkg in pkgs_handling_mimetype(mimetype):
7029 print &quot; %s&quot; %pkg
7030 &lt;/pre&gt;
7031
7032 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
7033
7034 &lt;pre&gt;
7035 % ./apt-find-browserplug-for-mimetype
7036 Browser plugin packages supporting audio/ogg:
7037 gecko-mediaplayer
7038 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7039 Browser plugin packages supporting application/x-shockwave-flash:
7040 browser-plugin-gnash
7041 %
7042 &lt;/pre&gt;
7043
7044 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
7045 itself to query for plugins and propose to install the needed
7046 packages. It would be great if Debian supported such feature too. Is
7047 anyone working on adding it?&lt;/p&gt;
7048
7049 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
7050 request for icweasel support for this feature is
7051 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
7052 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
7053 of manpower and wish for a different design is the reason thus feature
7054 is not yet in iceweasel from Debian.&lt;/p&gt;
7055 </description>
7056 </item>
7057
7058 <item>
7059 <title>What is the most supported MIME type in Debian?</title>
7060 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
7061 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
7062 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
7063 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
7064 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
7065 proposal to make it possible for a Desktop application to propose to
7066 the user some package to install to gain support for a given MIME
7067 type, font, library etc. that is currently missing. With such
7068 mechanism in place, it would be possible for the desktop to
7069 automatically propose and install leocad if some LDraw file is
7070 downloaded by the browser.&lt;/p&gt;
7071
7072 &lt;p&gt;To get some idea about the current content of the archive, I decided
7073 to write a simple program to extract all .desktop files from the
7074 Debian archive and look up the claimed MIME support there. The result
7075 can be found on the
7076 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
7077 site&lt;/a&gt;. Using the collected information, it become possible to
7078 answer the question in the title. Here are the 20 most supported MIME
7079 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7080 The complete list is available from the link above.&lt;/p&gt;
7081
7082 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
7083
7084 &lt;pre&gt;
7085 count MIME type
7086 ----- -----------------------
7087 32 text/plain
7088 30 audio/mpeg
7089 29 image/png
7090 28 image/jpeg
7091 27 application/ogg
7092 26 audio/x-mp3
7093 25 image/tiff
7094 25 image/gif
7095 22 image/bmp
7096 22 audio/x-wav
7097 20 audio/x-flac
7098 19 audio/x-mpegurl
7099 18 video/x-ms-asf
7100 18 audio/x-musepack
7101 18 audio/x-mpeg
7102 18 application/x-ogg
7103 17 video/mpeg
7104 17 audio/x-scpls
7105 17 audio/ogg
7106 16 video/x-ms-wmv
7107 &lt;/pre&gt;
7108
7109 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
7110
7111 &lt;pre&gt;
7112 count MIME type
7113 ----- -----------------------
7114 33 text/plain
7115 32 image/png
7116 32 image/jpeg
7117 29 audio/mpeg
7118 27 image/gif
7119 26 image/tiff
7120 26 application/ogg
7121 25 audio/x-mp3
7122 22 image/bmp
7123 21 audio/x-wav
7124 19 audio/x-mpegurl
7125 19 audio/x-mpeg
7126 18 video/mpeg
7127 18 audio/x-scpls
7128 18 audio/x-flac
7129 18 application/x-ogg
7130 17 video/x-ms-asf
7131 17 text/html
7132 17 audio/x-musepack
7133 16 image/x-xbitmap
7134 &lt;/pre&gt;
7135
7136 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
7137
7138 &lt;pre&gt;
7139 count MIME type
7140 ----- -----------------------
7141 31 text/plain
7142 31 image/png
7143 31 image/jpeg
7144 29 audio/mpeg
7145 28 application/ogg
7146 27 image/gif
7147 26 image/tiff
7148 26 audio/x-mp3
7149 23 audio/x-wav
7150 22 image/bmp
7151 21 audio/x-flac
7152 20 audio/x-mpegurl
7153 19 audio/x-mpeg
7154 18 video/x-ms-asf
7155 18 video/mpeg
7156 18 audio/x-scpls
7157 18 application/x-ogg
7158 17 audio/x-musepack
7159 16 video/x-ms-wmv
7160 16 video/x-msvideo
7161 &lt;/pre&gt;
7162
7163 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
7164 information mentioned in DEP-11. I have not yet had time to look at
7165 it, but hope the PackageKit people in Debian are on top of these
7166 issues.&lt;/p&gt;
7167
7168 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
7169 discovering a typo in my script.&lt;/p&gt;
7170 </description>
7171 </item>
7172
7173 <item>
7174 <title>Using modalias info to find packages handling my hardware</title>
7175 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
7176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
7177 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
7178 <description>&lt;p&gt;Yesterday, I wrote about the
7179 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
7180 values provided by the Linux kernel&lt;/a&gt; following my hope for
7181 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
7182 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
7183 modalias values attached to package names can be used to map packages
7184 to hardware. This allow the system to look up and suggest relevant
7185 packages when I plug in some new hardware into my machine, and replace
7186 discover and discover-data as the database used to map hardware to
7187 packages.&lt;/p&gt;
7188
7189 &lt;p&gt;I create a modaliases file with entries like the following,
7190 containing package name, kernel module name (if relevant, otherwise
7191 the package name) and globs matching the relevant hardware
7192 modalias.&lt;/p&gt;
7193
7194 &lt;p&gt;&lt;blockquote&gt;
7195 Package: package-name
7196 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
7197 &lt;/blockquote&gt;&lt;/p&gt;
7198
7199 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
7200 for a given modalias value using this file.&lt;/p&gt;
7201
7202 &lt;p&gt;An entry like this would suggest the video and picture application
7203 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
7204
7205 &lt;p&gt;&lt;blockquote&gt;
7206 Package: cheese
7207 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
7208 &lt;/blockquote&gt;&lt;/p&gt;
7209
7210 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
7211 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
7212
7213 &lt;p&gt;&lt;blockquote&gt;
7214 Package: pcmciautils
7215 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7216 &lt;/blockquote&gt;&lt;/p&gt;
7217
7218 &lt;p&gt;An entry like this would suggest the package colorhug-client when
7219 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
7220
7221 &lt;p&gt;&lt;blockquote&gt;
7222 Package: colorhug-client
7223 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
7224 &lt;/blockquote&gt;&lt;/p&gt;
7225
7226 &lt;p&gt;I believe the format is compatible with the format of the Packages
7227 file in the Debian archive. Ubuntu already uses their Packages file
7228 to store their mappings from packages to hardware.&lt;/p&gt;
7229
7230 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
7231 announce the hardware it support in a way my prototype understand.
7232 This allow those publishing packages in an APT source outside the
7233 Debian archive as well as those backporting packages to make sure the
7234 hardware mapping are included in the package meta information. I&#39;ve
7235 tested such header in the pymissile package, and its modalias mapping
7236 is working as it should with my prototype. It even made it to Ubuntu
7237 Raring.&lt;/p&gt;
7238
7239 &lt;p&gt;To test if it was possible to look up supported hardware using only
7240 the shell tools available in the Debian installer, I wrote a shell
7241 implementation of the lookup code. The idea is to create files for
7242 each modalias and let the shell do the matching. Please check out and
7243 try the
7244 &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;
7245 shell script. It run without any extra dependencies and fetch the
7246 hardware mappings from the Debian archive and the subversion
7247 repository where I currently work on my prototype.&lt;/p&gt;
7248
7249 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
7250 install yubikey-personalization:&lt;/p&gt;
7251
7252 &lt;p&gt;&lt;blockquote&gt;
7253 % ./hw-support-lookup
7254 &lt;br&gt;yubikey-personalization
7255 &lt;br&gt;%
7256 &lt;/blockquote&gt;&lt;/p&gt;
7257
7258 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7259 propose to install the pcmciautils package:&lt;/p&gt;
7260
7261 &lt;p&gt;&lt;blockquote&gt;
7262 % ./hw-support-lookup
7263 &lt;br&gt;pcmciautils
7264 &lt;br&gt;%
7265 &lt;/blockquote&gt;&lt;/p&gt;
7266
7267 &lt;p&gt;If you know of any hardware-package mapping that should be added to
7268 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
7269 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
7270
7271 &lt;p&gt;It could be possible to generate several of the mappings between
7272 packages and hardware. One source would be to look at packages with
7273 kernel modules, ie packages with *.ko files in /lib/modules/, and
7274 extract their modalias information. Another would be to look at
7275 packages with udev rules, ie packages with files in
7276 /lib/udev/rules.d/, and extract their vendor/model information to
7277 generate a modalias matching rule. I have not tested any of these to
7278 see if it work.&lt;/p&gt;
7279
7280 &lt;p&gt;If you want to help implementing a system to let us propose what
7281 packages to install when new hardware is plugged into a Debian
7282 machine, please send me an email or talk to me on
7283 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7284 </description>
7285 </item>
7286
7287 <item>
7288 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7289 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7291 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7292 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7293 information, to find the packages that support a given piece of
7294 hardware, I refreshed my memory regarding modalias values, and decided
7295 to document the details. Here are my findings so far, also available
7296 in
7297 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7298 Debian Edu subversion repository&lt;/a&gt;:
7299
7300 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7301
7302 &lt;p&gt;This document try to explain what the different types of modalias
7303 values stands for. It is in part based on information from
7304 &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;,
7305 &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;,
7306 &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
7307 &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;.
7308
7309 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7310 this shell script:&lt;/p&gt;
7311
7312 &lt;pre&gt;
7313 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7314 &lt;/pre&gt;
7315
7316 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7317 using modinfo:&lt;/p&gt;
7318
7319 &lt;pre&gt;
7320 % /sbin/modinfo psmouse | grep alias:
7321 alias: serio:ty05pr*id*ex*
7322 alias: serio:ty01pr*id*ex*
7323 %
7324 &lt;/pre&gt;
7325
7326 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7327
7328 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7329 Bridge memory controller:&lt;/p&gt;
7330
7331 &lt;p&gt;&lt;blockquote&gt;
7332 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7333 &lt;/blockquote&gt;&lt;/p&gt;
7334
7335 &lt;p&gt;This represent these values:&lt;/p&gt;
7336
7337 &lt;pre&gt;
7338 v 00008086 (vendor)
7339 d 00002770 (device)
7340 sv 00001028 (subvendor)
7341 sd 000001AD (subdevice)
7342 bc 06 (bus class)
7343 sc 00 (bus subclass)
7344 i 00 (interface)
7345 &lt;/pre&gt;
7346
7347 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7348 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7349 0600. The 0600 class is a host bridge. Other useful bus values are
7350 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7351
7352 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7353 means.&lt;/p&gt;
7354
7355 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7356
7357 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7358 USB hub in a laptop:&lt;/p&gt;
7359
7360 &lt;p&gt;&lt;blockquote&gt;
7361 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7362 &lt;/blockquote&gt;&lt;/p&gt;
7363
7364 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7365
7366 &lt;pre&gt;
7367 v 1D6B (device vendor)
7368 p 0001 (device product)
7369 d 0206 (bcddevice)
7370 dc 09 (device class)
7371 dsc 00 (device subclass)
7372 dp 00 (device protocol)
7373 ic 09 (interface class)
7374 isc 00 (interface subclass)
7375 ip 00 (interface protocol)
7376 &lt;/pre&gt;
7377
7378 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7379 class is in the interface class section. For a simple USB web camera,
7380 these alias entries show up:&lt;/p&gt;
7381
7382 &lt;p&gt;&lt;blockquote&gt;
7383 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7384 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7385 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7386 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7387 &lt;/blockquote&gt;&lt;/p&gt;
7388
7389 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7390 camera), 0101 is audio control device and 0102 is audio streaming (aka
7391 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7392
7393 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7394
7395 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7396 receiver in a Thinkpad X40:&lt;/p&gt;
7397
7398 &lt;p&gt;&lt;blockquote&gt;
7399 acpi:IBM0071:PNP0511:
7400 &lt;/blockquote&gt;&lt;/p&gt;
7401
7402 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7403
7404 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7405
7406 &lt;p&gt;The DMI table contain lots of information about the computer case
7407 and model. This is an entry for a IBM Thinkpad X40, fetched from
7408 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7409
7410 &lt;p&gt;&lt;blockquote&gt;
7411 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7412 &lt;/blockquote&gt;&lt;/p&gt;
7413
7414 &lt;p&gt;The values present are&lt;/p&gt;
7415
7416 &lt;pre&gt;
7417 bvn IBM (BIOS vendor)
7418 bvr 1UETB6WW(1.66) (BIOS version)
7419 bd 06/15/2005 (BIOS date)
7420 svn IBM (system vendor)
7421 pn 2371H4G (product name)
7422 pvr ThinkPadX40 (product version)
7423 rvn IBM (board vendor)
7424 rn 2371H4G (board name)
7425 rvr NotAvailable (board version)
7426 cvn IBM (chassis vendor)
7427 ct 10 (chassis type)
7428 cvr NotAvailable (chassis version)
7429 &lt;/pre&gt;
7430
7431 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7432 found in the dmidecode source:&lt;/p&gt;
7433
7434 &lt;pre&gt;
7435 3 Desktop
7436 4 Low Profile Desktop
7437 5 Pizza Box
7438 6 Mini Tower
7439 7 Tower
7440 8 Portable
7441 9 Laptop
7442 10 Notebook
7443 11 Hand Held
7444 12 Docking Station
7445 13 All In One
7446 14 Sub Notebook
7447 15 Space-saving
7448 16 Lunch Box
7449 17 Main Server Chassis
7450 18 Expansion Chassis
7451 19 Sub Chassis
7452 20 Bus Expansion Chassis
7453 21 Peripheral Chassis
7454 22 RAID Chassis
7455 23 Rack Mount Chassis
7456 24 Sealed-case PC
7457 25 Multi-system
7458 26 CompactPCI
7459 27 AdvancedTCA
7460 28 Blade
7461 29 Blade Enclosing
7462 &lt;/pre&gt;
7463
7464 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7465 table. For example my home server is a tower, but the DMI modalias
7466 claim it is a desktop.&lt;/p&gt;
7467
7468 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7469
7470 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7471 test machine:&lt;/p&gt;
7472
7473 &lt;p&gt;&lt;blockquote&gt;
7474 serio:ty01pr00id00ex00
7475 &lt;/blockquote&gt;&lt;/p&gt;
7476
7477 &lt;p&gt;The values present are&lt;/p&gt;
7478
7479 &lt;pre&gt;
7480 ty 01 (type)
7481 pr 00 (prototype)
7482 id 00 (id)
7483 ex 00 (extra)
7484 &lt;/pre&gt;
7485
7486 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7487 the valid values are.&lt;/p&gt;
7488
7489 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7490
7491 &lt;p&gt;There are heaps of other modalias subtypes according to
7492 file2alias.c. There is the rest of the list from that source: amba,
7493 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7494 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7495 vmbus, x86cpu and zorro. I did not spend time documenting all of
7496 these, as they do not seem relevant for my intended use with mapping
7497 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7498
7499 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7500
7501 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7502 one can use the following shell script:&lt;/p&gt;
7503
7504 &lt;pre&gt;
7505 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7506 echo &quot;$id&quot; ; \
7507 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7508 done
7509 &lt;/pre&gt;
7510
7511 &lt;p&gt;The output can look like this (only the first few entries as the
7512 list is very long on my test machine):&lt;/p&gt;
7513
7514 &lt;pre&gt;
7515 acpi:ACPI0003:
7516 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7517 acpi:device:
7518 FATAL: Module acpi:device: not found.
7519 acpi:IBM0068:
7520 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7521 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7522 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7523 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7524 acpi:IBM0071:PNP0511:
7525 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7526 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7527 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7528 [...]
7529 &lt;/pre&gt;
7530
7531 &lt;p&gt;If you want to help implementing a system to let us propose what
7532 packages to install when new hardware is plugged into a Debian
7533 machine, please send me an email or talk to me on
7534 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7535
7536 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7537 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7538 in /sys/ with space in them.&lt;/p&gt;
7539 </description>
7540 </item>
7541
7542 <item>
7543 <title>Moved the pymissile Debian packaging to collab-maint</title>
7544 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7545 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7546 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7547 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7548 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7549 Launcher and updated the Debian package
7550 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7551 sure udev will fix the device permissions when it is plugged in. I
7552 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7553 hopefully make the package be proposed by jockey in Ubuntu when a user
7554 plug in his rocket launcher. In the process I moved the source to a
7555 git repository under collab-maint, to make it easier for any DD to
7556 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7557 is not very active, but the software still work for me even after five
7558 years of relative silence. The new git repository is not listed in
7559 the uploaded package yet, because I want to test the other changes a
7560 bit more before I upload the new version. If you want to check out
7561 the new version with a .desktop file included, visit the
7562 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7563 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7564 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7565 </description>
7566 </item>
7567
7568 <item>
7569 <title>Lets make hardware dongles easier to use in Debian</title>
7570 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7571 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7572 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7573 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7574 general, is that there is a great package management system with the
7575 ability to automatically install software packages by downloading them
7576 from the distribution mirrors, but no way to get it to automatically
7577 install the packages I need to use the hardware I plug into my
7578 machine. Even if the package to use it is easily available from the
7579 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7580 suggest to automatically install the python-nxt, nbc and t2n packages
7581 I need to talk to it. When I plug in a Yubikey, it could propose the
7582 yubikey-personalization package. The information required to do this
7583 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7584
7585 &lt;p&gt;Some years ago, I proposed to
7586 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7587 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7588 simple:
7589
7590 &lt;ul&gt;
7591
7592 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7593 starting when a user log in.&lt;/li&gt;
7594
7595 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7596 hardware is inserted into the computer.&lt;/li&gt;
7597
7598 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7599 database mapping to packages, and take note of any non-installed
7600 packages.&lt;/li&gt;
7601
7602 &lt;li&gt;Show a message to the user proposing to install the discovered
7603 package, and make it easy to install it.&lt;/li&gt;
7604
7605 &lt;/ul&gt;
7606
7607 &lt;p&gt;I am not sure what the best way to implement this is, but my
7608 initial idea was to use dbus events to discover new hardware, the
7609 discover database to find packages and
7610 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7611 packages.&lt;/p&gt;
7612
7613 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7614 draft package is now checked into
7615 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7616 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7617 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7618 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7619 the relevant packages in Debian, and uploaded a new version
7620 2.2013.01.09 to unstable. I also discovered that the current
7621 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7622 package in Debian no longer discovered any USB devices, because
7623 /proc/bus/usb/devices is no longer present. I ported it to use
7624 libusb as a fall back option to get it working. The fixed package
7625 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7626 because of the freeze).&lt;/p&gt;
7627
7628 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7629 desktop notification to show up (only once, the first time it is
7630 inserted):&lt;/p&gt;
7631
7632 &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;
7633
7634 &lt;p&gt;For this prototype to be really useful, some way to automatically
7635 install the proposed packages by pressing the &quot;Please install
7636 program(s)&quot; button should to be implemented.&lt;/p&gt;
7637
7638 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7639 happen, please help me update the discover-data database with mappings
7640 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7641 list the package you would like to have installed when a given
7642 hardware device is inserted into your computer, and report bugs using
7643 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7644 such mapping, please let me know.&lt;/p&gt;
7645
7646 &lt;p&gt;This prototype need more work, and there are several questions that
7647 should be considered before it is ready for production use. Is dbus
7648 the correct way to detect new hardware? At the moment I look for HAL
7649 dbus events on the system bus, because that is the events I could see
7650 on my Debian Squeeze KDE desktop. Are there better events to use?
7651 How should the user be notified? Is the desktop notification
7652 mechanism the best option, or should the background daemon raise a
7653 popup instead? How should packages be installed? When should they
7654 not be installed?&lt;/p&gt;
7655
7656 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7657 please send me an email. :)&lt;/p&gt;
7658 </description>
7659 </item>
7660
7661 <item>
7662 <title>New IRC channel for LEGO designers using Debian</title>
7663 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7664 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7665 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7666 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7667 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7668 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7669 discovered I had to build all the tools myself because none were
7670 already in Debian Squeeze. If Debian support for LEGO is something
7671 you care about, please join me on the IRC channel
7672 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7673 irc.debian.org). There is a lot that could be done to improve the
7674 Debian support for LEGO designers. For example both CAD software
7675 and Mindstorm compilers are missing. :)&lt;/p&gt;
7676
7677 &lt;p&gt;Update 2012-01-03: A
7678 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7679 including links to Lego related packages is now available.&lt;/p&gt;
7680 </description>
7681 </item>
7682
7683 <item>
7684 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7685 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7687 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7688 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7689 year! I hope next year will prove to be a good year.&lt;/p&gt;
7690
7691 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7692 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7693 between each other with minimal overhead, is a very interesting
7694 experiment. And as I wrote a few days ago, the bitcoin situation in
7695 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7696 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7697 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7698 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7699 for one of the ftpmasters to approve the new bitcoin-qt package
7700 name.&lt;/p&gt;
7701
7702 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7703 team in Debian, you can easily test the package in Debian Squeeze
7704 using the following steps to get a set of working packages:&lt;/p&gt;
7705
7706 &lt;blockquote&gt;&lt;pre&gt;
7707 git clone git://git.debian.org/git/collab-maint/bitcoin
7708 cd bitcoin
7709 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7710 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7711 &lt;/pre&gt;&lt;/blockquote&gt;
7712
7713 &lt;p&gt;You might have to install some build dependencies as well. The
7714 list of commands should give you two packages, bitcoind and
7715 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7716 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7717 around 5.6 GiB of data on my machine at the moment. Make sure your
7718 ~/.bitcoin/ directory have lots of spare room if you want to download
7719 all the blocks. The client will warn if the disk is getting full, so
7720 there is not really a problem if you got too little room, but you will
7721 not be able to get all the features out of the client.&lt;/p&gt;
7722
7723 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7724 activities, please send Bitcoin donations to my address
7725 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7726 </description>
7727 </item>
7728
7729 <item>
7730 <title>A word on bitcoin support in Debian</title>
7731 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7733 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7734 <description>&lt;p&gt;It has been a while since I wrote about
7735 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7736 peer-to-peer based crypto-currency, and the reason is simply that I
7737 have been busy elsewhere. But two days ago, I started looking at the
7738 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7739 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7740 is now maintained by a
7741 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7742 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7743 owe a huge thank you to all these team members. :)
7744 But I was sad to discover that the bitcoin client is missing in
7745 Wheezy. It is only available in Sid (and an outdated client from
7746 backports). The client had several RC bugs registered in BTS blocking
7747 it from entering testing. To try to help the team and improve the
7748 situation, I spent some time providing patches and triaging the bug
7749 reports. I also had a look at the bitcoin package available from Matt
7750 Corallo in a
7751 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7752 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7753 Debian package.&lt;/p&gt;
7754
7755 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7756 IRC, I pushed several patches into the collab-maint git repository to
7757 improve the package. It now contains fixes for the RC issues (not from
7758 me, but fixed by Scott Howard), build rules for a Qt GUI client
7759 package, konqueror support for the bitcoin: URI and bash completion
7760 setup. As I work on Debian Squeeze, I also created
7761 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7762 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7763 it and try to integrate it into the git repository before uploading a
7764 new version to unstable.
7765
7766 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7767 centralized control currently exercised in the monetary system. I
7768 find it completely unacceptable that the USA government is collecting
7769 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7770 that the major credit card companies can block legal money
7771 transactions to Wikileaks. But for bitcoin to succeed, more people
7772 need to use bitcoins, and more people need to accept bitcoins when
7773 they sell products and services. Improving the bitcoin support in
7774 Debian is a small step in the right direction, but not enough.
7775 Unfortunately the user experience when browsing the web and wanting to
7776 pay with bitcoin is still not very good. The bitcoin: URI is a step
7777 in the right direction, but need to work in most or every browser in
7778 use. Also the bitcoin-qt client is too heavy to fire up to do a
7779 quick transaction. I believe there are other clients available, but
7780 have not tested them.&lt;/p&gt;
7781
7782 &lt;p&gt;My
7783 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
7784 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
7785 I received 20.15 BTC so far on the address I provided in my blog two
7786 years ago, as can be
7787 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
7788 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
7789 donation. The blockexplorer service demonstrates quite well that
7790 bitcoin is not quite anonymous and untracked. :) I wonder if the
7791 number of users have gone up since then. If you use bitcoin and want
7792 to show your support of my activity, please send Bitcoin donations to
7793 the same address as last time,
7794 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7795 </description>
7796 </item>
7797
7798 <item>
7799 <title>Git repository for song book for Computer Scientists</title>
7800 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
7801 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
7802 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
7803 <description>&lt;p&gt;As I
7804 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
7805 this summer&lt;/a&gt;, I have created a Computer Science song book a few
7806 years ago, and today I finally found time to create a public
7807 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
7808 repository for the project&lt;/a&gt;.&lt;/p&gt;
7809
7810 &lt;p&gt;If you want to help out, please clone the source and submit patches
7811 to the HTML version. To generate the PDF and PostScript version,
7812 please use prince XML, or let me know about a useful free software
7813 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
7814
7815 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
7816 PostScript formats at
7817 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
7818 Science Songbook&lt;/a&gt;.&lt;/p&gt;
7819 </description>
7820 </item>
7821
7822 <item>
7823 <title>Gratulerer med 19-årsdagen, Debian!</title>
7824 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
7825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
7826 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
7827 <description>&lt;p&gt;I dag fyller
7828 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
7829 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
7830 si gratulerer med dagen, Debian!&lt;/p&gt;
7831 </description>
7832 </item>
7833
7834 <item>
7835 <title>Song book for Computer Scientists</title>
7836 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
7837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
7838 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
7839 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
7840 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
7841 collecting computer related songs for use at parties. The original
7842 version was written in LaTeX, but a few years ago I got help from
7843 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7844 while keeping the ability to create a nice book in PDF format. I have
7845 not had time to maintain the book for a while now, and guess I should
7846 put it up on some public version control repository where others can
7847 help me extend and update the book. If anyone is volunteering to help
7848 me with this, send me an email. Also let me know if there are songs
7849 missing in my book.&lt;/p&gt;
7850
7851 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
7852 me today that I really should let all my readers share the joys of
7853 singing out load about programming, computers and computer networks.
7854 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
7855 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
7856 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
7857 Computer Science Songbook&lt;/a&gt;.
7858 </description>
7859 </item>
7860
7861 <item>
7862 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
7863 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
7864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
7865 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
7866 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
7867 around 1000 at the moment. To be able to get help from the vendors
7868 when something go wrong, we want to keep the firmware on the servers
7869 up to date. If the firmware isn&#39;t the latest and greatest, the
7870 vendors typically refuse to start debugging any problems until the
7871 firmware is upgraded. So before every reboot, we want to upgrade the
7872 firmware, and we would really like everyone handling servers at the
7873 university to do this themselves when they plan to reboot a machine.
7874 For that to happen we at the unix server admin group need to provide
7875 the tools to do so.&lt;/p&gt;
7876
7877 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
7878 fetch and install the latest firmware for the servers we got. Most of
7879 our hardware are from Dell and HP, so I have focused on these servers
7880 so far. This blog post is about the Dell part.&lt;/P&gt;
7881
7882 &lt;p&gt;On the Dell FTP site I was lucky enough to find
7883 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
7884 with firmware information for all 11th generation servers, listing
7885 which firmware should be used on a given model and where on the FTP
7886 site I can find it. Using a simple perl XML parser I can then
7887 download the shell scripts Dell provides to do firmware upgrades from
7888 within Linux and reboot when all the firmware is primed and ready to
7889 be activated on the first reboot.&lt;/p&gt;
7890
7891 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
7892 Are there anyone working on similar tools for firmware upgrading all
7893 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
7894
7895 &lt;p&gt;&lt;pre&gt;
7896 #!/usr/bin/perl
7897 use strict;
7898 use warnings;
7899 use File::Temp qw(tempdir);
7900 BEGIN {
7901 # Install needed RHEL packages if missing
7902 my %rhelmodules = (
7903 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
7904 );
7905 for my $module (keys %rhelmodules) {
7906 eval &quot;use $module;&quot;;
7907 if ($@) {
7908 my $pkg = $rhelmodules{$module};
7909 system(&quot;yum install -y $pkg&quot;);
7910 eval &quot;use $module;&quot;;
7911 }
7912 }
7913 }
7914 my $errorsto = &#39;pere@hungry.com&#39;;
7915
7916 upgrade_dell();
7917
7918 exit 0;
7919
7920 sub run_firmware_script {
7921 my ($opts, $script) = @_;
7922 unless ($script) {
7923 print STDERR &quot;fail: missing script name\n&quot;;
7924 exit 1
7925 }
7926 print STDERR &quot;Running $script\n\n&quot;;
7927
7928 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
7929 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
7930 } else {
7931 print STDERR &quot;fail: firmware script returned error\n&quot;;
7932 }
7933 }
7934
7935 sub run_firmware_scripts {
7936 my ($opts, @dirs) = @_;
7937 # Run firmware packages
7938 for my $dir (@dirs) {
7939 print STDERR &quot;info: Running scripts in $dir\n&quot;;
7940 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
7941 while (my $s = readdir $dh) {
7942 next if $s =~ m/^\.\.?/;
7943 run_firmware_script($opts, &quot;$dir/$s&quot;);
7944 }
7945 closedir $dh;
7946 }
7947 }
7948
7949 sub download {
7950 my $url = shift;
7951 print STDERR &quot;info: Downloading $url\n&quot;;
7952 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
7953 }
7954
7955 sub upgrade_dell {
7956 my @dirs;
7957 my $product = `dmidecode -s system-product-name`;
7958 chomp $product;
7959
7960 if ($product =~ m/PowerEdge/) {
7961
7962 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7963 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
7964
7965 my $tmpdir = tempdir(
7966 CLEANUP =&gt; 1
7967 );
7968 chdir($tmpdir);
7969 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
7970 system(&#39;gunzip Catalog.xml.gz&#39;);
7971 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
7972 # -q is quiet, disabling interactivity and reducing console output
7973 my $fwopts = &quot;-q&quot;;
7974 if (@paths) {
7975 for my $url (@paths) {
7976 fetch_dell_fw($url);
7977 }
7978 run_firmware_scripts($fwopts, $tmpdir);
7979 } else {
7980 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7981 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7982 }
7983 chdir(&#39;/&#39;);
7984 } else {
7985 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7986 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7987 }
7988 }
7989
7990 sub fetch_dell_fw {
7991 my $path = shift;
7992 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
7993 download($url);
7994 }
7995
7996 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7997 # firmware packages to download from Dell. Only work for Linux
7998 # machines and 11th generation Dell servers.
7999 sub fetch_dell_fw_list {
8000 my $filename = shift;
8001
8002 my $product = `dmidecode -s system-product-name`;
8003 chomp $product;
8004 my ($mybrand, $mymodel) = split(/\s+/, $product);
8005
8006 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
8007
8008 my $xml = XMLin($filename);
8009 my @paths;
8010 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
8011 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
8012 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
8013 my $oscode;
8014 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
8015 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
8016 } else {
8017 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
8018 }
8019 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
8020 {
8021 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
8022 }
8023 }
8024 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
8025 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
8026
8027 # Drop application packages, only firmware and BIOS
8028 next if &#39;APAC&#39; eq $componenttype;
8029
8030 my $cpath = $component-&gt;{path};
8031 for my $path (@paths) {
8032 if ($cpath =~ m%/$path$%) {
8033 push(@paths, $cpath);
8034 }
8035 }
8036 }
8037 return @paths;
8038 }
8039 &lt;/pre&gt;
8040
8041 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
8042 it could work on other platforms with some tweaking. Anyone know a
8043 index like Catalog.xml is available from HP for HP servers? At the
8044 moment I maintain a similar list manually and it is quickly getting
8045 outdated.&lt;/p&gt;
8046 </description>
8047 </item>
8048
8049 <item>
8050 <title>How is booting into runlevel 1 different from single user boots?</title>
8051 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
8052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
8053 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
8054 <description>&lt;p&gt;Wouter Verhelst have some
8055 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
8056 comments and opinions&lt;/a&gt; on my blog post on
8057 &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
8058 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
8059 &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
8060 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
8061 small piece of his comment now, and though it best to address the
8062 misunderstanding he bring forward:&lt;/p&gt;
8063
8064 &lt;p&gt;&lt;blockquote&gt;
8065 Currently, a system admin has four options: [...] boot to a
8066 single-user system (by adding &#39;single&#39; to the kernel command line;
8067 this runs rcS and rc1 scripts)
8068 &lt;/blockquote&gt;&lt;/p&gt;
8069
8070 &lt;p&gt;This make me believe Wouter believe booting into single user mode
8071 and booting into runlevel 1 is the same. I am not surprised he
8072 believe this, because it would make sense and is a quite sensible
8073 thing to believe. But because the boot in Debian is slightly broken,
8074 runlevel 1 do not work properly and it isn&#39;t the same as single user
8075 mode. I&#39;ll try to explain what is actually happing, but it is a bit
8076 hard to explain.&lt;/p&gt;
8077
8078 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
8079 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
8080 executed in single user mode is sulogin. Single user mode is a boot
8081 state &quot;between&quot; the runlevels, and when booting into single user mode,
8082 only the scripts in /etc/rcS.d/ are executed before the init process
8083 enters the single user state. When switching to runlevel 1, the state
8084 is in fact not ending in runlevel 1, but it passes through runlevel 1
8085 and end up in the single user mode (see /etc/rc1.d/S03single, which
8086 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
8087 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
8088 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8089 mode).&lt;/p&gt;
8090
8091 &lt;p&gt;This summary might make it clearer. When booting for the first
8092 time into single user mode, the following commands are executed:
8093 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
8094 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
8095 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
8096 trying to continue after visiting single user mode. Not all services
8097 are started again as they should, causing the machine to end up in an
8098 unpredicatble state. This is why Debian admins recommend rebooting
8099 after visiting single user mode.&lt;/p&gt;
8100
8101 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
8102 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
8103 to runlevel 1, the services started from /etc/rcS.d/ are not properly
8104 stopped when passing through the scripts in /etc/rc1.d/, and not
8105 started again when switching away from runlevel 1 to the runlevels
8106 2-5. I believe the problem is best fixed by moving all the scripts
8107 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
8108 functioning single user mode during boot.&lt;/p&gt;
8109
8110 &lt;p&gt;I have spent several years investigating the Debian boot system,
8111 and discovered this problem a few years ago. I suspect it originates
8112 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
8113 </description>
8114 </item>
8115
8116 <item>
8117 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
8118 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
8119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
8120 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
8121 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
8122 are started from /etc/rcS.d/. In fact, there is a bite more of them
8123 than make sense, and this causes a few problems. What kind of
8124 problems, you might ask. There are at least two problems. The first
8125 is that it is not possible to recover a machine after switching to
8126 runlevel 1. One need to actually reboot to get the machine back to
8127 the expected state. The other is that single user boot will sometimes
8128 run into problems because some of the subsystems are activated before
8129 the root login is presented, causing problems when trying to recover a
8130 machine from a problem in that subsystem. A minor additional point is
8131 that moving more scripts out of rcS.d/ and into the other rc#.d/
8132 directories will increase the amount of scripts that can run in
8133 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
8134
8135 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
8136 scripts that _have_ to execute before the root login prompt is
8137 presented during a single user boot should go there. Everything else
8138 should go into the numeric runlevels. This means things like
8139 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8140 the numeric runlevels. Today in Debian, there are around 115 init.d
8141 scripts that are started from rcS.d/, and most of them should be moved
8142 out. Do your package have one of them? Please help us make single
8143 user and runlevel 1 better by moving it.&lt;/p&gt;
8144
8145 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
8146 etc. should still be started from rcS.d/, but there is for example no
8147 need to have the network enabled before the single user login prompt
8148 is presented.&lt;/p&gt;
8149
8150 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
8151 Debian systems working while scripts migrate and during upgrades, the
8152 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8153 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8154 and the next ones can only be moved when their dependencies have been
8155 moved first. This migration must be done sequentially while we ensure
8156 that the package system upgrade packages in the right order to keep
8157 the system state correct. This will require some coordination when it
8158 comes to network related packages, but most of the packages with
8159 scripts that should migrate do not have anything in rcS.d/ depending
8160 on them. Some packages have already been updated, like the sudo
8161 package, while others are still left to do. I wish I had time to work
8162 on this myself, but real live constrains make it unlikely that I will
8163 find time to push this forward.&lt;/p&gt;
8164 </description>
8165 </item>
8166
8167 <item>
8168 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
8169 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
8170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
8171 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
8172 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
8173 mentioned the issues I believe should be improved in Debian for its
8174 desktop to be useful for more people. The use case for this is my
8175 parents, which are currently running Kubuntu which solve the
8176 issues.&lt;/p&gt;
8177
8178 &lt;p&gt;I suspect these four missing features are not very hard to
8179 implement. After all, they are present in Ubuntu, so if we wanted to
8180 do this in Debian we would have a source.&lt;/p&gt;
8181
8182 &lt;ol&gt;
8183
8184 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
8185 are new packages available for upgrades, a icon in the KDE status bar
8186 indicate this, and clicking on it will activate the simple upgrade
8187 tool to handle it. I have no problem guiding both of my parents
8188 through the process over the phone. If a kernel reboot is required,
8189 this too is indicated by the status bars and the upgrade tool. Last
8190 time I checked, nothing with the same features was working in KDE in
8191 Debian.&lt;/li&gt;
8192
8193 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
8194 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
8195 currently have a handler for, it will ask the user if the system
8196 should search for a package that would add support for this MIME type,
8197 and if the user say yes, the APT sources will be searched for packages
8198 advertising the MIME type in their control file (visible in the
8199 Packages file in the APT archive). If one or more packages are found,
8200 it is a simple click of the mouse to add support for the missing mime
8201 type. If the package require the user to accept some non-free
8202 license, this is explained to the user. The entire process make it
8203 more clear to the user why something do not work in the browser, and
8204 make the chances higher for the user to blame the web page authors and
8205 not the browser for any missing features.&lt;/li&gt;
8206
8207 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
8208 handlers.&lt;/strong&gt; When the media players encounter a format or codec
8209 it is not supporting, a dialog pop up asking the user if the system
8210 should search for a package that would add support for it. This
8211 happen with things like MP3, Windows Media or H.264. The selection
8212 and installation procedure is very similar to the Firefox browser
8213 plugin handling. This is as far as I know implemented using a
8214 gstreamer hook. The end result is that the user easily get access to
8215 the codecs that are present from the APT archives available, while
8216 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
8217
8218 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
8219 displaying a text/plain file in my Debian browser, it will propose to
8220 start emacs to show it. If I remember correctly, when doing the same
8221 in Kunbutu it show the file as a text file in the browser. At least I
8222 know Opera will show text files within the browser. I much prefer the
8223 latter behaviour.&lt;/li&gt;
8224
8225 &lt;/ol&gt;
8226
8227 &lt;p&gt;There are other nice features as well, like the simplified suite
8228 upgrader, but given that I am the one mostly doing the dist-upgrade,
8229 it do not matter much.&lt;/p&gt;
8230
8231 &lt;p&gt;I really hope we could get these features in place for the next
8232 Debian release. It would require the coordinated effort of several
8233 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
8234 </description>
8235 </item>
8236
8237 <item>
8238 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
8239 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
8240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
8241 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
8242 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
8243 site is build on Debian/Squeeze, and this platform was chosen because
8244 I am most familiar with Debian (being a Debian Developer for around 10
8245 years) because it is the latest stable Debian release which should get
8246 security support for a few years.&lt;/p&gt;
8247
8248 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
8249 that are missing in Debian at the moment. It would be great if these
8250 modules were added to the Debian archive, allowing anyone to set up
8251 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
8252 in their own country using only Debian packages. The list of modules
8253 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
8254 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
8255 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8256 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8257 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8258 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8259 easier in the future.&lt;/p&gt;
8260
8261 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
8262 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
8263 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
8264 with the responsibility of tracking security problems, which I really
8265 do not have time for.&lt;/p&gt;
8266 </description>
8267 </item>
8268
8269 <item>
8270 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
8271 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
8272 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
8273 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
8274 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
8275 posts have been in Norwegian the last few weeks, so here is a short
8276 update in English.&lt;/p&gt;
8277
8278 &lt;p&gt;The kids still keep me too busy to get much free software work
8279 done, but I did manage to organise a project to get a Norwegian port
8280 of the British service
8281 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8282 and it has been running for a month now. The entire project has been
8283 organised by me and two others. Around Christmas we gathered sponsors
8284 to fund the development work. In January I drafted a contract with
8285 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8286 and in February the development took place. Most of it involved
8287 converting the source to use GPS coordinates instead of British
8288 easting/northing, and the resulting code should be a lot easier to get
8289 running in any country by now. The Norwegian
8290 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8291 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8292 source and the source for administrative borders in Norway, and
8293 support for this had to be added/fixed.&lt;/p&gt;
8294
8295 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8296 polishing the system before we announced it March 7th. The system is
8297 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8298 problem reports in a few weeks. Soon we hope to announce the Android
8299 and iPhone versions making it even easier to report problems with the
8300 public infrastructure.&lt;/p&gt;
8301
8302 &lt;p&gt;Perhaps something to consider for those of you in countries without
8303 such service?&lt;/p&gt;
8304 </description>
8305 </item>
8306
8307 <item>
8308 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8309 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8311 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8312 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8313 issues here at my work with the University of Oslo. My idea is that
8314 it should be possible to use the information about security issues
8315 available on the Internet, and check our locally
8316 maintained/distributed software against this information. It should
8317 allow us to verify that no known security issues are forgotten. The
8318 CVE database listing vulnerabilities seem like a great central point,
8319 and by using the package lists from Debian mapped to CVEs provided by
8320 the testing security team, I believed it should be possible to figure
8321 out which security holes were present in our free software
8322 collection.&lt;/p&gt;
8323
8324 &lt;p&gt;After reading up on the topic, it became obvious that the first
8325 building block is to be able to name software packages in a unique and
8326 consistent way across data sources. I considered several ways to do
8327 this, for example coming up with my own naming scheme like using URLs
8328 to project home pages or URLs to the Freshmeat entries, or using some
8329 existing naming scheme. And it seem like I am not the first one to
8330 come across this problem, as MITRE already proposed and implemented a
8331 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8332 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8333 software, hardware and other platform components. The CPE ids are
8334 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8335 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8336 issues for any CPE name. With this in place, all I need to do is to
8337 locate the CPE id for the software packages we use at the university.
8338 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8339 NVD entry if a CVE for the package exist).&lt;/p&gt;
8340
8341 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8342 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8343 check out, one could look up
8344 &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
8345 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8346 The most recent one is
8347 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8348 and at the bottom of the NVD page for this vulnerability the complete
8349 list of affected versions is provided.&lt;/p&gt;
8350
8351 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8352 for offline processing of issues. Using this dump, I&#39;ve written a
8353 small script taking a list of CPEs as input and list all CVEs
8354 affecting the packages represented by these CPEs. One give it CPEs
8355 with version numbers as specified above and get a list of open
8356 security issues out.&lt;/p&gt;
8357
8358 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8359 information need to be high. For that to happen, I believe as many as
8360 possible need to use and contribute to the NVD database. I notice
8361 RHEL is providing
8362 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8363 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8364 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8365
8366 &lt;p&gt;To get an idea about the quality for free software, I spent some
8367 time making it possible to compare the CVE database from Debian with
8368 the CVE database in NVD. The result look fairly good, but there are
8369 some inconsistencies in NVD (same software package having several
8370 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8371 Debian believe are affected by a CVE). Hope to find time to improve
8372 the quality of NVD, but that require being able to get in touch with
8373 someone maintaining it. So far my three emails with questions and
8374 corrections have not seen any reply, but I hope contact can be
8375 established soon.&lt;/p&gt;
8376
8377 &lt;p&gt;An interesting application for CPEs is cross platform package
8378 mapping. It would be useful to know which packages in for example
8379 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8380 this would be trivial if all linux distributions provided CPE entries
8381 for their packages.&lt;/p&gt;
8382 </description>
8383 </item>
8384
8385 <item>
8386 <title>Which module is loaded for a given PCI and USB device?</title>
8387 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8389 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8390 <description>&lt;p&gt;In the
8391 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8392 package in Debian, there is a script to report useful information
8393 about the running hardware for use when people report missing
8394 information. One part of this script that I find very useful when
8395 debugging hardware problems, is the part mapping loaded kernel module
8396 to the PCI device it claims. It allow me to quickly see if the kernel
8397 module I expect is driving the hardware I am struggling with. To see
8398 the output, make sure discover-data is installed and run
8399 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8400 one of my machines like this:&lt;/p&gt;
8401
8402 &lt;pre&gt;
8403 loaded modules:
8404 10de:03eb i2c_nforce2
8405 10de:03f1 ohci_hcd
8406 10de:03f2 ehci_hcd
8407 10de:03f0 snd_hda_intel
8408 10de:03ec pata_amd
8409 10de:03f6 sata_nv
8410 1022:1103 k8temp
8411 109e:036e bttv
8412 109e:0878 snd_bt87x
8413 11ab:4364 sky2
8414 &lt;/pre&gt;
8415
8416 &lt;p&gt;The code in question look like this, slightly modified for
8417 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8418
8419 &lt;pre&gt;
8420 if [ -d /sys/bus/pci/devices/ ] ; then
8421 echo loaded pci modules:
8422 (
8423 cd /sys/bus/pci/devices/
8424 for address in * ; do
8425 if [ -d &quot;$address/driver/module&quot; ] ; then
8426 module=`cd $address/driver/module ; pwd -P | xargs basename`
8427 if grep -q &quot;^$module &quot; /proc/modules ; then
8428 address=$(echo $address |sed s/0000://)
8429 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8430 echo &quot;$id $module&quot;
8431 fi
8432 fi
8433 done
8434 )
8435 echo
8436 fi
8437 &lt;/pre&gt;
8438
8439 &lt;p&gt;Similar code could be used to extract USB device module
8440 mappings:&lt;/p&gt;
8441
8442 &lt;pre&gt;
8443 if [ -d /sys/bus/usb/devices/ ] ; then
8444 echo loaded usb modules:
8445 (
8446 cd /sys/bus/usb/devices/
8447 for address in * ; do
8448 if [ -d &quot;$address/driver/module&quot; ] ; then
8449 module=`cd $address/driver/module ; pwd -P | xargs basename`
8450 if grep -q &quot;^$module &quot; /proc/modules ; then
8451 address=$(echo $address |sed s/0000://)
8452 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8453 if [ &quot;$id&quot; ] ; then
8454 echo &quot;$id $module&quot;
8455 fi
8456 fi
8457 fi
8458 done
8459 )
8460 echo
8461 fi
8462 &lt;/pre&gt;
8463
8464 &lt;p&gt;This might perhaps be something to include in other tools as
8465 well.&lt;/p&gt;
8466 </description>
8467 </item>
8468
8469 <item>
8470 <title>How to test if a laptop is working with Linux</title>
8471 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8472 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8473 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8474 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8475 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8476 batch of computers will work with Linux. Every year for the last few
8477 years the university have organised shared bid of a few thousand
8478 computers, and this year HP won the bid. Two different desktops and
8479 five different laptops are on the list this year. We in the UNIX
8480 group want to know which one of these computers work well with RHEL
8481 and Ubuntu, the two Linux distributions we currently handle at the
8482 university.&lt;/p&gt;
8483
8484 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8485 perhaps inspire others to test hardware as well. To test, I PXE
8486 install the OS version of choice, and log in as my normal user and run
8487 a few applications and plug in selected pieces of hardware. When
8488 something fail, I make a note about this in the test matrix and move
8489 on. If I have some spare time I try to report the bug to the OS
8490 vendor, but as I only have the machines for a short time, I rarely
8491 have the time to do this for all the problems I find.&lt;/p&gt;
8492
8493 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8494 I perform on a new model.&lt;/p&gt;
8495
8496 &lt;ul&gt;
8497
8498 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8499 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8500 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8501
8502 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8503 installation, X.org is working.&lt;/li&gt;
8504
8505 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8506 package mesa-utils on Ubuntu) and writing down the frames per second
8507 reported by the program.&lt;/li&gt;
8508
8509 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8510 logging in, and if I can hear this the test is successful. If there
8511 are several audio exits on the machine, I try them all and check if
8512 the Gnome/KDE audio mixer can control where to send the sound. I
8513 normally test this by playing
8514 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8515 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8516
8517 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8518 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8519
8520 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8521 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8522
8523 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8524 picture from the v4l device show up.&lt;/li&gt;
8525
8526 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8527 any bluetooth devices are discovered. In my office, I normally see a
8528 few.&lt;/li&gt;
8529
8530 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8531 memory modules lying around, and stick them in and see if Gnome/KDE
8532 notice this.&lt;/li&gt;
8533
8534 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8535 special button work, and if the laptop continue to work after
8536 resume.&lt;/li&gt;
8537
8538 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8539 adjusting background light, switching on/off external video output,
8540 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8541 laptop to laptop, so I just write down which are working and which are
8542 not.&lt;/li&gt;
8543
8544 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8545 acceleration sensors etc. I rarely test these, as I do not know how
8546 to quickly test if they are working or not, so I only document their
8547 existence.&lt;/li&gt;
8548
8549 &lt;/ul&gt;
8550
8551 &lt;p&gt;By now I suspect you are really curious what the test results are
8552 for the HP machines I am testing. I&#39;m not done yet, so I will report
8553 the test results later. For now I can report that HP 8100 Elite work
8554 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8555 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8556 can see, I have most machines left to test. One interesting
8557 observation is that Ubuntu Lucid has almost twice the frame rate than
8558 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8559 </description>
8560 </item>
8561
8562 <item>
8563 <title>Some thoughts on BitCoins</title>
8564 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8565 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8566 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8567 <description>&lt;p&gt;As I continue to explore
8568 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8569 what properties the system have, and how it will be affected by laws
8570 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8571
8572 &lt;p&gt;One interesting thing to note is that since the transactions are
8573 verified using a peer to peer network, all details about a transaction
8574 is known to everyone. This means that if a BitCoin address has been
8575 published like I did with mine in my initial post about BitCoin, it is
8576 possible for everyone to see how many BitCoins have been transfered to
8577 that address. There is even a web service to look at the details for
8578 all transactions. There I can see that my address
8579 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8580 have received 16.06 Bitcoin, the
8581 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8582 address of Simon Phipps have received 181.97 BitCoin and the address
8583 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8584 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8585 every one of you that donated bitcoins to support my activity. The
8586 fact that anyone can see how much money was transfered to a given
8587 address make it more obvious why the BitCoin community recommend to
8588 generate and hand out a new address for each transaction. I&#39;m told
8589 there is no way to track which addresses belong to a given person or
8590 organisation without the person or organisation revealing it
8591 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8592
8593 &lt;p&gt;In Norway, and in most other countries, there are laws and
8594 regulations limiting how much money one can transfer across the border
8595 without declaring it. There are money laundering, tax and accounting
8596 laws and regulations I would expect to apply to the use of BitCoin.
8597 If the Skolelinux foundation
8598 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8599 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8600 normal bank transfers like EFF is doing, how should this be accounted?
8601 Given that it is impossible to know if money can cross the border or
8602 not, should everything or nothing be declared? What exchange rate
8603 should be used when calculating taxes? Would receivers have to pay
8604 income tax if the foundation were to pay Skolelinux contributors in
8605 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8606
8607 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8608 accepted by a lot of users. It must be possible to get easy access to
8609 the currency (as a wage or using currency exchanges), and it must be
8610 easy to spend it. At the moment BitCoin seem fairly easy to get
8611 access to, but there are very few places to spend it. I am not really
8612 a regular user of any of the vendor types currently accepting BitCoin,
8613 so I wonder when my kind of shop would start accepting BitCoins. I
8614 would like to buy electronics, travels and subway tickets, not herbs
8615 and books. :) The currency is young, and this will improve over time
8616 if it become popular, but I suspect regular banks will start to lobby
8617 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8618 will claim it is helping fund terrorism and money laundering (which
8619 probably would be true, as is any currency in existence), but I
8620 believe the problems should be solved elsewhere and not by blaming
8621 currencies.&lt;/p&gt;
8622
8623 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8624 CPU intensive process that depend on a bit of luck as well (as one is
8625 competing against all the other miners currently spending CPU cycles
8626 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8627 BitCoin when this happen. Yesterday I came across the obvious way to
8628 join forces to increase ones changes of getting at least some coins,
8629 by coordinating the work on mining BitCoins across several machines
8630 and people, and sharing the result if one is lucky and get the 50
8631 BitCoins. Check out
8632 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8633 if this sounds interesting. I have not had time to try to set up a
8634 machine to participate there yet, but have seen that running on ones
8635 own for a few days have not yield any BitCoins througth mining
8636 yet.&lt;/p&gt;
8637
8638 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8639 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8640 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8641 it was interesting to read. The arguments presented seem to be
8642 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8643 </description>
8644 </item>
8645
8646 <item>
8647 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8648 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8649 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8650 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8651 <description>&lt;p&gt;With this weeks lawless
8652 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8653 attacks&lt;/a&gt; on Wikileak and
8654 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8655 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8656 not be trusted to handle money transactions.
8657 A blog post from
8658 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8659 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8660 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8661 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8662 some help from my friend to get it all running, and he even handed me
8663 some bitcoins to get started. I even donated a few bitcoins to Simon
8664 for helping me remember BitCoin.&lt;/p&gt;
8665
8666 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8667 crypto-currency, decentralised and handled using peer-to-peer
8668 networks. It allows anonymous transactions and prohibits central
8669 control over the transactions, making it impossible for governments
8670 and companies alike to block donations and other transactions. The
8671 source is free software, and while the key dependency wxWidgets 2.9
8672 for the graphical user interface is missing in Debian, the command
8673 line client builds just fine. Hopefully Jonas
8674 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8675 Debian&lt;/a&gt; soon.&lt;/p&gt;
8676
8677 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8678 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8679 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8680 currency &quot;stock&quot; markets where the exchange rate is decided. There
8681 are not many users so far, but the concept seems promising. If you
8682 want to get started and lack a friend with any bitcoins to spare,
8683 you can even get
8684 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8685 bitcoin at the time of writing). Use
8686 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8687 on the current exchange rates.&lt;/p&gt;
8688
8689 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8690 machines. If you want to support my activity, please send Bitcoin
8691 donations to the address
8692 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8693 </description>
8694 </item>
8695
8696 <item>
8697 <title>Why isn&#39;t Debian Edu using VLC?</title>
8698 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8700 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8701 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8702 presented, and the winner among the multimedia player were VLC.
8703 Personally, I like VLC, and it is my player of choice when I first try
8704 to play a video file or stream. Only if VLC fail will I drag out
8705 gmplayer to see if it can do better. The reason is mostly the failure
8706 model and trust. When VLC fail, it normally pop up a error message
8707 reporting the problem. When mplayer fail, it normally segfault or
8708 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8709
8710 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8711 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8712 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8713 plugin to play web videos seamlessly, and the VLC browser plugin is
8714 not very good. For example, it lack in-line control buttons, so there
8715 is no way for the user to pause the video. Also, when I
8716 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8717 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8718 failed on several video pages where mplayer based plugins worked. If
8719 the browser plugin for VLC was as good as the gecko-mediaplayer
8720 package (which uses mplayer), we would switch.&lt;/P&gt;
8721
8722 &lt;p&gt;While VLC is a good player, its user interface is slightly
8723 annoying. The most annoying feature is its inconsistent use of
8724 keyboard shortcuts. When the player is in full screen mode, its
8725 shortcuts are different from when it is playing the video in a window.
8726 For example, space only work as pause when in full screen mode. I
8727 wish it had consisten shortcuts and that space also would work when in
8728 window mode. Another nice shortcut in gmplayer is [enter] to restart
8729 the current video. It is very nice when playing short videos from the
8730 web and want to restart it when new people arrive to have a look at
8731 what is going on.&lt;/p&gt;
8732 </description>
8733 </item>
8734
8735 <item>
8736 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8737 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8738 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</guid>
8739 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8740 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8741 upgrade testing of the
8742 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8743 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8744 This seem like a very good idea, so I adjusted by test scripts and
8745 can now present the updated result from today:&lt;/p&gt;
8746
8747 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8748
8749 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8750
8751 &lt;blockquote&gt;&lt;p&gt;
8752 apache2.2-bin
8753 aptdaemon
8754 baobab
8755 binfmt-support
8756 browser-plugin-gnash
8757 cheese-common
8758 cli-common
8759 cups-pk-helper
8760 dmz-cursor-theme
8761 empathy
8762 empathy-common
8763 freedesktop-sound-theme
8764 freeglut3
8765 gconf-defaults-service
8766 gdm-themes
8767 gedit-plugins
8768 geoclue
8769 geoclue-hostip
8770 geoclue-localnet
8771 geoclue-manual
8772 geoclue-yahoo
8773 gnash
8774 gnash-common
8775 gnome
8776 gnome-backgrounds
8777 gnome-cards-data
8778 gnome-codec-install
8779 gnome-core
8780 gnome-desktop-environment
8781 gnome-disk-utility
8782 gnome-screenshot
8783 gnome-search-tool
8784 gnome-session-canberra
8785 gnome-system-log
8786 gnome-themes-extras
8787 gnome-themes-more
8788 gnome-user-share
8789 gstreamer0.10-fluendo-mp3
8790 gstreamer0.10-tools
8791 gtk2-engines
8792 gtk2-engines-pixbuf
8793 gtk2-engines-smooth
8794 hamster-applet
8795 libapache2-mod-dnssd
8796 libapr1
8797 libaprutil1
8798 libaprutil1-dbd-sqlite3
8799 libaprutil1-ldap
8800 libart2.0-cil
8801 libboost-date-time1.42.0
8802 libboost-python1.42.0
8803 libboost-thread1.42.0
8804 libchamplain-0.4-0
8805 libchamplain-gtk-0.4-0
8806 libcheese-gtk18
8807 libclutter-gtk-0.10-0
8808 libcryptui0
8809 libdiscid0
8810 libelf1
8811 libepc-1.0-2
8812 libepc-common
8813 libepc-ui-1.0-2
8814 libfreerdp-plugins-standard
8815 libfreerdp0
8816 libgconf2.0-cil
8817 libgdata-common
8818 libgdata7
8819 libgdu-gtk0
8820 libgee2
8821 libgeoclue0
8822 libgexiv2-0
8823 libgif4
8824 libglade2.0-cil
8825 libglib2.0-cil
8826 libgmime2.4-cil
8827 libgnome-vfs2.0-cil
8828 libgnome2.24-cil
8829 libgnomepanel2.24-cil
8830 libgpod-common
8831 libgpod4
8832 libgtk2.0-cil
8833 libgtkglext1
8834 libgtksourceview2.0-common
8835 libmono-addins-gui0.2-cil
8836 libmono-addins0.2-cil
8837 libmono-cairo2.0-cil
8838 libmono-corlib2.0-cil
8839 libmono-i18n-west2.0-cil
8840 libmono-posix2.0-cil
8841 libmono-security2.0-cil
8842 libmono-sharpzip2.84-cil
8843 libmono-system2.0-cil
8844 libmtp8
8845 libmusicbrainz3-6
8846 libndesk-dbus-glib1.0-cil
8847 libndesk-dbus1.0-cil
8848 libopal3.6.8
8849 libpolkit-gtk-1-0
8850 libpt2.6.7
8851 libpython2.6
8852 librpm1
8853 librpmio1
8854 libsdl1.2debian
8855 libsrtp0
8856 libssh-4
8857 libtelepathy-farsight0
8858 libtelepathy-glib0
8859 libtidy-0.99-0
8860 media-player-info
8861 mesa-utils
8862 mono-2.0-gac
8863 mono-gac
8864 mono-runtime
8865 nautilus-sendto
8866 nautilus-sendto-empathy
8867 p7zip-full
8868 pkg-config
8869 python-aptdaemon
8870 python-aptdaemon-gtk
8871 python-axiom
8872 python-beautifulsoup
8873 python-bugbuddy
8874 python-clientform
8875 python-coherence
8876 python-configobj
8877 python-crypto
8878 python-cupshelpers
8879 python-elementtree
8880 python-epsilon
8881 python-evolution
8882 python-feedparser
8883 python-gdata
8884 python-gdbm
8885 python-gst0.10
8886 python-gtkglext1
8887 python-gtksourceview2
8888 python-httplib2
8889 python-louie
8890 python-mako
8891 python-markupsafe
8892 python-mechanize
8893 python-nevow
8894 python-notify
8895 python-opengl
8896 python-openssl
8897 python-pam
8898 python-pkg-resources
8899 python-pyasn1
8900 python-pysqlite2
8901 python-rdflib
8902 python-serial
8903 python-tagpy
8904 python-twisted-bin
8905 python-twisted-conch
8906 python-twisted-core
8907 python-twisted-web
8908 python-utidylib
8909 python-webkit
8910 python-xdg
8911 python-zope.interface
8912 remmina
8913 remmina-plugin-data
8914 remmina-plugin-rdp
8915 remmina-plugin-vnc
8916 rhythmbox-plugin-cdrecorder
8917 rhythmbox-plugins
8918 rpm-common
8919 rpm2cpio
8920 seahorse-plugins
8921 shotwell
8922 software-center
8923 system-config-printer-udev
8924 telepathy-gabble
8925 telepathy-mission-control-5
8926 telepathy-salut
8927 tomboy
8928 totem
8929 totem-coherence
8930 totem-mozilla
8931 totem-plugins
8932 transmission-common
8933 xdg-user-dirs
8934 xdg-user-dirs-gtk
8935 xserver-xephyr
8936 &lt;/p&gt;&lt;/blockquote&gt;
8937
8938 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8939
8940 &lt;blockquote&gt;&lt;p&gt;
8941 cheese
8942 ekiga
8943 eog
8944 epiphany-extensions
8945 evolution-exchange
8946 fast-user-switch-applet
8947 file-roller
8948 gcalctool
8949 gconf-editor
8950 gdm
8951 gedit
8952 gedit-common
8953 gnome-games
8954 gnome-games-data
8955 gnome-nettool
8956 gnome-system-tools
8957 gnome-themes
8958 gnuchess
8959 gucharmap
8960 guile-1.8-libs
8961 libavahi-ui0
8962 libdmx1
8963 libgalago3
8964 libgtk-vnc-1.0-0
8965 libgtksourceview2.0-0
8966 liblircclient0
8967 libsdl1.2debian-alsa
8968 libspeexdsp1
8969 libsvga1
8970 rhythmbox
8971 seahorse
8972 sound-juicer
8973 system-config-printer
8974 totem-common
8975 transmission-gtk
8976 vinagre
8977 vino
8978 &lt;/p&gt;&lt;/blockquote&gt;
8979
8980 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8981
8982 &lt;blockquote&gt;&lt;p&gt;
8983 gstreamer0.10-gnomevfs
8984 &lt;/p&gt;&lt;/blockquote&gt;
8985
8986 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8987
8988 &lt;blockquote&gt;&lt;p&gt;
8989 [nothing]
8990 &lt;/p&gt;&lt;/blockquote&gt;
8991
8992 &lt;p&gt;This is for KDE:&lt;/p&gt;
8993
8994 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8995
8996 &lt;blockquote&gt;&lt;p&gt;
8997 ksmserver
8998 &lt;/p&gt;&lt;/blockquote&gt;
8999
9000 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9001
9002 &lt;blockquote&gt;&lt;p&gt;
9003 kwin
9004 network-manager-kde
9005 &lt;/p&gt;&lt;/blockquote&gt;
9006
9007 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9008
9009 &lt;blockquote&gt;&lt;p&gt;
9010 arts
9011 dolphin
9012 freespacenotifier
9013 google-gadgets-gst
9014 google-gadgets-xul
9015 kappfinder
9016 kcalc
9017 kcharselect
9018 kde-core
9019 kde-plasma-desktop
9020 kde-standard
9021 kde-window-manager
9022 kdeartwork
9023 kdeartwork-emoticons
9024 kdeartwork-style
9025 kdeartwork-theme-icon
9026 kdebase
9027 kdebase-apps
9028 kdebase-workspace
9029 kdebase-workspace-bin
9030 kdebase-workspace-data
9031 kdeeject
9032 kdelibs
9033 kdeplasma-addons
9034 kdeutils
9035 kdewallpapers
9036 kdf
9037 kfloppy
9038 kgpg
9039 khelpcenter4
9040 kinfocenter
9041 konq-plugins-l10n
9042 konqueror-nsplugins
9043 kscreensaver
9044 kscreensaver-xsavers
9045 ktimer
9046 kwrite
9047 libgle3
9048 libkde4-ruby1.8
9049 libkonq5
9050 libkonq5-templates
9051 libnetpbm10
9052 libplasma-ruby
9053 libplasma-ruby1.8
9054 libqt4-ruby1.8
9055 marble-data
9056 marble-plugins
9057 netpbm
9058 nuvola-icon-theme
9059 plasma-dataengines-workspace
9060 plasma-desktop
9061 plasma-desktopthemes-artwork
9062 plasma-runners-addons
9063 plasma-scriptengine-googlegadgets
9064 plasma-scriptengine-python
9065 plasma-scriptengine-qedje
9066 plasma-scriptengine-ruby
9067 plasma-scriptengine-webkit
9068 plasma-scriptengines
9069 plasma-wallpapers-addons
9070 plasma-widget-folderview
9071 plasma-widget-networkmanagement
9072 ruby
9073 sweeper
9074 update-notifier-kde
9075 xscreensaver-data-extra
9076 xscreensaver-gl
9077 xscreensaver-gl-extra
9078 xscreensaver-screensaver-bsod
9079 &lt;/p&gt;&lt;/blockquote&gt;
9080
9081 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9082
9083 &lt;blockquote&gt;&lt;p&gt;
9084 ark
9085 google-gadgets-common
9086 google-gadgets-qt
9087 htdig
9088 kate
9089 kdebase-bin
9090 kdebase-data
9091 kdepasswd
9092 kfind
9093 klipper
9094 konq-plugins
9095 konqueror
9096 ksysguard
9097 ksysguardd
9098 libarchive1
9099 libcln6
9100 libeet1
9101 libeina-svn-06
9102 libggadget-1.0-0b
9103 libggadget-qt-1.0-0b
9104 libgps19
9105 libkdecorations4
9106 libkephal4
9107 libkonq4
9108 libkonqsidebarplugin4a
9109 libkscreensaver5
9110 libksgrd4
9111 libksignalplotter4
9112 libkunitconversion4
9113 libkwineffects1a
9114 libmarblewidget4
9115 libntrack-qt4-1
9116 libntrack0
9117 libplasma-geolocation-interface4
9118 libplasmaclock4a
9119 libplasmagenericshell4
9120 libprocesscore4a
9121 libprocessui4a
9122 libqalculate5
9123 libqedje0a
9124 libqtruby4shared2
9125 libqzion0a
9126 libruby1.8
9127 libscim8c2a
9128 libsmokekdecore4-3
9129 libsmokekdeui4-3
9130 libsmokekfile3
9131 libsmokekhtml3
9132 libsmokekio3
9133 libsmokeknewstuff2-3
9134 libsmokeknewstuff3-3
9135 libsmokekparts3
9136 libsmokektexteditor3
9137 libsmokekutils3
9138 libsmokenepomuk3
9139 libsmokephonon3
9140 libsmokeplasma3
9141 libsmokeqtcore4-3
9142 libsmokeqtdbus4-3
9143 libsmokeqtgui4-3
9144 libsmokeqtnetwork4-3
9145 libsmokeqtopengl4-3
9146 libsmokeqtscript4-3
9147 libsmokeqtsql4-3
9148 libsmokeqtsvg4-3
9149 libsmokeqttest4-3
9150 libsmokeqtuitools4-3
9151 libsmokeqtwebkit4-3
9152 libsmokeqtxml4-3
9153 libsmokesolid3
9154 libsmokesoprano3
9155 libtaskmanager4a
9156 libtidy-0.99-0
9157 libweather-ion4a
9158 libxklavier16
9159 libxxf86misc1
9160 okteta
9161 oxygencursors
9162 plasma-dataengines-addons
9163 plasma-scriptengine-superkaramba
9164 plasma-widget-lancelot
9165 plasma-widgets-addons
9166 plasma-widgets-workspace
9167 polkit-kde-1
9168 ruby1.8
9169 systemsettings
9170 update-notifier-common
9171 &lt;/p&gt;&lt;/blockquote&gt;
9172
9173 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
9174 aptitude a bit more similar, but there are still quite a lott of
9175 differences. I have no idea what packages should be installed after
9176 the upgrade, but hope those that do can have a look.&lt;/p&gt;
9177 </description>
9178 </item>
9179
9180 <item>
9181 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
9182 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
9183 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
9184 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
9185 <description>&lt;p&gt;Most of the computers in use by the
9186 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
9187 are virtual machines. And they have been Xen machines running on a
9188 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
9189 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
9190 bit harder that it could have been, because we set up the Xen virtual
9191 machines to get the virtual partitions from LVM, which as far as I
9192 know is not supported by KVM. So to migrate, we had to convert
9193 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
9194
9195 &lt;p&gt;I found
9196 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
9197 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
9198 migration. It uses qemu-img from the qemu package to make the disk
9199 image, parted to partition it, losetup and kpartx to present the disk
9200 image partions as devices, and dd to copy the data. I NFS mounted the
9201 new servers storage area on the old server to do the migration.&lt;/p&gt;
9202
9203 &lt;pre&gt;
9204 #!/bin/sh
9205
9206 # Based on
9207 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9208
9209 set -e
9210 set -x
9211
9212 if [ -z &quot;$1&quot; ] ; then
9213 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
9214 exit 1
9215 else
9216 host=&quot;$1&quot;
9217 fi
9218
9219 if [ ! -e /dev/vg_data/$host-disk ] ; then
9220 echo &quot;error: unable to find LVM volume for $host&quot;
9221 exit 1
9222 fi
9223
9224 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9225 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9226 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9227 totalsize=$(( ( $disksize + $swapsize ) ))
9228
9229 img=$host.img
9230 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
9231 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9232
9233 parted $img mklabel msdos
9234 parted $img mkpart primary linux-swap 0 $disksize
9235 parted $img mkpart primary ext2 $disksize $totalsize
9236 parted $img set 1 boot on
9237
9238 modprobe dm-mod
9239 losetup /dev/loop0 $img
9240 kpartx -a /dev/loop0
9241
9242 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
9243 fsck.ext3 -f /dev/mapper/loop0p1 || true
9244 mkswap /dev/mapper/loop0p2
9245
9246 kpartx -d /dev/loop0
9247 losetup -d /dev/loop0
9248 &lt;/pre&gt;
9249
9250 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
9251 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
9252
9253 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
9254 the new disk image attached, installed grub-pc and linux-image-686 and
9255 set up grub to boot from the disk image. After this, the KVM machines
9256 seem to work just fine.&lt;/p&gt;
9257 </description>
9258 </item>
9259
9260 <item>
9261 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
9262 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
9263 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
9264 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
9265 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
9266 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9267 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
9268 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
9269
9270 &lt;p&gt;I still do not know what a correct migration should look like, so I
9271 report any differences between apt and aptitude and hope someone else
9272 can see if anything should be changed.&lt;/p&gt;
9273
9274 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9275
9276 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9277
9278 &lt;blockquote&gt;&lt;p&gt;
9279 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9280 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9281 dmz-cursor-theme empathy empathy-common finger
9282 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9283 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9284 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9285 gnome-cards-data gnome-codec-install gnome-core
9286 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9287 gnome-search-tool gnome-session-canberra gnome-spell
9288 gnome-system-log gnome-themes-extras gnome-themes-more
9289 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9290 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9291 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9292 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9293 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9294 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9295 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9296 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9297 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9298 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9299 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9300 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9301 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9302 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9303 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9304 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9305 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9306 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9307 libmono-security2.0-cil libmono-sharpzip2.84-cil
9308 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9309 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9310 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9311 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9312 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9313 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9314 libxalan2-java libxerces2-java media-player-info mesa-utils
9315 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9316 nautilus-sendto-empathy openoffice.org-writer2latex
9317 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9318 python-aptdaemon python-aptdaemon-gtk python-axiom
9319 python-beautifulsoup python-bugbuddy python-clientform
9320 python-coherence python-configobj python-crypto python-cupshelpers
9321 python-cupsutils python-eggtrayicon python-elementtree
9322 python-epsilon python-evolution python-feedparser python-gdata
9323 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9324 python-gtksourceview2 python-httplib2 python-louie python-mako
9325 python-markupsafe python-mechanize python-nevow python-notify
9326 python-opengl python-openssl python-pam python-pkg-resources
9327 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9328 python-tagpy python-twisted-bin python-twisted-conch
9329 python-twisted-core python-twisted-web python-utidylib python-webkit
9330 python-xdg python-zope.interface remmina remmina-plugin-data
9331 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9332 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9333 software-center svgalibg1 system-config-printer-udev
9334 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9335 totem totem-coherence totem-mozilla totem-plugins
9336 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9337 zip
9338 &lt;/p&gt;&lt;/blockquote&gt;
9339
9340 Installed using apt-get, removed with aptitude
9341
9342 &lt;blockquote&gt;&lt;p&gt;
9343 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9344 epiphany-extensions epiphany-gecko evolution-exchange
9345 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9346 gedit-common gnome-app-install gnome-games gnome-games-data
9347 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9348 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9349 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9350 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9351 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9352 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9353 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9354 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9355 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9356 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9357 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9358 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9359 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9360 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9361 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9362 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9363 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9364 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9365 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9366 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9367 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9368 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9369 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9370 sound-juicer swfdec-gnome system-config-printer totem-common
9371 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9372 &lt;/p&gt;&lt;/blockquote&gt;
9373
9374 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9375
9376 &lt;blockquote&gt;&lt;p&gt;
9377 gstreamer0.10-gnomevfs
9378 &lt;/p&gt;&lt;/blockquote&gt;
9379
9380 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9381
9382 &lt;blockquote&gt;&lt;p&gt;
9383 [nothing]
9384 &lt;/p&gt;&lt;/blockquote&gt;
9385
9386 &lt;p&gt;This is for KDE:&lt;/p&gt;
9387
9388 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9389
9390 &lt;blockquote&gt;&lt;p&gt;
9391 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9392 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9393 ghostscript-x git gnome-audio gnugo granatier gs-common
9394 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9395 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9396 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9397 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9398 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9399 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9400 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9401 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9402 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9403 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9404 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9405 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9406 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9407 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9408 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9409 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9410 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9411 libkrossui4 libmailtools-perl libmime-tools-perl
9412 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9413 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9414 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9415 lirc luatex marble networkstatus noatun-plugins
9416 openoffice.org-writer2latex palapeli palapeli-data parley
9417 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9418 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9419 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9420 ttf-sazanami-gothic
9421 &lt;/p&gt;&lt;/blockquote&gt;
9422
9423 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9424
9425 &lt;blockquote&gt;&lt;p&gt;
9426 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9427 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9428 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9429 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9430 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9431 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9432 kitchensync kiten kjumpingcube klatin klettres klickety klines
9433 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9434 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9435 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9436 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9437 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9438 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9439 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9440 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9441 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9442 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9443 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9444 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9445 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9446 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9447 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9448 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9449 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9450 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9451 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9452 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9453 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9454 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9455 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9456 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9457 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9458 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9459 &lt;/p&gt;&lt;/blockquote&gt;
9460
9461 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9462
9463 &lt;blockquote&gt;&lt;p&gt;
9464 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9465 kdeartwork kdebase kdebase-apps kdebase-workspace
9466 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9467 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9468 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9469 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9470 xscreensaver-screensaver-bsod
9471 &lt;/p&gt;&lt;/blockquote&gt;
9472
9473 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9474
9475 &lt;blockquote&gt;&lt;p&gt;
9476 kdebase-bin konq-plugins konqueror
9477 &lt;/p&gt;&lt;/blockquote&gt;
9478 </description>
9479 </item>
9480
9481 <item>
9482 <title>Gnash buildbot slave and Debian kfreebsd</title>
9483 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9484 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9485 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9486 <description>&lt;p&gt;Answering
9487 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9488 call from the Gnash project&lt;/a&gt; for
9489 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9490 current source, I have set up a virtual KVM machine on the Debian
9491 Edu/Skolelinux virtualization host to test the git source on
9492 Debian/Squeeze. I hope this can help the developers in getting new
9493 releases out more often.&lt;/p&gt;
9494
9495 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9496 I have considered setting up a &lt;a
9497 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9498 machine as well. I have also considered using the kfreebsd
9499 architecture in Debian as a file server in NUUG to get access to the 5
9500 TB zfs volume we currently use to store DV video. Because of this, I
9501 finally got around to do a test installation of Debian/Squeeze with
9502 kfreebsd. Installation went fairly smooth, thought I noticed some
9503 visual glitches in the cdebconf dialogs (black cursor left on the
9504 screen at random locations). Have not gotten very far with the
9505 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9506 fatal problem. Have to spend some more time on it to see if it is
9507 useful as a file server for NUUG. Will try to find time to set up a
9508 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9509 </description>
9510 </item>
9511
9512 <item>
9513 <title>Debian in 3D</title>
9514 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9516 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9517 <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;
9518
9519 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9520 3D linked in from
9521 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9522 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9523 </description>
9524 </item>
9525
9526 <item>
9527 <title>Software updates 2010-10-24</title>
9528 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9530 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9531 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9532
9533 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9534 raise money for the project is going well. The lower limit of 10
9535 signers was reached in 24 hours, and so far 13 people have signed it.
9536 More signers and more funding is most welcome, and I am really curious
9537 how far we can get before the time limit of December 24 is reached.
9538 :)&lt;/p&gt;
9539
9540 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9541 about what appear to be a great code coverage tool capable of
9542 generating code coverage stats without any changes to the source code.
9543 It is called
9544 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9545 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9546 It is missing in Debian, but the git source built just fine in Squeeze
9547 after I installed libelf-dev, libdwarf-dev, pkg-config and
9548 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9549 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9550
9551 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9552 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9553 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9554 alpha test release of the Squeeze based Debian Edu /
9555 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9556 release. Give it a try if you need a complete linux solution for your
9557 school, including central infrastructure server, workstations, thin
9558 client servers and diskless workstations. A nice touch added
9559 yesterday is RDP support on the thin client servers, for windows
9560 clients to get a Linux desktop on request.&lt;/p&gt;
9561 </description>
9562 </item>
9563
9564 <item>
9565 <title>Some notes on Flash in Debian and Debian Edu</title>
9566 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9567 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9568 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9569 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9570 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9571 second most popular used package that is missing in Debian. The sixth
9572 most popular is flashplayer-mozilla. This is a clear indication that
9573 working flash is important for Debian users. Around 10 percent of the
9574 users submitting data to popcon.debian.org have this package
9575 installed.&lt;/p&gt;
9576
9577 &lt;p&gt;In the report written by Lars Risan in August 2008
9578&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
9579 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9580 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9581 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9582 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9583 web sites require Flash to work, and lacking working Flash support in
9584 the web browser and the problems with installing it was perceived as a
9585 good reason to stay with Windows.&lt;/p&gt;
9586
9587 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9588 said to be the retarded cousin that did not really understand
9589 everything you told him but could work fairly well. This was a
9590 comment regarding the problems Linux have with proprietary formats and
9591 non-standard web pages, and is sad because it exposes a fairly common
9592 understanding of whose fault it is if web pages that only work in for
9593 example Internet Explorer 6 fail to work on Firefox, and funny because
9594 it explain very well how annoying it is for users when Linux
9595 distributions do not work with the documents they receive or the web
9596 pages they want to visit.&lt;/p&gt;
9597
9598 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9599 and Debian Edu to have a well working Flash implementation in the
9600 distribution, to get at least popular sites as Youtube and Google
9601 Video to working out of the box. For Squeeze, Debian have the chance
9602 to include the latest version of Gnash that will make this happen, as
9603 the new release 0.8.8 was published a few weeks ago and is resting in
9604 unstable. The new version work with more sites that version 0.8.7.
9605 The Gnash maintainers have asked for a freeze exception, but the
9606 release team have not had time to reply to it yet. I hope they agree
9607 with me that Flash is important for the Debian desktop users, and thus
9608 accept the new package into Squeeze.&lt;/p&gt;
9609 </description>
9610 </item>
9611
9612 <item>
9613 <title>Circular package dependencies harms apt recovery</title>
9614 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9615 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9616 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9617 <description>&lt;p&gt;I discovered this while doing
9618 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9619 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9620 in Debian still got circular dependencies, and it is often claimed
9621 that apt and aptitude should be able to handle this just fine, but
9622 some times these dependency loops causes apt to fail.&lt;/p&gt;
9623
9624 &lt;p&gt;An example is from todays
9625 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9626 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9627 causes perl-modules to fail to upgrade. The cause is simple. If a
9628 package fail to unpack, then only part of packages with the circular
9629 dependency might end up being unpacked when unpacking aborts, and the
9630 ones already unpacked will fail to configure in the recovery phase
9631 because its dependencies are unavailable.&lt;/p&gt;
9632
9633 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9634
9635 &lt;blockquote&gt;&lt;pre&gt;
9636 dpkg: dependency problems prevent configuration of perl-modules:
9637 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9638 Version of perl on system is 5.10.0-19lenny2.
9639 dpkg: error processing perl-modules (--configure):
9640 dependency problems - leaving unconfigured
9641 &lt;/pre&gt;&lt;/blockquote&gt;
9642
9643 &lt;p&gt;The perl/perl-modules circular dependency is already
9644 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9645 hopefully be solved as soon as possible, but it is not the only one,
9646 and each one of these loops in the dependency tree can cause similar
9647 failures. Of course, they only occur when there are bugs in other
9648 packages causing the unpacking to fail, but it is rather nasty when
9649 the failure of one package causes the problem to become worse because
9650 of dependency loops.&lt;/p&gt;
9651
9652 &lt;p&gt;Thanks to
9653 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9654 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9655 dependencies
9656 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9657 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9658
9659 &lt;p&gt;Todays testing also exposed a bug in
9660 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9661 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9662 apt-get and aptitude, the latter possibly caused by some circular
9663 dependency. Reported both to BTS to try to get someone to look at
9664 it.&lt;/p&gt;
9665 </description>
9666 </item>
9667
9668 <item>
9669 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9670 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9671 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9672 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9673 <description>&lt;p&gt;This is a
9674 &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;
9675 on my
9676 &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
9677 work&lt;/a&gt; on
9678 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9679 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9680
9681 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9682 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9683 and dhcp3-server-ldap in Debian use the LDAP server. The two
9684 implementations are quite different in how they use LDAP.&lt;/p&gt;
9685
9686 To get this information, I started slapd with debugging enabled and
9687 dumped the debug output to a file to get the LDAP searches performed
9688 on a Debian Edu main-server. Here is a summary.
9689
9690 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9691
9692 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9693 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9694 the web.
9695
9696 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9697 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9698 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9699 reverse entries are in two different subtrees in LDAP with a structure
9700 based on the DNS names, as in tjener.intern and
9701 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9702
9703 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9704 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9705 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9706 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9707 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9708 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9709 forward entries, it is looking for attributes named dnsttl, arecord,
9710 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9711 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9712 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9713 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9714 spfrecord and modifytimestamp. For reverse entries it is looking for
9715 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9716 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9717 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9718 ldapsearch commands could look like this:&lt;/p&gt;
9719
9720 &lt;blockquote&gt;&lt;pre&gt;
9721 ldapsearch -h ldap \
9722 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9723 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9724 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9725 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9726 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9727 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9728
9729 ldapsearch -h ldap \
9730 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9731 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9732 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9733 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9734 srvrecord naptrrecord modifytimestamp
9735 &lt;/pre&gt;&lt;/blockquote&gt;
9736
9737 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9738 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9739 example LDAP objects used there. In addition to these objects, the
9740 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9741 also exist.&lt;/p&gt;
9742
9743 &lt;blockquote&gt;&lt;pre&gt;
9744 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9745 objectclass: top
9746 objectclass: dnsdomain
9747 objectclass: domainrelatedobject
9748 dc: tjener
9749 arecord: 10.0.2.2
9750 associateddomain: tjener.intern
9751
9752 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9753 objectclass: top
9754 objectclass: dnsdomain2
9755 objectclass: domainrelatedobject
9756 dc: 2
9757 ptrrecord: tjener.intern
9758 associateddomain: 2.2.0.10.in-addr.arpa
9759 &lt;/pre&gt;&lt;/blockquote&gt;
9760
9761 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9762 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9763 same base as in the tree mode for a object with filter
9764 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9765 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9766 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9767 naptrrecord and modifytimestamp. For reverse entires it also do a
9768 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9769 and the requested attributes are associateddomain, dnsttl and
9770 modifytimestamp. In short, in strict mode the objects with ptrrecord
9771 go away, and the arecord attribute in the forward object is used
9772 instead.&lt;/p&gt;
9773
9774 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
9775 like this:&lt;/p&gt;
9776
9777 &lt;blockquote&gt;&lt;pre&gt;
9778 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9779 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9780 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9781 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9782 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9783 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9784
9785 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9786 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
9787 &lt;/pre&gt;&lt;/blockquote&gt;
9788
9789 &lt;p&gt;In addition to the forward and reverse searches , there is also a
9790 search for SOA records, which behave similar to the forward and
9791 reverse lookups.&lt;/p&gt;
9792
9793 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
9794 specify any objectclass names, and instead look for the attributes it
9795 need to generate a DNS reply. This make it able to work with any
9796 objectclass that provide the needed attributes.&lt;/p&gt;
9797
9798 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
9799 dnsdomain2 schemas. The latter is used for reverse entries like
9800 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
9801
9802 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
9803 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9804 attributes) and domainrelatedobject (for associatedDomain). The use
9805 of structural object classes make it impossible to combine these
9806 classes with the object classes used by DHCP.&lt;/p&gt;
9807
9808 &lt;p&gt;There are other schemas that could be used too, for example the
9809 dnszone structural object class used by Gosa and bind-sdb for the DNS
9810 attributes combined with the domainrelatedobject object class, but in
9811 this case some unused attributes would have to be included as well
9812 (zonename and relativedomainname).&lt;/p&gt;
9813
9814 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
9815 mode and not use any of the existing objectclasses (dnsdomain,
9816 dnsdomain2 and dnszone) when one want to combine the DNS information
9817 with DHCP information, and instead create a auxiliary object class
9818 defined something like this (using the attributes defined for
9819 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
9820
9821 &lt;blockquote&gt;&lt;pre&gt;
9822 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
9823 SUP top
9824 AUXILIARY
9825 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9826 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9827 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9828 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9829 A6Record $ DNAMERecord
9830 ))
9831 &lt;/pre&gt;&lt;/blockquote&gt;
9832
9833 &lt;p&gt;This will allow any object to become a DNS entry when combined with
9834 the domainrelatedobject object class, and allow any entity to include
9835 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
9836 developers asking for their view on this schema and if they are
9837 interested in providing such schema with PowerDNS, and I hope my
9838 message will be accepted into their mailing list soon.&lt;/p&gt;
9839
9840 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
9841
9842 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
9843 the object attributes, and then uses the attributes it want. This
9844 make it harder to figure out exactly what attributes are used, but
9845 thanks to the working example in Debian Edu I can at least get an idea
9846 what is needed without having to read the source code.&lt;/p&gt;
9847
9848 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
9849 search filter to use to locate the correct dhcpServer entity is
9850 stored. These are the relevant entries from
9851 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
9852
9853 &lt;blockquote&gt;&lt;pre&gt;
9854 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
9855 ldap-dhcp-server-cn &quot;dhcp&quot;;
9856 &lt;/pre&gt;&lt;/blockquote&gt;
9857
9858 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
9859 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
9860 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
9861 search result is this entry:&lt;/p&gt;
9862
9863 &lt;blockquote&gt;&lt;pre&gt;
9864 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9865 cn: dhcp
9866 objectClass: top
9867 objectClass: dhcpServer
9868 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9869 &lt;/pre&gt;&lt;/blockquote&gt;
9870
9871 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
9872 subtree with DHCP configuration. The DHCP configuration subtree base
9873 is located using a base scope search with base &quot;cn=DHCP
9874 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
9875 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
9876 The search result is this entry:&lt;/p&gt;
9877
9878 &lt;blockquote&gt;&lt;pre&gt;
9879 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9880 cn: DHCP Config
9881 objectClass: top
9882 objectClass: dhcpService
9883 objectClass: dhcpOptions
9884 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9885 dhcpStatements: ddns-update-style none
9886 dhcpStatements: authoritative
9887 dhcpOption: smtp-server code 69 = array of ip-address
9888 dhcpOption: www-server code 72 = array of ip-address
9889 dhcpOption: wpad-url code 252 = text
9890 &lt;/pre&gt;&lt;/blockquote&gt;
9891
9892 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
9893 all the DHCP configuration is loaded, it is ready to receive requests.
9894 The subtree in Debian Edu contain objects with object classes
9895 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9896 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9897 and information about netmasks, dynamic range etc. Leaving out the
9898 details here because it is not relevant for the focus of my
9899 investigation, which is to see if it is possible to merge dns and dhcp
9900 related computer objects.&lt;/p&gt;
9901
9902 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
9903 of the client (00:00:00:00:00:00 in this example), using a subtree
9904 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
9905 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9906 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
9907 like:&lt;/p&gt;
9908
9909 &lt;blockquote&gt;&lt;pre&gt;
9910 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9911 cn: hostname
9912 objectClass: top
9913 objectClass: dhcpHost
9914 dhcpHWAddress: ethernet 00:00:00:00:00:00
9915 dhcpStatements: fixed-address hostname
9916 &lt;/pre&gt;&lt;/blockquote&gt;
9917
9918 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
9919 The object classes need to have fixed names, and the configuration
9920 need to be stored in a fairly specific LDAP structure. On the
9921 positive side, the invidiual dhcpHost entires can be anywhere without
9922 the DN pointed to by the dhcpServer entries. The latter should make
9923 it possible to group all host entries in a subtree next to the
9924 configuration entries, and this subtree can also be shared with the
9925 DNS server if the schema proposed above is combined with the dhcpHost
9926 structural object class.
9927
9928 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
9929
9930 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
9931 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
9932 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
9933 allowing DNS objects to be stored anywhere under the base cn specified
9934 in the configuration.&lt;/p&gt;
9935
9936 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
9937 regarding which LDAP schemas to use and which LDAP structure to use.
9938 I guess one could implement ones own schema, as long as the
9939 objectclasses and attributes have the names used, but this do not
9940 really help when the DHCP subtree need to have a fairly fixed
9941 structure.&lt;/p&gt;
9942
9943 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
9944 this might work for Debian Edu:&lt;/p&gt;
9945
9946 &lt;blockquote&gt;&lt;pre&gt;
9947 ou=services
9948 cn=machine-info (dhcpService) - dhcpServiceDN points here
9949 cn=dhcp (dhcpServer)
9950 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9951 cn=10.0.2.0 (dhcpSubnet)
9952 cn=group1 (dhcpGroup/dhcpOptions)
9953 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9954 cn=192.168.0.0 (dhcpSubnet)
9955 cn=group1 (dhcpGroup/dhcpOptions)
9956 ou=machines - PowerDNS base points here
9957 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9958 &lt;/pre&gt;&lt;/blockquote&gt;
9959
9960 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
9961 entries to be in the dhcpGroup subtrees, the entries can be stored
9962 there instead of a common machines subtree, and the PowerDNS base
9963 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
9964
9965 &lt;p&gt;The combined object under the machines subtree would look something
9966 like this:&lt;/p&gt;
9967
9968 &lt;blockquote&gt;&lt;pre&gt;
9969 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9970 dc: hostname
9971 objectClass: top
9972 objectClass: dhcpHost
9973 objectclass: domainrelatedobject
9974 objectclass: dnsDomainAux
9975 associateddomain: hostname.intern
9976 arecord: 10.11.12.13
9977 dhcpHWAddress: ethernet 00:00:00:00:00:00
9978 dhcpStatements: fixed-address hostname.intern
9979 &lt;/pre&gt;&lt;/blockquote&gt;
9980
9981 &lt;/p&gt;One could even add the LTSP configuration associated with a given
9982 machine, as long as the required attributes are available in a
9983 auxiliary object class.&lt;/p&gt;
9984 </description>
9985 </item>
9986
9987 <item>
9988 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
9989 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
9990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
9991 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
9992 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
9993 DHCP services in Debian Edu to use the same LDAP objects for a given
9994 computer, to avoid the possibility of having a inconsistent state for
9995 a computer in LDAP (as in DHCP but no DNS entry or the other way
9996 around) and make it easier to add computers to LDAP.&lt;/p&gt;
9997
9998 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
9999 information finally found a solution that seem to work.&lt;/p&gt;
10000
10001 &lt;p&gt;The old setup required three LDAP objects for a given computer.
10002 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10003 we switch powerdns to use its strict LDAP method (ldap-method=strict
10004 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10005 merged into one while making it impossible to transfer the reverse map
10006 to a slave DNS server.&lt;/p&gt;
10007
10008 &lt;p&gt;If we also replace the object class used to get the DNS related
10009 attributes to one allowing these attributes to be combined with the
10010 dhcphost object class, we can merge the DNS and DHCP entries into one.
10011 I&#39;ve written such object class in the dnsdomainaux.schema file (need
10012 proper OIDs, but that is a minor issue), and tested the setup. It
10013 seem to work.&lt;/p&gt;
10014
10015 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
10016 for both DNS and DHCP, and even the LTSP configuration I suggested in
10017 an earlier email. The combined LDAP object will look something like
10018 this:&lt;/p&gt;
10019
10020 &lt;blockquote&gt;&lt;pre&gt;
10021 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10022 cn: hostname
10023 objectClass: dhcphost
10024 objectclass: domainrelatedobject
10025 objectclass: dnsdomainaux
10026 associateddomain: hostname.intern
10027 arecord: 10.11.12.13
10028 dhcphwaddress: ethernet 00:00:00:00:00:00
10029 dhcpstatements: fixed-address hostname
10030 ldapconfigsound: Y
10031 &lt;/pre&gt;&lt;/blockquote&gt;
10032
10033 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
10034 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10035 before asking DNS to resolve the fixed-adddress. LTSP will use
10036 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
10037
10038 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
10039 dhcphost in a different location, to allow us to put the objects
10040 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
10041 that. If I can&#39;t figure out a way to do that, we can still get rid of
10042 the hosts subtree and move all its content into the DHCP Config tree
10043 (which probably should be renamed to be more related to the new
10044 content. I suspect cn=dnsdhcp,ou=services or something like that
10045 might be a good place to put it.&lt;/p&gt;
10046
10047 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10048 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10049 </description>
10050 </item>
10051
10052 <item>
10053 <title>Idea for storing LTSP configuration in LDAP</title>
10054 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
10055 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
10056 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
10057 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
10058 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10059 clients, and that this can be used to fetch configuration from LDAP if
10060 Debian Edu choose to store configuration there.&lt;/p&gt;
10061
10062 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
10063 to get configuration from LDAP. The idea is to look up the MAC
10064 address of the client in LDAP, and look for attributes on the form
10065 ltspconfigsetting=value, and use this to export SETTING=value to the
10066 LTSP clients.&lt;/p&gt;
10067
10068 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
10069 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
10070 allowing us to store all information about a computer in one place.&lt;/p&gt;
10071
10072 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
10073 this approach. A real LDAP schema for the ltspClientAux objectclass
10074 need to be written. Comments, suggestions, etc?&lt;/p&gt;
10075
10076 &lt;blockquote&gt;&lt;pre&gt;
10077 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10078 #
10079 # Fetch LTSP client settings from LDAP based on MAC address
10080 #
10081 # Uses ethernet address as stored in the dhcpHost objectclass using
10082 # the dhcpHWAddress attribute or ethernet address stored in the
10083 # ieee802Device objectclass with the macAddress attribute.
10084 #
10085 # This module is written to be schema agnostic, and only depend on the
10086 # existence of attribute names.
10087 #
10088 # The LTSP configuration variables are saved directly using a
10089 # ltspConfig prefix and uppercasing the rest of the attribute name.
10090 # To set the SERVER variable, set the ltspConfigServer attribute.
10091 #
10092 # Some LDAP schema should be created with all the relevant
10093 # configuration settings. Something like this should work:
10094 #
10095 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
10096 # SUP top
10097 # AUXILIARY
10098 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10099
10100 LDAPSERVER=$(debian-edu-ldapserver)
10101 if [ &quot;$LDAPSERVER&quot; ] ; then
10102 LDAPBASE=$(debian-edu-ldapserver -b)
10103 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
10104 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
10105 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
10106 grep &#39;^ltspConfig&#39; | while read attr value ; do
10107 # Remove prefix and convert to upper case
10108 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
10109 # bass value on to clients
10110 eval &quot;$attr=$value; export $attr&quot;
10111 done
10112 done
10113 fi
10114 &lt;/pre&gt;&lt;/blockquote&gt;
10115
10116 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
10117 the while block might end up in a subshell causing the variables set
10118 there to not show up in ltsp-config, but if that is the case I am sure
10119 the code can be restructured to make sure the variables are passed on.
10120 I expect that can be solved with some testing. :)&lt;/p&gt;
10121
10122 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10123 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10124
10125 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
10126 configuration in LDAP that was created around year 2000 by
10127 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
10128 Xperience, Inc., 2000&lt;/a&gt;. I found its
10129 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
10130 personal home page over at redhat.com.&lt;/p&gt;
10131 </description>
10132 </item>
10133
10134 <item>
10135 <title>jXplorer, a very nice LDAP GUI</title>
10136 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
10137 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
10138 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
10139 <description>&lt;p&gt;Since
10140 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
10141 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
10142 LDAP GUI that is even better than luma. The java application
10143 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
10144 moving LDAP objects and subtrees using drag-and-drop, and can
10145 authenticate using Kerberos. I have only tested the Kerberos
10146 authentication, but do not have a LDAP setup allowing me to rewrite
10147 LDAP with my test user yet. It is
10148 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
10149 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
10150 have with it is how it handle errors. If something go wrong, its
10151 non-intuitive behaviour require me to go through some query work list
10152 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
10153 </description>
10154 </item>
10155
10156 <item>
10157 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
10158 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
10159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
10160 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
10161 <description>&lt;p&gt;Here is a short update on my &lt;a
10162 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
10163 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
10164 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
10165 not reporting the status for KDE, because the upgrade crashes when
10166 aptitude try because of missing conflicts
10167 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
10168 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
10169
10170 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
10171 complete list of the installed packages. Based on this I see these
10172 differences when I did a test run today. As usual, I do not really
10173 know what the correct set of packages would be, but thought it best to
10174 publish the difference.&lt;/p&gt;
10175
10176 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10177
10178 &lt;blockquote&gt;&lt;p&gt;
10179 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
10180 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
10181 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10182 libgtksourceview-common libpt-1.10.10-plugins-alsa
10183 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10184 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10185 python-4suite-xml python-eggtrayicon python-gtkhtml2
10186 python-gtkmozembed svgalibg1 xserver-xephyr zip
10187 &lt;/p&gt;&lt;/blockquote&gt;
10188
10189 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10190
10191 &lt;blockquote&gt;&lt;p&gt;
10192 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10193 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10194 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
10195 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
10196 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
10197 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
10198 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10199 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10200 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10201 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
10202 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
10203 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
10204 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10205 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
10206 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10207 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
10208 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
10209 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10210 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10211 mysql-common swfdec-gnome totem-gstreamer wodim
10212 &lt;/p&gt;&lt;/blockquote&gt;
10213
10214 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10215
10216 &lt;blockquote&gt;&lt;p&gt;
10217 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10218 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10219 xserver-xorg-input-all xserver-xorg-input-evdev
10220 xserver-xorg-input-kbd xserver-xorg-input-mouse
10221 xserver-xorg-input-synaptics xserver-xorg-video-all
10222 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10223 xserver-xorg-video-chips xserver-xorg-video-cirrus
10224 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10225 xserver-xorg-video-glint xserver-xorg-video-i128
10226 xserver-xorg-video-i740 xserver-xorg-video-mach64
10227 xserver-xorg-video-mga xserver-xorg-video-neomagic
10228 xserver-xorg-video-nouveau xserver-xorg-video-nv
10229 xserver-xorg-video-r128 xserver-xorg-video-radeon
10230 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10231 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10232 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10233 xserver-xorg-video-sis xserver-xorg-video-sisusb
10234 xserver-xorg-video-tdfx xserver-xorg-video-tga
10235 xserver-xorg-video-trident xserver-xorg-video-tseng
10236 xserver-xorg-video-vesa xserver-xorg-video-vmware
10237 xserver-xorg-video-voodoo
10238 &lt;/p&gt;&lt;/blockquote&gt;
10239
10240 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10241
10242 &lt;blockquote&gt;&lt;p&gt;
10243 deskbar-applet xserver-xorg xserver-xorg-core
10244 xserver-xorg-input-wacom xserver-xorg-video-intel
10245 xserver-xorg-video-openchrome
10246 &lt;/p&gt;&lt;/blockquote&gt;
10247
10248 &lt;p&gt;I was told on IRC that the xorg-xserver package was
10249 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
10250 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
10251 No idea when it hits Squeeze, but when it does I hope it will reduce
10252 the difference somewhat.
10253 </description>
10254 </item>
10255
10256 <item>
10257 <title>LUMA, a very nice LDAP GUI</title>
10258 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
10259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
10260 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
10261 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
10262 directory in Debian Edu, and in the process I started to miss a GUI
10263 tool to browse the LDAP tree. The only one I was able to find in
10264 Debian/Squeeze and Lenny is
10265 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
10266 be a great tool to get a overview of the current LDAP directory
10267 populated by default in Skolelinux. Thanks to it, I have been able to
10268 find empty and obsolete subtrees, misplaced objects and duplicate
10269 objects. It will be installed by default in Debian/Squeeze. If you
10270 are working with LDAP, give it a go. :)&lt;/p&gt;
10271
10272 &lt;p&gt;I did notice one problem with it I have not had time to report to
10273 the BTS yet. There is no .desktop file in the package, so the tool do
10274 not show up in the Gnome and KDE menus, but only deep down in in the
10275 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10276 released.&lt;/p&gt;
10277
10278 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10279 like to move objects and remove subtrees directly in the GUI, but have
10280 not found a way to do that with LUMA yet. So in the mean time, I use
10281 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10282
10283 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10284 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10285
10286 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10287 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10288 useful GUI alternative. It seem like a good tool, but is unmaintained
10289 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10290 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10291 </description>
10292 </item>
10293
10294 <item>
10295 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10296 <link>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</link>
10297 <guid isPermaLink="true">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</guid>
10298 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10299 <description>&lt;p&gt;A while back, I
10300 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10301 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10302 for storing DNS and DHCP information in LDAP to combine the two sets
10303 of information into one LDAP object representing a computer.&lt;/p&gt;
10304
10305 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10306 the dhcpHost object class auxiliary, to allow it to be combined with
10307 the dNSDomain object class, and thus forming one object for one
10308 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10309
10310 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10311 without also changing the assigned number for the object class, and I
10312 do not know enough about LDAP schema design to do that properly for
10313 Debian Edu.&lt;/p&gt;
10314
10315 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10316 the
10317 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10318 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10319 available today from IETF.&lt;/p&gt;
10320
10321 &lt;pre&gt;
10322 --- dhcp.schema (revision 65192)
10323 +++ dhcp.schema (working copy)
10324 @@ -376,7 +376,7 @@
10325 objectclass ( 2.16.840.1.113719.1.203.6.6
10326 NAME &#39;dhcpHost&#39;
10327 DESC &#39;This represents information about a particular client&#39;
10328 - SUP top
10329 + SUP top AUXILIARY
10330 MUST cn
10331 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10332 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10333 &lt;/pre&gt;
10334
10335 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10336 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10337 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10338
10339 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10340 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10341 </description>
10342 </item>
10343
10344 <item>
10345 <title>Calling tasksel like the installer, while still getting useful output</title>
10346 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10347 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10348 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10349 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10350 installs packages during the normal debian-installer run. Until now,
10351 I have ended up letting tasksel do the work, with the annoying problem
10352 of not getting any feedback at all when something fails (like a
10353 conffile question from dpkg or a download that fails), using code like
10354 this:
10355
10356 &lt;blockquote&gt;&lt;pre&gt;
10357 export DEBIAN_FRONTEND=noninteractive
10358 tasksel --new-install
10359 &lt;/pre&gt;&lt;/blockquote&gt;
10360
10361 This would invoke tasksel, let its automatic task selection pick the
10362 tasks to install, and continue to install the requested tasks without
10363 any output what so ever.
10364
10365 Recently I revisited this problem while working on the automatic
10366 package upgrade testing, because tasksel would some times hang without
10367 any useful feedback, and I want to see what is going on when it
10368 happen. Then it occured to me, I can parse the output from tasksel
10369 when asked to run in test mode, and use that aptitude command line
10370 printed by tasksel then to simulate the tasksel run. I ended up using
10371 code like this:
10372
10373 &lt;blockquote&gt;&lt;pre&gt;
10374 export DEBIAN_FRONTEND=noninteractive
10375 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10376 $cmd
10377 &lt;/pre&gt;&lt;/blockquote&gt;
10378
10379 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10380 --without-recommends -o APT::Install-Recommends=no -y install
10381 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10382 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10383 laptop task and all packages with priority standard , required and
10384 important, just like tasksel would have done it during
10385 installation.&lt;/p&gt;
10386
10387 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10388 install packages without using debconf-apt-progress, for use cases
10389 like this.&lt;/p&gt;
10390 </description>
10391 </item>
10392
10393 <item>
10394 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10395 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10397 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10398 <description>&lt;p&gt;My
10399 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10400 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10401 finally made the upgrade logs available from
10402 &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;.
10403 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10404 apt and aptitude, and found their differences interesting. This time
10405 I will only focus on their removal plans.&lt;/p&gt;
10406
10407 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10408 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10409 surprising part is that it want to remove xorg and all
10410 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10411 sure why. When asking aptitude to do the same, it want to remove 129
10412 packages, but most of them are library packages I suspect are no
10413 longer needed. Both of them want to remove bluetooth packages, which
10414 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10415
10416 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10417 which seem like a bad idea and xorg the same way as with Gnome. Asking
10418 aptitude for the same, it wants to remove 192 packages, none which are
10419 too surprising.&lt;/p&gt;
10420
10421 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10422 and avoided, and perhaps others as well. Here are the complete list
10423 of planned removals. The complete logs is available from the URL
10424 above. Note if you want to repeat these tests, that the upgrade test
10425 for kde+apt-get hung in the tasksel setup because of dpkg asking
10426 conffile questions. No idea why. I worked around it by using
10427 &#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
10428 continue.&lt;/p&gt;
10429
10430 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10431 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10432 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10433 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10434 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10435 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10436 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10437 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10438 xserver-xorg-input-kbd xserver-xorg-input-mouse
10439 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10440 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10441 xserver-xorg-video-ati xserver-xorg-video-chips
10442 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10443 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10444 xserver-xorg-video-glint xserver-xorg-video-i128
10445 xserver-xorg-video-i740 xserver-xorg-video-imstt
10446 xserver-xorg-video-intel xserver-xorg-video-mach64
10447 xserver-xorg-video-mga xserver-xorg-video-neomagic
10448 xserver-xorg-video-nsc xserver-xorg-video-nv
10449 xserver-xorg-video-openchrome xserver-xorg-video-r128
10450 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10451 xserver-xorg-video-rendition xserver-xorg-video-s3
10452 xserver-xorg-video-s3virge xserver-xorg-video-savage
10453 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10454 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10455 xserver-xorg-video-tga xserver-xorg-video-trident
10456 xserver-xorg-video-tseng xserver-xorg-video-v4l
10457 xserver-xorg-video-vesa xserver-xorg-video-vga
10458 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10459 xulrunner-1.9-gnome-support&lt;/p&gt;
10460
10461 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10462
10463 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10464 djvulibre-desktop finger gnome-app-install gnome-mount
10465 gnome-network-admin gnome-spell gnome-vfs-obexftp
10466 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10467 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10468 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10469 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10470 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10471 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10472 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10473 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10474 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10475 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10476 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10477 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10478 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10479 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10480 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10481 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10482 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10483 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10484 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10485 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10486 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10487 openoffice.org-writer2latex openssl-blacklist p7zip
10488 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10489 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10490 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10491 swfdec-mozilla totem-gstreamer update-manager wodim
10492 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10493 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10494 zip&lt;/p&gt;
10495
10496 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10497
10498 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10499 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10500 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10501 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10502 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10503 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10504 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10505 xserver-xorg-input-kbd xserver-xorg-input-mouse
10506 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10507 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10508 xserver-xorg-video-ati xserver-xorg-video-chips
10509 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10510 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10511 xserver-xorg-video-glint xserver-xorg-video-i128
10512 xserver-xorg-video-i740 xserver-xorg-video-imstt
10513 xserver-xorg-video-intel xserver-xorg-video-mach64
10514 xserver-xorg-video-mga xserver-xorg-video-neomagic
10515 xserver-xorg-video-nsc xserver-xorg-video-nv
10516 xserver-xorg-video-openchrome xserver-xorg-video-r128
10517 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10518 xserver-xorg-video-rendition xserver-xorg-video-s3
10519 xserver-xorg-video-s3virge xserver-xorg-video-savage
10520 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10521 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10522 xserver-xorg-video-tga xserver-xorg-video-trident
10523 xserver-xorg-video-tseng xserver-xorg-video-v4l
10524 xserver-xorg-video-vesa xserver-xorg-video-vga
10525 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10526
10527 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10528 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10529 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10530 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10531 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10532 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10533 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10534 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10535 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10536 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10537 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10538 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10539 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10540 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10541 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10542 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10543 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10544 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10545 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10546 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10547 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10548 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10549 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10550 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10551 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10552 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10553 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10554 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10555 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10556 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10557 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10558 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10559 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10560 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10561 texlive-common texlive-doc-base texlive-fonts-recommended
10562 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10563 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10564 xulrunner-1.9&lt;/p&gt;
10565
10566 </description>
10567 </item>
10568
10569 <item>
10570 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10571 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10573 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10574 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10575 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10576 have been discovered and reported in the process
10577 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10578 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10579 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10580 kdebase-workspace-data), and to get a more regular testing going on, I
10581 am working on a script to automate the test.&lt;/p&gt;
10582
10583 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10584 Gnome or KDE desktop installation inside the chroot before upgrading
10585 it. To ensure no services are started in the chroot, a policy-rc.d
10586 script is inserted. To make sure tasksel believe it is to install a
10587 desktop on a laptop, the tasksel tests are replaced in the chroot
10588 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10589
10590 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10591 currently always fail because udev refuses to upgrade with the kernel
10592 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10593 is created. The bug report
10594 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10595 this problem do not trigger in a chroot, but I touch the file anyway
10596 to make sure the upgrade go well. Testing on virtual and real
10597 hardware have failed me because of udev so far, and creating this file
10598 do the trick in such settings anyway. This is a
10599 &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
10600 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10601 maintainer because he lack the resources to rewrite udev to keep
10602 working with old kernels or something like that. I really wish the
10603 udev upstream would keep udev backwards compatible, to avoid such
10604 upgrade problem, but given that they fail to do so, I guess
10605 documenting the way out of this mess is the best option we got for
10606 Debian Squeeze.&lt;/p&gt;
10607
10608 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10609 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10610 trick:&lt;/p&gt;
10611
10612 &lt;blockquote&gt;&lt;pre&gt;
10613 #!/bin/sh
10614 set -ex
10615
10616 if [ &quot;$1&quot; ] ; then
10617 desktop=$1
10618 else
10619 desktop=gnome
10620 fi
10621
10622 from=lenny
10623 to=squeeze
10624
10625 exec &amp;lt; /dev/null
10626 unset LANG
10627 mirror=http://ftp.skolelinux.org/debian
10628 tmpdir=chroot-$from-upgrade-$to-$desktop
10629 fuser -mv .
10630 debootstrap $from $tmpdir $mirror
10631 chroot $tmpdir aptitude update
10632 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10633 #!/bin/sh
10634 exit 101
10635 EOF
10636 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10637 exit_cleanup() {
10638 umount $tmpdir/proc
10639 }
10640 mount -t proc proc $tmpdir/proc
10641 # Make sure proc is unmounted also on failure
10642 trap exit_cleanup EXIT INT
10643
10644 chroot $tmpdir aptitude -y install debconf-utils
10645
10646 # Make sure tasksel autoselection trigger. It need the test scripts
10647 # to return the correct answers.
10648 echo tasksel tasksel/desktop multiselect $desktop | \
10649 chroot $tmpdir debconf-set-selections
10650
10651 # Include the desktop and laptop task
10652 for test in desktop laptop ; do
10653 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10654 #!/bin/sh
10655 exit 2
10656 EOF
10657 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10658 done
10659
10660 DEBIAN_FRONTEND=noninteractive
10661 DEBIAN_PRIORITY=critical
10662 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10663 chroot $tmpdir tasksel --new-install
10664
10665 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10666 chroot $tmpdir aptitude update
10667 touch $tmpdir/etc/udev/kernel-upgrade
10668 chroot $tmpdir aptitude -y dist-upgrade
10669 fuser -mv
10670 &lt;/pre&gt;&lt;/blockquote&gt;
10671
10672 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10673 with aptitude, but I have not had time to look at how they behave
10674 differently so far. I hope to get a cron job running to do the test
10675 regularly and post the result on the web. The Gnome upgrade currently
10676 work, while the KDE upgrade fail because of the bug in
10677 kdebase-workspace-data&lt;/p&gt;
10678
10679 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10680 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10681 post, so I will refrain from trying. I can report that for Gnome,
10682 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10683 remove and 1 not upgraded and 1024MB need to be downloaded while for
10684 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10685 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10686
10687 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10688 is able to migrate to dependency based boot sequencing and parallel
10689 booting without a hitch. Was unsure if there were still bugs with
10690 packages failing to clean up their obsolete init.d script during
10691 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10692 packages.&lt;/p&gt;
10693 </description>
10694 </item>
10695
10696 <item>
10697 <title>Upstart or sysvinit - as init.d scripts see it</title>
10698 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10700 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10701 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10702 scripts to migrate (some of) their operations to upstart job while
10703 keeping the init.d for hurd and kfreebsd. The packages with such
10704 needs will need a way to get their init.d scripts to behave
10705 differently when used with sysvinit and with upstart. Because of
10706 this, I had a look at the environment variables set when a init.d
10707 script is running under upstart, and when it is not.&lt;/p&gt;
10708
10709 &lt;p&gt;With upstart, I notice these environment variables are set when a
10710 script is started from rcS.d/ (ignoring some irrelevant ones like
10711 COLUMNS):&lt;/p&gt;
10712
10713 &lt;blockquote&gt;&lt;pre&gt;
10714 DEFAULT_RUNLEVEL=2
10715 previous=N
10716 PREVLEVEL=
10717 RUNLEVEL=
10718 runlevel=S
10719 UPSTART_EVENTS=startup
10720 UPSTART_INSTANCE=
10721 UPSTART_JOB=rc-sysinit
10722 &lt;/pre&gt;&lt;/blockquote&gt;
10723
10724 &lt;p&gt;With sysvinit, these environment variables are set for the same
10725 script.&lt;/p&gt;
10726
10727 &lt;blockquote&gt;&lt;pre&gt;
10728 INIT_VERSION=sysvinit-2.88
10729 previous=N
10730 PREVLEVEL=N
10731 RUNLEVEL=S
10732 runlevel=S
10733 &lt;/pre&gt;&lt;/blockquote&gt;
10734
10735 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10736 sysvinit are not set by upstart. Not sure if it is intentional or not
10737 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10738
10739 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10740 looking for the UPSTART_JOB environment variable seem to be a good
10741 choice.&lt;/p&gt;
10742 </description>
10743 </item>
10744
10745 <item>
10746 <title>A manual for standards wars...</title>
10747 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10748 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10749 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10750 <description>&lt;p&gt;Via the
10751 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10752 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10753 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10754 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10755 following the standards wars of today.&lt;/p&gt;
10756 </description>
10757 </item>
10758
10759 <item>
10760 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10761 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10763 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10764 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10765 to get a list of the machine types in use thanks to the DMI
10766 information extracted from each machine. The script to do so is
10767 included in the sitesummary package, and here is example output from
10768 the Skolelinux build servers:&lt;/p&gt;
10769
10770 &lt;blockquote&gt;&lt;pre&gt;
10771 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10772 vendor count
10773 Dell Computer Corporation 1
10774 PowerEdge 1750 1
10775 IBM 1
10776 eserver xSeries 345 -[8670M1X]- 1
10777 Intel 2
10778 [no-dmi-info] 3
10779 maintainer:~#
10780 &lt;/pre&gt;&lt;/blockquote&gt;
10781
10782 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
10783 provided in each machine. Here there are Intel machines without model
10784 information listed with Intel as vendor and no model, and virtual Xen
10785 machines listed as [no-dmi-info]. One can add -l as a command line
10786 option to list the individual machines.&lt;/p&gt;
10787
10788 &lt;p&gt;A larger list is
10789 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
10790 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
10791 provide the basic sitesummary report publicly. In their report there
10792 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
10793 their machines, and as sitesummary is available in both distributions,
10794 it is trivial to get all of them to report to the same central
10795 collector.&lt;/p&gt;
10796 </description>
10797 </item>
10798
10799 <item>
10800 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
10801 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
10802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</guid>
10803 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
10804 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
10805 start at boot when an NVidia video card is used is handled. The
10806 problem seem to be that the nvidia X.org driver uses a long time to
10807 initialize, and this duration is longer than kdm is configured to
10808 wait.&lt;/p&gt;
10809
10810 &lt;p&gt;I came across two bugs related to this issue,
10811 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
10812 against initscripts and passed on to nvidia-glx when it became obvious
10813 that the nvidia drivers were involved, and
10814 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
10815 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
10816
10817 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
10818 problem nvidia video card owners experience and make sure the Debian
10819 distribution work out of the box for these users. The nvidia driver
10820 maintainers expect kdm to be set up to wait longer, while kdm expect
10821 the nvidia driver maintainers to fix the driver to start faster, and
10822 while they wait for each other I guess the users end up switching to a
10823 distribution that work for them. I have no idea what the solution is,
10824 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
10825
10826 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
10827 </description>
10828 </item>
10829
10830 <item>
10831 <title>Parallellized boot seem to hold up well in Debian/testing</title>
10832 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
10833 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
10834 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
10835 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
10836 The feature seem to hold up pretty well, but three fairly serious
10837 issues are known and should be solved:
10838
10839 &lt;p&gt;&lt;ul&gt;
10840
10841 &lt;li&gt;The wicd package seen to
10842 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
10843 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
10844 parallel booting is enabled. No idea why, but the wicd maintainer
10845 seem to be on the case.&lt;/li&gt;
10846
10847 &lt;li&gt;The nvidia X driver seem to
10848 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
10849 triggered more easily when parallel booting is in effect. The
10850 maintainer is on the case.&lt;/li&gt;
10851
10852 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
10853 sequencing (the shutdown is broken) when old file-rc users
10854 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
10855 sysv-rc. One way to solve it would be for file-rc to create
10856 /etc/init.d/.legacy-bootordering, and another is to try to make
10857 sysv-rc more robust. Will investigate some more and probably upload a
10858 workaround in sysv-rc to help those trying to move from file-rc to
10859 sysv-rc get a working shutdown.&lt;/li&gt;
10860
10861 &lt;/ul&gt;&lt;/p&gt;
10862
10863 &lt;p&gt;All in all not many surprising issues, and all of them seem
10864 solvable before Squeeze is released. In addition to these there are
10865 some packages with bugs in their dependencies and run level settings,
10866 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
10867
10868 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10869 the BTS, please usertag the report to get it to show up at
10870 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10871 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10872
10873 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
10874 </description>
10875 </item>
10876
10877 <item>
10878 <title>More flexible firmware handling in debian-installer</title>
10879 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
10880 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
10881 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
10882 <description>&lt;p&gt;After a long break from debian-installer development, I finally
10883 found time today to return to the project. Having to spend less time
10884 working dependency based boot in debian, as it is almost complete now,
10885 definitely helped freeing some time.&lt;/p&gt;
10886
10887 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
10888 include some firmware packages on the Debian Edu CDs, those needed to
10889 get disk and network controllers working. Without having these
10890 firmware packages available during installation, it is impossible to
10891 install Debian Edu on the given machine, and because our target group
10892 are non-technical people, asking them to provide firmware packages on
10893 an external medium is a support pain. Initially, I expected it to be
10894 enough to include the firmware packages on the CD to get
10895 debian-installer to find and use them. This proved to be wrong.
10896 Next, I hoped it was enough to symlink the relevant firmware packages
10897 to some useful location on the CD (tried /cdrom/ and
10898 /cdrom/firmware/). This also proved to not work, and at this point I
10899 found time to look at the debian-installer code to figure out what was
10900 going to work.&lt;/p&gt;
10901
10902 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
10903 look revealed that it would only look for firmware packages outside
10904 the installation media, so the CD was never checked for firmware
10905 packages. It would only check USB sticks, floppies and other
10906 &quot;external&quot; media devices. Today I changed it to also look in the
10907 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10908 solve the problem I ran into with Debian edu. I also changed it to
10909 look in /firmware/, to make sure the installer also find firmware
10910 provided in the initrd when booting the installer via PXE, to allow us
10911 to provide the same feature in the PXE setup included in Debian
10912 Edu.&lt;/p&gt;
10913
10914 &lt;p&gt;To make sure firmware deb packages with a license questions are not
10915 activated without asking if the license is accepted, I extended
10916 hw-detect to look for preinst scripts in the firmware packages, and
10917 run these before activating the firmware during installation. The
10918 license question is asked using debconf in the preinst, so this should
10919 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
10920
10921 &lt;p&gt;If you want to discuss the details of these features, please
10922 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
10923 </description>
10924 </item>
10925
10926 <item>
10927 <title>Parallellized boot is now the default in Debian/unstable</title>
10928 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
10929 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
10930 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
10931 <description>&lt;p&gt;Since this evening, parallel booting is the default in
10932 Debian/unstable for machines using dependency based boot sequencing.
10933 Apparently the testing of concurrent booting has been wider than
10934 expected, if I am to believe the
10935 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10936 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
10937 with the feature this weekend, to give us some time to detect any
10938 remaining problems before Squeeze is frozen. If serious problems are
10939 detected, it is simple to change the default back to sequential boot.
10940 The upload of the new sysvinit package also activate a new upstream
10941 version.&lt;/p&gt;
10942
10943 More information about
10944 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10945 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
10946 currently possible to disable parallel booting when one run into
10947 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
10948
10949 &lt;blockquote&gt;&lt;pre&gt;
10950 CONCURRENCY=none
10951 &lt;/pre&gt;&lt;/blockquote&gt;
10952
10953 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10954 the BTS, please usertag the report to get it to show up at
10955 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10956 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10957 </description>
10958 </item>
10959
10960 <item>
10961 <title>Sitesummary tip: Listing MAC address of all clients</title>
10962 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
10963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
10964 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
10965 <description>&lt;p&gt;In the recent Debian Edu versions, the
10966 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
10967 system&lt;/a&gt; is used to keep track of the machines in the school
10968 network. Each machine will automatically report its status to the
10969 central server after boot and once per night. The network setup is
10970 also reported, and using this information it is possible to get the
10971 MAC address of all network interfaces in the machines. This is useful
10972 to update the DHCP configuration.&lt;/p&gt;
10973
10974 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
10975 ist all MAC addresses of all machines reporting to sitesummary. Run
10976 this on the collector host:&lt;/p&gt;
10977
10978 &lt;blockquote&gt;&lt;pre&gt;
10979 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
10980 &lt;/pre&gt;&lt;/blockquote&gt;
10981
10982 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
10983 line per machine and with space between the MAC addresses.&lt;/p&gt;
10984
10985 &lt;p&gt;To allow system administrators easier job at adding static DHCP
10986 addresses for hosts, it would be possible to extend this to fetch
10987 machine information from sitesummary and update the DHCP and DNS
10988 tables in LDAP using this information. Such tool is unfortunately not
10989 written yet.&lt;/p&gt;
10990 </description>
10991 </item>
10992
10993 <item>
10994 <title>systemd, an interesting alternative to upstart</title>
10995 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
10996 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
10997 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
10998 <description>&lt;p&gt;The last few days a new boot system called
10999 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
11000 has been
11001 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
11002
11003 to the free software world. I have not yet had time to play around
11004 with it, but it seem to be a very interesting alternative to
11005 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
11006 a good alternative for Debian when we are able to switch to an event
11007 based boot system. Tollef is
11008 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
11009 systemd into Debian, and I look forward to seeing how well it work. I
11010 like the fact that systemd handles init.d scripts with dependency
11011 information natively, allowing them to run in parallel where upstart
11012 at the moment do not.&lt;/p&gt;
11013
11014 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
11015 platform support. It only work on recent Linux kernels, and also need
11016 some new kernel features enabled to function properly. This means
11017 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11018 system. Not sure how that will be handled if systemd proves to be the
11019 way forward.&lt;/p&gt;
11020
11021 &lt;p&gt;In the mean time, based on the
11022 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11023 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
11024 decided to enable full parallel booting as the default in Debian as
11025 soon as possible (probably this weekend or early next week), to see if
11026 there are any remaining serious bugs in the init.d dependencies. A
11027 new version of the sysvinit package implementing this change is
11028 already in experimental. If all go well, Squeeze will be released
11029 with parallel booting enabled by default.&lt;/p&gt;
11030 </description>
11031 </item>
11032
11033 <item>
11034 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
11035 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
11036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
11037 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
11038 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
11039 complete, so complete that it is actually possible to run all the
11040 init.d scripts in parallell based on these dependencies. If you want
11041 to test your Squeeze system, make sure
11042 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11043 based boot sequencing&lt;/a&gt; is enabled, and add this line to
11044 /etc/default/rcS:&lt;/p&gt;
11045
11046 &lt;blockquote&gt;&lt;pre&gt;
11047 CONCURRENCY=makefile
11048 &lt;/pre&gt;&lt;/blockquote&gt;
11049
11050 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
11051 scripts in parallel using the dependency information stored in
11052 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11053 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11054 to try to start the kdm and gdm scripts as early as possible, and will
11055 start the facilities required by kdm or gdm as early as possible to
11056 make this happen.&lt;/p&gt;
11057
11058 &lt;p&gt;Give it a try, and see if you like the result. If some services
11059 fail to start properly, it is most likely because they have incomplete
11060 init.d script dependencies in their startup script (or some of their
11061 dependent scripts have incomplete dependencies). Report bugs and get
11062 the package maintainers to fix it. :)&lt;/p&gt;
11063
11064 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
11065 manage to get the init.d script dependencies complete and correct. I
11066 expect we will get there in Squeeze+1, if we get manage to test and
11067 fix the remaining issues.&lt;/p&gt;
11068
11069 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11070 the BTS, please usertag the report to get it to show up at
11071 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11072 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11073 </description>
11074 </item>
11075
11076 <item>
11077 <title>Debian has switched to dependency based boot sequencing</title>
11078 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
11079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
11080 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
11081 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
11082 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
11083 have been migrated to using dependency based boot sequencing. This
11084 conclude work me and others have been doing for the last three days.
11085 It feels great to see this finally part of the default Debian
11086 installation. Now we just need to weed out the last few problems that
11087 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
11088
11089 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
11090 fixing the more fundamental problem of handing the event based
11091 non-predictable kernel in the early boot.&lt;/p&gt;
11092 </description>
11093 </item>
11094
11095 <item>
11096 <title>Taking over sysvinit development</title>
11097 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
11098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
11099 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
11100 <description>&lt;p&gt;After several years of frustration with the lack of activity from
11101 the existing sysvinit upstream developer, I decided a few weeks ago to
11102 take over the package and become the new upstream. The number of
11103 patches to track for the Debian package was becoming a burden, and the
11104 lack of synchronization between the distribution made it hard to keep
11105 the package up to date.&lt;/p&gt;
11106
11107 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11108 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
11109 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
11110 and Fedora), based on the patches currently in use in these
11111 distributions. We Debian maintainers plan to move to this tarball as
11112 the new upstream as soon as we find time to do the merge. Since the
11113 new tarball was created, we agreed with Werner at SuSe to make a new
11114 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
11115 development there. The project is registered and currently waiting
11116 for approval by the Savannah administrators, and as soon as it is
11117 approved, we will import the old versions from svn and continue
11118 working on the future release.&lt;/p&gt;
11119
11120 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
11121 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
11122 </description>
11123 </item>
11124
11125 <item>
11126 <title>Debian boots quicker and quicker</title>
11127 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
11128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
11129 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
11130 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
11131 people involved in the boot system on Debian and Ubuntu, to see if we
11132 could find more ways to speed up the boot system. This was an Ubuntu
11133 funded
11134 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
11135 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
11136 of boot systems, and ways to handle the increasing number of boot
11137 issues introduced by the Linux kernel becoming more and more
11138 asynchronous and event base. The Ubuntu approach using udev and
11139 upstart might be a good way forward. Time will show.&lt;/p&gt;
11140
11141 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
11142 process in Debian. All of these should be applied to get a quick
11143 boot:&lt;/p&gt;
11144
11145 &lt;ul&gt;
11146
11147 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
11148
11149 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
11150 clock is in UTC.&lt;/li&gt;
11151
11152 &lt;li&gt;Install and activate the insserv package to enable
11153 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11154 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
11155
11156 &lt;/ul&gt;
11157
11158 These points are based on the Google summer of code work done by
11159 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
11160 Villegas&lt;/a&gt;.
11161
11162 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
11163 unstable yesterday. When we tested it, we were able to cut 6 seconds
11164 from the boot sequence. It depend on very correct dependency
11165 declaration in all init.d scripts, so I expect us to find edge cases
11166 where the dependences in some scripts are slightly wrong when we start
11167 using this.&lt;/p&gt;
11168
11169 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11170 introduced by Raphael Geissert today, one that could affect the
11171 startup speed as well. Instead of starting some scripts concurrently
11172 from rcS.d/ and another set of scripts from rc2.d/, it would be
11173 possible to run a of them in the same process. A quick way to test
11174 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
11175 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
11176 </description>
11177 </item>
11178
11179 <item>
11180 <title>BSAs påstander om piratkopiering møter motstand</title>
11181 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
11182 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
11183 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
11184 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
11185 programvareselskapene som Microsoft og Apple, publisert en rapport der
11186 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11187 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11188 dager siden kom
11189 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
11190 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
11191 dagene. Et spesielt interessant kommentar fra Sverige,
11192 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
11193 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
11194
11195 &lt;blockquote&gt;
11196 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
11197 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11198 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
11199 exakta&quot;, säger BSAs Sverigechef John Hugosson.
11200 &lt;/blockquote&gt;
11201
11202 &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
11203 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
11204 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
11205 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
11206 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
11207
11208 &lt;p&gt;Fant lenkene via &lt;a
11209 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
11210 på Slashdot&lt;/a&gt;.&lt;/p&gt;
11211 </description>
11212 </item>
11213
11214 <item>
11215 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
11216 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
11217 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
11218 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
11219 <description>&lt;p&gt;Kom over
11220 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
11221 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11222 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11223 jobber til daglig. En rask opptelling forteller meg at vi har 490
11224 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
11225 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
11226 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
11227 </description>
11228 </item>
11229
11230 <item>
11231 <title>Kryptert harddisk - naturligvis</title>
11232 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
11233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
11234 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
11235 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
11236 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
11237 når en tar tap av arbeidstid, fortrolige dokumenter,
11238 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11239 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11240 til at jeg har kryptert harddisken på både kontormaskinen og min
11241 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11242 komme på avveie, den første informasjon relatert til jobben min ved
11243 Universitetet i Oslo, og den andre relatert til blant annet
11244 foreningsarbeide. Kryptering av diskene gjør at det er lite
11245 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11246 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11247 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11248 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11249 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11250 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11251 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11252 det er gjort slik jeg gjør det er minimale, og gevinstene er
11253 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11254 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
11255
11256 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11257 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11258 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11259 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11260 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11261 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11262 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11263 betydelige.&lt;/p&gt;
11264 </description>
11265 </item>
11266
11267 <item>
11268 <title>Two projects that have improved the quality of free software a lot</title>
11269 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
11270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
11271 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
11272 <description>&lt;p&gt;There are two software projects that have had huge influence on the
11273 quality of free software, and I wanted to mention both in case someone
11274 do not yet know them.&lt;/p&gt;
11275
11276 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11277 tool to detect and expose errors in the memory handling of programs.
11278 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11279 and it will report any problems on stdout. It is even better if the
11280 program include debug information. With debug information, it is able
11281 to report the source file name and line number where the problem
11282 occurs. It can report things like &#39;reading past memory block in file
11283 X line N, the memory block was allocated in file Y, line M&#39;, and
11284 &#39;using uninitialised value in control logic&#39;. This tool has made it
11285 trivial to investigate reproducible crash bugs in programs, and have
11286 reduced the number of this kind of bugs in free software a lot.
11287
11288 &lt;p&gt;The second one is
11289 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11290 a source code checker. It is able to process the source of a program
11291 and find problems in the logic without running the program. It
11292 started out as the Stanford Checker and became well known when it was
11293 used to find bugs in the Linux kernel. It is now a commercial tool
11294 and the company behind it is running
11295 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11296 free software community, where a lot of free software projects get
11297 their source checked for free. Several thousand defects have been
11298 found and fixed so far. It can find errors like &#39;lock L taken in file
11299 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11300 Y lines O to P can never be executed&#39;. The projects included in the
11301 community service project have managed to get rid of a lot of
11302 reliability problems thanks to Coverity.&lt;/p&gt;
11303
11304 &lt;p&gt;I believe tools like this, that are able to automatically find
11305 errors in the source, are vital to improve the quality of software and
11306 make sure we can get rid of the crashing and failing software we are
11307 surrounded by today.&lt;/p&gt;
11308 </description>
11309 </item>
11310
11311 <item>
11312 <title>No patch is not better than a useless patch</title>
11313 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11315 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11316 <description>&lt;p&gt;Julien Blache
11317 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11318 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11319 patch allow one to discuss a concrete and proposed solution, and also
11320 prove that the issue at hand is important enough for someone to spent
11321 time on fixing it. No patch do not provide any of these positive
11322 properties.&lt;/p&gt;
11323 </description>
11324 </item>
11325
11326 <item>
11327 <title>Standardize on protocols and formats, not vendors and applications</title>
11328 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11329 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11330 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11331 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11332 very good one to form a long lived computer infrastructure. It is the
11333 simple one, lost by many in todays computer industry: Standardize on
11334 open network protocols and open exchange/storage formats, not applications.
11335 Applications come and go, while protocols and files tend to stay, and
11336 thus one want to make it easy to change application and vendor, while
11337 avoiding conversion costs and locking users to a specific platform or
11338 application.&lt;/p&gt;
11339
11340 &lt;p&gt;This approach make it possible to replace the client applications
11341 independently of the server applications. One can even allow users to
11342 use several different applications as long as they handle the selected
11343 protocol and format. In the normal case, only one client application
11344 is recommended and users only get help if they choose to use this
11345 application, but those that want to deviate from the easy path are not
11346 blocked from doing so.&lt;/p&gt;
11347
11348 &lt;p&gt;It also allow us to replace the server side without forcing the
11349 users to replace their applications, and thus allow us to select the
11350 best server implementation at any moment, when scale and resouce
11351 requirements change.&lt;/p&gt;
11352
11353 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11354 open formats, but I would never recommend standardizing on a single
11355 application that do not use open network protocol or open formats.&lt;/p&gt;
11356 </description>
11357 </item>
11358
11359 <item>
11360 <title>Returning from Skolelinux developer gathering</title>
11361 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11362 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11363 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11364 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11365 Edu/Skolelinux development gathering. I got a bit done tuning the
11366 desktop, and looked into the dynamic service location protocol
11367 implementation avahi. It look like it could be useful for us. Almost
11368 30 people participated, and I believe it was a great environment to
11369 get to know the Skolelinux system. Walter Bender, involved in the
11370 development of the Sugar educational platform, presented his stuff and
11371 also helped me improve my OLPC installation. He also showed me that
11372 his Turtle Art application can be used in standalone mode, and we
11373 agreed that I would help getting it packaged for Debian. As a
11374 standalone application it would be great for Debian Edu. We also
11375 tried to get the video conferencing working with two OLPCs, but that
11376 proved to be too hard for us. The application seem to need more work
11377 before it is ready for me. I look forward to getting home and relax
11378 now. :)&lt;/p&gt;
11379 </description>
11380 </item>
11381
11382 <item>
11383 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11384 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11386 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11387 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11388 optimal. There is RFC 2307 documenting one way to store NIS maps in
11389 LDAP, and a modified version of this normally called RFC 2307bis, with
11390 some modifications to be compatible with Active Directory. The RFC
11391 specification handle the content of a lot of system databases, but do
11392 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11393
11394 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11395 we would like to store information about users, SMB clients/hosts,
11396 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11397 and LTSP configuration in LDAP. These objects have a lot in common,
11398 but with the current LDAP schemas it is not possible to have one
11399 object per entity. For example, one need to have at least three LDAP
11400 objects for a given computer, one with the SMB related stuff, one with
11401 DNS information and another with DHCP information. The schemas
11402 provided for DNS and DHCP are impossible to combine into one LDAP
11403 object. In addition, it is impossible to implement quick queries for
11404 netgroup membership, because of the way NIS triples are implemented.
11405 It just do not scale. I believe it is time for a few RFC
11406 specifications to cleam up this mess.&lt;/p&gt;
11407
11408 &lt;p&gt;I would like to have one LDAP object representing each computer in
11409 the network, and this object can then keep the SMB (ie host key), DHCP
11410 (mac address/name) and DNS (name/IP address) settings in one place.
11411 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11412
11413 &lt;p&gt;I would also like to have a quick way to map from a user or
11414 computer and to the net group this user or computer is a member.&lt;/p&gt;
11415
11416 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11417 in this regard, and the unix side need to catch up. Time to start a
11418 new IETF work group?&lt;/p&gt;
11419 </description>
11420 </item>
11421
11422 <item>
11423 <title>Endelig er Debian Lenny gitt ut</title>
11424 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11425 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11426 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11427 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11428 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11429 Et langt steg videre for Debian-prosjektet, og en rekke nye
11430 programpakker blir nå tilgjengelig for de av oss som bruker den
11431 stabile utgaven av Debian. Neste steg er nå å få
11432 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11433 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11434 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11435 slippes løs på skolene. Takk til alle debian-utviklerne som har
11436 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11437 bootsekvens tilgjengelig i stabil utgave, vha pakken
11438 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11439 </description>
11440 </item>
11441
11442 <item>
11443 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11444 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11446 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11447 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11448 Oslo. Most of Saturday was used for the general assemly for the
11449 member organization, but the rest of the weekend I used to tune the
11450 LTSP installation. LTSP now work out of the box on the 10-network.
11451 Acer Aspire One proved to be a very nice thin client, with both
11452 screen, mouse and keybard in a small box. Was working on getting the
11453 diskless workstation setup configured out of the box, but did not
11454 finish it before the weekend was up.&lt;/p&gt;
11455
11456 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11457 the Brazilian group, so that will have to wait for the next
11458 development gathering. Would love to have the Debian Edu installer
11459 automatically detect and configure a multiseat setup when it find one
11460 of these cards.&lt;/p&gt;
11461 </description>
11462 </item>
11463
11464 <item>
11465 <title>The sorry state of multimedia browser plugins in Debian</title>
11466 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11467 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11468 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11469 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11470 plugins available in Debian Lenny, to see which one we should use by
11471 default in Debian Edu. We need an embedded video playing plugin with
11472 control buttons to pause or stop the video, and capable of streaming
11473 all the multimedia content available on the web. The test results and
11474 notes are available on
11475 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11476 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11477 fill this need. My personal video player favorite, VLC, has a really
11478 bad plugin which fail on a lot of the test pages. A lot of the MIME
11479 types I would expect to work with any free software player (like
11480 video/ogg), just do not work. And simple formats like the
11481 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11482 totem and vlc plugins. I hope the situation will improve soon. No
11483 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11484
11485 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11486 be the only one fitting our needs. :/&lt;/p&gt;
11487 </description>
11488 </item>
11489
11490 </channel>
11491 </rss>