]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
f22a27f89dc71543109997d556161efe57b87b53
[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>Automatic Google Drive sync using grive in Debian</title>
11 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
13 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
14 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
15 rescue the remains, I helped set up automatic sync with Google Drive.
16 I did not find any sensible Debian package handling this
17 automatically, so I rebuild the grive2 source from
18 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
19 task and added a autostart desktop entry and a small shell script to
20 run in the background while the user is logged in to do the sync.
21 Here is a sketch of the setup for future reference.&lt;/p&gt;
22
23 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
24 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
25 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
26 to start the sync when the user log in:&lt;/p&gt;
27
28 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
29 [Desktop Entry]
30 Name=Google drive autosync
31 Type=Application
32 Exec=/home/user/bin/grive-sync
33 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
34
35 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
36 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
37
38 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
39 #!/bin/sh
40 set -e
41 cd ~/
42 cleanup() {
43 if [ &quot;$syncpid&quot; ] ; then
44 kill $syncpid
45 fi
46 }
47 trap cleanup EXIT INT QUIT
48 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
49 syncpdi=$!
50 while true; do
51 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
52 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
53 exit 1
54 fi
55 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
56 /usr/lib/grive/grive-sync.sh sync googledrive
57 fi
58 sleep 300
59 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
60 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
61
62 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
63 GNU GPL v2 licensed (or any later version, at your leisure), but I
64 doubt this code is possible to claim copyright on.&lt;/p&gt;
65
66 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
67 activities, please send Bitcoin donations to my address
68 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
69 </description>
70 </item>
71
72 <item>
73 <title>Using the Kodi API to play Youtube videos</title>
74 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
75 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
76 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
77 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
78 tell it to play a youtube URL I received in a chat, without having to
79 insert search terms using the on-screen keyboard. After searching the
80 web for API access to the Youtube plugin and testing a bit, I managed
81 to find a recipe that worked. If you got a kodi instance with its API
82 available from http://kodihost/jsonrpc, you can try the following to
83 have check out a nice cover band.&lt;/p&gt;
84
85 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
86 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
87 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
88 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
89 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
90
91 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
92 first argument. It can now handle direct video links, youtube links
93 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
94 Chromecast. :)&lt;/p&gt;
95
96 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
97 activities, please send Bitcoin donations to my address
98 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
99 </description>
100 </item>
101
102 <item>
103 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
104 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
105 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
106 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
107 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
108 with my family using a self hosted solution, as it is unacceptable to
109 place images from my personal life under the control of strangers
110 working for data hoarders like Google or Dropbox. The last few days I
111 have drafted an approach that might work out, and I would like to
112 share it with you. I would like to publish images on a server under
113 my control, and point some Internet connected display units using some
114 free and open standard to the images I published. As my primary
115 language is not limited to ASCII, I need to store metadata using
116 UTF-8. Many years ago, I hoped to find a digital photo frame capable
117 of reading a RSS feed with image references (aka using the
118 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
119 of such frames. In the end I gave up that approach.&lt;/p&gt;
120
121 &lt;p&gt;Some months ago, I discovered that
122 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
123 read images from a RSS feed, and used it to set up a screen saver on
124 my home info screen, showing images from the Daily images feed from
125 NASA. This proved to work well. More recently I discovered that
126 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
127 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
128 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
129 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
130 screen saver capable of reading a RSS feed with images and news. For
131 fun, I used it this summer to test Kodi on my parents TV by hooking up
132 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
133 screen saver showing selected pictures from my selection.&lt;/p&gt;
134
135 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
136 a RSS feed for the Kodi instance. I adjusted my &lt;a
137 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
138 /var/www/html/privatepictures/, wrote a small Perl script to extract
139 title and description metadata from the photo files and generate the
140 RSS file. I ended up using Perl instead of python, as the
141 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
142 tags I ended up using, while python3-exif did not. The relevant EXIF
143 tags only support ASCII, so I had to find better alternatives. XMP
144 seem to have the support I need.&lt;/p&gt;
145
146 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
147 use tags that can be easily added/updated using normal free software
148 photo managing software. I ended up using the tags set using this
149 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
150
151 &lt;blockquote&gt;&lt;pre&gt;
152 exiftool -headline=&#39;The RSS image title&#39; \
153 -description=&#39;The RSS image description.&#39; \
154 -subject+=for-family photo.jpeg
155 &lt;/pre&gt;&lt;/blockquote&gt;
156
157 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
158 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
159 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
160 shared with my family. Images with this keyword set are located and
161 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
162
163 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
164 suggestions.&lt;/p&gt;
165
166 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
167 activities, please send Bitcoin donations to my address
168 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
169 </description>
170 </item>
171
172 <item>
173 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
174 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
175 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
176 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
177 <description>&lt;p&gt;Last night, I wrote
178 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
179 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
180 During the day I received valuable feedback, and thanks to the
181 suggestions I have been able to rewrite the recipe into a much simpler
182 approach requiring no setup at all. It is a single script that take
183 care of it all.&lt;/p&gt;
184
185 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
186 desktop and stream it to Kodi. This fixed the video quality issue I
187 saw initially. It further removes the need to add a m3u file on the
188 Kodi machine, as it instead connects to
189 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
190 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
191 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
192 the script below, run it with the DNS name or IP address of the kodi
193 server to stream to as the only argument, and watch your screen show
194 up on the Kodi screen. Note, it depend on multicast on the local
195 network, so if you need to stream outside the local network, the
196 script must be modified. Also note, I have no idea if audio work, as
197 I only care about the picture part.&lt;/p&gt;
198
199 &lt;blockquote&gt;&lt;pre&gt;
200 #!/bin/sh
201 #
202 # Stream the Linux desktop view to Kodi. See
203 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
204 # for backgorund information.
205
206 # Make sure the stream is stopped in Kodi and the gstreamer process is
207 # killed if something go wrong (for example if curl is unable to find the
208 # kodi server). Do the same when interrupting this script.
209 kodicmd() {
210 host=&quot;$1&quot;
211 cmd=&quot;$2&quot;
212 params=&quot;$3&quot;
213 curl --silent --header &#39;Content-Type: application/json&#39; \
214 --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; \
215 &quot;http://$host/jsonrpc&quot;
216 }
217 cleanup() {
218 if [ -n &quot;$kodihost&quot; ] ; then
219 # Stop the playing when we end
220 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
221 jq .result[].playerid)
222 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
223 fi
224 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
225 kill &quot;$gstpid&quot;
226 fi
227 }
228 trap cleanup EXIT INT
229
230 if [ -n &quot;$1&quot; ]; then
231 kodihost=$1
232 shift
233 else
234 kodihost=kodi.local
235 fi
236
237 mcast=239.255.0.1
238 mcastport=1234
239 mcastttl=1
240
241 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
242 cut -d&quot; &quot; -f2|head -1)
243 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
244 videoconvert ! queue2 ! \
245 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
246 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
247 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
248 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
249 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
250 &gt; /dev/null 2&gt;&amp;1 &amp;
251 gstpid=$!
252
253 # Give stream a second to get going
254 sleep 1
255
256 # Ask kodi to start streaming using its JSON-RPC API
257 kodicmd &quot;$kodihost&quot; Player.Open \
258 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
259
260 # wait for gst to end
261 wait &quot;$gstpid&quot;
262 &lt;/pre&gt;&lt;/blockquote&gt;
263
264 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
265
266 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
267 activities, please send Bitcoin donations to my address
268 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
269 </description>
270 </item>
271
272 <item>
273 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
274 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
275 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
276 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
277 <description>&lt;p&gt;PS: See
278 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
279 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
280
281 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
282 my projector connected to Kodi. I sadly had to admit that I had no
283 idea, as it was a task I never had tried. Since then, I have been
284 looking for a way to do so, preferable without much extra software to
285 install on either side. Today I found a way that seem to kind of
286 work. Not great, but it is a start.&lt;/p&gt;
287
288 &lt;p&gt;I had a look at several approaches, for example
289 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
290 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
291 local storage enough to store the stream locally. This is not going
292 to work well for me, lacking enough free space, and it would
293 impossible for my friend to get working.&lt;/p&gt;
294
295 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
296 video stream that Kodi could play. Preferably using
297 broadcast/multicast, to avoid having to change any setup on the Kodi
298 side when starting such stream. Unfortunately, the only recipe I
299 could find using multicast used the rtp protocol, and this protocol
300 seem to not be supported by Kodi.&lt;/p&gt;
301
302 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
303 have to specify the IP address of the streaming machine in both the
304 sending command and the file on the Kodi server. But it is showing my
305 desktop, and thus allow us to have a shared look on the big screen at
306 the programs I work on.&lt;/p&gt;
307
308 &lt;p&gt;I did not spend much time investigating codeces. I combined the
309 rtp and rtsp recipes from
310 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
311 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
312 this working on the desktop/streaming end.&lt;/p&gt;
313
314 &lt;blockquote&gt;&lt;pre&gt;
315 vlc screen:// --sout \
316 &#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;
317 &lt;/pre&gt;&lt;/blockquote&gt;
318
319 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
320 same IP address:&lt;/p&gt;
321
322 &lt;blockquote&gt;&lt;pre&gt;
323 echo rtsp://192.168.11.4:8080/test.sdp \
324 &gt; /storage/videos/screenstream.m3u
325 &lt;/pre&gt;&lt;/blockquote&gt;
326
327 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
328 as I can tell the IP must be hardcoded for this to work. In other
329 words, if someone elses machine is going to do the steaming, you have
330 to update screenstream.m3u on the Kodi machine and adjust the vlc
331 recipe. To get started, locate the file in Kodi and select the m3u
332 file while the VLC stream is running. The desktop then show up in my
333 big screen. :)&lt;/p&gt;
334
335 &lt;p&gt;When using the same technique to stream a video file with audio,
336 the audio quality is really bad. No idea if the problem is package
337 loss or bad parameters for the transcode. I do not know VLC nor Kodi
338 enough to tell.&lt;/p&gt;
339
340 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
341 succestions and reminded me about an important step. The &quot;screen:&quot;
342 input source is only available once the vlc-plugin-access-extra
343 package is installed on Debian. Without it, you will see this error
344 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
345 for details.&quot; He further found that it is possible to drop some parts
346 of the VLC command line to reduce the amount of hardcoded information.
347 It is also useful to consider using cvlc to avoid having the VLC
348 window in the desktop view. In sum, this give us this command line on
349 the source end
350
351 &lt;blockquote&gt;&lt;pre&gt;
352 cvlc screen:// --sout \
353 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
354 &lt;/pre&gt;&lt;/blockquote&gt;
355
356 &lt;p&gt;and this on the Kodi end&lt;p&gt;
357
358 &lt;blockquote&gt;&lt;pre&gt;
359 echo rtsp://192.168.11.4:8080/ \
360 &gt; /storage/videos/screenstream.m3u
361 &lt;/pre&gt;&lt;/blockquote&gt;
362
363 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
364 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
365 audio quality, so I guess the issue is in the input or transcoding
366 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
367 parameters to use more bandwidth, but it did not make a
368 difference.&lt;/p&gt;
369
370 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
371 gstreamer instead of VLC, and this proved to work great! He also
372 provided me with the trick to get Kodi to use a multicast stream as
373 its source. By using this monstrous oneliner, I can stream my desktop
374 with good video quality in reasonable framerate to the 239.255.0.1
375 multicast address on port 1234:
376
377 &lt;blockquote&gt;&lt;pre&gt;
378 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
379 videoconvert ! queue2 ! \
380 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
381 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
382 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
383 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
384 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
385 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
386 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
387 &lt;/pre&gt;&lt;/blockquote&gt;
388
389 &lt;p&gt;and this on the Kodi end&lt;p&gt;
390
391 &lt;blockquote&gt;&lt;pre&gt;
392 echo udp://@239.255.0.1:1234 \
393 &gt; /storage/videos/screenstream.m3u
394 &lt;/pre&gt;&lt;/blockquote&gt;
395
396 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
397 pick the one you need. This approach will of course lead to trouble
398 if more than one source uses the same multicast port and address.
399 Note the ttl-mc=1 setting, which limit the multicast packages to the
400 local network. If the value is increased, your screen will be
401 broadcasted further, one network &quot;hop&quot; for each increase (read up on
402 multicast to learn more. :)!&lt;/p&gt;
403
404 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
405 could use this VLC command to stream to the same multicast address.
406 The image quality is way better than the rtsp approach, but gstreamer
407 seem to be doing a better job.&lt;/p&gt;
408
409 &lt;blockquote&gt;&lt;pre&gt;
410 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;
411 &lt;/pre&gt;&lt;/blockquote&gt;
412
413 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
414 activities, please send Bitcoin donations to my address
415 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
416 </description>
417 </item>
418
419 <item>
420 <title>What is the most supported MIME type in Debian in 2018?</title>
421 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
423 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
424 <description>&lt;p&gt;Five years ago,
425 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
426 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
427 analysing the desktop files in all packages in the archive. Since
428 then, the DEP-11 AppStream system has been put into production, making
429 the task a lot easier. This made me want to repeat the measurement,
430 to see how much things changed. Here are the new numbers, for
431 unstable only this time:
432
433 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
434
435 &lt;pre&gt;
436 count MIME type
437 ----- -----------------------
438 56 image/jpeg
439 55 image/png
440 49 image/tiff
441 48 image/gif
442 39 image/bmp
443 38 text/plain
444 37 audio/mpeg
445 34 application/ogg
446 33 audio/x-flac
447 32 audio/x-mp3
448 30 audio/x-wav
449 30 audio/x-vorbis+ogg
450 29 image/x-portable-pixmap
451 27 inode/directory
452 27 image/x-portable-bitmap
453 27 audio/x-mpeg
454 26 application/x-ogg
455 25 audio/x-mpegurl
456 25 audio/ogg
457 24 text/html
458 &lt;/pre&gt;
459
460 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
461 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
462 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
463
464 &lt;p&gt;It is interesting to see how image formats have passed text/plain
465 as the most announced supported MIME type. These days, thanks to the
466 AppStream system, if you run into a file format you do not know, and
467 want to figure out which packages support the format, you can find the
468 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
469 look up all packages announcing support for this format in their
470 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
471 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
472 me, want to know which packages support inode/directory, you can get a
473 list like this:&lt;/p&gt;
474
475 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
476 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
477 Package: anjuta
478 Package: audacious
479 Package: baobab
480 Package: cervisia
481 Package: chirp
482 Package: dolphin
483 Package: doublecmd-common
484 Package: easytag
485 Package: enlightenment
486 Package: ephoto
487 Package: filelight
488 Package: gwenview
489 Package: k4dirstat
490 Package: kaffeine
491 Package: kdesvn
492 Package: kid3
493 Package: kid3-qt
494 Package: nautilus
495 Package: nemo
496 Package: pcmanfm
497 Package: pcmanfm-qt
498 Package: qweborf
499 Package: ranger
500 Package: sirikali
501 Package: spacefm
502 Package: spacefm
503 Package: vifm
504 %
505 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
506
507 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
508 format is not yet supported by any package in Debian:&lt;/p&gt;
509
510 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
511 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
512 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
513 %
514 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
515
516 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
517 format:&lt;/p&gt;
518
519 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
520 % appstreamcli what-provides mimetype application/sla|grep Package
521 Package: cura
522 Package: meshlab
523 Package: printrun
524 %
525 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
526
527 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
528
529 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
530 activities, please send Bitcoin donations to my address
531 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
532 </description>
533 </item>
534
535 <item>
536 <title>Debian APT upgrade without enough free space on the disk...</title>
537 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
539 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
540 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
541 for a while, and when I need to update it there is not enough free
542 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
543 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
544 upgrade only some of the packages in one batch, until the amount of
545 packages to download fall below the amount of free space available.
546 Today, I had about 500 packages to upgrade, and after a while I got
547 tired of trying to install chunks of packages manually. I concluded
548 that I did not have the spare hours required to complete the task, and
549 decided to see if I could automate it. I came up with this small
550 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
551
552 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
553 #!/bin/sh
554 #
555 # Upgrade packages when the disk is too full to upgrade every
556 # upgradable package in one lump. Fetching packages to upgrade using
557 # apt, and then installing using dpkg, to avoid changing the package
558 # flag for manual/automatic.
559
560 set -e
561
562 ignore() {
563 if [ &quot;$1&quot; ]; then
564 grep -v &quot;$1&quot;
565 else
566 cat
567 fi
568 }
569
570 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
571 echo &quot;Upgrading $p&quot;
572 apt clean
573 apt install --download-only -y $p
574 for f in /var/cache/apt/archives/*.deb; do
575 if [ -e &quot;$f&quot; ]; then
576 dpkg -i /var/cache/apt/archives/*.deb
577 break
578 fi
579 done
580 done
581 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
582
583 &lt;p&gt;The script will extract the list of packages to upgrade, try to
584 download the packages needed to upgrade one package, install the
585 downloaded packages using dpkg. The idea is to upgrade packages
586 without changing the APT mark for the package (ie the one recording of
587 the package was manually requested or pulled in as a dependency). To
588 use it, simply run it as root from the command line. If it fail, try
589 &#39;apt install -f&#39; to clean up the mess and run the script again. This
590 might happen if the new packages conflict with one of the old
591 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
592
593 &lt;p&gt;It take one option, a package to ignore in the list of packages to
594 upgrade. The option to ignore a package is there to be able to skip
595 the packages that are simply too large to unpack. Today this was
596 &#39;ghc&#39;, but I have run into other large packages causing similar
597 problems earlier (like TeX).&lt;/p&gt;
598
599 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
600 alternative ways to handle this. The &quot;unattended-upgrades
601 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
602 each package to upgrade, and then upgrade them in order, smallest set
603 first. It might be a better option than my above mentioned script.
604 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
605 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
606
607 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
608 activities, please send Bitcoin donations to my address
609 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
610 </description>
611 </item>
612
613 <item>
614 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
615 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
617 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
618 <description>&lt;p&gt;A new version of the
619 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
620 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
621 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
622 useful. It was uploaded the last few days, and the last update will
623 enter testing tomorrow. See the
624 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
625 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
626 was announced 6 days ago. We will try to get it into Debian as
627 well.&lt;/p&gt;
628
629 &lt;p&gt;More information related to 3D printing is available on the
630 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
631 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
632 in Debian.&lt;/p&gt;
633
634 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
635 activities, please send Bitcoin donations to my address
636 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
637 </description>
638 </item>
639
640 <item>
641 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
642 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
643 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
644 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
645 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
646 that the nice and user friendly 3D printer slicer software Cura just
647 entered Debian Unstable. It consist of five packages,
648 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
649 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
650 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
651 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
652 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
653 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
654 two, uranium and cura, entered Unstable yesterday. This should make
655 it easier for Debian users to print on at least the Ultimaker class of
656 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
657 make life easier for at least me. :)&lt;/p&gt;
658
659 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
660 happy to assist him in sponsoring the packages. With the introduction
661 of Cura, Debian is up to three 3D printer slicers at your service,
662 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
663 printer, give it a go. :)&lt;/p&gt;
664
665 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
666 team, flocking together on the
667 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
668 mailing list and the
669 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
670 IRC channel.&lt;/p&gt;
671
672 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
673 version 3.0.3 and then update the entire set of packages to version
674 3.1.0 which showed up the last few days.&lt;/p&gt;
675 </description>
676 </item>
677
678 <item>
679 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
680 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
681 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
682 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
683 <description>&lt;p&gt;At my nearby maker space,
684 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
685 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
686 on Windows and MacOS X than Linux, because the software involved had
687 to be manually compiled and set up on Linux while premade packages
688 worked out of the box on Windows and MacOS X. I found this annoying,
689 as the software involved,
690 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
691 and should be trivial to get up and running on Linux if someone took
692 the time to package it for the relevant distributions. I even found
693 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
694 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
695 never resulted in the software showing up in Debian. So a few days
696 ago I offered my help to try to improve the situation.&lt;/p&gt;
697
698 &lt;p&gt;Now I am very happy to see that all the packages required by a
699 working Cura in Debian are uploaded into Debian and waiting in the NEW
700 queue for the ftpmasters to have a look. You can track the progress
701 on
702 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
703 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
704
705 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
706 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
707 queue&lt;/a&gt; while we work up updating the packages to the latest
708 upstream version.&lt;/p&gt;
709
710 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
711 to use and was unable to configure correctly for Ultimaker 2+ in the
712 short time I spent on it, are already in Debian. If you are looking
713 for 3D printer &quot;slicers&quot; and want something already available in
714 Debian, check out
715 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
716 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
717 The latter is a fork of the former.&lt;/p&gt;
718
719 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
720 activities, please send Bitcoin donations to my address
721 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
722 </description>
723 </item>
724
725 <item>
726 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
727 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
728 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
729 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
730 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
731 mobile cell towers. And this radio chatter is available for anyone
732 with a radio receiver capable of receiving them. Details about the
733 mobile phones with very good accuracy is of course collected by the
734 phone companies, but this is not the topic of this blog post. The
735 mobile phone radio chatter make it possible to figure out when a cell
736 phone is nearby, as it include the SIM card ID (IMSI). By paying
737 attention over time, one can see when a phone arrive and when it leave
738 an area. I believe it would be nice to make this information more
739 available to the general public, to make more people aware of how
740 their phones are announcing their whereabouts to anyone that care to
741 listen.&lt;/p&gt;
742
743 &lt;p&gt;I am very happy to report that we managed to get something
744 visualizing this information up and running for
745 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
746 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
747 library. The solution is based on the
748 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
749 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
750 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
751 Sone from the Computer Science department of the University of
752 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
753 IMSIs) as dots in a web browser graph, with lines to the dot
754 representing mobile base station it is talking to. It was working in
755 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
756
757 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
758 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
759 connected and visualize the visible cell phone towers using an
760 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
761 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
762 grgsm_livemon_headless processes from
763 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
764 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
765
766 &lt;p&gt;The frequencies to listen to, are identified using a slightly
767 patched scan-and-livemon (to set the --args values for each receiver),
768 and the Hopglass data is generated using the
769 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
770 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
771 more than four SDRs working. There is also a geographical map trying
772 to show the location of the base stations, but I believe their
773 coordinates are hardcoded to some random location in Germany, I
774 believe. The code should be replaced with code to look up location in
775 a text file, a sqlite database or one of the online databases
776 mentioned in
777 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
778 issue for the topic&lt;/a&gt;.
779
780 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
781 </description>
782 </item>
783
784 <item>
785 <title>Easier recipe to observe the cell phones around you</title>
786 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
787 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
788 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
789 <description>&lt;p&gt;A little more than a month ago I wrote
790 &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
791 to observe the SIM card ID (aka IMSI number) of mobile phones talking
792 to nearby mobile phone base stations using Debian GNU/Linux and a
793 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
794 the location of people and equipment (like cars and trains) with an
795 accuracy of a few kilometer. Since then we have worked to make the
796 procedure even simpler, and it is now possible to do this without any
797 manual frequency tuning and without building your own packages.&lt;/p&gt;
798
799 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
800 package is now included in Debian testing and unstable, and the
801 IMSI-catcher code no longer require root access to fetch and decode
802 the GSM data collected using gr-gsm.&lt;/p&gt;
803
804 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
805 clone of two python scripts:&lt;/p&gt;
806
807 &lt;ol&gt;
808
809 &lt;li&gt;Start with a Debian machine running the Buster version (aka
810 testing).&lt;/li&gt;
811
812 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
813 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
814
815 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
816 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
817
818 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
819
820 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
821 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
822 stations and start listening for GSM packages on one of them.&lt;/li&gt;
823
824 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
825 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
826
827 &lt;/ol&gt;
828
829 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
830 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
831 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
832 work with RTL 8232 and other similar USB radio receivers you can get
833 very cheaply
834 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
835 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
836 and only use HackRF for fetching GSM data.&lt;/p&gt;
837
838 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
839 frequencies at the time, so if you are going to track and count every
840 cell phone around you, you need to listen to all the frequencies used.
841 To listen to several frequencies, use the --numrecv argument to
842 scan-and-livemon to use several receivers. Further, I am not sure if
843 phones using 3G or 4G will show as talking GSM to base stations, so
844 this approach might not see all phones around you. I typically see
845 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
846
847 &lt;p&gt;I&#39;ve tried to run the scanner on a
848 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
849 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
850 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
851 stdout, I am told there it is caused by a buffer overflow between the
852 radio and GNU Radio, caused by the program being unable to read the
853 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
854 where you started scan-and-livemon, you need a give the process more
855 CPU power. Perhaps someone are able to optimize the code to a point
856 where it become possible to set up RPi3 based GSM sniffers? I tried
857 using Raspbian instead of Debian, but there seem to be something wrong
858 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
859 </description>
860 </item>
861
862 <item>
863 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
864 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
866 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
867 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
868 web based ICT news magazine digi.no on
869 &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
870 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
871 DVB-T software defined radios. The article refered to instructions
872 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
873 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;
874
875 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
876 bypass apt), use pip to install pybombs (to bypass both apt and pip),
877 and the ask pybombs to fetch and build everything you need from
878 scratch. I wanted to see if I could do the same on the most recent
879 Debian packages, but this did not work because pybombs tried to build
880 stuff that no longer build with the most recent openssl library or
881 some other version skew problem. While trying to get this recipe
882 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
883 and the only piece of software dependency missing in Debian was the
884 gr-gsm package. I also found out that the lead upstream developer of
885 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
886 Debian packages provided in an Ubuntu PPA repository. All I needed to
887 do was to dget the Debian source package and built it.&lt;/p&gt;
888
889 &lt;p&gt;The IMSI collector is a python script listening for packages on the
890 loopback network device and printing to the terminal some specific GSM
891 packages with IMSI numbers in them. The code is fairly short and easy
892 to understand. The reason this work is because gr-gsm include a tool
893 to read GSM data from a software defined radio like a DVB-T USB stick
894 and other software defined radios, decode them and inject them into a
895 network device on your Linux machine (using the loopback device by
896 default). This proved to work just fine, and I&#39;ve been testing the
897 collector for a few days now.&lt;/p&gt;
898
899 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
900
901 &lt;ol&gt;
902
903 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
904
905 &lt;li&gt;build and install the gr-gsm package available from
906 &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;
907
908 &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;
909
910 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
911 where it was started is filled with a stream of text (meaning you
912 found a GSM station).&lt;/li&gt;
913
914 &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;
915
916 &lt;/ol&gt;
917
918 &lt;p&gt;To make it even easier in the future to get this sniffer up and
919 running, I decided to package
920 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
921 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
922 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
923 Luckily the gnuradio maintainer has promised to help me, as I do not
924 know much about gnuradio stuff yet.&lt;/p&gt;
925
926 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
927 commercial tools like
928 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
929 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
930 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
931 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
932 more people realise how their whereabouts when carrying a cell phone
933 is easily tracked. Seeing the data flow on the screen, realizing that
934 I live close to a police station and knowing that the police is also
935 wearing cell phones, I wonder how hard it would be for criminals to
936 track the position of the police officers to discover when there are
937 police near by, or for foreign military forces to track the location
938 of the Norwegian military forces, or for anyone to track the location
939 of government officials...&lt;/p&gt;
940
941 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
942 script mentioned above is only a fraction of the data broadcasted on
943 the GSM network. It will only collect one frequency at the time,
944 while a typical phone will be using several frequencies, and not all
945 phones will be using the frequencies tracked by the grgsm_livemod
946 program. Also, there is a lot of radio chatter being ignored by the
947 simple_IMSI-catcher script, which would be collected by extending the
948 parser code. I wonder if gr-gsm can be set up to listen to more than
949 one frequency?&lt;/p&gt;
950 </description>
951 </item>
952
953 <item>
954 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
955 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
957 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
958 <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;
959
960 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
961 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
962 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
963 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
964 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
965 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
966 price. The book is also available for download in electronic form as
967 PDF, EPUB and Mobipocket, as can be
968 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
969 as a web page&lt;/a&gt;.&lt;/p&gt;
970
971 &lt;p&gt;This is the second book I publish (the first was the book
972 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
973 in
974 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
975 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
976 and
977 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
978 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
979 project. I hope
980 &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
981 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
982 </description>
983 </item>
984
985 <item>
986 <title>Når nynorskoversettelsen svikter til eksamen...</title>
987 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
989 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
990 <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
991 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
992 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
993 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
994 på om den fri oversetterløsningen
995 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
996 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
997
998 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
999
1000 &lt;blockquote&gt;
1001 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1002 rolle og muligheter til å håndtere internasjonale utfordringer, som
1003 for eksempel flykningekrisen.&lt;/p&gt;
1004
1005 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1006 på temaet:&lt;/p&gt;
1007 &lt;ol&gt;
1008 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
1009 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
1010 &lt;/ol&gt;
1011
1012 &lt;/blockquote&gt;
1013
1014 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
1015
1016 &lt;blockquote&gt;
1017 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1018 andre aktørar og høve til å handtera internasjonale utfordringar, som
1019 til dømes *flykningekrisen.&lt;/p&gt;
1020
1021 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
1022 temaet:&lt;/p&gt;
1023
1024 &lt;ol&gt;
1025 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
1026 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
1027 &lt;/ol&gt;
1028
1029 &lt;/blockquote&gt;
1030
1031 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
1032 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1033 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1034 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
1035 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
1036 det er kanskje flisespikking. Det understreker vel bare at det alltid
1037 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
1038 </description>
1039 </item>
1040
1041 <item>
1042 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
1043 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
1044 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
1045 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
1046 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
1047 computers at the time, I often needed a way to detect if the machine
1048 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
1049 file or directory affected by the hang, the process (and possibly the
1050 shell) will hang too. So you want to be able to detect this without
1051 risking the detection process getting stuck too. It has not been
1052 obvious how to do this. When the hang has lasted a while, it is
1053 possible to find messages like these in dmesg:&lt;/p&gt;
1054
1055 &lt;p&gt;&lt;blockquote&gt;
1056 nfs: server nfsserver not responding, still trying
1057 &lt;br&gt;nfs: server nfsserver OK
1058 &lt;/blockquote&gt;&lt;/p&gt;
1059
1060 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
1061 be sure looking in dmesg is going to work. If there are lots of other
1062 messages in dmesg the lines might have rotated out of site before they
1063 are noticed.&lt;/p&gt;
1064
1065 &lt;p&gt;While reading through the nfs client implementation in linux kernel
1066 code, I came across some statistics that seem to give a way to detect
1067 it. The om_timeouts sunrpc value in the kernel will increase every
1068 time the above log entry is inserted into dmesg. And after digging a
1069 bit further, I discovered that this value show up in
1070 /proc/self/mountstats on Linux.&lt;/p&gt;
1071
1072 &lt;p&gt;The mountstats content seem to be shared between files using the
1073 same file system context, so it is enough to check one of the
1074 mountstats files to get the state of the mount point for the machine.
1075 I assume this will not show lazy umounted NFS points, nor NFS mount
1076 points in a different process context (ie with a different filesystem
1077 view), but that does not worry me.&lt;/p&gt;
1078
1079 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
1080
1081 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1082 [...]
1083 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1084 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
1085 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
1086 age: 7863311
1087 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
1088 sec: flavor=1,pseudoflavor=1
1089 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
1090 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1091 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
1092 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1093 per-op statistics
1094 NULL: 0 0 0 0 0 0 0 0
1095 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1096 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
1097 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1098 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1099 READLINK: 125 125 0 20472 18620 0 1112 1118
1100 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1101 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1102 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
1103 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
1104 SYMLINK: 903 903 0 233428 245488 6 5865 5917
1105 MKNOD: 80 80 0 20148 21760 0 299 304
1106 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
1107 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
1108 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
1109 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
1110 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1111 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1112 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
1113 FSINFO: 2 2 0 232 328 0 1 1
1114 PATHCONF: 1 1 0 116 140 0 0 0
1115 COMMIT: 0 0 0 0 0 0 0 0
1116
1117 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1118 [...]
1119 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1120
1121 &lt;p&gt;The key number to look at is the third number in the per-op list.
1122 It is the number of NFS timeouts experiences per file system
1123 operation. Here 22 write timeouts and 5 access timeouts. If these
1124 numbers are increasing, I believe the machine is experiencing NFS
1125 hang. Unfortunately the timeout value do not start to increase right
1126 away. The NFS operations need to time out first, and this can take a
1127 while. The exact timeout value depend on the setup. For example the
1128 defaults for TCP and UDP mount points are quite different, and the
1129 timeout value is affected by the soft, hard, timeo and retrans NFS
1130 mount options.&lt;/p&gt;
1131
1132 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
1133 Enterprise Linux for getting the timeout count is to peek in /proc/.
1134 But according to
1135 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
1136 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
1137 command can be used to get these timeout values. But this do not work
1138 on Linux, as far as I can tell. I
1139 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
1140 but have not seen any replies yet.&lt;/p&gt;
1141
1142 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
1143 experiencing NFS hangs? Is there a way to detect which processes are
1144 affected? Is there a way to get the NFS mount going quickly once the
1145 network problem causing the NFS hang has been cleared? I would very
1146 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
1147 </description>
1148 </item>
1149
1150 <item>
1151 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
1152 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
1153 <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>
1154 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
1155 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
1156 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1157 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
1158 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1159 we are working on the proof reading to ensure consistent language and
1160 use of correct computer science terms. The plan is to make the book
1161 available on paper, as well as in electronic form. For that to
1162 happen, the proof reading must be completed and all the figures need
1163 to be translated. If you want to help out, get in touch.&lt;/p&gt;
1164
1165 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
1166
1167 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
1168 pages) of the book created every morning is available for
1169 proofreading. If you find any errors, please
1170 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
1171 Weblate and correct the error&lt;/a&gt;. The
1172 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
1173 of the translation including figures&lt;/a&gt; is a useful source for those
1174 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
1175 </description>
1176 </item>
1177
1178 <item>
1179 <title>Unlimited randomness with the ChaosKey?</title>
1180 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
1181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
1182 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
1183 <description>&lt;p&gt;A few days ago I ordered a small batch of
1184 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
1185 USB dongle for generating entropy created by Bdale Garbee and Keith
1186 Packard. Yesterday it arrived, and I am very happy to report that it
1187 work great! According to its designers, to get it to work out of the
1188 box, you need the Linux kernel version 4.1 or later. I tested on a
1189 Debian Stretch machine (kernel version 4.9), and there it worked just
1190 fine, increasing the available entropy very quickly. I wrote a small
1191 test oneliner to test. It first print the current entropy level,
1192 drain /dev/random, and then print the entropy level for five seconds.
1193 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
1194
1195 &lt;blockquote&gt;&lt;pre&gt;
1196 % cat /proc/sys/kernel/random/entropy_avail; \
1197 dd bs=1M if=/dev/random of=/dev/null count=1; \
1198 for n in $(seq 1 5); do \
1199 cat /proc/sys/kernel/random/entropy_avail; \
1200 sleep 1; \
1201 done
1202 300
1203 0+1 oppføringer inn
1204 0+1 oppføringer ut
1205 28 byte kopiert, 0,000264565 s, 106 kB/s
1206 4
1207 8
1208 12
1209 17
1210 21
1211 %
1212 &lt;/pre&gt;&lt;/blockquote&gt;
1213
1214 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
1215 application requiring random bits (like a HTTPS enabled web server)
1216 will halt and wait for more entrpy. And here is the situation with
1217 the ChaosKey inserted:&lt;/p&gt;
1218
1219 &lt;blockquote&gt;&lt;pre&gt;
1220 % cat /proc/sys/kernel/random/entropy_avail; \
1221 dd bs=1M if=/dev/random of=/dev/null count=1; \
1222 for n in $(seq 1 5); do \
1223 cat /proc/sys/kernel/random/entropy_avail; \
1224 sleep 1; \
1225 done
1226 1079
1227 0+1 oppføringer inn
1228 0+1 oppføringer ut
1229 104 byte kopiert, 0,000487647 s, 213 kB/s
1230 433
1231 1028
1232 1031
1233 1035
1234 1038
1235 %
1236 &lt;/pre&gt;&lt;/blockquote&gt;
1237
1238 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
1239 someone want to buy one here in Norway. :)&lt;/p&gt;
1240
1241 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
1242 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
1243 recording illuminating&lt;/a&gt;. It explains exactly what the source of
1244 randomness is, if you are unable to spot it from the schema drawing
1245 available from the ChaosKey web site linked at the start of this blog
1246 post.&lt;/p&gt;
1247 </description>
1248 </item>
1249
1250 <item>
1251 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
1252 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
1253 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
1254 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
1255 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
1256 web servers, and who own the network equipment it is flowing through?
1257 It is possible to get a glimpse of this from using traceroute, but it
1258 is hard to find all the details. Many years ago, I wrote a system to
1259 map the Norwegian Internet (trying to figure out if our plans for a
1260 network game service would get low enough latency, and who we needed
1261 to talk to about setting up game servers close to the users. Back
1262 then I used traceroute output from many locations (I asked my friends
1263 to run a script and send me their traceroute output) to create the
1264 graph and the map. The output from traceroute typically look like
1265 this:
1266
1267 &lt;p&gt;&lt;pre&gt;
1268 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
1269 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
1270 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
1271 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
1272 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
1273 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
1274 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
1275 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
1276 8 * * *
1277 9 * * *
1278 [...]
1279 &lt;/pre&gt;&lt;/p&gt;
1280
1281 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
1282 network equipment involved in getting the data traffic from me to the
1283 www.stortinget.no server, and how long it took in milliseconds for a
1284 package to reach the equipment and return to me. Three packages are
1285 sent, and some times the packages do not follow the same path. This
1286 is shown for hop 5, where three different IP addresses replied to the
1287 traceroute request.&lt;/p&gt;
1288
1289 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
1290 implementations I use are traceroute (using ICMP packages) mtr (can do
1291 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1292 traceroute and a lot of other capabilities). All of them are easily
1293 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
1294
1295 &lt;p&gt;This time around, I wanted to know the geographic location of
1296 different route points, to visualize how visiting a web page spread
1297 information about the visit to a lot of servers around the globe. The
1298 background is that a web site today often will ask the browser to get
1299 from many servers the parts (for example HTML, JSON, fonts,
1300 JavaScript, CSS, video) required to display the content. This will
1301 leak information about the visit to those controlling these servers
1302 and anyone able to peek at the data traffic passing by (like your ISP,
1303 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
1304
1305 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
1306 www.stortinget.no. It is read daily by all members of parliament and
1307 their staff, as well as political journalists, activits and many other
1308 citizens of Norway. A visit to the www.stortinget.no web site will
1309 ask your browser to contact 8 other servers: ajax.googleapis.com,
1310 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1311 stats.g.doubleclick.net, www.google-analytics.com,
1312 www.googletagmanager.com and www.netigate.se. I extracted this by
1313 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
1314 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1315 render the page (in HAR format using
1316 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
1317 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
1318 to do this). My goal is to visualize network traces to all IP
1319 addresses behind these DNS names, do show where visitors personal
1320 information is spread when visiting the page.&lt;/p&gt;
1321
1322 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
1323 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;
1324
1325 &lt;p&gt;When I had a look around for options, I could not find any good
1326 free software tools to do this, and decided I needed my own traceroute
1327 wrapper outputting KML based on locations looked up using GeoIP. KML
1328 is easy to work with and easy to generate, and understood by several
1329 of the GIS tools I have available. I got good help from by NUUG
1330 colleague Anders Einar with this, and the result can be seen in
1331 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
1332 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
1333 free GeoIP databases I could find (and the for-pay databases my
1334 friends had access to) is not up to the task. The IP addresses of
1335 central Internet infrastructure would typically be placed near the
1336 controlling companies main office, and not where the router is really
1337 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
1338 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
1339
1340 &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
1341 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;
1342
1343 &lt;p&gt;I also had a look at the visual traceroute graph created by
1344 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1345 showing IP network ownership (aka AS owner) for the IP address in
1346 question.
1347 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1348 graph display a lot of useful information about the traceroute in SVG
1349 format&lt;/a&gt;, and give a good indication on who control the network
1350 equipment involved, but it do not include geolocation. This graph
1351 make it possible to see the information is made available at least for
1352 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1353 3 Communications and NetDNA.&lt;/p&gt;
1354
1355 &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
1356 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;
1357
1358 &lt;p&gt;In the process, I came across the
1359 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1360 Salim Gasmi. Its methology of combining guesses based on DNS names,
1361 various location databases and finally use latecy times to rule out
1362 candidate locations seemed to do a very good job of guessing correct
1363 geolocation. But it could only do one trace at the time, did not have
1364 a sensor in Norway and did not make the geolocations easily available
1365 for postprocessing. So I contacted the developer and asked if he
1366 would be willing to share the code (he refused until he had time to
1367 clean it up), but he was interested in providing the geolocations in a
1368 machine readable format, and willing to set up a sensor in Norway. So
1369 since yesterday, it is possible to run traces from Norway in this
1370 service thanks to a sensor node set up by
1371 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1372 trace in KML format for further processing.&lt;/p&gt;
1373
1374 &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
1375 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;
1376
1377 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1378 Denmark, Germany, Holland and Ireland. Plenty of places where the
1379 Snowden confirmations verified the traffic is read by various actors
1380 without your best interest as their top priority.&lt;/p&gt;
1381
1382 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1383 over all the hosts behind the urls imported by www.stortinget.no and
1384 ask for the KML file from GeoTraceroute, and create a combined KML
1385 file with all the traces (unfortunately only one of the IP addresses
1386 behind the DNS name is traced this time. To get them all, one would
1387 have to request traces using IP number instead of DNS names from
1388 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1389
1390 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1391 the IP traffic moves and who control the boxes involved in moving it.
1392 And every time the link crosses for example the Swedish border, we can
1393 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1394 Britain and NSA in USA and cables around the globe. (Hm, what should
1395 we tell them? :) Keep that in mind if you ever send anything
1396 unencrypted over the Internet.&lt;/p&gt;
1397
1398 &lt;p&gt;PS: KML files are drawn using
1399 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1400 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1401 Marble. There are heaps of other options too.&lt;/p&gt;
1402
1403 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1404 activities, please send Bitcoin donations to my address
1405 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1406 </description>
1407 </item>
1408
1409 <item>
1410 <title>Appstream just learned how to map hardware to packages too!</title>
1411 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1413 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1414 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1415 readers probably know, I have been working on the
1416 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1417 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1418 it easier for users to figure out what to install to get a given piece
1419 of hardware to work in Debian, and a key part of this system is a way
1420 to map hardware to packages. Isenkram have its own mapping database,
1421 and also uses data provided by each package using the AppStream
1422 metadata format. And today,
1423 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1424 Debian learned to look up hardware the same way Isenkram is doing it,
1425 ie using fnmatch():&lt;/p&gt;
1426
1427 &lt;p&gt;&lt;pre&gt;
1428 % appstreamcli what-provides modalias \
1429 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1430 Identifier: pymissile [generic]
1431 Name: pymissile
1432 Summary: Control original Striker USB Missile Launcher
1433 Package: pymissile
1434 % appstreamcli what-provides modalias usb:v0694p0002d0000
1435 Identifier: libnxt [generic]
1436 Name: libnxt
1437 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1438 Package: libnxt
1439 ---
1440 Identifier: t2n [generic]
1441 Name: t2n
1442 Summary: Simple command-line tool for Lego NXT
1443 Package: t2n
1444 ---
1445 Identifier: python-nxt [generic]
1446 Name: python-nxt
1447 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1448 Package: python-nxt
1449 ---
1450 Identifier: nbc [generic]
1451 Name: nbc
1452 Summary: C compiler for LEGO Mindstorms NXT bricks
1453 Package: nbc
1454 %
1455 &lt;/pre&gt;&lt;/p&gt;
1456
1457 &lt;p&gt;A similar query can be done using the combined AppStream and
1458 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1459
1460 &lt;p&gt;&lt;pre&gt;
1461 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1462 pymissile
1463 % isenkram-lookup usb:v0694p0002d0000
1464 libnxt
1465 nbc
1466 python-nxt
1467 t2n
1468 %
1469 &lt;/pre&gt;&lt;/p&gt;
1470
1471 &lt;p&gt;You can find modalias values relevant for your machine using
1472 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1473
1474 &lt;p&gt;If you want to make this system a success and help Debian users
1475 make the most of the hardware they have, please
1476 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1477 AppStream metadata for your package following the guidelines&lt;/a&gt;
1478 documented in the wiki. So far only 11 packages provide such
1479 information, among the several hundred hardware specific packages in
1480 Debian. The Isenkram database on the other hand contain 101 packages,
1481 mostly related to USB dongles. Most of the packages with hardware
1482 mapping in AppStream are LEGO Mindstorms related, because I have, as
1483 part of my involvement in
1484 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1485 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1486 complete set of packages in Debian for that particular hardware. The
1487 team also got a nice Christmas present today. The
1488 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1489 package&lt;/a&gt; made it into Debian. With this package in place, it is
1490 now possible to use the LEGO Mindstorms NXT unit with only free
1491 software, as the nxt-firmware package contain the source and firmware
1492 binaries for the NXT brick.&lt;/p&gt;
1493
1494 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1495 activities, please send Bitcoin donations to my address
1496 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1497 </description>
1498 </item>
1499
1500 <item>
1501 <title>Isenkram updated with a lot more hardware-package mappings</title>
1502 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1504 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1505 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1506 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1507 and install packages to get your hardware dongles to work, is still
1508 going strong. It is a system to look up the hardware present on or
1509 connected to the current system, and map the hardware to Debian
1510 packages. It can either be done using the tools in isenkram-cli or
1511 using the user space daemon in the isenkram package. The latter will
1512 notify you, when inserting new hardware, about what packages to
1513 install to get the dongle working. It will even provide a button to
1514 click on to ask packagekit to install the packages.&lt;/p&gt;
1515
1516 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1517
1518 &lt;p&gt;&lt;pre&gt;
1519 % isenkram-lookup
1520 bluez
1521 cheese
1522 ethtool
1523 fprintd
1524 fprintd-demo
1525 gkrellm-thinkbat
1526 hdapsd
1527 libpam-fprintd
1528 pidgin-blinklight
1529 thinkfan
1530 tlp
1531 tp-smapi-dkms
1532 tp-smapi-source
1533 tpb
1534 %
1535 &lt;/pre&gt;&lt;/p&gt;
1536
1537 &lt;p&gt;It can also list the firware package providing firmware requested
1538 by the load kernel modules, which in my case is an empty list because
1539 I have all the firmware my machine need:
1540
1541 &lt;p&gt;&lt;pre&gt;
1542 % /usr/sbin/isenkram-autoinstall-firmware -l
1543 info: did not find any firmware files requested by loaded kernel modules. exiting
1544 %
1545 &lt;/pre&gt;&lt;/p&gt;
1546
1547 &lt;p&gt;The last few days I had a look at several of the around 250
1548 packages in Debian with udev rules. These seem like good candidates
1549 to install when a given hardware dongle is inserted, and I found
1550 several that should be proposed by isenkram. I have not had time to
1551 check all of them, but am happy to report that now there are 97
1552 packages packages mapped to hardware by Isenkram. 11 of these
1553 packages provide hardware mapping using AppStream, while the rest are
1554 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1555
1556 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1557 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1558 support using AppStream, for everyone to use:&lt;/p&gt;
1559
1560 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1561 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1562 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1563 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1564 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1565 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1566 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1567 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1568 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1569 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1570 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1571 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1572 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1573 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1574 pcscd, pidgin-blinklight, printer-driver-splix,
1575 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1576 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1577 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1578 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1579 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1580 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1581 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1582 xserver-xorg-video-vmware, yubikey-personalization and
1583 zd1211-firmware&lt;/p&gt;
1584
1585 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1586 bug report against the isenkram-cli package, and ask the package
1587 maintainer to
1588 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1589 metadata according to the guidelines&lt;/a&gt; to provide the information
1590 for everyone. In time, I hope to get rid of the isenkram specific
1591 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1592
1593 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1594 much hardware, and suggest that the package with with any ethernet
1595 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1596 the details. I hope the maintainer find time to address it soon. In
1597 the mean time I provide an override in isenkram.&lt;/p&gt;
1598 </description>
1599 </item>
1600
1601 <item>
1602 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1603 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1604 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1605 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1606 <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;
1607
1608 &lt;p&gt;In my early years, I played
1609 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1610 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1611 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1612 original Elite game was available on Commodore 64 and the IBM PC
1613 edition I played had a 64 KB executable. I am still impressed today
1614 that the authors managed to squeeze both a 3D engine and details about
1615 more than 2000 planet systems across 7 galaxies into a binary so
1616 small.&lt;/p&gt;
1617
1618 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1619 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1620 really have time to test it properly until a few days ago. It was
1621 great to discover that my old knowledge about trading routes were
1622 still valid. But my fighting and flying abilities were gone, so I had
1623 to retrain to be able to dock on a space station. And I am still not
1624 able to make much resistance when I am attacked by pirates, so I
1625 bougth and mounted the most powerful laser in the rear to be able to
1626 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1627
1628 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1629 everything on my own, and I had long lists of prices seen on different
1630 planets to be able to decide where to trade what. This time I had the
1631 advantages of the
1632 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1633 where information about each planet is easily available with common
1634 price ranges and suggested trading routes. This improved my ability
1635 to earn money and I have been able to earn enough to buy a lot of
1636 useful equipent in a few days. I believe I originally played for
1637 months before I could get a docking computer, while now I could get it
1638 after less then a week.&lt;/p&gt;
1639
1640 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1641 space, you should try out Oolite. It is available for Linux, MacOSX
1642 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1643
1644 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1645 activities, please send Bitcoin donations to my address
1646 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1647 </description>
1648 </item>
1649
1650 <item>
1651 <title>Quicker Debian installations using eatmydata</title>
1652 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1654 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1655 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1656 installation system, observing how using
1657 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1658 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1659 speedup around 20-40 percent for Debian Edu, where we install around
1660 1000 packages from within the installer. The eatmydata package
1661 provide a way to disable/delay file system flushing. This is a bit
1662 risky in the general case, as files that should be stored on disk will
1663 stay only in memory a bit longer than expected, causing problems if a
1664 machine crashes at an inconvenient time. But for an installation, if
1665 the machine crashes during installation the process is normally
1666 restarted, and avoiding disk operations as much as possible to speed
1667 up the process make perfect sense.
1668
1669 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1670 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1671 but did not have time to push it any further. But a few months ago I
1672 picked it up again and worked with the libeatmydata package maintainer
1673 Mattia Rizzolo to make it easier for everyone to get this installation
1674 speedup in Debian. Thanks to our cooperation There is now an
1675 eatmydata-udeb package in Debian testing and unstable, and simply
1676 enabling/installing it in debian-installer (d-i) is enough to get the
1677 quicker installations. It can be enabled using preseeding. The
1678 following untested kernel argument should do the trick:&lt;/p&gt;
1679
1680 &lt;blockquote&gt;&lt;pre&gt;
1681 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1682 &lt;/pre&gt;&lt;/blockquote&gt;
1683
1684 &lt;p&gt;This should ask d-i to install the package inside the d-i
1685 environment early in the installation sequence. Having it installed
1686 in d-i in turn will make sure the relevant scripts are called just
1687 after debootstrap filled /target/ with the freshly installed Debian
1688 system to configure apt to run dpkg with eatmydata. This is enough to
1689 speed up the installation process. There is a proposal to
1690 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1691 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1692 tested its impact.&lt;/p&gt;
1693
1694 </description>
1695 </item>
1696
1697 <item>
1698 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1699 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1701 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1702 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1703 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1704 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1705 elever over det ganske land skal levere inn hvert år. Det mange ikke
1706 vet er at selv om de kommersielle alternativene
1707 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1708 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1709 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1710 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1711 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1712 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1713 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1714 nynorsk, og få den automatoversatt til det andre skriftspråket.
1715 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1716 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1717 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1718 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1719 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1720 teksten din i webskjemaet der.
1721
1722 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1723 teknologien kan du enten installere pakken
1724 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1725 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1726 api.apertium.org. Se
1727 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1728 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1729 denne teksten som ble skrevet på bokmål over maskinoversatt til
1730 nynorsk.&lt;/p&gt;
1731
1732 &lt;hr/&gt;
1733
1734 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1735 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1736 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1737 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1738 veit er at sjølv om dei kommersielle alternativa
1739 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1740 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1741 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1742 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1743 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1744 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1745 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1746 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1747 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1748 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1749 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1750 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1751 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1752 teksta di i *webskjemaet der.
1753
1754 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1755 teknologien kan du anten installera pakken
1756 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1757 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1758 *api.*apertium.org. Sjå
1759 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1760 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1761 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1762 nynorsk.&lt;/p&gt;
1763 </description>
1764 </item>
1765
1766 <item>
1767 <title>Coz profiler for multi-threaded software is now in Debian</title>
1768 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1770 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1771 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1772 profiler able to run benchmarking experiments on the instrumented
1773 multi-threaded program, finally
1774 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1775 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1776 months since
1777 &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
1778 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1779 it suitable for Debian. There are still issues with clang
1780 compatibility, inline assembly only working x86 and minimized
1781 JavaScript libraries.&lt;/p&gt;
1782
1783 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1784
1785 &lt;p&gt;&lt;blockquote&gt;
1786 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1787 &lt;/blockquote&gt;&lt;/p&gt;
1788
1789 &lt;p&gt;This will produce a profile.coz file in the current working
1790 directory with the profiling information. This is then given to a
1791 JavaScript application provided in the package and available from
1792 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1793 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1794
1795 &lt;p&gt;&lt;blockquote&gt;
1796 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1797 &lt;/blockquote&gt;&lt;/p&gt;
1798
1799 &lt;p&gt;See the project home page and the
1800 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1801 ;login: article on Coz&lt;/a&gt; for more information on how it is
1802 working.&lt;/p&gt;
1803 </description>
1804 </item>
1805
1806 <item>
1807 <title>My own self balancing Lego Segway</title>
1808 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1809 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1810 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1811 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1812 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1813 present. It had been on my wishlist for a while, because I wanted to
1814 build a Segway like balancing lego robot. I had already built
1815 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1816 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1817 NXT kit as the balance sensor, but it was not working very well. It
1818 could balance for a while, but was very sensitive to the light
1819 condition in the room and the reflective properties of the surface and
1820 would fall over after a short while. I wanted something more robust,
1821 and had
1822 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1823 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1824 wishlist for some years before it suddenly showed up as a gift from my
1825 loved ones. :)&lt;/p&gt;
1826
1827 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1828 since then. But that changed some days ago, when I was searching for
1829 lego segway information and came across a recipe from HiTechnic for
1830 building
1831 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1832 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1833 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1834 code&lt;/a&gt; was included, so it was just a question of putting it all
1835 together. And thanks to the great work of many Debian developers, the
1836 compiler needed to build the source for the NXT is already included in
1837 Debian, so I was read to go in less than an hour. The resulting robot
1838 do not look very impressive in its simplicity:&lt;/p&gt;
1839
1840 &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;
1841
1842 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
1843 design from HiTechnic, I had to comment out the last task
1844 (taskControl). I simply placed /* and */ around it get the program
1845 working without that sensor present. Now it balances just fine until
1846 the battery status run low:&lt;/p&gt;
1847
1848 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
1849 &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;
1850 &lt;/video&gt;&lt;/p&gt;
1851
1852 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
1853 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
1854
1855 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
1856 they need to work with LEGO in Debian and all our derivative
1857 distributions like Ubuntu, check out
1858 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
1859 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
1860 RCX and NXT controller (no EV3), and would like to make sure the
1861 Debian tools needed to program the systems I own work as they
1862 should.&lt;/p&gt;
1863 </description>
1864 </item>
1865
1866 <item>
1867 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
1868 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
1869 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
1870 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
1871 <description>&lt;p&gt;In July
1872 &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
1873 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
1874 the ability to receive SMS messages (aka without a cell phone). It is
1875 time to share some experiences and provide an updated setup.&lt;/p&gt;
1876
1877 &lt;p&gt;The Signal app have worked fine for several months now, and I use
1878 it regularly to chat with my loved ones. I had a major snag at the
1879 end of my summer vacation, when the the app completely forgot my
1880 setup, identity and keys. The reason behind this major mess was
1881 running out of disk space. To avoid that ever happening again I have
1882 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
1883 roll back to an earlier version if the files are wiped by mistake. I
1884 had to use it once after introducing the git backup. When rolling
1885 back to an earlier version, one need to use the &#39;reset session&#39; option
1886 in Signal to get going, and notify the people you talk with about the
1887 problem. I assume there is some sequence number tracking in the
1888 protocol to detect rollback attacks. The git repository is rather big
1889 (674 MiB so far), but I have not tried to figure out if some of the
1890 content can be added to a .gitignore file due to lack of spare
1891 time.&lt;/p&gt;
1892
1893 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
1894 make it impossible to send messages using Signal. I could still
1895 receive them, but had to patch the code with a new timestamp to send.
1896 I believe the timeout is added by the developers to force people to
1897 upgrade to the latest version of the app, even when there is no
1898 protocol changes, to reduce the version skew among the user base and
1899 thus try to keep the number of support requests down.&lt;/p&gt;
1900
1901 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
1902 making the old patch fail to apply cleanly. Below is an updated
1903 patch, including the shell wrapper I use to start Signal. The
1904 original version required a new user to locate the JavaScript console
1905 and call a function from there. I got help from a friend with more
1906 JavaScript knowledge than me to modify the code to provide a GUI
1907 button instead. This mean that to get started you just need to run
1908 the wrapper and click the &#39;Register without mobile phone&#39; to get going
1909 now. I&#39;ve also modified the timeout code to always set it to 90 days
1910 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
1911
1912 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
1913
1914 &lt;ol&gt;
1915
1916 &lt;li&gt;First, install required packages to get the source code and the
1917 browser you need. Signal only work with Chrome/Chromium, as far as I
1918 know, so you need to install it.
1919
1920 &lt;pre&gt;
1921 apt install git tor chromium
1922 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1923 &lt;/pre&gt;&lt;/li&gt;
1924
1925 &lt;li&gt;Modify the source code using command listed in the the patch
1926 block below.&lt;/li&gt;
1927
1928 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
1929 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
1930
1931 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
1932 number you can receive calls to the next minute, receive the
1933 verification code and enter it into the form field and press
1934 &#39;Register&#39;. Note, the phone number you use will be user Signal
1935 username, ie the way others can find you on Signal.&lt;/li&gt;
1936
1937 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
1938 not show up in the contact list until you restart Signal, and there is
1939 no way to assign names to Contacts. There is also no way to create or
1940 update chat groups. I suspect this is because the web app do not have
1941 a associated contact database.&lt;/li&gt;
1942
1943 &lt;/ol&gt;
1944
1945 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
1946 main author moxie0 reject federation and accept dependencies to major
1947 corporations like Google (part of the code is fetched from Google) and
1948 Amazon (the central coordination point is owned by Amazon). See for
1949 example
1950 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
1951 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
1952 view on these issues. But the network effect is strong in this case,
1953 and several of the people I want to communicate with already use
1954 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
1955 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
1956 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
1957 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
1958 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
1959 working on Debian Stable.&lt;/p&gt;
1960
1961 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
1962 working. It switch to the production servers, disable to timeout,
1963 make registration easier and add the shell wrapper:&lt;/p&gt;
1964
1965 &lt;pre&gt;
1966 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
1967 diff --git a/js/background.js b/js/background.js
1968 index 24b4c1d..579345f 100644
1969 --- a/js/background.js
1970 +++ b/js/background.js
1971 @@ -33,9 +33,9 @@
1972 });
1973 });
1974
1975 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1976 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
1977 var SERVER_PORTS = [80, 4433, 8443];
1978 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1979 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1980 var messageReceiver;
1981 window.getSocketStatus = function() {
1982 if (messageReceiver) {
1983 diff --git a/js/expire.js b/js/expire.js
1984 index 639aeae..beb91c3 100644
1985 --- a/js/expire.js
1986 +++ b/js/expire.js
1987 @@ -1,6 +1,6 @@
1988 ;(function() {
1989 &#39;use strict&#39;;
1990 - var BUILD_EXPIRATION = 0;
1991 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
1992
1993 window.extension = window.extension || {};
1994
1995 diff --git a/js/views/install_view.js b/js/views/install_view.js
1996 index 7816f4f..1d6233b 100644
1997 --- a/js/views/install_view.js
1998 +++ b/js/views/install_view.js
1999 @@ -38,7 +38,8 @@
2000 return {
2001 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
2002 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
2003 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
2004 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
2005 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
2006 };
2007 },
2008 clearQR: function() {
2009 diff --git a/options.html b/options.html
2010 index dc0f28e..8d709f6 100644
2011 --- a/options.html
2012 +++ b/options.html
2013 @@ -14,7 +14,10 @@
2014 &amp;lt;div class=&#39;nav&#39;&gt;
2015 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
2016 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
2017 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
2018 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
2019 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
2020 +
2021 + &amp;lt;/div&gt;
2022 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
2023 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
2024 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
2025 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
2026 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
2027 @@ -0,0 +1,12 @@
2028 +#!/bin/sh
2029 +set -e
2030 +cd $(dirname $0)
2031 +mkdir -p userdata
2032 +userdata=&quot;`pwd`/userdata&quot;
2033 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
2034 + (cd $userdata &amp;&amp; git init)
2035 +fi
2036 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
2037 +exec chromium \
2038 + --proxy-server=&quot;socks://localhost:9050&quot; \
2039 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2040 EOF
2041 chmod a+rx run-signal-app
2042 &lt;/pre&gt;
2043
2044 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2045 activities, please send Bitcoin donations to my address
2046 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2047 </description>
2048 </item>
2049
2050 <item>
2051 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
2052 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
2053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
2054 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
2055 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2056 system&lt;/a&gt; provide a practical and easy way to figure out which
2057 packages support the hardware in a given machine. The command line
2058 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
2059 convenient way to list and install packages relevant for the current
2060 hardware during system installation, both user space packages and
2061 firmware packages. The GUI background daemon on the other hand provide
2062 a pop-up proposing to install packages when a new dongle is inserted
2063 while using the computer. For example, if you plug in a smart card
2064 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
2065 that package isn&#39;t already installed, and if you plug in a USB video
2066 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
2067 cheese is currently missing. This already work just fine.&lt;/p&gt;
2068
2069 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
2070 package names. When I started no such database existed in Debian, so
2071 I made my own data set and included it with the isenkram package and
2072 made isenkram fetch the latest version of this database from git using
2073 http. This way the isenkram users would get updated package proposals
2074 as soon as I learned more about hardware related packages.&lt;/p&gt;
2075
2076 &lt;p&gt;The hardware is identified using modalias strings. The modalias
2077 design is from the Linux kernel where most hardware descriptors are
2078 made available as a strings that can be matched using filename style
2079 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2080 identifiers.&lt;/p&gt;
2081
2082 &lt;p&gt;The downside to the Isenkram specific database is that there is no
2083 information about relevant distribution / Debian version, making
2084 isenkram propose obsolete packages too. But along came AppStream, a
2085 cross distribution mechanism to store and collect metadata about
2086 software packages. When I heard about the proposal, I contacted the
2087 people involved and suggested to add a hardware matching rule using
2088 modalias strings in the specification, to be able to use AppStream for
2089 mapping hardware to packages. This idea was accepted and AppStream is
2090 now a great way for a package to announce the hardware it support in a
2091 distribution neutral way. I wrote
2092 &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
2093 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
2094 December. If you have a hardware related package in Debian, please
2095 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
2096
2097 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
2098 RCX or NXT unit, announce this support using AppStream. The effect is
2099 that when you insert such LEGO robot controller into your Debian
2100 machine, Isenkram will propose to install the packages needed to get
2101 it working. The intention is that this should allow the local user to
2102 start programming his robot controller right away without having to
2103 guess what packages to use or which permissions to fix.&lt;/p&gt;
2104
2105 &lt;p&gt;But when I sat down with my son the other day to program our NXT
2106 unit using his Debian Stretch computer, I discovered something
2107 annoying. The local console user (ie my son) did not get access to
2108 the USB device for programming the unit. This used to work, but no
2109 longer in Jessie and Stretch. After some investigation and asking
2110 around on #debian-devel, I discovered that this was because udev had
2111 changed the mechanism used to grant access to local devices. The
2112 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
2113 no longer applied, because LDAP users no longer was added to the
2114 plugdev group during login. Michael Biebl told me that this method
2115 was obsolete and the new method used ACLs instead. This was good
2116 news, as the plugdev mechanism is a mess when using a remote user
2117 directory like LDAP. Using ACLs would make sure a user lost device
2118 access when she logged out, even if the user left behind a background
2119 process which would retain the plugdev membership with the ConsoleKit
2120 setup. Armed with this knowledge I moved on to fix the access problem
2121 for the LEGO Mindstorms related packages.&lt;/p&gt;
2122
2123 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
2124 applied directly for a device, or is applied in
2125 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
2126 LEGO Mindstorms udev rules did not have a class, I decided to add the
2127 tag directly in the udev rules files included in the packages. Here
2128 is one example. For the nqc C compiler for the RCX, the
2129 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
2130
2131 &lt;p&gt;&lt;pre&gt;
2132 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
2133 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
2134 &lt;/pre&gt;&lt;/p&gt;
2135
2136 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
2137 packages using plugdev in their /lib/udev/rules.d/ files should be
2138 changed to use this tag (either directly or indirectly via
2139 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
2140 to detect this?&lt;/p&gt;
2141
2142 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
2143 It is unclear to me if the uaccess tag is an internal implementation
2144 detail like the udev-acl tag used by
2145 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
2146 indirect method is the preferred way. Michael
2147 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
2148 documentation from the systemd project&lt;/a&gt; and I hope it will make
2149 this clearer. For now I use the generic classes when they exist and
2150 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
2151 directly if no such class exist.&lt;/p&gt;
2152
2153 &lt;p&gt;To learn more about the isenkram system, please check out
2154 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2155 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2156
2157 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
2158 please join us on our IRC channel
2159 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
2160 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
2161 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
2162 list is not yet created, but we are working on it. :)&lt;/p&gt;
2163
2164 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2165 activities, please send Bitcoin donations to my address
2166 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2167 </description>
2168 </item>
2169
2170 <item>
2171 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
2172 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
2173 <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>
2174 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
2175 <description>&lt;p&gt;In April we
2176 &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
2177 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
2178 how to set up and administrate a Debian system. Today I am happy to
2179 report that the first draft is now publicly available. You can find
2180 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
2181 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
2182 eight chapters have a first draft translation, and we are working on
2183 proofreading the content. If you want to help out, please start
2184 contributing using
2185 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2186 hosted weblate project page&lt;/a&gt;, and get in touch using
2187 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2188 translators mailing list&lt;/a&gt;. Please also check out
2189 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2190 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
2191 and update weblate if you find errors.&lt;/p&gt;
2192
2193 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
2194 electronic form.&lt;/p&gt;
2195 </description>
2196 </item>
2197
2198 <item>
2199 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
2200 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
2201 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
2202 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
2203 <description>&lt;p&gt;This summer, I read a great article
2204 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
2205 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
2206 how to profile multi-threaded programs. It presented a system for
2207 profiling software by running experiences in the running program,
2208 testing how run time performance is affected by &quot;speeding up&quot; parts of
2209 the code to various degrees compared to a normal run. It does this by
2210 slowing down parallel threads while the &quot;faster up&quot; code is running
2211 and measure how this affect processing time. The processing time is
2212 measured using probes inserted into the code, either using progress
2213 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2214 can also measure unmodified code by measuring complete the program
2215 runtime and running the program several times instead.&lt;/p&gt;
2216
2217 &lt;p&gt;The project and presentation was so inspiring that I would like to
2218 get the system into Debian. I
2219 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
2220 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
2221 system ready for Debian by sending patches. The build process need to
2222 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
2223 to include the JavaScript web page used to visualize the collected
2224 profiling information included in the source package.
2225 But I expect that should work out fairly soon.&lt;/p&gt;
2226
2227 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
2228 on a binary with debug symbols available, start the program like this:
2229
2230 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2231 coz run --- program-to-run
2232 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2233
2234 &lt;p&gt;This will create a text file profile.coz with the instrumentation
2235 information. To show what part of the code affect the performance
2236 most, use a web browser and either point it to
2237 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
2238 or use the copy from git (in the gh-pages branch). Check out this web
2239 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
2240 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
2241 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2242 code, rebuild and run the profiler. This allow coz to do more
2243 targeted experiments.&lt;/p&gt;
2244
2245 &lt;p&gt;A video published by ACM
2246 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
2247 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
2248 from the 25th Symposium on Operating Systems Principles available
2249 titled
2250 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
2251 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
2252
2253 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
2254 for Coz is available from github. It will only build with clang
2255 because it uses a
2256 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
2257 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
2258 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
2259 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
2260
2261 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
2262 of software in Debian. I would very much like some help with the
2263 packaging effort, as I lack the in depth knowledge on how to package
2264 C++ libraries.&lt;/p&gt;
2265 </description>
2266 </item>
2267
2268 <item>
2269 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
2270 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
2271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
2272 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
2273 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2274 to be a slight challenge. Here is the recipe if I ever need to do it
2275 again. It all started by me wanting to try the recipe to set up
2276 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
2277 hardened Android installation&lt;/a&gt; from the Tor project blog on a
2278 device I had access to. It is a old mobile phone with a broken
2279 microphone The initial idea had been to just
2280 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
2281 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
2282 until a few days ago.&lt;/p&gt;
2283
2284 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
2285 loader (press volume down and power at the same time), (2) select
2286 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
2287 machine, (4) request the device identifier token by running &#39;fastboot
2288 oem get_identifier_token&#39;, (5) request the device unlocking key using
2289 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
2290 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
2291
2292 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
2293 or newer, and the device I was working on had 2.00.0027. This
2294 apparently can be easily fixed by downloading a Windows program and
2295 running it on your Windows machine, if you accept the terms Microsoft
2296 require you to accept to use Windows - which I do not. So I had to
2297 come up with a different approach. I got a lot of help from AndyCap
2298 on #nuug, and would not have been able to get this working without
2299 him.&lt;/p&gt;
2300
2301 &lt;p&gt;First I needed to extract the hboot firmware from
2302 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
2303 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
2304 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
2305 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
2306 recognise the file format, but unruu worked and extracted rom.zip,
2307 containing the new hboot firmware and a text file describing which
2308 devices it would work for.&lt;/p&gt;
2309
2310 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
2311 followed some instructions
2312 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
2313 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
2314 machine with Debian testing:&lt;/p&gt;
2315
2316 &lt;p&gt;&lt;pre&gt;
2317 adb reboot-bootloader
2318 fastboot oem rebootRUU
2319 fastboot flash zip rom.zip
2320 fastboot flash zip rom.zip
2321 fastboot reboot
2322 &lt;/pre&gt;&lt;/p&gt;
2323
2324 &lt;p&gt;The flash command apparently need to be done twice to take effect,
2325 as the first is just preparations and the second one do the flashing.
2326 The adb command is just to get to the boot loader menu, so turning the
2327 device on while holding volume down and the power button should work
2328 too.&lt;/p&gt;
2329
2330 &lt;p&gt;With the new hboot version in place I could start following the
2331 instructions on the HTC developer web site. I got the device token
2332 like this:&lt;/p&gt;
2333
2334 &lt;p&gt;&lt;pre&gt;
2335 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
2336 &lt;/pre&gt;
2337
2338 &lt;p&gt;And once I got the unlock code via email, I could use it like
2339 this:&lt;/p&gt;
2340
2341 &lt;p&gt;&lt;pre&gt;
2342 fastboot flash unlocktoken Unlock_code.bin
2343 &lt;/pre&gt;&lt;/p&gt;
2344
2345 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2346 could start stuffing the software of my own choosing into the device.
2347 So far I only inserted a replacement recovery image to wipe the phone
2348 before I start. We will see what happen next. Perhaps I should
2349 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2350 </description>
2351 </item>
2352
2353 <item>
2354 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2355 <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>
2356 <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>
2357 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2358 <description>&lt;p&gt;For a while now, I have wanted to test
2359 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2360 said to provide end to end encrypted communication and several of my
2361 friends and family are already using it. As I by choice do not own a
2362 mobile phone, this proved to be harder than expected. And I wanted to
2363 have the source of the client and know that it was the code used on my
2364 machine. But yesterday I managed to get it working. I used the
2365 Github source, compared it to the source in
2366 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2367 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2368 patches to use the production Signal servers, started the app and
2369 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2370 the recipe how I did it.&lt;/p&gt;
2371
2372 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2373
2374 &lt;pre&gt;
2375 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2376 &lt;/pre&gt;
2377
2378 &lt;p&gt;Next, I patched the source to use the production servers, to be
2379 able to talk to other Signal users:&lt;/p&gt;
2380
2381 &lt;pre&gt;
2382 cat &amp;lt;&amp;lt;EOF | patch -p0
2383 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2384 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2385 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2386 @@ -47,8 +47,8 @@
2387 });
2388 });
2389
2390 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2391 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2392 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2393 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2394 var messageReceiver;
2395 window.getSocketStatus = function() {
2396 if (messageReceiver) {
2397 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2398 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2399 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2400 @@ -1,6 +1,6 @@
2401 ;(function() {
2402 &#39;use strict&#39;;
2403 - var BUILD_EXPIRATION = 0;
2404 + var BUILD_EXPIRATION = 1474492690000;
2405
2406 window.extension = window.extension || {};
2407
2408 EOF
2409 &lt;/pre&gt;
2410
2411 &lt;p&gt;The first part is changing the servers, and the second is updating
2412 an expiration timestamp. This timestamp need to be updated regularly.
2413 It is set 90 days in the future by the build process (Gruntfile.js).
2414 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2415
2416 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2417 script to launch Signal in Chromium.&lt;/p&gt;
2418
2419 &lt;pre&gt;
2420 #!/bin/sh
2421 cd $(dirname $0)
2422 mkdir -p userdata
2423 exec chromium \
2424 --proxy-server=&quot;socks://localhost:9050&quot; \
2425 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2426 &lt;/pre&gt;
2427
2428 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2429 SOCKS5 proxy to make sure those controlling the Signal servers (today
2430 Amazon and Whisper Systems) as well as those listening on the lines
2431 will have a harder time location my laptop based on the Signal
2432 connections if they use source IP address.&lt;/p&gt;
2433
2434 &lt;p&gt;When the script starts, one need to follow the instructions under
2435 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2436 repository. I right clicked on the Signal window to get up the
2437 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2438 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2439 registration form. Then I entered by land line phone number and
2440 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2441 repeated the verification code three times. After entering the number
2442 into the verification code field in the form, I could start using
2443 Signal from my laptop.
2444
2445 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2446 whom and thus who know who to those controlling the central server,
2447 but such leakage is hard to avoid with a centrally controlled server
2448 setup. It is something to keep in mind when using Signal - the
2449 content of your chats are harder to intercept, but the meta data
2450 exposing your contact network is available to people you do not know.
2451 So better than many options, but not great. And sadly the usage is
2452 connected to my land line, thus allowing those controlling the server
2453 to associate it to my home and person. I would prefer it if only
2454 those I knew could tell who I was on Signal. There are options
2455 avoiding such information leakage, but most of my friends are not
2456 using them, so I am stuck with Signal for now.&lt;/p&gt;
2457
2458 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2459 on this topic in
2460 &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
2461 and updated recipe for using the Signal app without a mobile
2462 phone&lt;/a&gt;.&lt;/p&gt;
2463 </description>
2464 </item>
2465
2466 <item>
2467 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2468 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2470 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2471 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2472 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2473 multimedia player in Debian claimed to support most file formats /
2474 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2475 the various players claimed support for. The range was from 55 to 130
2476 MIME types. I suspect most media formats are supported by all
2477 players, but this is not really reflected in the MimeTypes values in
2478 their desktop files. There are probably also some bogus MIME types
2479 listed, but it is hard to identify which one this is.&lt;/p&gt;
2480
2481 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2482 the players suggesting to add more MIME types to their desktop files,
2483 and decided to spend some time myself improving the situation for my
2484 favorite media player VLC. The fixes for VLC entered Debian unstable
2485 yesterday. The complete list of MIME types can be seen on the
2486 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2487 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2488
2489 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2490 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2491 kmplayer. I am sure some of the other players desktop files support
2492 several of the formats currently listed as working only with vlc,
2493 toten and parole.&lt;/p&gt;
2494
2495 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2496 supported by all the tested multimedia players in Debian in their
2497 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2498 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2499 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2500 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2501 it sad that video/ogg and video/webm is not supported by all the media
2502 players in Debian. As far as I can tell, all of them can handle both
2503 formats.&lt;/p&gt;
2504 </description>
2505 </item>
2506
2507 <item>
2508 <title>A program should be able to open its own files on Linux</title>
2509 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2511 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2512 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2513 decided to test its presentation tool when making the slides for a
2514 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2515 wrote the first draft of the slides, saved the result and went to bed
2516 the day before I would give the talk. The next day I took a plane to
2517 the location where the meeting should take place, and on the plane I
2518 started up koffice again to polish the talk a bit, only to discover
2519 that kpresenter refused to load its own data file. I cursed a bit and
2520 started making the slides again from memory, to have something to
2521 present when I arrived. I tested that the saved files could be
2522 loaded, and the day seemed to be rescued. I continued to polish the
2523 slides until I suddenly discovered that the saved file could no longer
2524 be loaded into kpresenter. In the end I had to rewrite the slides
2525 three times, condensing the content until the talk became shorter and
2526 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2527 kpresenter wrote inline images in a way itself could not understand.
2528 Eventually that bug was fixed and kpresenter ended up being a great
2529 program to make slides. The point I&#39;m trying to make is that we
2530 expect a program to be able to load its own data files, and it is
2531 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2532
2533 &lt;p&gt;Did you ever experience a program failing to load its own data
2534 files from the desktop file browser? It is not a uncommon problem. A
2535 while back I discovered that the screencast recorder
2536 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2537 browser would refuse to open. No video player claimed to understand
2538 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2539 returning the application/ogg MIME type, which no video player I had
2540 installed listed as a MIME type they would understand. I asked for
2541 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2542 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2543 several video players to add video/ogg to their desktop files, to give
2544 the file browser an idea what to do about Ogg Theora files. After a
2545 while, the desktop file browsers in Debian started to handle the
2546 output from gtk-recordmydesktop properly.&lt;/p&gt;
2547
2548 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2549 system Rosegarden again, and I discovered that the KDE and xfce file
2550 browsers did not know what to do with the Rosegarden project files
2551 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2552 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2553 included in the next upload. To increase the chance of me remembering
2554 how to fix the problem next time some program fail to load its files
2555 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2556
2557 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2558 There are two sources for the MIME type of a given file. The output from
2559 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2560 shared MIME type registry (under /usr/share/mime/). The file MIME
2561 type is mapped to programs supporting the MIME type, and this
2562 information is collected from
2563 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2564 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2565 one desktop file claiming support for the MIME type of the file, it is
2566 activated when asking to open a given file. If there are more, one
2567 can normally select which one to use by right-clicking on the file and
2568 selecting the wanted one using &#39;Open with&#39; or similar. In general
2569 this work well. But it depend on each program picking a good MIME
2570 type (preferably
2571 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2572 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2573 registry recognizing the file and the desktop file to list the MIME
2574 type in its list of supported MIME types.&lt;/p&gt;
2575
2576 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2577 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2578 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2579
2580 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2581 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2582 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2583 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2584 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2585 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2586 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2587 &amp;lt;/mime-type&amp;gt;
2588 &amp;lt;/mime-info&amp;gt;
2589 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2590
2591 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2592 (it is a gzipped XML file). Note, it is much better to use an
2593 official MIME type registered with IANA than it is to make up ones own
2594 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2595
2596 &lt;p&gt;The desktop file of the rosegarden program failed to list
2597 audio/x-rosegarden in its list of supported MIME types, causing the
2598 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2599
2600 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2601 % grep Mime /usr/share/applications/rosegarden.desktop
2602 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2603 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2604 %
2605 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2606
2607 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2608 MimeType= line.&lt;/p&gt;
2609
2610 &lt;p&gt;If you run into a file which fail to open the correct program when
2611 selected from the file browser, please check out the output from
2612 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2613 MIME type is registered somewhere under /usr/share/mime/ and check
2614 that some desktop file under /usr/share/applications/ is claiming
2615 support for this MIME type. If not, please report a bug to have it
2616 fixed. :)&lt;/p&gt;
2617 </description>
2618 </item>
2619
2620 <item>
2621 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2622 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2624 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2625 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2626 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2627 related packages. The idea is to have a database of mappings between
2628 hardware and packages, and pop up a dialog suggesting for the user to
2629 install the packages to use a given hardware dongle. Some use cases
2630 are when you insert a Yubikey, it proposes to install the software
2631 needed to control it; when you insert a braille reader list it
2632 proposes to install the packages needed to send text to the reader;
2633 and when you insert a ColorHug screen calibrator it suggests to
2634 install the driver for it. The system work well, and even have a few
2635 command line tools to install firmware packages and packages for the
2636 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2637
2638 &lt;p&gt;The system was initially written using aptdaemon, because I found
2639 good documentation and example code on how to use it. But aptdaemon
2640 is going away and is generally being replaced by
2641 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2642 so Isenkram needed a rewrite. And today, thanks to the great patch
2643 from my college Sunil Mohan Adapa in the FreedomBox project, the
2644 rewrite finally took place. I&#39;ve just uploaded a new version of
2645 Isenkram into Debian Unstable with the patch included, and the default
2646 for the background daemon is now to use PackageKit. To check it out,
2647 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2648 and see if it is recognised.&lt;/p&gt;
2649
2650 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2651 the machine it is running on, you can check out the isenkram-lookup
2652 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2653
2654 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2655 % isenkram-lookup
2656 bluez
2657 cheese
2658 fprintd
2659 fprintd-demo
2660 gkrellm-thinkbat
2661 hdapsd
2662 libpam-fprintd
2663 pidgin-blinklight
2664 thinkfan
2665 tleds
2666 tp-smapi-dkms
2667 tp-smapi-source
2668 tpb
2669 %p
2670 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2671
2672 &lt;p&gt;The hardware mappings come from several places. The preferred way
2673 is for packages to announce their hardware support using
2674 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2675 cross distribution appstream system&lt;/a&gt;.
2676 See
2677 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2678 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2679 </description>
2680 </item>
2681
2682 <item>
2683 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2684 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2686 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2687 <description>&lt;p&gt;Yesterday I updated the
2688 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2689 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2690 enterprising users. There were some nice user and visible changes.
2691 First of all, both desktop menu entries now work. A design flaw in
2692 one of the script made the history graph fail to show up (its PNG was
2693 dumped in ~/.xsession-errors) if no controlling TTY was available.
2694 The script worked when called from the command line, but not when
2695 called from the desktop menu. I changed this to look for a DISPLAY
2696 variable or a TTY before deciding where to draw the graph, and now the
2697 graph window pop up as expected.&lt;/p&gt;
2698
2699 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2700 graphs (the one showing the last few hours). New is also the user of
2701 colours showing charging in blue and discharge in red. The percentages
2702 of this graph is relative to last full charge, not battery design
2703 capacity.&lt;/p&gt;
2704
2705 &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;
2706
2707 &lt;p&gt;The other graph show the entire history of the collected battery
2708 statistics, comparing it to the design capacity of the battery to
2709 visualise how the battery life time get shorter over time. The red
2710 line in this graph is what the previous graph considers 100 percent:
2711
2712 &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;
2713
2714 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2715 percent of last full capacity, and how the capacity of the battery is
2716 shrinking. :(&lt;/p&gt;
2717
2718 &lt;p&gt;The last new feature is in the collector, which now will handle
2719 more hardware models. On some hardware, Linux power supply
2720 information is stored in /sys/class/power_supply/ACAD/, while the
2721 collector previously only looked in /sys/class/power_supply/AC/. Now
2722 both are checked to figure if there is power connected to the
2723 machine.&lt;/p&gt;
2724
2725 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2726 check out the
2727 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2728 in Debian unstable, or rebuild it on Jessie to get it working on
2729 Debian stable. :) The upstream source is available from &lt;a
2730 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2731 Patches are very welcome.&lt;/p&gt;
2732
2733 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2734 activities, please send Bitcoin donations to my address
2735 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2736 </description>
2737 </item>
2738
2739 <item>
2740 <title>Debian now with ZFS on Linux included</title>
2741 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2743 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2744 <description>&lt;p&gt;Today, after many years of hard work from many people,
2745 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2746 Debian. The package status can be seen on
2747 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2748 for zfs-linux&lt;/a&gt;. and
2749 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2750 team status page&lt;/a&gt;. If you want to help out, please join us.
2751 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2752 source code&lt;/a&gt; is available via git on Alioth. It would also be
2753 great if you could help out with
2754 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2755 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2756 </description>
2757 </item>
2758
2759 <item>
2760 <title>What is the best multimedia player in Debian?</title>
2761 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2763 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2764 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2765 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2766
2767 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2768 plugins in Debian, to get an idea which plugins to include in Debian
2769 Edu. I created a script to extract the set of supported MIME types
2770 for each plugin, and used this to find out which multimedia browser
2771 plugin supported most file formats / media types.
2772 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2773 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2774 not been updated for a while. But browser plugins are less relevant
2775 these days, so I thought it was time to look at standalone
2776 players.&lt;/p&gt;
2777
2778 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2779 player when I wanted to play videos from the Norwegian National
2780 Broadcasting Company, and decided to investigate why. The cause is a
2781 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2782 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2783 of MIME types announced in the desktop file and the browser plugin,
2784 only to discover that there is quite a large difference between the
2785 two for VLC. This discovery made me dig up the script I used to
2786 compare browser plugins, and adjust it to compare desktop files
2787 instead, to try to figure out which multimedia player in Debian
2788 support most file formats.&lt;/p&gt;
2789
2790 &lt;p&gt;The result can be seen on the Debian Wiki, as
2791 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2792 table listing all MIME types supported by one of the packages included
2793 in the table&lt;/a&gt;, with the package supporting most MIME types being
2794 listed first in the table.&lt;/p&gt;
2795
2796 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2797 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2798 kmplayer. Time for the other players to update their announced MIME
2799 support?&lt;/p&gt;
2800 </description>
2801 </item>
2802
2803 <item>
2804 <title>The Pyra - handheld computer with Debian preinstalled</title>
2805 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2807 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2808 <description>A friend of mine made me aware of
2809 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2810 handheld computer which will be delivered with Debian preinstalled. I
2811 would love to get one of those for my birthday. :)&lt;/p&gt;
2812
2813 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2814 plugs and many others connectors, and include a full keyboard and a 5&quot;
2815 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2816 day of battery life time, but I have not seen any independent tests
2817 confirming this. The vendor is still collecting preorders, and the
2818 last I heard last night was that 22 more orders were needed before
2819 production started.&lt;/p&gt;
2820
2821 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2822 Debian. Please let me know if you know of any others. Is it the
2823 first computer being sold with Debian preinstalled?&lt;/p&gt;
2824 </description>
2825 </item>
2826
2827 <item>
2828 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2829 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2830 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2831 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2832 <description>&lt;p&gt;During this weekends
2833 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2834 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
2835 to make sure there are good books about Debian available in Norwegian
2836 Bokmål, and got in touch with the people behind the
2837 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
2838 project&lt;/a&gt; to get started. If you want to help out, please start
2839 contributing using
2840 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2841 hosted weblate project page&lt;/a&gt;, and get in touch using
2842 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2843 translators mailing list&lt;/a&gt;. Please also check out
2844 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2845 contributors&lt;/a&gt;.&lt;/p&gt;
2846
2847 &lt;p&gt;The book is already available on paper in English, French and
2848 Japanese, and our goal is to get it available on paper in Norwegian
2849 Bokmål too. In addition to the paper edition, there are also EPUB and
2850 Mobi versions available. And there are incomplete translations
2851 available for many more languages.&lt;/p&gt;
2852 </description>
2853 </item>
2854
2855 <item>
2856 <title>One in two hundred Debian users using ZFS on Linux?</title>
2857 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
2858 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
2859 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
2860 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
2861 packages in Debian, and was quite surprised with what I found. I use
2862 ZFS myself at home, but did not really expect many others to do so.
2863 But I might be wrong.&lt;/p&gt;
2864
2865 &lt;p&gt;According to
2866 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
2867 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
2868 0.53% of the population, with the package installed. As far as I know
2869 the only use of the spl-linux package is as a support library for ZFS
2870 on Linux, so I use it here as proxy for measuring the number of ZFS
2871 installation on Linux in Debian. In the kFreeBSD variant of Debian
2872 the ZFS feature is already available, and there
2873 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
2874 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
2875 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
2876
2877 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
2878 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
2879 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
2880 cleared, the package is still not in Debian. The package is again in
2881 the NEW queue. Several uploads have been rejected so far because the
2882 debian/copyright file was incomplete or wrong, but there is no reason
2883 to give up. The current status can be seen on
2884 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2885 team status page&lt;/a&gt;, and
2886 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
2887 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
2888
2889 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
2890 my home server can function in the future using only official Debian
2891 packages, and the current blocker is to get the debian/copyright file
2892 accepted by the FTP masters in Debian, I decided a while back to try
2893 to help out the team. This was the background for my blog post about
2894 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
2895 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
2896 used the techniques I explored there to try to find any errors in the
2897 copyright file. It is not very easy to check every one of the around
2898 2000 files in the source package, but I hope we this time got it
2899 right. If you want to help out, check out the git source and try to
2900 find missing entries in the debian/copyright file.&lt;/p&gt;
2901 </description>
2902 </item>
2903
2904 <item>
2905 <title>Full battery stats collector is now available in Debian</title>
2906 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
2907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
2908 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
2909 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
2910 extended collector that will collect the complete battery history for
2911 later processing and graphing. The original collector store the
2912 battery level as percentage of last full level, while the new
2913 collector also record battery vendor, model, serial number, design
2914 full level, last full level and current battery level. This make it
2915 possible to predict the lifetime of the battery as well as visualise
2916 the energy flow when the battery is charging or discharging.&lt;/p&gt;
2917
2918 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
2919 in the version 0.5.1 package in unstable. Get the new battery level graph
2920 and lifetime prediction by running:
2921
2922 &lt;p&gt;&lt;pre&gt;
2923 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2924 &lt;/pre&gt;&lt;/p&gt;
2925
2926 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
2927
2928 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
2929 entry yet):&lt;/p&gt;
2930
2931 &lt;p&gt;&lt;pre&gt;
2932 /usr/share/battery-stats/battery-stats-graph-flow
2933 &lt;/pre&gt;&lt;/p&gt;
2934
2935 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
2936 when there are few data points. The graphs look a bit better with a
2937 few years of data.&lt;/p&gt;
2938
2939 &lt;p&gt;A while back one important feature I use in the battery stats
2940 collector broke in Debian. The scripts in
2941 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
2942 suspect it happened when Jessie started using systemd, but I do not
2943 know. The issue is reported as
2944 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
2945 pm-utils. I managed to work around it by adding an udev rule to call
2946 the collector script every time the power connector is connected and
2947 disconnected. With this fix in place it was finally time to make a
2948 new release of the package, and get it into Debian.&lt;/p&gt;
2949
2950 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2951 check out the
2952 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2953 in Debian unstable, or rebuild it on Jessie to get it working on
2954 Debian stable. :) The upstream source is available from
2955 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2956 As always, patches are very welcome.&lt;/p&gt;
2957 </description>
2958 </item>
2959
2960 <item>
2961 <title>Making battery measurements a little easier in Debian</title>
2962 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
2963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
2964 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
2965 <description>&lt;p&gt;Back in September, I blogged about
2966 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
2967 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
2968 how it showed the decay and death of this battery (now replaced). I
2969 created a simple deb package to handle the collection and graphing,
2970 but did not want to upload it to Debian as there were already
2971 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
2972 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
2973 a point of uploading a competing package when battery-stats could be
2974 fixed instead. I reported a few bugs about its non-function, and
2975 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
2976
2977 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
2978 hands. The end result is that I am now the new upstream developer of
2979 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
2980 battery-stats in Debian, and the package in Debian unstable is finally
2981 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
2982 information provided by the Linux kernel. If you install the
2983 battery-stats package from unstable now, you will be able to get a
2984 graph of the current battery fill level, to get some idea about the
2985 status of the battery. The source package build and work just fine in
2986 Debian testing and stable (and probably oldstable too, but I have not
2987 tested). The default graph you get for that system look like this:&lt;/p&gt;
2988
2989 &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;
2990
2991 &lt;p&gt;My plans for the future is to merge my old scripts into the
2992 battery-stats package, as my old scripts collected a lot more details
2993 about the battery. The scripts are merged into the upstream
2994 battery-stats git repository already, but I am not convinced they work
2995 yet, as I changed a lot of paths along the way. Will have to test a
2996 bit more before I make a new release.&lt;/p&gt;
2997
2998 &lt;p&gt;I will also consider changing the file format slightly, as I
2999 suspect the way I combine several values into one field might make it
3000 impossible to know the type of the value when using it for processing
3001 and graphing.&lt;/p&gt;
3002
3003 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
3004 battery, check out the battery-stats package in
3005 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
3006 on
3007 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3008 I would love some help to improve the system further.&lt;/p&gt;
3009 </description>
3010 </item>
3011
3012 <item>
3013 <title>Creating, updating and checking debian/copyright semi-automatically</title>
3014 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
3015 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
3016 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
3017 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
3018 details. And one of the details is the content of the
3019 debian/copyright file, which should list all relevant licenses used by
3020 the code in the package in question, preferably in
3021 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
3022 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
3023
3024 &lt;p&gt;For large packages with lots of contributors it is hard to write
3025 and update this file manually, and if you get some detail wrong, the
3026 package is normally rejected by the ftpmasters. So getting it right
3027 the first time around get the package into Debian faster, and save
3028 both you and the ftpmasters some work.. Today, while trying to figure
3029 out what was wrong with
3030 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
3031 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
3032 figuring out the options for doing this job automatically, or at least
3033 semi-automatically.&lt;/p&gt;
3034
3035 &lt;p&gt;Lucikly, there are at least two tools available for generating the
3036 file based on the code in the source package,
3037 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
3038 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
3039 not sure which one of them came first, but both seem to be able to
3040 create a sensible draft file. As far as I can tell, none of them can
3041 be trusted to get the result just right, so the content need to be
3042 polished a bit before the file is OK to upload. I found the debmake
3043 option in
3044 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
3045 blog posts from 2014&lt;/a&gt;.
3046
3047 &lt;p&gt;To generate using debmake, use the -cc option:
3048
3049 &lt;p&gt;&lt;pre&gt;
3050 debmake -cc &gt; debian/copyright
3051 &lt;/pre&gt;&lt;/p&gt;
3052
3053 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
3054 this might not be the best option.&lt;/p&gt;
3055
3056 &lt;p&gt;The cme option is based on a config parsing library, and I found
3057 this approach in
3058 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
3059 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
3060 dpkg-copyright&#39; option:
3061
3062 &lt;p&gt;&lt;pre&gt;
3063 cme update dpkg-copyright
3064 &lt;/pre&gt;&lt;/p&gt;
3065
3066 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
3067 handle UTF-8 names better than debmake.&lt;/p&gt;
3068
3069 &lt;p&gt;When the copyright file is created, I would also like some help to
3070 check if the file is correct. For this I found two good options,
3071 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
3072 to focus on license types and file matching, and is able to detect
3073 ineffective blocks in the copyright file. The latter reports missing
3074 copyright holders and years, but was confused by inconsistent license
3075 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
3076 fix all issues reported by them before uploading. But I do not know
3077 if the tools and the ftpmasters agree on what is important to fix in a
3078 copyright file, so the package might still be rejected.&lt;/p&gt;
3079
3080 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
3081 will read through the source and try to find all copyright statements.
3082 It is not comparing the result to the content of debian/copyright, but
3083 can be useful when verifying the content of the copyright file.&lt;/p&gt;
3084
3085 &lt;p&gt;Are you aware of better tools in Debian to create and update
3086 debian/copyright file. Please let me know, or blog about it on
3087 planet.debian.org.&lt;/p&gt;
3088
3089 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3090 activities, please send Bitcoin donations to my address
3091 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3092
3093 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
3094 on how to use licensecheck and cdbs to create a draft copyright file
3095
3096 &lt;p&gt;&lt;pre&gt;
3097 licensecheck --copyright -r `find * -type f` | \
3098 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
3099 &lt;/pre&gt;&lt;/p&gt;
3100
3101 &lt;p&gt;He mentioned that he normally check the generated file into the
3102 version control system to make it easier to discover license and
3103 copyright changes in the upstream source. I will try to do the same
3104 with my packages in the future.&lt;/p&gt;
3105
3106 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
3107 against using -quiet for new users, so I removed it from the proposed
3108 command line.&lt;/p&gt;
3109 </description>
3110 </item>
3111
3112 <item>
3113 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
3114 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
3115 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
3116 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
3117 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
3118 is taking shape in Debian, and one provided feature is a very
3119 convenient way to tell you which package to install to make a given
3120 firmware file available when the kernel is looking for it. This can
3121 be done using apt-file too, but that is for someone else to blog
3122 about. :)&lt;/p&gt;
3123
3124 &lt;p&gt;Here is a small recipe to find the package with a given firmware
3125 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
3126 picked from the set of firmware announced using appstream in Debian
3127 unstable. In general you would be looking for the firmware requested
3128 by the kernel during kernel module loading. To find the package
3129 providing the example file, do like this:&lt;/p&gt;
3130
3131 &lt;blockquote&gt;&lt;pre&gt;
3132 % apt install appstream
3133 [...]
3134 % apt update
3135 [...]
3136 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
3137 awk &#39;/Package:/ {print $2}&#39;
3138 firmware-qlogic
3139 %
3140 &lt;/pre&gt;&lt;/blockquote&gt;
3141
3142 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
3143 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
3144 a way appstream can use.&lt;/p&gt;
3145
3146 &lt;p&gt;This same approach can be used to find any package supporting a
3147 given MIME type. This is very useful when you get a file you do not
3148 know how to handle. First find the mime type using &lt;tt&gt;file
3149 --mime-type&lt;/tt&gt;, and next look up the package providing support for
3150 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3151 and you can find all packages handling this type like this:&lt;/p&gt;
3152
3153 &lt;blockquote&gt;&lt;pre&gt;
3154 % apt install appstream
3155 [...]
3156 % apt update
3157 [...]
3158 % appstreamcli what-provides mimetype image/svg+xml | \
3159 awk &#39;/Package:/ {print $2}&#39;
3160 bkchem
3161 phototonic
3162 inkscape
3163 shutter
3164 tetzle
3165 geeqie
3166 xia
3167 pinta
3168 gthumb
3169 karbon
3170 comix
3171 mirage
3172 viewnior
3173 postr
3174 ristretto
3175 kolourpaint4
3176 eog
3177 eom
3178 gimagereader
3179 midori
3180 %
3181 &lt;/pre&gt;&lt;/blockquote&gt;
3182
3183 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
3184 packages providing appstream metadata.&lt;/p&gt;
3185 </description>
3186 </item>
3187
3188 <item>
3189 <title>Creepy, visualise geotagged social media information - nice free software</title>
3190 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
3191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
3192 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
3193 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
3194 with the computerised radio beacon known as a mobile phone their
3195 position is tracked by the phone company and often stored for a long
3196 time (like every time a SMS is received or sent). And if their
3197 computerised radio beacon is capable of running programs (often called
3198 mobile apps) downloaded from the Internet, these programs are often
3199 also capable of tracking their location (if the app requested access
3200 during installation). And when these programs send out information to
3201 central collection points, the location is often included, unless
3202 extra care is taken to not send the location. The provided
3203 information is used by several entities, for good and bad (what is
3204 good and bad, depend on your point of view). What is certain, is that
3205 the private sphere and the right to free movement is challenged and
3206 perhaps even eradicated for those announcing their location this way,
3207 when they share their whereabouts with private and public
3208 entities.&lt;/p&gt;
3209
3210 &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;
3211
3212 &lt;p&gt;The phone company logs provide a register of locations to check out
3213 when one want to figure out what the tracked person was doing. It is
3214 unavailable for most of us, but provided to selected government
3215 officials, company staff, those illegally buying information from
3216 unfaithful servants and crackers stealing the information. But the
3217 public information can be collected and analysed, and a free software
3218 tool to do so is called
3219 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
3220 discovered it when I read
3221 &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
3222 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
3223 November 2014, and decided to check if it was available in Debian.
3224 The python program was in Debian, but
3225 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
3226 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
3227 uploaded a new version which did not work quite right, but did not
3228 have time to fix it then. This Christmas I decided to finally try to
3229 get Creepy operational in Debian. Now a fixed version is available in
3230 Debian unstable and testing, and almost all Debian specific patches
3231 are now included
3232 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
3233
3234 &lt;p&gt;The Creepy program visualises geolocation information fetched from
3235 Twitter, Instagram, Flickr and Google+, and allow one to get a
3236 complete picture of every social media message posted recently in a
3237 given area, or track the movement of a given individual across all
3238 these services. Earlier it was possible to use the search API of at
3239 least some of these services without identifying oneself, but these
3240 days it is impossible. This mean that to use Creepy, you need to
3241 configure it to log in as yourself on these services, and provide
3242 information to them about your search interests. This should be taken
3243 into account when using Creepy, as it will also share information
3244 about yourself with the services.&lt;/p&gt;
3245
3246 &lt;p&gt;The picture above show the twitter messages sent from (or at least
3247 geotagged with a position from) the city centre of Oslo, the capital
3248 of Norway. One useful way to use Creepy is to first look at
3249 information tagged with an area of interest, and next look at all the
3250 information provided by one or more individuals who was in the area.
3251 I tested it by checking out which celebrity provide their location in
3252 twitter messages by checkout out who sent twitter messages near a
3253 Norwegian TV station, and next could track their position over time,
3254 making it possible to locate their home and work place, among other
3255 things. A similar technique have been
3256 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
3257 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
3258 tool to discover lying governments, and a useful tool to help people
3259 understand the value of the private information they provide to the
3260 public.&lt;/p&gt;
3261
3262 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
3263 it depend on several python modules currently missing in Jessie (at
3264 least python-instagram, python-flickrapi and
3265 python-requests-toolbelt).&lt;/p&gt;
3266
3267 &lt;p&gt;(I have uploaded
3268 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
3269 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
3270 Creepy program in Debian.)&lt;/p&gt;
3271 </description>
3272 </item>
3273
3274 <item>
3275 <title>Always download Debian packages using Tor - the simple recipe</title>
3276 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
3277 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
3278 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
3279 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
3280 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
3281 that those listening on the Internet lines would have good reason to
3282 believe a computer have a given security hole&lt;/a&gt; if it download a
3283 security fix from a Debian mirror. This is a good reason to always
3284 use encrypted connections to the Debian mirror, to make sure those
3285 listening do not know which IP address to attack. In August, Richard
3286 Hartmann observed that encryption was not enough, when it was possible
3287 to interfere download size to security patches or the fact that
3288 download took place shortly after a security fix was released, and
3289 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
3290 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
3291 was not the first to propose this, as the
3292 &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;
3293 package by Tim Retout already existed to make it easy to convince apt
3294 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
3295 aware of that package when I read the blog post from Richard.&lt;/p&gt;
3296
3297 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
3298 sysadmins, and he set up a Tor hidden service on one of the central
3299 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3300 it possible to download packages directly between two tor nodes,
3301 making sure the network traffic always were encrypted.&lt;/p&gt;
3302
3303 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
3304 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
3305 urls with tor+http and tor+https, and using the hidden service instead
3306 of the official Debian mirror site. I recommend installing
3307 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
3308 done in /etc/.&lt;/p&gt;
3309
3310 &lt;blockquote&gt;&lt;pre&gt;
3311 apt install apt-transport-tor
3312 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
3313 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
3314 &lt;/pre&gt;&lt;/blockquote&gt;
3315
3316 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
3317 the sed commands for these too. The sed command is assuming your are
3318 using the ftp.debian.org Debian mirror. Adjust the command (or just
3319 edit the file manually) to match your mirror.&lt;/p&gt;
3320
3321 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
3322 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
3323 system, and do not work with these tor+http URLs. For
3324 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
3325 which need a recent apt version currently only in unstable. So if you
3326 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
3327
3328 &lt;p&gt;Another advantage from this change is that your machine will start
3329 using Tor regularly and at fairly random intervals (every time you
3330 update the package lists or upgrade or install a new package), thus
3331 masking other Tor traffic done from the same machine. Using Tor will
3332 become normal for the machine in question.&lt;/p&gt;
3333
3334 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
3335 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
3336 enabled. It would be great if it was the default on any Debian
3337 system.&lt;/p&gt;
3338 </description>
3339 </item>
3340
3341 <item>
3342 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3343 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3344 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3345 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3346 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3347 call the car license plate numbers in those days. I would write the
3348 numbers down in my little book and compare notes with the other kids
3349 to see how many region codes we had seen and if we had seen some
3350 exotic or special region codes and numbers. It was a fun game to pass
3351 time, as we kids have plenty of it.&lt;/p&gt;
3352
3353 &lt;p&gt;A few days I came across
3354 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3355 project&lt;/a&gt;, a free software project to automatically discover and
3356 report license plates in images and video streams, and provide the
3357 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3358 such system for a while now, because I believe it is a bad idea that the
3359 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3360 number plate recognition&lt;/a&gt; tool only is available in the hands of
3361 the powerful, and want it to be available also for the powerless to
3362 even the score when it comes to surveillance and sousveillance. I
3363 discovered the developer
3364 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3365 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3366 help him get it into shape to get the package uploaded into the Debian
3367 archive.&lt;/p&gt;
3368
3369 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3370 it into Debian, where it currently
3371 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3372 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3373
3374 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3375 for the common folks, ie those not running a large government
3376 surveillance system? Well, I plan to put it in a computer on my bike
3377 and in my car, tracking the cars nearby and allowing me to be notified
3378 when number plates on my watch list are discovered. Another use case
3379 was suggested by a friend of mine, who wanted to set it up at his home
3380 to open the car port automatically when it discovered the plate on his
3381 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3382 capable of placing his license plate number of a piece of cardboard to
3383 open his car port, men replied that it was always unlocked anyway. I
3384 guess for such use case it make sense. I am sure there are other use
3385 cases too, for those with imagination and a vision.&lt;/p&gt;
3386
3387 &lt;p&gt;If you want to build your own version of the Debian package, check
3388 out the upstream git source and symlink ./distros/debian to ./debian/
3389 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3390 package show up in unstable.&lt;/p&gt;
3391 </description>
3392 </item>
3393
3394 <item>
3395 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3396 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3398 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3399 <description>&lt;p&gt;Around three years ago, I created
3400 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3401 system&lt;/a&gt; to get a more practical solution in Debian for handing
3402 hardware related packages. A GUI system in the isenkram package will
3403 present a pop-up dialog when some hardware dongle supported by
3404 relevant packages in Debian is inserted into the machine. The same
3405 lookup mechanism to detect packages is available as command line
3406 tools in the isenkram-cli package. In addition to mapping hardware,
3407 it will also map kernel firmware files to packages and make it easy to
3408 install needed firmware packages automatically. The key for this
3409 system to work is a good way to map hardware to packages, in other
3410 words, allow packages to announce what hardware they will work
3411 with.&lt;/p&gt;
3412
3413 &lt;p&gt;I started by providing data files in the isenkram source, and
3414 adding code to download the latest version of these data files at run
3415 time, to ensure every user had the most up to date mapping available.
3416 I also added support for storing the mapping in the Packages file in
3417 the apt repositories, but did not push this approach because while I
3418 was trying to figure out how to best store hardware/package mappings,
3419 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3420 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3421 add the hardware mapping into that data set to be able to use
3422 appstream as a data source, and this was accepted at least for the
3423 Debian version of appstream.&lt;/p&gt;
3424
3425 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3426 and today I uploaded a new version 0.20 of isenkram adding support for
3427 appstream as a data source for mapping hardware to packages. The only
3428 package so far using appstream to announce its hardware support is my
3429 pymissile package. I got help from Matthias Klumpp with figuring out
3430 how do add the required
3431 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3432 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3433 this content:&lt;/p&gt;
3434
3435 &lt;blockquote&gt;&lt;pre&gt;
3436 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3437 &amp;lt;component&amp;gt;
3438 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3439 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3440 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3441 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3442 &amp;lt;description&amp;gt;
3443 &amp;lt;p&amp;gt;
3444 Pymissile provides a curses interface to control an original
3445 Marks and Spencer / Striker USB Missile Launcher, as well as a
3446 motion control script to allow a webcamera to control the
3447 launcher.
3448 &amp;lt;/p&amp;gt;
3449 &amp;lt;/description&amp;gt;
3450 &amp;lt;provides&amp;gt;
3451 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3452 &amp;lt;/provides&amp;gt;
3453 &amp;lt;/component&amp;gt;
3454 &lt;/pre&gt;&lt;/blockquote&gt;
3455
3456 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3457 which is a glob style match rule for hardware specific strings
3458 (modalias strings) provided by the Linux kernel. In this case, it
3459 will map to all USB devices with vendor code 1130 and product code
3460 0202.&lt;/p&gt;
3461
3462 &lt;p&gt;Note, it is important that the license of all the metadata files
3463 are compatible to have permissions to aggregate them into archive wide
3464 appstream files. Matthias suggested to use MIT or BSD licenses for
3465 these files. A challenge is figuring out a good id for the data, as
3466 it is supposed to be globally unique and shared across distributions
3467 (in other words, best to coordinate with upstream what to use). But
3468 it can be changed later or, so we went with the package name as
3469 upstream for this project is dormant.&lt;/p&gt;
3470
3471 &lt;p&gt;To get the metadata file installed in the correct location for the
3472 mirror update scripts to pick it up and include its content the
3473 appstream data source, the file must be installed in the binary
3474 package under /usr/share/appdata/. I did this by adding the following
3475 line to debian/pymissile.install:&lt;/p&gt;
3476
3477 &lt;blockquote&gt;&lt;pre&gt;
3478 debian/pymissile.metainfo.xml usr/share/appdata
3479 &lt;/pre&gt;&lt;/blockquote&gt;
3480
3481 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3482 all packages useful on the current computer automatically, and the GUI
3483 pop-up handler will propose to install the package not already
3484 installed if a hardware dongle is inserted into the machine in
3485 question.&lt;/p&gt;
3486
3487 &lt;p&gt;Details of the modalias field in appstream is available from the
3488 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3489
3490 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3491 try running this command on the command line:&lt;/p&gt;
3492
3493 &lt;blockquote&gt;&lt;pre&gt;
3494 cat $(find /sys/devices/|grep modalias)
3495 &lt;/pre&gt;&lt;/blockquote&gt;
3496
3497 &lt;p&gt;To learn more about the isenkram system, please check out
3498 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3499 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3500 </description>
3501 </item>
3502
3503 <item>
3504 <title>The GNU General Public License is not magic pixie dust</title>
3505 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3506 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3507 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3508 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3509 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3510 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3511 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3512 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3513
3514 &lt;blockquote&gt;
3515
3516 &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;
3517
3518 &lt;blockquote&gt;
3519 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3520
3521 The first step is to choose a
3522 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3523 code.&lt;br/&gt;
3524
3525 The next step is, when someone fails to follow that copyleft license,
3526 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3527
3528 and its a simple fact of our modern society that such type of
3529 work&lt;br/&gt;
3530
3531 is incredibly expensive to do and incredibly difficult to do.
3532 &lt;/blockquote&gt;
3533
3534 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3535 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3536 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3537 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3538
3539 &lt;p&gt;As the Debian Website
3540 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3541 &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;
3542 imply, public domain and permissively licensed software can lead to
3543 the production of more proprietary software as people discover useful
3544 software, extend it and or incorporate it into their hardware or
3545 software products. Copyleft licenses such as the GNU GPL were created
3546 to close off this avenue to the production of proprietary software but
3547 such licenses are not enough. With the ongoing adoption of Free
3548 Software by individuals and groups, inevitably the community&#39;s
3549 expectations of license compliance are violated, usually out of
3550 ignorance of the way Free Software works, but not always. As Karen
3551 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3552 Freedom&quot;&gt;FaiF&lt;/a&gt;
3553 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3554 copyleft is nothing if no-one is willing and able to stand up in court
3555 to protect it. The reality of today&#39;s world is that legal
3556 representation is expensive, difficult and time consuming. With
3557 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3558 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3559 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3560 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3561 of the Linux project, Debian and other groups against GPL violations.
3562 In March the SFC supported a
3563 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3564 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3565 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3566 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3567 kernel. Since then two of their sponsors pulled corporate funding and
3568 conferences
3569 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3570 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3571 less on corporate funding and more on the broad community of
3572 individuals who support Free Software and copyleft. So the SFC has
3573 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3574 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3575 a community of folks who stand up for copyleft and the GPL by
3576 supporting their work on promoting and supporting copyleft and Free
3577 Software.&lt;/p&gt;
3578
3579 &lt;p&gt;If you support Free Software,
3580 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3581 what the SFC do, agree with their
3582 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3583 principles&lt;/a&gt;, are happy about their
3584 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3585 work on a project that is an SFC
3586 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3587 just want to stand up for copyleft, please join
3588 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3589 Allan Webber&lt;/a&gt;,
3590 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3591 Smith&lt;/a&gt;,
3592 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3593 Bacon&lt;/a&gt;, myself and
3594 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3595 becoming a
3596 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3597 next week your donation will be
3598 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3599 by an anonymous donor. Please also consider asking your employer to
3600 match your donation or become a sponsor of SFC. Don&#39;t forget to
3601 spread the word about your support for SFC via email, your blog and or
3602 social media accounts.&lt;/p&gt;
3603
3604 &lt;/blockquote&gt;
3605
3606 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3607 of Software Freedom Conservancy myself. Perhaps you should be a
3608 supporter too?&lt;/p&gt;
3609 </description>
3610 </item>
3611
3612 <item>
3613 <title>PGP key transition statement for key EE4E02F9</title>
3614 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3615 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3616 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3617 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3618 set it up properly. I wanted to generate it offline and have it
3619 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3620 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3621 time to sit down with an offline machine almost took forever. But
3622 finally I&#39;ve been able to complete the process, and have now moved
3623 from my old GPG key to a new GPG key. See
3624 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3625 full transition statement, signed with both my old and new key&lt;/a&gt; for
3626 the details. This is my new key:&lt;/p&gt;
3627
3628 &lt;pre&gt;
3629 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]
3630 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3631 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3632 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3633 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3634 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3635 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3636 &lt;/pre&gt;
3637
3638 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3639 my old key.&lt;/p&gt;
3640
3641 &lt;p&gt;If you signed my old key
3642 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3643 I&#39;d very much appreciate a signature on my new key, details and
3644 instructions in the transition statement. I m happy to reciprocate if
3645 you have a similarly signed transition statement to present.&lt;/p&gt;
3646 </description>
3647 </item>
3648
3649 <item>
3650 <title>The life and death of a laptop battery</title>
3651 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3652 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3653 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3654 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3655 But this do not last. The last few laptops gave me a feeling that
3656 within a year, the life time is just a fraction of what it used to be,
3657 and it slowly become painful to use the laptop without power connected
3658 all the time. Because of this, when I got a new Thinkpad X230 laptop
3659 about two years ago, I decided to monitor its battery state to have
3660 more hard facts when the battery started to fail.&lt;/p&gt;
3661
3662 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3663
3664 &lt;p&gt;First I tried to find a sensible Debian package to record the
3665 battery status, assuming that this must be a problem already handled
3666 by someone else. I found
3667 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3668 which collects statistics from the battery, but it was completely
3669 broken. I sent a few suggestions to the maintainer, but decided to
3670 write my own collector as a shell script while I waited for feedback
3671 from him. Via
3672 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3673 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3674 discovered
3675 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3676 available in Debian.&lt;/p&gt;
3677
3678 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3679 battery stats ever since. Now my
3680 /var/log/hjemmenett-battery-status.log file contain around 115,000
3681 measurements, from the time the battery was working great until now,
3682 when it is unable to charge above 7% of original capacity. My
3683 collector shell script is quite simple and look like this:&lt;/p&gt;
3684
3685 &lt;pre&gt;
3686 #!/bin/sh
3687 # Inspired by
3688 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3689 # See also
3690 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3691 logfile=/var/log/hjemmenett-battery-status.log
3692
3693 files=&quot;manufacturer model_name technology serial_number \
3694 energy_full energy_full_design energy_now cycle_count status&quot;
3695
3696 if [ ! -e &quot;$logfile&quot; ] ; then
3697 (
3698 printf &quot;timestamp,&quot;
3699 for f in $files; do
3700 printf &quot;%s,&quot; $f
3701 done
3702 echo
3703 ) &gt; &quot;$logfile&quot;
3704 fi
3705
3706 log_battery() {
3707 # Print complete message in one echo call, to avoid race condition
3708 # when several log processes run in parallel.
3709 msg=$(printf &quot;%s,&quot; $(date +%s); \
3710 for f in $files; do \
3711 printf &quot;%s,&quot; $(cat $f); \
3712 done)
3713 echo &quot;$msg&quot;
3714 }
3715
3716 cd /sys/class/power_supply
3717
3718 for bat in BAT*; do
3719 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3720 done
3721 &lt;/pre&gt;
3722
3723 &lt;p&gt;The script is called when the power management system detect a
3724 change in the power status (power plug in or out), and when going into
3725 and out of hibernation and suspend. In addition, it collect a value
3726 every 10 minutes. This make it possible for me know when the battery
3727 is discharging, charging and how the maximum charge change over time.
3728 The code for the Debian package
3729 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3730 available on github&lt;/a&gt;.&lt;/p&gt;
3731
3732 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3733
3734 &lt;pre&gt;
3735 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3736 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3737 [...]
3738 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3739 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3740 &lt;/pre&gt;
3741
3742 &lt;p&gt;I wrote a small script to create a graph of the charge development
3743 over time. This graph depicted above show the slow death of my laptop
3744 battery.&lt;/p&gt;
3745
3746 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3747 dying in a year or two, while the batteries of space probes and
3748 satellites keep working year after year. If we are to believe
3749 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3750 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3751 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3752 all the time, but to stay below 90% of full charge most of the time.
3753 I&#39;ve been told that the Tesla electric cars
3754 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3755 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3756 100% when preparing for a longer trip (not that I would want a car
3757 like Tesla where rights to privacy is abandoned, but that is another
3758 story), which I guess is the option we should have for laptops on
3759 Linux too.&lt;/p&gt;
3760
3761 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3762 stop charging at 80%, unless requested to charge to 100% once in
3763 preparation for a longer trip? I found
3764 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3765 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3766 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3767 load).&lt;/p&gt;
3768
3769 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3770 at the start. I also wonder why the &quot;full capacity&quot; increases some
3771 times, and if it is possible to repeat the process to get the battery
3772 back to design capacity. And I wonder if the discharge and charge
3773 speed change over time, or if this stay the same. I did not yet try
3774 to write a tool to calculate the derivative values of the battery
3775 level, but suspect some interesting insights might be learned from
3776 those.&lt;/p&gt;
3777
3778 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3779 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3780 packages instead of the tp-smapi-dkms package I had tried to use
3781 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3782 and stop. I&#39;ve done so now, but expect my existing battery is toast
3783 and need to be replaced. The proposal is unfortunately Thinkpad
3784 specific.&lt;/p&gt;
3785 </description>
3786 </item>
3787
3788 <item>
3789 <title>New laptop - some more clues and ideas based on feedback</title>
3790 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3792 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3793 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3794 need for a new laptop, and provided very useful feedback. I wish to
3795 thank every one of these. Several pointed me to the possibility of
3796 fixing my X230, and I am already in the process of getting Lenovo to
3797 do so thanks to the on site, next day support contract covering the
3798 machine. But the battery is almost useless (I expect to replace it
3799 with a non-official battery) and I do not expect the machine to live
3800 for many more years, so it is time to plan its replacement. If I did
3801 not have a support contract, it was suggested to find replacement parts
3802 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3803 might present a language barrier as I do not understand French.&lt;/p&gt;
3804
3805 &lt;p&gt;One tip I got was to use the
3806 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3807 compare laptop models. It seem to have more models available than
3808 prisjakt.no. Another tip I got from someone I know have similar
3809 keyboard preferences was that the HP EliteBook 840 keyboard is not
3810 very good, and this matches my experience with earlier EliteBook
3811 keyboards I tested. Because of this, I will not consider it any further.
3812
3813 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3814 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3815 (which is missing from the X240), and is working fairly well with
3816 Debian Sid/Unstable according to
3817 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3818 got on the keyboard quality are not consistent. Some say the keyboard
3819 is good, others say it is ok, while others say it is not very good.
3820 Those with experience from X41 and and X60 agree that the X250
3821 keyboard is not as good as those trusty old laptops, and suggest I
3822 keep and fix my X230 instead of upgrading, or get a used X230 to
3823 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3824 activity and battery status, which is very convenient on my X230. I&#39;m
3825 also told that the CPU fan is running very often, making it a bit
3826 noisy. In any case, the X250 do not work out of the box with Debian
3827 Stable/Jessie, one of my requirements.&lt;/p&gt;
3828
3829 &lt;p&gt;I have also gotten a few vendor proposals, one was
3830 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3831 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3832 The latter look very attractive to me.&lt;/p&gt;
3833
3834 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
3835 as I keep looking for a replacement.&lt;/p&gt;
3836
3837 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
3838 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
3839 different
3840 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
3841 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
3842 </description>
3843 </item>
3844
3845 <item>
3846 <title>Time to find a new laptop, as the old one is broken after only two years</title>
3847 <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>
3848 <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>
3849 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
3850 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
3851 replacement soon. The left 5 cm of the screen on my Thinkpad X230
3852 started flickering yesterday, and I suspect the cause is a broken
3853 cable, as changing the angle of the screen some times get rid of the
3854 flickering.&lt;/p&gt;
3855
3856 &lt;p&gt;My requirements have not really changed since I bought it, and is
3857 still as
3858 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
3859 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
3860 good help from
3861 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
3862 where I could select at least a few of the requirements (mouse pin,
3863 wifi, weight) and go through the rest manually. Three button mouse
3864 and a good keyboard is not available as an option, and all the three
3865 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
3866 G2) lack three mouse buttons). It is also unclear to me how good the
3867 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3868 the keyboard, even if the quality and robustness in the X series have
3869 deteriorated since X41.&lt;/p&gt;
3870
3871 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
3872 seem sensible to me? Are there better services around to search the
3873 set of available laptops for features? Please send me an email if you
3874 have suggestions.&lt;/p&gt;
3875
3876 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
3877 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
3878 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
3879 </description>
3880 </item>
3881
3882 <item>
3883 <title>How to stay with sysvinit in Debian Jessie</title>
3884 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
3885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
3886 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
3887 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
3888 sysvinit as its boot system by default. But how can one keep using
3889 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3890 courtesy of
3891 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
3892 Schubert&lt;/a&gt; and
3893 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
3894 McVittie&lt;/a&gt;.
3895
3896 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
3897 keep sysvinit as your boot system, create a file
3898 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
3899 you upgrade:&lt;/p&gt;
3900
3901 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3902 Package: systemd-sysv
3903 Pin: release o=Debian
3904 Pin-Priority: -1
3905 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3906
3907 &lt;p&gt;This file content will tell apt and aptitude to not consider
3908 installing systemd-sysv as part of any installation and upgrade
3909 solution when resolving dependencies, and thus tell it to avoid
3910 systemd as a default boot system. The end result should be that the
3911 upgraded system keep using sysvinit.&lt;/p&gt;
3912
3913 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
3914 get sysvinit installed by default (debootstrap used by
3915 debian-installer have no option for this), but one can tell the
3916 installer to switch to sysvinit before the first boot. Either by
3917 using a kernel argument to the installer, or by adding a line to the
3918 preseed file used. First, the kernel command line argument:
3919
3920 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3921 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
3922 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3923
3924 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
3925
3926 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3927 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3928 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3929
3930 &lt;p&gt;One can of course also do this after the first boot by installing
3931 the sysvinit-core package.&lt;/p&gt;
3932
3933 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
3934 sysvinit boot sequence in Debian have several hardware specific bugs
3935 on Linux caused by the fact that it is unpredictable when hardware
3936 devices show up during boot. But on the other hand, the new default
3937 boot system still have a few rough edges I hope will be fixed before
3938 Jessie is released.&lt;/p&gt;
3939
3940 &lt;p&gt;Update 2014-11-26: Inspired by
3941 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
3942 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
3943 line.&lt;/p&gt;
3944 </description>
3945 </item>
3946
3947 <item>
3948 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
3949 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
3950 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
3951 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
3952 <description>&lt;p&gt;The right to communicate with your friends and family in private,
3953 without anyone snooping, is a right every citicen have in a liberal
3954 democracy. But this right is under serious attack these days.&lt;/p&gt;
3955
3956 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
3957 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3958 the whisleblower Snowden) more expensive for Internet email,
3959 is to deliver all email using SMTP via Tor. Such SMTP option would be
3960 a nice addition to the FreedomBox project if we could send email
3961 between FreedomBox machines without leaking metadata about the emails
3962 to the people peeking on the wire. I
3963 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
3964 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
3965 lot of useful feedback and suggestions. It also became obvious to me
3966 that this was not a novel idea, as the same idea was tested and
3967 documented by Johannes Berg as early as 2006, and both
3968 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
3969 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
3970 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
3971
3972 &lt;p&gt;To implement such system one need to set up a Tor hidden service
3973 providing the SMTP protocol on port 25, and use email addresses
3974 looking like username@hidden-service-name.onion. With such addresses
3975 the connections to port 25 on hidden-service-name.onion using Tor will
3976 go to the correct SMTP server. To do this, one need to configure the
3977 Tor daemon to provide the hidden service and the mail server to accept
3978 emails for this .onion domain. To learn more about Exim configuration
3979 in Debian and test the design provided by Johannes Berg in his FAQ, I
3980 set out yesterday to create a Debian package for making it trivial to
3981 set up such SMTP over Tor service based on Debian. Getting it to work
3982 were fairly easy, and
3983 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
3984 source code for the Debian package&lt;/a&gt; is available from github. I
3985 plan to move it into Debian if further testing prove this to be a
3986 useful approach.&lt;/p&gt;
3987
3988 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
3989 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
3990 get rid of exim4). Install tor, clone the git repository mentioned
3991 above, build the deb and install it on the machine. Next, run
3992 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
3993 the instructions to get the service up and running. Restart tor and
3994 exim when it is done, and test mail delivery using swaks like
3995 this:&lt;/p&gt;
3996
3997 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3998 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3999 --to fbx@dutlqrrmjhtfa3vp.onion
4000 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4001
4002 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
4003 address with your own address to test your server. :)&lt;/p&gt;
4004
4005 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
4006 easier and more automatic. Especially the tor setup need more work.
4007 Also, the package include a tor-smtp tool written in C, but its task
4008 should probably be rewritten in some script language to make the deb
4009 architecture independent. It would probably also make the code easier
4010 to review. The tor-smtp tool currently need to listen on a socket for
4011 exim to talk to it and is started using xinetd. It would be better if
4012 no daemon and no socket is needed. I suspect it is possible to get
4013 exim to run a command line tool for delivery instead of talking to a
4014 socket, and hope to figure out how in a future version of this
4015 system.&lt;/p&gt;
4016
4017 &lt;p&gt;Until I wipe my test machine, I can be reached using the
4018 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
4019 SMTorP. :)&lt;/p&gt;
4020 </description>
4021 </item>
4022
4023 <item>
4024 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
4025 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
4026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
4027 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
4028 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
4029 alioth.debian.org, you know the web interface is fairly slow to
4030 operate. First you visit one web page, enter the moderation password
4031 and get a new page shown with a list of all the messages to moderate
4032 and various options for each email address. This take a while for
4033 every list you moderate, and you need to do it regularly to do a good
4034 job as a list moderator. But there is a quick alternative,
4035 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
4036 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
4037 to moderate in a fraction of a second. Here is a test run on two
4038 lists I recently took over:&lt;/p&gt;
4039
4040 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4041 % time listadmin xiph
4042 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4043 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4044
4045 real 0m1.709s
4046 user 0m0.232s
4047 sys 0m0.012s
4048 %
4049 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4050
4051 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
4052 there are no message in the moderation queue. Every morning I
4053 currently moderate 68 mailman lists, and it normally take around two
4054 minutes. When I took over the two pkg-xiph lists above a few days
4055 ago, there were 400 emails waiting in the moderator queue. It took me
4056 less than 15 minutes to process them all using the listadmin
4057 program.&lt;/p&gt;
4058
4059 &lt;p&gt;If you install
4060 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
4061 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
4062 with content like this, the moderation task is a breeze:&lt;/p&gt;
4063
4064 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4065 username username@example.org
4066 spamlevel 23
4067 default discard
4068 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
4069
4070 password secret
4071 adminurl https://{domain}/mailman/admindb/{list}
4072 mailman-list@lists.example.com
4073
4074 password hidden
4075 other-list@otherserver.example.org
4076 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4077
4078 &lt;p&gt;There are other options to set as well. Check the manual page to
4079 learn the details.&lt;/p&gt;
4080
4081 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
4082 the SSL certificate is self signed or not properly signed by a
4083 generally accepted signing authority, you can set a environment
4084 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
4085
4086 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4087 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
4088 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4089
4090 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
4091 can provide an argument to the listadmin script like I do in the
4092 initial screen dump (the xiph argument). Using an argument, only
4093 lists matching the argument string will be processed. This make it
4094 quick to accept messages if you notice the moderation request in your
4095 email.&lt;/p&gt;
4096
4097 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
4098 mailing lists, as I simply do not have time to spend on that if the
4099 process was any slower. The listadmin program have saved me hours of
4100 time I could spend elsewhere over the years. It truly is nice free
4101 software.&lt;/p&gt;
4102
4103 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4104 activities, please send Bitcoin donations to my address
4105 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4106
4107 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
4108 configuration example. Also, I&#39;ve been told that the
4109 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
4110 sure why.&lt;/p&gt;
4111 </description>
4112 </item>
4113
4114 <item>
4115 <title>Debian Jessie, PXE and automatic firmware installation</title>
4116 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
4117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
4118 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
4119 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
4120 problem that the WiFi card require some firmware to work properly.
4121 And it has been a pain to fix this using preseeding in Debian.
4122 Normally something more is needed. But thanks to
4123 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
4124 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
4125 to do this using simple preseeding.&lt;/p&gt;
4126
4127 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
4128 firmware for the hardware found in the machine (actually, requested by
4129 the kernel modules for the hardware). (It can also install user space
4130 programs supporting the hardware detected, but that is not the focus
4131 of this story.)&lt;/p&gt;
4132
4133 &lt;p&gt;To get this working in the default installation, two preeseding
4134 values are needed. First, the isenkram-cli package must be installed
4135 into the target chroot (aka the hard drive) before tasksel is executed
4136 in the pkgsel step of the debian-installer system. This is done by
4137 preseeding the base-installer/includes debconf value to include the
4138 isenkram-cli package. The package name is next passed to debootstrap
4139 for installation. With the isenkram-cli package in place, tasksel
4140 will automatically use the isenkram tasks to detect hardware specific
4141 packages for the machine being installed and install them, because
4142 isenkram-cli contain tasksel tasks.&lt;/p&gt;
4143
4144 &lt;p&gt;Second, one need to enable the non-free APT repository, because
4145 most firmware unfortunately is non-free. This is done by preseeding
4146 the apt-mirror-setup step. This is unfortunate, but for a lot of
4147 hardware it is the only option in Debian.&lt;/p&gt;
4148
4149 &lt;p&gt;The end result is two lines needed in your preseeding file to get
4150 firmware installed automatically by the installer:&lt;/p&gt;
4151
4152 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4153 base-installer base-installer/includes string isenkram-cli
4154 apt-mirror-setup apt-setup/non-free boolean true
4155 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4156
4157 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
4158 both firmware and user space packages when using this method. It also
4159 do not work well, so use version 0.15 or later. Installing both
4160 firmware and user space packages might give you a bit more than you
4161 want, so I decided to split the tasksel task in two, one for firmware
4162 and one for user space programs. The firmware task is enabled by
4163 default, while the one for user space programs is not. This split is
4164 implemented in the package currently in unstable.&lt;/p&gt;
4165
4166 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
4167 this recipe work for you. :)&lt;/p&gt;
4168
4169 &lt;p&gt;So, I bet you are wondering, how can this work. First and
4170 foremost, it work because tasksel is modular, and driven by whatever
4171 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4172 isenkram-cli package place two files for tasksel to find. First there
4173 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
4174
4175 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4176 Task: isenkram-packages
4177 Section: hardware
4178 Description: Hardware specific packages (autodetected by isenkram)
4179 Based on the detected hardware various hardware specific packages are
4180 proposed.
4181 Test-new-install: show show
4182 Relevance: 8
4183 Packages: for-current-hardware
4184
4185 Task: isenkram-firmware
4186 Section: hardware
4187 Description: Hardware specific firmware packages (autodetected by isenkram)
4188 Based on the detected hardware various hardware specific firmware
4189 packages are proposed.
4190 Test-new-install: mark show
4191 Relevance: 8
4192 Packages: for-current-hardware-firmware
4193 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4194
4195 &lt;p&gt;The key parts are Test-new-install which indicate how the task
4196 should be handled and the Packages line referencing to a script in
4197 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4198 list of packages to install. The for-current-hardware-firmware script
4199 look like this to list relevant firmware for the machine:
4200
4201 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4202 #!/bin/sh
4203 #
4204 PATH=/usr/sbin:$PATH
4205 export PATH
4206 isenkram-autoinstall-firmware -l
4207 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4208
4209 &lt;p&gt;With those two pieces in place, the firmware is installed by
4210 tasksel during the normal d-i run. :)&lt;/p&gt;
4211
4212 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
4213 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
4214 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
4215 install.&lt;/p&gt;
4216
4217 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
4218 pilots in testing this feature, as isenkram is used there now to
4219 install firmware, replacing the earlier scripts.&lt;/p&gt;
4220 </description>
4221 </item>
4222
4223 <item>
4224 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
4225 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
4226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
4227 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
4228 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
4229 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4230 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
4231 on a screen normally showing the bread types and prizes:&lt;/p&gt;
4232
4233 &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;
4234
4235 &lt;p&gt;If it had booted as it was supposed to, I would never had known
4236 about this hidden Linux installation. It is interesting what
4237 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
4238 </description>
4239 </item>
4240
4241 <item>
4242 <title>New lsdvd release version 0.17 is ready</title>
4243 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
4244 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
4245 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
4246 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
4247 got a new set of developers a few weeks ago, after the original
4248 developer decided to step down and pass the project to fresh blood.
4249 This project is now maintained by Petter Reinholdtsen and Steve
4250 Dibb.&lt;/p&gt;
4251
4252 &lt;p&gt;I just wrapped up
4253 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
4254 new lsdvd release&lt;/a&gt;, available in git or from
4255 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
4256 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
4257 0.17.&lt;/p&gt;
4258
4259 &lt;ul&gt;
4260
4261 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
4262 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
4263 non-existant, to work around additional copy protection&lt;/li&gt;
4264 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
4265 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
4266 &lt;li&gt;Fix include orders&lt;/li&gt;
4267 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
4268 &lt;li&gt;Fix the chapter count&lt;/li&gt;
4269 &lt;li&gt;Make sure the array size and the array limit used when initialising
4270 the palette size is the same.&lt;/li&gt;
4271 &lt;li&gt;Fix array printing.&lt;/li&gt;
4272 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
4273 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
4274 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
4275 with more GCC compiler warnings.&lt;/li&gt;
4276
4277 &lt;/ul&gt;
4278
4279 &lt;p&gt;This change bring together patches for lsdvd in use in various
4280 Linux and Unix distributions, as well as patches submitted to the
4281 project the last nine years. Please check it out. :)&lt;/p&gt;
4282 </description>
4283 </item>
4284
4285 <item>
4286 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
4287 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
4288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
4289 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
4290 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4291 project&lt;/a&gt; provide a Linux solution for schools, including a
4292 powerful desktop with education software, a central server providing
4293 web pages, user database, user home directories, central login and PXE
4294 boot of both clients without disk and the installation to install Debian
4295 Edu on machines with disk (and a few other services perhaps to small
4296 to mention here). We in the Debian Edu team are currently working on
4297 the Jessie based version, trying to get everything in shape before the
4298 freeze, to avoid having to maintain our own package repository in the
4299 future. The
4300 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
4301 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
4302 work left. Some fatal problems block testing, breaking the installer,
4303 but it is possible to work around these to get anyway. Here is a
4304 recipe on how to get the installation limping along.&lt;/p&gt;
4305
4306 &lt;p&gt;First, download the test ISO via
4307 &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;,
4308 &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;
4309 or rsync (use
4310 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
4311 The ISO build was broken on Tuesday, so we do not get a new ISO every
4312 12 hours or so, but thankfully the ISO we already got we are able to
4313 install with some tweaking.&lt;/p&gt;
4314
4315 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
4316 (use Alt-Ctrl-F2), run&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4319 nano /usr/bin/edu-eatmydata-install
4320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4321
4322 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
4323 optimization. Return to the installation, select the profile you want
4324 and continue. Without this change, exim4-config will fail to install
4325 due to a known bug in eatmydata.&lt;/p&gt;
4326
4327 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
4328 this do not work, figure out what your correct value would be. All my
4329 test machines need /dev/sda, so I have no advice if it do not fit
4330 your need.&lt;/p&gt;
4331
4332 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
4333 root after the initial boot from hard drive, and install the
4334 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4335 or mate. If you want several desktop options, install more than one
4336 metapackage. Once this is done, reboot and you should have a working
4337 graphical login screen. This workaround should no longer be needed
4338 once the education-tasks package version 1.801 enter testing in two
4339 days.&lt;/p&gt;
4340
4341 &lt;p&gt;I believe the ISO build will start working on two days when the new
4342 tasksel package enter testing and Steve McIntyre get a chance to
4343 update the debian-cd git repository. The eatmydata, grub and desktop
4344 issues are already fixed in unstable and testing, and should show up
4345 on the ISO as soon as the ISO build start working again. Well the
4346 eatmydata optimization is really just disabled. The proper fix
4347 require an upload by the eatmydata maintainer applying the patch
4348 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4349 The rest have proper fixes in unstable.&lt;/p&gt;
4350
4351 &lt;p&gt;I hope this get you going with the installation testing, as we are
4352 quickly running out of time trying to get our Jessie based
4353 installation ready before the distribution freeze in a month.&lt;/p&gt;
4354 </description>
4355 </item>
4356
4357 <item>
4358 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4359 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4360 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4361 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4362 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4363 to handle my fairly large DVD collection. It is a nice command line
4364 tool to get details about a DVD, like title, tracks, track length,
4365 etc, in XML, Perl or human readable format. But lsdvd have not seen
4366 any new development since 2006 and had a few irritating bugs affecting
4367 its use with some DVDs. Upstream seemed to be dead, and in January I
4368 sent a small probe asking for a version control repository for the
4369 project, without any reply. But I use it regularly and would like to
4370 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4371 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4372 the project admin, and after getting a reply from him explaining that
4373 he was no longer interested in the project, I asked if I could take
4374 over. And yesterday, I became project admin.&lt;/p&gt;
4375
4376 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4377 maintainer interested in joining forces to maintain the upstream
4378 project, and I hope we can get a new release out fairly quickly,
4379 collecting the patches spread around on the internet into on place.
4380 I&#39;ve added the relevant Debian patches to the freshly created git
4381 repository, and expect the Gentoo patches to make it too. If you got
4382 a DVD collection and care about command line tools, check out
4383 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4384 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4385 list&lt;/a&gt;. :)&lt;/p&gt;
4386 </description>
4387 </item>
4388
4389 <item>
4390 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4391 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4392 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4393 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4394 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4395 a lot quicker. When we install more than 2000 packages in
4396 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4397 tasksel in the installer, unpacking the binary packages take forever.
4398 A part of the slow I/O issue was discussed in
4399 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4400 much file system sync-ing done by dpkg, which is the package
4401 responsible for unpacking the binary packages. Other parts (like code
4402 executed by postinst scripts) might also sync to disk during
4403 installation. All this sync-ing to disk do not really make sense to
4404 me. If the machine crash half-way through, I start over, I do not try
4405 to salvage the half installed system. So the failure sync-ing is
4406 supposed to protect against, hardware or system crash, is not really
4407 relevant while the installer is running.&lt;/p&gt;
4408
4409 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4410 system sync()-ing in a fairly non-intrusive way, without the need to
4411 change the code in several packages. The idea is not new, but I have
4412 not heard anyone propose the approach using dpkg-divert before. It
4413 depend on the small and clever package
4414 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4415 uses LD_PRELOAD to replace the system functions for syncing data to
4416 disk with functions doing nothing, thus allowing programs to live
4417 dangerous while speeding up disk I/O significantly. Instead of
4418 modifying the implementation of dpkg, apt and tasksel (which are the
4419 packages responsible for selecting, fetching and installing packages),
4420 it occurred to me that we could just divert the programs away, replace
4421 them with a simple shell wrapper calling
4422 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4423 Two days ago I decided to test the idea, and wrapped up a simple
4424 implementation for the Debian Edu udeb.&lt;/p&gt;
4425
4426 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4427 time of the pkgsel step (installing tasks) from 64 to less than 44
4428 minutes (20 minutes shaved off the installation) on an old Dell
4429 Latitude D505 machine. I am not quite sure what the optimised time
4430 would have been, as I messed up the testing a bit, causing the debconf
4431 priority to get low enough for two questions to pop up during
4432 installation. As soon as I saw the questions I moved the installation
4433 along, but do not know how long the question were holding up the
4434 installation. I did some more measurements using Debian Edu Jessie,
4435 and got these results. The time measured is the time stamp in
4436 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4437 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4438 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4439 timing thus do not depend on how quickly the user handle the tasksel
4440 dialog.&lt;/p&gt;
4441
4442 &lt;p&gt;&lt;table&gt;
4443
4444 &lt;tr&gt;
4445 &lt;th&gt;Machine/setup&lt;/th&gt;
4446 &lt;th&gt;Original tasksel&lt;/th&gt;
4447 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4448 &lt;th&gt;Reduction&lt;/th&gt;
4449 &lt;/tr&gt;
4450
4451 &lt;tr&gt;
4452 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4453 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4454 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4455 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4456 &lt;/tr&gt;
4457
4458 &lt;tr&gt;
4459 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4460 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4461 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4462 &lt;td&gt;23 min 40%&lt;/td&gt;
4463 &lt;/tr&gt;
4464
4465 &lt;tr&gt;
4466 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4467 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4468 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4469 &lt;td&gt;11 min 50%&lt;/td&gt;
4470 &lt;/tr&gt;
4471
4472 &lt;tr&gt;
4473 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4474 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4475 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4476 &lt;td&gt;2 min 33%&lt;/td&gt;
4477 &lt;/tr&gt;
4478
4479 &lt;tr&gt;
4480 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4481 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4482 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4483 &lt;td&gt;4 min 21%&lt;/td&gt;
4484 &lt;/tr&gt;
4485
4486 &lt;/table&gt;&lt;/p&gt;
4487
4488 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4489 time is spent downloading packages. The connection to the Internet
4490 was 100Mbit/s during testing, so downloading should not be a
4491 significant factor in the measurement. Download typically took a few
4492 seconds to a few minutes, depending on the amount of packages being
4493 installed.&lt;/p&gt;
4494
4495 &lt;p&gt;The speedup is implemented by using two hooks in
4496 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4497 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4498 finish-install.d hook to remove the divert at the end of the
4499 installation. I picked the pre-pkgsel.d hook instead of the
4500 post-base-installer.d hook because I test using an ISO without the
4501 eatmydata package included, and the post-base-installer.d hook in
4502 Debian Edu can only operate on packages included in the ISO. The
4503 negative effect of this is that I am unable to activate this
4504 optimization for the kernel installation step in d-i. If the code is
4505 moved to the post-base-installer.d hook, the speedup would be larger
4506 for the entire installation.&lt;/p&gt;
4507
4508 &lt;p&gt;I&#39;ve implemented this in the
4509 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4510 git repository, and plan to provide the optimization as part of the
4511 Debian Edu installation. If you want to test this yourself, you can
4512 create two files in the installer (or in an udeb). One shell script
4513 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4514
4515 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4516 #!/bin/sh
4517 set -e
4518 . /usr/share/debconf/confmodule
4519 info() {
4520 logger -t my-pkgsel &quot;info: $*&quot;
4521 }
4522 error() {
4523 logger -t my-pkgsel &quot;error: $*&quot;
4524 }
4525 override_install() {
4526 apt-install eatmydata || true
4527 if [ -x /target/usr/bin/eatmydata ] ; then
4528 for bin in dpkg apt-get aptitude tasksel ; do
4529 file=/usr/bin/$bin
4530 # Test that the file exist and have not been diverted already.
4531 if [ -f /target$file ] ; then
4532 info &quot;diverting $file using eatmydata&quot;
4533 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4534 &gt; /target$file.edu
4535 chmod 755 /target$file.edu
4536 in-target dpkg-divert --package debian-edu-config \
4537 --rename --quiet --add $file
4538 ln -sf ./$bin.edu /target$file
4539 else
4540 error &quot;unable to divert $file, as it is missing.&quot;
4541 fi
4542 done
4543 else
4544 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4545 fi
4546 }
4547
4548 override_install
4549 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4550
4551 &lt;p&gt;To clean up, another shell script should go into
4552 /usr/lib/finish-install.d/ with code like this:
4553
4554 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4555 #! /bin/sh -e
4556 . /usr/share/debconf/confmodule
4557 error() {
4558 logger -t my-finish-install &quot;error: $@&quot;
4559 }
4560 remove_install_override() {
4561 for bin in dpkg apt-get aptitude tasksel ; do
4562 file=/usr/bin/$bin
4563 if [ -x /target$file.edu ] ; then
4564 rm /target$file
4565 in-target dpkg-divert --package debian-edu-config \
4566 --rename --quiet --remove $file
4567 rm /target$file.edu
4568 else
4569 error &quot;Missing divert for $file.&quot;
4570 fi
4571 done
4572 sync # Flush file buffers before continuing
4573 }
4574
4575 remove_install_override
4576 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4577
4578 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4579 edu-eatmydata-install and call it from the pre-pkgsel.d and
4580 finish-install.d scripts.&lt;/p&gt;
4581
4582 &lt;p&gt;By now you might ask if this change should get into the normal
4583 Debian installer too? I suspect it should, but am not sure the
4584 current debian-installer coordinators find it useful enough. It also
4585 depend on the side effects of the change. I&#39;m not aware of any, but I
4586 guess we will see if the change is safe after some more testing.
4587 Perhaps there is some package in Debian depending on sync() and
4588 fsync() having effect? Perhaps it should go into its own udeb, to
4589 allow those of us wanting to enable it to do so without affecting
4590 everyone.&lt;/p&gt;
4591
4592 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4593 will break installation of all programs using gnutls because of
4594 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4595 eatmydata package in Debian will solve it.&lt;/p&gt;
4596
4597 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4598 the optimization work again. And I have discovered that the
4599 dpkg-divert trick is not really needed and implemented a slightly
4600 simpler approach as part of the debian-edu-install package. See
4601 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4602
4603 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4604 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4605 triggering on i386 made it into testing, and broke this installation
4606 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4607 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4608 </description>
4609 </item>
4610
4611 <item>
4612 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4613 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4614 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4615 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4616 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4617 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4618 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4619 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4620 learn that there is a large set of publicly available key servers to
4621 use when looking for peoples public key. So far I have used
4622 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4623 were misbehaving, but those days are ended. The servers I have used
4624 up until yesterday have been slow and some times unavailable. I hope
4625 those problems are gone now.&lt;/p&gt;
4626
4627 &lt;p&gt;Behind the round robin DNS entry of the
4628 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4629 there is a pool of more than 100 keyservers which are checked every
4630 day to ensure they are well connected and up to date. It must be
4631 better than what I have used so far. :)&lt;/p&gt;
4632
4633 &lt;p&gt;Yesterdays speaker told me that the service is the default
4634 keyserver provided by the default configuration in GnuPG, but this do
4635 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4636
4637 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4638 line:&lt;/p&gt;
4639
4640 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4641 keyserver pool.sks-keyservers.net
4642 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4643
4644 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4645 entries in DNS. Just for fun, I did just that at work, so now every
4646 user of GnuPG at the University of Oslo should find a OpenGPG
4647 keyserver automatically should their need it:&lt;/p&gt;
4648
4649 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4650 % host -t srv _pgpkey-http._tcp.uio.no
4651 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4652 %
4653 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4654
4655 &lt;p&gt;Now if only
4656 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4657 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4658 very happy. It can look up a given key or search for a user ID, but I
4659 normally do not want that, but to find a trust path from my key to
4660 another key. Given a user ID or key ID, I would like to find (and
4661 download) the keys representing a signature path from my key to the
4662 key in question, to be able to get a trust path between the two keys.
4663 This is as far as I can tell not possible today. Perhaps something
4664 for a future version of the protocol?&lt;/p&gt;
4665 </description>
4666 </item>
4667
4668 <item>
4669 <title>From English wiki to translated PDF and epub via Docbook</title>
4670 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4671 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4672 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4673 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4674 project&lt;/a&gt; provide an instruction manual for teachers, system
4675 administrators and other users that contain useful tips for setting up
4676 and maintaining a Debian Edu installation. This text is about how the
4677 text processing of this manual is handled in the project.&lt;/p&gt;
4678
4679 &lt;p&gt;One goal of the project is to provide information in the native
4680 language of its users, and for this we need to handle translations.
4681 But we also want to make sure each language contain the same
4682 information, so for this we need a good way to keep the translations
4683 in sync. And we want it to be easy for our users to improve the
4684 documentation, avoiding the need to learn special formats or tools to
4685 contribute, and the obvious way to do this is to make it possible to
4686 edit the documentation using a web browser. We also want it to be
4687 easy for translators to keep the translation up to date, and give them
4688 help in figuring out what need to be translated. Here is the list of
4689 tools and the process we have found trying to reach all these
4690 goals.&lt;/p&gt;
4691
4692 &lt;p&gt;We maintain the authoritative source of our manual in the
4693 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4694 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4695 front page with references to the different chapters, several pages
4696 for each chapter, and finally one &quot;collection page&quot; gluing all the
4697 chapters together into one large web page (aka
4698 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4699 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4700 processing and translations. Thanks to the fact that the
4701 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4702 wiki.debian.org support exporting pages in
4703 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4704 the list of pages to export using the raw version of the AllInOne
4705 page, loop over each of them to generate a Docbook XML version of the
4706 manual. This process also download images and transform image
4707 references to use the locally downloaded images. The generated
4708 Docbook XML files are slightly broken, so some post-processing is done
4709 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4710 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4711 a handfull of images. The XML file can now be used to generate PDF, HTML
4712 and epub versions of the English manual. This is the basic step of
4713 our process, making PDF (using dblatex), HTML (using xsltproc) and
4714 epub (using dbtoepub) version from Docbook XML, and the resulting files
4715 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4716
4717 &lt;p&gt;But English documentation is not enough for us. We want translated
4718 documentation too, and we want to make it easy for translators to
4719 track the English original. For this we use the
4720 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4721 which allow us to transform the English Docbook XML file into a
4722 translation file (a .pot file), usable with the normal gettext based
4723 translation tools used by those translating free software. The pot
4724 file is used to create and maintain translation files (several .po
4725 files), which the translations update with the native language
4726 translations of all titles, paragraphs and blocks of text in the
4727 original. The next step is combining the original English Docbook XML
4728 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4729 create a translated Docbook XML file (in this case
4730 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4731 translated, if the translation is not complete) Docbook XML file can
4732 then be used like the original to create a PDF, HTML and epub version
4733 of the documentation.&lt;/p&gt;
4734
4735 &lt;p&gt;The translators use different tools to edit the .po files. We
4736 recommend using
4737 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4738 while some use emacs and vi, others can use web based editors like
4739 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4740 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4741 is where the .po file end up, in our git repository. Updated
4742 translations can either be committed directly to git, or submitted as
4743 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4744 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4745
4746 &lt;p&gt;One challenge is images, which both might need to be translated (if
4747 they show translated user applications), and are needed in different
4748 formats when creating PDF and HTML versions (epub is a HTML version in
4749 this regard). For this we transform the original PNG images to the
4750 needed density and format during build, and have a way to provide
4751 translated images by storing translated versions in
4752 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4753 package maintainers know more.&lt;/p&gt;
4754
4755 &lt;p&gt;If you wonder what the result look like, we provide
4756 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4757 of the documentation packages on the web&lt;/a&gt;. See for example the
4758 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4759 PDF version&lt;/a&gt; or the
4760 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4761 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4762 but perhaps it will be done in the future.&lt;/p&gt;
4763
4764 &lt;p&gt;To learn more, check out
4765 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4766 debian-edu-doc package&lt;/a&gt;,
4767 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4768 manual on the wiki&lt;/a&gt; and
4769 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4770 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4771 </description>
4772 </item>
4773
4774 <item>
4775 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4776 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4778 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4779 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4780 related packages relevant for the computer installed automatically.
4781 So I implemented one, using
4782 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4783 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4784 run tasksel as user root. You should be presented with a new option,
4785 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4786 select it, tasksel will install the packages isenkram claim is fit for
4787 the current hardware, hot pluggable or not.&lt;p&gt;
4788
4789 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4790 description, and the other is the script used to extract the list of
4791 packages to install. The first part is in
4792 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4793 this:&lt;/p&gt;
4794
4795 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4796 Task: isenkram
4797 Section: hardware
4798 Description: Hardware specific packages (autodetected by isenkram)
4799 Based on the detected hardware various hardware specific packages are
4800 proposed.
4801 Test-new-install: mark show
4802 Relevance: 8
4803 Packages: for-current-hardware
4804 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4805
4806 &lt;p&gt;The second part is in
4807 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4808 this:&lt;/p&gt;
4809
4810 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4811 #!/bin/sh
4812 #
4813 (
4814 isenkram-lookup
4815 isenkram-autoinstall-firmware -l
4816 ) | sort -u
4817 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4818
4819 &lt;p&gt;All in all, a very short and simple implementation making it
4820 trivial to install the hardware dependent package we all may want to
4821 have installed on our machines. I&#39;ve not been able to find a way to
4822 get tasksel to tell you exactly which packages it plan to install
4823 before doing the installation. So if you are curious or careful,
4824 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4825
4826 &lt;p&gt;The information about which packages are handling which hardware is
4827 fetched either from the isenkram package itself in
4828 /usr/share/isenkram/, from git.debian.org or from the APT package
4829 database (using the Modaliases header). The APT package database
4830 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4831 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4832 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4833 the python-apt code (bug
4834 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
4835 workaround I was able to get rid of the file descriptor leak and
4836 reduce the memory leak from ~30 MiB per hardware detection down to
4837 around 2 MiB per hardware detection. It should make the desktop
4838 daemon a lot more useful. The fix is in version 0.7 uploaded to
4839 unstable today.&lt;/p&gt;
4840
4841 &lt;p&gt;I believe the current way of mapping hardware to packages in
4842 Isenkram is is a good draft, but in the future I expect isenkram to
4843 use the AppStream data source for this. A proposal for getting proper
4844 AppStream support into Debian is floating around as
4845 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
4846 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
4847 project&lt;/a&gt; will take place this summer to improve the situation. I
4848 look forward to seeing the result, and welcome patches for isenkram to
4849 start using the information when it is ready.&lt;/p&gt;
4850
4851 &lt;p&gt;If you want your package to map to some specific hardware, either
4852 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
4853 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
4854 package&lt;/a&gt; or submit a bug report with the details to the isenkram
4855 package. See also
4856 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
4857 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
4858 the information will be migrated to AppStream eventually, but for the
4859 moment I got no better place to store it.&lt;/p&gt;
4860 </description>
4861 </item>
4862
4863 <item>
4864 <title>FreedomBox milestone - all packages now in Debian Sid</title>
4865 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
4866 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
4867 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
4868 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4869 project&lt;/a&gt; is working on providing the software and hardware to make
4870 it easy for non-technical people to host their data and communication
4871 at home, and being able to communicate with their friends and family
4872 encrypted and away from prying eyes. It is still going strong, and
4873 today a major mile stone was reached.&lt;/p&gt;
4874
4875 &lt;p&gt;Today, the last of the packages currently used by the project to
4876 created the system images were accepted into Debian Unstable. It was
4877 the freedombox-setup package, which is used to configure the images
4878 during build and on the first boot. Now all one need to get going is
4879 the build code from the freedom-maker git repository and packages from
4880 Debian. And once the freedombox-setup package enter testing, we can
4881 build everything directly from Debian. :)&lt;/p&gt;
4882
4883 &lt;p&gt;Some key packages used by Freedombox are
4884 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
4885 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
4886 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
4887 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
4888 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
4889 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
4890 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
4891 are plans to integrate more packages into the setup. User
4892 documentation is maintained on the Debian wiki. Please
4893 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
4894 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
4895
4896 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
4897 setup, run this on a Debian machine using a user with sudo rights to
4898 become root:&lt;/p&gt;
4899
4900 &lt;p&gt;&lt;pre&gt;
4901 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4902 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4903 u-boot-tools
4904 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4905 freedom-maker
4906 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4907 &lt;/pre&gt;&lt;/p&gt;
4908
4909 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4910 devices. See the README in the freedom-maker git repo for more
4911 details on the build. If you do not want all three images, trim the
4912 make line. Note that the virtualbox-image target is not really
4913 virtualbox specific. It create a x86 image usable in kvm, qemu,
4914 vmware and any other x86 virtual machine environment. You might need
4915 the version of vmdebootstrap in Jessie to get the build working, as it
4916 include fixes for a race condition with kpartx.&lt;/p&gt;
4917
4918 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4919 method, boot a Debian Wheezy ISO and use this boot argument to load
4920 the preseed values:&lt;/p&gt;
4921
4922 &lt;p&gt;&lt;pre&gt;
4923 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;
4924 &lt;/pre&gt;&lt;/p&gt;
4925
4926 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
4927 it still work.&lt;/p&gt;
4928
4929 &lt;p&gt;If you wonder how to help, one task you could look at is using
4930 systemd as the boot system. It will become the default for Linux in
4931 Jessie, so we need to make sure it is usable on the Freedombox. I did
4932 a simple test a few weeks ago, and noticed dnsmasq failed to start
4933 during boot when using systemd. I suspect there are other problems
4934 too. :) To detect problems, there is a test suite included, which can
4935 be run from the plinth web interface.&lt;/p&gt;
4936
4937 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4938 us get the new release published. :) Please join us on
4939 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4940 irc.debian.org)&lt;/a&gt; and
4941 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4942 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4943 </description>
4944 </item>
4945
4946 <item>
4947 <title>S3QL, a locally mounted cloud file system - nice free software</title>
4948 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
4949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
4950 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
4951 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
4952 solution for use at home. My requirements are simple, it must be
4953 cheap and locally encrypted (in other words, I keep the encryption
4954 keys, the storage provider do not have access to my private files).
4955 One idea me and my friends had many years ago, before the cloud
4956 storage providers showed up, was to use Google mail as storage,
4957 writing a Linux block device storing blocks as emails in the mail
4958 service provided by Google, and thus get heaps of free space. On top
4959 of this one can add encryption, RAID and volume management to have
4960 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4961 I never found time to implement such system. But the last few weeks I
4962 have looked at a system called
4963 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
4964 mounted network backed file system with the features I need.&lt;/p&gt;
4965
4966 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
4967 handling several different storage providers, any with Amazon S3,
4968 Google Drive or OpenStack API. There are heaps of such storage
4969 providers. S3QL can also use a local directory as storage, which
4970 combined with sshfs allow for file storage on any ssh server. S3QL
4971 include support for encryption, compression, de-duplication, snapshots
4972 and immutable file systems, allowing me to mount the remote storage as
4973 a local mount point, look at and use the files as if they were local,
4974 while the content is stored in the cloud as well. This allow me to
4975 have a backup that should survive fire. The file system can not be
4976 shared between several machines at the same time, as only one can
4977 mount it at the time, but any machine with the encryption key and
4978 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
4979
4980 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
4981 package is included already. So to get started, run &lt;tt&gt;apt-get
4982 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
4983 Greenqloud, after reading their nice recipe on
4984 &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
4985 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
4986 in Iceland more than those in USA when it come to keeping my personal
4987 data safe and private, and thus would rather spend money on a company
4988 in Iceland. Another nice recipe is available from the article
4989 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
4990 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
4991 Admin magazine. When the provider is picked, figure out how to get
4992 the API key needed to connect to the storage API. With Greencloud,
4993 the key did not show up until I had added payment details to my
4994 account.&lt;/p&gt;
4995
4996 &lt;p&gt;Armed with the API access details, it is time to create the file
4997 system. First, create a new bucket in the cloud. This bucket is the
4998 file system storage area. I picked a bucket name reflecting the
4999 machine that was going to store data there, but any name will do.
5000 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
5001 the API login and password, and a locally created password. Store it
5002 all in ~root/.s3ql/authinfo2 like this:
5003
5004 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5005 [s3c]
5006 storage-url: s3c://s.greenqloud.com:443/bucket-name
5007 backend-login: API-login
5008 backend-password: API-password
5009 fs-passphrase: local-password
5010 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5011
5012 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
5013 but any sensible way to create a fairly random password should do it.
5014 Armed with these details, it is now time to run mkfs, entering the API
5015 details and password to create it:&lt;/p&gt;
5016
5017 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5018 # mkdir -m 700 /var/lib/s3ql-cache
5019 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5020 --ssl s3c://s.greenqloud.com:443/bucket-name
5021 Enter backend login:
5022 Enter backend password:
5023 Before using S3QL, make sure to read the user&#39;s guide, especially
5024 the &#39;Important Rules to Avoid Loosing Data&#39; section.
5025 Enter encryption password:
5026 Confirm encryption password:
5027 Generating random encryption key...
5028 Creating metadata tables...
5029 Dumping metadata...
5030 ..objects..
5031 ..blocks..
5032 ..inodes..
5033 ..inode_blocks..
5034 ..symlink_targets..
5035 ..names..
5036 ..contents..
5037 ..ext_attributes..
5038 Compressing and uploading metadata...
5039 Wrote 0.00 MB of compressed metadata.
5040 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5041
5042 &lt;p&gt;The next step is mounting the file system to make the storage available.
5043
5044 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5045 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5046 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5047 Using 4 upload threads.
5048 Downloading and decompressing metadata...
5049 Reading metadata...
5050 ..objects..
5051 ..blocks..
5052 ..inodes..
5053 ..inode_blocks..
5054 ..symlink_targets..
5055 ..names..
5056 ..contents..
5057 ..ext_attributes..
5058 Mounting filesystem...
5059 # df -h /s3ql
5060 Filesystem Size Used Avail Use% Mounted on
5061 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
5062 #
5063 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5064
5065 &lt;p&gt;The file system is now ready for use. I use rsync to store my
5066 backups in it, and as the metadata used by rsync is downloaded at
5067 mount time, no network traffic (and storage cost) is triggered by
5068 running rsync. To unmount, one should not use the normal umount
5069 command, as this will not flush the cache to the cloud storage, but
5070 instead running the umount.s3ql command like this:
5071
5072 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5073 # umount.s3ql /s3ql
5074 #
5075 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5076
5077 &lt;p&gt;There is a fsck command available to check the file system and
5078 correct any problems detected. This can be used if the local server
5079 crashes while the file system is mounted, to reset the &quot;already
5080 mounted&quot; flag. This is what it look like when processing a working
5081 file system:&lt;/p&gt;
5082
5083 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5084 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
5085 Using cached metadata.
5086 File system seems clean, checking anyway.
5087 Checking DB integrity...
5088 Creating temporary extra indices...
5089 Checking lost+found...
5090 Checking cached objects...
5091 Checking names (refcounts)...
5092 Checking contents (names)...
5093 Checking contents (inodes)...
5094 Checking contents (parent inodes)...
5095 Checking objects (reference counts)...
5096 Checking objects (backend)...
5097 ..processed 5000 objects so far..
5098 ..processed 10000 objects so far..
5099 ..processed 15000 objects so far..
5100 Checking objects (sizes)...
5101 Checking blocks (referenced objects)...
5102 Checking blocks (refcounts)...
5103 Checking inode-block mapping (blocks)...
5104 Checking inode-block mapping (inodes)...
5105 Checking inodes (refcounts)...
5106 Checking inodes (sizes)...
5107 Checking extended attributes (names)...
5108 Checking extended attributes (inodes)...
5109 Checking symlinks (inodes)...
5110 Checking directory reachability...
5111 Checking unix conventions...
5112 Checking referential integrity...
5113 Dropping temporary indices...
5114 Backing up old metadata...
5115 Dumping metadata...
5116 ..objects..
5117 ..blocks..
5118 ..inodes..
5119 ..inode_blocks..
5120 ..symlink_targets..
5121 ..names..
5122 ..contents..
5123 ..ext_attributes..
5124 Compressing and uploading metadata...
5125 Wrote 0.89 MB of compressed metadata.
5126 #
5127 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5128
5129 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
5130 quick, about the same speed as local file access. Uploading large
5131 amount of data is to me limited by the bandwidth out of and into my
5132 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
5133 which is very close to my upload speed, and downloading the same
5134 Debian installation ISO gave me 610 kiB/s, close to my download speed.
5135 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
5136 network, not the file system code. I do not know what a good cache
5137 size would be, but suspect that the cache should e larger than your
5138 working set.&lt;/p&gt;
5139
5140 &lt;p&gt;I mentioned that only one machine can mount the file system at the
5141 time. If another machine try, it is told that the file system is
5142 busy:&lt;/p&gt;
5143
5144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5145 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5146 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5147 Using 8 upload threads.
5148 Backend reports that fs is still mounted elsewhere, aborting.
5149 #
5150 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5151
5152 &lt;p&gt;The file content is uploaded when the cache is full, while the
5153 metadata is uploaded once every 24 hour by default. To ensure the
5154 file system content is flushed to the cloud, one can either umount the
5155 file system, or ask S3QL to flush the cache and metadata using
5156 s3qlctrl:
5157
5158 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5159 # s3qlctrl upload-meta /s3ql
5160 # s3qlctrl flushcache /s3ql
5161 #
5162 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5163
5164 &lt;p&gt;If you are curious about how much space your data uses in the
5165 cloud, and how much compression and deduplication cut down on the
5166 storage usage, you can use s3qlstat on the mounted file system to get
5167 a report:&lt;/p&gt;
5168
5169 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5170 # s3qlstat /s3ql
5171 Directory entries: 9141
5172 Inodes: 9143
5173 Data blocks: 8851
5174 Total data size: 22049.38 MB
5175 After de-duplication: 21955.46 MB (99.57% of total)
5176 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
5177 Database size: 2.39 MB (uncompressed)
5178 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5179 #
5180 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5181
5182 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
5183 storage. I did not try to locate them all, but am aware of at least
5184 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
5185 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
5186 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
5187 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
5188 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
5189 accept payment in Bitcoin. Pick one that suit your need. Some of
5190 them provide several GiB of free storage, but the prize models are
5191 quite different and you will have to figure out what suits you
5192 best.&lt;/p&gt;
5193
5194 &lt;p&gt;While researching this blog post, I had a look at research papers
5195 and posters discussing the S3QL file system. There are several, which
5196 told me that the file system is getting a critical check by the
5197 science community and increased my confidence in using it. One nice
5198 poster is titled
5199 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
5200 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5201 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
5202 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5203 and Pamela Smith. Please have a look.&lt;/p&gt;
5204
5205 &lt;p&gt;Given my problems with different file systems earlier, I decided to
5206 check out the mounted S3QL file system to see if it would be usable as
5207 a home directory (in other word, that it provided POSIX semantics when
5208 it come to locking and umask handling etc). Running
5209 &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
5210 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
5211 no error was found. So the file system can be used for home
5212 directories, if one chooses to do so.&lt;/p&gt;
5213
5214 &lt;p&gt;If you do not want a locally file system, and want something that
5215 work without the Linux fuse file system, I would like to mention the
5216 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
5217 provide locally encrypted backup using a command line client. It have
5218 a nicer access control system, where one can split out read and write
5219 access, allowing some systems to write to the backup and others to
5220 only read from it.&lt;/p&gt;
5221
5222 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5223 activities, please send Bitcoin donations to my address
5224 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5225 </description>
5226 </item>
5227
5228 <item>
5229 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
5230 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
5231 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
5232 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
5233 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5234 project&lt;/a&gt; is working on providing the software and hardware for
5235 making it easy for non-technical people to host their data and
5236 communication at home, and being able to communicate with their
5237 friends and family encrypted and away from prying eyes. It has been
5238 going on for a while, and is slowly progressing towards a new test
5239 release (0.2).&lt;/p&gt;
5240
5241 &lt;p&gt;And what day could be better than the Pi day to announce that the
5242 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
5243 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5244 system), and can also be installed using a Debian installer preseed
5245 file. The Debian based Freedombox is now based on Debian Jessie,
5246 where most of the needed packages used are already present. Only one,
5247 the freedombox-setup package, is missing. To try to build your own
5248 boot image to test the current status, fetch the freedom-maker scripts
5249 and build using
5250 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
5251 with a user with sudo access to become root:
5252
5253 &lt;pre&gt;
5254 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5255 freedom-maker
5256 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5257 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5258 u-boot-tools
5259 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5260 &lt;/pre&gt;
5261
5262 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5263 devices. See the README for more details on the build. If you do not
5264 want all three images, trim the make line. But note that thanks to &lt;a
5265 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
5266 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
5267 kpartx call.&lt;/p&gt;
5268
5269 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5270 method, boot a Debian Wheezy ISO and use this boot argument to load
5271 the preseed values:&lt;/p&gt;
5272
5273 &lt;pre&gt;
5274 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;
5275 &lt;/pre&gt;
5276
5277 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
5278 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
5279 currently hang while setting up APT sources. Killing the
5280 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
5281 installation will get the installation going. This affect all
5282 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
5283
5284 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5285 us get the new release published. :) Please join us on
5286 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5287 irc.debian.org)&lt;/a&gt; and
5288 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5289 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5290 </description>
5291 </item>
5292
5293 <item>
5294 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
5295 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
5296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
5297 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
5298 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
5299 innetgr tools, because I needed them in
5300 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
5301 ng-utils, and it has served me well. I placed the project under the
5302 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
5303 repository. But many years ago, the CVS repository was dropped (lost,
5304 not migrated to new hardware, not sure), and the project have lacked a
5305 proper home since then.&lt;/p&gt;
5306
5307 &lt;p&gt;Last summer, I had a look at the package and made a new release
5308 fixing a irritating crash bug, but was unable to store the changes in
5309 a proper source control system. I applied for a project on
5310 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
5311 to follow up on it. Until today. :)&lt;/p&gt;
5312
5313 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
5314 now have a new home, and a git repository with the highlight of the
5315 history of the project. I published all release tarballs and imported
5316 them into the git repository. As the project is really stable and not
5317 expected to gain new features any time soon, I decided to make a new
5318 release and call it 1.0. Visit the new project home on
5319 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
5320 if you want to check it out. The new version is also uploaded into
5321 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
5322 </description>
5323 </item>
5324
5325 <item>
5326 <title>Testing sysvinit from experimental in Debian Hurd</title>
5327 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
5328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
5329 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
5330 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
5331 their changes into sysvinit, to allow them to use the normal sysvinit
5332 boot system instead of their old one. This follow up on the
5333 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
5334 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
5335 get Debian on Hurd working more like Debian on Linux. To get started,
5336 I downloaded a prebuilt hard disk image from
5337 &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;,
5338 and started it using virt-manager.&lt;/p&gt;
5339
5340 &lt;p&gt;The first think I had to do after logging in (root without any
5341 password) was to get the network operational. I followed
5342 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5343 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5344 commands as root to get the machine to accept a IP address from the
5345 kvm internal DHCP server:&lt;/p&gt;
5346
5347 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5348 settrans -fgap /dev/netdde /hurd/netdde
5349 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5350 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5351 dhclient /dev/eth0
5352 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5353
5354 &lt;p&gt;After this, the machine had internet connectivity, and I could
5355 upgrade it and install the sysvinit packages from experimental and
5356 enable it as the default boot system in Hurd.&lt;/p&gt;
5357
5358 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5359 running on the machine it for ssh login to work a password need to be
5360 set. Also, note that a bug somewhere in openssh on Hurd block
5361 compression from working. Remember to turn that off on the client
5362 side.&lt;/p&gt;
5363
5364 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5365 stuff:&lt;/p&gt;
5366
5367 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5368 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5369 deb http://http.debian.net/debian/ experimental main
5370 EOF
5371 apt-get update
5372 apt-get dist-upgrade
5373 apt-get install -t experimental initscripts sysv-rc sysvinit \
5374 sysvinit-core sysvinit-utils
5375 update-alternatives --config runsystem
5376 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5377
5378 &lt;p&gt;To reboot after switching boot system, you have to use
5379 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5380 yet a sysvinit process able to receive the signals from the normal
5381 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5382 upgrading every package and rebooting, the network come up with DHCP
5383 after boot as it should, and the settrans/pkill hack mentioned at the
5384 start is no longer needed. But for some strange reason, there are no
5385 longer any login prompt in the virtual console, so I logged in using
5386 ssh instead.
5387
5388 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5389 fail some times. No idea what the cause is, but hope the Hurd porters
5390 figure it out. At least Justus said on IRC (#debian-hurd on
5391 irc.debian.org) that they are aware of the problem. A way to reduce
5392 the impact is to upgrade to the Hurd packages built by Justus by
5393 adding this repository to the machine:&lt;/p&gt;
5394
5395 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5396 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5397 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5398 EOF
5399 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5400
5401 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5402 http://ftp.debian-ports.org/debian, because some of the packages in
5403 unstable do not yet include the required patches that are lingering in
5404 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5405
5406 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5407 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5408 i emacs - GNU Emacs editor (metapackage)
5409 i gdb - GNU Debugger
5410 i hurd-recommended - Miscellaneous translators
5411 i isc-dhcp-client - ISC DHCP client
5412 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5413 i libc-bin - Embedded GNU C Library: Binaries
5414 i libc-dev-bin - Embedded GNU C Library: Development binaries
5415 i libc0.3 - Embedded GNU C Library: Shared libraries
5416 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5417 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5418 i multiarch-support - Transitional package to ensure multiarch compatibilit
5419 i A x11-common - X Window System (X.Org) infrastructure
5420 i xorg - X.Org X Window System
5421 i A xserver-xorg - X.Org X server
5422 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5423 #
5424 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5425
5426 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5427 X.org did not work out of the box and I never took the time to follow
5428 the porters instructions to fix it. This time I was interested in the
5429 command line stuff.&lt;p&gt;
5430 </description>
5431 </item>
5432
5433 <item>
5434 <title>New chrpath release 0.16</title>
5435 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5436 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5437 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5438 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5439 find problems in C, C++ and Java code using static source code
5440 analysis. It can detect a lot of different problems, and is very
5441 useful to find memory and locking bugs in the error handling part of
5442 the source. The company behind it provide
5443 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5444 a community service&lt;/a&gt;, and many hundred free software projects are
5445 already checked. A few days ago I decided to have a closer look at
5446 the Coverity system, and discovered that the
5447 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5448 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5449 projects I am involved with was already registered. But these are
5450 fairly big, and I would also like to have a small and easy project to
5451 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5452 checking of the chrpath project&lt;/a&gt;. It was
5453 added to the checker and discovered seven potential defects. Six of
5454 these were real, mostly resource &quot;leak&quot; when the program detected an
5455 error. Nothing serious, as the resources would be released a fraction
5456 of a second later when the program exited because of the error, but it
5457 is nice to do it right in case the source of the program some time in
5458 the future end up in a library. Having fixed all defects and added
5459 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5460 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5461 publish a new release. These are the release notes:&lt;/p&gt;
5462
5463 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5464
5465 &lt;ul&gt;
5466
5467 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5468 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5469 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5470
5471 &lt;/ul&gt;
5472
5473 &lt;p&gt;You can
5474 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5475 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5476 project if something is wrong with the new release. The test suite
5477 did not discover any old errors, so if you find a new one, please also
5478 include a test suite check.&lt;/p&gt;
5479 </description>
5480 </item>
5481
5482 <item>
5483 <title>New chrpath release 0.15</title>
5484 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5486 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5487 <description>&lt;p&gt;After many years break from the package and a vain hope that
5488 development would be continued by someone else, I finally pulled my
5489 acts together this morning and wrapped up a new release of chrpath,
5490 the command line tool to modify the rpath and runpath of already
5491 compiled ELF programs. The update was triggered by the persistence of
5492 Isha Vishnoi at IBM, which needed a new config.guess file to get
5493 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5494 is working on. I checked the
5495 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5496 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5497 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5498 packages for interesting patches (failed to find the source from
5499 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5500 These are the release notes:&lt;/p&gt;
5501
5502 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5503
5504 &lt;ul&gt;
5505
5506 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5507 with newer architectures. Thanks to isha vishnoi for the heads
5508 up.&lt;/li&gt;
5509
5510 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5511
5512 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5513 Matthias Klose.&lt;/li&gt;
5514
5515 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5516 Petr Machata found in Fedora.&lt;/li&gt;
5517
5518 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5519 .dynamic is a NULL terminated string. Based on patch found in
5520 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5521
5522 &lt;/ul&gt;
5523
5524 &lt;p&gt;You can
5525 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5526 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5527 project if something is wrong with the new release. The test suite
5528 did not discover any old errors, so if you find a new one, please also
5529 include a testsuite check.&lt;/p&gt;
5530 </description>
5531 </item>
5532
5533 <item>
5534 <title>Debian init.d boot script example for rsyslog</title>
5535 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5536 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5537 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5538 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5539 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5540 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5541 init.d scripts at all. Here is an example init.d script, ie a rewrite
5542 of /etc/init.d/rsyslog:&lt;/p&gt;
5543
5544 &lt;p&gt;&lt;pre&gt;
5545 #!/lib/init/init-d-script
5546 ### BEGIN INIT INFO
5547 # Provides: rsyslog
5548 # Required-Start: $remote_fs $time
5549 # Required-Stop: umountnfs $time
5550 # X-Stop-After: sendsigs
5551 # Default-Start: 2 3 4 5
5552 # Default-Stop: 0 1 6
5553 # Short-Description: enhanced syslogd
5554 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5555 # It is quite compatible to stock sysklogd and can be
5556 # used as a drop-in replacement.
5557 ### END INIT INFO
5558 DESC=&quot;enhanced syslogd&quot;
5559 DAEMON=/usr/sbin/rsyslogd
5560 &lt;/pre&gt;&lt;/p&gt;
5561
5562 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5563 script was 137 lines, and the above is just 15 lines, most of it meta
5564 info/comments.&lt;/p&gt;
5565
5566 &lt;p&gt;How to do this, you ask? Well, one create a new script
5567 /lib/init/init-d-script looking something like this:
5568
5569 &lt;p&gt;&lt;pre&gt;
5570 #!/bin/sh
5571
5572 # Define LSB log_* functions.
5573 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5574 # and status_of_proc is working.
5575 . /lib/lsb/init-functions
5576
5577 #
5578 # Function that starts the daemon/service
5579
5580 #
5581 do_start()
5582 {
5583 # Return
5584 # 0 if daemon has been started
5585 # 1 if daemon was already running
5586 # 2 if daemon could not be started
5587 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5588 || return 1
5589 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5590 $DAEMON_ARGS \
5591 || return 2
5592 # Add code here, if necessary, that waits for the process to be ready
5593 # to handle requests from services started subsequently which depend
5594 # on this one. As a last resort, sleep for some time.
5595 }
5596
5597 #
5598 # Function that stops the daemon/service
5599 #
5600 do_stop()
5601 {
5602 # Return
5603 # 0 if daemon has been stopped
5604 # 1 if daemon was already stopped
5605 # 2 if daemon could not be stopped
5606 # other if a failure occurred
5607 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5608 RETVAL=&quot;$?&quot;
5609 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5610 # Wait for children to finish too if this is a daemon that forks
5611 # and if the daemon is only ever run from this initscript.
5612 # If the above conditions are not satisfied then add some other code
5613 # that waits for the process to drop all resources that could be
5614 # needed by services started subsequently. A last resort is to
5615 # sleep for some time.
5616 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5617 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5618 # Many daemons don&#39;t delete their pidfiles when they exit.
5619 rm -f $PIDFILE
5620 return &quot;$RETVAL&quot;
5621 }
5622
5623 #
5624 # Function that sends a SIGHUP to the daemon/service
5625 #
5626 do_reload() {
5627 #
5628 # If the daemon can reload its configuration without
5629 # restarting (for example, when it is sent a SIGHUP),
5630 # then implement that here.
5631 #
5632 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5633 return 0
5634 }
5635
5636 SCRIPTNAME=$1
5637 scriptbasename=&quot;$(basename $1)&quot;
5638 echo &quot;SN: $scriptbasename&quot;
5639 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5640 script=&quot;$1&quot;
5641 shift
5642 . $script
5643 else
5644 exit 0
5645 fi
5646
5647 NAME=$(basename $DAEMON)
5648 PIDFILE=/var/run/$NAME.pid
5649
5650 # Exit if the package is not installed
5651 #[ -x &quot;$DAEMON&quot; ] || exit 0
5652
5653 # Read configuration variable file if it is present
5654 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5655
5656 # Load the VERBOSE setting and other rcS variables
5657 . /lib/init/vars.sh
5658
5659 case &quot;$1&quot; in
5660 start)
5661 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5662 do_start
5663 case &quot;$?&quot; in
5664 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5665 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5666 esac
5667 ;;
5668 stop)
5669 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5670 do_stop
5671 case &quot;$?&quot; in
5672 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5673 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5674 esac
5675 ;;
5676 status)
5677 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5678 ;;
5679 #reload|force-reload)
5680 #
5681 # If do_reload() is not implemented then leave this commented out
5682 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5683 #
5684 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5685 #do_reload
5686 #log_end_msg $?
5687 #;;
5688 restart|force-reload)
5689 #
5690 # If the &quot;reload&quot; option is implemented then remove the
5691 # &#39;force-reload&#39; alias
5692 #
5693 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5694 do_stop
5695 case &quot;$?&quot; in
5696 0|1)
5697 do_start
5698 case &quot;$?&quot; in
5699 0) log_end_msg 0 ;;
5700 1) log_end_msg 1 ;; # Old process is still running
5701 *) log_end_msg 1 ;; # Failed to start
5702 esac
5703 ;;
5704 *)
5705 # Failed to stop
5706 log_end_msg 1
5707 ;;
5708 esac
5709 ;;
5710 *)
5711 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5712 exit 3
5713 ;;
5714 esac
5715
5716 :
5717 &lt;/pre&gt;&lt;/p&gt;
5718
5719 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5720 lot. I did not really polish the approach, so it might not always
5721 work out of the box, but you get the idea. I did not try very hard to
5722 optimize it nor make it more robust either.&lt;/p&gt;
5723
5724 &lt;p&gt;A better argument for switching init system in Debian than reducing
5725 the size of init scripts (which is a good thing to do anyway), is to
5726 get boot system that is able to handle the kernel events sensibly and
5727 robustly, and do not depend on the boot to run sequentially. The boot
5728 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5729 </description>
5730 </item>
5731
5732 <item>
5733 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5734 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5735 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5736 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5737 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5738 remote display access is the preferred solution with oVirt and RedHat
5739 Enterprise Virtualization, and I was sad to discover the other day
5740 that the browser plugin needed to use these systems seamlessly was
5741 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5742 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5743 2013-04-01, so I decided to wrap up a package based on the great work
5744 from Cajus Pollmeier and put it in a collab-maint maintained git
5745 repository to get a package I could use. I would very much like
5746 others to help me maintain the package (or just take over, I do not
5747 mind), but as no-one had volunteered so far, I just uploaded it to
5748 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5749
5750 &lt;p&gt;The source is now available from
5751 &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;
5752 </description>
5753 </item>
5754
5755 <item>
5756 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5757 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5758 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5759 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5760 <description>&lt;p&gt;The
5761 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5762 program is a a very nice system to create virtual machine images. It
5763 create a image file, add a partition table, mount it and run
5764 debootstrap in the mounted directory to create a Debian system on a
5765 stick. Yesterday, I decided to try to teach it how to make images for
5766 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5767 of a plan to simplify the build system for
5768 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5769 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5770 the virtualbox images, but its current build system made multistrap
5771 based system for Dreamplug images, and it is lacking support for
5772 Raspberry Pi.&lt;/p&gt;
5773
5774 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5775 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5776 code and adjusted it to be able to build armel images on my amd64
5777 Debian laptop. I ended up giving vmdebootstrap five new options,
5778 allowing me to replicate the image creation process I use to make
5779 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5780 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5781 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5782 call debootstrap with --foreign and to copy the handler into the
5783 generated chroot before running the second stage. This allow
5784 vmdebootstrap to create armel images on an amd64 host. Next I added
5785 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5786 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5787 given file system type, allowing me to create an image with a vfat
5788 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5789 variant&lt;/tt&gt; option to allow me to create smaller images without the
5790 Debian base system packages installed. Finally, I added an option
5791 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5792 as a boot loader. It is not needed on the Raspberry Pi and probably
5793 most other non-x86 architectures. The changes were accepted by the
5794 upstream author of vmdebootstrap yesterday and today, and is now
5795 available from
5796 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5797 upstream project page&lt;/a&gt;.&lt;/p&gt;
5798
5799 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5800 create a small script (the customize script) to add the non-free
5801 binary blob needed to boot the Raspberry Pi and the APT source
5802 list:&lt;/p&gt;
5803
5804 &lt;p&gt;&lt;pre&gt;
5805 #!/bin/sh
5806 set -e # Exit on first error
5807 rootdir=&quot;$1&quot;
5808 cd &quot;$rootdir&quot;
5809 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5810 deb http://http.debian.net/debian/ jessie main contrib non-free
5811 EOF
5812 # Install non-free binary blob needed to boot Raspberry Pi. This
5813 # install a kernel somewhere too.
5814 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5815 -O $rootdir/usr/bin/rpi-update
5816 chmod a+x $rootdir/usr/bin/rpi-update
5817 mkdir -p $rootdir/lib/modules
5818 touch $rootdir/boot/start.elf
5819 chroot $rootdir rpi-update
5820 &lt;/pre&gt;&lt;/p&gt;
5821
5822 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5823 to build the image:&lt;/p&gt;
5824
5825 &lt;pre&gt;
5826 sudo ./vmdebootstrap \
5827 --variant minbase \
5828 --arch armel \
5829 --distribution jessie \
5830 --mirror http://http.debian.net/debian \
5831 --image test.img \
5832 --size 600M \
5833 --bootsize 64M \
5834 --boottype vfat \
5835 --log-level debug \
5836 --verbose \
5837 --no-kernel \
5838 --no-extlinux \
5839 --root-password raspberry \
5840 --hostname raspberrypi \
5841 --foreign /usr/bin/qemu-arm-static \
5842 --customize `pwd`/customize \
5843 --package netbase \
5844 --package git-core \
5845 --package binutils \
5846 --package ca-certificates \
5847 --package wget \
5848 --package kmod
5849 &lt;/pre&gt;&lt;/p&gt;
5850
5851 &lt;p&gt;The list of packages being installed are the ones needed by
5852 rpi-update to make the image bootable on the Raspberry Pi, with the
5853 exception of netbase, which is needed by debootstrap to find
5854 /etc/hosts with the minbase variant. I really wish there was a way to
5855 set up an Raspberry Pi using only packages in the Debian archive, but
5856 that is not possible as far as I know, because it boots from the GPU
5857 using a non-free binary blob.&lt;/p&gt;
5858
5859 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
5860 probably a few others installed. I have not checked the complete
5861 build dependency list.&lt;/p&gt;
5862
5863 &lt;p&gt;The resulting image will not use the hardware floating point unit
5864 on the Raspberry PI, because the armel architecture in Debian is not
5865 optimized for that use. So the images created will be a bit slower
5866 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
5867 </description>
5868 </item>
5869
5870 <item>
5871 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
5872 <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>
5873 <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>
5874 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
5875 <description>&lt;p&gt;The last few days I came across a few good causes that should get
5876 wider attention. I recommend signing and donating to each one of
5877 these. :)&lt;/p&gt;
5878
5879 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
5880 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
5881 Women program which is a Google Summer of Code like initiative to get
5882 more women involved in free software. One debian sponsor has offered
5883 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
5884 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
5885 hope you will to. :)&lt;/p&gt;
5886
5887 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
5888 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
5889 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
5890 take place these days, and their need to fund the work. I&#39;ve already
5891 donated. Are you next?&lt;/p&gt;
5892
5893 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
5894 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5895 statement under the heading
5896 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
5897 Access&lt;/a&gt; for those of us asking for more focus on open access in the
5898 Norwegian government. So far 499 signatures. I hope you will sign it
5899 too.&lt;/p&gt;
5900 </description>
5901 </item>
5902
5903 <item>
5904 <title>Videos about the Freedombox project - for inspiration and learning</title>
5905 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
5906 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
5907 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
5908 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
5909 project&lt;/a&gt; have been going on for a while, and have presented the
5910 vision, ideas and solution several places. Here is a little
5911 collection of videos of talks and presentation of the project.&lt;/p&gt;
5912
5913 &lt;ul&gt;
5914
5915 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
5916 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
5917
5918 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
5919 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5920
5921 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
5922 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5923 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
5924 (Youtube)&lt;/li&gt;
5925
5926 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
5927 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
5928
5929 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
5930 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5931
5932 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
5933 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5934 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
5935
5936 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
5937 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
5938 (Youtube)&lt;/li&gt;
5939
5940 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
5941 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
5942
5943 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
5944 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
5945
5946 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
5947 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5948 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
5949
5950 &lt;/ul&gt;
5951
5952 &lt;p&gt;A larger list is available from
5953 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
5954 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
5955
5956 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
5957 Jessie is coming along quite well, and soon both Owncloud and using
5958 Tor should be available for testers of the Freedombox solution. :) In
5959 a few weeks I hope everything needed to test it is included in Debian.
5960 The withsqlite package is already in Debian, and the plinth package is
5961 pending in NEW. The third and vital part of that puzzle is the
5962 metapackage/setup framework, which is still pending an upload. Join
5963 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
5964 (#freedombox on irc.debian.org)&lt;/a&gt; and
5965 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5966 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5967 </description>
5968 </item>
5969
5970 <item>
5971 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
5972 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
5973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
5974 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
5975 <description>&lt;p&gt;I was introduced to the
5976 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
5977 in 2010, when Eben Moglen presented his vision about serving the need
5978 of non-technical people to keep their personal information private and
5979 within the legal protection of their own homes. The idea is to give
5980 people back the power over their network and machines, and return
5981 Internet back to its intended peer-to-peer architecture. Instead of
5982 depending on a central service, the Freedombox will give everyone
5983 control over their own basic infrastructure.&lt;/p&gt;
5984
5985 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
5986 taken priority. But this summers nasty news about the misuse of trust
5987 and privilege exercised by the &quot;western&quot; intelligence gathering
5988 communities increased my eagerness to contribute to a point where I
5989 actually started working on the project a while back.&lt;/p&gt;
5990
5991 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
5992 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
5993 create a simple and cheap Debian based appliance that anyone can hook
5994 up in their home and get access to secure and private services and
5995 communication. The initial deployment platform have been the
5996 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
5997 which is a piece of hardware I do not own. So to be able to test what
5998 the current Freedombox setup look like, I had to come up with a way to install
5999 it on some hardware I do have access to. I have rewritten the
6000 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
6001 image build framework to use .deb packages instead of only copying
6002 setup into the boot images, and thanks to this rewrite I am able to
6003 set up any machine supported by Debian Wheezy as a Freedombox, using
6004 the previously mentioned deb (and a few support debs for packages
6005 missing in Debian).&lt;/p&gt;
6006
6007 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
6008 scripts
6009 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
6010 and a administrative web interface
6011 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
6012 withsqlite), as well as a privacy enhancing proxy based on
6013 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
6014 (freedombox-privoxy). There is also a web/javascript based XMPP
6015 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
6016 trying (unsuccessfully so far) to talk to the XMPP server
6017 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
6018 web interface is pluggable, and the goal is to use it to enable OpenID
6019 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6020 this is really working yet, see
6021 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
6022 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
6023 on github at the moment. The HTTP proxy is operational out of the
6024 box, and the admin web interface can be used to add/remove plinth
6025 users. I&#39;ve not been able to do anything else with it so far, but
6026 know there are several branches spread around github and other places
6027 with lots of half baked features.&lt;/p&gt;
6028
6029 &lt;p&gt;Anyway, if you want to have a look at the current state, the
6030 following recipes should work to give you a test machine to poke
6031 at.&lt;/p&gt;
6032
6033 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
6034
6035 &lt;ol&gt;
6036
6037 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
6038 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
6039 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
6040 to the Debian installer:&lt;p&gt;
6041 &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;
6042
6043 &lt;li&gt;Answer the few language/region/password questions and pick disk to
6044 install on.&lt;/li&gt;
6045
6046 &lt;li&gt;When the installation is finished and the machine have rebooted a
6047 few times, your Freedombox is ready for testing.&lt;/li&gt;
6048
6049 &lt;/ol&gt;
6050
6051 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
6052
6053 &lt;ol&gt;
6054
6055 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
6056 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
6057 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
6058 &lt;pre&gt;
6059 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
6060 &lt;/pre&gt;&lt;/li&gt;
6061 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
6062 &lt;pre&gt;
6063 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6064 apt-key add -
6065 apt-get update
6066 apt-get install freedombox-setup
6067 /usr/lib/freedombox/setup
6068 &lt;/pre&gt;&lt;/li&gt;
6069 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
6070
6071 &lt;/ol&gt;
6072
6073 &lt;p&gt;You can test it on other architectures too, but because the
6074 freedombox-privoxy package is binary, it will only work as intended on
6075 the architectures where I have had time to build the binary and put it
6076 in my APT repository. But do not let this stop you. It is only a
6077 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
6078
6079 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
6080 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
6081 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
6082 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
6083
6084 &lt;p&gt;Please let me know if this works for you, or if you have any
6085 problems. We gather on the IRC channel
6086 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
6087 irc.debian.org and the
6088 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
6089 mailing list&lt;/a&gt;.&lt;/p&gt;
6090
6091 &lt;p&gt;Once you get your freedombox operational, you can visit
6092 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
6093 welcome screen (dead end - do not be surprised if you are unable to
6094 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
6095 to look at the rest of plinth. The default user is &#39;admin&#39; and the
6096 default password is &#39;secret&#39;.&lt;/p&gt;
6097 </description>
6098 </item>
6099
6100 <item>
6101 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
6102 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
6103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
6104 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
6105 <description>&lt;p&gt;Earlier, I reported about
6106 &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
6107 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
6108 told by IBM that the original disk should be thrown away. And as
6109 there no longer was a problem if I bricked the firmware, I decided
6110 today to try to install Intel firmware to replace the Lenovo firmware
6111 currently on the disk.&lt;/p&gt;
6112
6113 &lt;p&gt;I searched the Intel site for firmware, and found
6114 &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;
6115 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6116 according to the site should contain the latest firmware for SSD
6117 disks. I inserted the broken disk in one of my spare laptops and
6118 booted the ISO from a USB stick. The disk was recognized, but the
6119 program claimed the newest firmware already were installed and refused
6120 to insert any Intel firmware. So no change, and the disk is still
6121 unable to handle write load. :( I guess the only way to get them
6122 working would be if Lenovo releases new firmware. No idea how likely
6123 that is. Anyway, just blogging about this test for completeness. I
6124 got a working Samsung disk, and see no point in spending more time on
6125 the broken disks.&lt;/p&gt;
6126 </description>
6127 </item>
6128
6129 <item>
6130 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
6131 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
6132 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
6133 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
6134 <description>&lt;p&gt;Today I switched to
6135 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
6136 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
6137 my new Thinkpad X230, which was delivered with an
6138 &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
6139 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
6140 sustained writes. My hardware supplier have been very forthcoming in
6141 trying to find a solution, and after first trying with another
6142 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
6143 disk instead to fix it once and for all. The Samsung disk survived
6144 the installation of Debian with encrypted disks (filling the disk with
6145 random data during installation killed the first two), and I thus
6146 decided to trust it with my data. I have installed it as a Debian Edu
6147 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6148 server at home using Kerberos and LDAP, and will use it as my work
6149 station from now on.&lt;/p&gt;
6150
6151 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
6152 Debian Wheezy default installation need to be tuned a bit to increase
6153 performance and increase life time of the disk. The Linux kernel and
6154 user space applications do not yet adjust automatically to such
6155 environment. To make it easier for my self, I created a draft Debian
6156 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
6157 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
6158 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
6159 is set up to adjust the setup of the machine by just installing the
6160 package. If there is any non-SSD disk in the machine, the package
6161 will refuse to install, as I did not try to write any logic to sort
6162 file systems in SSD and non-SSD file systems.&lt;/p&gt;
6163
6164 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
6165 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6166 where I set up the machine with one large encrypted partition (in
6167 addition to /boot), put LVM on top of this and set up partitions on
6168 top of this again. See the README file in the package source for the
6169 references I used to pick the settings. At the moment these
6170 parameters are tuned:&lt;/p&gt;
6171
6172 &lt;ul&gt;
6173
6174 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
6175 (adding discard to /etc/crypttab)&lt;/li&gt;
6176
6177 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
6178 this case a cryptsetup partition) by changing issue_discards from
6179 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
6180
6181 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
6182 systems.&lt;/li&gt;
6183
6184 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
6185 /etc/fstab.&lt;/li&gt;
6186
6187 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
6188
6189 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
6190 cron.daily).&lt;/li&gt;
6191
6192 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
6193 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
6194
6195 &lt;/ul&gt;
6196
6197 &lt;p&gt;During installation, I cancelled the part where the installer fill
6198 the disk with random data, as this would kill the SSD performance for
6199 little gain. My goal with the encrypted file system is to ensure
6200 those stealing my laptop end up with a brick and not a working
6201 computer. I have no hope in keeping the really resourceful people
6202 from getting the data on the disk (see
6203 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
6204 Thus I concluded that adding the discard option to crypttab is the
6205 right thing to do.&lt;/p&gt;
6206
6207 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
6208 it for SSD, but others recommended deadline and a benchmark I found
6209 indicated that deadline might be better for interactive use.&lt;/p&gt;
6210
6211 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
6212 and ext4, but read that it would give a performance hit ever time a
6213 file is removed, and thought it best to that that slowdown once a day
6214 instead of during my work.&lt;/p&gt;
6215
6216 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6217 this is already done by Debian Edu.&lt;/p&gt;
6218
6219 &lt;p&gt;I have not yet started on the user space tuning. I expect
6220 iceweasel need some tuning, and perhaps other applications too, but
6221 have not yet had time to investigate those parts.&lt;/p&gt;
6222
6223 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
6224 there.&lt;/p&gt;
6225
6226 &lt;p&gt;As for the answer to the question in the title of this blog post,
6227 as far as I know, the only solution I know about is to replace the
6228 disk. It might be possible to flash it with Intel firmware instead of
6229 the Lenovo firmware. But I have not tried and did not want to do so
6230 without approval from Lenovo as I wanted to keep the warranty on the
6231 disk until a solution was found and they wanted the broken disks
6232 back.&lt;/p&gt;
6233 </description>
6234 </item>
6235
6236 <item>
6237 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
6238 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
6239 <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>
6240 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
6241 <description>&lt;p&gt;A few days ago, I wrote about
6242 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
6243 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
6244 was dying during installation because it is unable to cope with
6245 sustained write. My supplier is in contact with
6246 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
6247 replacement disk to try to fix the problem. They decided to send an
6248 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
6249
6250 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
6251 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6252 same firmware version as the original. This time my hope raised
6253 slightly as the installation progressed, as the original disk used to
6254 die after 4-7% of the disk was written to, while this time it kept
6255 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
6256 died again and I was back on square one. I still do not have a new
6257 laptop with a disk I can trust. I can not live with a disk that might
6258 lock up when I download a new
6259 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
6260 other large files. I look forward to hearing from my supplier with
6261 the next proposal from Lenovo.&lt;/p&gt;
6262
6263 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
6264 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6265 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6266 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
6267 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6268 P/N 45N8295, P0C38732.&lt;/p&gt;
6269
6270 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
6271 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
6272 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6273 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
6274 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6275 P/N 45N8295, P0C38732.&lt;/p&gt;
6276
6277 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
6278 SA, date and WNPP values. Mentioning all the details here in case
6279 someone is able to use the information to find a way to identify the
6280 failing disk among working ones (if any such working disk actually
6281 exist).&lt;/p&gt;
6282 </description>
6283 </item>
6284
6285 <item>
6286 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
6287 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
6288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
6289 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
6290 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
6291 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6292 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
6293 member assosiation NUUG&lt;/a&gt; and
6294 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
6295 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
6296 Bitraf&lt;/a&gt;.&lt;/p&gt;
6297
6298 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
6299 welcome, and there is no fee to participate. There is on the other
6300 hand limited space, and only room for 30 people. Please put your name
6301 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
6302 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
6303 </description>
6304 </item>
6305
6306 <item>
6307 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
6308 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
6309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
6310 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
6311 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
6312 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
6313 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
6314 time to spend on it, and it took a while to find a model I believe
6315 will do the job, but two days ago the replacement finally arrived. I
6316 ended up picking a
6317 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
6318 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6319 a roaming workstation, and it seemed to work flawlessly. But my
6320 second installation with encrypted disk was not as successful. More
6321 on that below.&lt;/p&gt;
6322
6323 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6324 important requirements (robust and with a good keyboard) are never
6325 listed in the feature list. But I did get good help from the search
6326 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6327 allowed me to limit the list of interesting laptops based on my other
6328 requirements. A bit surprising that SSD disk are not disks according
6329 to that search interface, so I had to drop specifying the number of
6330 disks from my search parameters. I also asked around among friends to
6331 get their impression on keyboards and robustness.&lt;/p&gt;
6332
6333 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
6334 X41. I am not quite convinced about the keyboard, as it is
6335 significantly wider than my old keyboard, and I have to stretch my
6336 hand a lot more to reach the edges. But the key response is fairly
6337 good and the individual key shape is fairly easy to handle, so I hope
6338 I will get used to it. My old X40 was starting to fail, and I really
6339 needed a new laptop now. :)&lt;/p&gt;
6340
6341 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6342 visit to the BIOS during boot it disable it.&lt;/p&gt;
6343
6344 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6345 lock up during load. And this happen when installing Debian Wheezy
6346 with encrypted disk, while the disk is being filled with random data.
6347 I also tested to install Ubuntu Raring, and it happen there too if I
6348 reenable the code to fill the disk with random data (it is disabled by
6349 default in Ubuntu). And the bug with is already known. It was
6350 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6351 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6352 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6353 kernel developers as
6354 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6355 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6356 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6357 Lenovo forums, both for
6358 &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
6359 2012-11-10&lt;/a&gt; and for
6360 &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
6361 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6362 reports state that the disk lock up during use if many writes are done
6363 on the disk, so it is much no use to work around the installation
6364 problem and end up with a computer that can lock up at any moment.
6365 There is even a
6366 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6367 available&lt;/a&gt; that will lock up the hard drive after running a few
6368 minutes by writing to a file.&lt;/p&gt;
6369
6370 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6371 contacting PCHELP Norway (request 01D1FDP) which handle support
6372 requests for Lenovo, his first suggestion was to upgrade the disk
6373 firmware. Unfortunately there is no newer firmware available from
6374 Lenovo, as my disk already have the most recent one (version LF1i). I
6375 hope to hear more from him today and hope the problem can be
6376 fixed. :)&lt;/p&gt;
6377 </description>
6378 </item>
6379
6380 <item>
6381 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6382 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6383 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6384 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6385 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6386 trusty old Thinkpad X41. Unfortunately I did not have much time to
6387 spend on it, but today the replacement finally arrived. I ended up
6388 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6389 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6390 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6391 this, it is installing what I hope will be a more final installation,
6392 with a encrypted hard drive to ensure any dope head stealing it end up
6393 with an expencive door stop.&lt;/p&gt;
6394
6395 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6396 important requirements (robust and with a good keyboard) are never
6397 listed in the feature list. But I did get good help from the search
6398 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6399 allowed me to limit the list of interesting laptops based on my other
6400 requirements. A bit surprising that SSD disk are not disks, so I had
6401 to drop number of disks from my search parameters.&lt;/p&gt;
6402
6403 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6404 wider than my old keyboard, and I have to stretch my hand a lot more
6405 to reach the edges. But the key response is fairly good and the
6406 individual key shape is fairly easy to handle, so I hope I will get
6407 used to it. My old X40 was starting to fail, and I really needed a
6408 new laptop now. :)&lt;/p&gt;
6409
6410 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6411 </description>
6412 </item>
6413
6414 <item>
6415 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6416 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6417 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6418 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6419 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6420 perfectly capable of, and I have to do it manually to get things
6421 working. One such task is to find out what firmware packages are
6422 needed to get the hardware on my computer working. Most often this
6423 affect the wifi card, but some times it even affect the RAID
6424 controller or the ethernet card. Today I pushed version 0.4 of the
6425 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6426 including a new script isenkram-autoinstall-firmware handling the
6427 process of asking all the loaded kernel modules what firmware files
6428 they want, find debian packages providing these files and install the
6429 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6430
6431 &lt;p&gt;&lt;pre&gt;
6432 # isenkram-autoinstall-firmware
6433 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6434 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6435 info: locating packages with the requested firmware files
6436 info: Updating APT sources after adding non-free APT source
6437 info: trying to install firmware-ipw2x00
6438 firmware-ipw2x00
6439 firmware-ipw2x00
6440 Preconfiguring packages ...
6441 Selecting previously deselected package firmware-ipw2x00.
6442 (Reading database ... 259727 files and directories currently installed.)
6443 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6444 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6445 #
6446 &lt;/pre&gt;&lt;/p&gt;
6447
6448 &lt;p&gt;When all the requested firmware is present, a simple message is
6449 printed instead:&lt;/p&gt;
6450
6451 &lt;p&gt;&lt;pre&gt;
6452 # isenkram-autoinstall-firmware
6453 info: did not find any firmware files requested by loaded kernel modules. exiting
6454 #
6455 &lt;/pre&gt;&lt;/p&gt;
6456
6457 &lt;p&gt;It could use some polish, but it is already working well and saving
6458 me some time when setting up new machines. :)&lt;/p&gt;
6459
6460 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6461 kernel modules, and look up each one of them using modinfo, to find
6462 the firmware files listed in the module meta-information. Next, it
6463 download the Contents file from a nearby APT mirror, and search for
6464 the firmware files in this file to locate the package with the
6465 requested firmware file. If the package is in the non-free section, a
6466 non-free APT source is added and the package is installed using
6467 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6468 machine.&lt;/p&gt;
6469
6470 &lt;p&gt;I hope someone find time to implement a more polished version of
6471 this script as part of the hw-detect debian-installer module, to
6472 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6473 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6474 firmware during a PXE install when the packages already are available
6475 from the nearby Debian mirror.&lt;/p&gt;
6476 </description>
6477 </item>
6478
6479 <item>
6480 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6481 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6482 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6483 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6484 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6485 the screen just turn black when Linux boot, either during installation
6486 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6487 last few years, but only recently understood the cause. I&#39;ve seen it
6488 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6489 The reason seem to be in the wiring of some laptops. The system to
6490 control the screen background light is inverted, so when Linux try to
6491 turn the brightness fully on, it end up turning it off instead. I do
6492 not know which Linux drivers are affected, but this post is about the
6493 i915 driver used by the
6494 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6495 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6496
6497 &lt;p&gt;The problem can be worked around two ways. Either by adding
6498 i915.invert_brightness=1 as a kernel option, or by adding a file in
6499 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6500 option when it load the i915 kernel module. On Debian and Ubuntu, it
6501 can be done by running these commands as root:&lt;/p&gt;
6502
6503 &lt;pre&gt;
6504 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6505 update-initramfs -u -k all
6506 &lt;/pre&gt;
6507
6508 &lt;p&gt;Since March 2012 there is
6509 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6510 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6511 hardware have this problem, and get the driver to invert the
6512 brightness setting automatically. To use it, one need to add a row in
6513 &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
6514 intel_quirks array&lt;/a&gt; in the driver source
6515 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6516 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6517 number (vendor number 8086 is assumed) and subdevice vendor and device
6518 number.&lt;/p&gt;
6519
6520 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6521 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6522
6523 &lt;p&gt;&lt;pre&gt;
6524 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6525 3rd Gen Core processor Graphics Controller [8086:0156] \
6526 (rev 09) (prog-if 00 [VGA controller])
6527 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6528 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6529 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6530 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6531 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6532 Latency: 0
6533 Interrupt: pin A routed to IRQ 42
6534 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6535 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6536 Region 4: I/O ports at 4000 [size=64]
6537 Expansion ROM at &lt;unassigned&gt; [disabled]
6538 Capabilities: &lt;access denied&gt;
6539 Kernel driver in use: i915
6540 &lt;/pre&gt;&lt;/p&gt;
6541
6542 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6543
6544 &lt;p&gt;&lt;pre&gt;
6545 struct intel_quirk intel_quirks[] = {
6546 ...
6547 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6548 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6549 ...
6550 }
6551 &lt;/pre&gt;&lt;/p&gt;
6552
6553 &lt;p&gt;According to the kernel module instructions (as seen using
6554 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6555 invert_brightness flag should be sent to the
6556 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6557 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6558 developers. But my email about the laptop sent 2013-06-03 have not
6559 yet shown up in
6560 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6561 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6562 emails from non-subscribers. Because of this, I sent my patch also to
6563 the Debian bug tracking system instead as
6564 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6565 sure the patch is not lost.&lt;/p&gt;
6566
6567 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6568 with this problem working properly with Linux. If you use Gnome, your
6569 worries should be over at this point. But if you use KDE, there is
6570 something in KDE ignoring the invert_brightness setting and turning on
6571 the screen during login. I&#39;ve reported it to Debian as
6572 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6573 have no idea yet how to figure out exactly what subsystem is doing
6574 this. Perhaps you can help? Perhaps you know what the Gnome
6575 developers did to handle this, and this can give a clue to the KDE
6576 developers? Or you know where in KDE the screen brightness is changed
6577 during login? If so, please update the BTS report (or get in touch if
6578 you do not know how to update BTS).&lt;/p&gt;
6579
6580 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6581 acpi_backlight=vendor, to disable ACPI backlight support completely,
6582 as the ACPI information on the machine is trash and it is better to
6583 leave it to the intel video driver to control the screen
6584 backlight.&lt;/p&gt;
6585 </description>
6586 </item>
6587
6588 <item>
6589 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6590 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6591 <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>
6592 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6593 <description>&lt;p&gt;Two days ago, I asked
6594 &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
6595 I could install Linux on a Packard Bell EasyNote LV computer
6596 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6597 with the obstacles put in the way of Linux users on a laptop with UEFI
6598 and Windows 8.&lt;/p&gt;
6599
6600 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6601 secure booting or fast boot. I suspect fast boot was the problem,
6602 causing the firmware to boot directly from HD without considering any
6603 key presses and alternative devices, but do not know UEFI settings
6604 enough to tell.&lt;/p&gt;
6605
6606 &lt;p&gt;There is no way to install Linux on the machine in question without
6607 opening the box and disconnecting the hard drive! This is as far as I
6608 can tell, the only way to get access to the firmware setup menu
6609 without accepting the Windows 8 license agreement. I am told (and
6610 found description on how to) that it is possible to configure the
6611 firmware setup once booted into Windows 8. But as I believe the terms
6612 of that agreement are completely unacceptable, accepting the license
6613 was never an alternative. I do not enter agreements I do not intend
6614 to follow.&lt;/p&gt;
6615
6616 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6617 waste many hours on this, but luckily there was a way to get it to
6618 work. But I would not recommend it to anyone planning to run Linux on
6619 it, and I have become sceptical to Windows 8 certified laptops. Is
6620 this the way Linux will be forced out of the market place, by making
6621 it close to impossible for &quot;normal&quot; users to install Linux without
6622 accepting the Microsoft Windows license terms? Or at least not
6623 without risking to loose the warranty?&lt;/p&gt;
6624
6625 &lt;p&gt;I&#39;ve updated the
6626 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6627 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6628 do not have to struggle as much as I did to get Linux into the
6629 machine.&lt;/p&gt;
6630
6631 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6632 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6633 </description>
6634 </item>
6635
6636 <item>
6637 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6638 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6639 <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>
6640 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6641 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6642 new laptops for my parents and a few others. I bought Packard Bell
6643 Easynote LV to run Kubuntu on and use as their home computer. But I
6644 am completely unable to figure out how to install Linux on it. The
6645 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6646 instead of a BIOS to boot.&lt;/p&gt;
6647
6648 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6649 to get it to boot the Linux installer from my USB stick. I have yet
6650 to try the DVD install, and still hope it will work. when I turn on
6651 the computer, there is no information on what buttons to press to get
6652 the normal boot menu. I expect to get some boot menu to select PXE or
6653 USB stick booting. When booting, it first ask for the language to
6654 use, then for some regional settings, and finally if I will accept the
6655 Windows 8 terms of use. As these terms are completely unacceptable to
6656 me, I have no other choice but to turn off the computer and try again
6657 to get it to boot the Linux installer.&lt;/p&gt;
6658
6659 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6660 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6661 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6662 installed on this machine, please get in touch or update that wiki
6663 page. If I can&#39;t find a way to install Linux, I will have to return
6664 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6665
6666 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6667 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6668 on new Laptops?&lt;/p&gt;
6669 </description>
6670 </item>
6671
6672 <item>
6673 <title>How to transform a Debian based system to a Debian Edu installation</title>
6674 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6675 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6676 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6677 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6678 an operating system based on Debian intended for use in schools. It
6679 contain a turn-key solution for the computer network provided to
6680 pupils in the primary schools. It provide both the central server,
6681 network boot servers and desktop environments with heaps of
6682 educational software. The project was founded almost 12 years ago,
6683 2001-07-02. If you want to support the project, which is in need for
6684 cash to fund developer gatherings and other project related activity,
6685 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6686 donate some money&lt;/a&gt;.
6687
6688 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6689 lists and elsewhere, is the question on how to transform a Debian or
6690 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6691 hard, and last week I wrote a script to replicate the steps done by
6692 the Debian Edu installer.&lt;/p&gt;
6693
6694 &lt;p&gt;The script,
6695 &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;
6696 in the debian-edu-config package, will go through these six steps and
6697 transform an existing Debian Wheezy or Ubuntu (untested) installation
6698 into a Debian Edu Workstation:&lt;/p&gt;
6699
6700 &lt;ol&gt;
6701
6702 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6703 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6704 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6705 our configuration.&lt;/li&gt;
6706 &lt;li&gt;Preseed debconf database with profile setup in
6707 /etc/debian-edu/config, and run tasksel to install packages
6708 according to the profile specified in the config above,
6709 overriding some of the Debian automation machinery.&lt;/li&gt;
6710 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6711 that could not be done using preseeding.&lt;/li&gt;
6712 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6713
6714 &lt;/ol&gt;
6715
6716 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6717 replicated like this. Disk partitioning and LVM setup, for example.
6718 So this script just assume there is enough disk space to install all
6719 the needed packages.&lt;/p&gt;
6720
6721 &lt;p&gt;The script was created to help a Debian Edu student working on
6722 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6723 Debian Edu client, and using it he can take the existing
6724 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6725 transform it into a fully functioning Debian Edu Workstation (or
6726 Roaming Workstation, or whatever :).&lt;/p&gt;
6727
6728 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6729 If a LXDE based Roaming workstation is wanted instead, modify the
6730 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6731
6732 &lt;p&gt;&lt;pre&gt;
6733 PROFILE=&quot;Roaming-Workstation&quot;
6734 DESKTOP=&quot;lxde&quot;
6735 &lt;/pre&gt;&lt;/p&gt;
6736
6737 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6738 the cloud, by starting with a virtual Debian installation at some
6739 virtual hosting service and setting up all the services on first
6740 boot.&lt;/p&gt;
6741 </description>
6742 </item>
6743
6744 <item>
6745 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6746 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6748 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6749 <description>&lt;P&gt;In January,
6750 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6751 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6752 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6753 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6754 marvellous construction system from Denmark. We also created
6755 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6756 a place to take notes and write down our plans and hopes. And several
6757 people showed up to help. I was very happy to see the effect of my
6758 call. Since the small start, we have a debtags tag
6759 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6760 tag for LEGO related packages, and now count 10 packages related to
6761 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6762
6763 &lt;p&gt;&lt;table&gt;
6764 &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;
6765 &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;
6766 &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;
6767 &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;
6768 &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;
6769 &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;
6770 &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;
6771 &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;
6772 &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;
6773 &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;
6774 &lt;/table&gt;&lt;/p&gt;
6775
6776 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6777 currently available in Jessie/testing. leocad is so far only
6778 available in experimental.&lt;/p&gt;
6779
6780 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6781 adding the rest of the great free software tools available on Linux
6782 for LEGO designers.&lt;/p&gt;
6783 </description>
6784 </item>
6785
6786 <item>
6787 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6788 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6789 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6790 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6791 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6792 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6793 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6794 Debian release, and I expect to move my machines at home over to it fairly
6795 soon.&lt;/p&gt;
6796
6797 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6798 in particular make me very happy to see included. The
6799 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6800 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6801 included for the first time. Alongside similar programs like
6802 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6803 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6804 it allow for visual programming where syntax errors can not happen,
6805 and a friendly programming environment for learning to control the
6806 computer. Scratch will also be included in the next release of Debian
6807 Edu.&lt;/a&gt;
6808
6809 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6810 Edu/Skolelinux release too. The
6811 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6812 alpha release&lt;/a&gt; went out last week, and the next should soon
6813 follow.&lt;p&gt;
6814 </description>
6815 </item>
6816
6817 <item>
6818 <title>Isenkram 0.2 finally in the Debian archive</title>
6819 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6820 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6821 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6822 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6823 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6824 for many months. I uploaded it to the Debian experimental suite
6825 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6826
6827 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6828 install to work with a pluggable hardware device. The suggestion pop
6829 up when the device is plugged in. For example if a Lego Mindstorm NXT
6830 is inserted, it will suggest to install the program needed to program
6831 the NXT controller. Give it a go, and report bugs and suggestions to
6832 BTS. :)&lt;/p&gt;
6833 </description>
6834 </item>
6835
6836 <item>
6837 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
6838 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
6839 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
6840 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
6841 <description>&lt;p&gt;My
6842 &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
6843 bitcoin related blog post&lt;/a&gt; mentioned that the new
6844 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
6845 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6846 2013-01-19, and have been available in unstable since then. It was
6847 automatically copied to Ubuntu, and is available in their Raring
6848 version too.&lt;/p&gt;
6849
6850 &lt;p&gt;But there is a strange problem with the build that block this new
6851 version from being available on the i386 and kfreebsd-i386
6852 architectures. For some strange reason, the autobuilders in Debian
6853 for these architectures fail to run the test suite on these
6854 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
6855 We are so far unable to reproduce it when building it manually, and
6856 no-one have been able to propose a fix. If you got an idea what is
6857 failing, please let us know via the BTS.&lt;/p&gt;
6858
6859 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
6860 I often run low on disk space, is the fact that the client will exit
6861 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
6862 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
6863 it. :)&lt;/p&gt;
6864
6865 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6866 activities, please send Bitcoin donations to my address
6867 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6868 </description>
6869 </item>
6870
6871 <item>
6872 <title>Welcome to the world, Isenkram!</title>
6873 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
6874 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
6875 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
6876 <description>&lt;p&gt;Yesterday, I
6877 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
6878 for testers&lt;/a&gt; for my prototype for making Debian better at handling
6879 pluggable hardware devices, which I
6880 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
6881 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
6882 up, and caused me to really want to to open up the development to more
6883 people. But before I did this, I want to come up with a sensible name
6884 for this project. Today I finally decided on a new name, and I have
6885 renamed the project from hw-support-handler to this new name. In the
6886 process, I moved the source to git and made it available as a
6887 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
6888 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
6889 To fetch and build the latest version of the source, use&lt;/p&gt;
6890
6891 &lt;pre&gt;
6892 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6893 cd isenkram &amp;&amp; git-buildpackage -us -uc
6894 &lt;/pre&gt;
6895
6896 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
6897 want to hack on the source or improve the package, please go ahead.
6898 But please talk to me first on IRC or via email before you do major
6899 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
6900
6901 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
6902 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6903 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
6904 the German word eisenkram, for those that are familiar with that
6905 word.&lt;/p&gt;
6906
6907 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
6908 instructions, to avoid confusing people with an error from the signing
6909 process.&lt;/p&gt;
6910
6911 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
6912 clone argument to avoid the need for authentication.&lt;/p&gt;
6913 </description>
6914 </item>
6915
6916 <item>
6917 <title>First prototype ready making hardware easier to use in Debian</title>
6918 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
6919 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
6920 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
6921 <description>&lt;p&gt;Early this month I set out to try to
6922 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
6923 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
6924 prototype is working, and it is ready for a larger audience. To test
6925 it, fetch the
6926 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
6927 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
6928 package. You might have to log out and in again activate the
6929 autostart script.&lt;/p&gt;
6930
6931 &lt;p&gt;The design is simple:&lt;/p&gt;
6932
6933 &lt;ul&gt;
6934
6935 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
6936 hw-support-handlerd to start when the user log in.&lt;/li&gt;
6937
6938 &lt;li&gt;This program listen for kernel events about new hardware (directly
6939 from the kernel like udev does), not using HAL dbus events as I
6940 initially did.&lt;/li&gt;
6941
6942 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
6943 the APT database, a database
6944 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
6945 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
6946
6947 &lt;li&gt;If a package is mapped to the hardware in question, the package
6948 isn&#39;t installed yet and this is the first time the hardware was
6949 plugged in, show a desktop notification suggesting to install the
6950 package or packages.&lt;/li&gt;
6951
6952 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
6953 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
6954
6955 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
6956 package while showing progress information in a window.&lt;/li&gt;
6957
6958 &lt;/ul&gt;
6959
6960 &lt;p&gt;I still need to come up with a better name for the system. Here
6961 are some screen shots showing the prototype in action. First the
6962 notification, then the password request, and finally the request to
6963 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
6964
6965 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
6966 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
6967 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
6968 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
6969 &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;
6970
6971 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
6972 is already useful. The database of hardware to package mappings also
6973 need more work. It is currently compatible with the Ubuntu way of
6974 storing such information in the package control file, but could be
6975 changed to use other formats instead or in addition to the current
6976 method. I&#39;ve dropped the use of discover for this mapping, as the
6977 modalias approach is more flexible and easier to use on Linux as long
6978 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
6979
6980 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
6981 here is the command required to check out and build the source: Use
6982 &#39;&lt;tt&gt;svn checkout
6983 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6984 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
6985 devscripts package.&lt;/p&gt;
6986
6987 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
6988 renamed to Isenkram and the source moved from the Debian Edu
6989 subversion repository to a Debian collab-maint git repository. See
6990 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
6991 instructions&lt;/a&gt; for details.&lt;/p&gt;
6992 </description>
6993 </item>
6994
6995 <item>
6996 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
6997 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
6998 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
6999 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
7000 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
7001 suddenly in bed. With a quiet whimper, it went completely quiet and
7002 black. The power button was no longer able to turn it on. It was a
7003 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7004 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7005 Compaq I had before that. Now I need to find a replacement. To keep
7006 going during Christmas, I moved the one year old SSD disk to my old
7007 X40 where it fitted (only one I had left that could use it), but it is
7008 not a durable solution.
7009
7010 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
7011 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
7012
7013 &lt;ul&gt;
7014
7015 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
7016 than A4).&lt;/li&gt;
7017 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
7018 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
7019 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
7020 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
7021 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
7022 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
7023 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
7024 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
7025 size).&lt;/li&gt;
7026 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
7027 X.org packages.&lt;/li&gt;
7028 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
7029 the time).
7030
7031 &lt;/ul&gt;
7032
7033 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
7034 list. The reason is simply that the specifications on laptops the
7035 last 10-15 years have been sufficient for my needs, and I have to look
7036 at other features to choose my laptop. But are there still made as
7037 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7038 robust, and Thinkpads seem to be heading in the wrong direction since
7039 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
7040 still be useful.&lt;/p&gt;
7041
7042 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
7043 external keyboard? I&#39;ll have to check the
7044 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
7045 well-supported laptops, or perhaps just buy one preinstalled from one
7046 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
7047 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
7048 </description>
7049 </item>
7050
7051 <item>
7052 <title>How to find a browser plugin supporting a given MIME type</title>
7053 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
7054 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
7055 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
7056 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
7057 install to get support for a given MIME type. Thanks to
7058 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
7059 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
7060 Unfortunately, not very many packages provide the needed meta
7061 information, Anyway, here is a small script to look up all browser
7062 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
7063
7064 &lt;pre&gt;
7065 #!/usr/bin/python
7066 import sys
7067 import apt
7068 def pkgs_handling_mimetype(mimetype):
7069 cache = apt.Cache()
7070 cache.open(None)
7071 thepkgs = []
7072 for pkg in cache:
7073 version = pkg.candidate
7074 if version is None:
7075 version = pkg.installed
7076 if version is None:
7077 continue
7078 record = version.record
7079 if not record.has_key(&#39;Npp-MimeType&#39;):
7080 continue
7081 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
7082 for t in mime_types:
7083 t = t.rstrip().strip()
7084 if t == mimetype:
7085 thepkgs.append(pkg.name)
7086 return thepkgs
7087 mimetype = &quot;audio/ogg&quot;
7088 if 1 &lt; len(sys.argv):
7089 mimetype = sys.argv[1]
7090 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
7091 for pkg in pkgs_handling_mimetype(mimetype):
7092 print &quot; %s&quot; %pkg
7093 &lt;/pre&gt;
7094
7095 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
7096
7097 &lt;pre&gt;
7098 % ./apt-find-browserplug-for-mimetype
7099 Browser plugin packages supporting audio/ogg:
7100 gecko-mediaplayer
7101 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7102 Browser plugin packages supporting application/x-shockwave-flash:
7103 browser-plugin-gnash
7104 %
7105 &lt;/pre&gt;
7106
7107 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
7108 itself to query for plugins and propose to install the needed
7109 packages. It would be great if Debian supported such feature too. Is
7110 anyone working on adding it?&lt;/p&gt;
7111
7112 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
7113 request for icweasel support for this feature is
7114 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
7115 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
7116 of manpower and wish for a different design is the reason thus feature
7117 is not yet in iceweasel from Debian.&lt;/p&gt;
7118 </description>
7119 </item>
7120
7121 <item>
7122 <title>What is the most supported MIME type in Debian?</title>
7123 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
7124 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
7125 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
7126 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
7127 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
7128 proposal to make it possible for a Desktop application to propose to
7129 the user some package to install to gain support for a given MIME
7130 type, font, library etc. that is currently missing. With such
7131 mechanism in place, it would be possible for the desktop to
7132 automatically propose and install leocad if some LDraw file is
7133 downloaded by the browser.&lt;/p&gt;
7134
7135 &lt;p&gt;To get some idea about the current content of the archive, I decided
7136 to write a simple program to extract all .desktop files from the
7137 Debian archive and look up the claimed MIME support there. The result
7138 can be found on the
7139 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
7140 site&lt;/a&gt;. Using the collected information, it become possible to
7141 answer the question in the title. Here are the 20 most supported MIME
7142 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7143 The complete list is available from the link above.&lt;/p&gt;
7144
7145 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
7146
7147 &lt;pre&gt;
7148 count MIME type
7149 ----- -----------------------
7150 32 text/plain
7151 30 audio/mpeg
7152 29 image/png
7153 28 image/jpeg
7154 27 application/ogg
7155 26 audio/x-mp3
7156 25 image/tiff
7157 25 image/gif
7158 22 image/bmp
7159 22 audio/x-wav
7160 20 audio/x-flac
7161 19 audio/x-mpegurl
7162 18 video/x-ms-asf
7163 18 audio/x-musepack
7164 18 audio/x-mpeg
7165 18 application/x-ogg
7166 17 video/mpeg
7167 17 audio/x-scpls
7168 17 audio/ogg
7169 16 video/x-ms-wmv
7170 &lt;/pre&gt;
7171
7172 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
7173
7174 &lt;pre&gt;
7175 count MIME type
7176 ----- -----------------------
7177 33 text/plain
7178 32 image/png
7179 32 image/jpeg
7180 29 audio/mpeg
7181 27 image/gif
7182 26 image/tiff
7183 26 application/ogg
7184 25 audio/x-mp3
7185 22 image/bmp
7186 21 audio/x-wav
7187 19 audio/x-mpegurl
7188 19 audio/x-mpeg
7189 18 video/mpeg
7190 18 audio/x-scpls
7191 18 audio/x-flac
7192 18 application/x-ogg
7193 17 video/x-ms-asf
7194 17 text/html
7195 17 audio/x-musepack
7196 16 image/x-xbitmap
7197 &lt;/pre&gt;
7198
7199 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
7200
7201 &lt;pre&gt;
7202 count MIME type
7203 ----- -----------------------
7204 31 text/plain
7205 31 image/png
7206 31 image/jpeg
7207 29 audio/mpeg
7208 28 application/ogg
7209 27 image/gif
7210 26 image/tiff
7211 26 audio/x-mp3
7212 23 audio/x-wav
7213 22 image/bmp
7214 21 audio/x-flac
7215 20 audio/x-mpegurl
7216 19 audio/x-mpeg
7217 18 video/x-ms-asf
7218 18 video/mpeg
7219 18 audio/x-scpls
7220 18 application/x-ogg
7221 17 audio/x-musepack
7222 16 video/x-ms-wmv
7223 16 video/x-msvideo
7224 &lt;/pre&gt;
7225
7226 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
7227 information mentioned in DEP-11. I have not yet had time to look at
7228 it, but hope the PackageKit people in Debian are on top of these
7229 issues.&lt;/p&gt;
7230
7231 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
7232 discovering a typo in my script.&lt;/p&gt;
7233 </description>
7234 </item>
7235
7236 <item>
7237 <title>Using modalias info to find packages handling my hardware</title>
7238 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
7239 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
7240 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
7241 <description>&lt;p&gt;Yesterday, I wrote about the
7242 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
7243 values provided by the Linux kernel&lt;/a&gt; following my hope for
7244 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
7245 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
7246 modalias values attached to package names can be used to map packages
7247 to hardware. This allow the system to look up and suggest relevant
7248 packages when I plug in some new hardware into my machine, and replace
7249 discover and discover-data as the database used to map hardware to
7250 packages.&lt;/p&gt;
7251
7252 &lt;p&gt;I create a modaliases file with entries like the following,
7253 containing package name, kernel module name (if relevant, otherwise
7254 the package name) and globs matching the relevant hardware
7255 modalias.&lt;/p&gt;
7256
7257 &lt;p&gt;&lt;blockquote&gt;
7258 Package: package-name
7259 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
7260 &lt;/blockquote&gt;&lt;/p&gt;
7261
7262 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
7263 for a given modalias value using this file.&lt;/p&gt;
7264
7265 &lt;p&gt;An entry like this would suggest the video and picture application
7266 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
7267
7268 &lt;p&gt;&lt;blockquote&gt;
7269 Package: cheese
7270 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
7271 &lt;/blockquote&gt;&lt;/p&gt;
7272
7273 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
7274 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
7275
7276 &lt;p&gt;&lt;blockquote&gt;
7277 Package: pcmciautils
7278 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7279 &lt;/blockquote&gt;&lt;/p&gt;
7280
7281 &lt;p&gt;An entry like this would suggest the package colorhug-client when
7282 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
7283
7284 &lt;p&gt;&lt;blockquote&gt;
7285 Package: colorhug-client
7286 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
7287 &lt;/blockquote&gt;&lt;/p&gt;
7288
7289 &lt;p&gt;I believe the format is compatible with the format of the Packages
7290 file in the Debian archive. Ubuntu already uses their Packages file
7291 to store their mappings from packages to hardware.&lt;/p&gt;
7292
7293 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
7294 announce the hardware it support in a way my prototype understand.
7295 This allow those publishing packages in an APT source outside the
7296 Debian archive as well as those backporting packages to make sure the
7297 hardware mapping are included in the package meta information. I&#39;ve
7298 tested such header in the pymissile package, and its modalias mapping
7299 is working as it should with my prototype. It even made it to Ubuntu
7300 Raring.&lt;/p&gt;
7301
7302 &lt;p&gt;To test if it was possible to look up supported hardware using only
7303 the shell tools available in the Debian installer, I wrote a shell
7304 implementation of the lookup code. The idea is to create files for
7305 each modalias and let the shell do the matching. Please check out and
7306 try the
7307 &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;
7308 shell script. It run without any extra dependencies and fetch the
7309 hardware mappings from the Debian archive and the subversion
7310 repository where I currently work on my prototype.&lt;/p&gt;
7311
7312 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
7313 install yubikey-personalization:&lt;/p&gt;
7314
7315 &lt;p&gt;&lt;blockquote&gt;
7316 % ./hw-support-lookup
7317 &lt;br&gt;yubikey-personalization
7318 &lt;br&gt;%
7319 &lt;/blockquote&gt;&lt;/p&gt;
7320
7321 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7322 propose to install the pcmciautils package:&lt;/p&gt;
7323
7324 &lt;p&gt;&lt;blockquote&gt;
7325 % ./hw-support-lookup
7326 &lt;br&gt;pcmciautils
7327 &lt;br&gt;%
7328 &lt;/blockquote&gt;&lt;/p&gt;
7329
7330 &lt;p&gt;If you know of any hardware-package mapping that should be added to
7331 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
7332 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
7333
7334 &lt;p&gt;It could be possible to generate several of the mappings between
7335 packages and hardware. One source would be to look at packages with
7336 kernel modules, ie packages with *.ko files in /lib/modules/, and
7337 extract their modalias information. Another would be to look at
7338 packages with udev rules, ie packages with files in
7339 /lib/udev/rules.d/, and extract their vendor/model information to
7340 generate a modalias matching rule. I have not tested any of these to
7341 see if it work.&lt;/p&gt;
7342
7343 &lt;p&gt;If you want to help implementing a system to let us propose what
7344 packages to install when new hardware is plugged into a Debian
7345 machine, please send me an email or talk to me on
7346 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7347 </description>
7348 </item>
7349
7350 <item>
7351 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7352 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7354 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7355 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7356 information, to find the packages that support a given piece of
7357 hardware, I refreshed my memory regarding modalias values, and decided
7358 to document the details. Here are my findings so far, also available
7359 in
7360 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7361 Debian Edu subversion repository&lt;/a&gt;:
7362
7363 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7364
7365 &lt;p&gt;This document try to explain what the different types of modalias
7366 values stands for. It is in part based on information from
7367 &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;,
7368 &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;,
7369 &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
7370 &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;.
7371
7372 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7373 this shell script:&lt;/p&gt;
7374
7375 &lt;pre&gt;
7376 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7377 &lt;/pre&gt;
7378
7379 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7380 using modinfo:&lt;/p&gt;
7381
7382 &lt;pre&gt;
7383 % /sbin/modinfo psmouse | grep alias:
7384 alias: serio:ty05pr*id*ex*
7385 alias: serio:ty01pr*id*ex*
7386 %
7387 &lt;/pre&gt;
7388
7389 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7390
7391 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7392 Bridge memory controller:&lt;/p&gt;
7393
7394 &lt;p&gt;&lt;blockquote&gt;
7395 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7396 &lt;/blockquote&gt;&lt;/p&gt;
7397
7398 &lt;p&gt;This represent these values:&lt;/p&gt;
7399
7400 &lt;pre&gt;
7401 v 00008086 (vendor)
7402 d 00002770 (device)
7403 sv 00001028 (subvendor)
7404 sd 000001AD (subdevice)
7405 bc 06 (bus class)
7406 sc 00 (bus subclass)
7407 i 00 (interface)
7408 &lt;/pre&gt;
7409
7410 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7411 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7412 0600. The 0600 class is a host bridge. Other useful bus values are
7413 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7414
7415 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7416 means.&lt;/p&gt;
7417
7418 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7419
7420 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7421 USB hub in a laptop:&lt;/p&gt;
7422
7423 &lt;p&gt;&lt;blockquote&gt;
7424 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7425 &lt;/blockquote&gt;&lt;/p&gt;
7426
7427 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7428
7429 &lt;pre&gt;
7430 v 1D6B (device vendor)
7431 p 0001 (device product)
7432 d 0206 (bcddevice)
7433 dc 09 (device class)
7434 dsc 00 (device subclass)
7435 dp 00 (device protocol)
7436 ic 09 (interface class)
7437 isc 00 (interface subclass)
7438 ip 00 (interface protocol)
7439 &lt;/pre&gt;
7440
7441 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7442 class is in the interface class section. For a simple USB web camera,
7443 these alias entries show up:&lt;/p&gt;
7444
7445 &lt;p&gt;&lt;blockquote&gt;
7446 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7447 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7448 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7449 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7450 &lt;/blockquote&gt;&lt;/p&gt;
7451
7452 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7453 camera), 0101 is audio control device and 0102 is audio streaming (aka
7454 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7455
7456 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7457
7458 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7459 receiver in a Thinkpad X40:&lt;/p&gt;
7460
7461 &lt;p&gt;&lt;blockquote&gt;
7462 acpi:IBM0071:PNP0511:
7463 &lt;/blockquote&gt;&lt;/p&gt;
7464
7465 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7466
7467 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7468
7469 &lt;p&gt;The DMI table contain lots of information about the computer case
7470 and model. This is an entry for a IBM Thinkpad X40, fetched from
7471 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7472
7473 &lt;p&gt;&lt;blockquote&gt;
7474 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
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 bvn IBM (BIOS vendor)
7481 bvr 1UETB6WW(1.66) (BIOS version)
7482 bd 06/15/2005 (BIOS date)
7483 svn IBM (system vendor)
7484 pn 2371H4G (product name)
7485 pvr ThinkPadX40 (product version)
7486 rvn IBM (board vendor)
7487 rn 2371H4G (board name)
7488 rvr NotAvailable (board version)
7489 cvn IBM (chassis vendor)
7490 ct 10 (chassis type)
7491 cvr NotAvailable (chassis version)
7492 &lt;/pre&gt;
7493
7494 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7495 found in the dmidecode source:&lt;/p&gt;
7496
7497 &lt;pre&gt;
7498 3 Desktop
7499 4 Low Profile Desktop
7500 5 Pizza Box
7501 6 Mini Tower
7502 7 Tower
7503 8 Portable
7504 9 Laptop
7505 10 Notebook
7506 11 Hand Held
7507 12 Docking Station
7508 13 All In One
7509 14 Sub Notebook
7510 15 Space-saving
7511 16 Lunch Box
7512 17 Main Server Chassis
7513 18 Expansion Chassis
7514 19 Sub Chassis
7515 20 Bus Expansion Chassis
7516 21 Peripheral Chassis
7517 22 RAID Chassis
7518 23 Rack Mount Chassis
7519 24 Sealed-case PC
7520 25 Multi-system
7521 26 CompactPCI
7522 27 AdvancedTCA
7523 28 Blade
7524 29 Blade Enclosing
7525 &lt;/pre&gt;
7526
7527 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7528 table. For example my home server is a tower, but the DMI modalias
7529 claim it is a desktop.&lt;/p&gt;
7530
7531 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7532
7533 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7534 test machine:&lt;/p&gt;
7535
7536 &lt;p&gt;&lt;blockquote&gt;
7537 serio:ty01pr00id00ex00
7538 &lt;/blockquote&gt;&lt;/p&gt;
7539
7540 &lt;p&gt;The values present are&lt;/p&gt;
7541
7542 &lt;pre&gt;
7543 ty 01 (type)
7544 pr 00 (prototype)
7545 id 00 (id)
7546 ex 00 (extra)
7547 &lt;/pre&gt;
7548
7549 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7550 the valid values are.&lt;/p&gt;
7551
7552 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7553
7554 &lt;p&gt;There are heaps of other modalias subtypes according to
7555 file2alias.c. There is the rest of the list from that source: amba,
7556 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7557 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7558 vmbus, x86cpu and zorro. I did not spend time documenting all of
7559 these, as they do not seem relevant for my intended use with mapping
7560 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7561
7562 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7563
7564 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7565 one can use the following shell script:&lt;/p&gt;
7566
7567 &lt;pre&gt;
7568 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7569 echo &quot;$id&quot; ; \
7570 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7571 done
7572 &lt;/pre&gt;
7573
7574 &lt;p&gt;The output can look like this (only the first few entries as the
7575 list is very long on my test machine):&lt;/p&gt;
7576
7577 &lt;pre&gt;
7578 acpi:ACPI0003:
7579 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7580 acpi:device:
7581 FATAL: Module acpi:device: not found.
7582 acpi:IBM0068:
7583 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7584 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7585 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7586 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7587 acpi:IBM0071:PNP0511:
7588 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7589 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7590 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7591 [...]
7592 &lt;/pre&gt;
7593
7594 &lt;p&gt;If you want to help implementing a system to let us propose what
7595 packages to install when new hardware is plugged into a Debian
7596 machine, please send me an email or talk to me on
7597 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7598
7599 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7600 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7601 in /sys/ with space in them.&lt;/p&gt;
7602 </description>
7603 </item>
7604
7605 <item>
7606 <title>Moved the pymissile Debian packaging to collab-maint</title>
7607 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7609 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7610 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7611 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7612 Launcher and updated the Debian package
7613 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7614 sure udev will fix the device permissions when it is plugged in. I
7615 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7616 hopefully make the package be proposed by jockey in Ubuntu when a user
7617 plug in his rocket launcher. In the process I moved the source to a
7618 git repository under collab-maint, to make it easier for any DD to
7619 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7620 is not very active, but the software still work for me even after five
7621 years of relative silence. The new git repository is not listed in
7622 the uploaded package yet, because I want to test the other changes a
7623 bit more before I upload the new version. If you want to check out
7624 the new version with a .desktop file included, visit the
7625 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7626 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7627 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7628 </description>
7629 </item>
7630
7631 <item>
7632 <title>Lets make hardware dongles easier to use in Debian</title>
7633 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7634 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7635 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7636 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7637 general, is that there is a great package management system with the
7638 ability to automatically install software packages by downloading them
7639 from the distribution mirrors, but no way to get it to automatically
7640 install the packages I need to use the hardware I plug into my
7641 machine. Even if the package to use it is easily available from the
7642 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7643 suggest to automatically install the python-nxt, nbc and t2n packages
7644 I need to talk to it. When I plug in a Yubikey, it could propose the
7645 yubikey-personalization package. The information required to do this
7646 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7647
7648 &lt;p&gt;Some years ago, I proposed to
7649 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7650 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7651 simple:
7652
7653 &lt;ul&gt;
7654
7655 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7656 starting when a user log in.&lt;/li&gt;
7657
7658 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7659 hardware is inserted into the computer.&lt;/li&gt;
7660
7661 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7662 database mapping to packages, and take note of any non-installed
7663 packages.&lt;/li&gt;
7664
7665 &lt;li&gt;Show a message to the user proposing to install the discovered
7666 package, and make it easy to install it.&lt;/li&gt;
7667
7668 &lt;/ul&gt;
7669
7670 &lt;p&gt;I am not sure what the best way to implement this is, but my
7671 initial idea was to use dbus events to discover new hardware, the
7672 discover database to find packages and
7673 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7674 packages.&lt;/p&gt;
7675
7676 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7677 draft package is now checked into
7678 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7679 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7680 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7681 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7682 the relevant packages in Debian, and uploaded a new version
7683 2.2013.01.09 to unstable. I also discovered that the current
7684 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7685 package in Debian no longer discovered any USB devices, because
7686 /proc/bus/usb/devices is no longer present. I ported it to use
7687 libusb as a fall back option to get it working. The fixed package
7688 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7689 because of the freeze).&lt;/p&gt;
7690
7691 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7692 desktop notification to show up (only once, the first time it is
7693 inserted):&lt;/p&gt;
7694
7695 &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;
7696
7697 &lt;p&gt;For this prototype to be really useful, some way to automatically
7698 install the proposed packages by pressing the &quot;Please install
7699 program(s)&quot; button should to be implemented.&lt;/p&gt;
7700
7701 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7702 happen, please help me update the discover-data database with mappings
7703 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7704 list the package you would like to have installed when a given
7705 hardware device is inserted into your computer, and report bugs using
7706 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7707 such mapping, please let me know.&lt;/p&gt;
7708
7709 &lt;p&gt;This prototype need more work, and there are several questions that
7710 should be considered before it is ready for production use. Is dbus
7711 the correct way to detect new hardware? At the moment I look for HAL
7712 dbus events on the system bus, because that is the events I could see
7713 on my Debian Squeeze KDE desktop. Are there better events to use?
7714 How should the user be notified? Is the desktop notification
7715 mechanism the best option, or should the background daemon raise a
7716 popup instead? How should packages be installed? When should they
7717 not be installed?&lt;/p&gt;
7718
7719 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7720 please send me an email. :)&lt;/p&gt;
7721 </description>
7722 </item>
7723
7724 <item>
7725 <title>New IRC channel for LEGO designers using Debian</title>
7726 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7728 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7729 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7730 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7731 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7732 discovered I had to build all the tools myself because none were
7733 already in Debian Squeeze. If Debian support for LEGO is something
7734 you care about, please join me on the IRC channel
7735 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7736 irc.debian.org). There is a lot that could be done to improve the
7737 Debian support for LEGO designers. For example both CAD software
7738 and Mindstorm compilers are missing. :)&lt;/p&gt;
7739
7740 &lt;p&gt;Update 2012-01-03: A
7741 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7742 including links to Lego related packages is now available.&lt;/p&gt;
7743 </description>
7744 </item>
7745
7746 <item>
7747 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7748 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7749 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7750 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7751 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7752 year! I hope next year will prove to be a good year.&lt;/p&gt;
7753
7754 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7755 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7756 between each other with minimal overhead, is a very interesting
7757 experiment. And as I wrote a few days ago, the bitcoin situation in
7758 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7759 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7760 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7761 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7762 for one of the ftpmasters to approve the new bitcoin-qt package
7763 name.&lt;/p&gt;
7764
7765 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7766 team in Debian, you can easily test the package in Debian Squeeze
7767 using the following steps to get a set of working packages:&lt;/p&gt;
7768
7769 &lt;blockquote&gt;&lt;pre&gt;
7770 git clone git://git.debian.org/git/collab-maint/bitcoin
7771 cd bitcoin
7772 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7773 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7774 &lt;/pre&gt;&lt;/blockquote&gt;
7775
7776 &lt;p&gt;You might have to install some build dependencies as well. The
7777 list of commands should give you two packages, bitcoind and
7778 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7779 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7780 around 5.6 GiB of data on my machine at the moment. Make sure your
7781 ~/.bitcoin/ directory have lots of spare room if you want to download
7782 all the blocks. The client will warn if the disk is getting full, so
7783 there is not really a problem if you got too little room, but you will
7784 not be able to get all the features out of the client.&lt;/p&gt;
7785
7786 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7787 activities, please send Bitcoin donations to my address
7788 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7789 </description>
7790 </item>
7791
7792 <item>
7793 <title>A word on bitcoin support in Debian</title>
7794 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7795 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7796 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7797 <description>&lt;p&gt;It has been a while since I wrote about
7798 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7799 peer-to-peer based crypto-currency, and the reason is simply that I
7800 have been busy elsewhere. But two days ago, I started looking at the
7801 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7802 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7803 is now maintained by a
7804 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7805 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7806 owe a huge thank you to all these team members. :)
7807 But I was sad to discover that the bitcoin client is missing in
7808 Wheezy. It is only available in Sid (and an outdated client from
7809 backports). The client had several RC bugs registered in BTS blocking
7810 it from entering testing. To try to help the team and improve the
7811 situation, I spent some time providing patches and triaging the bug
7812 reports. I also had a look at the bitcoin package available from Matt
7813 Corallo in a
7814 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7815 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7816 Debian package.&lt;/p&gt;
7817
7818 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7819 IRC, I pushed several patches into the collab-maint git repository to
7820 improve the package. It now contains fixes for the RC issues (not from
7821 me, but fixed by Scott Howard), build rules for a Qt GUI client
7822 package, konqueror support for the bitcoin: URI and bash completion
7823 setup. As I work on Debian Squeeze, I also created
7824 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7825 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7826 it and try to integrate it into the git repository before uploading a
7827 new version to unstable.
7828
7829 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7830 centralized control currently exercised in the monetary system. I
7831 find it completely unacceptable that the USA government is collecting
7832 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7833 that the major credit card companies can block legal money
7834 transactions to Wikileaks. But for bitcoin to succeed, more people
7835 need to use bitcoins, and more people need to accept bitcoins when
7836 they sell products and services. Improving the bitcoin support in
7837 Debian is a small step in the right direction, but not enough.
7838 Unfortunately the user experience when browsing the web and wanting to
7839 pay with bitcoin is still not very good. The bitcoin: URI is a step
7840 in the right direction, but need to work in most or every browser in
7841 use. Also the bitcoin-qt client is too heavy to fire up to do a
7842 quick transaction. I believe there are other clients available, but
7843 have not tested them.&lt;/p&gt;
7844
7845 &lt;p&gt;My
7846 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
7847 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
7848 I received 20.15 BTC so far on the address I provided in my blog two
7849 years ago, as can be
7850 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
7851 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
7852 donation. The blockexplorer service demonstrates quite well that
7853 bitcoin is not quite anonymous and untracked. :) I wonder if the
7854 number of users have gone up since then. If you use bitcoin and want
7855 to show your support of my activity, please send Bitcoin donations to
7856 the same address as last time,
7857 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7858 </description>
7859 </item>
7860
7861 <item>
7862 <title>Git repository for song book for Computer Scientists</title>
7863 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
7864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
7865 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
7866 <description>&lt;p&gt;As I
7867 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
7868 this summer&lt;/a&gt;, I have created a Computer Science song book a few
7869 years ago, and today I finally found time to create a public
7870 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
7871 repository for the project&lt;/a&gt;.&lt;/p&gt;
7872
7873 &lt;p&gt;If you want to help out, please clone the source and submit patches
7874 to the HTML version. To generate the PDF and PostScript version,
7875 please use prince XML, or let me know about a useful free software
7876 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
7877
7878 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
7879 PostScript formats at
7880 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
7881 Science Songbook&lt;/a&gt;.&lt;/p&gt;
7882 </description>
7883 </item>
7884
7885 <item>
7886 <title>Gratulerer med 19-årsdagen, Debian!</title>
7887 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
7888 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
7889 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
7890 <description>&lt;p&gt;I dag fyller
7891 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
7892 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
7893 si gratulerer med dagen, Debian!&lt;/p&gt;
7894 </description>
7895 </item>
7896
7897 <item>
7898 <title>Song book for Computer Scientists</title>
7899 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
7900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
7901 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
7902 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
7903 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
7904 collecting computer related songs for use at parties. The original
7905 version was written in LaTeX, but a few years ago I got help from
7906 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7907 while keeping the ability to create a nice book in PDF format. I have
7908 not had time to maintain the book for a while now, and guess I should
7909 put it up on some public version control repository where others can
7910 help me extend and update the book. If anyone is volunteering to help
7911 me with this, send me an email. Also let me know if there are songs
7912 missing in my book.&lt;/p&gt;
7913
7914 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
7915 me today that I really should let all my readers share the joys of
7916 singing out load about programming, computers and computer networks.
7917 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
7918 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
7919 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
7920 Computer Science Songbook&lt;/a&gt;.
7921 </description>
7922 </item>
7923
7924 <item>
7925 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
7926 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
7927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
7928 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
7929 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
7930 around 1000 at the moment. To be able to get help from the vendors
7931 when something go wrong, we want to keep the firmware on the servers
7932 up to date. If the firmware isn&#39;t the latest and greatest, the
7933 vendors typically refuse to start debugging any problems until the
7934 firmware is upgraded. So before every reboot, we want to upgrade the
7935 firmware, and we would really like everyone handling servers at the
7936 university to do this themselves when they plan to reboot a machine.
7937 For that to happen we at the unix server admin group need to provide
7938 the tools to do so.&lt;/p&gt;
7939
7940 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
7941 fetch and install the latest firmware for the servers we got. Most of
7942 our hardware are from Dell and HP, so I have focused on these servers
7943 so far. This blog post is about the Dell part.&lt;/P&gt;
7944
7945 &lt;p&gt;On the Dell FTP site I was lucky enough to find
7946 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
7947 with firmware information for all 11th generation servers, listing
7948 which firmware should be used on a given model and where on the FTP
7949 site I can find it. Using a simple perl XML parser I can then
7950 download the shell scripts Dell provides to do firmware upgrades from
7951 within Linux and reboot when all the firmware is primed and ready to
7952 be activated on the first reboot.&lt;/p&gt;
7953
7954 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
7955 Are there anyone working on similar tools for firmware upgrading all
7956 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
7957
7958 &lt;p&gt;&lt;pre&gt;
7959 #!/usr/bin/perl
7960 use strict;
7961 use warnings;
7962 use File::Temp qw(tempdir);
7963 BEGIN {
7964 # Install needed RHEL packages if missing
7965 my %rhelmodules = (
7966 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
7967 );
7968 for my $module (keys %rhelmodules) {
7969 eval &quot;use $module;&quot;;
7970 if ($@) {
7971 my $pkg = $rhelmodules{$module};
7972 system(&quot;yum install -y $pkg&quot;);
7973 eval &quot;use $module;&quot;;
7974 }
7975 }
7976 }
7977 my $errorsto = &#39;pere@hungry.com&#39;;
7978
7979 upgrade_dell();
7980
7981 exit 0;
7982
7983 sub run_firmware_script {
7984 my ($opts, $script) = @_;
7985 unless ($script) {
7986 print STDERR &quot;fail: missing script name\n&quot;;
7987 exit 1
7988 }
7989 print STDERR &quot;Running $script\n\n&quot;;
7990
7991 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
7992 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
7993 } else {
7994 print STDERR &quot;fail: firmware script returned error\n&quot;;
7995 }
7996 }
7997
7998 sub run_firmware_scripts {
7999 my ($opts, @dirs) = @_;
8000 # Run firmware packages
8001 for my $dir (@dirs) {
8002 print STDERR &quot;info: Running scripts in $dir\n&quot;;
8003 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
8004 while (my $s = readdir $dh) {
8005 next if $s =~ m/^\.\.?/;
8006 run_firmware_script($opts, &quot;$dir/$s&quot;);
8007 }
8008 closedir $dh;
8009 }
8010 }
8011
8012 sub download {
8013 my $url = shift;
8014 print STDERR &quot;info: Downloading $url\n&quot;;
8015 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
8016 }
8017
8018 sub upgrade_dell {
8019 my @dirs;
8020 my $product = `dmidecode -s system-product-name`;
8021 chomp $product;
8022
8023 if ($product =~ m/PowerEdge/) {
8024
8025 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8026 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
8027
8028 my $tmpdir = tempdir(
8029 CLEANUP =&gt; 1
8030 );
8031 chdir($tmpdir);
8032 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
8033 system(&#39;gunzip Catalog.xml.gz&#39;);
8034 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
8035 # -q is quiet, disabling interactivity and reducing console output
8036 my $fwopts = &quot;-q&quot;;
8037 if (@paths) {
8038 for my $url (@paths) {
8039 fetch_dell_fw($url);
8040 }
8041 run_firmware_scripts($fwopts, $tmpdir);
8042 } else {
8043 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8044 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8045 }
8046 chdir(&#39;/&#39;);
8047 } else {
8048 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8049 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8050 }
8051 }
8052
8053 sub fetch_dell_fw {
8054 my $path = shift;
8055 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
8056 download($url);
8057 }
8058
8059 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8060 # firmware packages to download from Dell. Only work for Linux
8061 # machines and 11th generation Dell servers.
8062 sub fetch_dell_fw_list {
8063 my $filename = shift;
8064
8065 my $product = `dmidecode -s system-product-name`;
8066 chomp $product;
8067 my ($mybrand, $mymodel) = split(/\s+/, $product);
8068
8069 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
8070
8071 my $xml = XMLin($filename);
8072 my @paths;
8073 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
8074 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
8075 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
8076 my $oscode;
8077 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
8078 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
8079 } else {
8080 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
8081 }
8082 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
8083 {
8084 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
8085 }
8086 }
8087 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
8088 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
8089
8090 # Drop application packages, only firmware and BIOS
8091 next if &#39;APAC&#39; eq $componenttype;
8092
8093 my $cpath = $component-&gt;{path};
8094 for my $path (@paths) {
8095 if ($cpath =~ m%/$path$%) {
8096 push(@paths, $cpath);
8097 }
8098 }
8099 }
8100 return @paths;
8101 }
8102 &lt;/pre&gt;
8103
8104 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
8105 it could work on other platforms with some tweaking. Anyone know a
8106 index like Catalog.xml is available from HP for HP servers? At the
8107 moment I maintain a similar list manually and it is quickly getting
8108 outdated.&lt;/p&gt;
8109 </description>
8110 </item>
8111
8112 <item>
8113 <title>How is booting into runlevel 1 different from single user boots?</title>
8114 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
8115 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
8116 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
8117 <description>&lt;p&gt;Wouter Verhelst have some
8118 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
8119 comments and opinions&lt;/a&gt; on my blog post on
8120 &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
8121 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
8122 &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
8123 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
8124 small piece of his comment now, and though it best to address the
8125 misunderstanding he bring forward:&lt;/p&gt;
8126
8127 &lt;p&gt;&lt;blockquote&gt;
8128 Currently, a system admin has four options: [...] boot to a
8129 single-user system (by adding &#39;single&#39; to the kernel command line;
8130 this runs rcS and rc1 scripts)
8131 &lt;/blockquote&gt;&lt;/p&gt;
8132
8133 &lt;p&gt;This make me believe Wouter believe booting into single user mode
8134 and booting into runlevel 1 is the same. I am not surprised he
8135 believe this, because it would make sense and is a quite sensible
8136 thing to believe. But because the boot in Debian is slightly broken,
8137 runlevel 1 do not work properly and it isn&#39;t the same as single user
8138 mode. I&#39;ll try to explain what is actually happing, but it is a bit
8139 hard to explain.&lt;/p&gt;
8140
8141 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
8142 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
8143 executed in single user mode is sulogin. Single user mode is a boot
8144 state &quot;between&quot; the runlevels, and when booting into single user mode,
8145 only the scripts in /etc/rcS.d/ are executed before the init process
8146 enters the single user state. When switching to runlevel 1, the state
8147 is in fact not ending in runlevel 1, but it passes through runlevel 1
8148 and end up in the single user mode (see /etc/rc1.d/S03single, which
8149 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
8150 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
8151 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8152 mode).&lt;/p&gt;
8153
8154 &lt;p&gt;This summary might make it clearer. When booting for the first
8155 time into single user mode, the following commands are executed:
8156 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
8157 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
8158 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
8159 trying to continue after visiting single user mode. Not all services
8160 are started again as they should, causing the machine to end up in an
8161 unpredicatble state. This is why Debian admins recommend rebooting
8162 after visiting single user mode.&lt;/p&gt;
8163
8164 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
8165 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
8166 to runlevel 1, the services started from /etc/rcS.d/ are not properly
8167 stopped when passing through the scripts in /etc/rc1.d/, and not
8168 started again when switching away from runlevel 1 to the runlevels
8169 2-5. I believe the problem is best fixed by moving all the scripts
8170 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
8171 functioning single user mode during boot.&lt;/p&gt;
8172
8173 &lt;p&gt;I have spent several years investigating the Debian boot system,
8174 and discovered this problem a few years ago. I suspect it originates
8175 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
8176 </description>
8177 </item>
8178
8179 <item>
8180 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
8181 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
8182 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
8183 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
8184 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
8185 are started from /etc/rcS.d/. In fact, there is a bite more of them
8186 than make sense, and this causes a few problems. What kind of
8187 problems, you might ask. There are at least two problems. The first
8188 is that it is not possible to recover a machine after switching to
8189 runlevel 1. One need to actually reboot to get the machine back to
8190 the expected state. The other is that single user boot will sometimes
8191 run into problems because some of the subsystems are activated before
8192 the root login is presented, causing problems when trying to recover a
8193 machine from a problem in that subsystem. A minor additional point is
8194 that moving more scripts out of rcS.d/ and into the other rc#.d/
8195 directories will increase the amount of scripts that can run in
8196 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
8197
8198 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
8199 scripts that _have_ to execute before the root login prompt is
8200 presented during a single user boot should go there. Everything else
8201 should go into the numeric runlevels. This means things like
8202 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8203 the numeric runlevels. Today in Debian, there are around 115 init.d
8204 scripts that are started from rcS.d/, and most of them should be moved
8205 out. Do your package have one of them? Please help us make single
8206 user and runlevel 1 better by moving it.&lt;/p&gt;
8207
8208 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
8209 etc. should still be started from rcS.d/, but there is for example no
8210 need to have the network enabled before the single user login prompt
8211 is presented.&lt;/p&gt;
8212
8213 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
8214 Debian systems working while scripts migrate and during upgrades, the
8215 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8216 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8217 and the next ones can only be moved when their dependencies have been
8218 moved first. This migration must be done sequentially while we ensure
8219 that the package system upgrade packages in the right order to keep
8220 the system state correct. This will require some coordination when it
8221 comes to network related packages, but most of the packages with
8222 scripts that should migrate do not have anything in rcS.d/ depending
8223 on them. Some packages have already been updated, like the sudo
8224 package, while others are still left to do. I wish I had time to work
8225 on this myself, but real live constrains make it unlikely that I will
8226 find time to push this forward.&lt;/p&gt;
8227 </description>
8228 </item>
8229
8230 <item>
8231 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
8232 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
8233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
8234 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
8235 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
8236 mentioned the issues I believe should be improved in Debian for its
8237 desktop to be useful for more people. The use case for this is my
8238 parents, which are currently running Kubuntu which solve the
8239 issues.&lt;/p&gt;
8240
8241 &lt;p&gt;I suspect these four missing features are not very hard to
8242 implement. After all, they are present in Ubuntu, so if we wanted to
8243 do this in Debian we would have a source.&lt;/p&gt;
8244
8245 &lt;ol&gt;
8246
8247 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
8248 are new packages available for upgrades, a icon in the KDE status bar
8249 indicate this, and clicking on it will activate the simple upgrade
8250 tool to handle it. I have no problem guiding both of my parents
8251 through the process over the phone. If a kernel reboot is required,
8252 this too is indicated by the status bars and the upgrade tool. Last
8253 time I checked, nothing with the same features was working in KDE in
8254 Debian.&lt;/li&gt;
8255
8256 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
8257 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
8258 currently have a handler for, it will ask the user if the system
8259 should search for a package that would add support for this MIME type,
8260 and if the user say yes, the APT sources will be searched for packages
8261 advertising the MIME type in their control file (visible in the
8262 Packages file in the APT archive). If one or more packages are found,
8263 it is a simple click of the mouse to add support for the missing mime
8264 type. If the package require the user to accept some non-free
8265 license, this is explained to the user. The entire process make it
8266 more clear to the user why something do not work in the browser, and
8267 make the chances higher for the user to blame the web page authors and
8268 not the browser for any missing features.&lt;/li&gt;
8269
8270 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
8271 handlers.&lt;/strong&gt; When the media players encounter a format or codec
8272 it is not supporting, a dialog pop up asking the user if the system
8273 should search for a package that would add support for it. This
8274 happen with things like MP3, Windows Media or H.264. The selection
8275 and installation procedure is very similar to the Firefox browser
8276 plugin handling. This is as far as I know implemented using a
8277 gstreamer hook. The end result is that the user easily get access to
8278 the codecs that are present from the APT archives available, while
8279 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
8280
8281 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
8282 displaying a text/plain file in my Debian browser, it will propose to
8283 start emacs to show it. If I remember correctly, when doing the same
8284 in Kunbutu it show the file as a text file in the browser. At least I
8285 know Opera will show text files within the browser. I much prefer the
8286 latter behaviour.&lt;/li&gt;
8287
8288 &lt;/ol&gt;
8289
8290 &lt;p&gt;There are other nice features as well, like the simplified suite
8291 upgrader, but given that I am the one mostly doing the dist-upgrade,
8292 it do not matter much.&lt;/p&gt;
8293
8294 &lt;p&gt;I really hope we could get these features in place for the next
8295 Debian release. It would require the coordinated effort of several
8296 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
8297 </description>
8298 </item>
8299
8300 <item>
8301 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
8302 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
8303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
8304 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
8305 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
8306 site is build on Debian/Squeeze, and this platform was chosen because
8307 I am most familiar with Debian (being a Debian Developer for around 10
8308 years) because it is the latest stable Debian release which should get
8309 security support for a few years.&lt;/p&gt;
8310
8311 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
8312 that are missing in Debian at the moment. It would be great if these
8313 modules were added to the Debian archive, allowing anyone to set up
8314 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
8315 in their own country using only Debian packages. The list of modules
8316 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
8317 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
8318 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8319 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8320 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8321 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8322 easier in the future.&lt;/p&gt;
8323
8324 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
8325 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
8326 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
8327 with the responsibility of tracking security problems, which I really
8328 do not have time for.&lt;/p&gt;
8329 </description>
8330 </item>
8331
8332 <item>
8333 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
8334 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
8335 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
8336 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
8337 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
8338 posts have been in Norwegian the last few weeks, so here is a short
8339 update in English.&lt;/p&gt;
8340
8341 &lt;p&gt;The kids still keep me too busy to get much free software work
8342 done, but I did manage to organise a project to get a Norwegian port
8343 of the British service
8344 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8345 and it has been running for a month now. The entire project has been
8346 organised by me and two others. Around Christmas we gathered sponsors
8347 to fund the development work. In January I drafted a contract with
8348 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8349 and in February the development took place. Most of it involved
8350 converting the source to use GPS coordinates instead of British
8351 easting/northing, and the resulting code should be a lot easier to get
8352 running in any country by now. The Norwegian
8353 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8354 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8355 source and the source for administrative borders in Norway, and
8356 support for this had to be added/fixed.&lt;/p&gt;
8357
8358 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8359 polishing the system before we announced it March 7th. The system is
8360 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8361 problem reports in a few weeks. Soon we hope to announce the Android
8362 and iPhone versions making it even easier to report problems with the
8363 public infrastructure.&lt;/p&gt;
8364
8365 &lt;p&gt;Perhaps something to consider for those of you in countries without
8366 such service?&lt;/p&gt;
8367 </description>
8368 </item>
8369
8370 <item>
8371 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8372 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8374 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8375 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8376 issues here at my work with the University of Oslo. My idea is that
8377 it should be possible to use the information about security issues
8378 available on the Internet, and check our locally
8379 maintained/distributed software against this information. It should
8380 allow us to verify that no known security issues are forgotten. The
8381 CVE database listing vulnerabilities seem like a great central point,
8382 and by using the package lists from Debian mapped to CVEs provided by
8383 the testing security team, I believed it should be possible to figure
8384 out which security holes were present in our free software
8385 collection.&lt;/p&gt;
8386
8387 &lt;p&gt;After reading up on the topic, it became obvious that the first
8388 building block is to be able to name software packages in a unique and
8389 consistent way across data sources. I considered several ways to do
8390 this, for example coming up with my own naming scheme like using URLs
8391 to project home pages or URLs to the Freshmeat entries, or using some
8392 existing naming scheme. And it seem like I am not the first one to
8393 come across this problem, as MITRE already proposed and implemented a
8394 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8395 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8396 software, hardware and other platform components. The CPE ids are
8397 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8398 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8399 issues for any CPE name. With this in place, all I need to do is to
8400 locate the CPE id for the software packages we use at the university.
8401 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8402 NVD entry if a CVE for the package exist).&lt;/p&gt;
8403
8404 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8405 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8406 check out, one could look up
8407 &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
8408 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8409 The most recent one is
8410 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8411 and at the bottom of the NVD page for this vulnerability the complete
8412 list of affected versions is provided.&lt;/p&gt;
8413
8414 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8415 for offline processing of issues. Using this dump, I&#39;ve written a
8416 small script taking a list of CPEs as input and list all CVEs
8417 affecting the packages represented by these CPEs. One give it CPEs
8418 with version numbers as specified above and get a list of open
8419 security issues out.&lt;/p&gt;
8420
8421 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8422 information need to be high. For that to happen, I believe as many as
8423 possible need to use and contribute to the NVD database. I notice
8424 RHEL is providing
8425 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8426 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8427 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8428
8429 &lt;p&gt;To get an idea about the quality for free software, I spent some
8430 time making it possible to compare the CVE database from Debian with
8431 the CVE database in NVD. The result look fairly good, but there are
8432 some inconsistencies in NVD (same software package having several
8433 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8434 Debian believe are affected by a CVE). Hope to find time to improve
8435 the quality of NVD, but that require being able to get in touch with
8436 someone maintaining it. So far my three emails with questions and
8437 corrections have not seen any reply, but I hope contact can be
8438 established soon.&lt;/p&gt;
8439
8440 &lt;p&gt;An interesting application for CPEs is cross platform package
8441 mapping. It would be useful to know which packages in for example
8442 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8443 this would be trivial if all linux distributions provided CPE entries
8444 for their packages.&lt;/p&gt;
8445 </description>
8446 </item>
8447
8448 <item>
8449 <title>Which module is loaded for a given PCI and USB device?</title>
8450 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8452 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8453 <description>&lt;p&gt;In the
8454 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8455 package in Debian, there is a script to report useful information
8456 about the running hardware for use when people report missing
8457 information. One part of this script that I find very useful when
8458 debugging hardware problems, is the part mapping loaded kernel module
8459 to the PCI device it claims. It allow me to quickly see if the kernel
8460 module I expect is driving the hardware I am struggling with. To see
8461 the output, make sure discover-data is installed and run
8462 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8463 one of my machines like this:&lt;/p&gt;
8464
8465 &lt;pre&gt;
8466 loaded modules:
8467 10de:03eb i2c_nforce2
8468 10de:03f1 ohci_hcd
8469 10de:03f2 ehci_hcd
8470 10de:03f0 snd_hda_intel
8471 10de:03ec pata_amd
8472 10de:03f6 sata_nv
8473 1022:1103 k8temp
8474 109e:036e bttv
8475 109e:0878 snd_bt87x
8476 11ab:4364 sky2
8477 &lt;/pre&gt;
8478
8479 &lt;p&gt;The code in question look like this, slightly modified for
8480 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8481
8482 &lt;pre&gt;
8483 if [ -d /sys/bus/pci/devices/ ] ; then
8484 echo loaded pci modules:
8485 (
8486 cd /sys/bus/pci/devices/
8487 for address in * ; do
8488 if [ -d &quot;$address/driver/module&quot; ] ; then
8489 module=`cd $address/driver/module ; pwd -P | xargs basename`
8490 if grep -q &quot;^$module &quot; /proc/modules ; then
8491 address=$(echo $address |sed s/0000://)
8492 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8493 echo &quot;$id $module&quot;
8494 fi
8495 fi
8496 done
8497 )
8498 echo
8499 fi
8500 &lt;/pre&gt;
8501
8502 &lt;p&gt;Similar code could be used to extract USB device module
8503 mappings:&lt;/p&gt;
8504
8505 &lt;pre&gt;
8506 if [ -d /sys/bus/usb/devices/ ] ; then
8507 echo loaded usb modules:
8508 (
8509 cd /sys/bus/usb/devices/
8510 for address in * ; do
8511 if [ -d &quot;$address/driver/module&quot; ] ; then
8512 module=`cd $address/driver/module ; pwd -P | xargs basename`
8513 if grep -q &quot;^$module &quot; /proc/modules ; then
8514 address=$(echo $address |sed s/0000://)
8515 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8516 if [ &quot;$id&quot; ] ; then
8517 echo &quot;$id $module&quot;
8518 fi
8519 fi
8520 fi
8521 done
8522 )
8523 echo
8524 fi
8525 &lt;/pre&gt;
8526
8527 &lt;p&gt;This might perhaps be something to include in other tools as
8528 well.&lt;/p&gt;
8529 </description>
8530 </item>
8531
8532 <item>
8533 <title>How to test if a laptop is working with Linux</title>
8534 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8535 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8536 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8537 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8538 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8539 batch of computers will work with Linux. Every year for the last few
8540 years the university have organised shared bid of a few thousand
8541 computers, and this year HP won the bid. Two different desktops and
8542 five different laptops are on the list this year. We in the UNIX
8543 group want to know which one of these computers work well with RHEL
8544 and Ubuntu, the two Linux distributions we currently handle at the
8545 university.&lt;/p&gt;
8546
8547 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8548 perhaps inspire others to test hardware as well. To test, I PXE
8549 install the OS version of choice, and log in as my normal user and run
8550 a few applications and plug in selected pieces of hardware. When
8551 something fail, I make a note about this in the test matrix and move
8552 on. If I have some spare time I try to report the bug to the OS
8553 vendor, but as I only have the machines for a short time, I rarely
8554 have the time to do this for all the problems I find.&lt;/p&gt;
8555
8556 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8557 I perform on a new model.&lt;/p&gt;
8558
8559 &lt;ul&gt;
8560
8561 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8562 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8563 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8564
8565 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8566 installation, X.org is working.&lt;/li&gt;
8567
8568 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8569 package mesa-utils on Ubuntu) and writing down the frames per second
8570 reported by the program.&lt;/li&gt;
8571
8572 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8573 logging in, and if I can hear this the test is successful. If there
8574 are several audio exits on the machine, I try them all and check if
8575 the Gnome/KDE audio mixer can control where to send the sound. I
8576 normally test this by playing
8577 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8578 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8579
8580 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8581 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8582
8583 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8584 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8585
8586 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8587 picture from the v4l device show up.&lt;/li&gt;
8588
8589 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8590 any bluetooth devices are discovered. In my office, I normally see a
8591 few.&lt;/li&gt;
8592
8593 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8594 memory modules lying around, and stick them in and see if Gnome/KDE
8595 notice this.&lt;/li&gt;
8596
8597 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8598 special button work, and if the laptop continue to work after
8599 resume.&lt;/li&gt;
8600
8601 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8602 adjusting background light, switching on/off external video output,
8603 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8604 laptop to laptop, so I just write down which are working and which are
8605 not.&lt;/li&gt;
8606
8607 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8608 acceleration sensors etc. I rarely test these, as I do not know how
8609 to quickly test if they are working or not, so I only document their
8610 existence.&lt;/li&gt;
8611
8612 &lt;/ul&gt;
8613
8614 &lt;p&gt;By now I suspect you are really curious what the test results are
8615 for the HP machines I am testing. I&#39;m not done yet, so I will report
8616 the test results later. For now I can report that HP 8100 Elite work
8617 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8618 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8619 can see, I have most machines left to test. One interesting
8620 observation is that Ubuntu Lucid has almost twice the frame rate than
8621 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8622 </description>
8623 </item>
8624
8625 <item>
8626 <title>Some thoughts on BitCoins</title>
8627 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8628 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8629 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8630 <description>&lt;p&gt;As I continue to explore
8631 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8632 what properties the system have, and how it will be affected by laws
8633 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8634
8635 &lt;p&gt;One interesting thing to note is that since the transactions are
8636 verified using a peer to peer network, all details about a transaction
8637 is known to everyone. This means that if a BitCoin address has been
8638 published like I did with mine in my initial post about BitCoin, it is
8639 possible for everyone to see how many BitCoins have been transfered to
8640 that address. There is even a web service to look at the details for
8641 all transactions. There I can see that my address
8642 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8643 have received 16.06 Bitcoin, the
8644 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8645 address of Simon Phipps have received 181.97 BitCoin and the address
8646 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8647 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8648 every one of you that donated bitcoins to support my activity. The
8649 fact that anyone can see how much money was transfered to a given
8650 address make it more obvious why the BitCoin community recommend to
8651 generate and hand out a new address for each transaction. I&#39;m told
8652 there is no way to track which addresses belong to a given person or
8653 organisation without the person or organisation revealing it
8654 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8655
8656 &lt;p&gt;In Norway, and in most other countries, there are laws and
8657 regulations limiting how much money one can transfer across the border
8658 without declaring it. There are money laundering, tax and accounting
8659 laws and regulations I would expect to apply to the use of BitCoin.
8660 If the Skolelinux foundation
8661 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8662 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8663 normal bank transfers like EFF is doing, how should this be accounted?
8664 Given that it is impossible to know if money can cross the border or
8665 not, should everything or nothing be declared? What exchange rate
8666 should be used when calculating taxes? Would receivers have to pay
8667 income tax if the foundation were to pay Skolelinux contributors in
8668 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8669
8670 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8671 accepted by a lot of users. It must be possible to get easy access to
8672 the currency (as a wage or using currency exchanges), and it must be
8673 easy to spend it. At the moment BitCoin seem fairly easy to get
8674 access to, but there are very few places to spend it. I am not really
8675 a regular user of any of the vendor types currently accepting BitCoin,
8676 so I wonder when my kind of shop would start accepting BitCoins. I
8677 would like to buy electronics, travels and subway tickets, not herbs
8678 and books. :) The currency is young, and this will improve over time
8679 if it become popular, but I suspect regular banks will start to lobby
8680 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8681 will claim it is helping fund terrorism and money laundering (which
8682 probably would be true, as is any currency in existence), but I
8683 believe the problems should be solved elsewhere and not by blaming
8684 currencies.&lt;/p&gt;
8685
8686 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8687 CPU intensive process that depend on a bit of luck as well (as one is
8688 competing against all the other miners currently spending CPU cycles
8689 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8690 BitCoin when this happen. Yesterday I came across the obvious way to
8691 join forces to increase ones changes of getting at least some coins,
8692 by coordinating the work on mining BitCoins across several machines
8693 and people, and sharing the result if one is lucky and get the 50
8694 BitCoins. Check out
8695 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8696 if this sounds interesting. I have not had time to try to set up a
8697 machine to participate there yet, but have seen that running on ones
8698 own for a few days have not yield any BitCoins througth mining
8699 yet.&lt;/p&gt;
8700
8701 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8702 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8703 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8704 it was interesting to read. The arguments presented seem to be
8705 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8706 </description>
8707 </item>
8708
8709 <item>
8710 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8711 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8713 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8714 <description>&lt;p&gt;With this weeks lawless
8715 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8716 attacks&lt;/a&gt; on Wikileak and
8717 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8718 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8719 not be trusted to handle money transactions.
8720 A blog post from
8721 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8722 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8723 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8724 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8725 some help from my friend to get it all running, and he even handed me
8726 some bitcoins to get started. I even donated a few bitcoins to Simon
8727 for helping me remember BitCoin.&lt;/p&gt;
8728
8729 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8730 crypto-currency, decentralised and handled using peer-to-peer
8731 networks. It allows anonymous transactions and prohibits central
8732 control over the transactions, making it impossible for governments
8733 and companies alike to block donations and other transactions. The
8734 source is free software, and while the key dependency wxWidgets 2.9
8735 for the graphical user interface is missing in Debian, the command
8736 line client builds just fine. Hopefully Jonas
8737 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8738 Debian&lt;/a&gt; soon.&lt;/p&gt;
8739
8740 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8741 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8742 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8743 currency &quot;stock&quot; markets where the exchange rate is decided. There
8744 are not many users so far, but the concept seems promising. If you
8745 want to get started and lack a friend with any bitcoins to spare,
8746 you can even get
8747 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8748 bitcoin at the time of writing). Use
8749 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8750 on the current exchange rates.&lt;/p&gt;
8751
8752 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8753 machines. If you want to support my activity, please send Bitcoin
8754 donations to the address
8755 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8756 </description>
8757 </item>
8758
8759 <item>
8760 <title>Why isn&#39;t Debian Edu using VLC?</title>
8761 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8763 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8764 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8765 presented, and the winner among the multimedia player were VLC.
8766 Personally, I like VLC, and it is my player of choice when I first try
8767 to play a video file or stream. Only if VLC fail will I drag out
8768 gmplayer to see if it can do better. The reason is mostly the failure
8769 model and trust. When VLC fail, it normally pop up a error message
8770 reporting the problem. When mplayer fail, it normally segfault or
8771 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8772
8773 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8774 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8775 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8776 plugin to play web videos seamlessly, and the VLC browser plugin is
8777 not very good. For example, it lack in-line control buttons, so there
8778 is no way for the user to pause the video. Also, when I
8779 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8780 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8781 failed on several video pages where mplayer based plugins worked. If
8782 the browser plugin for VLC was as good as the gecko-mediaplayer
8783 package (which uses mplayer), we would switch.&lt;/P&gt;
8784
8785 &lt;p&gt;While VLC is a good player, its user interface is slightly
8786 annoying. The most annoying feature is its inconsistent use of
8787 keyboard shortcuts. When the player is in full screen mode, its
8788 shortcuts are different from when it is playing the video in a window.
8789 For example, space only work as pause when in full screen mode. I
8790 wish it had consisten shortcuts and that space also would work when in
8791 window mode. Another nice shortcut in gmplayer is [enter] to restart
8792 the current video. It is very nice when playing short videos from the
8793 web and want to restart it when new people arrive to have a look at
8794 what is going on.&lt;/p&gt;
8795 </description>
8796 </item>
8797
8798 <item>
8799 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8800 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8801 <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>
8802 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8803 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8804 upgrade testing of the
8805 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8806 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8807 This seem like a very good idea, so I adjusted by test scripts and
8808 can now present the updated result from today:&lt;/p&gt;
8809
8810 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8811
8812 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8813
8814 &lt;blockquote&gt;&lt;p&gt;
8815 apache2.2-bin
8816 aptdaemon
8817 baobab
8818 binfmt-support
8819 browser-plugin-gnash
8820 cheese-common
8821 cli-common
8822 cups-pk-helper
8823 dmz-cursor-theme
8824 empathy
8825 empathy-common
8826 freedesktop-sound-theme
8827 freeglut3
8828 gconf-defaults-service
8829 gdm-themes
8830 gedit-plugins
8831 geoclue
8832 geoclue-hostip
8833 geoclue-localnet
8834 geoclue-manual
8835 geoclue-yahoo
8836 gnash
8837 gnash-common
8838 gnome
8839 gnome-backgrounds
8840 gnome-cards-data
8841 gnome-codec-install
8842 gnome-core
8843 gnome-desktop-environment
8844 gnome-disk-utility
8845 gnome-screenshot
8846 gnome-search-tool
8847 gnome-session-canberra
8848 gnome-system-log
8849 gnome-themes-extras
8850 gnome-themes-more
8851 gnome-user-share
8852 gstreamer0.10-fluendo-mp3
8853 gstreamer0.10-tools
8854 gtk2-engines
8855 gtk2-engines-pixbuf
8856 gtk2-engines-smooth
8857 hamster-applet
8858 libapache2-mod-dnssd
8859 libapr1
8860 libaprutil1
8861 libaprutil1-dbd-sqlite3
8862 libaprutil1-ldap
8863 libart2.0-cil
8864 libboost-date-time1.42.0
8865 libboost-python1.42.0
8866 libboost-thread1.42.0
8867 libchamplain-0.4-0
8868 libchamplain-gtk-0.4-0
8869 libcheese-gtk18
8870 libclutter-gtk-0.10-0
8871 libcryptui0
8872 libdiscid0
8873 libelf1
8874 libepc-1.0-2
8875 libepc-common
8876 libepc-ui-1.0-2
8877 libfreerdp-plugins-standard
8878 libfreerdp0
8879 libgconf2.0-cil
8880 libgdata-common
8881 libgdata7
8882 libgdu-gtk0
8883 libgee2
8884 libgeoclue0
8885 libgexiv2-0
8886 libgif4
8887 libglade2.0-cil
8888 libglib2.0-cil
8889 libgmime2.4-cil
8890 libgnome-vfs2.0-cil
8891 libgnome2.24-cil
8892 libgnomepanel2.24-cil
8893 libgpod-common
8894 libgpod4
8895 libgtk2.0-cil
8896 libgtkglext1
8897 libgtksourceview2.0-common
8898 libmono-addins-gui0.2-cil
8899 libmono-addins0.2-cil
8900 libmono-cairo2.0-cil
8901 libmono-corlib2.0-cil
8902 libmono-i18n-west2.0-cil
8903 libmono-posix2.0-cil
8904 libmono-security2.0-cil
8905 libmono-sharpzip2.84-cil
8906 libmono-system2.0-cil
8907 libmtp8
8908 libmusicbrainz3-6
8909 libndesk-dbus-glib1.0-cil
8910 libndesk-dbus1.0-cil
8911 libopal3.6.8
8912 libpolkit-gtk-1-0
8913 libpt2.6.7
8914 libpython2.6
8915 librpm1
8916 librpmio1
8917 libsdl1.2debian
8918 libsrtp0
8919 libssh-4
8920 libtelepathy-farsight0
8921 libtelepathy-glib0
8922 libtidy-0.99-0
8923 media-player-info
8924 mesa-utils
8925 mono-2.0-gac
8926 mono-gac
8927 mono-runtime
8928 nautilus-sendto
8929 nautilus-sendto-empathy
8930 p7zip-full
8931 pkg-config
8932 python-aptdaemon
8933 python-aptdaemon-gtk
8934 python-axiom
8935 python-beautifulsoup
8936 python-bugbuddy
8937 python-clientform
8938 python-coherence
8939 python-configobj
8940 python-crypto
8941 python-cupshelpers
8942 python-elementtree
8943 python-epsilon
8944 python-evolution
8945 python-feedparser
8946 python-gdata
8947 python-gdbm
8948 python-gst0.10
8949 python-gtkglext1
8950 python-gtksourceview2
8951 python-httplib2
8952 python-louie
8953 python-mako
8954 python-markupsafe
8955 python-mechanize
8956 python-nevow
8957 python-notify
8958 python-opengl
8959 python-openssl
8960 python-pam
8961 python-pkg-resources
8962 python-pyasn1
8963 python-pysqlite2
8964 python-rdflib
8965 python-serial
8966 python-tagpy
8967 python-twisted-bin
8968 python-twisted-conch
8969 python-twisted-core
8970 python-twisted-web
8971 python-utidylib
8972 python-webkit
8973 python-xdg
8974 python-zope.interface
8975 remmina
8976 remmina-plugin-data
8977 remmina-plugin-rdp
8978 remmina-plugin-vnc
8979 rhythmbox-plugin-cdrecorder
8980 rhythmbox-plugins
8981 rpm-common
8982 rpm2cpio
8983 seahorse-plugins
8984 shotwell
8985 software-center
8986 system-config-printer-udev
8987 telepathy-gabble
8988 telepathy-mission-control-5
8989 telepathy-salut
8990 tomboy
8991 totem
8992 totem-coherence
8993 totem-mozilla
8994 totem-plugins
8995 transmission-common
8996 xdg-user-dirs
8997 xdg-user-dirs-gtk
8998 xserver-xephyr
8999 &lt;/p&gt;&lt;/blockquote&gt;
9000
9001 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9002
9003 &lt;blockquote&gt;&lt;p&gt;
9004 cheese
9005 ekiga
9006 eog
9007 epiphany-extensions
9008 evolution-exchange
9009 fast-user-switch-applet
9010 file-roller
9011 gcalctool
9012 gconf-editor
9013 gdm
9014 gedit
9015 gedit-common
9016 gnome-games
9017 gnome-games-data
9018 gnome-nettool
9019 gnome-system-tools
9020 gnome-themes
9021 gnuchess
9022 gucharmap
9023 guile-1.8-libs
9024 libavahi-ui0
9025 libdmx1
9026 libgalago3
9027 libgtk-vnc-1.0-0
9028 libgtksourceview2.0-0
9029 liblircclient0
9030 libsdl1.2debian-alsa
9031 libspeexdsp1
9032 libsvga1
9033 rhythmbox
9034 seahorse
9035 sound-juicer
9036 system-config-printer
9037 totem-common
9038 transmission-gtk
9039 vinagre
9040 vino
9041 &lt;/p&gt;&lt;/blockquote&gt;
9042
9043 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9044
9045 &lt;blockquote&gt;&lt;p&gt;
9046 gstreamer0.10-gnomevfs
9047 &lt;/p&gt;&lt;/blockquote&gt;
9048
9049 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9050
9051 &lt;blockquote&gt;&lt;p&gt;
9052 [nothing]
9053 &lt;/p&gt;&lt;/blockquote&gt;
9054
9055 &lt;p&gt;This is for KDE:&lt;/p&gt;
9056
9057 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9058
9059 &lt;blockquote&gt;&lt;p&gt;
9060 ksmserver
9061 &lt;/p&gt;&lt;/blockquote&gt;
9062
9063 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9064
9065 &lt;blockquote&gt;&lt;p&gt;
9066 kwin
9067 network-manager-kde
9068 &lt;/p&gt;&lt;/blockquote&gt;
9069
9070 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9071
9072 &lt;blockquote&gt;&lt;p&gt;
9073 arts
9074 dolphin
9075 freespacenotifier
9076 google-gadgets-gst
9077 google-gadgets-xul
9078 kappfinder
9079 kcalc
9080 kcharselect
9081 kde-core
9082 kde-plasma-desktop
9083 kde-standard
9084 kde-window-manager
9085 kdeartwork
9086 kdeartwork-emoticons
9087 kdeartwork-style
9088 kdeartwork-theme-icon
9089 kdebase
9090 kdebase-apps
9091 kdebase-workspace
9092 kdebase-workspace-bin
9093 kdebase-workspace-data
9094 kdeeject
9095 kdelibs
9096 kdeplasma-addons
9097 kdeutils
9098 kdewallpapers
9099 kdf
9100 kfloppy
9101 kgpg
9102 khelpcenter4
9103 kinfocenter
9104 konq-plugins-l10n
9105 konqueror-nsplugins
9106 kscreensaver
9107 kscreensaver-xsavers
9108 ktimer
9109 kwrite
9110 libgle3
9111 libkde4-ruby1.8
9112 libkonq5
9113 libkonq5-templates
9114 libnetpbm10
9115 libplasma-ruby
9116 libplasma-ruby1.8
9117 libqt4-ruby1.8
9118 marble-data
9119 marble-plugins
9120 netpbm
9121 nuvola-icon-theme
9122 plasma-dataengines-workspace
9123 plasma-desktop
9124 plasma-desktopthemes-artwork
9125 plasma-runners-addons
9126 plasma-scriptengine-googlegadgets
9127 plasma-scriptengine-python
9128 plasma-scriptengine-qedje
9129 plasma-scriptengine-ruby
9130 plasma-scriptengine-webkit
9131 plasma-scriptengines
9132 plasma-wallpapers-addons
9133 plasma-widget-folderview
9134 plasma-widget-networkmanagement
9135 ruby
9136 sweeper
9137 update-notifier-kde
9138 xscreensaver-data-extra
9139 xscreensaver-gl
9140 xscreensaver-gl-extra
9141 xscreensaver-screensaver-bsod
9142 &lt;/p&gt;&lt;/blockquote&gt;
9143
9144 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9145
9146 &lt;blockquote&gt;&lt;p&gt;
9147 ark
9148 google-gadgets-common
9149 google-gadgets-qt
9150 htdig
9151 kate
9152 kdebase-bin
9153 kdebase-data
9154 kdepasswd
9155 kfind
9156 klipper
9157 konq-plugins
9158 konqueror
9159 ksysguard
9160 ksysguardd
9161 libarchive1
9162 libcln6
9163 libeet1
9164 libeina-svn-06
9165 libggadget-1.0-0b
9166 libggadget-qt-1.0-0b
9167 libgps19
9168 libkdecorations4
9169 libkephal4
9170 libkonq4
9171 libkonqsidebarplugin4a
9172 libkscreensaver5
9173 libksgrd4
9174 libksignalplotter4
9175 libkunitconversion4
9176 libkwineffects1a
9177 libmarblewidget4
9178 libntrack-qt4-1
9179 libntrack0
9180 libplasma-geolocation-interface4
9181 libplasmaclock4a
9182 libplasmagenericshell4
9183 libprocesscore4a
9184 libprocessui4a
9185 libqalculate5
9186 libqedje0a
9187 libqtruby4shared2
9188 libqzion0a
9189 libruby1.8
9190 libscim8c2a
9191 libsmokekdecore4-3
9192 libsmokekdeui4-3
9193 libsmokekfile3
9194 libsmokekhtml3
9195 libsmokekio3
9196 libsmokeknewstuff2-3
9197 libsmokeknewstuff3-3
9198 libsmokekparts3
9199 libsmokektexteditor3
9200 libsmokekutils3
9201 libsmokenepomuk3
9202 libsmokephonon3
9203 libsmokeplasma3
9204 libsmokeqtcore4-3
9205 libsmokeqtdbus4-3
9206 libsmokeqtgui4-3
9207 libsmokeqtnetwork4-3
9208 libsmokeqtopengl4-3
9209 libsmokeqtscript4-3
9210 libsmokeqtsql4-3
9211 libsmokeqtsvg4-3
9212 libsmokeqttest4-3
9213 libsmokeqtuitools4-3
9214 libsmokeqtwebkit4-3
9215 libsmokeqtxml4-3
9216 libsmokesolid3
9217 libsmokesoprano3
9218 libtaskmanager4a
9219 libtidy-0.99-0
9220 libweather-ion4a
9221 libxklavier16
9222 libxxf86misc1
9223 okteta
9224 oxygencursors
9225 plasma-dataengines-addons
9226 plasma-scriptengine-superkaramba
9227 plasma-widget-lancelot
9228 plasma-widgets-addons
9229 plasma-widgets-workspace
9230 polkit-kde-1
9231 ruby1.8
9232 systemsettings
9233 update-notifier-common
9234 &lt;/p&gt;&lt;/blockquote&gt;
9235
9236 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
9237 aptitude a bit more similar, but there are still quite a lott of
9238 differences. I have no idea what packages should be installed after
9239 the upgrade, but hope those that do can have a look.&lt;/p&gt;
9240 </description>
9241 </item>
9242
9243 <item>
9244 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
9245 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
9246 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
9247 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
9248 <description>&lt;p&gt;Most of the computers in use by the
9249 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
9250 are virtual machines. And they have been Xen machines running on a
9251 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
9252 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
9253 bit harder that it could have been, because we set up the Xen virtual
9254 machines to get the virtual partitions from LVM, which as far as I
9255 know is not supported by KVM. So to migrate, we had to convert
9256 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
9257
9258 &lt;p&gt;I found
9259 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
9260 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
9261 migration. It uses qemu-img from the qemu package to make the disk
9262 image, parted to partition it, losetup and kpartx to present the disk
9263 image partions as devices, and dd to copy the data. I NFS mounted the
9264 new servers storage area on the old server to do the migration.&lt;/p&gt;
9265
9266 &lt;pre&gt;
9267 #!/bin/sh
9268
9269 # Based on
9270 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9271
9272 set -e
9273 set -x
9274
9275 if [ -z &quot;$1&quot; ] ; then
9276 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
9277 exit 1
9278 else
9279 host=&quot;$1&quot;
9280 fi
9281
9282 if [ ! -e /dev/vg_data/$host-disk ] ; then
9283 echo &quot;error: unable to find LVM volume for $host&quot;
9284 exit 1
9285 fi
9286
9287 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9288 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9289 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9290 totalsize=$(( ( $disksize + $swapsize ) ))
9291
9292 img=$host.img
9293 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
9294 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9295
9296 parted $img mklabel msdos
9297 parted $img mkpart primary linux-swap 0 $disksize
9298 parted $img mkpart primary ext2 $disksize $totalsize
9299 parted $img set 1 boot on
9300
9301 modprobe dm-mod
9302 losetup /dev/loop0 $img
9303 kpartx -a /dev/loop0
9304
9305 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
9306 fsck.ext3 -f /dev/mapper/loop0p1 || true
9307 mkswap /dev/mapper/loop0p2
9308
9309 kpartx -d /dev/loop0
9310 losetup -d /dev/loop0
9311 &lt;/pre&gt;
9312
9313 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
9314 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
9315
9316 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
9317 the new disk image attached, installed grub-pc and linux-image-686 and
9318 set up grub to boot from the disk image. After this, the KVM machines
9319 seem to work just fine.&lt;/p&gt;
9320 </description>
9321 </item>
9322
9323 <item>
9324 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
9325 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
9326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
9327 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
9328 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
9329 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9330 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
9331 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
9332
9333 &lt;p&gt;I still do not know what a correct migration should look like, so I
9334 report any differences between apt and aptitude and hope someone else
9335 can see if anything should be changed.&lt;/p&gt;
9336
9337 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9338
9339 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9340
9341 &lt;blockquote&gt;&lt;p&gt;
9342 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9343 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9344 dmz-cursor-theme empathy empathy-common finger
9345 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9346 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9347 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9348 gnome-cards-data gnome-codec-install gnome-core
9349 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9350 gnome-search-tool gnome-session-canberra gnome-spell
9351 gnome-system-log gnome-themes-extras gnome-themes-more
9352 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9353 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9354 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9355 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9356 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9357 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9358 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9359 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9360 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9361 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9362 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9363 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9364 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9365 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9366 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9367 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9368 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9369 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9370 libmono-security2.0-cil libmono-sharpzip2.84-cil
9371 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9372 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9373 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9374 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9375 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9376 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9377 libxalan2-java libxerces2-java media-player-info mesa-utils
9378 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9379 nautilus-sendto-empathy openoffice.org-writer2latex
9380 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9381 python-aptdaemon python-aptdaemon-gtk python-axiom
9382 python-beautifulsoup python-bugbuddy python-clientform
9383 python-coherence python-configobj python-crypto python-cupshelpers
9384 python-cupsutils python-eggtrayicon python-elementtree
9385 python-epsilon python-evolution python-feedparser python-gdata
9386 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9387 python-gtksourceview2 python-httplib2 python-louie python-mako
9388 python-markupsafe python-mechanize python-nevow python-notify
9389 python-opengl python-openssl python-pam python-pkg-resources
9390 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9391 python-tagpy python-twisted-bin python-twisted-conch
9392 python-twisted-core python-twisted-web python-utidylib python-webkit
9393 python-xdg python-zope.interface remmina remmina-plugin-data
9394 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9395 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9396 software-center svgalibg1 system-config-printer-udev
9397 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9398 totem totem-coherence totem-mozilla totem-plugins
9399 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9400 zip
9401 &lt;/p&gt;&lt;/blockquote&gt;
9402
9403 Installed using apt-get, removed with aptitude
9404
9405 &lt;blockquote&gt;&lt;p&gt;
9406 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9407 epiphany-extensions epiphany-gecko evolution-exchange
9408 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9409 gedit-common gnome-app-install gnome-games gnome-games-data
9410 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9411 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9412 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9413 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9414 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9415 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9416 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9417 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9418 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9419 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9420 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9421 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9422 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9423 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9424 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9425 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9426 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9427 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9428 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9429 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9430 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9431 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9432 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9433 sound-juicer swfdec-gnome system-config-printer totem-common
9434 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9435 &lt;/p&gt;&lt;/blockquote&gt;
9436
9437 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9438
9439 &lt;blockquote&gt;&lt;p&gt;
9440 gstreamer0.10-gnomevfs
9441 &lt;/p&gt;&lt;/blockquote&gt;
9442
9443 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9444
9445 &lt;blockquote&gt;&lt;p&gt;
9446 [nothing]
9447 &lt;/p&gt;&lt;/blockquote&gt;
9448
9449 &lt;p&gt;This is for KDE:&lt;/p&gt;
9450
9451 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9452
9453 &lt;blockquote&gt;&lt;p&gt;
9454 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9455 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9456 ghostscript-x git gnome-audio gnugo granatier gs-common
9457 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9458 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9459 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9460 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9461 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9462 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9463 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9464 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9465 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9466 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9467 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9468 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9469 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9470 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9471 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9472 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9473 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9474 libkrossui4 libmailtools-perl libmime-tools-perl
9475 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9476 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9477 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9478 lirc luatex marble networkstatus noatun-plugins
9479 openoffice.org-writer2latex palapeli palapeli-data parley
9480 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9481 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9482 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9483 ttf-sazanami-gothic
9484 &lt;/p&gt;&lt;/blockquote&gt;
9485
9486 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9487
9488 &lt;blockquote&gt;&lt;p&gt;
9489 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9490 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9491 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9492 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9493 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9494 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9495 kitchensync kiten kjumpingcube klatin klettres klickety klines
9496 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9497 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9498 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9499 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9500 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9501 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9502 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9503 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9504 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9505 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9506 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9507 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9508 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9509 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9510 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9511 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9512 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9513 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9514 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9515 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9516 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9517 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9518 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9519 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9520 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9521 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9522 &lt;/p&gt;&lt;/blockquote&gt;
9523
9524 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9525
9526 &lt;blockquote&gt;&lt;p&gt;
9527 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9528 kdeartwork kdebase kdebase-apps kdebase-workspace
9529 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9530 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9531 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9532 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9533 xscreensaver-screensaver-bsod
9534 &lt;/p&gt;&lt;/blockquote&gt;
9535
9536 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9537
9538 &lt;blockquote&gt;&lt;p&gt;
9539 kdebase-bin konq-plugins konqueror
9540 &lt;/p&gt;&lt;/blockquote&gt;
9541 </description>
9542 </item>
9543
9544 <item>
9545 <title>Gnash buildbot slave and Debian kfreebsd</title>
9546 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9547 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9548 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9549 <description>&lt;p&gt;Answering
9550 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9551 call from the Gnash project&lt;/a&gt; for
9552 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9553 current source, I have set up a virtual KVM machine on the Debian
9554 Edu/Skolelinux virtualization host to test the git source on
9555 Debian/Squeeze. I hope this can help the developers in getting new
9556 releases out more often.&lt;/p&gt;
9557
9558 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9559 I have considered setting up a &lt;a
9560 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9561 machine as well. I have also considered using the kfreebsd
9562 architecture in Debian as a file server in NUUG to get access to the 5
9563 TB zfs volume we currently use to store DV video. Because of this, I
9564 finally got around to do a test installation of Debian/Squeeze with
9565 kfreebsd. Installation went fairly smooth, thought I noticed some
9566 visual glitches in the cdebconf dialogs (black cursor left on the
9567 screen at random locations). Have not gotten very far with the
9568 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9569 fatal problem. Have to spend some more time on it to see if it is
9570 useful as a file server for NUUG. Will try to find time to set up a
9571 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9572 </description>
9573 </item>
9574
9575 <item>
9576 <title>Debian in 3D</title>
9577 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9579 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9580 <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;
9581
9582 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9583 3D linked in from
9584 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9585 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9586 </description>
9587 </item>
9588
9589 <item>
9590 <title>Software updates 2010-10-24</title>
9591 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9592 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9593 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9594 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9595
9596 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9597 raise money for the project is going well. The lower limit of 10
9598 signers was reached in 24 hours, and so far 13 people have signed it.
9599 More signers and more funding is most welcome, and I am really curious
9600 how far we can get before the time limit of December 24 is reached.
9601 :)&lt;/p&gt;
9602
9603 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9604 about what appear to be a great code coverage tool capable of
9605 generating code coverage stats without any changes to the source code.
9606 It is called
9607 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9608 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9609 It is missing in Debian, but the git source built just fine in Squeeze
9610 after I installed libelf-dev, libdwarf-dev, pkg-config and
9611 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9612 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9613
9614 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9615 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9616 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9617 alpha test release of the Squeeze based Debian Edu /
9618 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9619 release. Give it a try if you need a complete linux solution for your
9620 school, including central infrastructure server, workstations, thin
9621 client servers and diskless workstations. A nice touch added
9622 yesterday is RDP support on the thin client servers, for windows
9623 clients to get a Linux desktop on request.&lt;/p&gt;
9624 </description>
9625 </item>
9626
9627 <item>
9628 <title>Some notes on Flash in Debian and Debian Edu</title>
9629 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9631 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9632 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9633 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9634 second most popular used package that is missing in Debian. The sixth
9635 most popular is flashplayer-mozilla. This is a clear indication that
9636 working flash is important for Debian users. Around 10 percent of the
9637 users submitting data to popcon.debian.org have this package
9638 installed.&lt;/p&gt;
9639
9640 &lt;p&gt;In the report written by Lars Risan in August 2008
9641&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
9642 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9643 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9644 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9645 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9646 web sites require Flash to work, and lacking working Flash support in
9647 the web browser and the problems with installing it was perceived as a
9648 good reason to stay with Windows.&lt;/p&gt;
9649
9650 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9651 said to be the retarded cousin that did not really understand
9652 everything you told him but could work fairly well. This was a
9653 comment regarding the problems Linux have with proprietary formats and
9654 non-standard web pages, and is sad because it exposes a fairly common
9655 understanding of whose fault it is if web pages that only work in for
9656 example Internet Explorer 6 fail to work on Firefox, and funny because
9657 it explain very well how annoying it is for users when Linux
9658 distributions do not work with the documents they receive or the web
9659 pages they want to visit.&lt;/p&gt;
9660
9661 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9662 and Debian Edu to have a well working Flash implementation in the
9663 distribution, to get at least popular sites as Youtube and Google
9664 Video to working out of the box. For Squeeze, Debian have the chance
9665 to include the latest version of Gnash that will make this happen, as
9666 the new release 0.8.8 was published a few weeks ago and is resting in
9667 unstable. The new version work with more sites that version 0.8.7.
9668 The Gnash maintainers have asked for a freeze exception, but the
9669 release team have not had time to reply to it yet. I hope they agree
9670 with me that Flash is important for the Debian desktop users, and thus
9671 accept the new package into Squeeze.&lt;/p&gt;
9672 </description>
9673 </item>
9674
9675 <item>
9676 <title>Circular package dependencies harms apt recovery</title>
9677 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9678 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9679 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9680 <description>&lt;p&gt;I discovered this while doing
9681 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9682 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9683 in Debian still got circular dependencies, and it is often claimed
9684 that apt and aptitude should be able to handle this just fine, but
9685 some times these dependency loops causes apt to fail.&lt;/p&gt;
9686
9687 &lt;p&gt;An example is from todays
9688 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9689 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9690 causes perl-modules to fail to upgrade. The cause is simple. If a
9691 package fail to unpack, then only part of packages with the circular
9692 dependency might end up being unpacked when unpacking aborts, and the
9693 ones already unpacked will fail to configure in the recovery phase
9694 because its dependencies are unavailable.&lt;/p&gt;
9695
9696 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9697
9698 &lt;blockquote&gt;&lt;pre&gt;
9699 dpkg: dependency problems prevent configuration of perl-modules:
9700 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9701 Version of perl on system is 5.10.0-19lenny2.
9702 dpkg: error processing perl-modules (--configure):
9703 dependency problems - leaving unconfigured
9704 &lt;/pre&gt;&lt;/blockquote&gt;
9705
9706 &lt;p&gt;The perl/perl-modules circular dependency is already
9707 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9708 hopefully be solved as soon as possible, but it is not the only one,
9709 and each one of these loops in the dependency tree can cause similar
9710 failures. Of course, they only occur when there are bugs in other
9711 packages causing the unpacking to fail, but it is rather nasty when
9712 the failure of one package causes the problem to become worse because
9713 of dependency loops.&lt;/p&gt;
9714
9715 &lt;p&gt;Thanks to
9716 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9717 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9718 dependencies
9719 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9720 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9721
9722 &lt;p&gt;Todays testing also exposed a bug in
9723 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9724 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9725 apt-get and aptitude, the latter possibly caused by some circular
9726 dependency. Reported both to BTS to try to get someone to look at
9727 it.&lt;/p&gt;
9728 </description>
9729 </item>
9730
9731 <item>
9732 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9733 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9734 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9735 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9736 <description>&lt;p&gt;This is a
9737 &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;
9738 on my
9739 &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
9740 work&lt;/a&gt; on
9741 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9742 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9743
9744 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9745 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9746 and dhcp3-server-ldap in Debian use the LDAP server. The two
9747 implementations are quite different in how they use LDAP.&lt;/p&gt;
9748
9749 To get this information, I started slapd with debugging enabled and
9750 dumped the debug output to a file to get the LDAP searches performed
9751 on a Debian Edu main-server. Here is a summary.
9752
9753 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9754
9755 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9756 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9757 the web.
9758
9759 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9760 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9761 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9762 reverse entries are in two different subtrees in LDAP with a structure
9763 based on the DNS names, as in tjener.intern and
9764 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9765
9766 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9767 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9768 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9769 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9770 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9771 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9772 forward entries, it is looking for attributes named dnsttl, arecord,
9773 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9774 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9775 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9776 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9777 spfrecord and modifytimestamp. For reverse entries it is looking for
9778 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9779 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9780 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9781 ldapsearch commands could look like this:&lt;/p&gt;
9782
9783 &lt;blockquote&gt;&lt;pre&gt;
9784 ldapsearch -h ldap \
9785 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9786 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9787 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9788 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9789 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9790 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9791
9792 ldapsearch -h ldap \
9793 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9794 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9795 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9796 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9797 srvrecord naptrrecord modifytimestamp
9798 &lt;/pre&gt;&lt;/blockquote&gt;
9799
9800 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9801 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9802 example LDAP objects used there. In addition to these objects, the
9803 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9804 also exist.&lt;/p&gt;
9805
9806 &lt;blockquote&gt;&lt;pre&gt;
9807 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9808 objectclass: top
9809 objectclass: dnsdomain
9810 objectclass: domainrelatedobject
9811 dc: tjener
9812 arecord: 10.0.2.2
9813 associateddomain: tjener.intern
9814
9815 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9816 objectclass: top
9817 objectclass: dnsdomain2
9818 objectclass: domainrelatedobject
9819 dc: 2
9820 ptrrecord: tjener.intern
9821 associateddomain: 2.2.0.10.in-addr.arpa
9822 &lt;/pre&gt;&lt;/blockquote&gt;
9823
9824 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9825 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9826 same base as in the tree mode for a object with filter
9827 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9828 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9829 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9830 naptrrecord and modifytimestamp. For reverse entires it also do a
9831 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9832 and the requested attributes are associateddomain, dnsttl and
9833 modifytimestamp. In short, in strict mode the objects with ptrrecord
9834 go away, and the arecord attribute in the forward object is used
9835 instead.&lt;/p&gt;
9836
9837 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
9838 like this:&lt;/p&gt;
9839
9840 &lt;blockquote&gt;&lt;pre&gt;
9841 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9842 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9843 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9844 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9845 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9846 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9847
9848 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9849 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
9850 &lt;/pre&gt;&lt;/blockquote&gt;
9851
9852 &lt;p&gt;In addition to the forward and reverse searches , there is also a
9853 search for SOA records, which behave similar to the forward and
9854 reverse lookups.&lt;/p&gt;
9855
9856 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
9857 specify any objectclass names, and instead look for the attributes it
9858 need to generate a DNS reply. This make it able to work with any
9859 objectclass that provide the needed attributes.&lt;/p&gt;
9860
9861 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
9862 dnsdomain2 schemas. The latter is used for reverse entries like
9863 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
9864
9865 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
9866 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9867 attributes) and domainrelatedobject (for associatedDomain). The use
9868 of structural object classes make it impossible to combine these
9869 classes with the object classes used by DHCP.&lt;/p&gt;
9870
9871 &lt;p&gt;There are other schemas that could be used too, for example the
9872 dnszone structural object class used by Gosa and bind-sdb for the DNS
9873 attributes combined with the domainrelatedobject object class, but in
9874 this case some unused attributes would have to be included as well
9875 (zonename and relativedomainname).&lt;/p&gt;
9876
9877 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
9878 mode and not use any of the existing objectclasses (dnsdomain,
9879 dnsdomain2 and dnszone) when one want to combine the DNS information
9880 with DHCP information, and instead create a auxiliary object class
9881 defined something like this (using the attributes defined for
9882 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
9883
9884 &lt;blockquote&gt;&lt;pre&gt;
9885 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
9886 SUP top
9887 AUXILIARY
9888 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9889 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9890 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9891 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9892 A6Record $ DNAMERecord
9893 ))
9894 &lt;/pre&gt;&lt;/blockquote&gt;
9895
9896 &lt;p&gt;This will allow any object to become a DNS entry when combined with
9897 the domainrelatedobject object class, and allow any entity to include
9898 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
9899 developers asking for their view on this schema and if they are
9900 interested in providing such schema with PowerDNS, and I hope my
9901 message will be accepted into their mailing list soon.&lt;/p&gt;
9902
9903 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
9904
9905 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
9906 the object attributes, and then uses the attributes it want. This
9907 make it harder to figure out exactly what attributes are used, but
9908 thanks to the working example in Debian Edu I can at least get an idea
9909 what is needed without having to read the source code.&lt;/p&gt;
9910
9911 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
9912 search filter to use to locate the correct dhcpServer entity is
9913 stored. These are the relevant entries from
9914 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
9915
9916 &lt;blockquote&gt;&lt;pre&gt;
9917 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
9918 ldap-dhcp-server-cn &quot;dhcp&quot;;
9919 &lt;/pre&gt;&lt;/blockquote&gt;
9920
9921 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
9922 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
9923 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
9924 search result is this entry:&lt;/p&gt;
9925
9926 &lt;blockquote&gt;&lt;pre&gt;
9927 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9928 cn: dhcp
9929 objectClass: top
9930 objectClass: dhcpServer
9931 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9932 &lt;/pre&gt;&lt;/blockquote&gt;
9933
9934 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
9935 subtree with DHCP configuration. The DHCP configuration subtree base
9936 is located using a base scope search with base &quot;cn=DHCP
9937 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
9938 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
9939 The search result is this entry:&lt;/p&gt;
9940
9941 &lt;blockquote&gt;&lt;pre&gt;
9942 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9943 cn: DHCP Config
9944 objectClass: top
9945 objectClass: dhcpService
9946 objectClass: dhcpOptions
9947 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9948 dhcpStatements: ddns-update-style none
9949 dhcpStatements: authoritative
9950 dhcpOption: smtp-server code 69 = array of ip-address
9951 dhcpOption: www-server code 72 = array of ip-address
9952 dhcpOption: wpad-url code 252 = text
9953 &lt;/pre&gt;&lt;/blockquote&gt;
9954
9955 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
9956 all the DHCP configuration is loaded, it is ready to receive requests.
9957 The subtree in Debian Edu contain objects with object classes
9958 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9959 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9960 and information about netmasks, dynamic range etc. Leaving out the
9961 details here because it is not relevant for the focus of my
9962 investigation, which is to see if it is possible to merge dns and dhcp
9963 related computer objects.&lt;/p&gt;
9964
9965 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
9966 of the client (00:00:00:00:00:00 in this example), using a subtree
9967 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
9968 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9969 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
9970 like:&lt;/p&gt;
9971
9972 &lt;blockquote&gt;&lt;pre&gt;
9973 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9974 cn: hostname
9975 objectClass: top
9976 objectClass: dhcpHost
9977 dhcpHWAddress: ethernet 00:00:00:00:00:00
9978 dhcpStatements: fixed-address hostname
9979 &lt;/pre&gt;&lt;/blockquote&gt;
9980
9981 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
9982 The object classes need to have fixed names, and the configuration
9983 need to be stored in a fairly specific LDAP structure. On the
9984 positive side, the invidiual dhcpHost entires can be anywhere without
9985 the DN pointed to by the dhcpServer entries. The latter should make
9986 it possible to group all host entries in a subtree next to the
9987 configuration entries, and this subtree can also be shared with the
9988 DNS server if the schema proposed above is combined with the dhcpHost
9989 structural object class.
9990
9991 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
9992
9993 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
9994 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
9995 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
9996 allowing DNS objects to be stored anywhere under the base cn specified
9997 in the configuration.&lt;/p&gt;
9998
9999 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
10000 regarding which LDAP schemas to use and which LDAP structure to use.
10001 I guess one could implement ones own schema, as long as the
10002 objectclasses and attributes have the names used, but this do not
10003 really help when the DHCP subtree need to have a fairly fixed
10004 structure.&lt;/p&gt;
10005
10006 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
10007 this might work for Debian Edu:&lt;/p&gt;
10008
10009 &lt;blockquote&gt;&lt;pre&gt;
10010 ou=services
10011 cn=machine-info (dhcpService) - dhcpServiceDN points here
10012 cn=dhcp (dhcpServer)
10013 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10014 cn=10.0.2.0 (dhcpSubnet)
10015 cn=group1 (dhcpGroup/dhcpOptions)
10016 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10017 cn=192.168.0.0 (dhcpSubnet)
10018 cn=group1 (dhcpGroup/dhcpOptions)
10019 ou=machines - PowerDNS base points here
10020 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10021 &lt;/pre&gt;&lt;/blockquote&gt;
10022
10023 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
10024 entries to be in the dhcpGroup subtrees, the entries can be stored
10025 there instead of a common machines subtree, and the PowerDNS base
10026 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
10027
10028 &lt;p&gt;The combined object under the machines subtree would look something
10029 like this:&lt;/p&gt;
10030
10031 &lt;blockquote&gt;&lt;pre&gt;
10032 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10033 dc: hostname
10034 objectClass: top
10035 objectClass: dhcpHost
10036 objectclass: domainrelatedobject
10037 objectclass: dnsDomainAux
10038 associateddomain: hostname.intern
10039 arecord: 10.11.12.13
10040 dhcpHWAddress: ethernet 00:00:00:00:00:00
10041 dhcpStatements: fixed-address hostname.intern
10042 &lt;/pre&gt;&lt;/blockquote&gt;
10043
10044 &lt;/p&gt;One could even add the LTSP configuration associated with a given
10045 machine, as long as the required attributes are available in a
10046 auxiliary object class.&lt;/p&gt;
10047 </description>
10048 </item>
10049
10050 <item>
10051 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
10052 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
10053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
10054 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
10055 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
10056 DHCP services in Debian Edu to use the same LDAP objects for a given
10057 computer, to avoid the possibility of having a inconsistent state for
10058 a computer in LDAP (as in DHCP but no DNS entry or the other way
10059 around) and make it easier to add computers to LDAP.&lt;/p&gt;
10060
10061 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
10062 information finally found a solution that seem to work.&lt;/p&gt;
10063
10064 &lt;p&gt;The old setup required three LDAP objects for a given computer.
10065 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10066 we switch powerdns to use its strict LDAP method (ldap-method=strict
10067 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10068 merged into one while making it impossible to transfer the reverse map
10069 to a slave DNS server.&lt;/p&gt;
10070
10071 &lt;p&gt;If we also replace the object class used to get the DNS related
10072 attributes to one allowing these attributes to be combined with the
10073 dhcphost object class, we can merge the DNS and DHCP entries into one.
10074 I&#39;ve written such object class in the dnsdomainaux.schema file (need
10075 proper OIDs, but that is a minor issue), and tested the setup. It
10076 seem to work.&lt;/p&gt;
10077
10078 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
10079 for both DNS and DHCP, and even the LTSP configuration I suggested in
10080 an earlier email. The combined LDAP object will look something like
10081 this:&lt;/p&gt;
10082
10083 &lt;blockquote&gt;&lt;pre&gt;
10084 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10085 cn: hostname
10086 objectClass: dhcphost
10087 objectclass: domainrelatedobject
10088 objectclass: dnsdomainaux
10089 associateddomain: hostname.intern
10090 arecord: 10.11.12.13
10091 dhcphwaddress: ethernet 00:00:00:00:00:00
10092 dhcpstatements: fixed-address hostname
10093 ldapconfigsound: Y
10094 &lt;/pre&gt;&lt;/blockquote&gt;
10095
10096 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
10097 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10098 before asking DNS to resolve the fixed-adddress. LTSP will use
10099 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
10100
10101 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
10102 dhcphost in a different location, to allow us to put the objects
10103 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
10104 that. If I can&#39;t figure out a way to do that, we can still get rid of
10105 the hosts subtree and move all its content into the DHCP Config tree
10106 (which probably should be renamed to be more related to the new
10107 content. I suspect cn=dnsdhcp,ou=services or something like that
10108 might be a good place to put it.&lt;/p&gt;
10109
10110 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10111 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10112 </description>
10113 </item>
10114
10115 <item>
10116 <title>Idea for storing LTSP configuration in LDAP</title>
10117 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
10118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
10119 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
10120 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
10121 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10122 clients, and that this can be used to fetch configuration from LDAP if
10123 Debian Edu choose to store configuration there.&lt;/p&gt;
10124
10125 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
10126 to get configuration from LDAP. The idea is to look up the MAC
10127 address of the client in LDAP, and look for attributes on the form
10128 ltspconfigsetting=value, and use this to export SETTING=value to the
10129 LTSP clients.&lt;/p&gt;
10130
10131 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
10132 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
10133 allowing us to store all information about a computer in one place.&lt;/p&gt;
10134
10135 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
10136 this approach. A real LDAP schema for the ltspClientAux objectclass
10137 need to be written. Comments, suggestions, etc?&lt;/p&gt;
10138
10139 &lt;blockquote&gt;&lt;pre&gt;
10140 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10141 #
10142 # Fetch LTSP client settings from LDAP based on MAC address
10143 #
10144 # Uses ethernet address as stored in the dhcpHost objectclass using
10145 # the dhcpHWAddress attribute or ethernet address stored in the
10146 # ieee802Device objectclass with the macAddress attribute.
10147 #
10148 # This module is written to be schema agnostic, and only depend on the
10149 # existence of attribute names.
10150 #
10151 # The LTSP configuration variables are saved directly using a
10152 # ltspConfig prefix and uppercasing the rest of the attribute name.
10153 # To set the SERVER variable, set the ltspConfigServer attribute.
10154 #
10155 # Some LDAP schema should be created with all the relevant
10156 # configuration settings. Something like this should work:
10157 #
10158 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
10159 # SUP top
10160 # AUXILIARY
10161 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10162
10163 LDAPSERVER=$(debian-edu-ldapserver)
10164 if [ &quot;$LDAPSERVER&quot; ] ; then
10165 LDAPBASE=$(debian-edu-ldapserver -b)
10166 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
10167 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
10168 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
10169 grep &#39;^ltspConfig&#39; | while read attr value ; do
10170 # Remove prefix and convert to upper case
10171 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
10172 # bass value on to clients
10173 eval &quot;$attr=$value; export $attr&quot;
10174 done
10175 done
10176 fi
10177 &lt;/pre&gt;&lt;/blockquote&gt;
10178
10179 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
10180 the while block might end up in a subshell causing the variables set
10181 there to not show up in ltsp-config, but if that is the case I am sure
10182 the code can be restructured to make sure the variables are passed on.
10183 I expect that can be solved with some testing. :)&lt;/p&gt;
10184
10185 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10186 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10187
10188 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
10189 configuration in LDAP that was created around year 2000 by
10190 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
10191 Xperience, Inc., 2000&lt;/a&gt;. I found its
10192 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
10193 personal home page over at redhat.com.&lt;/p&gt;
10194 </description>
10195 </item>
10196
10197 <item>
10198 <title>jXplorer, a very nice LDAP GUI</title>
10199 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
10200 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
10201 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
10202 <description>&lt;p&gt;Since
10203 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
10204 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
10205 LDAP GUI that is even better than luma. The java application
10206 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
10207 moving LDAP objects and subtrees using drag-and-drop, and can
10208 authenticate using Kerberos. I have only tested the Kerberos
10209 authentication, but do not have a LDAP setup allowing me to rewrite
10210 LDAP with my test user yet. It is
10211 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
10212 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
10213 have with it is how it handle errors. If something go wrong, its
10214 non-intuitive behaviour require me to go through some query work list
10215 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
10216 </description>
10217 </item>
10218
10219 <item>
10220 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
10221 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
10222 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
10223 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
10224 <description>&lt;p&gt;Here is a short update on my &lt;a
10225 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
10226 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
10227 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
10228 not reporting the status for KDE, because the upgrade crashes when
10229 aptitude try because of missing conflicts
10230 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
10231 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
10232
10233 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
10234 complete list of the installed packages. Based on this I see these
10235 differences when I did a test run today. As usual, I do not really
10236 know what the correct set of packages would be, but thought it best to
10237 publish the difference.&lt;/p&gt;
10238
10239 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10240
10241 &lt;blockquote&gt;&lt;p&gt;
10242 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
10243 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
10244 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10245 libgtksourceview-common libpt-1.10.10-plugins-alsa
10246 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10247 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10248 python-4suite-xml python-eggtrayicon python-gtkhtml2
10249 python-gtkmozembed svgalibg1 xserver-xephyr zip
10250 &lt;/p&gt;&lt;/blockquote&gt;
10251
10252 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10253
10254 &lt;blockquote&gt;&lt;p&gt;
10255 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10256 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10257 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
10258 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
10259 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
10260 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
10261 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10262 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10263 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10264 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
10265 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
10266 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
10267 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10268 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
10269 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10270 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
10271 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
10272 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10273 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10274 mysql-common swfdec-gnome totem-gstreamer wodim
10275 &lt;/p&gt;&lt;/blockquote&gt;
10276
10277 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10278
10279 &lt;blockquote&gt;&lt;p&gt;
10280 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10281 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10282 xserver-xorg-input-all xserver-xorg-input-evdev
10283 xserver-xorg-input-kbd xserver-xorg-input-mouse
10284 xserver-xorg-input-synaptics xserver-xorg-video-all
10285 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10286 xserver-xorg-video-chips xserver-xorg-video-cirrus
10287 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10288 xserver-xorg-video-glint xserver-xorg-video-i128
10289 xserver-xorg-video-i740 xserver-xorg-video-mach64
10290 xserver-xorg-video-mga xserver-xorg-video-neomagic
10291 xserver-xorg-video-nouveau xserver-xorg-video-nv
10292 xserver-xorg-video-r128 xserver-xorg-video-radeon
10293 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10294 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10295 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10296 xserver-xorg-video-sis xserver-xorg-video-sisusb
10297 xserver-xorg-video-tdfx xserver-xorg-video-tga
10298 xserver-xorg-video-trident xserver-xorg-video-tseng
10299 xserver-xorg-video-vesa xserver-xorg-video-vmware
10300 xserver-xorg-video-voodoo
10301 &lt;/p&gt;&lt;/blockquote&gt;
10302
10303 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10304
10305 &lt;blockquote&gt;&lt;p&gt;
10306 deskbar-applet xserver-xorg xserver-xorg-core
10307 xserver-xorg-input-wacom xserver-xorg-video-intel
10308 xserver-xorg-video-openchrome
10309 &lt;/p&gt;&lt;/blockquote&gt;
10310
10311 &lt;p&gt;I was told on IRC that the xorg-xserver package was
10312 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
10313 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
10314 No idea when it hits Squeeze, but when it does I hope it will reduce
10315 the difference somewhat.
10316 </description>
10317 </item>
10318
10319 <item>
10320 <title>LUMA, a very nice LDAP GUI</title>
10321 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
10322 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
10323 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
10324 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
10325 directory in Debian Edu, and in the process I started to miss a GUI
10326 tool to browse the LDAP tree. The only one I was able to find in
10327 Debian/Squeeze and Lenny is
10328 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
10329 be a great tool to get a overview of the current LDAP directory
10330 populated by default in Skolelinux. Thanks to it, I have been able to
10331 find empty and obsolete subtrees, misplaced objects and duplicate
10332 objects. It will be installed by default in Debian/Squeeze. If you
10333 are working with LDAP, give it a go. :)&lt;/p&gt;
10334
10335 &lt;p&gt;I did notice one problem with it I have not had time to report to
10336 the BTS yet. There is no .desktop file in the package, so the tool do
10337 not show up in the Gnome and KDE menus, but only deep down in in the
10338 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10339 released.&lt;/p&gt;
10340
10341 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10342 like to move objects and remove subtrees directly in the GUI, but have
10343 not found a way to do that with LUMA yet. So in the mean time, I use
10344 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10345
10346 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10347 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10348
10349 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10350 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10351 useful GUI alternative. It seem like a good tool, but is unmaintained
10352 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10353 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10354 </description>
10355 </item>
10356
10357 <item>
10358 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10359 <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>
10360 <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>
10361 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10362 <description>&lt;p&gt;A while back, I
10363 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10364 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10365 for storing DNS and DHCP information in LDAP to combine the two sets
10366 of information into one LDAP object representing a computer.&lt;/p&gt;
10367
10368 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10369 the dhcpHost object class auxiliary, to allow it to be combined with
10370 the dNSDomain object class, and thus forming one object for one
10371 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10372
10373 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10374 without also changing the assigned number for the object class, and I
10375 do not know enough about LDAP schema design to do that properly for
10376 Debian Edu.&lt;/p&gt;
10377
10378 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10379 the
10380 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10381 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10382 available today from IETF.&lt;/p&gt;
10383
10384 &lt;pre&gt;
10385 --- dhcp.schema (revision 65192)
10386 +++ dhcp.schema (working copy)
10387 @@ -376,7 +376,7 @@
10388 objectclass ( 2.16.840.1.113719.1.203.6.6
10389 NAME &#39;dhcpHost&#39;
10390 DESC &#39;This represents information about a particular client&#39;
10391 - SUP top
10392 + SUP top AUXILIARY
10393 MUST cn
10394 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10395 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10396 &lt;/pre&gt;
10397
10398 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10399 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10400 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10401
10402 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10403 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10404 </description>
10405 </item>
10406
10407 <item>
10408 <title>Calling tasksel like the installer, while still getting useful output</title>
10409 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10410 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10411 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10412 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10413 installs packages during the normal debian-installer run. Until now,
10414 I have ended up letting tasksel do the work, with the annoying problem
10415 of not getting any feedback at all when something fails (like a
10416 conffile question from dpkg or a download that fails), using code like
10417 this:
10418
10419 &lt;blockquote&gt;&lt;pre&gt;
10420 export DEBIAN_FRONTEND=noninteractive
10421 tasksel --new-install
10422 &lt;/pre&gt;&lt;/blockquote&gt;
10423
10424 This would invoke tasksel, let its automatic task selection pick the
10425 tasks to install, and continue to install the requested tasks without
10426 any output what so ever.
10427
10428 Recently I revisited this problem while working on the automatic
10429 package upgrade testing, because tasksel would some times hang without
10430 any useful feedback, and I want to see what is going on when it
10431 happen. Then it occured to me, I can parse the output from tasksel
10432 when asked to run in test mode, and use that aptitude command line
10433 printed by tasksel then to simulate the tasksel run. I ended up using
10434 code like this:
10435
10436 &lt;blockquote&gt;&lt;pre&gt;
10437 export DEBIAN_FRONTEND=noninteractive
10438 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10439 $cmd
10440 &lt;/pre&gt;&lt;/blockquote&gt;
10441
10442 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10443 --without-recommends -o APT::Install-Recommends=no -y install
10444 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10445 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10446 laptop task and all packages with priority standard , required and
10447 important, just like tasksel would have done it during
10448 installation.&lt;/p&gt;
10449
10450 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10451 install packages without using debconf-apt-progress, for use cases
10452 like this.&lt;/p&gt;
10453 </description>
10454 </item>
10455
10456 <item>
10457 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10458 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10460 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10461 <description>&lt;p&gt;My
10462 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10463 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10464 finally made the upgrade logs available from
10465 &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;.
10466 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10467 apt and aptitude, and found their differences interesting. This time
10468 I will only focus on their removal plans.&lt;/p&gt;
10469
10470 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10471 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10472 surprising part is that it want to remove xorg and all
10473 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10474 sure why. When asking aptitude to do the same, it want to remove 129
10475 packages, but most of them are library packages I suspect are no
10476 longer needed. Both of them want to remove bluetooth packages, which
10477 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10478
10479 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10480 which seem like a bad idea and xorg the same way as with Gnome. Asking
10481 aptitude for the same, it wants to remove 192 packages, none which are
10482 too surprising.&lt;/p&gt;
10483
10484 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10485 and avoided, and perhaps others as well. Here are the complete list
10486 of planned removals. The complete logs is available from the URL
10487 above. Note if you want to repeat these tests, that the upgrade test
10488 for kde+apt-get hung in the tasksel setup because of dpkg asking
10489 conffile questions. No idea why. I worked around it by using
10490 &#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
10491 continue.&lt;/p&gt;
10492
10493 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10494 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10495 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10496 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10497 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10498 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10499 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10500 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10501 xserver-xorg-input-kbd xserver-xorg-input-mouse
10502 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10503 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10504 xserver-xorg-video-ati xserver-xorg-video-chips
10505 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10506 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10507 xserver-xorg-video-glint xserver-xorg-video-i128
10508 xserver-xorg-video-i740 xserver-xorg-video-imstt
10509 xserver-xorg-video-intel xserver-xorg-video-mach64
10510 xserver-xorg-video-mga xserver-xorg-video-neomagic
10511 xserver-xorg-video-nsc xserver-xorg-video-nv
10512 xserver-xorg-video-openchrome xserver-xorg-video-r128
10513 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10514 xserver-xorg-video-rendition xserver-xorg-video-s3
10515 xserver-xorg-video-s3virge xserver-xorg-video-savage
10516 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10517 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10518 xserver-xorg-video-tga xserver-xorg-video-trident
10519 xserver-xorg-video-tseng xserver-xorg-video-v4l
10520 xserver-xorg-video-vesa xserver-xorg-video-vga
10521 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10522 xulrunner-1.9-gnome-support&lt;/p&gt;
10523
10524 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10525
10526 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10527 djvulibre-desktop finger gnome-app-install gnome-mount
10528 gnome-network-admin gnome-spell gnome-vfs-obexftp
10529 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10530 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10531 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10532 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10533 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10534 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10535 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10536 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10537 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10538 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10539 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10540 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10541 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10542 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10543 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10544 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10545 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10546 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10547 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10548 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10549 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10550 openoffice.org-writer2latex openssl-blacklist p7zip
10551 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10552 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10553 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10554 swfdec-mozilla totem-gstreamer update-manager wodim
10555 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10556 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10557 zip&lt;/p&gt;
10558
10559 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10560
10561 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10562 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10563 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10564 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10565 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10566 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10567 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10568 xserver-xorg-input-kbd xserver-xorg-input-mouse
10569 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10570 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10571 xserver-xorg-video-ati xserver-xorg-video-chips
10572 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10573 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10574 xserver-xorg-video-glint xserver-xorg-video-i128
10575 xserver-xorg-video-i740 xserver-xorg-video-imstt
10576 xserver-xorg-video-intel xserver-xorg-video-mach64
10577 xserver-xorg-video-mga xserver-xorg-video-neomagic
10578 xserver-xorg-video-nsc xserver-xorg-video-nv
10579 xserver-xorg-video-openchrome xserver-xorg-video-r128
10580 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10581 xserver-xorg-video-rendition xserver-xorg-video-s3
10582 xserver-xorg-video-s3virge xserver-xorg-video-savage
10583 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10584 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10585 xserver-xorg-video-tga xserver-xorg-video-trident
10586 xserver-xorg-video-tseng xserver-xorg-video-v4l
10587 xserver-xorg-video-vesa xserver-xorg-video-vga
10588 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10589
10590 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10591 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10592 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10593 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10594 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10595 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10596 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10597 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10598 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10599 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10600 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10601 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10602 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10603 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10604 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10605 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10606 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10607 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10608 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10609 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10610 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10611 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10612 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10613 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10614 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10615 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10616 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10617 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10618 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10619 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10620 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10621 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10622 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10623 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10624 texlive-common texlive-doc-base texlive-fonts-recommended
10625 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10626 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10627 xulrunner-1.9&lt;/p&gt;
10628
10629 </description>
10630 </item>
10631
10632 <item>
10633 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10634 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10636 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10637 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10638 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10639 have been discovered and reported in the process
10640 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10641 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10642 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10643 kdebase-workspace-data), and to get a more regular testing going on, I
10644 am working on a script to automate the test.&lt;/p&gt;
10645
10646 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10647 Gnome or KDE desktop installation inside the chroot before upgrading
10648 it. To ensure no services are started in the chroot, a policy-rc.d
10649 script is inserted. To make sure tasksel believe it is to install a
10650 desktop on a laptop, the tasksel tests are replaced in the chroot
10651 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10652
10653 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10654 currently always fail because udev refuses to upgrade with the kernel
10655 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10656 is created. The bug report
10657 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10658 this problem do not trigger in a chroot, but I touch the file anyway
10659 to make sure the upgrade go well. Testing on virtual and real
10660 hardware have failed me because of udev so far, and creating this file
10661 do the trick in such settings anyway. This is a
10662 &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
10663 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10664 maintainer because he lack the resources to rewrite udev to keep
10665 working with old kernels or something like that. I really wish the
10666 udev upstream would keep udev backwards compatible, to avoid such
10667 upgrade problem, but given that they fail to do so, I guess
10668 documenting the way out of this mess is the best option we got for
10669 Debian Squeeze.&lt;/p&gt;
10670
10671 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10672 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10673 trick:&lt;/p&gt;
10674
10675 &lt;blockquote&gt;&lt;pre&gt;
10676 #!/bin/sh
10677 set -ex
10678
10679 if [ &quot;$1&quot; ] ; then
10680 desktop=$1
10681 else
10682 desktop=gnome
10683 fi
10684
10685 from=lenny
10686 to=squeeze
10687
10688 exec &amp;lt; /dev/null
10689 unset LANG
10690 mirror=http://ftp.skolelinux.org/debian
10691 tmpdir=chroot-$from-upgrade-$to-$desktop
10692 fuser -mv .
10693 debootstrap $from $tmpdir $mirror
10694 chroot $tmpdir aptitude update
10695 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10696 #!/bin/sh
10697 exit 101
10698 EOF
10699 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10700 exit_cleanup() {
10701 umount $tmpdir/proc
10702 }
10703 mount -t proc proc $tmpdir/proc
10704 # Make sure proc is unmounted also on failure
10705 trap exit_cleanup EXIT INT
10706
10707 chroot $tmpdir aptitude -y install debconf-utils
10708
10709 # Make sure tasksel autoselection trigger. It need the test scripts
10710 # to return the correct answers.
10711 echo tasksel tasksel/desktop multiselect $desktop | \
10712 chroot $tmpdir debconf-set-selections
10713
10714 # Include the desktop and laptop task
10715 for test in desktop laptop ; do
10716 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10717 #!/bin/sh
10718 exit 2
10719 EOF
10720 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10721 done
10722
10723 DEBIAN_FRONTEND=noninteractive
10724 DEBIAN_PRIORITY=critical
10725 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10726 chroot $tmpdir tasksel --new-install
10727
10728 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10729 chroot $tmpdir aptitude update
10730 touch $tmpdir/etc/udev/kernel-upgrade
10731 chroot $tmpdir aptitude -y dist-upgrade
10732 fuser -mv
10733 &lt;/pre&gt;&lt;/blockquote&gt;
10734
10735 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10736 with aptitude, but I have not had time to look at how they behave
10737 differently so far. I hope to get a cron job running to do the test
10738 regularly and post the result on the web. The Gnome upgrade currently
10739 work, while the KDE upgrade fail because of the bug in
10740 kdebase-workspace-data&lt;/p&gt;
10741
10742 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10743 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10744 post, so I will refrain from trying. I can report that for Gnome,
10745 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10746 remove and 1 not upgraded and 1024MB need to be downloaded while for
10747 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10748 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10749
10750 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10751 is able to migrate to dependency based boot sequencing and parallel
10752 booting without a hitch. Was unsure if there were still bugs with
10753 packages failing to clean up their obsolete init.d script during
10754 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10755 packages.&lt;/p&gt;
10756 </description>
10757 </item>
10758
10759 <item>
10760 <title>Upstart or sysvinit - as init.d scripts see it</title>
10761 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10762 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10763 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10764 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10765 scripts to migrate (some of) their operations to upstart job while
10766 keeping the init.d for hurd and kfreebsd. The packages with such
10767 needs will need a way to get their init.d scripts to behave
10768 differently when used with sysvinit and with upstart. Because of
10769 this, I had a look at the environment variables set when a init.d
10770 script is running under upstart, and when it is not.&lt;/p&gt;
10771
10772 &lt;p&gt;With upstart, I notice these environment variables are set when a
10773 script is started from rcS.d/ (ignoring some irrelevant ones like
10774 COLUMNS):&lt;/p&gt;
10775
10776 &lt;blockquote&gt;&lt;pre&gt;
10777 DEFAULT_RUNLEVEL=2
10778 previous=N
10779 PREVLEVEL=
10780 RUNLEVEL=
10781 runlevel=S
10782 UPSTART_EVENTS=startup
10783 UPSTART_INSTANCE=
10784 UPSTART_JOB=rc-sysinit
10785 &lt;/pre&gt;&lt;/blockquote&gt;
10786
10787 &lt;p&gt;With sysvinit, these environment variables are set for the same
10788 script.&lt;/p&gt;
10789
10790 &lt;blockquote&gt;&lt;pre&gt;
10791 INIT_VERSION=sysvinit-2.88
10792 previous=N
10793 PREVLEVEL=N
10794 RUNLEVEL=S
10795 runlevel=S
10796 &lt;/pre&gt;&lt;/blockquote&gt;
10797
10798 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10799 sysvinit are not set by upstart. Not sure if it is intentional or not
10800 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10801
10802 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10803 looking for the UPSTART_JOB environment variable seem to be a good
10804 choice.&lt;/p&gt;
10805 </description>
10806 </item>
10807
10808 <item>
10809 <title>A manual for standards wars...</title>
10810 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10812 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10813 <description>&lt;p&gt;Via the
10814 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10815 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10816 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10817 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10818 following the standards wars of today.&lt;/p&gt;
10819 </description>
10820 </item>
10821
10822 <item>
10823 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10824 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10826 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10827 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10828 to get a list of the machine types in use thanks to the DMI
10829 information extracted from each machine. The script to do so is
10830 included in the sitesummary package, and here is example output from
10831 the Skolelinux build servers:&lt;/p&gt;
10832
10833 &lt;blockquote&gt;&lt;pre&gt;
10834 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10835 vendor count
10836 Dell Computer Corporation 1
10837 PowerEdge 1750 1
10838 IBM 1
10839 eserver xSeries 345 -[8670M1X]- 1
10840 Intel 2
10841 [no-dmi-info] 3
10842 maintainer:~#
10843 &lt;/pre&gt;&lt;/blockquote&gt;
10844
10845 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
10846 provided in each machine. Here there are Intel machines without model
10847 information listed with Intel as vendor and no model, and virtual Xen
10848 machines listed as [no-dmi-info]. One can add -l as a command line
10849 option to list the individual machines.&lt;/p&gt;
10850
10851 &lt;p&gt;A larger list is
10852 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
10853 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
10854 provide the basic sitesummary report publicly. In their report there
10855 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
10856 their machines, and as sitesummary is available in both distributions,
10857 it is trivial to get all of them to report to the same central
10858 collector.&lt;/p&gt;
10859 </description>
10860 </item>
10861
10862 <item>
10863 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
10864 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
10865 <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>
10866 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
10867 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
10868 start at boot when an NVidia video card is used is handled. The
10869 problem seem to be that the nvidia X.org driver uses a long time to
10870 initialize, and this duration is longer than kdm is configured to
10871 wait.&lt;/p&gt;
10872
10873 &lt;p&gt;I came across two bugs related to this issue,
10874 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
10875 against initscripts and passed on to nvidia-glx when it became obvious
10876 that the nvidia drivers were involved, and
10877 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
10878 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
10879
10880 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
10881 problem nvidia video card owners experience and make sure the Debian
10882 distribution work out of the box for these users. The nvidia driver
10883 maintainers expect kdm to be set up to wait longer, while kdm expect
10884 the nvidia driver maintainers to fix the driver to start faster, and
10885 while they wait for each other I guess the users end up switching to a
10886 distribution that work for them. I have no idea what the solution is,
10887 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
10888
10889 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
10890 </description>
10891 </item>
10892
10893 <item>
10894 <title>Parallellized boot seem to hold up well in Debian/testing</title>
10895 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
10896 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
10897 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
10898 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
10899 The feature seem to hold up pretty well, but three fairly serious
10900 issues are known and should be solved:
10901
10902 &lt;p&gt;&lt;ul&gt;
10903
10904 &lt;li&gt;The wicd package seen to
10905 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
10906 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
10907 parallel booting is enabled. No idea why, but the wicd maintainer
10908 seem to be on the case.&lt;/li&gt;
10909
10910 &lt;li&gt;The nvidia X driver seem to
10911 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
10912 triggered more easily when parallel booting is in effect. The
10913 maintainer is on the case.&lt;/li&gt;
10914
10915 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
10916 sequencing (the shutdown is broken) when old file-rc users
10917 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
10918 sysv-rc. One way to solve it would be for file-rc to create
10919 /etc/init.d/.legacy-bootordering, and another is to try to make
10920 sysv-rc more robust. Will investigate some more and probably upload a
10921 workaround in sysv-rc to help those trying to move from file-rc to
10922 sysv-rc get a working shutdown.&lt;/li&gt;
10923
10924 &lt;/ul&gt;&lt;/p&gt;
10925
10926 &lt;p&gt;All in all not many surprising issues, and all of them seem
10927 solvable before Squeeze is released. In addition to these there are
10928 some packages with bugs in their dependencies and run level settings,
10929 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
10930
10931 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10932 the BTS, please usertag the report to get it to show up at
10933 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10934 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10935
10936 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
10937 </description>
10938 </item>
10939
10940 <item>
10941 <title>More flexible firmware handling in debian-installer</title>
10942 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
10943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
10944 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
10945 <description>&lt;p&gt;After a long break from debian-installer development, I finally
10946 found time today to return to the project. Having to spend less time
10947 working dependency based boot in debian, as it is almost complete now,
10948 definitely helped freeing some time.&lt;/p&gt;
10949
10950 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
10951 include some firmware packages on the Debian Edu CDs, those needed to
10952 get disk and network controllers working. Without having these
10953 firmware packages available during installation, it is impossible to
10954 install Debian Edu on the given machine, and because our target group
10955 are non-technical people, asking them to provide firmware packages on
10956 an external medium is a support pain. Initially, I expected it to be
10957 enough to include the firmware packages on the CD to get
10958 debian-installer to find and use them. This proved to be wrong.
10959 Next, I hoped it was enough to symlink the relevant firmware packages
10960 to some useful location on the CD (tried /cdrom/ and
10961 /cdrom/firmware/). This also proved to not work, and at this point I
10962 found time to look at the debian-installer code to figure out what was
10963 going to work.&lt;/p&gt;
10964
10965 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
10966 look revealed that it would only look for firmware packages outside
10967 the installation media, so the CD was never checked for firmware
10968 packages. It would only check USB sticks, floppies and other
10969 &quot;external&quot; media devices. Today I changed it to also look in the
10970 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10971 solve the problem I ran into with Debian edu. I also changed it to
10972 look in /firmware/, to make sure the installer also find firmware
10973 provided in the initrd when booting the installer via PXE, to allow us
10974 to provide the same feature in the PXE setup included in Debian
10975 Edu.&lt;/p&gt;
10976
10977 &lt;p&gt;To make sure firmware deb packages with a license questions are not
10978 activated without asking if the license is accepted, I extended
10979 hw-detect to look for preinst scripts in the firmware packages, and
10980 run these before activating the firmware during installation. The
10981 license question is asked using debconf in the preinst, so this should
10982 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
10983
10984 &lt;p&gt;If you want to discuss the details of these features, please
10985 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
10986 </description>
10987 </item>
10988
10989 <item>
10990 <title>Parallellized boot is now the default in Debian/unstable</title>
10991 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
10992 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
10993 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
10994 <description>&lt;p&gt;Since this evening, parallel booting is the default in
10995 Debian/unstable for machines using dependency based boot sequencing.
10996 Apparently the testing of concurrent booting has been wider than
10997 expected, if I am to believe the
10998 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10999 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
11000 with the feature this weekend, to give us some time to detect any
11001 remaining problems before Squeeze is frozen. If serious problems are
11002 detected, it is simple to change the default back to sequential boot.
11003 The upload of the new sysvinit package also activate a new upstream
11004 version.&lt;/p&gt;
11005
11006 More information about
11007 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11008 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
11009 currently possible to disable parallel booting when one run into
11010 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
11011
11012 &lt;blockquote&gt;&lt;pre&gt;
11013 CONCURRENCY=none
11014 &lt;/pre&gt;&lt;/blockquote&gt;
11015
11016 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11017 the BTS, please usertag the report to get it to show up at
11018 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11019 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11020 </description>
11021 </item>
11022
11023 <item>
11024 <title>Sitesummary tip: Listing MAC address of all clients</title>
11025 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
11026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
11027 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
11028 <description>&lt;p&gt;In the recent Debian Edu versions, the
11029 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
11030 system&lt;/a&gt; is used to keep track of the machines in the school
11031 network. Each machine will automatically report its status to the
11032 central server after boot and once per night. The network setup is
11033 also reported, and using this information it is possible to get the
11034 MAC address of all network interfaces in the machines. This is useful
11035 to update the DHCP configuration.&lt;/p&gt;
11036
11037 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
11038 ist all MAC addresses of all machines reporting to sitesummary. Run
11039 this on the collector host:&lt;/p&gt;
11040
11041 &lt;blockquote&gt;&lt;pre&gt;
11042 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
11043 &lt;/pre&gt;&lt;/blockquote&gt;
11044
11045 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
11046 line per machine and with space between the MAC addresses.&lt;/p&gt;
11047
11048 &lt;p&gt;To allow system administrators easier job at adding static DHCP
11049 addresses for hosts, it would be possible to extend this to fetch
11050 machine information from sitesummary and update the DHCP and DNS
11051 tables in LDAP using this information. Such tool is unfortunately not
11052 written yet.&lt;/p&gt;
11053 </description>
11054 </item>
11055
11056 <item>
11057 <title>systemd, an interesting alternative to upstart</title>
11058 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
11059 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
11060 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
11061 <description>&lt;p&gt;The last few days a new boot system called
11062 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
11063 has been
11064 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
11065
11066 to the free software world. I have not yet had time to play around
11067 with it, but it seem to be a very interesting alternative to
11068 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
11069 a good alternative for Debian when we are able to switch to an event
11070 based boot system. Tollef is
11071 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
11072 systemd into Debian, and I look forward to seeing how well it work. I
11073 like the fact that systemd handles init.d scripts with dependency
11074 information natively, allowing them to run in parallel where upstart
11075 at the moment do not.&lt;/p&gt;
11076
11077 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
11078 platform support. It only work on recent Linux kernels, and also need
11079 some new kernel features enabled to function properly. This means
11080 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11081 system. Not sure how that will be handled if systemd proves to be the
11082 way forward.&lt;/p&gt;
11083
11084 &lt;p&gt;In the mean time, based on the
11085 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11086 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
11087 decided to enable full parallel booting as the default in Debian as
11088 soon as possible (probably this weekend or early next week), to see if
11089 there are any remaining serious bugs in the init.d dependencies. A
11090 new version of the sysvinit package implementing this change is
11091 already in experimental. If all go well, Squeeze will be released
11092 with parallel booting enabled by default.&lt;/p&gt;
11093 </description>
11094 </item>
11095
11096 <item>
11097 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
11098 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
11099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
11100 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
11101 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
11102 complete, so complete that it is actually possible to run all the
11103 init.d scripts in parallell based on these dependencies. If you want
11104 to test your Squeeze system, make sure
11105 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11106 based boot sequencing&lt;/a&gt; is enabled, and add this line to
11107 /etc/default/rcS:&lt;/p&gt;
11108
11109 &lt;blockquote&gt;&lt;pre&gt;
11110 CONCURRENCY=makefile
11111 &lt;/pre&gt;&lt;/blockquote&gt;
11112
11113 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
11114 scripts in parallel using the dependency information stored in
11115 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11116 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11117 to try to start the kdm and gdm scripts as early as possible, and will
11118 start the facilities required by kdm or gdm as early as possible to
11119 make this happen.&lt;/p&gt;
11120
11121 &lt;p&gt;Give it a try, and see if you like the result. If some services
11122 fail to start properly, it is most likely because they have incomplete
11123 init.d script dependencies in their startup script (or some of their
11124 dependent scripts have incomplete dependencies). Report bugs and get
11125 the package maintainers to fix it. :)&lt;/p&gt;
11126
11127 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
11128 manage to get the init.d script dependencies complete and correct. I
11129 expect we will get there in Squeeze+1, if we get manage to test and
11130 fix the remaining issues.&lt;/p&gt;
11131
11132 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11133 the BTS, please usertag the report to get it to show up at
11134 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11135 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11136 </description>
11137 </item>
11138
11139 <item>
11140 <title>Debian has switched to dependency based boot sequencing</title>
11141 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
11142 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
11143 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
11144 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
11145 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
11146 have been migrated to using dependency based boot sequencing. This
11147 conclude work me and others have been doing for the last three days.
11148 It feels great to see this finally part of the default Debian
11149 installation. Now we just need to weed out the last few problems that
11150 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
11151
11152 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
11153 fixing the more fundamental problem of handing the event based
11154 non-predictable kernel in the early boot.&lt;/p&gt;
11155 </description>
11156 </item>
11157
11158 <item>
11159 <title>Taking over sysvinit development</title>
11160 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
11161 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
11162 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
11163 <description>&lt;p&gt;After several years of frustration with the lack of activity from
11164 the existing sysvinit upstream developer, I decided a few weeks ago to
11165 take over the package and become the new upstream. The number of
11166 patches to track for the Debian package was becoming a burden, and the
11167 lack of synchronization between the distribution made it hard to keep
11168 the package up to date.&lt;/p&gt;
11169
11170 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11171 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
11172 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
11173 and Fedora), based on the patches currently in use in these
11174 distributions. We Debian maintainers plan to move to this tarball as
11175 the new upstream as soon as we find time to do the merge. Since the
11176 new tarball was created, we agreed with Werner at SuSe to make a new
11177 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
11178 development there. The project is registered and currently waiting
11179 for approval by the Savannah administrators, and as soon as it is
11180 approved, we will import the old versions from svn and continue
11181 working on the future release.&lt;/p&gt;
11182
11183 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
11184 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
11185 </description>
11186 </item>
11187
11188 <item>
11189 <title>Debian boots quicker and quicker</title>
11190 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
11191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
11192 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
11193 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
11194 people involved in the boot system on Debian and Ubuntu, to see if we
11195 could find more ways to speed up the boot system. This was an Ubuntu
11196 funded
11197 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
11198 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
11199 of boot systems, and ways to handle the increasing number of boot
11200 issues introduced by the Linux kernel becoming more and more
11201 asynchronous and event base. The Ubuntu approach using udev and
11202 upstart might be a good way forward. Time will show.&lt;/p&gt;
11203
11204 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
11205 process in Debian. All of these should be applied to get a quick
11206 boot:&lt;/p&gt;
11207
11208 &lt;ul&gt;
11209
11210 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
11211
11212 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
11213 clock is in UTC.&lt;/li&gt;
11214
11215 &lt;li&gt;Install and activate the insserv package to enable
11216 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11217 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
11218
11219 &lt;/ul&gt;
11220
11221 These points are based on the Google summer of code work done by
11222 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
11223 Villegas&lt;/a&gt;.
11224
11225 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
11226 unstable yesterday. When we tested it, we were able to cut 6 seconds
11227 from the boot sequence. It depend on very correct dependency
11228 declaration in all init.d scripts, so I expect us to find edge cases
11229 where the dependences in some scripts are slightly wrong when we start
11230 using this.&lt;/p&gt;
11231
11232 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11233 introduced by Raphael Geissert today, one that could affect the
11234 startup speed as well. Instead of starting some scripts concurrently
11235 from rcS.d/ and another set of scripts from rc2.d/, it would be
11236 possible to run a of them in the same process. A quick way to test
11237 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
11238 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
11239 </description>
11240 </item>
11241
11242 <item>
11243 <title>BSAs påstander om piratkopiering møter motstand</title>
11244 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
11245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
11246 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
11247 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
11248 programvareselskapene som Microsoft og Apple, publisert en rapport der
11249 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11250 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11251 dager siden kom
11252 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
11253 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
11254 dagene. Et spesielt interessant kommentar fra Sverige,
11255 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
11256 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
11257
11258 &lt;blockquote&gt;
11259 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
11260 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11261 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
11262 exakta&quot;, säger BSAs Sverigechef John Hugosson.
11263 &lt;/blockquote&gt;
11264
11265 &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
11266 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
11267 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
11268 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
11269 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
11270
11271 &lt;p&gt;Fant lenkene via &lt;a
11272 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
11273 på Slashdot&lt;/a&gt;.&lt;/p&gt;
11274 </description>
11275 </item>
11276
11277 <item>
11278 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
11279 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
11280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
11281 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
11282 <description>&lt;p&gt;Kom over
11283 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
11284 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11285 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11286 jobber til daglig. En rask opptelling forteller meg at vi har 490
11287 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
11288 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
11289 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
11290 </description>
11291 </item>
11292
11293 <item>
11294 <title>Kryptert harddisk - naturligvis</title>
11295 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
11296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
11297 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
11298 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
11299 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
11300 når en tar tap av arbeidstid, fortrolige dokumenter,
11301 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11302 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11303 til at jeg har kryptert harddisken på både kontormaskinen og min
11304 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11305 komme på avveie, den første informasjon relatert til jobben min ved
11306 Universitetet i Oslo, og den andre relatert til blant annet
11307 foreningsarbeide. Kryptering av diskene gjør at det er lite
11308 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11309 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11310 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11311 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11312 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11313 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11314 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11315 det er gjort slik jeg gjør det er minimale, og gevinstene er
11316 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11317 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
11318
11319 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11320 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11321 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11322 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11323 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11324 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11325 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11326 betydelige.&lt;/p&gt;
11327 </description>
11328 </item>
11329
11330 <item>
11331 <title>Two projects that have improved the quality of free software a lot</title>
11332 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
11333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
11334 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
11335 <description>&lt;p&gt;There are two software projects that have had huge influence on the
11336 quality of free software, and I wanted to mention both in case someone
11337 do not yet know them.&lt;/p&gt;
11338
11339 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11340 tool to detect and expose errors in the memory handling of programs.
11341 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11342 and it will report any problems on stdout. It is even better if the
11343 program include debug information. With debug information, it is able
11344 to report the source file name and line number where the problem
11345 occurs. It can report things like &#39;reading past memory block in file
11346 X line N, the memory block was allocated in file Y, line M&#39;, and
11347 &#39;using uninitialised value in control logic&#39;. This tool has made it
11348 trivial to investigate reproducible crash bugs in programs, and have
11349 reduced the number of this kind of bugs in free software a lot.
11350
11351 &lt;p&gt;The second one is
11352 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11353 a source code checker. It is able to process the source of a program
11354 and find problems in the logic without running the program. It
11355 started out as the Stanford Checker and became well known when it was
11356 used to find bugs in the Linux kernel. It is now a commercial tool
11357 and the company behind it is running
11358 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11359 free software community, where a lot of free software projects get
11360 their source checked for free. Several thousand defects have been
11361 found and fixed so far. It can find errors like &#39;lock L taken in file
11362 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11363 Y lines O to P can never be executed&#39;. The projects included in the
11364 community service project have managed to get rid of a lot of
11365 reliability problems thanks to Coverity.&lt;/p&gt;
11366
11367 &lt;p&gt;I believe tools like this, that are able to automatically find
11368 errors in the source, are vital to improve the quality of software and
11369 make sure we can get rid of the crashing and failing software we are
11370 surrounded by today.&lt;/p&gt;
11371 </description>
11372 </item>
11373
11374 <item>
11375 <title>No patch is not better than a useless patch</title>
11376 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11378 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11379 <description>&lt;p&gt;Julien Blache
11380 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11381 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11382 patch allow one to discuss a concrete and proposed solution, and also
11383 prove that the issue at hand is important enough for someone to spent
11384 time on fixing it. No patch do not provide any of these positive
11385 properties.&lt;/p&gt;
11386 </description>
11387 </item>
11388
11389 <item>
11390 <title>Standardize on protocols and formats, not vendors and applications</title>
11391 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11392 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11393 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11394 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11395 very good one to form a long lived computer infrastructure. It is the
11396 simple one, lost by many in todays computer industry: Standardize on
11397 open network protocols and open exchange/storage formats, not applications.
11398 Applications come and go, while protocols and files tend to stay, and
11399 thus one want to make it easy to change application and vendor, while
11400 avoiding conversion costs and locking users to a specific platform or
11401 application.&lt;/p&gt;
11402
11403 &lt;p&gt;This approach make it possible to replace the client applications
11404 independently of the server applications. One can even allow users to
11405 use several different applications as long as they handle the selected
11406 protocol and format. In the normal case, only one client application
11407 is recommended and users only get help if they choose to use this
11408 application, but those that want to deviate from the easy path are not
11409 blocked from doing so.&lt;/p&gt;
11410
11411 &lt;p&gt;It also allow us to replace the server side without forcing the
11412 users to replace their applications, and thus allow us to select the
11413 best server implementation at any moment, when scale and resouce
11414 requirements change.&lt;/p&gt;
11415
11416 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11417 open formats, but I would never recommend standardizing on a single
11418 application that do not use open network protocol or open formats.&lt;/p&gt;
11419 </description>
11420 </item>
11421
11422 <item>
11423 <title>Returning from Skolelinux developer gathering</title>
11424 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11425 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11426 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11427 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11428 Edu/Skolelinux development gathering. I got a bit done tuning the
11429 desktop, and looked into the dynamic service location protocol
11430 implementation avahi. It look like it could be useful for us. Almost
11431 30 people participated, and I believe it was a great environment to
11432 get to know the Skolelinux system. Walter Bender, involved in the
11433 development of the Sugar educational platform, presented his stuff and
11434 also helped me improve my OLPC installation. He also showed me that
11435 his Turtle Art application can be used in standalone mode, and we
11436 agreed that I would help getting it packaged for Debian. As a
11437 standalone application it would be great for Debian Edu. We also
11438 tried to get the video conferencing working with two OLPCs, but that
11439 proved to be too hard for us. The application seem to need more work
11440 before it is ready for me. I look forward to getting home and relax
11441 now. :)&lt;/p&gt;
11442 </description>
11443 </item>
11444
11445 <item>
11446 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11447 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11448 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11449 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11450 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11451 optimal. There is RFC 2307 documenting one way to store NIS maps in
11452 LDAP, and a modified version of this normally called RFC 2307bis, with
11453 some modifications to be compatible with Active Directory. The RFC
11454 specification handle the content of a lot of system databases, but do
11455 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11456
11457 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11458 we would like to store information about users, SMB clients/hosts,
11459 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11460 and LTSP configuration in LDAP. These objects have a lot in common,
11461 but with the current LDAP schemas it is not possible to have one
11462 object per entity. For example, one need to have at least three LDAP
11463 objects for a given computer, one with the SMB related stuff, one with
11464 DNS information and another with DHCP information. The schemas
11465 provided for DNS and DHCP are impossible to combine into one LDAP
11466 object. In addition, it is impossible to implement quick queries for
11467 netgroup membership, because of the way NIS triples are implemented.
11468 It just do not scale. I believe it is time for a few RFC
11469 specifications to cleam up this mess.&lt;/p&gt;
11470
11471 &lt;p&gt;I would like to have one LDAP object representing each computer in
11472 the network, and this object can then keep the SMB (ie host key), DHCP
11473 (mac address/name) and DNS (name/IP address) settings in one place.
11474 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11475
11476 &lt;p&gt;I would also like to have a quick way to map from a user or
11477 computer and to the net group this user or computer is a member.&lt;/p&gt;
11478
11479 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11480 in this regard, and the unix side need to catch up. Time to start a
11481 new IETF work group?&lt;/p&gt;
11482 </description>
11483 </item>
11484
11485 <item>
11486 <title>Endelig er Debian Lenny gitt ut</title>
11487 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11488 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11489 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11490 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11491 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11492 Et langt steg videre for Debian-prosjektet, og en rekke nye
11493 programpakker blir nå tilgjengelig for de av oss som bruker den
11494 stabile utgaven av Debian. Neste steg er nå å få
11495 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11496 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11497 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11498 slippes løs på skolene. Takk til alle debian-utviklerne som har
11499 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11500 bootsekvens tilgjengelig i stabil utgave, vha pakken
11501 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11502 </description>
11503 </item>
11504
11505 <item>
11506 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11507 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11509 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11510 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11511 Oslo. Most of Saturday was used for the general assemly for the
11512 member organization, but the rest of the weekend I used to tune the
11513 LTSP installation. LTSP now work out of the box on the 10-network.
11514 Acer Aspire One proved to be a very nice thin client, with both
11515 screen, mouse and keybard in a small box. Was working on getting the
11516 diskless workstation setup configured out of the box, but did not
11517 finish it before the weekend was up.&lt;/p&gt;
11518
11519 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11520 the Brazilian group, so that will have to wait for the next
11521 development gathering. Would love to have the Debian Edu installer
11522 automatically detect and configure a multiseat setup when it find one
11523 of these cards.&lt;/p&gt;
11524 </description>
11525 </item>
11526
11527 <item>
11528 <title>The sorry state of multimedia browser plugins in Debian</title>
11529 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11530 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11531 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11532 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11533 plugins available in Debian Lenny, to see which one we should use by
11534 default in Debian Edu. We need an embedded video playing plugin with
11535 control buttons to pause or stop the video, and capable of streaming
11536 all the multimedia content available on the web. The test results and
11537 notes are available on
11538 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11539 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11540 fill this need. My personal video player favorite, VLC, has a really
11541 bad plugin which fail on a lot of the test pages. A lot of the MIME
11542 types I would expect to work with any free software player (like
11543 video/ogg), just do not work. And simple formats like the
11544 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11545 totem and vlc plugins. I hope the situation will improve soon. No
11546 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11547
11548 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11549 be the only one fitting our needs. :/&lt;/p&gt;
11550 </description>
11551 </item>
11552
11553 </channel>
11554 </rss>