]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
929f98a7f40a6ca9af965f60f8f78907aee0d3ec
[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>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
11 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
13 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
14 <description>&lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
15 my projector connected to Kodi. I sadly had to admit that I had no
16 idea, as it was a task I never had tried. Since then, I have been
17 looking for a way to do so, preferable without much extra software to
18 install on either side. Today I found a way that seem to kind of
19 work. Not great, but it is a start.&lt;/p&gt;
20
21 &lt;p&gt;I had a look at several approaches, for example
22 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
23 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
24 local storage enough to store the stream locally. This is not going
25 to work well for me, lacking enough free space, and it would
26 impossible for my friend to get working.&lt;/p&gt;
27
28 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
29 video stream that Kodi could play. Preferably using
30 broadcast/multicast, to avoid having to change any setup on the Kodi
31 side when starting such stream. Unfortunately, the only recipe I
32 could find using multicast used the rtp protocol, and this protocol
33 seem to not be supported by Kodi.&lt;/p&gt;
34
35 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
36 have to specify the IP address of the streaming machine in both the
37 sending command and the file on the Kodi server. But it is showing my
38 desktop, and thus allow us to have a shared look on the big screen at
39 the programs I work on.&lt;/p&gt;
40
41 &lt;p&gt;I did not spend much time investigating codeces. I combined the
42 rtp and rtsp recipes from
43 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
44 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
45 this working on the desktop/streaming end.&lt;/p&gt;
46
47 &lt;blockquote&gt;&lt;pre&gt;
48 vlc screen:// --sout \
49 &#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;
50 &lt;/pre&gt;&lt;/blockquote&gt;
51
52 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
53 same IP address:&lt;/p&gt;
54
55 &lt;blockquote&gt;&lt;pre&gt;
56 echo rtsp://192.168.11.4:8080/test.sdp \
57 &gt; /storage/videos/screenstream.m3u
58 &lt;/pre&gt;&lt;/blockquote&gt;
59
60 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
61 as I can tell the IP must be hardcoded for this to work. In other
62 words, if someone elses machine is going to do the steaming, you have
63 to update screenstream.m4u on the Kodi machine and adjust the vlc
64 repice. To get started, locate the file in Kodi and select the m3u
65 file while the VLC stream is running. The desktop then show up in my
66 big screen. :)&lt;/p&gt;
67
68 &lt;p&gt;When using the same technique to stream a video file with audio,
69 the audio quality is really bad. No idea if the problem is package
70 loss or bad parameters for the transcode. I do not know VLC nor Kodi
71 enough to tell.&lt;/p&gt;
72
73 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
74 activities, please send Bitcoin donations to my address
75 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
76 </description>
77 </item>
78
79 <item>
80 <title>What is the most supported MIME type in Debian in 2018?</title>
81 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
82 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
83 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
84 <description>&lt;p&gt;Five years ago,
85 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
86 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
87 analysing the desktop files in all packages in the archive. Since
88 then, the DEP-11 AppStream system has been put into production, making
89 the task a lot easier. This made me want to repeat the measurement,
90 to see how much things changed. Here are the new numbers, for
91 unstable only this time:
92
93 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
94
95 &lt;pre&gt;
96 count MIME type
97 ----- -----------------------
98 56 image/jpeg
99 55 image/png
100 49 image/tiff
101 48 image/gif
102 39 image/bmp
103 38 text/plain
104 37 audio/mpeg
105 34 application/ogg
106 33 audio/x-flac
107 32 audio/x-mp3
108 30 audio/x-wav
109 30 audio/x-vorbis+ogg
110 29 image/x-portable-pixmap
111 27 inode/directory
112 27 image/x-portable-bitmap
113 27 audio/x-mpeg
114 26 application/x-ogg
115 25 audio/x-mpegurl
116 25 audio/ogg
117 24 text/html
118 &lt;/pre&gt;
119
120 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
121 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
122 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
123
124 &lt;p&gt;It is interesting to see how image formats have passed text/plain
125 as the most announced supported MIME type. These days, thanks to the
126 AppStream system, if you run into a file format you do not know, and
127 want to figure out which packages support the format, you can find the
128 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
129 look up all packages announcing support for this format in their
130 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
131 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
132 me, want to know which packages support inode/directory, you can get a
133 list like this:&lt;/p&gt;
134
135 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
136 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
137 Package: anjuta
138 Package: audacious
139 Package: baobab
140 Package: cervisia
141 Package: chirp
142 Package: dolphin
143 Package: doublecmd-common
144 Package: easytag
145 Package: enlightenment
146 Package: ephoto
147 Package: filelight
148 Package: gwenview
149 Package: k4dirstat
150 Package: kaffeine
151 Package: kdesvn
152 Package: kid3
153 Package: kid3-qt
154 Package: nautilus
155 Package: nemo
156 Package: pcmanfm
157 Package: pcmanfm-qt
158 Package: qweborf
159 Package: ranger
160 Package: sirikali
161 Package: spacefm
162 Package: spacefm
163 Package: vifm
164 %
165 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
166
167 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
168 format is not yet supported by any package in Debian:&lt;/p&gt;
169
170 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
171 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
172 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
173 %
174 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
175
176 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
177 format:&lt;/p&gt;
178
179 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
180 % appstreamcli what-provides mimetype application/sla|grep Package
181 Package: cura
182 Package: meshlab
183 Package: printrun
184 %
185 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
186
187 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
188
189 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
190 activities, please send Bitcoin donations to my address
191 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
192 </description>
193 </item>
194
195 <item>
196 <title>Debian APT upgrade without enough free space on the disk...</title>
197 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
198 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
199 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
200 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
201 for a while, and when I need to update it there is not enough free
202 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
203 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
204 upgrade only some of the packages in one batch, until the amount of
205 packages to download fall below the amount of free space available.
206 Today, I had about 500 packages to upgrade, and after a while I got
207 tired of trying to install chunks of packages manually. I concluded
208 that I did not have the spare hours required to complete the task, and
209 decided to see if I could automate it. I came up with this small
210 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
211
212 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
213 #!/bin/sh
214 #
215 # Upgrade packages when the disk is too full to upgrade every
216 # upgradable package in one lump. Fetching packages to upgrade using
217 # apt, and then installing using dpkg, to avoid changing the package
218 # flag for manual/automatic.
219
220 set -e
221
222 ignore() {
223 if [ &quot;$1&quot; ]; then
224 grep -v &quot;$1&quot;
225 else
226 cat
227 fi
228 }
229
230 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
231 echo &quot;Upgrading $p&quot;
232 apt clean
233 apt install --download-only -y $p
234 for f in /var/cache/apt/archives/*.deb; do
235 if [ -e &quot;$f&quot; ]; then
236 dpkg -i /var/cache/apt/archives/*.deb
237 break
238 fi
239 done
240 done
241 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
242
243 &lt;p&gt;The script will extract the list of packages to upgrade, try to
244 download the packages needed to upgrade one package, install the
245 downloaded packages using dpkg. The idea is to upgrade packages
246 without changing the APT mark for the package (ie the one recording of
247 the package was manually requested or pulled in as a dependency). To
248 use it, simply run it as root from the command line. If it fail, try
249 &#39;apt install -f&#39; to clean up the mess and run the script again. This
250 might happen if the new packages conflict with one of the old
251 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
252
253 &lt;p&gt;It take one option, a package to ignore in the list of packages to
254 upgrade. The option to ignore a package is there to be able to skip
255 the packages that are simply too large to unpack. Today this was
256 &#39;ghc&#39;, but I have run into other large packages causing similar
257 problems earlier (like TeX).&lt;/p&gt;
258
259 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
260 alternative ways to handle this. The &quot;unattended-upgrades
261 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
262 each package to upgrade, and then upgrade them in order, smallest set
263 first. It might be a better option than my above mentioned script.
264 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
265 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
266
267 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
268 activities, please send Bitcoin donations to my address
269 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
270 </description>
271 </item>
272
273 <item>
274 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
275 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
277 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
278 <description>&lt;p&gt;A new version of the
279 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
280 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
281 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
282 useful. It was uploaded the last few days, and the last update will
283 enter testing tomorrow. See the
284 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
285 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
286 was announced 6 days ago. We will try to get it into Debian as
287 well.&lt;/p&gt;
288
289 &lt;p&gt;More information related to 3D printing is available on the
290 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
291 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
292 in Debian.&lt;/p&gt;
293
294 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
295 activities, please send Bitcoin donations to my address
296 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
297 </description>
298 </item>
299
300 <item>
301 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
302 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
304 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
305 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
306 that the nice and user friendly 3D printer slicer software Cura just
307 entered Debian Unstable. It consist of five packages,
308 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
309 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
310 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
311 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
312 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
313 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
314 two, uranium and cura, entered Unstable yesterday. This should make
315 it easier for Debian users to print on at least the Ultimaker class of
316 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
317 make life easier for at least me. :)&lt;/p&gt;
318
319 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
320 happy to assist him in sponsoring the packages. With the introduction
321 of Cura, Debian is up to three 3D printer slicers at your service,
322 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
323 printer, give it a go. :)&lt;/p&gt;
324
325 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
326 team, flocking together on the
327 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
328 mailing list and the
329 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
330 IRC channel.&lt;/p&gt;
331
332 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
333 version 3.0.3 and then update the entire set of packages to version
334 3.1.0 which showed up the last few days.&lt;/p&gt;
335 </description>
336 </item>
337
338 <item>
339 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
340 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
341 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
342 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
343 <description>&lt;p&gt;At my nearby maker space,
344 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
345 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
346 on Windows and MacOS X than Linux, because the software involved had
347 to be manually compiled and set up on Linux while premade packages
348 worked out of the box on Windows and MacOS X. I found this annoying,
349 as the software involved,
350 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
351 and should be trivial to get up and running on Linux if someone took
352 the time to package it for the relevant distributions. I even found
353 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
354 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
355 never resulted in the software showing up in Debian. So a few days
356 ago I offered my help to try to improve the situation.&lt;/p&gt;
357
358 &lt;p&gt;Now I am very happy to see that all the packages required by a
359 working Cura in Debian are uploaded into Debian and waiting in the NEW
360 queue for the ftpmasters to have a look. You can track the progress
361 on
362 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
363 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
364
365 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
366 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
367 queue&lt;/a&gt; while we work up updating the packages to the latest
368 upstream version.&lt;/p&gt;
369
370 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
371 to use and was unable to configure correctly for Ultimaker 2+ in the
372 short time I spent on it, are already in Debian. If you are looking
373 for 3D printer &quot;slicers&quot; and want something already available in
374 Debian, check out
375 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
376 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
377 The latter is a fork of the former.&lt;/p&gt;
378
379 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
380 activities, please send Bitcoin donations to my address
381 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
382 </description>
383 </item>
384
385 <item>
386 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
387 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
389 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
390 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
391 mobile cell towers. And this radio chatter is available for anyone
392 with a radio receiver capable of receiving them. Details about the
393 mobile phones with very good accuracy is of course collected by the
394 phone companies, but this is not the topic of this blog post. The
395 mobile phone radio chatter make it possible to figure out when a cell
396 phone is nearby, as it include the SIM card ID (IMSI). By paying
397 attention over time, one can see when a phone arrive and when it leave
398 an area. I believe it would be nice to make this information more
399 available to the general public, to make more people aware of how
400 their phones are announcing their whereabouts to anyone that care to
401 listen.&lt;/p&gt;
402
403 &lt;p&gt;I am very happy to report that we managed to get something
404 visualizing this information up and running for
405 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
406 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
407 library. The solution is based on the
408 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
409 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
410 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
411 Sone from the Computer Science department of the University of
412 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
413 IMSIs) as dots in a web browser graph, with lines to the dot
414 representing mobile base station it is talking to. It was working in
415 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
416
417 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
418 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
419 connected and visualize the visible cell phone towers using an
420 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
421 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
422 grgsm_livemon_headless processes from
423 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
424 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
425
426 &lt;p&gt;The frequencies to listen to, are identified using a slightly
427 patched scan-and-livemon (to set the --args values for each receiver),
428 and the Hopglass data is generated using the
429 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
430 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
431 more than four SDRs working. There is also a geographical map trying
432 to show the location of the base stations, but I believe their
433 coordinates are hardcoded to some random location in Germany, I
434 believe. The code should be replaced with code to look up location in
435 a text file, a sqlite database or one of the online databases
436 mentioned in
437 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
438 issue for the topic&lt;/a&gt;.
439
440 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
441 </description>
442 </item>
443
444 <item>
445 <title>Easier recipe to observe the cell phones around you</title>
446 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
447 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
448 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
449 <description>&lt;p&gt;A little more than a month ago I wrote
450 &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
451 to observe the SIM card ID (aka IMSI number) of mobile phones talking
452 to nearby mobile phone base stations using Debian GNU/Linux and a
453 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
454 the location of people and equipment (like cars and trains) with an
455 accuracy of a few kilometer. Since then we have worked to make the
456 procedure even simpler, and it is now possible to do this without any
457 manual frequency tuning and without building your own packages.&lt;/p&gt;
458
459 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
460 package is now included in Debian testing and unstable, and the
461 IMSI-catcher code no longer require root access to fetch and decode
462 the GSM data collected using gr-gsm.&lt;/p&gt;
463
464 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
465 clone of two python scripts:&lt;/p&gt;
466
467 &lt;ol&gt;
468
469 &lt;li&gt;Start with a Debian machine running the Buster version (aka
470 testing).&lt;/li&gt;
471
472 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
473 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
474
475 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
476 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
477
478 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
479
480 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
481 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
482 stations and start listening for GSM packages on one of them.&lt;/li&gt;
483
484 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
485 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
486
487 &lt;/ol&gt;
488
489 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
490 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
491 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
492 work with RTL 8232 and other similar USB radio receivers you can get
493 very cheaply
494 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
495 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
496 and only use HackRF for fetching GSM data.&lt;/p&gt;
497
498 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
499 frequencies at the time, so if you are going to track and count every
500 cell phone around you, you need to listen to all the frequencies used.
501 To listen to several frequencies, use the --numrecv argument to
502 scan-and-livemon to use several receivers. Further, I am not sure if
503 phones using 3G or 4G will show as talking GSM to base stations, so
504 this approach might not see all phones around you. I typically see
505 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
506
507 &lt;p&gt;I&#39;ve tried to run the scanner on a
508 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
509 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
510 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
511 stdout, I am told there it is caused by a buffer overflow between the
512 radio and GNU Radio, caused by the program being unable to read the
513 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
514 where you started scan-and-livemon, you need a give the process more
515 CPU power. Perhaps someone are able to optimize the code to a point
516 where it become possible to set up RPi3 based GSM sniffers? I tried
517 using Raspbian instead of Debian, but there seem to be something wrong
518 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
519 </description>
520 </item>
521
522 <item>
523 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
524 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
526 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
527 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
528 web based ICT news magazine digi.no on
529 &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
530 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
531 DVB-T software defined radios. The article refered to instructions
532 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
533 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;
534
535 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
536 bypass apt), use pip to install pybombs (to bypass both apt and pip),
537 and the ask pybombs to fetch and build everything you need from
538 scratch. I wanted to see if I could do the same on the most recent
539 Debian packages, but this did not work because pybombs tried to build
540 stuff that no longer build with the most recent openssl library or
541 some other version skew problem. While trying to get this recipe
542 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
543 and the only piece of software dependency missing in Debian was the
544 gr-gsm package. I also found out that the lead upstream developer of
545 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
546 Debian packages provided in an Ubuntu PPA repository. All I needed to
547 do was to dget the Debian source package and built it.&lt;/p&gt;
548
549 &lt;p&gt;The IMSI collector is a python script listening for packages on the
550 loopback network device and printing to the terminal some specific GSM
551 packages with IMSI numbers in them. The code is fairly short and easy
552 to understand. The reason this work is because gr-gsm include a tool
553 to read GSM data from a software defined radio like a DVB-T USB stick
554 and other software defined radios, decode them and inject them into a
555 network device on your Linux machine (using the loopback device by
556 default). This proved to work just fine, and I&#39;ve been testing the
557 collector for a few days now.&lt;/p&gt;
558
559 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
560
561 &lt;ol&gt;
562
563 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
564
565 &lt;li&gt;build and install the gr-gsm package available from
566 &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;
567
568 &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;
569
570 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
571 where it was started is filled with a stream of text (meaning you
572 found a GSM station).&lt;/li&gt;
573
574 &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;
575
576 &lt;/ol&gt;
577
578 &lt;p&gt;To make it even easier in the future to get this sniffer up and
579 running, I decided to package
580 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
581 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
582 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
583 Luckily the gnuradio maintainer has promised to help me, as I do not
584 know much about gnuradio stuff yet.&lt;/p&gt;
585
586 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
587 commercial tools like
588 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
589 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
590 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
591 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
592 more people realise how their whereabouts when carrying a cell phone
593 is easily tracked. Seeing the data flow on the screen, realizing that
594 I live close to a police station and knowing that the police is also
595 wearing cell phones, I wonder how hard it would be for criminals to
596 track the position of the police officers to discover when there are
597 police near by, or for foreign military forces to track the location
598 of the Norwegian military forces, or for anyone to track the location
599 of government officials...&lt;/p&gt;
600
601 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
602 script mentioned above is only a fraction of the data broadcasted on
603 the GSM network. It will only collect one frequency at the time,
604 while a typical phone will be using several frequencies, and not all
605 phones will be using the frequencies tracked by the grgsm_livemod
606 program. Also, there is a lot of radio chatter being ignored by the
607 simple_IMSI-catcher script, which would be collected by extending the
608 parser code. I wonder if gr-gsm can be set up to listen to more than
609 one frequency?&lt;/p&gt;
610 </description>
611 </item>
612
613 <item>
614 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
615 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
617 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
618 <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;
619
620 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
621 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
622 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
623 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
624 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
625 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
626 price. The book is also available for download in electronic form as
627 PDF, EPUB and Mobipocket, as can be
628 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
629 as a web page&lt;/a&gt;.&lt;/p&gt;
630
631 &lt;p&gt;This is the second book I publish (the first was the book
632 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
633 in
634 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
635 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
636 and
637 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
638 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
639 project. I hope
640 &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
641 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
642 </description>
643 </item>
644
645 <item>
646 <title>Når nynorskoversettelsen svikter til eksamen...</title>
647 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
649 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
650 <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
651 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
652 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
653 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
654 på om den fri oversetterløsningen
655 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
656 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
657
658 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
659
660 &lt;blockquote&gt;
661 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
662 rolle og muligheter til å håndtere internasjonale utfordringer, som
663 for eksempel flykningekrisen.&lt;/p&gt;
664
665 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
666 på temaet:&lt;/p&gt;
667 &lt;ol&gt;
668 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
669 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
670 &lt;/ol&gt;
671
672 &lt;/blockquote&gt;
673
674 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
675
676 &lt;blockquote&gt;
677 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
678 andre aktørar og høve til å handtera internasjonale utfordringar, som
679 til dømes *flykningekrisen.&lt;/p&gt;
680
681 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
682 temaet:&lt;/p&gt;
683
684 &lt;ol&gt;
685 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
686 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
687 &lt;/ol&gt;
688
689 &lt;/blockquote&gt;
690
691 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
692 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
693 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
694 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
695 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
696 det er kanskje flisespikking. Det understreker vel bare at det alltid
697 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
698 </description>
699 </item>
700
701 <item>
702 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
703 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
704 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
705 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
706 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
707 computers at the time, I often needed a way to detect if the machine
708 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
709 file or directory affected by the hang, the process (and possibly the
710 shell) will hang too. So you want to be able to detect this without
711 risking the detection process getting stuck too. It has not been
712 obvious how to do this. When the hang has lasted a while, it is
713 possible to find messages like these in dmesg:&lt;/p&gt;
714
715 &lt;p&gt;&lt;blockquote&gt;
716 nfs: server nfsserver not responding, still trying
717 &lt;br&gt;nfs: server nfsserver OK
718 &lt;/blockquote&gt;&lt;/p&gt;
719
720 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
721 be sure looking in dmesg is going to work. If there are lots of other
722 messages in dmesg the lines might have rotated out of site before they
723 are noticed.&lt;/p&gt;
724
725 &lt;p&gt;While reading through the nfs client implementation in linux kernel
726 code, I came across some statistics that seem to give a way to detect
727 it. The om_timeouts sunrpc value in the kernel will increase every
728 time the above log entry is inserted into dmesg. And after digging a
729 bit further, I discovered that this value show up in
730 /proc/self/mountstats on Linux.&lt;/p&gt;
731
732 &lt;p&gt;The mountstats content seem to be shared between files using the
733 same file system context, so it is enough to check one of the
734 mountstats files to get the state of the mount point for the machine.
735 I assume this will not show lazy umounted NFS points, nor NFS mount
736 points in a different process context (ie with a different filesystem
737 view), but that does not worry me.&lt;/p&gt;
738
739 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
740
741 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
742 [...]
743 device /dev/mapper/Debian-var mounted on /var with fstype ext3
744 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
745 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
746 age: 7863311
747 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
748 sec: flavor=1,pseudoflavor=1
749 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
750 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
751 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
752 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
753 per-op statistics
754 NULL: 0 0 0 0 0 0 0 0
755 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
756 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
757 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
758 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
759 READLINK: 125 125 0 20472 18620 0 1112 1118
760 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
761 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
762 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
763 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
764 SYMLINK: 903 903 0 233428 245488 6 5865 5917
765 MKNOD: 80 80 0 20148 21760 0 299 304
766 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
767 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
768 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
769 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
770 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
771 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
772 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
773 FSINFO: 2 2 0 232 328 0 1 1
774 PATHCONF: 1 1 0 116 140 0 0 0
775 COMMIT: 0 0 0 0 0 0 0 0
776
777 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
778 [...]
779 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
780
781 &lt;p&gt;The key number to look at is the third number in the per-op list.
782 It is the number of NFS timeouts experiences per file system
783 operation. Here 22 write timeouts and 5 access timeouts. If these
784 numbers are increasing, I believe the machine is experiencing NFS
785 hang. Unfortunately the timeout value do not start to increase right
786 away. The NFS operations need to time out first, and this can take a
787 while. The exact timeout value depend on the setup. For example the
788 defaults for TCP and UDP mount points are quite different, and the
789 timeout value is affected by the soft, hard, timeo and retrans NFS
790 mount options.&lt;/p&gt;
791
792 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
793 Enterprise Linux for getting the timeout count is to peek in /proc/.
794 But according to
795 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
796 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
797 command can be used to get these timeout values. But this do not work
798 on Linux, as far as I can tell. I
799 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
800 but have not seen any replies yet.&lt;/p&gt;
801
802 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
803 experiencing NFS hangs? Is there a way to detect which processes are
804 affected? Is there a way to get the NFS mount going quickly once the
805 network problem causing the NFS hang has been cleared? I would very
806 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
807 </description>
808 </item>
809
810 <item>
811 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
812 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
813 <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>
814 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
815 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
816 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
817 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
818 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
819 we are working on the proof reading to ensure consistent language and
820 use of correct computer science terms. The plan is to make the book
821 available on paper, as well as in electronic form. For that to
822 happen, the proof reading must be completed and all the figures need
823 to be translated. If you want to help out, get in touch.&lt;/p&gt;
824
825 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
826
827 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
828 pages) of the book created every morning is available for
829 proofreading. If you find any errors, please
830 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
831 Weblate and correct the error&lt;/a&gt;. The
832 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
833 of the translation including figures&lt;/a&gt; is a useful source for those
834 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
835 </description>
836 </item>
837
838 <item>
839 <title>Unlimited randomness with the ChaosKey?</title>
840 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
842 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
843 <description>&lt;p&gt;A few days ago I ordered a small batch of
844 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
845 USB dongle for generating entropy created by Bdale Garbee and Keith
846 Packard. Yesterday it arrived, and I am very happy to report that it
847 work great! According to its designers, to get it to work out of the
848 box, you need the Linux kernel version 4.1 or later. I tested on a
849 Debian Stretch machine (kernel version 4.9), and there it worked just
850 fine, increasing the available entropy very quickly. I wrote a small
851 test oneliner to test. It first print the current entropy level,
852 drain /dev/random, and then print the entropy level for five seconds.
853 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
854
855 &lt;blockquote&gt;&lt;pre&gt;
856 % cat /proc/sys/kernel/random/entropy_avail; \
857 dd bs=1M if=/dev/random of=/dev/null count=1; \
858 for n in $(seq 1 5); do \
859 cat /proc/sys/kernel/random/entropy_avail; \
860 sleep 1; \
861 done
862 300
863 0+1 oppføringer inn
864 0+1 oppføringer ut
865 28 byte kopiert, 0,000264565 s, 106 kB/s
866 4
867 8
868 12
869 17
870 21
871 %
872 &lt;/pre&gt;&lt;/blockquote&gt;
873
874 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
875 application requiring random bits (like a HTTPS enabled web server)
876 will halt and wait for more entrpy. And here is the situation with
877 the ChaosKey inserted:&lt;/p&gt;
878
879 &lt;blockquote&gt;&lt;pre&gt;
880 % cat /proc/sys/kernel/random/entropy_avail; \
881 dd bs=1M if=/dev/random of=/dev/null count=1; \
882 for n in $(seq 1 5); do \
883 cat /proc/sys/kernel/random/entropy_avail; \
884 sleep 1; \
885 done
886 1079
887 0+1 oppføringer inn
888 0+1 oppføringer ut
889 104 byte kopiert, 0,000487647 s, 213 kB/s
890 433
891 1028
892 1031
893 1035
894 1038
895 %
896 &lt;/pre&gt;&lt;/blockquote&gt;
897
898 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
899 someone want to buy one here in Norway. :)&lt;/p&gt;
900
901 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
902 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
903 recording illuminating&lt;/a&gt;. It explains exactly what the source of
904 randomness is, if you are unable to spot it from the schema drawing
905 available from the ChaosKey web site linked at the start of this blog
906 post.&lt;/p&gt;
907 </description>
908 </item>
909
910 <item>
911 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
912 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
914 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
915 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
916 web servers, and who own the network equipment it is flowing through?
917 It is possible to get a glimpse of this from using traceroute, but it
918 is hard to find all the details. Many years ago, I wrote a system to
919 map the Norwegian Internet (trying to figure out if our plans for a
920 network game service would get low enough latency, and who we needed
921 to talk to about setting up game servers close to the users. Back
922 then I used traceroute output from many locations (I asked my friends
923 to run a script and send me their traceroute output) to create the
924 graph and the map. The output from traceroute typically look like
925 this:
926
927 &lt;p&gt;&lt;pre&gt;
928 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
929 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
930 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
931 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
932 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
933 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
934 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
935 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
936 8 * * *
937 9 * * *
938 [...]
939 &lt;/pre&gt;&lt;/p&gt;
940
941 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
942 network equipment involved in getting the data traffic from me to the
943 www.stortinget.no server, and how long it took in milliseconds for a
944 package to reach the equipment and return to me. Three packages are
945 sent, and some times the packages do not follow the same path. This
946 is shown for hop 5, where three different IP addresses replied to the
947 traceroute request.&lt;/p&gt;
948
949 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
950 implementations I use are traceroute (using ICMP packages) mtr (can do
951 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
952 traceroute and a lot of other capabilities). All of them are easily
953 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
954
955 &lt;p&gt;This time around, I wanted to know the geographic location of
956 different route points, to visualize how visiting a web page spread
957 information about the visit to a lot of servers around the globe. The
958 background is that a web site today often will ask the browser to get
959 from many servers the parts (for example HTML, JSON, fonts,
960 JavaScript, CSS, video) required to display the content. This will
961 leak information about the visit to those controlling these servers
962 and anyone able to peek at the data traffic passing by (like your ISP,
963 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
964
965 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
966 www.stortinget.no. It is read daily by all members of parliament and
967 their staff, as well as political journalists, activits and many other
968 citizens of Norway. A visit to the www.stortinget.no web site will
969 ask your browser to contact 8 other servers: ajax.googleapis.com,
970 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
971 stats.g.doubleclick.net, www.google-analytics.com,
972 www.googletagmanager.com and www.netigate.se. I extracted this by
973 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
974 Stortinget web page and tell me all the URLs PhantomJS downloaded to
975 render the page (in HAR format using
976 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
977 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
978 to do this). My goal is to visualize network traces to all IP
979 addresses behind these DNS names, do show where visitors personal
980 information is spread when visiting the page.&lt;/p&gt;
981
982 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
983 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;
984
985 &lt;p&gt;When I had a look around for options, I could not find any good
986 free software tools to do this, and decided I needed my own traceroute
987 wrapper outputting KML based on locations looked up using GeoIP. KML
988 is easy to work with and easy to generate, and understood by several
989 of the GIS tools I have available. I got good help from by NUUG
990 colleague Anders Einar with this, and the result can be seen in
991 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
992 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
993 free GeoIP databases I could find (and the for-pay databases my
994 friends had access to) is not up to the task. The IP addresses of
995 central Internet infrastructure would typically be placed near the
996 controlling companies main office, and not where the router is really
997 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
998 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
999
1000 &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
1001 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;
1002
1003 &lt;p&gt;I also had a look at the visual traceroute graph created by
1004 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1005 showing IP network ownership (aka AS owner) for the IP address in
1006 question.
1007 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1008 graph display a lot of useful information about the traceroute in SVG
1009 format&lt;/a&gt;, and give a good indication on who control the network
1010 equipment involved, but it do not include geolocation. This graph
1011 make it possible to see the information is made available at least for
1012 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1013 3 Communications and NetDNA.&lt;/p&gt;
1014
1015 &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
1016 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;
1017
1018 &lt;p&gt;In the process, I came across the
1019 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1020 Salim Gasmi. Its methology of combining guesses based on DNS names,
1021 various location databases and finally use latecy times to rule out
1022 candidate locations seemed to do a very good job of guessing correct
1023 geolocation. But it could only do one trace at the time, did not have
1024 a sensor in Norway and did not make the geolocations easily available
1025 for postprocessing. So I contacted the developer and asked if he
1026 would be willing to share the code (he refused until he had time to
1027 clean it up), but he was interested in providing the geolocations in a
1028 machine readable format, and willing to set up a sensor in Norway. So
1029 since yesterday, it is possible to run traces from Norway in this
1030 service thanks to a sensor node set up by
1031 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1032 trace in KML format for further processing.&lt;/p&gt;
1033
1034 &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
1035 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;
1036
1037 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1038 Denmark, Germany, Holland and Ireland. Plenty of places where the
1039 Snowden confirmations verified the traffic is read by various actors
1040 without your best interest as their top priority.&lt;/p&gt;
1041
1042 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1043 over all the hosts behind the urls imported by www.stortinget.no and
1044 ask for the KML file from GeoTraceroute, and create a combined KML
1045 file with all the traces (unfortunately only one of the IP addresses
1046 behind the DNS name is traced this time. To get them all, one would
1047 have to request traces using IP number instead of DNS names from
1048 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1049
1050 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1051 the IP traffic moves and who control the boxes involved in moving it.
1052 And every time the link crosses for example the Swedish border, we can
1053 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1054 Britain and NSA in USA and cables around the globe. (Hm, what should
1055 we tell them? :) Keep that in mind if you ever send anything
1056 unencrypted over the Internet.&lt;/p&gt;
1057
1058 &lt;p&gt;PS: KML files are drawn using
1059 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1060 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1061 Marble. There are heaps of other options too.&lt;/p&gt;
1062
1063 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1064 activities, please send Bitcoin donations to my address
1065 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1066 </description>
1067 </item>
1068
1069 <item>
1070 <title>Appstream just learned how to map hardware to packages too!</title>
1071 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1073 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1074 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1075 readers probably know, I have been working on the
1076 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1077 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1078 it easier for users to figure out what to install to get a given piece
1079 of hardware to work in Debian, and a key part of this system is a way
1080 to map hardware to packages. Isenkram have its own mapping database,
1081 and also uses data provided by each package using the AppStream
1082 metadata format. And today,
1083 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1084 Debian learned to look up hardware the same way Isenkram is doing it,
1085 ie using fnmatch():&lt;/p&gt;
1086
1087 &lt;p&gt;&lt;pre&gt;
1088 % appstreamcli what-provides modalias \
1089 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1090 Identifier: pymissile [generic]
1091 Name: pymissile
1092 Summary: Control original Striker USB Missile Launcher
1093 Package: pymissile
1094 % appstreamcli what-provides modalias usb:v0694p0002d0000
1095 Identifier: libnxt [generic]
1096 Name: libnxt
1097 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1098 Package: libnxt
1099 ---
1100 Identifier: t2n [generic]
1101 Name: t2n
1102 Summary: Simple command-line tool for Lego NXT
1103 Package: t2n
1104 ---
1105 Identifier: python-nxt [generic]
1106 Name: python-nxt
1107 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1108 Package: python-nxt
1109 ---
1110 Identifier: nbc [generic]
1111 Name: nbc
1112 Summary: C compiler for LEGO Mindstorms NXT bricks
1113 Package: nbc
1114 %
1115 &lt;/pre&gt;&lt;/p&gt;
1116
1117 &lt;p&gt;A similar query can be done using the combined AppStream and
1118 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1119
1120 &lt;p&gt;&lt;pre&gt;
1121 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1122 pymissile
1123 % isenkram-lookup usb:v0694p0002d0000
1124 libnxt
1125 nbc
1126 python-nxt
1127 t2n
1128 %
1129 &lt;/pre&gt;&lt;/p&gt;
1130
1131 &lt;p&gt;You can find modalias values relevant for your machine using
1132 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1133
1134 &lt;p&gt;If you want to make this system a success and help Debian users
1135 make the most of the hardware they have, please
1136 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1137 AppStream metadata for your package following the guidelines&lt;/a&gt;
1138 documented in the wiki. So far only 11 packages provide such
1139 information, among the several hundred hardware specific packages in
1140 Debian. The Isenkram database on the other hand contain 101 packages,
1141 mostly related to USB dongles. Most of the packages with hardware
1142 mapping in AppStream are LEGO Mindstorms related, because I have, as
1143 part of my involvement in
1144 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1145 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1146 complete set of packages in Debian for that particular hardware. The
1147 team also got a nice Christmas present today. The
1148 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1149 package&lt;/a&gt; made it into Debian. With this package in place, it is
1150 now possible to use the LEGO Mindstorms NXT unit with only free
1151 software, as the nxt-firmware package contain the source and firmware
1152 binaries for the NXT brick.&lt;/p&gt;
1153
1154 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1155 activities, please send Bitcoin donations to my address
1156 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1157 </description>
1158 </item>
1159
1160 <item>
1161 <title>Isenkram updated with a lot more hardware-package mappings</title>
1162 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1164 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1165 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1166 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1167 and install packages to get your hardware dongles to work, is still
1168 going strong. It is a system to look up the hardware present on or
1169 connected to the current system, and map the hardware to Debian
1170 packages. It can either be done using the tools in isenkram-cli or
1171 using the user space daemon in the isenkram package. The latter will
1172 notify you, when inserting new hardware, about what packages to
1173 install to get the dongle working. It will even provide a button to
1174 click on to ask packagekit to install the packages.&lt;/p&gt;
1175
1176 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1177
1178 &lt;p&gt;&lt;pre&gt;
1179 % isenkram-lookup
1180 bluez
1181 cheese
1182 ethtool
1183 fprintd
1184 fprintd-demo
1185 gkrellm-thinkbat
1186 hdapsd
1187 libpam-fprintd
1188 pidgin-blinklight
1189 thinkfan
1190 tlp
1191 tp-smapi-dkms
1192 tp-smapi-source
1193 tpb
1194 %
1195 &lt;/pre&gt;&lt;/p&gt;
1196
1197 &lt;p&gt;It can also list the firware package providing firmware requested
1198 by the load kernel modules, which in my case is an empty list because
1199 I have all the firmware my machine need:
1200
1201 &lt;p&gt;&lt;pre&gt;
1202 % /usr/sbin/isenkram-autoinstall-firmware -l
1203 info: did not find any firmware files requested by loaded kernel modules. exiting
1204 %
1205 &lt;/pre&gt;&lt;/p&gt;
1206
1207 &lt;p&gt;The last few days I had a look at several of the around 250
1208 packages in Debian with udev rules. These seem like good candidates
1209 to install when a given hardware dongle is inserted, and I found
1210 several that should be proposed by isenkram. I have not had time to
1211 check all of them, but am happy to report that now there are 97
1212 packages packages mapped to hardware by Isenkram. 11 of these
1213 packages provide hardware mapping using AppStream, while the rest are
1214 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1215
1216 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1217 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1218 support using AppStream, for everyone to use:&lt;/p&gt;
1219
1220 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1221 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1222 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1223 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1224 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1225 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1226 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1227 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1228 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1229 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1230 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1231 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1232 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1233 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1234 pcscd, pidgin-blinklight, printer-driver-splix,
1235 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1236 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1237 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1238 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1239 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1240 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1241 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1242 xserver-xorg-video-vmware, yubikey-personalization and
1243 zd1211-firmware&lt;/p&gt;
1244
1245 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1246 bug report against the isenkram-cli package, and ask the package
1247 maintainer to
1248 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1249 metadata according to the guidelines&lt;/a&gt; to provide the information
1250 for everyone. In time, I hope to get rid of the isenkram specific
1251 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1252
1253 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1254 much hardware, and suggest that the package with with any ethernet
1255 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1256 the details. I hope the maintainer find time to address it soon. In
1257 the mean time I provide an override in isenkram.&lt;/p&gt;
1258 </description>
1259 </item>
1260
1261 <item>
1262 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1263 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1265 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1266 <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;
1267
1268 &lt;p&gt;In my early years, I played
1269 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1270 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1271 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1272 original Elite game was available on Commodore 64 and the IBM PC
1273 edition I played had a 64 KB executable. I am still impressed today
1274 that the authors managed to squeeze both a 3D engine and details about
1275 more than 2000 planet systems across 7 galaxies into a binary so
1276 small.&lt;/p&gt;
1277
1278 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1279 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1280 really have time to test it properly until a few days ago. It was
1281 great to discover that my old knowledge about trading routes were
1282 still valid. But my fighting and flying abilities were gone, so I had
1283 to retrain to be able to dock on a space station. And I am still not
1284 able to make much resistance when I am attacked by pirates, so I
1285 bougth and mounted the most powerful laser in the rear to be able to
1286 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1287
1288 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1289 everything on my own, and I had long lists of prices seen on different
1290 planets to be able to decide where to trade what. This time I had the
1291 advantages of the
1292 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1293 where information about each planet is easily available with common
1294 price ranges and suggested trading routes. This improved my ability
1295 to earn money and I have been able to earn enough to buy a lot of
1296 useful equipent in a few days. I believe I originally played for
1297 months before I could get a docking computer, while now I could get it
1298 after less then a week.&lt;/p&gt;
1299
1300 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1301 space, you should try out Oolite. It is available for Linux, MacOSX
1302 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1303
1304 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1305 activities, please send Bitcoin donations to my address
1306 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1307 </description>
1308 </item>
1309
1310 <item>
1311 <title>Quicker Debian installations using eatmydata</title>
1312 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1313 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1314 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1315 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1316 installation system, observing how using
1317 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1318 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1319 speedup around 20-40 percent for Debian Edu, where we install around
1320 1000 packages from within the installer. The eatmydata package
1321 provide a way to disable/delay file system flushing. This is a bit
1322 risky in the general case, as files that should be stored on disk will
1323 stay only in memory a bit longer than expected, causing problems if a
1324 machine crashes at an inconvenient time. But for an installation, if
1325 the machine crashes during installation the process is normally
1326 restarted, and avoiding disk operations as much as possible to speed
1327 up the process make perfect sense.
1328
1329 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1330 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1331 but did not have time to push it any further. But a few months ago I
1332 picked it up again and worked with the libeatmydata package maintainer
1333 Mattia Rizzolo to make it easier for everyone to get this installation
1334 speedup in Debian. Thanks to our cooperation There is now an
1335 eatmydata-udeb package in Debian testing and unstable, and simply
1336 enabling/installing it in debian-installer (d-i) is enough to get the
1337 quicker installations. It can be enabled using preseeding. The
1338 following untested kernel argument should do the trick:&lt;/p&gt;
1339
1340 &lt;blockquote&gt;&lt;pre&gt;
1341 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1342 &lt;/pre&gt;&lt;/blockquote&gt;
1343
1344 &lt;p&gt;This should ask d-i to install the package inside the d-i
1345 environment early in the installation sequence. Having it installed
1346 in d-i in turn will make sure the relevant scripts are called just
1347 after debootstrap filled /target/ with the freshly installed Debian
1348 system to configure apt to run dpkg with eatmydata. This is enough to
1349 speed up the installation process. There is a proposal to
1350 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1351 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1352 tested its impact.&lt;/p&gt;
1353
1354 </description>
1355 </item>
1356
1357 <item>
1358 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1359 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1360 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1361 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1362 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1363 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1364 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1365 elever over det ganske land skal levere inn hvert år. Det mange ikke
1366 vet er at selv om de kommersielle alternativene
1367 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1368 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1369 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1370 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1371 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1372 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1373 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1374 nynorsk, og få den automatoversatt til det andre skriftspråket.
1375 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1376 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1377 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1378 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1379 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1380 teksten din i webskjemaet der.
1381
1382 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1383 teknologien kan du enten installere pakken
1384 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1385 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1386 api.apertium.org. Se
1387 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1388 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1389 denne teksten som ble skrevet på bokmål over maskinoversatt til
1390 nynorsk.&lt;/p&gt;
1391
1392 &lt;hr/&gt;
1393
1394 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1395 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1396 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1397 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1398 veit er at sjølv om dei kommersielle alternativa
1399 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1400 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1401 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1402 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1403 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1404 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1405 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1406 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1407 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1408 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1409 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1410 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1411 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1412 teksta di i *webskjemaet der.
1413
1414 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1415 teknologien kan du anten installera pakken
1416 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1417 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1418 *api.*apertium.org. Sjå
1419 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1420 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1421 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1422 nynorsk.&lt;/p&gt;
1423 </description>
1424 </item>
1425
1426 <item>
1427 <title>Coz profiler for multi-threaded software is now in Debian</title>
1428 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1429 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1430 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1431 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1432 profiler able to run benchmarking experiments on the instrumented
1433 multi-threaded program, finally
1434 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1435 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1436 months since
1437 &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
1438 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1439 it suitable for Debian. There are still issues with clang
1440 compatibility, inline assembly only working x86 and minimized
1441 JavaScript libraries.&lt;/p&gt;
1442
1443 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1444
1445 &lt;p&gt;&lt;blockquote&gt;
1446 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1447 &lt;/blockquote&gt;&lt;/p&gt;
1448
1449 &lt;p&gt;This will produce a profile.coz file in the current working
1450 directory with the profiling information. This is then given to a
1451 JavaScript application provided in the package and available from
1452 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1453 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1454
1455 &lt;p&gt;&lt;blockquote&gt;
1456 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1457 &lt;/blockquote&gt;&lt;/p&gt;
1458
1459 &lt;p&gt;See the project home page and the
1460 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1461 ;login: article on Coz&lt;/a&gt; for more information on how it is
1462 working.&lt;/p&gt;
1463 </description>
1464 </item>
1465
1466 <item>
1467 <title>My own self balancing Lego Segway</title>
1468 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1470 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1471 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1472 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1473 present. It had been on my wishlist for a while, because I wanted to
1474 build a Segway like balancing lego robot. I had already built
1475 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1476 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1477 NXT kit as the balance sensor, but it was not working very well. It
1478 could balance for a while, but was very sensitive to the light
1479 condition in the room and the reflective properties of the surface and
1480 would fall over after a short while. I wanted something more robust,
1481 and had
1482 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1483 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1484 wishlist for some years before it suddenly showed up as a gift from my
1485 loved ones. :)&lt;/p&gt;
1486
1487 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1488 since then. But that changed some days ago, when I was searching for
1489 lego segway information and came across a recipe from HiTechnic for
1490 building
1491 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1492 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1493 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1494 code&lt;/a&gt; was included, so it was just a question of putting it all
1495 together. And thanks to the great work of many Debian developers, the
1496 compiler needed to build the source for the NXT is already included in
1497 Debian, so I was read to go in less than an hour. The resulting robot
1498 do not look very impressive in its simplicity:&lt;/p&gt;
1499
1500 &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;
1501
1502 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
1503 design from HiTechnic, I had to comment out the last task
1504 (taskControl). I simply placed /* and */ around it get the program
1505 working without that sensor present. Now it balances just fine until
1506 the battery status run low:&lt;/p&gt;
1507
1508 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
1509 &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;
1510 &lt;/video&gt;&lt;/p&gt;
1511
1512 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
1513 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
1514
1515 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
1516 they need to work with LEGO in Debian and all our derivative
1517 distributions like Ubuntu, check out
1518 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
1519 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
1520 RCX and NXT controller (no EV3), and would like to make sure the
1521 Debian tools needed to program the systems I own work as they
1522 should.&lt;/p&gt;
1523 </description>
1524 </item>
1525
1526 <item>
1527 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
1528 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
1529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
1530 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
1531 <description>&lt;p&gt;In July
1532 &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
1533 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
1534 the ability to receive SMS messages (aka without a cell phone). It is
1535 time to share some experiences and provide an updated setup.&lt;/p&gt;
1536
1537 &lt;p&gt;The Signal app have worked fine for several months now, and I use
1538 it regularly to chat with my loved ones. I had a major snag at the
1539 end of my summer vacation, when the the app completely forgot my
1540 setup, identity and keys. The reason behind this major mess was
1541 running out of disk space. To avoid that ever happening again I have
1542 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
1543 roll back to an earlier version if the files are wiped by mistake. I
1544 had to use it once after introducing the git backup. When rolling
1545 back to an earlier version, one need to use the &#39;reset session&#39; option
1546 in Signal to get going, and notify the people you talk with about the
1547 problem. I assume there is some sequence number tracking in the
1548 protocol to detect rollback attacks. The git repository is rather big
1549 (674 MiB so far), but I have not tried to figure out if some of the
1550 content can be added to a .gitignore file due to lack of spare
1551 time.&lt;/p&gt;
1552
1553 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
1554 make it impossible to send messages using Signal. I could still
1555 receive them, but had to patch the code with a new timestamp to send.
1556 I believe the timeout is added by the developers to force people to
1557 upgrade to the latest version of the app, even when there is no
1558 protocol changes, to reduce the version skew among the user base and
1559 thus try to keep the number of support requests down.&lt;/p&gt;
1560
1561 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
1562 making the old patch fail to apply cleanly. Below is an updated
1563 patch, including the shell wrapper I use to start Signal. The
1564 original version required a new user to locate the JavaScript console
1565 and call a function from there. I got help from a friend with more
1566 JavaScript knowledge than me to modify the code to provide a GUI
1567 button instead. This mean that to get started you just need to run
1568 the wrapper and click the &#39;Register without mobile phone&#39; to get going
1569 now. I&#39;ve also modified the timeout code to always set it to 90 days
1570 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
1571
1572 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
1573
1574 &lt;ol&gt;
1575
1576 &lt;li&gt;First, install required packages to get the source code and the
1577 browser you need. Signal only work with Chrome/Chromium, as far as I
1578 know, so you need to install it.
1579
1580 &lt;pre&gt;
1581 apt install git tor chromium
1582 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1583 &lt;/pre&gt;&lt;/li&gt;
1584
1585 &lt;li&gt;Modify the source code using command listed in the the patch
1586 block below.&lt;/li&gt;
1587
1588 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
1589 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
1590
1591 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
1592 number you can receive calls to the next minute, receive the
1593 verification code and enter it into the form field and press
1594 &#39;Register&#39;. Note, the phone number you use will be user Signal
1595 username, ie the way others can find you on Signal.&lt;/li&gt;
1596
1597 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
1598 not show up in the contact list until you restart Signal, and there is
1599 no way to assign names to Contacts. There is also no way to create or
1600 update chat groups. I suspect this is because the web app do not have
1601 a associated contact database.&lt;/li&gt;
1602
1603 &lt;/ol&gt;
1604
1605 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
1606 main author moxie0 reject federation and accept dependencies to major
1607 corporations like Google (part of the code is fetched from Google) and
1608 Amazon (the central coordination point is owned by Amazon). See for
1609 example
1610 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
1611 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
1612 view on these issues. But the network effect is strong in this case,
1613 and several of the people I want to communicate with already use
1614 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
1615 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
1616 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
1617 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
1618 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
1619 working on Debian Stable.&lt;/p&gt;
1620
1621 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
1622 working. It switch to the production servers, disable to timeout,
1623 make registration easier and add the shell wrapper:&lt;/p&gt;
1624
1625 &lt;pre&gt;
1626 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
1627 diff --git a/js/background.js b/js/background.js
1628 index 24b4c1d..579345f 100644
1629 --- a/js/background.js
1630 +++ b/js/background.js
1631 @@ -33,9 +33,9 @@
1632 });
1633 });
1634
1635 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1636 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
1637 var SERVER_PORTS = [80, 4433, 8443];
1638 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1639 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1640 var messageReceiver;
1641 window.getSocketStatus = function() {
1642 if (messageReceiver) {
1643 diff --git a/js/expire.js b/js/expire.js
1644 index 639aeae..beb91c3 100644
1645 --- a/js/expire.js
1646 +++ b/js/expire.js
1647 @@ -1,6 +1,6 @@
1648 ;(function() {
1649 &#39;use strict&#39;;
1650 - var BUILD_EXPIRATION = 0;
1651 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
1652
1653 window.extension = window.extension || {};
1654
1655 diff --git a/js/views/install_view.js b/js/views/install_view.js
1656 index 7816f4f..1d6233b 100644
1657 --- a/js/views/install_view.js
1658 +++ b/js/views/install_view.js
1659 @@ -38,7 +38,8 @@
1660 return {
1661 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
1662 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
1663 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
1664 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
1665 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
1666 };
1667 },
1668 clearQR: function() {
1669 diff --git a/options.html b/options.html
1670 index dc0f28e..8d709f6 100644
1671 --- a/options.html
1672 +++ b/options.html
1673 @@ -14,7 +14,10 @@
1674 &amp;lt;div class=&#39;nav&#39;&gt;
1675 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
1676 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
1677 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
1678 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
1679 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
1680 +
1681 + &amp;lt;/div&gt;
1682 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
1683 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
1684 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
1685 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
1686 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
1687 @@ -0,0 +1,12 @@
1688 +#!/bin/sh
1689 +set -e
1690 +cd $(dirname $0)
1691 +mkdir -p userdata
1692 +userdata=&quot;`pwd`/userdata&quot;
1693 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
1694 + (cd $userdata &amp;&amp; git init)
1695 +fi
1696 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
1697 +exec chromium \
1698 + --proxy-server=&quot;socks://localhost:9050&quot; \
1699 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1700 EOF
1701 chmod a+rx run-signal-app
1702 &lt;/pre&gt;
1703
1704 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1705 activities, please send Bitcoin donations to my address
1706 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1707 </description>
1708 </item>
1709
1710 <item>
1711 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
1712 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
1713 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
1714 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
1715 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1716 system&lt;/a&gt; provide a practical and easy way to figure out which
1717 packages support the hardware in a given machine. The command line
1718 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
1719 convenient way to list and install packages relevant for the current
1720 hardware during system installation, both user space packages and
1721 firmware packages. The GUI background daemon on the other hand provide
1722 a pop-up proposing to install packages when a new dongle is inserted
1723 while using the computer. For example, if you plug in a smart card
1724 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
1725 that package isn&#39;t already installed, and if you plug in a USB video
1726 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
1727 cheese is currently missing. This already work just fine.&lt;/p&gt;
1728
1729 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
1730 package names. When I started no such database existed in Debian, so
1731 I made my own data set and included it with the isenkram package and
1732 made isenkram fetch the latest version of this database from git using
1733 http. This way the isenkram users would get updated package proposals
1734 as soon as I learned more about hardware related packages.&lt;/p&gt;
1735
1736 &lt;p&gt;The hardware is identified using modalias strings. The modalias
1737 design is from the Linux kernel where most hardware descriptors are
1738 made available as a strings that can be matched using filename style
1739 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1740 identifiers.&lt;/p&gt;
1741
1742 &lt;p&gt;The downside to the Isenkram specific database is that there is no
1743 information about relevant distribution / Debian version, making
1744 isenkram propose obsolete packages too. But along came AppStream, a
1745 cross distribution mechanism to store and collect metadata about
1746 software packages. When I heard about the proposal, I contacted the
1747 people involved and suggested to add a hardware matching rule using
1748 modalias strings in the specification, to be able to use AppStream for
1749 mapping hardware to packages. This idea was accepted and AppStream is
1750 now a great way for a package to announce the hardware it support in a
1751 distribution neutral way. I wrote
1752 &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
1753 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
1754 December. If you have a hardware related package in Debian, please
1755 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
1756
1757 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
1758 RCX or NXT unit, announce this support using AppStream. The effect is
1759 that when you insert such LEGO robot controller into your Debian
1760 machine, Isenkram will propose to install the packages needed to get
1761 it working. The intention is that this should allow the local user to
1762 start programming his robot controller right away without having to
1763 guess what packages to use or which permissions to fix.&lt;/p&gt;
1764
1765 &lt;p&gt;But when I sat down with my son the other day to program our NXT
1766 unit using his Debian Stretch computer, I discovered something
1767 annoying. The local console user (ie my son) did not get access to
1768 the USB device for programming the unit. This used to work, but no
1769 longer in Jessie and Stretch. After some investigation and asking
1770 around on #debian-devel, I discovered that this was because udev had
1771 changed the mechanism used to grant access to local devices. The
1772 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
1773 no longer applied, because LDAP users no longer was added to the
1774 plugdev group during login. Michael Biebl told me that this method
1775 was obsolete and the new method used ACLs instead. This was good
1776 news, as the plugdev mechanism is a mess when using a remote user
1777 directory like LDAP. Using ACLs would make sure a user lost device
1778 access when she logged out, even if the user left behind a background
1779 process which would retain the plugdev membership with the ConsoleKit
1780 setup. Armed with this knowledge I moved on to fix the access problem
1781 for the LEGO Mindstorms related packages.&lt;/p&gt;
1782
1783 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
1784 applied directly for a device, or is applied in
1785 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
1786 LEGO Mindstorms udev rules did not have a class, I decided to add the
1787 tag directly in the udev rules files included in the packages. Here
1788 is one example. For the nqc C compiler for the RCX, the
1789 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
1790
1791 &lt;p&gt;&lt;pre&gt;
1792 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
1793 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
1794 &lt;/pre&gt;&lt;/p&gt;
1795
1796 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
1797 packages using plugdev in their /lib/udev/rules.d/ files should be
1798 changed to use this tag (either directly or indirectly via
1799 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
1800 to detect this?&lt;/p&gt;
1801
1802 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
1803 It is unclear to me if the uaccess tag is an internal implementation
1804 detail like the udev-acl tag used by
1805 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
1806 indirect method is the preferred way. Michael
1807 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
1808 documentation from the systemd project&lt;/a&gt; and I hope it will make
1809 this clearer. For now I use the generic classes when they exist and
1810 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
1811 directly if no such class exist.&lt;/p&gt;
1812
1813 &lt;p&gt;To learn more about the isenkram system, please check out
1814 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1815 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1816
1817 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
1818 please join us on our IRC channel
1819 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
1820 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
1821 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
1822 list is not yet created, but we are working on it. :)&lt;/p&gt;
1823
1824 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1825 activities, please send Bitcoin donations to my address
1826 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1827 </description>
1828 </item>
1829
1830 <item>
1831 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
1832 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
1833 <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>
1834 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
1835 <description>&lt;p&gt;In April we
1836 &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
1837 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
1838 how to set up and administrate a Debian system. Today I am happy to
1839 report that the first draft is now publicly available. You can find
1840 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
1841 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
1842 eight chapters have a first draft translation, and we are working on
1843 proofreading the content. If you want to help out, please start
1844 contributing using
1845 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1846 hosted weblate project page&lt;/a&gt;, and get in touch using
1847 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1848 translators mailing list&lt;/a&gt;. Please also check out
1849 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1850 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
1851 and update weblate if you find errors.&lt;/p&gt;
1852
1853 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
1854 electronic form.&lt;/p&gt;
1855 </description>
1856 </item>
1857
1858 <item>
1859 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
1860 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
1861 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
1862 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
1863 <description>&lt;p&gt;This summer, I read a great article
1864 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
1865 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
1866 how to profile multi-threaded programs. It presented a system for
1867 profiling software by running experiences in the running program,
1868 testing how run time performance is affected by &quot;speeding up&quot; parts of
1869 the code to various degrees compared to a normal run. It does this by
1870 slowing down parallel threads while the &quot;faster up&quot; code is running
1871 and measure how this affect processing time. The processing time is
1872 measured using probes inserted into the code, either using progress
1873 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1874 can also measure unmodified code by measuring complete the program
1875 runtime and running the program several times instead.&lt;/p&gt;
1876
1877 &lt;p&gt;The project and presentation was so inspiring that I would like to
1878 get the system into Debian. I
1879 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
1880 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
1881 system ready for Debian by sending patches. The build process need to
1882 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
1883 to include the JavaScript web page used to visualize the collected
1884 profiling information included in the source package.
1885 But I expect that should work out fairly soon.&lt;/p&gt;
1886
1887 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
1888 on a binary with debug symbols available, start the program like this:
1889
1890 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1891 coz run --- program-to-run
1892 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1893
1894 &lt;p&gt;This will create a text file profile.coz with the instrumentation
1895 information. To show what part of the code affect the performance
1896 most, use a web browser and either point it to
1897 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
1898 or use the copy from git (in the gh-pages branch). Check out this web
1899 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
1900 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
1901 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1902 code, rebuild and run the profiler. This allow coz to do more
1903 targeted experiments.&lt;/p&gt;
1904
1905 &lt;p&gt;A video published by ACM
1906 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
1907 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
1908 from the 25th Symposium on Operating Systems Principles available
1909 titled
1910 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
1911 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
1912
1913 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
1914 for Coz is available from github. It will only build with clang
1915 because it uses a
1916 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
1917 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
1918 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
1919 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
1920
1921 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
1922 of software in Debian. I would very much like some help with the
1923 packaging effort, as I lack the in depth knowledge on how to package
1924 C++ libraries.&lt;/p&gt;
1925 </description>
1926 </item>
1927
1928 <item>
1929 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
1930 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
1931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
1932 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
1933 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1934 to be a slight challenge. Here is the recipe if I ever need to do it
1935 again. It all started by me wanting to try the recipe to set up
1936 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
1937 hardened Android installation&lt;/a&gt; from the Tor project blog on a
1938 device I had access to. It is a old mobile phone with a broken
1939 microphone The initial idea had been to just
1940 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
1941 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
1942 until a few days ago.&lt;/p&gt;
1943
1944 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
1945 loader (press volume down and power at the same time), (2) select
1946 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
1947 machine, (4) request the device identifier token by running &#39;fastboot
1948 oem get_identifier_token&#39;, (5) request the device unlocking key using
1949 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
1950 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
1951
1952 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
1953 or newer, and the device I was working on had 2.00.0027. This
1954 apparently can be easily fixed by downloading a Windows program and
1955 running it on your Windows machine, if you accept the terms Microsoft
1956 require you to accept to use Windows - which I do not. So I had to
1957 come up with a different approach. I got a lot of help from AndyCap
1958 on #nuug, and would not have been able to get this working without
1959 him.&lt;/p&gt;
1960
1961 &lt;p&gt;First I needed to extract the hboot firmware from
1962 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
1963 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
1964 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
1965 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
1966 recognise the file format, but unruu worked and extracted rom.zip,
1967 containing the new hboot firmware and a text file describing which
1968 devices it would work for.&lt;/p&gt;
1969
1970 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
1971 followed some instructions
1972 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
1973 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
1974 machine with Debian testing:&lt;/p&gt;
1975
1976 &lt;p&gt;&lt;pre&gt;
1977 adb reboot-bootloader
1978 fastboot oem rebootRUU
1979 fastboot flash zip rom.zip
1980 fastboot flash zip rom.zip
1981 fastboot reboot
1982 &lt;/pre&gt;&lt;/p&gt;
1983
1984 &lt;p&gt;The flash command apparently need to be done twice to take effect,
1985 as the first is just preparations and the second one do the flashing.
1986 The adb command is just to get to the boot loader menu, so turning the
1987 device on while holding volume down and the power button should work
1988 too.&lt;/p&gt;
1989
1990 &lt;p&gt;With the new hboot version in place I could start following the
1991 instructions on the HTC developer web site. I got the device token
1992 like this:&lt;/p&gt;
1993
1994 &lt;p&gt;&lt;pre&gt;
1995 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
1996 &lt;/pre&gt;
1997
1998 &lt;p&gt;And once I got the unlock code via email, I could use it like
1999 this:&lt;/p&gt;
2000
2001 &lt;p&gt;&lt;pre&gt;
2002 fastboot flash unlocktoken Unlock_code.bin
2003 &lt;/pre&gt;&lt;/p&gt;
2004
2005 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2006 could start stuffing the software of my own choosing into the device.
2007 So far I only inserted a replacement recovery image to wipe the phone
2008 before I start. We will see what happen next. Perhaps I should
2009 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2010 </description>
2011 </item>
2012
2013 <item>
2014 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2015 <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>
2016 <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>
2017 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2018 <description>&lt;p&gt;For a while now, I have wanted to test
2019 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2020 said to provide end to end encrypted communication and several of my
2021 friends and family are already using it. As I by choice do not own a
2022 mobile phone, this proved to be harder than expected. And I wanted to
2023 have the source of the client and know that it was the code used on my
2024 machine. But yesterday I managed to get it working. I used the
2025 Github source, compared it to the source in
2026 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2027 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2028 patches to use the production Signal servers, started the app and
2029 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2030 the recipe how I did it.&lt;/p&gt;
2031
2032 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2033
2034 &lt;pre&gt;
2035 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2036 &lt;/pre&gt;
2037
2038 &lt;p&gt;Next, I patched the source to use the production servers, to be
2039 able to talk to other Signal users:&lt;/p&gt;
2040
2041 &lt;pre&gt;
2042 cat &amp;lt;&amp;lt;EOF | patch -p0
2043 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2044 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2045 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2046 @@ -47,8 +47,8 @@
2047 });
2048 });
2049
2050 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2051 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2052 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2053 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2054 var messageReceiver;
2055 window.getSocketStatus = function() {
2056 if (messageReceiver) {
2057 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2058 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2059 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2060 @@ -1,6 +1,6 @@
2061 ;(function() {
2062 &#39;use strict&#39;;
2063 - var BUILD_EXPIRATION = 0;
2064 + var BUILD_EXPIRATION = 1474492690000;
2065
2066 window.extension = window.extension || {};
2067
2068 EOF
2069 &lt;/pre&gt;
2070
2071 &lt;p&gt;The first part is changing the servers, and the second is updating
2072 an expiration timestamp. This timestamp need to be updated regularly.
2073 It is set 90 days in the future by the build process (Gruntfile.js).
2074 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2075
2076 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2077 script to launch Signal in Chromium.&lt;/p&gt;
2078
2079 &lt;pre&gt;
2080 #!/bin/sh
2081 cd $(dirname $0)
2082 mkdir -p userdata
2083 exec chromium \
2084 --proxy-server=&quot;socks://localhost:9050&quot; \
2085 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2086 &lt;/pre&gt;
2087
2088 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2089 SOCKS5 proxy to make sure those controlling the Signal servers (today
2090 Amazon and Whisper Systems) as well as those listening on the lines
2091 will have a harder time location my laptop based on the Signal
2092 connections if they use source IP address.&lt;/p&gt;
2093
2094 &lt;p&gt;When the script starts, one need to follow the instructions under
2095 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2096 repository. I right clicked on the Signal window to get up the
2097 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2098 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2099 registration form. Then I entered by land line phone number and
2100 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2101 repeated the verification code three times. After entering the number
2102 into the verification code field in the form, I could start using
2103 Signal from my laptop.
2104
2105 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2106 whom and thus who know who to those controlling the central server,
2107 but such leakage is hard to avoid with a centrally controlled server
2108 setup. It is something to keep in mind when using Signal - the
2109 content of your chats are harder to intercept, but the meta data
2110 exposing your contact network is available to people you do not know.
2111 So better than many options, but not great. And sadly the usage is
2112 connected to my land line, thus allowing those controlling the server
2113 to associate it to my home and person. I would prefer it if only
2114 those I knew could tell who I was on Signal. There are options
2115 avoiding such information leakage, but most of my friends are not
2116 using them, so I am stuck with Signal for now.&lt;/p&gt;
2117
2118 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2119 on this topic in
2120 &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
2121 and updated recipe for using the Signal app without a mobile
2122 phone&lt;/a&gt;.&lt;/p&gt;
2123 </description>
2124 </item>
2125
2126 <item>
2127 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2128 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2129 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2130 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2131 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2132 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2133 multimedia player in Debian claimed to support most file formats /
2134 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2135 the various players claimed support for. The range was from 55 to 130
2136 MIME types. I suspect most media formats are supported by all
2137 players, but this is not really reflected in the MimeTypes values in
2138 their desktop files. There are probably also some bogus MIME types
2139 listed, but it is hard to identify which one this is.&lt;/p&gt;
2140
2141 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2142 the players suggesting to add more MIME types to their desktop files,
2143 and decided to spend some time myself improving the situation for my
2144 favorite media player VLC. The fixes for VLC entered Debian unstable
2145 yesterday. The complete list of MIME types can be seen on the
2146 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2147 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2148
2149 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2150 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2151 kmplayer. I am sure some of the other players desktop files support
2152 several of the formats currently listed as working only with vlc,
2153 toten and parole.&lt;/p&gt;
2154
2155 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2156 supported by all the tested multimedia players in Debian in their
2157 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2158 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2159 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2160 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2161 it sad that video/ogg and video/webm is not supported by all the media
2162 players in Debian. As far as I can tell, all of them can handle both
2163 formats.&lt;/p&gt;
2164 </description>
2165 </item>
2166
2167 <item>
2168 <title>A program should be able to open its own files on Linux</title>
2169 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2171 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2172 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2173 decided to test its presentation tool when making the slides for a
2174 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2175 wrote the first draft of the slides, saved the result and went to bed
2176 the day before I would give the talk. The next day I took a plane to
2177 the location where the meeting should take place, and on the plane I
2178 started up koffice again to polish the talk a bit, only to discover
2179 that kpresenter refused to load its own data file. I cursed a bit and
2180 started making the slides again from memory, to have something to
2181 present when I arrived. I tested that the saved files could be
2182 loaded, and the day seemed to be rescued. I continued to polish the
2183 slides until I suddenly discovered that the saved file could no longer
2184 be loaded into kpresenter. In the end I had to rewrite the slides
2185 three times, condensing the content until the talk became shorter and
2186 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2187 kpresenter wrote inline images in a way itself could not understand.
2188 Eventually that bug was fixed and kpresenter ended up being a great
2189 program to make slides. The point I&#39;m trying to make is that we
2190 expect a program to be able to load its own data files, and it is
2191 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2192
2193 &lt;p&gt;Did you ever experience a program failing to load its own data
2194 files from the desktop file browser? It is not a uncommon problem. A
2195 while back I discovered that the screencast recorder
2196 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2197 browser would refuse to open. No video player claimed to understand
2198 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2199 returning the application/ogg MIME type, which no video player I had
2200 installed listed as a MIME type they would understand. I asked for
2201 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2202 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2203 several video players to add video/ogg to their desktop files, to give
2204 the file browser an idea what to do about Ogg Theora files. After a
2205 while, the desktop file browsers in Debian started to handle the
2206 output from gtk-recordmydesktop properly.&lt;/p&gt;
2207
2208 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2209 system Rosegarden again, and I discovered that the KDE and xfce file
2210 browsers did not know what to do with the Rosegarden project files
2211 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2212 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2213 included in the next upload. To increase the chance of me remembering
2214 how to fix the problem next time some program fail to load its files
2215 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2216
2217 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2218 There are two sources for the MIME type of a given file. The output from
2219 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2220 shared MIME type registry (under /usr/share/mime/). The file MIME
2221 type is mapped to programs supporting the MIME type, and this
2222 information is collected from
2223 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2224 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2225 one desktop file claiming support for the MIME type of the file, it is
2226 activated when asking to open a given file. If there are more, one
2227 can normally select which one to use by right-clicking on the file and
2228 selecting the wanted one using &#39;Open with&#39; or similar. In general
2229 this work well. But it depend on each program picking a good MIME
2230 type (preferably
2231 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2232 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2233 registry recognizing the file and the desktop file to list the MIME
2234 type in its list of supported MIME types.&lt;/p&gt;
2235
2236 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2237 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2238 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2239
2240 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2241 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2242 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2243 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2244 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2245 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2246 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2247 &amp;lt;/mime-type&amp;gt;
2248 &amp;lt;/mime-info&amp;gt;
2249 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2250
2251 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2252 (it is a gzipped XML file). Note, it is much better to use an
2253 official MIME type registered with IANA than it is to make up ones own
2254 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2255
2256 &lt;p&gt;The desktop file of the rosegarden program failed to list
2257 audio/x-rosegarden in its list of supported MIME types, causing the
2258 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2259
2260 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2261 % grep Mime /usr/share/applications/rosegarden.desktop
2262 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2263 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2264 %
2265 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2266
2267 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2268 MimeType= line.&lt;/p&gt;
2269
2270 &lt;p&gt;If you run into a file which fail to open the correct program when
2271 selected from the file browser, please check out the output from
2272 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2273 MIME type is registered somewhere under /usr/share/mime/ and check
2274 that some desktop file under /usr/share/applications/ is claiming
2275 support for this MIME type. If not, please report a bug to have it
2276 fixed. :)&lt;/p&gt;
2277 </description>
2278 </item>
2279
2280 <item>
2281 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2282 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2283 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2284 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2285 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2286 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2287 related packages. The idea is to have a database of mappings between
2288 hardware and packages, and pop up a dialog suggesting for the user to
2289 install the packages to use a given hardware dongle. Some use cases
2290 are when you insert a Yubikey, it proposes to install the software
2291 needed to control it; when you insert a braille reader list it
2292 proposes to install the packages needed to send text to the reader;
2293 and when you insert a ColorHug screen calibrator it suggests to
2294 install the driver for it. The system work well, and even have a few
2295 command line tools to install firmware packages and packages for the
2296 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2297
2298 &lt;p&gt;The system was initially written using aptdaemon, because I found
2299 good documentation and example code on how to use it. But aptdaemon
2300 is going away and is generally being replaced by
2301 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2302 so Isenkram needed a rewrite. And today, thanks to the great patch
2303 from my college Sunil Mohan Adapa in the FreedomBox project, the
2304 rewrite finally took place. I&#39;ve just uploaded a new version of
2305 Isenkram into Debian Unstable with the patch included, and the default
2306 for the background daemon is now to use PackageKit. To check it out,
2307 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2308 and see if it is recognised.&lt;/p&gt;
2309
2310 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2311 the machine it is running on, you can check out the isenkram-lookup
2312 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2313
2314 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2315 % isenkram-lookup
2316 bluez
2317 cheese
2318 fprintd
2319 fprintd-demo
2320 gkrellm-thinkbat
2321 hdapsd
2322 libpam-fprintd
2323 pidgin-blinklight
2324 thinkfan
2325 tleds
2326 tp-smapi-dkms
2327 tp-smapi-source
2328 tpb
2329 %p
2330 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2331
2332 &lt;p&gt;The hardware mappings come from several places. The preferred way
2333 is for packages to announce their hardware support using
2334 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2335 cross distribution appstream system&lt;/a&gt;.
2336 See
2337 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2338 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2339 </description>
2340 </item>
2341
2342 <item>
2343 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2344 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2346 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2347 <description>&lt;p&gt;Yesterday I updated the
2348 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2349 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2350 enterprising users. There were some nice user and visible changes.
2351 First of all, both desktop menu entries now work. A design flaw in
2352 one of the script made the history graph fail to show up (its PNG was
2353 dumped in ~/.xsession-errors) if no controlling TTY was available.
2354 The script worked when called from the command line, but not when
2355 called from the desktop menu. I changed this to look for a DISPLAY
2356 variable or a TTY before deciding where to draw the graph, and now the
2357 graph window pop up as expected.&lt;/p&gt;
2358
2359 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2360 graphs (the one showing the last few hours). New is also the user of
2361 colours showing charging in blue and discharge in red. The percentages
2362 of this graph is relative to last full charge, not battery design
2363 capacity.&lt;/p&gt;
2364
2365 &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;
2366
2367 &lt;p&gt;The other graph show the entire history of the collected battery
2368 statistics, comparing it to the design capacity of the battery to
2369 visualise how the battery life time get shorter over time. The red
2370 line in this graph is what the previous graph considers 100 percent:
2371
2372 &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;
2373
2374 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2375 percent of last full capacity, and how the capacity of the battery is
2376 shrinking. :(&lt;/p&gt;
2377
2378 &lt;p&gt;The last new feature is in the collector, which now will handle
2379 more hardware models. On some hardware, Linux power supply
2380 information is stored in /sys/class/power_supply/ACAD/, while the
2381 collector previously only looked in /sys/class/power_supply/AC/. Now
2382 both are checked to figure if there is power connected to the
2383 machine.&lt;/p&gt;
2384
2385 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2386 check out the
2387 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2388 in Debian unstable, or rebuild it on Jessie to get it working on
2389 Debian stable. :) The upstream source is available from &lt;a
2390 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2391 Patches are very welcome.&lt;/p&gt;
2392
2393 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2394 activities, please send Bitcoin donations to my address
2395 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2396 </description>
2397 </item>
2398
2399 <item>
2400 <title>Debian now with ZFS on Linux included</title>
2401 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2403 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2404 <description>&lt;p&gt;Today, after many years of hard work from many people,
2405 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2406 Debian. The package status can be seen on
2407 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2408 for zfs-linux&lt;/a&gt;. and
2409 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2410 team status page&lt;/a&gt;. If you want to help out, please join us.
2411 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2412 source code&lt;/a&gt; is available via git on Alioth. It would also be
2413 great if you could help out with
2414 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2415 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2416 </description>
2417 </item>
2418
2419 <item>
2420 <title>What is the best multimedia player in Debian?</title>
2421 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2423 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2424 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2425 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2426
2427 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2428 plugins in Debian, to get an idea which plugins to include in Debian
2429 Edu. I created a script to extract the set of supported MIME types
2430 for each plugin, and used this to find out which multimedia browser
2431 plugin supported most file formats / media types.
2432 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2433 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2434 not been updated for a while. But browser plugins are less relevant
2435 these days, so I thought it was time to look at standalone
2436 players.&lt;/p&gt;
2437
2438 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2439 player when I wanted to play videos from the Norwegian National
2440 Broadcasting Company, and decided to investigate why. The cause is a
2441 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2442 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2443 of MIME types announced in the desktop file and the browser plugin,
2444 only to discover that there is quite a large difference between the
2445 two for VLC. This discovery made me dig up the script I used to
2446 compare browser plugins, and adjust it to compare desktop files
2447 instead, to try to figure out which multimedia player in Debian
2448 support most file formats.&lt;/p&gt;
2449
2450 &lt;p&gt;The result can be seen on the Debian Wiki, as
2451 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2452 table listing all MIME types supported by one of the packages included
2453 in the table&lt;/a&gt;, with the package supporting most MIME types being
2454 listed first in the table.&lt;/p&gt;
2455
2456 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2457 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2458 kmplayer. Time for the other players to update their announced MIME
2459 support?&lt;/p&gt;
2460 </description>
2461 </item>
2462
2463 <item>
2464 <title>The Pyra - handheld computer with Debian preinstalled</title>
2465 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2467 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2468 <description>A friend of mine made me aware of
2469 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2470 handheld computer which will be delivered with Debian preinstalled. I
2471 would love to get one of those for my birthday. :)&lt;/p&gt;
2472
2473 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2474 plugs and many others connectors, and include a full keyboard and a 5&quot;
2475 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2476 day of battery life time, but I have not seen any independent tests
2477 confirming this. The vendor is still collecting preorders, and the
2478 last I heard last night was that 22 more orders were needed before
2479 production started.&lt;/p&gt;
2480
2481 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2482 Debian. Please let me know if you know of any others. Is it the
2483 first computer being sold with Debian preinstalled?&lt;/p&gt;
2484 </description>
2485 </item>
2486
2487 <item>
2488 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2489 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2490 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2491 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2492 <description>&lt;p&gt;During this weekends
2493 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2494 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
2495 to make sure there are good books about Debian available in Norwegian
2496 Bokmål, and got in touch with the people behind the
2497 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
2498 project&lt;/a&gt; to get started. If you want to help out, please start
2499 contributing using
2500 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2501 hosted weblate project page&lt;/a&gt;, and get in touch using
2502 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2503 translators mailing list&lt;/a&gt;. Please also check out
2504 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2505 contributors&lt;/a&gt;.&lt;/p&gt;
2506
2507 &lt;p&gt;The book is already available on paper in English, French and
2508 Japanese, and our goal is to get it available on paper in Norwegian
2509 Bokmål too. In addition to the paper edition, there are also EPUB and
2510 Mobi versions available. And there are incomplete translations
2511 available for many more languages.&lt;/p&gt;
2512 </description>
2513 </item>
2514
2515 <item>
2516 <title>One in two hundred Debian users using ZFS on Linux?</title>
2517 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
2518 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
2519 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
2520 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
2521 packages in Debian, and was quite surprised with what I found. I use
2522 ZFS myself at home, but did not really expect many others to do so.
2523 But I might be wrong.&lt;/p&gt;
2524
2525 &lt;p&gt;According to
2526 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
2527 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
2528 0.53% of the population, with the package installed. As far as I know
2529 the only use of the spl-linux package is as a support library for ZFS
2530 on Linux, so I use it here as proxy for measuring the number of ZFS
2531 installation on Linux in Debian. In the kFreeBSD variant of Debian
2532 the ZFS feature is already available, and there
2533 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
2534 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
2535 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
2536
2537 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
2538 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
2539 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
2540 cleared, the package is still not in Debian. The package is again in
2541 the NEW queue. Several uploads have been rejected so far because the
2542 debian/copyright file was incomplete or wrong, but there is no reason
2543 to give up. The current status can be seen on
2544 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2545 team status page&lt;/a&gt;, and
2546 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
2547 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
2548
2549 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
2550 my home server can function in the future using only official Debian
2551 packages, and the current blocker is to get the debian/copyright file
2552 accepted by the FTP masters in Debian, I decided a while back to try
2553 to help out the team. This was the background for my blog post about
2554 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
2555 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
2556 used the techniques I explored there to try to find any errors in the
2557 copyright file. It is not very easy to check every one of the around
2558 2000 files in the source package, but I hope we this time got it
2559 right. If you want to help out, check out the git source and try to
2560 find missing entries in the debian/copyright file.&lt;/p&gt;
2561 </description>
2562 </item>
2563
2564 <item>
2565 <title>Full battery stats collector is now available in Debian</title>
2566 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
2567 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
2568 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
2569 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
2570 extended collector that will collect the complete battery history for
2571 later processing and graphing. The original collector store the
2572 battery level as percentage of last full level, while the new
2573 collector also record battery vendor, model, serial number, design
2574 full level, last full level and current battery level. This make it
2575 possible to predict the lifetime of the battery as well as visualise
2576 the energy flow when the battery is charging or discharging.&lt;/p&gt;
2577
2578 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
2579 in the version 0.5.1 package in unstable. Get the new battery level graph
2580 and lifetime prediction by running:
2581
2582 &lt;p&gt;&lt;pre&gt;
2583 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2584 &lt;/pre&gt;&lt;/p&gt;
2585
2586 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
2587
2588 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
2589 entry yet):&lt;/p&gt;
2590
2591 &lt;p&gt;&lt;pre&gt;
2592 /usr/share/battery-stats/battery-stats-graph-flow
2593 &lt;/pre&gt;&lt;/p&gt;
2594
2595 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
2596 when there are few data points. The graphs look a bit better with a
2597 few years of data.&lt;/p&gt;
2598
2599 &lt;p&gt;A while back one important feature I use in the battery stats
2600 collector broke in Debian. The scripts in
2601 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
2602 suspect it happened when Jessie started using systemd, but I do not
2603 know. The issue is reported as
2604 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
2605 pm-utils. I managed to work around it by adding an udev rule to call
2606 the collector script every time the power connector is connected and
2607 disconnected. With this fix in place it was finally time to make a
2608 new release of the package, and get it into Debian.&lt;/p&gt;
2609
2610 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2611 check out the
2612 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2613 in Debian unstable, or rebuild it on Jessie to get it working on
2614 Debian stable. :) The upstream source is available from
2615 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2616 As always, patches are very welcome.&lt;/p&gt;
2617 </description>
2618 </item>
2619
2620 <item>
2621 <title>Making battery measurements a little easier in Debian</title>
2622 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
2623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
2624 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
2625 <description>&lt;p&gt;Back in September, I blogged about
2626 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
2627 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
2628 how it showed the decay and death of this battery (now replaced). I
2629 created a simple deb package to handle the collection and graphing,
2630 but did not want to upload it to Debian as there were already
2631 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
2632 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
2633 a point of uploading a competing package when battery-stats could be
2634 fixed instead. I reported a few bugs about its non-function, and
2635 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
2636
2637 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
2638 hands. The end result is that I am now the new upstream developer of
2639 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
2640 battery-stats in Debian, and the package in Debian unstable is finally
2641 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
2642 information provided by the Linux kernel. If you install the
2643 battery-stats package from unstable now, you will be able to get a
2644 graph of the current battery fill level, to get some idea about the
2645 status of the battery. The source package build and work just fine in
2646 Debian testing and stable (and probably oldstable too, but I have not
2647 tested). The default graph you get for that system look like this:&lt;/p&gt;
2648
2649 &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;
2650
2651 &lt;p&gt;My plans for the future is to merge my old scripts into the
2652 battery-stats package, as my old scripts collected a lot more details
2653 about the battery. The scripts are merged into the upstream
2654 battery-stats git repository already, but I am not convinced they work
2655 yet, as I changed a lot of paths along the way. Will have to test a
2656 bit more before I make a new release.&lt;/p&gt;
2657
2658 &lt;p&gt;I will also consider changing the file format slightly, as I
2659 suspect the way I combine several values into one field might make it
2660 impossible to know the type of the value when using it for processing
2661 and graphing.&lt;/p&gt;
2662
2663 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
2664 battery, check out the battery-stats package in
2665 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
2666 on
2667 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2668 I would love some help to improve the system further.&lt;/p&gt;
2669 </description>
2670 </item>
2671
2672 <item>
2673 <title>Creating, updating and checking debian/copyright semi-automatically</title>
2674 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
2675 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
2676 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
2677 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
2678 details. And one of the details is the content of the
2679 debian/copyright file, which should list all relevant licenses used by
2680 the code in the package in question, preferably in
2681 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
2682 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
2683
2684 &lt;p&gt;For large packages with lots of contributors it is hard to write
2685 and update this file manually, and if you get some detail wrong, the
2686 package is normally rejected by the ftpmasters. So getting it right
2687 the first time around get the package into Debian faster, and save
2688 both you and the ftpmasters some work.. Today, while trying to figure
2689 out what was wrong with
2690 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
2691 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
2692 figuring out the options for doing this job automatically, or at least
2693 semi-automatically.&lt;/p&gt;
2694
2695 &lt;p&gt;Lucikly, there are at least two tools available for generating the
2696 file based on the code in the source package,
2697 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
2698 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
2699 not sure which one of them came first, but both seem to be able to
2700 create a sensible draft file. As far as I can tell, none of them can
2701 be trusted to get the result just right, so the content need to be
2702 polished a bit before the file is OK to upload. I found the debmake
2703 option in
2704 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
2705 blog posts from 2014&lt;/a&gt;.
2706
2707 &lt;p&gt;To generate using debmake, use the -cc option:
2708
2709 &lt;p&gt;&lt;pre&gt;
2710 debmake -cc &gt; debian/copyright
2711 &lt;/pre&gt;&lt;/p&gt;
2712
2713 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
2714 this might not be the best option.&lt;/p&gt;
2715
2716 &lt;p&gt;The cme option is based on a config parsing library, and I found
2717 this approach in
2718 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
2719 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
2720 dpkg-copyright&#39; option:
2721
2722 &lt;p&gt;&lt;pre&gt;
2723 cme update dpkg-copyright
2724 &lt;/pre&gt;&lt;/p&gt;
2725
2726 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
2727 handle UTF-8 names better than debmake.&lt;/p&gt;
2728
2729 &lt;p&gt;When the copyright file is created, I would also like some help to
2730 check if the file is correct. For this I found two good options,
2731 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
2732 to focus on license types and file matching, and is able to detect
2733 ineffective blocks in the copyright file. The latter reports missing
2734 copyright holders and years, but was confused by inconsistent license
2735 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
2736 fix all issues reported by them before uploading. But I do not know
2737 if the tools and the ftpmasters agree on what is important to fix in a
2738 copyright file, so the package might still be rejected.&lt;/p&gt;
2739
2740 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
2741 will read through the source and try to find all copyright statements.
2742 It is not comparing the result to the content of debian/copyright, but
2743 can be useful when verifying the content of the copyright file.&lt;/p&gt;
2744
2745 &lt;p&gt;Are you aware of better tools in Debian to create and update
2746 debian/copyright file. Please let me know, or blog about it on
2747 planet.debian.org.&lt;/p&gt;
2748
2749 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2750 activities, please send Bitcoin donations to my address
2751 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2752
2753 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
2754 on how to use licensecheck and cdbs to create a draft copyright file
2755
2756 &lt;p&gt;&lt;pre&gt;
2757 licensecheck --copyright -r `find * -type f` | \
2758 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
2759 &lt;/pre&gt;&lt;/p&gt;
2760
2761 &lt;p&gt;He mentioned that he normally check the generated file into the
2762 version control system to make it easier to discover license and
2763 copyright changes in the upstream source. I will try to do the same
2764 with my packages in the future.&lt;/p&gt;
2765
2766 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
2767 against using -quiet for new users, so I removed it from the proposed
2768 command line.&lt;/p&gt;
2769 </description>
2770 </item>
2771
2772 <item>
2773 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
2774 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
2775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
2776 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
2777 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
2778 is taking shape in Debian, and one provided feature is a very
2779 convenient way to tell you which package to install to make a given
2780 firmware file available when the kernel is looking for it. This can
2781 be done using apt-file too, but that is for someone else to blog
2782 about. :)&lt;/p&gt;
2783
2784 &lt;p&gt;Here is a small recipe to find the package with a given firmware
2785 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
2786 picked from the set of firmware announced using appstream in Debian
2787 unstable. In general you would be looking for the firmware requested
2788 by the kernel during kernel module loading. To find the package
2789 providing the example file, do like this:&lt;/p&gt;
2790
2791 &lt;blockquote&gt;&lt;pre&gt;
2792 % apt install appstream
2793 [...]
2794 % apt update
2795 [...]
2796 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
2797 awk &#39;/Package:/ {print $2}&#39;
2798 firmware-qlogic
2799 %
2800 &lt;/pre&gt;&lt;/blockquote&gt;
2801
2802 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
2803 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
2804 a way appstream can use.&lt;/p&gt;
2805
2806 &lt;p&gt;This same approach can be used to find any package supporting a
2807 given MIME type. This is very useful when you get a file you do not
2808 know how to handle. First find the mime type using &lt;tt&gt;file
2809 --mime-type&lt;/tt&gt;, and next look up the package providing support for
2810 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2811 and you can find all packages handling this type like this:&lt;/p&gt;
2812
2813 &lt;blockquote&gt;&lt;pre&gt;
2814 % apt install appstream
2815 [...]
2816 % apt update
2817 [...]
2818 % appstreamcli what-provides mimetype image/svg+xml | \
2819 awk &#39;/Package:/ {print $2}&#39;
2820 bkchem
2821 phototonic
2822 inkscape
2823 shutter
2824 tetzle
2825 geeqie
2826 xia
2827 pinta
2828 gthumb
2829 karbon
2830 comix
2831 mirage
2832 viewnior
2833 postr
2834 ristretto
2835 kolourpaint4
2836 eog
2837 eom
2838 gimagereader
2839 midori
2840 %
2841 &lt;/pre&gt;&lt;/blockquote&gt;
2842
2843 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
2844 packages providing appstream metadata.&lt;/p&gt;
2845 </description>
2846 </item>
2847
2848 <item>
2849 <title>Creepy, visualise geotagged social media information - nice free software</title>
2850 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
2851 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
2852 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
2853 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
2854 with the computerised radio beacon known as a mobile phone their
2855 position is tracked by the phone company and often stored for a long
2856 time (like every time a SMS is received or sent). And if their
2857 computerised radio beacon is capable of running programs (often called
2858 mobile apps) downloaded from the Internet, these programs are often
2859 also capable of tracking their location (if the app requested access
2860 during installation). And when these programs send out information to
2861 central collection points, the location is often included, unless
2862 extra care is taken to not send the location. The provided
2863 information is used by several entities, for good and bad (what is
2864 good and bad, depend on your point of view). What is certain, is that
2865 the private sphere and the right to free movement is challenged and
2866 perhaps even eradicated for those announcing their location this way,
2867 when they share their whereabouts with private and public
2868 entities.&lt;/p&gt;
2869
2870 &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;
2871
2872 &lt;p&gt;The phone company logs provide a register of locations to check out
2873 when one want to figure out what the tracked person was doing. It is
2874 unavailable for most of us, but provided to selected government
2875 officials, company staff, those illegally buying information from
2876 unfaithful servants and crackers stealing the information. But the
2877 public information can be collected and analysed, and a free software
2878 tool to do so is called
2879 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
2880 discovered it when I read
2881 &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
2882 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
2883 November 2014, and decided to check if it was available in Debian.
2884 The python program was in Debian, but
2885 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
2886 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
2887 uploaded a new version which did not work quite right, but did not
2888 have time to fix it then. This Christmas I decided to finally try to
2889 get Creepy operational in Debian. Now a fixed version is available in
2890 Debian unstable and testing, and almost all Debian specific patches
2891 are now included
2892 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
2893
2894 &lt;p&gt;The Creepy program visualises geolocation information fetched from
2895 Twitter, Instagram, Flickr and Google+, and allow one to get a
2896 complete picture of every social media message posted recently in a
2897 given area, or track the movement of a given individual across all
2898 these services. Earlier it was possible to use the search API of at
2899 least some of these services without identifying oneself, but these
2900 days it is impossible. This mean that to use Creepy, you need to
2901 configure it to log in as yourself on these services, and provide
2902 information to them about your search interests. This should be taken
2903 into account when using Creepy, as it will also share information
2904 about yourself with the services.&lt;/p&gt;
2905
2906 &lt;p&gt;The picture above show the twitter messages sent from (or at least
2907 geotagged with a position from) the city centre of Oslo, the capital
2908 of Norway. One useful way to use Creepy is to first look at
2909 information tagged with an area of interest, and next look at all the
2910 information provided by one or more individuals who was in the area.
2911 I tested it by checking out which celebrity provide their location in
2912 twitter messages by checkout out who sent twitter messages near a
2913 Norwegian TV station, and next could track their position over time,
2914 making it possible to locate their home and work place, among other
2915 things. A similar technique have been
2916 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
2917 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
2918 tool to discover lying governments, and a useful tool to help people
2919 understand the value of the private information they provide to the
2920 public.&lt;/p&gt;
2921
2922 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
2923 it depend on several python modules currently missing in Jessie (at
2924 least python-instagram, python-flickrapi and
2925 python-requests-toolbelt).&lt;/p&gt;
2926
2927 &lt;p&gt;(I have uploaded
2928 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
2929 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
2930 Creepy program in Debian.)&lt;/p&gt;
2931 </description>
2932 </item>
2933
2934 <item>
2935 <title>Always download Debian packages using Tor - the simple recipe</title>
2936 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
2937 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
2938 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
2939 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
2940 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
2941 that those listening on the Internet lines would have good reason to
2942 believe a computer have a given security hole&lt;/a&gt; if it download a
2943 security fix from a Debian mirror. This is a good reason to always
2944 use encrypted connections to the Debian mirror, to make sure those
2945 listening do not know which IP address to attack. In August, Richard
2946 Hartmann observed that encryption was not enough, when it was possible
2947 to interfere download size to security patches or the fact that
2948 download took place shortly after a security fix was released, and
2949 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
2950 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
2951 was not the first to propose this, as the
2952 &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;
2953 package by Tim Retout already existed to make it easy to convince apt
2954 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
2955 aware of that package when I read the blog post from Richard.&lt;/p&gt;
2956
2957 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
2958 sysadmins, and he set up a Tor hidden service on one of the central
2959 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2960 it possible to download packages directly between two tor nodes,
2961 making sure the network traffic always were encrypted.&lt;/p&gt;
2962
2963 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
2964 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
2965 urls with tor+http and tor+https, and using the hidden service instead
2966 of the official Debian mirror site. I recommend installing
2967 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
2968 done in /etc/.&lt;/p&gt;
2969
2970 &lt;blockquote&gt;&lt;pre&gt;
2971 apt install apt-transport-tor
2972 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
2973 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
2974 &lt;/pre&gt;&lt;/blockquote&gt;
2975
2976 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
2977 the sed commands for these too. The sed command is assuming your are
2978 using the ftp.debian.org Debian mirror. Adjust the command (or just
2979 edit the file manually) to match your mirror.&lt;/p&gt;
2980
2981 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
2982 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
2983 system, and do not work with these tor+http URLs. For
2984 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
2985 which need a recent apt version currently only in unstable. So if you
2986 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
2987
2988 &lt;p&gt;Another advantage from this change is that your machine will start
2989 using Tor regularly and at fairly random intervals (every time you
2990 update the package lists or upgrade or install a new package), thus
2991 masking other Tor traffic done from the same machine. Using Tor will
2992 become normal for the machine in question.&lt;/p&gt;
2993
2994 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
2995 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
2996 enabled. It would be great if it was the default on any Debian
2997 system.&lt;/p&gt;
2998 </description>
2999 </item>
3000
3001 <item>
3002 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3003 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3005 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3006 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3007 call the car license plate numbers in those days. I would write the
3008 numbers down in my little book and compare notes with the other kids
3009 to see how many region codes we had seen and if we had seen some
3010 exotic or special region codes and numbers. It was a fun game to pass
3011 time, as we kids have plenty of it.&lt;/p&gt;
3012
3013 &lt;p&gt;A few days I came across
3014 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3015 project&lt;/a&gt;, a free software project to automatically discover and
3016 report license plates in images and video streams, and provide the
3017 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3018 such system for a while now, because I believe it is a bad idea that the
3019 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3020 number plate recognition&lt;/a&gt; tool only is available in the hands of
3021 the powerful, and want it to be available also for the powerless to
3022 even the score when it comes to surveillance and sousveillance. I
3023 discovered the developer
3024 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3025 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3026 help him get it into shape to get the package uploaded into the Debian
3027 archive.&lt;/p&gt;
3028
3029 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3030 it into Debian, where it currently
3031 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3032 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3033
3034 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3035 for the common folks, ie those not running a large government
3036 surveillance system? Well, I plan to put it in a computer on my bike
3037 and in my car, tracking the cars nearby and allowing me to be notified
3038 when number plates on my watch list are discovered. Another use case
3039 was suggested by a friend of mine, who wanted to set it up at his home
3040 to open the car port automatically when it discovered the plate on his
3041 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3042 capable of placing his license plate number of a piece of cardboard to
3043 open his car port, men replied that it was always unlocked anyway. I
3044 guess for such use case it make sense. I am sure there are other use
3045 cases too, for those with imagination and a vision.&lt;/p&gt;
3046
3047 &lt;p&gt;If you want to build your own version of the Debian package, check
3048 out the upstream git source and symlink ./distros/debian to ./debian/
3049 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3050 package show up in unstable.&lt;/p&gt;
3051 </description>
3052 </item>
3053
3054 <item>
3055 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3056 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3057 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3058 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3059 <description>&lt;p&gt;Around three years ago, I created
3060 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3061 system&lt;/a&gt; to get a more practical solution in Debian for handing
3062 hardware related packages. A GUI system in the isenkram package will
3063 present a pop-up dialog when some hardware dongle supported by
3064 relevant packages in Debian is inserted into the machine. The same
3065 lookup mechanism to detect packages is available as command line
3066 tools in the isenkram-cli package. In addition to mapping hardware,
3067 it will also map kernel firmware files to packages and make it easy to
3068 install needed firmware packages automatically. The key for this
3069 system to work is a good way to map hardware to packages, in other
3070 words, allow packages to announce what hardware they will work
3071 with.&lt;/p&gt;
3072
3073 &lt;p&gt;I started by providing data files in the isenkram source, and
3074 adding code to download the latest version of these data files at run
3075 time, to ensure every user had the most up to date mapping available.
3076 I also added support for storing the mapping in the Packages file in
3077 the apt repositories, but did not push this approach because while I
3078 was trying to figure out how to best store hardware/package mappings,
3079 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3080 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3081 add the hardware mapping into that data set to be able to use
3082 appstream as a data source, and this was accepted at least for the
3083 Debian version of appstream.&lt;/p&gt;
3084
3085 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3086 and today I uploaded a new version 0.20 of isenkram adding support for
3087 appstream as a data source for mapping hardware to packages. The only
3088 package so far using appstream to announce its hardware support is my
3089 pymissile package. I got help from Matthias Klumpp with figuring out
3090 how do add the required
3091 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3092 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3093 this content:&lt;/p&gt;
3094
3095 &lt;blockquote&gt;&lt;pre&gt;
3096 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3097 &amp;lt;component&amp;gt;
3098 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3099 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3100 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3101 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3102 &amp;lt;description&amp;gt;
3103 &amp;lt;p&amp;gt;
3104 Pymissile provides a curses interface to control an original
3105 Marks and Spencer / Striker USB Missile Launcher, as well as a
3106 motion control script to allow a webcamera to control the
3107 launcher.
3108 &amp;lt;/p&amp;gt;
3109 &amp;lt;/description&amp;gt;
3110 &amp;lt;provides&amp;gt;
3111 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3112 &amp;lt;/provides&amp;gt;
3113 &amp;lt;/component&amp;gt;
3114 &lt;/pre&gt;&lt;/blockquote&gt;
3115
3116 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3117 which is a glob style match rule for hardware specific strings
3118 (modalias strings) provided by the Linux kernel. In this case, it
3119 will map to all USB devices with vendor code 1130 and product code
3120 0202.&lt;/p&gt;
3121
3122 &lt;p&gt;Note, it is important that the license of all the metadata files
3123 are compatible to have permissions to aggregate them into archive wide
3124 appstream files. Matthias suggested to use MIT or BSD licenses for
3125 these files. A challenge is figuring out a good id for the data, as
3126 it is supposed to be globally unique and shared across distributions
3127 (in other words, best to coordinate with upstream what to use). But
3128 it can be changed later or, so we went with the package name as
3129 upstream for this project is dormant.&lt;/p&gt;
3130
3131 &lt;p&gt;To get the metadata file installed in the correct location for the
3132 mirror update scripts to pick it up and include its content the
3133 appstream data source, the file must be installed in the binary
3134 package under /usr/share/appdata/. I did this by adding the following
3135 line to debian/pymissile.install:&lt;/p&gt;
3136
3137 &lt;blockquote&gt;&lt;pre&gt;
3138 debian/pymissile.metainfo.xml usr/share/appdata
3139 &lt;/pre&gt;&lt;/blockquote&gt;
3140
3141 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3142 all packages useful on the current computer automatically, and the GUI
3143 pop-up handler will propose to install the package not already
3144 installed if a hardware dongle is inserted into the machine in
3145 question.&lt;/p&gt;
3146
3147 &lt;p&gt;Details of the modalias field in appstream is available from the
3148 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3149
3150 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3151 try running this command on the command line:&lt;/p&gt;
3152
3153 &lt;blockquote&gt;&lt;pre&gt;
3154 cat $(find /sys/devices/|grep modalias)
3155 &lt;/pre&gt;&lt;/blockquote&gt;
3156
3157 &lt;p&gt;To learn more about the isenkram system, please check out
3158 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3159 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3160 </description>
3161 </item>
3162
3163 <item>
3164 <title>The GNU General Public License is not magic pixie dust</title>
3165 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3167 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3168 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3169 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3170 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3171 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3172 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3173
3174 &lt;blockquote&gt;
3175
3176 &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;
3177
3178 &lt;blockquote&gt;
3179 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3180
3181 The first step is to choose a
3182 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3183 code.&lt;br/&gt;
3184
3185 The next step is, when someone fails to follow that copyleft license,
3186 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3187
3188 and its a simple fact of our modern society that such type of
3189 work&lt;br/&gt;
3190
3191 is incredibly expensive to do and incredibly difficult to do.
3192 &lt;/blockquote&gt;
3193
3194 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3195 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3196 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3197 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3198
3199 &lt;p&gt;As the Debian Website
3200 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3201 &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;
3202 imply, public domain and permissively licensed software can lead to
3203 the production of more proprietary software as people discover useful
3204 software, extend it and or incorporate it into their hardware or
3205 software products. Copyleft licenses such as the GNU GPL were created
3206 to close off this avenue to the production of proprietary software but
3207 such licenses are not enough. With the ongoing adoption of Free
3208 Software by individuals and groups, inevitably the community&#39;s
3209 expectations of license compliance are violated, usually out of
3210 ignorance of the way Free Software works, but not always. As Karen
3211 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3212 Freedom&quot;&gt;FaiF&lt;/a&gt;
3213 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3214 copyleft is nothing if no-one is willing and able to stand up in court
3215 to protect it. The reality of today&#39;s world is that legal
3216 representation is expensive, difficult and time consuming. With
3217 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3218 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3219 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3220 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3221 of the Linux project, Debian and other groups against GPL violations.
3222 In March the SFC supported a
3223 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3224 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3225 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3226 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3227 kernel. Since then two of their sponsors pulled corporate funding and
3228 conferences
3229 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3230 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3231 less on corporate funding and more on the broad community of
3232 individuals who support Free Software and copyleft. So the SFC has
3233 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3234 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3235 a community of folks who stand up for copyleft and the GPL by
3236 supporting their work on promoting and supporting copyleft and Free
3237 Software.&lt;/p&gt;
3238
3239 &lt;p&gt;If you support Free Software,
3240 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3241 what the SFC do, agree with their
3242 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3243 principles&lt;/a&gt;, are happy about their
3244 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3245 work on a project that is an SFC
3246 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3247 just want to stand up for copyleft, please join
3248 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3249 Allan Webber&lt;/a&gt;,
3250 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3251 Smith&lt;/a&gt;,
3252 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3253 Bacon&lt;/a&gt;, myself and
3254 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3255 becoming a
3256 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3257 next week your donation will be
3258 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3259 by an anonymous donor. Please also consider asking your employer to
3260 match your donation or become a sponsor of SFC. Don&#39;t forget to
3261 spread the word about your support for SFC via email, your blog and or
3262 social media accounts.&lt;/p&gt;
3263
3264 &lt;/blockquote&gt;
3265
3266 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3267 of Software Freedom Conservancy myself. Perhaps you should be a
3268 supporter too?&lt;/p&gt;
3269 </description>
3270 </item>
3271
3272 <item>
3273 <title>PGP key transition statement for key EE4E02F9</title>
3274 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3275 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3276 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3277 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3278 set it up properly. I wanted to generate it offline and have it
3279 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3280 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3281 time to sit down with an offline machine almost took forever. But
3282 finally I&#39;ve been able to complete the process, and have now moved
3283 from my old GPG key to a new GPG key. See
3284 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3285 full transition statement, signed with both my old and new key&lt;/a&gt; for
3286 the details. This is my new key:&lt;/p&gt;
3287
3288 &lt;pre&gt;
3289 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]
3290 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3291 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3292 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3293 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3294 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3295 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3296 &lt;/pre&gt;
3297
3298 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3299 my old key.&lt;/p&gt;
3300
3301 &lt;p&gt;If you signed my old key
3302 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3303 I&#39;d very much appreciate a signature on my new key, details and
3304 instructions in the transition statement. I m happy to reciprocate if
3305 you have a similarly signed transition statement to present.&lt;/p&gt;
3306 </description>
3307 </item>
3308
3309 <item>
3310 <title>The life and death of a laptop battery</title>
3311 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3312 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3313 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3314 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3315 But this do not last. The last few laptops gave me a feeling that
3316 within a year, the life time is just a fraction of what it used to be,
3317 and it slowly become painful to use the laptop without power connected
3318 all the time. Because of this, when I got a new Thinkpad X230 laptop
3319 about two years ago, I decided to monitor its battery state to have
3320 more hard facts when the battery started to fail.&lt;/p&gt;
3321
3322 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3323
3324 &lt;p&gt;First I tried to find a sensible Debian package to record the
3325 battery status, assuming that this must be a problem already handled
3326 by someone else. I found
3327 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3328 which collects statistics from the battery, but it was completely
3329 broken. I sent a few suggestions to the maintainer, but decided to
3330 write my own collector as a shell script while I waited for feedback
3331 from him. Via
3332 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3333 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3334 discovered
3335 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3336 available in Debian.&lt;/p&gt;
3337
3338 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3339 battery stats ever since. Now my
3340 /var/log/hjemmenett-battery-status.log file contain around 115,000
3341 measurements, from the time the battery was working great until now,
3342 when it is unable to charge above 7% of original capacity. My
3343 collector shell script is quite simple and look like this:&lt;/p&gt;
3344
3345 &lt;pre&gt;
3346 #!/bin/sh
3347 # Inspired by
3348 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3349 # See also
3350 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3351 logfile=/var/log/hjemmenett-battery-status.log
3352
3353 files=&quot;manufacturer model_name technology serial_number \
3354 energy_full energy_full_design energy_now cycle_count status&quot;
3355
3356 if [ ! -e &quot;$logfile&quot; ] ; then
3357 (
3358 printf &quot;timestamp,&quot;
3359 for f in $files; do
3360 printf &quot;%s,&quot; $f
3361 done
3362 echo
3363 ) &gt; &quot;$logfile&quot;
3364 fi
3365
3366 log_battery() {
3367 # Print complete message in one echo call, to avoid race condition
3368 # when several log processes run in parallel.
3369 msg=$(printf &quot;%s,&quot; $(date +%s); \
3370 for f in $files; do \
3371 printf &quot;%s,&quot; $(cat $f); \
3372 done)
3373 echo &quot;$msg&quot;
3374 }
3375
3376 cd /sys/class/power_supply
3377
3378 for bat in BAT*; do
3379 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3380 done
3381 &lt;/pre&gt;
3382
3383 &lt;p&gt;The script is called when the power management system detect a
3384 change in the power status (power plug in or out), and when going into
3385 and out of hibernation and suspend. In addition, it collect a value
3386 every 10 minutes. This make it possible for me know when the battery
3387 is discharging, charging and how the maximum charge change over time.
3388 The code for the Debian package
3389 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3390 available on github&lt;/a&gt;.&lt;/p&gt;
3391
3392 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3393
3394 &lt;pre&gt;
3395 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3396 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3397 [...]
3398 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3399 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3400 &lt;/pre&gt;
3401
3402 &lt;p&gt;I wrote a small script to create a graph of the charge development
3403 over time. This graph depicted above show the slow death of my laptop
3404 battery.&lt;/p&gt;
3405
3406 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3407 dying in a year or two, while the batteries of space probes and
3408 satellites keep working year after year. If we are to believe
3409 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3410 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3411 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3412 all the time, but to stay below 90% of full charge most of the time.
3413 I&#39;ve been told that the Tesla electric cars
3414 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3415 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3416 100% when preparing for a longer trip (not that I would want a car
3417 like Tesla where rights to privacy is abandoned, but that is another
3418 story), which I guess is the option we should have for laptops on
3419 Linux too.&lt;/p&gt;
3420
3421 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3422 stop charging at 80%, unless requested to charge to 100% once in
3423 preparation for a longer trip? I found
3424 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3425 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3426 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3427 load).&lt;/p&gt;
3428
3429 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3430 at the start. I also wonder why the &quot;full capacity&quot; increases some
3431 times, and if it is possible to repeat the process to get the battery
3432 back to design capacity. And I wonder if the discharge and charge
3433 speed change over time, or if this stay the same. I did not yet try
3434 to write a tool to calculate the derivative values of the battery
3435 level, but suspect some interesting insights might be learned from
3436 those.&lt;/p&gt;
3437
3438 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3439 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3440 packages instead of the tp-smapi-dkms package I had tried to use
3441 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3442 and stop. I&#39;ve done so now, but expect my existing battery is toast
3443 and need to be replaced. The proposal is unfortunately Thinkpad
3444 specific.&lt;/p&gt;
3445 </description>
3446 </item>
3447
3448 <item>
3449 <title>New laptop - some more clues and ideas based on feedback</title>
3450 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3452 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3453 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3454 need for a new laptop, and provided very useful feedback. I wish to
3455 thank every one of these. Several pointed me to the possibility of
3456 fixing my X230, and I am already in the process of getting Lenovo to
3457 do so thanks to the on site, next day support contract covering the
3458 machine. But the battery is almost useless (I expect to replace it
3459 with a non-official battery) and I do not expect the machine to live
3460 for many more years, so it is time to plan its replacement. If I did
3461 not have a support contract, it was suggested to find replacement parts
3462 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3463 might present a language barrier as I do not understand French.&lt;/p&gt;
3464
3465 &lt;p&gt;One tip I got was to use the
3466 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3467 compare laptop models. It seem to have more models available than
3468 prisjakt.no. Another tip I got from someone I know have similar
3469 keyboard preferences was that the HP EliteBook 840 keyboard is not
3470 very good, and this matches my experience with earlier EliteBook
3471 keyboards I tested. Because of this, I will not consider it any further.
3472
3473 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3474 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3475 (which is missing from the X240), and is working fairly well with
3476 Debian Sid/Unstable according to
3477 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3478 got on the keyboard quality are not consistent. Some say the keyboard
3479 is good, others say it is ok, while others say it is not very good.
3480 Those with experience from X41 and and X60 agree that the X250
3481 keyboard is not as good as those trusty old laptops, and suggest I
3482 keep and fix my X230 instead of upgrading, or get a used X230 to
3483 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3484 activity and battery status, which is very convenient on my X230. I&#39;m
3485 also told that the CPU fan is running very often, making it a bit
3486 noisy. In any case, the X250 do not work out of the box with Debian
3487 Stable/Jessie, one of my requirements.&lt;/p&gt;
3488
3489 &lt;p&gt;I have also gotten a few vendor proposals, one was
3490 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3491 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3492 The latter look very attractive to me.&lt;/p&gt;
3493
3494 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
3495 as I keep looking for a replacement.&lt;/p&gt;
3496
3497 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
3498 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
3499 different
3500 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
3501 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
3502 </description>
3503 </item>
3504
3505 <item>
3506 <title>Time to find a new laptop, as the old one is broken after only two years</title>
3507 <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>
3508 <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>
3509 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
3510 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
3511 replacement soon. The left 5 cm of the screen on my Thinkpad X230
3512 started flickering yesterday, and I suspect the cause is a broken
3513 cable, as changing the angle of the screen some times get rid of the
3514 flickering.&lt;/p&gt;
3515
3516 &lt;p&gt;My requirements have not really changed since I bought it, and is
3517 still as
3518 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
3519 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
3520 good help from
3521 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
3522 where I could select at least a few of the requirements (mouse pin,
3523 wifi, weight) and go through the rest manually. Three button mouse
3524 and a good keyboard is not available as an option, and all the three
3525 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
3526 G2) lack three mouse buttons). It is also unclear to me how good the
3527 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3528 the keyboard, even if the quality and robustness in the X series have
3529 deteriorated since X41.&lt;/p&gt;
3530
3531 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
3532 seem sensible to me? Are there better services around to search the
3533 set of available laptops for features? Please send me an email if you
3534 have suggestions.&lt;/p&gt;
3535
3536 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
3537 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
3538 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
3539 </description>
3540 </item>
3541
3542 <item>
3543 <title>How to stay with sysvinit in Debian Jessie</title>
3544 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
3545 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
3546 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
3547 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
3548 sysvinit as its boot system by default. But how can one keep using
3549 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3550 courtesy of
3551 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
3552 Schubert&lt;/a&gt; and
3553 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
3554 McVittie&lt;/a&gt;.
3555
3556 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
3557 keep sysvinit as your boot system, create a file
3558 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
3559 you upgrade:&lt;/p&gt;
3560
3561 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3562 Package: systemd-sysv
3563 Pin: release o=Debian
3564 Pin-Priority: -1
3565 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3566
3567 &lt;p&gt;This file content will tell apt and aptitude to not consider
3568 installing systemd-sysv as part of any installation and upgrade
3569 solution when resolving dependencies, and thus tell it to avoid
3570 systemd as a default boot system. The end result should be that the
3571 upgraded system keep using sysvinit.&lt;/p&gt;
3572
3573 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
3574 get sysvinit installed by default (debootstrap used by
3575 debian-installer have no option for this), but one can tell the
3576 installer to switch to sysvinit before the first boot. Either by
3577 using a kernel argument to the installer, or by adding a line to the
3578 preseed file used. First, the kernel command line argument:
3579
3580 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3581 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
3582 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3583
3584 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
3585
3586 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3587 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3588 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3589
3590 &lt;p&gt;One can of course also do this after the first boot by installing
3591 the sysvinit-core package.&lt;/p&gt;
3592
3593 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
3594 sysvinit boot sequence in Debian have several hardware specific bugs
3595 on Linux caused by the fact that it is unpredictable when hardware
3596 devices show up during boot. But on the other hand, the new default
3597 boot system still have a few rough edges I hope will be fixed before
3598 Jessie is released.&lt;/p&gt;
3599
3600 &lt;p&gt;Update 2014-11-26: Inspired by
3601 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
3602 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
3603 line.&lt;/p&gt;
3604 </description>
3605 </item>
3606
3607 <item>
3608 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
3609 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
3610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
3611 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
3612 <description>&lt;p&gt;The right to communicate with your friends and family in private,
3613 without anyone snooping, is a right every citicen have in a liberal
3614 democracy. But this right is under serious attack these days.&lt;/p&gt;
3615
3616 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
3617 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3618 the whisleblower Snowden) more expensive for Internet email,
3619 is to deliver all email using SMTP via Tor. Such SMTP option would be
3620 a nice addition to the FreedomBox project if we could send email
3621 between FreedomBox machines without leaking metadata about the emails
3622 to the people peeking on the wire. I
3623 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
3624 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
3625 lot of useful feedback and suggestions. It also became obvious to me
3626 that this was not a novel idea, as the same idea was tested and
3627 documented by Johannes Berg as early as 2006, and both
3628 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
3629 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
3630 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
3631
3632 &lt;p&gt;To implement such system one need to set up a Tor hidden service
3633 providing the SMTP protocol on port 25, and use email addresses
3634 looking like username@hidden-service-name.onion. With such addresses
3635 the connections to port 25 on hidden-service-name.onion using Tor will
3636 go to the correct SMTP server. To do this, one need to configure the
3637 Tor daemon to provide the hidden service and the mail server to accept
3638 emails for this .onion domain. To learn more about Exim configuration
3639 in Debian and test the design provided by Johannes Berg in his FAQ, I
3640 set out yesterday to create a Debian package for making it trivial to
3641 set up such SMTP over Tor service based on Debian. Getting it to work
3642 were fairly easy, and
3643 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
3644 source code for the Debian package&lt;/a&gt; is available from github. I
3645 plan to move it into Debian if further testing prove this to be a
3646 useful approach.&lt;/p&gt;
3647
3648 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
3649 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
3650 get rid of exim4). Install tor, clone the git repository mentioned
3651 above, build the deb and install it on the machine. Next, run
3652 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
3653 the instructions to get the service up and running. Restart tor and
3654 exim when it is done, and test mail delivery using swaks like
3655 this:&lt;/p&gt;
3656
3657 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3658 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3659 --to fbx@dutlqrrmjhtfa3vp.onion
3660 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3661
3662 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
3663 address with your own address to test your server. :)&lt;/p&gt;
3664
3665 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
3666 easier and more automatic. Especially the tor setup need more work.
3667 Also, the package include a tor-smtp tool written in C, but its task
3668 should probably be rewritten in some script language to make the deb
3669 architecture independent. It would probably also make the code easier
3670 to review. The tor-smtp tool currently need to listen on a socket for
3671 exim to talk to it and is started using xinetd. It would be better if
3672 no daemon and no socket is needed. I suspect it is possible to get
3673 exim to run a command line tool for delivery instead of talking to a
3674 socket, and hope to figure out how in a future version of this
3675 system.&lt;/p&gt;
3676
3677 &lt;p&gt;Until I wipe my test machine, I can be reached using the
3678 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
3679 SMTorP. :)&lt;/p&gt;
3680 </description>
3681 </item>
3682
3683 <item>
3684 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
3685 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
3686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
3687 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
3688 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
3689 alioth.debian.org, you know the web interface is fairly slow to
3690 operate. First you visit one web page, enter the moderation password
3691 and get a new page shown with a list of all the messages to moderate
3692 and various options for each email address. This take a while for
3693 every list you moderate, and you need to do it regularly to do a good
3694 job as a list moderator. But there is a quick alternative,
3695 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
3696 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
3697 to moderate in a fraction of a second. Here is a test run on two
3698 lists I recently took over:&lt;/p&gt;
3699
3700 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3701 % time listadmin xiph
3702 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3703 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3704
3705 real 0m1.709s
3706 user 0m0.232s
3707 sys 0m0.012s
3708 %
3709 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3710
3711 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
3712 there are no message in the moderation queue. Every morning I
3713 currently moderate 68 mailman lists, and it normally take around two
3714 minutes. When I took over the two pkg-xiph lists above a few days
3715 ago, there were 400 emails waiting in the moderator queue. It took me
3716 less than 15 minutes to process them all using the listadmin
3717 program.&lt;/p&gt;
3718
3719 &lt;p&gt;If you install
3720 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
3721 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
3722 with content like this, the moderation task is a breeze:&lt;/p&gt;
3723
3724 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3725 username username@example.org
3726 spamlevel 23
3727 default discard
3728 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
3729
3730 password secret
3731 adminurl https://{domain}/mailman/admindb/{list}
3732 mailman-list@lists.example.com
3733
3734 password hidden
3735 other-list@otherserver.example.org
3736 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3737
3738 &lt;p&gt;There are other options to set as well. Check the manual page to
3739 learn the details.&lt;/p&gt;
3740
3741 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
3742 the SSL certificate is self signed or not properly signed by a
3743 generally accepted signing authority, you can set a environment
3744 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
3745
3746 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3747 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
3748 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3749
3750 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
3751 can provide an argument to the listadmin script like I do in the
3752 initial screen dump (the xiph argument). Using an argument, only
3753 lists matching the argument string will be processed. This make it
3754 quick to accept messages if you notice the moderation request in your
3755 email.&lt;/p&gt;
3756
3757 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
3758 mailing lists, as I simply do not have time to spend on that if the
3759 process was any slower. The listadmin program have saved me hours of
3760 time I could spend elsewhere over the years. It truly is nice free
3761 software.&lt;/p&gt;
3762
3763 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3764 activities, please send Bitcoin donations to my address
3765 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3766
3767 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
3768 configuration example. Also, I&#39;ve been told that the
3769 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
3770 sure why.&lt;/p&gt;
3771 </description>
3772 </item>
3773
3774 <item>
3775 <title>Debian Jessie, PXE and automatic firmware installation</title>
3776 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
3777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
3778 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
3779 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
3780 problem that the WiFi card require some firmware to work properly.
3781 And it has been a pain to fix this using preseeding in Debian.
3782 Normally something more is needed. But thanks to
3783 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
3784 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
3785 to do this using simple preseeding.&lt;/p&gt;
3786
3787 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
3788 firmware for the hardware found in the machine (actually, requested by
3789 the kernel modules for the hardware). (It can also install user space
3790 programs supporting the hardware detected, but that is not the focus
3791 of this story.)&lt;/p&gt;
3792
3793 &lt;p&gt;To get this working in the default installation, two preeseding
3794 values are needed. First, the isenkram-cli package must be installed
3795 into the target chroot (aka the hard drive) before tasksel is executed
3796 in the pkgsel step of the debian-installer system. This is done by
3797 preseeding the base-installer/includes debconf value to include the
3798 isenkram-cli package. The package name is next passed to debootstrap
3799 for installation. With the isenkram-cli package in place, tasksel
3800 will automatically use the isenkram tasks to detect hardware specific
3801 packages for the machine being installed and install them, because
3802 isenkram-cli contain tasksel tasks.&lt;/p&gt;
3803
3804 &lt;p&gt;Second, one need to enable the non-free APT repository, because
3805 most firmware unfortunately is non-free. This is done by preseeding
3806 the apt-mirror-setup step. This is unfortunate, but for a lot of
3807 hardware it is the only option in Debian.&lt;/p&gt;
3808
3809 &lt;p&gt;The end result is two lines needed in your preseeding file to get
3810 firmware installed automatically by the installer:&lt;/p&gt;
3811
3812 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3813 base-installer base-installer/includes string isenkram-cli
3814 apt-mirror-setup apt-setup/non-free boolean true
3815 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3816
3817 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
3818 both firmware and user space packages when using this method. It also
3819 do not work well, so use version 0.15 or later. Installing both
3820 firmware and user space packages might give you a bit more than you
3821 want, so I decided to split the tasksel task in two, one for firmware
3822 and one for user space programs. The firmware task is enabled by
3823 default, while the one for user space programs is not. This split is
3824 implemented in the package currently in unstable.&lt;/p&gt;
3825
3826 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
3827 this recipe work for you. :)&lt;/p&gt;
3828
3829 &lt;p&gt;So, I bet you are wondering, how can this work. First and
3830 foremost, it work because tasksel is modular, and driven by whatever
3831 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3832 isenkram-cli package place two files for tasksel to find. First there
3833 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
3834
3835 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3836 Task: isenkram-packages
3837 Section: hardware
3838 Description: Hardware specific packages (autodetected by isenkram)
3839 Based on the detected hardware various hardware specific packages are
3840 proposed.
3841 Test-new-install: show show
3842 Relevance: 8
3843 Packages: for-current-hardware
3844
3845 Task: isenkram-firmware
3846 Section: hardware
3847 Description: Hardware specific firmware packages (autodetected by isenkram)
3848 Based on the detected hardware various hardware specific firmware
3849 packages are proposed.
3850 Test-new-install: mark show
3851 Relevance: 8
3852 Packages: for-current-hardware-firmware
3853 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3854
3855 &lt;p&gt;The key parts are Test-new-install which indicate how the task
3856 should be handled and the Packages line referencing to a script in
3857 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3858 list of packages to install. The for-current-hardware-firmware script
3859 look like this to list relevant firmware for the machine:
3860
3861 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3862 #!/bin/sh
3863 #
3864 PATH=/usr/sbin:$PATH
3865 export PATH
3866 isenkram-autoinstall-firmware -l
3867 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3868
3869 &lt;p&gt;With those two pieces in place, the firmware is installed by
3870 tasksel during the normal d-i run. :)&lt;/p&gt;
3871
3872 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
3873 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
3874 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
3875 install.&lt;/p&gt;
3876
3877 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
3878 pilots in testing this feature, as isenkram is used there now to
3879 install firmware, replacing the earlier scripts.&lt;/p&gt;
3880 </description>
3881 </item>
3882
3883 <item>
3884 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
3885 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
3886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
3887 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
3888 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
3889 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3890 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
3891 on a screen normally showing the bread types and prizes:&lt;/p&gt;
3892
3893 &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;
3894
3895 &lt;p&gt;If it had booted as it was supposed to, I would never had known
3896 about this hidden Linux installation. It is interesting what
3897 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
3898 </description>
3899 </item>
3900
3901 <item>
3902 <title>New lsdvd release version 0.17 is ready</title>
3903 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
3904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
3905 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
3906 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
3907 got a new set of developers a few weeks ago, after the original
3908 developer decided to step down and pass the project to fresh blood.
3909 This project is now maintained by Petter Reinholdtsen and Steve
3910 Dibb.&lt;/p&gt;
3911
3912 &lt;p&gt;I just wrapped up
3913 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
3914 new lsdvd release&lt;/a&gt;, available in git or from
3915 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
3916 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
3917 0.17.&lt;/p&gt;
3918
3919 &lt;ul&gt;
3920
3921 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
3922 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
3923 non-existant, to work around additional copy protection&lt;/li&gt;
3924 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
3925 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
3926 &lt;li&gt;Fix include orders&lt;/li&gt;
3927 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
3928 &lt;li&gt;Fix the chapter count&lt;/li&gt;
3929 &lt;li&gt;Make sure the array size and the array limit used when initialising
3930 the palette size is the same.&lt;/li&gt;
3931 &lt;li&gt;Fix array printing.&lt;/li&gt;
3932 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
3933 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
3934 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
3935 with more GCC compiler warnings.&lt;/li&gt;
3936
3937 &lt;/ul&gt;
3938
3939 &lt;p&gt;This change bring together patches for lsdvd in use in various
3940 Linux and Unix distributions, as well as patches submitted to the
3941 project the last nine years. Please check it out. :)&lt;/p&gt;
3942 </description>
3943 </item>
3944
3945 <item>
3946 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
3947 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
3948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
3949 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
3950 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3951 project&lt;/a&gt; provide a Linux solution for schools, including a
3952 powerful desktop with education software, a central server providing
3953 web pages, user database, user home directories, central login and PXE
3954 boot of both clients without disk and the installation to install Debian
3955 Edu on machines with disk (and a few other services perhaps to small
3956 to mention here). We in the Debian Edu team are currently working on
3957 the Jessie based version, trying to get everything in shape before the
3958 freeze, to avoid having to maintain our own package repository in the
3959 future. The
3960 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
3961 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
3962 work left. Some fatal problems block testing, breaking the installer,
3963 but it is possible to work around these to get anyway. Here is a
3964 recipe on how to get the installation limping along.&lt;/p&gt;
3965
3966 &lt;p&gt;First, download the test ISO via
3967 &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;,
3968 &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;
3969 or rsync (use
3970 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
3971 The ISO build was broken on Tuesday, so we do not get a new ISO every
3972 12 hours or so, but thankfully the ISO we already got we are able to
3973 install with some tweaking.&lt;/p&gt;
3974
3975 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
3976 (use Alt-Ctrl-F2), run&lt;/p&gt;
3977
3978 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3979 nano /usr/bin/edu-eatmydata-install
3980 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3981
3982 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
3983 optimization. Return to the installation, select the profile you want
3984 and continue. Without this change, exim4-config will fail to install
3985 due to a known bug in eatmydata.&lt;/p&gt;
3986
3987 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
3988 this do not work, figure out what your correct value would be. All my
3989 test machines need /dev/sda, so I have no advice if it do not fit
3990 your need.&lt;/p&gt;
3991
3992 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
3993 root after the initial boot from hard drive, and install the
3994 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3995 or mate. If you want several desktop options, install more than one
3996 metapackage. Once this is done, reboot and you should have a working
3997 graphical login screen. This workaround should no longer be needed
3998 once the education-tasks package version 1.801 enter testing in two
3999 days.&lt;/p&gt;
4000
4001 &lt;p&gt;I believe the ISO build will start working on two days when the new
4002 tasksel package enter testing and Steve McIntyre get a chance to
4003 update the debian-cd git repository. The eatmydata, grub and desktop
4004 issues are already fixed in unstable and testing, and should show up
4005 on the ISO as soon as the ISO build start working again. Well the
4006 eatmydata optimization is really just disabled. The proper fix
4007 require an upload by the eatmydata maintainer applying the patch
4008 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4009 The rest have proper fixes in unstable.&lt;/p&gt;
4010
4011 &lt;p&gt;I hope this get you going with the installation testing, as we are
4012 quickly running out of time trying to get our Jessie based
4013 installation ready before the distribution freeze in a month.&lt;/p&gt;
4014 </description>
4015 </item>
4016
4017 <item>
4018 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4019 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4020 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4021 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4022 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4023 to handle my fairly large DVD collection. It is a nice command line
4024 tool to get details about a DVD, like title, tracks, track length,
4025 etc, in XML, Perl or human readable format. But lsdvd have not seen
4026 any new development since 2006 and had a few irritating bugs affecting
4027 its use with some DVDs. Upstream seemed to be dead, and in January I
4028 sent a small probe asking for a version control repository for the
4029 project, without any reply. But I use it regularly and would like to
4030 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4031 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4032 the project admin, and after getting a reply from him explaining that
4033 he was no longer interested in the project, I asked if I could take
4034 over. And yesterday, I became project admin.&lt;/p&gt;
4035
4036 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4037 maintainer interested in joining forces to maintain the upstream
4038 project, and I hope we can get a new release out fairly quickly,
4039 collecting the patches spread around on the internet into on place.
4040 I&#39;ve added the relevant Debian patches to the freshly created git
4041 repository, and expect the Gentoo patches to make it too. If you got
4042 a DVD collection and care about command line tools, check out
4043 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4044 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4045 list&lt;/a&gt;. :)&lt;/p&gt;
4046 </description>
4047 </item>
4048
4049 <item>
4050 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4051 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4053 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4054 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4055 a lot quicker. When we install more than 2000 packages in
4056 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4057 tasksel in the installer, unpacking the binary packages take forever.
4058 A part of the slow I/O issue was discussed in
4059 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4060 much file system sync-ing done by dpkg, which is the package
4061 responsible for unpacking the binary packages. Other parts (like code
4062 executed by postinst scripts) might also sync to disk during
4063 installation. All this sync-ing to disk do not really make sense to
4064 me. If the machine crash half-way through, I start over, I do not try
4065 to salvage the half installed system. So the failure sync-ing is
4066 supposed to protect against, hardware or system crash, is not really
4067 relevant while the installer is running.&lt;/p&gt;
4068
4069 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4070 system sync()-ing in a fairly non-intrusive way, without the need to
4071 change the code in several packages. The idea is not new, but I have
4072 not heard anyone propose the approach using dpkg-divert before. It
4073 depend on the small and clever package
4074 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4075 uses LD_PRELOAD to replace the system functions for syncing data to
4076 disk with functions doing nothing, thus allowing programs to live
4077 dangerous while speeding up disk I/O significantly. Instead of
4078 modifying the implementation of dpkg, apt and tasksel (which are the
4079 packages responsible for selecting, fetching and installing packages),
4080 it occurred to me that we could just divert the programs away, replace
4081 them with a simple shell wrapper calling
4082 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4083 Two days ago I decided to test the idea, and wrapped up a simple
4084 implementation for the Debian Edu udeb.&lt;/p&gt;
4085
4086 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4087 time of the pkgsel step (installing tasks) from 64 to less than 44
4088 minutes (20 minutes shaved off the installation) on an old Dell
4089 Latitude D505 machine. I am not quite sure what the optimised time
4090 would have been, as I messed up the testing a bit, causing the debconf
4091 priority to get low enough for two questions to pop up during
4092 installation. As soon as I saw the questions I moved the installation
4093 along, but do not know how long the question were holding up the
4094 installation. I did some more measurements using Debian Edu Jessie,
4095 and got these results. The time measured is the time stamp in
4096 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4097 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4098 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4099 timing thus do not depend on how quickly the user handle the tasksel
4100 dialog.&lt;/p&gt;
4101
4102 &lt;p&gt;&lt;table&gt;
4103
4104 &lt;tr&gt;
4105 &lt;th&gt;Machine/setup&lt;/th&gt;
4106 &lt;th&gt;Original tasksel&lt;/th&gt;
4107 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4108 &lt;th&gt;Reduction&lt;/th&gt;
4109 &lt;/tr&gt;
4110
4111 &lt;tr&gt;
4112 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4113 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4114 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4115 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4116 &lt;/tr&gt;
4117
4118 &lt;tr&gt;
4119 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4120 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4121 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4122 &lt;td&gt;23 min 40%&lt;/td&gt;
4123 &lt;/tr&gt;
4124
4125 &lt;tr&gt;
4126 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4127 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4128 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4129 &lt;td&gt;11 min 50%&lt;/td&gt;
4130 &lt;/tr&gt;
4131
4132 &lt;tr&gt;
4133 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4134 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4135 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4136 &lt;td&gt;2 min 33%&lt;/td&gt;
4137 &lt;/tr&gt;
4138
4139 &lt;tr&gt;
4140 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4141 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4142 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4143 &lt;td&gt;4 min 21%&lt;/td&gt;
4144 &lt;/tr&gt;
4145
4146 &lt;/table&gt;&lt;/p&gt;
4147
4148 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4149 time is spent downloading packages. The connection to the Internet
4150 was 100Mbit/s during testing, so downloading should not be a
4151 significant factor in the measurement. Download typically took a few
4152 seconds to a few minutes, depending on the amount of packages being
4153 installed.&lt;/p&gt;
4154
4155 &lt;p&gt;The speedup is implemented by using two hooks in
4156 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4157 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4158 finish-install.d hook to remove the divert at the end of the
4159 installation. I picked the pre-pkgsel.d hook instead of the
4160 post-base-installer.d hook because I test using an ISO without the
4161 eatmydata package included, and the post-base-installer.d hook in
4162 Debian Edu can only operate on packages included in the ISO. The
4163 negative effect of this is that I am unable to activate this
4164 optimization for the kernel installation step in d-i. If the code is
4165 moved to the post-base-installer.d hook, the speedup would be larger
4166 for the entire installation.&lt;/p&gt;
4167
4168 &lt;p&gt;I&#39;ve implemented this in the
4169 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4170 git repository, and plan to provide the optimization as part of the
4171 Debian Edu installation. If you want to test this yourself, you can
4172 create two files in the installer (or in an udeb). One shell script
4173 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4174
4175 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4176 #!/bin/sh
4177 set -e
4178 . /usr/share/debconf/confmodule
4179 info() {
4180 logger -t my-pkgsel &quot;info: $*&quot;
4181 }
4182 error() {
4183 logger -t my-pkgsel &quot;error: $*&quot;
4184 }
4185 override_install() {
4186 apt-install eatmydata || true
4187 if [ -x /target/usr/bin/eatmydata ] ; then
4188 for bin in dpkg apt-get aptitude tasksel ; do
4189 file=/usr/bin/$bin
4190 # Test that the file exist and have not been diverted already.
4191 if [ -f /target$file ] ; then
4192 info &quot;diverting $file using eatmydata&quot;
4193 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4194 &gt; /target$file.edu
4195 chmod 755 /target$file.edu
4196 in-target dpkg-divert --package debian-edu-config \
4197 --rename --quiet --add $file
4198 ln -sf ./$bin.edu /target$file
4199 else
4200 error &quot;unable to divert $file, as it is missing.&quot;
4201 fi
4202 done
4203 else
4204 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4205 fi
4206 }
4207
4208 override_install
4209 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4210
4211 &lt;p&gt;To clean up, another shell script should go into
4212 /usr/lib/finish-install.d/ with code like this:
4213
4214 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4215 #! /bin/sh -e
4216 . /usr/share/debconf/confmodule
4217 error() {
4218 logger -t my-finish-install &quot;error: $@&quot;
4219 }
4220 remove_install_override() {
4221 for bin in dpkg apt-get aptitude tasksel ; do
4222 file=/usr/bin/$bin
4223 if [ -x /target$file.edu ] ; then
4224 rm /target$file
4225 in-target dpkg-divert --package debian-edu-config \
4226 --rename --quiet --remove $file
4227 rm /target$file.edu
4228 else
4229 error &quot;Missing divert for $file.&quot;
4230 fi
4231 done
4232 sync # Flush file buffers before continuing
4233 }
4234
4235 remove_install_override
4236 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4237
4238 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4239 edu-eatmydata-install and call it from the pre-pkgsel.d and
4240 finish-install.d scripts.&lt;/p&gt;
4241
4242 &lt;p&gt;By now you might ask if this change should get into the normal
4243 Debian installer too? I suspect it should, but am not sure the
4244 current debian-installer coordinators find it useful enough. It also
4245 depend on the side effects of the change. I&#39;m not aware of any, but I
4246 guess we will see if the change is safe after some more testing.
4247 Perhaps there is some package in Debian depending on sync() and
4248 fsync() having effect? Perhaps it should go into its own udeb, to
4249 allow those of us wanting to enable it to do so without affecting
4250 everyone.&lt;/p&gt;
4251
4252 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4253 will break installation of all programs using gnutls because of
4254 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4255 eatmydata package in Debian will solve it.&lt;/p&gt;
4256
4257 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4258 the optimization work again. And I have discovered that the
4259 dpkg-divert trick is not really needed and implemented a slightly
4260 simpler approach as part of the debian-edu-install package. See
4261 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4262
4263 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4264 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4265 triggering on i386 made it into testing, and broke this installation
4266 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4267 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4268 </description>
4269 </item>
4270
4271 <item>
4272 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4273 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4274 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4275 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4276 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4277 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4278 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4279 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4280 learn that there is a large set of publicly available key servers to
4281 use when looking for peoples public key. So far I have used
4282 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4283 were misbehaving, but those days are ended. The servers I have used
4284 up until yesterday have been slow and some times unavailable. I hope
4285 those problems are gone now.&lt;/p&gt;
4286
4287 &lt;p&gt;Behind the round robin DNS entry of the
4288 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4289 there is a pool of more than 100 keyservers which are checked every
4290 day to ensure they are well connected and up to date. It must be
4291 better than what I have used so far. :)&lt;/p&gt;
4292
4293 &lt;p&gt;Yesterdays speaker told me that the service is the default
4294 keyserver provided by the default configuration in GnuPG, but this do
4295 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4296
4297 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4298 line:&lt;/p&gt;
4299
4300 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4301 keyserver pool.sks-keyservers.net
4302 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4303
4304 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4305 entries in DNS. Just for fun, I did just that at work, so now every
4306 user of GnuPG at the University of Oslo should find a OpenGPG
4307 keyserver automatically should their need it:&lt;/p&gt;
4308
4309 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4310 % host -t srv _pgpkey-http._tcp.uio.no
4311 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4312 %
4313 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4314
4315 &lt;p&gt;Now if only
4316 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4317 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4318 very happy. It can look up a given key or search for a user ID, but I
4319 normally do not want that, but to find a trust path from my key to
4320 another key. Given a user ID or key ID, I would like to find (and
4321 download) the keys representing a signature path from my key to the
4322 key in question, to be able to get a trust path between the two keys.
4323 This is as far as I can tell not possible today. Perhaps something
4324 for a future version of the protocol?&lt;/p&gt;
4325 </description>
4326 </item>
4327
4328 <item>
4329 <title>From English wiki to translated PDF and epub via Docbook</title>
4330 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4331 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4332 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4333 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4334 project&lt;/a&gt; provide an instruction manual for teachers, system
4335 administrators and other users that contain useful tips for setting up
4336 and maintaining a Debian Edu installation. This text is about how the
4337 text processing of this manual is handled in the project.&lt;/p&gt;
4338
4339 &lt;p&gt;One goal of the project is to provide information in the native
4340 language of its users, and for this we need to handle translations.
4341 But we also want to make sure each language contain the same
4342 information, so for this we need a good way to keep the translations
4343 in sync. And we want it to be easy for our users to improve the
4344 documentation, avoiding the need to learn special formats or tools to
4345 contribute, and the obvious way to do this is to make it possible to
4346 edit the documentation using a web browser. We also want it to be
4347 easy for translators to keep the translation up to date, and give them
4348 help in figuring out what need to be translated. Here is the list of
4349 tools and the process we have found trying to reach all these
4350 goals.&lt;/p&gt;
4351
4352 &lt;p&gt;We maintain the authoritative source of our manual in the
4353 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4354 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4355 front page with references to the different chapters, several pages
4356 for each chapter, and finally one &quot;collection page&quot; gluing all the
4357 chapters together into one large web page (aka
4358 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4359 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4360 processing and translations. Thanks to the fact that the
4361 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4362 wiki.debian.org support exporting pages in
4363 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4364 the list of pages to export using the raw version of the AllInOne
4365 page, loop over each of them to generate a Docbook XML version of the
4366 manual. This process also download images and transform image
4367 references to use the locally downloaded images. The generated
4368 Docbook XML files are slightly broken, so some post-processing is done
4369 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4370 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4371 a handfull of images. The XML file can now be used to generate PDF, HTML
4372 and epub versions of the English manual. This is the basic step of
4373 our process, making PDF (using dblatex), HTML (using xsltproc) and
4374 epub (using dbtoepub) version from Docbook XML, and the resulting files
4375 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4376
4377 &lt;p&gt;But English documentation is not enough for us. We want translated
4378 documentation too, and we want to make it easy for translators to
4379 track the English original. For this we use the
4380 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4381 which allow us to transform the English Docbook XML file into a
4382 translation file (a .pot file), usable with the normal gettext based
4383 translation tools used by those translating free software. The pot
4384 file is used to create and maintain translation files (several .po
4385 files), which the translations update with the native language
4386 translations of all titles, paragraphs and blocks of text in the
4387 original. The next step is combining the original English Docbook XML
4388 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4389 create a translated Docbook XML file (in this case
4390 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4391 translated, if the translation is not complete) Docbook XML file can
4392 then be used like the original to create a PDF, HTML and epub version
4393 of the documentation.&lt;/p&gt;
4394
4395 &lt;p&gt;The translators use different tools to edit the .po files. We
4396 recommend using
4397 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4398 while some use emacs and vi, others can use web based editors like
4399 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4400 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4401 is where the .po file end up, in our git repository. Updated
4402 translations can either be committed directly to git, or submitted as
4403 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4404 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4405
4406 &lt;p&gt;One challenge is images, which both might need to be translated (if
4407 they show translated user applications), and are needed in different
4408 formats when creating PDF and HTML versions (epub is a HTML version in
4409 this regard). For this we transform the original PNG images to the
4410 needed density and format during build, and have a way to provide
4411 translated images by storing translated versions in
4412 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4413 package maintainers know more.&lt;/p&gt;
4414
4415 &lt;p&gt;If you wonder what the result look like, we provide
4416 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4417 of the documentation packages on the web&lt;/a&gt;. See for example the
4418 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4419 PDF version&lt;/a&gt; or the
4420 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4421 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4422 but perhaps it will be done in the future.&lt;/p&gt;
4423
4424 &lt;p&gt;To learn more, check out
4425 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4426 debian-edu-doc package&lt;/a&gt;,
4427 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4428 manual on the wiki&lt;/a&gt; and
4429 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4430 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4431 </description>
4432 </item>
4433
4434 <item>
4435 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4436 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4437 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4438 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4439 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4440 related packages relevant for the computer installed automatically.
4441 So I implemented one, using
4442 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4443 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4444 run tasksel as user root. You should be presented with a new option,
4445 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4446 select it, tasksel will install the packages isenkram claim is fit for
4447 the current hardware, hot pluggable or not.&lt;p&gt;
4448
4449 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4450 description, and the other is the script used to extract the list of
4451 packages to install. The first part is in
4452 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4453 this:&lt;/p&gt;
4454
4455 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4456 Task: isenkram
4457 Section: hardware
4458 Description: Hardware specific packages (autodetected by isenkram)
4459 Based on the detected hardware various hardware specific packages are
4460 proposed.
4461 Test-new-install: mark show
4462 Relevance: 8
4463 Packages: for-current-hardware
4464 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4465
4466 &lt;p&gt;The second part is in
4467 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4468 this:&lt;/p&gt;
4469
4470 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4471 #!/bin/sh
4472 #
4473 (
4474 isenkram-lookup
4475 isenkram-autoinstall-firmware -l
4476 ) | sort -u
4477 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4478
4479 &lt;p&gt;All in all, a very short and simple implementation making it
4480 trivial to install the hardware dependent package we all may want to
4481 have installed on our machines. I&#39;ve not been able to find a way to
4482 get tasksel to tell you exactly which packages it plan to install
4483 before doing the installation. So if you are curious or careful,
4484 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4485
4486 &lt;p&gt;The information about which packages are handling which hardware is
4487 fetched either from the isenkram package itself in
4488 /usr/share/isenkram/, from git.debian.org or from the APT package
4489 database (using the Modaliases header). The APT package database
4490 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4491 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4492 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4493 the python-apt code (bug
4494 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
4495 workaround I was able to get rid of the file descriptor leak and
4496 reduce the memory leak from ~30 MiB per hardware detection down to
4497 around 2 MiB per hardware detection. It should make the desktop
4498 daemon a lot more useful. The fix is in version 0.7 uploaded to
4499 unstable today.&lt;/p&gt;
4500
4501 &lt;p&gt;I believe the current way of mapping hardware to packages in
4502 Isenkram is is a good draft, but in the future I expect isenkram to
4503 use the AppStream data source for this. A proposal for getting proper
4504 AppStream support into Debian is floating around as
4505 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
4506 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
4507 project&lt;/a&gt; will take place this summer to improve the situation. I
4508 look forward to seeing the result, and welcome patches for isenkram to
4509 start using the information when it is ready.&lt;/p&gt;
4510
4511 &lt;p&gt;If you want your package to map to some specific hardware, either
4512 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
4513 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
4514 package&lt;/a&gt; or submit a bug report with the details to the isenkram
4515 package. See also
4516 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
4517 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
4518 the information will be migrated to AppStream eventually, but for the
4519 moment I got no better place to store it.&lt;/p&gt;
4520 </description>
4521 </item>
4522
4523 <item>
4524 <title>FreedomBox milestone - all packages now in Debian Sid</title>
4525 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
4526 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
4527 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
4528 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4529 project&lt;/a&gt; is working on providing the software and hardware to make
4530 it easy for non-technical people to host their data and communication
4531 at home, and being able to communicate with their friends and family
4532 encrypted and away from prying eyes. It is still going strong, and
4533 today a major mile stone was reached.&lt;/p&gt;
4534
4535 &lt;p&gt;Today, the last of the packages currently used by the project to
4536 created the system images were accepted into Debian Unstable. It was
4537 the freedombox-setup package, which is used to configure the images
4538 during build and on the first boot. Now all one need to get going is
4539 the build code from the freedom-maker git repository and packages from
4540 Debian. And once the freedombox-setup package enter testing, we can
4541 build everything directly from Debian. :)&lt;/p&gt;
4542
4543 &lt;p&gt;Some key packages used by Freedombox are
4544 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
4545 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
4546 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
4547 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
4548 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
4549 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
4550 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
4551 are plans to integrate more packages into the setup. User
4552 documentation is maintained on the Debian wiki. Please
4553 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
4554 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
4555
4556 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
4557 setup, run this on a Debian machine using a user with sudo rights to
4558 become root:&lt;/p&gt;
4559
4560 &lt;p&gt;&lt;pre&gt;
4561 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4562 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4563 u-boot-tools
4564 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4565 freedom-maker
4566 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4567 &lt;/pre&gt;&lt;/p&gt;
4568
4569 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4570 devices. See the README in the freedom-maker git repo for more
4571 details on the build. If you do not want all three images, trim the
4572 make line. Note that the virtualbox-image target is not really
4573 virtualbox specific. It create a x86 image usable in kvm, qemu,
4574 vmware and any other x86 virtual machine environment. You might need
4575 the version of vmdebootstrap in Jessie to get the build working, as it
4576 include fixes for a race condition with kpartx.&lt;/p&gt;
4577
4578 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4579 method, boot a Debian Wheezy ISO and use this boot argument to load
4580 the preseed values:&lt;/p&gt;
4581
4582 &lt;p&gt;&lt;pre&gt;
4583 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;
4584 &lt;/pre&gt;&lt;/p&gt;
4585
4586 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
4587 it still work.&lt;/p&gt;
4588
4589 &lt;p&gt;If you wonder how to help, one task you could look at is using
4590 systemd as the boot system. It will become the default for Linux in
4591 Jessie, so we need to make sure it is usable on the Freedombox. I did
4592 a simple test a few weeks ago, and noticed dnsmasq failed to start
4593 during boot when using systemd. I suspect there are other problems
4594 too. :) To detect problems, there is a test suite included, which can
4595 be run from the plinth web interface.&lt;/p&gt;
4596
4597 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4598 us get the new release published. :) Please join us on
4599 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4600 irc.debian.org)&lt;/a&gt; and
4601 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4602 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4603 </description>
4604 </item>
4605
4606 <item>
4607 <title>S3QL, a locally mounted cloud file system - nice free software</title>
4608 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
4609 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
4610 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
4611 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
4612 solution for use at home. My requirements are simple, it must be
4613 cheap and locally encrypted (in other words, I keep the encryption
4614 keys, the storage provider do not have access to my private files).
4615 One idea me and my friends had many years ago, before the cloud
4616 storage providers showed up, was to use Google mail as storage,
4617 writing a Linux block device storing blocks as emails in the mail
4618 service provided by Google, and thus get heaps of free space. On top
4619 of this one can add encryption, RAID and volume management to have
4620 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4621 I never found time to implement such system. But the last few weeks I
4622 have looked at a system called
4623 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
4624 mounted network backed file system with the features I need.&lt;/p&gt;
4625
4626 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
4627 handling several different storage providers, any with Amazon S3,
4628 Google Drive or OpenStack API. There are heaps of such storage
4629 providers. S3QL can also use a local directory as storage, which
4630 combined with sshfs allow for file storage on any ssh server. S3QL
4631 include support for encryption, compression, de-duplication, snapshots
4632 and immutable file systems, allowing me to mount the remote storage as
4633 a local mount point, look at and use the files as if they were local,
4634 while the content is stored in the cloud as well. This allow me to
4635 have a backup that should survive fire. The file system can not be
4636 shared between several machines at the same time, as only one can
4637 mount it at the time, but any machine with the encryption key and
4638 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
4639
4640 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
4641 package is included already. So to get started, run &lt;tt&gt;apt-get
4642 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
4643 Greenqloud, after reading their nice recipe on
4644 &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
4645 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
4646 in Iceland more than those in USA when it come to keeping my personal
4647 data safe and private, and thus would rather spend money on a company
4648 in Iceland. Another nice recipe is available from the article
4649 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
4650 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
4651 Admin magazine. When the provider is picked, figure out how to get
4652 the API key needed to connect to the storage API. With Greencloud,
4653 the key did not show up until I had added payment details to my
4654 account.&lt;/p&gt;
4655
4656 &lt;p&gt;Armed with the API access details, it is time to create the file
4657 system. First, create a new bucket in the cloud. This bucket is the
4658 file system storage area. I picked a bucket name reflecting the
4659 machine that was going to store data there, but any name will do.
4660 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
4661 the API login and password, and a locally created password. Store it
4662 all in ~root/.s3ql/authinfo2 like this:
4663
4664 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4665 [s3c]
4666 storage-url: s3c://s.greenqloud.com:443/bucket-name
4667 backend-login: API-login
4668 backend-password: API-password
4669 fs-passphrase: local-password
4670 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4671
4672 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
4673 but any sensible way to create a fairly random password should do it.
4674 Armed with these details, it is now time to run mkfs, entering the API
4675 details and password to create it:&lt;/p&gt;
4676
4677 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4678 # mkdir -m 700 /var/lib/s3ql-cache
4679 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4680 --ssl s3c://s.greenqloud.com:443/bucket-name
4681 Enter backend login:
4682 Enter backend password:
4683 Before using S3QL, make sure to read the user&#39;s guide, especially
4684 the &#39;Important Rules to Avoid Loosing Data&#39; section.
4685 Enter encryption password:
4686 Confirm encryption password:
4687 Generating random encryption key...
4688 Creating metadata tables...
4689 Dumping metadata...
4690 ..objects..
4691 ..blocks..
4692 ..inodes..
4693 ..inode_blocks..
4694 ..symlink_targets..
4695 ..names..
4696 ..contents..
4697 ..ext_attributes..
4698 Compressing and uploading metadata...
4699 Wrote 0.00 MB of compressed metadata.
4700 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4701
4702 &lt;p&gt;The next step is mounting the file system to make the storage available.
4703
4704 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4705 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4706 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4707 Using 4 upload threads.
4708 Downloading and decompressing metadata...
4709 Reading metadata...
4710 ..objects..
4711 ..blocks..
4712 ..inodes..
4713 ..inode_blocks..
4714 ..symlink_targets..
4715 ..names..
4716 ..contents..
4717 ..ext_attributes..
4718 Mounting filesystem...
4719 # df -h /s3ql
4720 Filesystem Size Used Avail Use% Mounted on
4721 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
4722 #
4723 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4724
4725 &lt;p&gt;The file system is now ready for use. I use rsync to store my
4726 backups in it, and as the metadata used by rsync is downloaded at
4727 mount time, no network traffic (and storage cost) is triggered by
4728 running rsync. To unmount, one should not use the normal umount
4729 command, as this will not flush the cache to the cloud storage, but
4730 instead running the umount.s3ql command like this:
4731
4732 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4733 # umount.s3ql /s3ql
4734 #
4735 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4736
4737 &lt;p&gt;There is a fsck command available to check the file system and
4738 correct any problems detected. This can be used if the local server
4739 crashes while the file system is mounted, to reset the &quot;already
4740 mounted&quot; flag. This is what it look like when processing a working
4741 file system:&lt;/p&gt;
4742
4743 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4744 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
4745 Using cached metadata.
4746 File system seems clean, checking anyway.
4747 Checking DB integrity...
4748 Creating temporary extra indices...
4749 Checking lost+found...
4750 Checking cached objects...
4751 Checking names (refcounts)...
4752 Checking contents (names)...
4753 Checking contents (inodes)...
4754 Checking contents (parent inodes)...
4755 Checking objects (reference counts)...
4756 Checking objects (backend)...
4757 ..processed 5000 objects so far..
4758 ..processed 10000 objects so far..
4759 ..processed 15000 objects so far..
4760 Checking objects (sizes)...
4761 Checking blocks (referenced objects)...
4762 Checking blocks (refcounts)...
4763 Checking inode-block mapping (blocks)...
4764 Checking inode-block mapping (inodes)...
4765 Checking inodes (refcounts)...
4766 Checking inodes (sizes)...
4767 Checking extended attributes (names)...
4768 Checking extended attributes (inodes)...
4769 Checking symlinks (inodes)...
4770 Checking directory reachability...
4771 Checking unix conventions...
4772 Checking referential integrity...
4773 Dropping temporary indices...
4774 Backing up old metadata...
4775 Dumping metadata...
4776 ..objects..
4777 ..blocks..
4778 ..inodes..
4779 ..inode_blocks..
4780 ..symlink_targets..
4781 ..names..
4782 ..contents..
4783 ..ext_attributes..
4784 Compressing and uploading metadata...
4785 Wrote 0.89 MB of compressed metadata.
4786 #
4787 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4788
4789 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
4790 quick, about the same speed as local file access. Uploading large
4791 amount of data is to me limited by the bandwidth out of and into my
4792 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
4793 which is very close to my upload speed, and downloading the same
4794 Debian installation ISO gave me 610 kiB/s, close to my download speed.
4795 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
4796 network, not the file system code. I do not know what a good cache
4797 size would be, but suspect that the cache should e larger than your
4798 working set.&lt;/p&gt;
4799
4800 &lt;p&gt;I mentioned that only one machine can mount the file system at the
4801 time. If another machine try, it is told that the file system is
4802 busy:&lt;/p&gt;
4803
4804 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4805 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4806 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4807 Using 8 upload threads.
4808 Backend reports that fs is still mounted elsewhere, aborting.
4809 #
4810 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4811
4812 &lt;p&gt;The file content is uploaded when the cache is full, while the
4813 metadata is uploaded once every 24 hour by default. To ensure the
4814 file system content is flushed to the cloud, one can either umount the
4815 file system, or ask S3QL to flush the cache and metadata using
4816 s3qlctrl:
4817
4818 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4819 # s3qlctrl upload-meta /s3ql
4820 # s3qlctrl flushcache /s3ql
4821 #
4822 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4823
4824 &lt;p&gt;If you are curious about how much space your data uses in the
4825 cloud, and how much compression and deduplication cut down on the
4826 storage usage, you can use s3qlstat on the mounted file system to get
4827 a report:&lt;/p&gt;
4828
4829 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4830 # s3qlstat /s3ql
4831 Directory entries: 9141
4832 Inodes: 9143
4833 Data blocks: 8851
4834 Total data size: 22049.38 MB
4835 After de-duplication: 21955.46 MB (99.57% of total)
4836 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
4837 Database size: 2.39 MB (uncompressed)
4838 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4839 #
4840 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4841
4842 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
4843 storage. I did not try to locate them all, but am aware of at least
4844 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
4845 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
4846 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
4847 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
4848 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
4849 accept payment in Bitcoin. Pick one that suit your need. Some of
4850 them provide several GiB of free storage, but the prize models are
4851 quite different and you will have to figure out what suits you
4852 best.&lt;/p&gt;
4853
4854 &lt;p&gt;While researching this blog post, I had a look at research papers
4855 and posters discussing the S3QL file system. There are several, which
4856 told me that the file system is getting a critical check by the
4857 science community and increased my confidence in using it. One nice
4858 poster is titled
4859 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
4860 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4861 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
4862 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4863 and Pamela Smith. Please have a look.&lt;/p&gt;
4864
4865 &lt;p&gt;Given my problems with different file systems earlier, I decided to
4866 check out the mounted S3QL file system to see if it would be usable as
4867 a home directory (in other word, that it provided POSIX semantics when
4868 it come to locking and umask handling etc). Running
4869 &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
4870 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
4871 no error was found. So the file system can be used for home
4872 directories, if one chooses to do so.&lt;/p&gt;
4873
4874 &lt;p&gt;If you do not want a locally file system, and want something that
4875 work without the Linux fuse file system, I would like to mention the
4876 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
4877 provide locally encrypted backup using a command line client. It have
4878 a nicer access control system, where one can split out read and write
4879 access, allowing some systems to write to the backup and others to
4880 only read from it.&lt;/p&gt;
4881
4882 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4883 activities, please send Bitcoin donations to my address
4884 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4885 </description>
4886 </item>
4887
4888 <item>
4889 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
4890 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
4891 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
4892 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
4893 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4894 project&lt;/a&gt; is working on providing the software and hardware for
4895 making it easy for non-technical people to host their data and
4896 communication at home, and being able to communicate with their
4897 friends and family encrypted and away from prying eyes. It has been
4898 going on for a while, and is slowly progressing towards a new test
4899 release (0.2).&lt;/p&gt;
4900
4901 &lt;p&gt;And what day could be better than the Pi day to announce that the
4902 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
4903 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4904 system), and can also be installed using a Debian installer preseed
4905 file. The Debian based Freedombox is now based on Debian Jessie,
4906 where most of the needed packages used are already present. Only one,
4907 the freedombox-setup package, is missing. To try to build your own
4908 boot image to test the current status, fetch the freedom-maker scripts
4909 and build using
4910 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
4911 with a user with sudo access to become root:
4912
4913 &lt;pre&gt;
4914 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4915 freedom-maker
4916 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4917 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4918 u-boot-tools
4919 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4920 &lt;/pre&gt;
4921
4922 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4923 devices. See the README for more details on the build. If you do not
4924 want all three images, trim the make line. But note that thanks to &lt;a
4925 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
4926 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
4927 kpartx call.&lt;/p&gt;
4928
4929 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4930 method, boot a Debian Wheezy ISO and use this boot argument to load
4931 the preseed values:&lt;/p&gt;
4932
4933 &lt;pre&gt;
4934 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;
4935 &lt;/pre&gt;
4936
4937 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
4938 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
4939 currently hang while setting up APT sources. Killing the
4940 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
4941 installation will get the installation going. This affect all
4942 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
4943
4944 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4945 us get the new release published. :) Please join us on
4946 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4947 irc.debian.org)&lt;/a&gt; and
4948 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4949 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4950 </description>
4951 </item>
4952
4953 <item>
4954 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
4955 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
4956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
4957 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
4958 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
4959 innetgr tools, because I needed them in
4960 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
4961 ng-utils, and it has served me well. I placed the project under the
4962 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
4963 repository. But many years ago, the CVS repository was dropped (lost,
4964 not migrated to new hardware, not sure), and the project have lacked a
4965 proper home since then.&lt;/p&gt;
4966
4967 &lt;p&gt;Last summer, I had a look at the package and made a new release
4968 fixing a irritating crash bug, but was unable to store the changes in
4969 a proper source control system. I applied for a project on
4970 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
4971 to follow up on it. Until today. :)&lt;/p&gt;
4972
4973 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
4974 now have a new home, and a git repository with the highlight of the
4975 history of the project. I published all release tarballs and imported
4976 them into the git repository. As the project is really stable and not
4977 expected to gain new features any time soon, I decided to make a new
4978 release and call it 1.0. Visit the new project home on
4979 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
4980 if you want to check it out. The new version is also uploaded into
4981 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
4982 </description>
4983 </item>
4984
4985 <item>
4986 <title>Testing sysvinit from experimental in Debian Hurd</title>
4987 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
4988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
4989 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
4990 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
4991 their changes into sysvinit, to allow them to use the normal sysvinit
4992 boot system instead of their old one. This follow up on the
4993 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
4994 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
4995 get Debian on Hurd working more like Debian on Linux. To get started,
4996 I downloaded a prebuilt hard disk image from
4997 &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;,
4998 and started it using virt-manager.&lt;/p&gt;
4999
5000 &lt;p&gt;The first think I had to do after logging in (root without any
5001 password) was to get the network operational. I followed
5002 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5003 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5004 commands as root to get the machine to accept a IP address from the
5005 kvm internal DHCP server:&lt;/p&gt;
5006
5007 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5008 settrans -fgap /dev/netdde /hurd/netdde
5009 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5010 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5011 dhclient /dev/eth0
5012 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5013
5014 &lt;p&gt;After this, the machine had internet connectivity, and I could
5015 upgrade it and install the sysvinit packages from experimental and
5016 enable it as the default boot system in Hurd.&lt;/p&gt;
5017
5018 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5019 running on the machine it for ssh login to work a password need to be
5020 set. Also, note that a bug somewhere in openssh on Hurd block
5021 compression from working. Remember to turn that off on the client
5022 side.&lt;/p&gt;
5023
5024 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5025 stuff:&lt;/p&gt;
5026
5027 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5028 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5029 deb http://http.debian.net/debian/ experimental main
5030 EOF
5031 apt-get update
5032 apt-get dist-upgrade
5033 apt-get install -t experimental initscripts sysv-rc sysvinit \
5034 sysvinit-core sysvinit-utils
5035 update-alternatives --config runsystem
5036 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5037
5038 &lt;p&gt;To reboot after switching boot system, you have to use
5039 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5040 yet a sysvinit process able to receive the signals from the normal
5041 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5042 upgrading every package and rebooting, the network come up with DHCP
5043 after boot as it should, and the settrans/pkill hack mentioned at the
5044 start is no longer needed. But for some strange reason, there are no
5045 longer any login prompt in the virtual console, so I logged in using
5046 ssh instead.
5047
5048 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5049 fail some times. No idea what the cause is, but hope the Hurd porters
5050 figure it out. At least Justus said on IRC (#debian-hurd on
5051 irc.debian.org) that they are aware of the problem. A way to reduce
5052 the impact is to upgrade to the Hurd packages built by Justus by
5053 adding this repository to the machine:&lt;/p&gt;
5054
5055 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5056 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5057 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5058 EOF
5059 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5060
5061 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5062 http://ftp.debian-ports.org/debian, because some of the packages in
5063 unstable do not yet include the required patches that are lingering in
5064 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5065
5066 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5067 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5068 i emacs - GNU Emacs editor (metapackage)
5069 i gdb - GNU Debugger
5070 i hurd-recommended - Miscellaneous translators
5071 i isc-dhcp-client - ISC DHCP client
5072 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5073 i libc-bin - Embedded GNU C Library: Binaries
5074 i libc-dev-bin - Embedded GNU C Library: Development binaries
5075 i libc0.3 - Embedded GNU C Library: Shared libraries
5076 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5077 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5078 i multiarch-support - Transitional package to ensure multiarch compatibilit
5079 i A x11-common - X Window System (X.Org) infrastructure
5080 i xorg - X.Org X Window System
5081 i A xserver-xorg - X.Org X server
5082 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5083 #
5084 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5085
5086 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5087 X.org did not work out of the box and I never took the time to follow
5088 the porters instructions to fix it. This time I was interested in the
5089 command line stuff.&lt;p&gt;
5090 </description>
5091 </item>
5092
5093 <item>
5094 <title>New chrpath release 0.16</title>
5095 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5096 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5097 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5098 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5099 find problems in C, C++ and Java code using static source code
5100 analysis. It can detect a lot of different problems, and is very
5101 useful to find memory and locking bugs in the error handling part of
5102 the source. The company behind it provide
5103 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5104 a community service&lt;/a&gt;, and many hundred free software projects are
5105 already checked. A few days ago I decided to have a closer look at
5106 the Coverity system, and discovered that the
5107 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5108 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5109 projects I am involved with was already registered. But these are
5110 fairly big, and I would also like to have a small and easy project to
5111 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5112 checking of the chrpath project&lt;/a&gt;. It was
5113 added to the checker and discovered seven potential defects. Six of
5114 these were real, mostly resource &quot;leak&quot; when the program detected an
5115 error. Nothing serious, as the resources would be released a fraction
5116 of a second later when the program exited because of the error, but it
5117 is nice to do it right in case the source of the program some time in
5118 the future end up in a library. Having fixed all defects and added
5119 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5120 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5121 publish a new release. These are the release notes:&lt;/p&gt;
5122
5123 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5124
5125 &lt;ul&gt;
5126
5127 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5128 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5129 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5130
5131 &lt;/ul&gt;
5132
5133 &lt;p&gt;You can
5134 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5135 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5136 project if something is wrong with the new release. The test suite
5137 did not discover any old errors, so if you find a new one, please also
5138 include a test suite check.&lt;/p&gt;
5139 </description>
5140 </item>
5141
5142 <item>
5143 <title>New chrpath release 0.15</title>
5144 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5145 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5146 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5147 <description>&lt;p&gt;After many years break from the package and a vain hope that
5148 development would be continued by someone else, I finally pulled my
5149 acts together this morning and wrapped up a new release of chrpath,
5150 the command line tool to modify the rpath and runpath of already
5151 compiled ELF programs. The update was triggered by the persistence of
5152 Isha Vishnoi at IBM, which needed a new config.guess file to get
5153 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5154 is working on. I checked the
5155 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5156 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5157 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5158 packages for interesting patches (failed to find the source from
5159 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5160 These are the release notes:&lt;/p&gt;
5161
5162 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5163
5164 &lt;ul&gt;
5165
5166 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5167 with newer architectures. Thanks to isha vishnoi for the heads
5168 up.&lt;/li&gt;
5169
5170 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5171
5172 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5173 Matthias Klose.&lt;/li&gt;
5174
5175 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5176 Petr Machata found in Fedora.&lt;/li&gt;
5177
5178 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5179 .dynamic is a NULL terminated string. Based on patch found in
5180 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5181
5182 &lt;/ul&gt;
5183
5184 &lt;p&gt;You can
5185 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5186 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5187 project if something is wrong with the new release. The test suite
5188 did not discover any old errors, so if you find a new one, please also
5189 include a testsuite check.&lt;/p&gt;
5190 </description>
5191 </item>
5192
5193 <item>
5194 <title>Debian init.d boot script example for rsyslog</title>
5195 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5196 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5197 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5198 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5199 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5200 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5201 init.d scripts at all. Here is an example init.d script, ie a rewrite
5202 of /etc/init.d/rsyslog:&lt;/p&gt;
5203
5204 &lt;p&gt;&lt;pre&gt;
5205 #!/lib/init/init-d-script
5206 ### BEGIN INIT INFO
5207 # Provides: rsyslog
5208 # Required-Start: $remote_fs $time
5209 # Required-Stop: umountnfs $time
5210 # X-Stop-After: sendsigs
5211 # Default-Start: 2 3 4 5
5212 # Default-Stop: 0 1 6
5213 # Short-Description: enhanced syslogd
5214 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5215 # It is quite compatible to stock sysklogd and can be
5216 # used as a drop-in replacement.
5217 ### END INIT INFO
5218 DESC=&quot;enhanced syslogd&quot;
5219 DAEMON=/usr/sbin/rsyslogd
5220 &lt;/pre&gt;&lt;/p&gt;
5221
5222 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5223 script was 137 lines, and the above is just 15 lines, most of it meta
5224 info/comments.&lt;/p&gt;
5225
5226 &lt;p&gt;How to do this, you ask? Well, one create a new script
5227 /lib/init/init-d-script looking something like this:
5228
5229 &lt;p&gt;&lt;pre&gt;
5230 #!/bin/sh
5231
5232 # Define LSB log_* functions.
5233 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5234 # and status_of_proc is working.
5235 . /lib/lsb/init-functions
5236
5237 #
5238 # Function that starts the daemon/service
5239
5240 #
5241 do_start()
5242 {
5243 # Return
5244 # 0 if daemon has been started
5245 # 1 if daemon was already running
5246 # 2 if daemon could not be started
5247 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5248 || return 1
5249 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5250 $DAEMON_ARGS \
5251 || return 2
5252 # Add code here, if necessary, that waits for the process to be ready
5253 # to handle requests from services started subsequently which depend
5254 # on this one. As a last resort, sleep for some time.
5255 }
5256
5257 #
5258 # Function that stops the daemon/service
5259 #
5260 do_stop()
5261 {
5262 # Return
5263 # 0 if daemon has been stopped
5264 # 1 if daemon was already stopped
5265 # 2 if daemon could not be stopped
5266 # other if a failure occurred
5267 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5268 RETVAL=&quot;$?&quot;
5269 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5270 # Wait for children to finish too if this is a daemon that forks
5271 # and if the daemon is only ever run from this initscript.
5272 # If the above conditions are not satisfied then add some other code
5273 # that waits for the process to drop all resources that could be
5274 # needed by services started subsequently. A last resort is to
5275 # sleep for some time.
5276 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5277 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5278 # Many daemons don&#39;t delete their pidfiles when they exit.
5279 rm -f $PIDFILE
5280 return &quot;$RETVAL&quot;
5281 }
5282
5283 #
5284 # Function that sends a SIGHUP to the daemon/service
5285 #
5286 do_reload() {
5287 #
5288 # If the daemon can reload its configuration without
5289 # restarting (for example, when it is sent a SIGHUP),
5290 # then implement that here.
5291 #
5292 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5293 return 0
5294 }
5295
5296 SCRIPTNAME=$1
5297 scriptbasename=&quot;$(basename $1)&quot;
5298 echo &quot;SN: $scriptbasename&quot;
5299 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5300 script=&quot;$1&quot;
5301 shift
5302 . $script
5303 else
5304 exit 0
5305 fi
5306
5307 NAME=$(basename $DAEMON)
5308 PIDFILE=/var/run/$NAME.pid
5309
5310 # Exit if the package is not installed
5311 #[ -x &quot;$DAEMON&quot; ] || exit 0
5312
5313 # Read configuration variable file if it is present
5314 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5315
5316 # Load the VERBOSE setting and other rcS variables
5317 . /lib/init/vars.sh
5318
5319 case &quot;$1&quot; in
5320 start)
5321 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5322 do_start
5323 case &quot;$?&quot; in
5324 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5325 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5326 esac
5327 ;;
5328 stop)
5329 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5330 do_stop
5331 case &quot;$?&quot; in
5332 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5333 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5334 esac
5335 ;;
5336 status)
5337 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5338 ;;
5339 #reload|force-reload)
5340 #
5341 # If do_reload() is not implemented then leave this commented out
5342 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5343 #
5344 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5345 #do_reload
5346 #log_end_msg $?
5347 #;;
5348 restart|force-reload)
5349 #
5350 # If the &quot;reload&quot; option is implemented then remove the
5351 # &#39;force-reload&#39; alias
5352 #
5353 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5354 do_stop
5355 case &quot;$?&quot; in
5356 0|1)
5357 do_start
5358 case &quot;$?&quot; in
5359 0) log_end_msg 0 ;;
5360 1) log_end_msg 1 ;; # Old process is still running
5361 *) log_end_msg 1 ;; # Failed to start
5362 esac
5363 ;;
5364 *)
5365 # Failed to stop
5366 log_end_msg 1
5367 ;;
5368 esac
5369 ;;
5370 *)
5371 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5372 exit 3
5373 ;;
5374 esac
5375
5376 :
5377 &lt;/pre&gt;&lt;/p&gt;
5378
5379 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5380 lot. I did not really polish the approach, so it might not always
5381 work out of the box, but you get the idea. I did not try very hard to
5382 optimize it nor make it more robust either.&lt;/p&gt;
5383
5384 &lt;p&gt;A better argument for switching init system in Debian than reducing
5385 the size of init scripts (which is a good thing to do anyway), is to
5386 get boot system that is able to handle the kernel events sensibly and
5387 robustly, and do not depend on the boot to run sequentially. The boot
5388 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5389 </description>
5390 </item>
5391
5392 <item>
5393 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5394 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5395 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5396 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5397 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5398 remote display access is the preferred solution with oVirt and RedHat
5399 Enterprise Virtualization, and I was sad to discover the other day
5400 that the browser plugin needed to use these systems seamlessly was
5401 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5402 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5403 2013-04-01, so I decided to wrap up a package based on the great work
5404 from Cajus Pollmeier and put it in a collab-maint maintained git
5405 repository to get a package I could use. I would very much like
5406 others to help me maintain the package (or just take over, I do not
5407 mind), but as no-one had volunteered so far, I just uploaded it to
5408 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5409
5410 &lt;p&gt;The source is now available from
5411 &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;
5412 </description>
5413 </item>
5414
5415 <item>
5416 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5417 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5418 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5419 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5420 <description>&lt;p&gt;The
5421 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5422 program is a a very nice system to create virtual machine images. It
5423 create a image file, add a partition table, mount it and run
5424 debootstrap in the mounted directory to create a Debian system on a
5425 stick. Yesterday, I decided to try to teach it how to make images for
5426 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5427 of a plan to simplify the build system for
5428 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5429 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5430 the virtualbox images, but its current build system made multistrap
5431 based system for Dreamplug images, and it is lacking support for
5432 Raspberry Pi.&lt;/p&gt;
5433
5434 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5435 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5436 code and adjusted it to be able to build armel images on my amd64
5437 Debian laptop. I ended up giving vmdebootstrap five new options,
5438 allowing me to replicate the image creation process I use to make
5439 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5440 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5441 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5442 call debootstrap with --foreign and to copy the handler into the
5443 generated chroot before running the second stage. This allow
5444 vmdebootstrap to create armel images on an amd64 host. Next I added
5445 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5446 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5447 given file system type, allowing me to create an image with a vfat
5448 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5449 variant&lt;/tt&gt; option to allow me to create smaller images without the
5450 Debian base system packages installed. Finally, I added an option
5451 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5452 as a boot loader. It is not needed on the Raspberry Pi and probably
5453 most other non-x86 architectures. The changes were accepted by the
5454 upstream author of vmdebootstrap yesterday and today, and is now
5455 available from
5456 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5457 upstream project page&lt;/a&gt;.&lt;/p&gt;
5458
5459 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5460 create a small script (the customize script) to add the non-free
5461 binary blob needed to boot the Raspberry Pi and the APT source
5462 list:&lt;/p&gt;
5463
5464 &lt;p&gt;&lt;pre&gt;
5465 #!/bin/sh
5466 set -e # Exit on first error
5467 rootdir=&quot;$1&quot;
5468 cd &quot;$rootdir&quot;
5469 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5470 deb http://http.debian.net/debian/ jessie main contrib non-free
5471 EOF
5472 # Install non-free binary blob needed to boot Raspberry Pi. This
5473 # install a kernel somewhere too.
5474 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5475 -O $rootdir/usr/bin/rpi-update
5476 chmod a+x $rootdir/usr/bin/rpi-update
5477 mkdir -p $rootdir/lib/modules
5478 touch $rootdir/boot/start.elf
5479 chroot $rootdir rpi-update
5480 &lt;/pre&gt;&lt;/p&gt;
5481
5482 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5483 to build the image:&lt;/p&gt;
5484
5485 &lt;pre&gt;
5486 sudo ./vmdebootstrap \
5487 --variant minbase \
5488 --arch armel \
5489 --distribution jessie \
5490 --mirror http://http.debian.net/debian \
5491 --image test.img \
5492 --size 600M \
5493 --bootsize 64M \
5494 --boottype vfat \
5495 --log-level debug \
5496 --verbose \
5497 --no-kernel \
5498 --no-extlinux \
5499 --root-password raspberry \
5500 --hostname raspberrypi \
5501 --foreign /usr/bin/qemu-arm-static \
5502 --customize `pwd`/customize \
5503 --package netbase \
5504 --package git-core \
5505 --package binutils \
5506 --package ca-certificates \
5507 --package wget \
5508 --package kmod
5509 &lt;/pre&gt;&lt;/p&gt;
5510
5511 &lt;p&gt;The list of packages being installed are the ones needed by
5512 rpi-update to make the image bootable on the Raspberry Pi, with the
5513 exception of netbase, which is needed by debootstrap to find
5514 /etc/hosts with the minbase variant. I really wish there was a way to
5515 set up an Raspberry Pi using only packages in the Debian archive, but
5516 that is not possible as far as I know, because it boots from the GPU
5517 using a non-free binary blob.&lt;/p&gt;
5518
5519 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
5520 probably a few others installed. I have not checked the complete
5521 build dependency list.&lt;/p&gt;
5522
5523 &lt;p&gt;The resulting image will not use the hardware floating point unit
5524 on the Raspberry PI, because the armel architecture in Debian is not
5525 optimized for that use. So the images created will be a bit slower
5526 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
5527 </description>
5528 </item>
5529
5530 <item>
5531 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
5532 <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>
5533 <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>
5534 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
5535 <description>&lt;p&gt;The last few days I came across a few good causes that should get
5536 wider attention. I recommend signing and donating to each one of
5537 these. :)&lt;/p&gt;
5538
5539 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
5540 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
5541 Women program which is a Google Summer of Code like initiative to get
5542 more women involved in free software. One debian sponsor has offered
5543 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
5544 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
5545 hope you will to. :)&lt;/p&gt;
5546
5547 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
5548 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
5549 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
5550 take place these days, and their need to fund the work. I&#39;ve already
5551 donated. Are you next?&lt;/p&gt;
5552
5553 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
5554 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5555 statement under the heading
5556 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
5557 Access&lt;/a&gt; for those of us asking for more focus on open access in the
5558 Norwegian government. So far 499 signatures. I hope you will sign it
5559 too.&lt;/p&gt;
5560 </description>
5561 </item>
5562
5563 <item>
5564 <title>Videos about the Freedombox project - for inspiration and learning</title>
5565 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
5566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
5567 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
5568 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
5569 project&lt;/a&gt; have been going on for a while, and have presented the
5570 vision, ideas and solution several places. Here is a little
5571 collection of videos of talks and presentation of the project.&lt;/p&gt;
5572
5573 &lt;ul&gt;
5574
5575 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
5576 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
5577
5578 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
5579 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5580
5581 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
5582 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5583 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
5584 (Youtube)&lt;/li&gt;
5585
5586 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
5587 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
5588
5589 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
5590 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5591
5592 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
5593 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5594 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
5595
5596 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
5597 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
5598 (Youtube)&lt;/li&gt;
5599
5600 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
5601 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
5602
5603 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
5604 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
5605
5606 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
5607 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5608 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
5609
5610 &lt;/ul&gt;
5611
5612 &lt;p&gt;A larger list is available from
5613 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
5614 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
5615
5616 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
5617 Jessie is coming along quite well, and soon both Owncloud and using
5618 Tor should be available for testers of the Freedombox solution. :) In
5619 a few weeks I hope everything needed to test it is included in Debian.
5620 The withsqlite package is already in Debian, and the plinth package is
5621 pending in NEW. The third and vital part of that puzzle is the
5622 metapackage/setup framework, which is still pending an upload. Join
5623 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
5624 (#freedombox on irc.debian.org)&lt;/a&gt; and
5625 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5626 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5627 </description>
5628 </item>
5629
5630 <item>
5631 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
5632 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
5633 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
5634 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
5635 <description>&lt;p&gt;I was introduced to the
5636 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
5637 in 2010, when Eben Moglen presented his vision about serving the need
5638 of non-technical people to keep their personal information private and
5639 within the legal protection of their own homes. The idea is to give
5640 people back the power over their network and machines, and return
5641 Internet back to its intended peer-to-peer architecture. Instead of
5642 depending on a central service, the Freedombox will give everyone
5643 control over their own basic infrastructure.&lt;/p&gt;
5644
5645 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
5646 taken priority. But this summers nasty news about the misuse of trust
5647 and privilege exercised by the &quot;western&quot; intelligence gathering
5648 communities increased my eagerness to contribute to a point where I
5649 actually started working on the project a while back.&lt;/p&gt;
5650
5651 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
5652 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
5653 create a simple and cheap Debian based appliance that anyone can hook
5654 up in their home and get access to secure and private services and
5655 communication. The initial deployment platform have been the
5656 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
5657 which is a piece of hardware I do not own. So to be able to test what
5658 the current Freedombox setup look like, I had to come up with a way to install
5659 it on some hardware I do have access to. I have rewritten the
5660 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
5661 image build framework to use .deb packages instead of only copying
5662 setup into the boot images, and thanks to this rewrite I am able to
5663 set up any machine supported by Debian Wheezy as a Freedombox, using
5664 the previously mentioned deb (and a few support debs for packages
5665 missing in Debian).&lt;/p&gt;
5666
5667 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
5668 scripts
5669 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
5670 and a administrative web interface
5671 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
5672 withsqlite), as well as a privacy enhancing proxy based on
5673 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
5674 (freedombox-privoxy). There is also a web/javascript based XMPP
5675 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
5676 trying (unsuccessfully so far) to talk to the XMPP server
5677 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
5678 web interface is pluggable, and the goal is to use it to enable OpenID
5679 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5680 this is really working yet, see
5681 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
5682 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
5683 on github at the moment. The HTTP proxy is operational out of the
5684 box, and the admin web interface can be used to add/remove plinth
5685 users. I&#39;ve not been able to do anything else with it so far, but
5686 know there are several branches spread around github and other places
5687 with lots of half baked features.&lt;/p&gt;
5688
5689 &lt;p&gt;Anyway, if you want to have a look at the current state, the
5690 following recipes should work to give you a test machine to poke
5691 at.&lt;/p&gt;
5692
5693 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
5694
5695 &lt;ol&gt;
5696
5697 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
5698 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
5699 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
5700 to the Debian installer:&lt;p&gt;
5701 &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;
5702
5703 &lt;li&gt;Answer the few language/region/password questions and pick disk to
5704 install on.&lt;/li&gt;
5705
5706 &lt;li&gt;When the installation is finished and the machine have rebooted a
5707 few times, your Freedombox is ready for testing.&lt;/li&gt;
5708
5709 &lt;/ol&gt;
5710
5711 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
5712
5713 &lt;ol&gt;
5714
5715 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
5716 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
5717 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
5718 &lt;pre&gt;
5719 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
5720 &lt;/pre&gt;&lt;/li&gt;
5721 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
5722 &lt;pre&gt;
5723 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5724 apt-key add -
5725 apt-get update
5726 apt-get install freedombox-setup
5727 /usr/lib/freedombox/setup
5728 &lt;/pre&gt;&lt;/li&gt;
5729 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
5730
5731 &lt;/ol&gt;
5732
5733 &lt;p&gt;You can test it on other architectures too, but because the
5734 freedombox-privoxy package is binary, it will only work as intended on
5735 the architectures where I have had time to build the binary and put it
5736 in my APT repository. But do not let this stop you. It is only a
5737 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
5738
5739 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
5740 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
5741 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
5742 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
5743
5744 &lt;p&gt;Please let me know if this works for you, or if you have any
5745 problems. We gather on the IRC channel
5746 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
5747 irc.debian.org and the
5748 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
5749 mailing list&lt;/a&gt;.&lt;/p&gt;
5750
5751 &lt;p&gt;Once you get your freedombox operational, you can visit
5752 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
5753 welcome screen (dead end - do not be surprised if you are unable to
5754 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
5755 to look at the rest of plinth. The default user is &#39;admin&#39; and the
5756 default password is &#39;secret&#39;.&lt;/p&gt;
5757 </description>
5758 </item>
5759
5760 <item>
5761 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
5762 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
5763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
5764 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
5765 <description>&lt;p&gt;Earlier, I reported about
5766 &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
5767 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
5768 told by IBM that the original disk should be thrown away. And as
5769 there no longer was a problem if I bricked the firmware, I decided
5770 today to try to install Intel firmware to replace the Lenovo firmware
5771 currently on the disk.&lt;/p&gt;
5772
5773 &lt;p&gt;I searched the Intel site for firmware, and found
5774 &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;
5775 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5776 according to the site should contain the latest firmware for SSD
5777 disks. I inserted the broken disk in one of my spare laptops and
5778 booted the ISO from a USB stick. The disk was recognized, but the
5779 program claimed the newest firmware already were installed and refused
5780 to insert any Intel firmware. So no change, and the disk is still
5781 unable to handle write load. :( I guess the only way to get them
5782 working would be if Lenovo releases new firmware. No idea how likely
5783 that is. Anyway, just blogging about this test for completeness. I
5784 got a working Samsung disk, and see no point in spending more time on
5785 the broken disks.&lt;/p&gt;
5786 </description>
5787 </item>
5788
5789 <item>
5790 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
5791 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
5792 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
5793 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
5794 <description>&lt;p&gt;Today I switched to
5795 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
5796 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
5797 my new Thinkpad X230, which was delivered with an
5798 &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
5799 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
5800 sustained writes. My hardware supplier have been very forthcoming in
5801 trying to find a solution, and after first trying with another
5802 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
5803 disk instead to fix it once and for all. The Samsung disk survived
5804 the installation of Debian with encrypted disks (filling the disk with
5805 random data during installation killed the first two), and I thus
5806 decided to trust it with my data. I have installed it as a Debian Edu
5807 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5808 server at home using Kerberos and LDAP, and will use it as my work
5809 station from now on.&lt;/p&gt;
5810
5811 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
5812 Debian Wheezy default installation need to be tuned a bit to increase
5813 performance and increase life time of the disk. The Linux kernel and
5814 user space applications do not yet adjust automatically to such
5815 environment. To make it easier for my self, I created a draft Debian
5816 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
5817 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
5818 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
5819 is set up to adjust the setup of the machine by just installing the
5820 package. If there is any non-SSD disk in the machine, the package
5821 will refuse to install, as I did not try to write any logic to sort
5822 file systems in SSD and non-SSD file systems.&lt;/p&gt;
5823
5824 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
5825 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5826 where I set up the machine with one large encrypted partition (in
5827 addition to /boot), put LVM on top of this and set up partitions on
5828 top of this again. See the README file in the package source for the
5829 references I used to pick the settings. At the moment these
5830 parameters are tuned:&lt;/p&gt;
5831
5832 &lt;ul&gt;
5833
5834 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
5835 (adding discard to /etc/crypttab)&lt;/li&gt;
5836
5837 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
5838 this case a cryptsetup partition) by changing issue_discards from
5839 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
5840
5841 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
5842 systems.&lt;/li&gt;
5843
5844 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
5845 /etc/fstab.&lt;/li&gt;
5846
5847 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
5848
5849 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
5850 cron.daily).&lt;/li&gt;
5851
5852 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
5853 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
5854
5855 &lt;/ul&gt;
5856
5857 &lt;p&gt;During installation, I cancelled the part where the installer fill
5858 the disk with random data, as this would kill the SSD performance for
5859 little gain. My goal with the encrypted file system is to ensure
5860 those stealing my laptop end up with a brick and not a working
5861 computer. I have no hope in keeping the really resourceful people
5862 from getting the data on the disk (see
5863 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
5864 Thus I concluded that adding the discard option to crypttab is the
5865 right thing to do.&lt;/p&gt;
5866
5867 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
5868 it for SSD, but others recommended deadline and a benchmark I found
5869 indicated that deadline might be better for interactive use.&lt;/p&gt;
5870
5871 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
5872 and ext4, but read that it would give a performance hit ever time a
5873 file is removed, and thought it best to that that slowdown once a day
5874 instead of during my work.&lt;/p&gt;
5875
5876 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5877 this is already done by Debian Edu.&lt;/p&gt;
5878
5879 &lt;p&gt;I have not yet started on the user space tuning. I expect
5880 iceweasel need some tuning, and perhaps other applications too, but
5881 have not yet had time to investigate those parts.&lt;/p&gt;
5882
5883 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
5884 there.&lt;/p&gt;
5885
5886 &lt;p&gt;As for the answer to the question in the title of this blog post,
5887 as far as I know, the only solution I know about is to replace the
5888 disk. It might be possible to flash it with Intel firmware instead of
5889 the Lenovo firmware. But I have not tried and did not want to do so
5890 without approval from Lenovo as I wanted to keep the warranty on the
5891 disk until a solution was found and they wanted the broken disks
5892 back.&lt;/p&gt;
5893 </description>
5894 </item>
5895
5896 <item>
5897 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
5898 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
5899 <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>
5900 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
5901 <description>&lt;p&gt;A few days ago, I wrote about
5902 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
5903 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
5904 was dying during installation because it is unable to cope with
5905 sustained write. My supplier is in contact with
5906 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
5907 replacement disk to try to fix the problem. They decided to send an
5908 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
5909
5910 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
5911 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5912 same firmware version as the original. This time my hope raised
5913 slightly as the installation progressed, as the original disk used to
5914 die after 4-7% of the disk was written to, while this time it kept
5915 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
5916 died again and I was back on square one. I still do not have a new
5917 laptop with a disk I can trust. I can not live with a disk that might
5918 lock up when I download a new
5919 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
5920 other large files. I look forward to hearing from my supplier with
5921 the next proposal from Lenovo.&lt;/p&gt;
5922
5923 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
5924 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5925 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5926 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
5927 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5928 P/N 45N8295, P0C38732.&lt;/p&gt;
5929
5930 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
5931 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
5932 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5933 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
5934 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5935 P/N 45N8295, P0C38732.&lt;/p&gt;
5936
5937 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
5938 SA, date and WNPP values. Mentioning all the details here in case
5939 someone is able to use the information to find a way to identify the
5940 failing disk among working ones (if any such working disk actually
5941 exist).&lt;/p&gt;
5942 </description>
5943 </item>
5944
5945 <item>
5946 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
5947 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
5948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
5949 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
5950 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
5951 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5952 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
5953 member assosiation NUUG&lt;/a&gt; and
5954 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
5955 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
5956 Bitraf&lt;/a&gt;.&lt;/p&gt;
5957
5958 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
5959 welcome, and there is no fee to participate. There is on the other
5960 hand limited space, and only room for 30 people. Please put your name
5961 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
5962 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
5963 </description>
5964 </item>
5965
5966 <item>
5967 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
5968 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
5969 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
5970 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
5971 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
5972 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
5973 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
5974 time to spend on it, and it took a while to find a model I believe
5975 will do the job, but two days ago the replacement finally arrived. I
5976 ended up picking a
5977 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
5978 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5979 a roaming workstation, and it seemed to work flawlessly. But my
5980 second installation with encrypted disk was not as successful. More
5981 on that below.&lt;/p&gt;
5982
5983 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5984 important requirements (robust and with a good keyboard) are never
5985 listed in the feature list. But I did get good help from the search
5986 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5987 allowed me to limit the list of interesting laptops based on my other
5988 requirements. A bit surprising that SSD disk are not disks according
5989 to that search interface, so I had to drop specifying the number of
5990 disks from my search parameters. I also asked around among friends to
5991 get their impression on keyboards and robustness.&lt;/p&gt;
5992
5993 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
5994 X41. I am not quite convinced about the keyboard, as it is
5995 significantly wider than my old keyboard, and I have to stretch my
5996 hand a lot more to reach the edges. But the key response is fairly
5997 good and the individual key shape is fairly easy to handle, so I hope
5998 I will get used to it. My old X40 was starting to fail, and I really
5999 needed a new laptop now. :)&lt;/p&gt;
6000
6001 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6002 visit to the BIOS during boot it disable it.&lt;/p&gt;
6003
6004 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6005 lock up during load. And this happen when installing Debian Wheezy
6006 with encrypted disk, while the disk is being filled with random data.
6007 I also tested to install Ubuntu Raring, and it happen there too if I
6008 reenable the code to fill the disk with random data (it is disabled by
6009 default in Ubuntu). And the bug with is already known. It was
6010 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6011 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6012 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6013 kernel developers as
6014 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6015 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6016 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6017 Lenovo forums, both for
6018 &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
6019 2012-11-10&lt;/a&gt; and for
6020 &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
6021 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6022 reports state that the disk lock up during use if many writes are done
6023 on the disk, so it is much no use to work around the installation
6024 problem and end up with a computer that can lock up at any moment.
6025 There is even a
6026 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6027 available&lt;/a&gt; that will lock up the hard drive after running a few
6028 minutes by writing to a file.&lt;/p&gt;
6029
6030 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6031 contacting PCHELP Norway (request 01D1FDP) which handle support
6032 requests for Lenovo, his first suggestion was to upgrade the disk
6033 firmware. Unfortunately there is no newer firmware available from
6034 Lenovo, as my disk already have the most recent one (version LF1i). I
6035 hope to hear more from him today and hope the problem can be
6036 fixed. :)&lt;/p&gt;
6037 </description>
6038 </item>
6039
6040 <item>
6041 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6042 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6043 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6044 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6045 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6046 trusty old Thinkpad X41. Unfortunately I did not have much time to
6047 spend on it, but today the replacement finally arrived. I ended up
6048 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6049 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6050 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6051 this, it is installing what I hope will be a more final installation,
6052 with a encrypted hard drive to ensure any dope head stealing it end up
6053 with an expencive door stop.&lt;/p&gt;
6054
6055 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6056 important requirements (robust and with a good keyboard) are never
6057 listed in the feature list. But I did get good help from the search
6058 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6059 allowed me to limit the list of interesting laptops based on my other
6060 requirements. A bit surprising that SSD disk are not disks, so I had
6061 to drop number of disks from my search parameters.&lt;/p&gt;
6062
6063 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6064 wider than my old keyboard, and I have to stretch my hand a lot more
6065 to reach the edges. But the key response is fairly good and the
6066 individual key shape is fairly easy to handle, so I hope I will get
6067 used to it. My old X40 was starting to fail, and I really needed a
6068 new laptop now. :)&lt;/p&gt;
6069
6070 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6071 </description>
6072 </item>
6073
6074 <item>
6075 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6076 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6077 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6078 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6079 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6080 perfectly capable of, and I have to do it manually to get things
6081 working. One such task is to find out what firmware packages are
6082 needed to get the hardware on my computer working. Most often this
6083 affect the wifi card, but some times it even affect the RAID
6084 controller or the ethernet card. Today I pushed version 0.4 of the
6085 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6086 including a new script isenkram-autoinstall-firmware handling the
6087 process of asking all the loaded kernel modules what firmware files
6088 they want, find debian packages providing these files and install the
6089 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6090
6091 &lt;p&gt;&lt;pre&gt;
6092 # isenkram-autoinstall-firmware
6093 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6094 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6095 info: locating packages with the requested firmware files
6096 info: Updating APT sources after adding non-free APT source
6097 info: trying to install firmware-ipw2x00
6098 firmware-ipw2x00
6099 firmware-ipw2x00
6100 Preconfiguring packages ...
6101 Selecting previously deselected package firmware-ipw2x00.
6102 (Reading database ... 259727 files and directories currently installed.)
6103 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6104 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6105 #
6106 &lt;/pre&gt;&lt;/p&gt;
6107
6108 &lt;p&gt;When all the requested firmware is present, a simple message is
6109 printed instead:&lt;/p&gt;
6110
6111 &lt;p&gt;&lt;pre&gt;
6112 # isenkram-autoinstall-firmware
6113 info: did not find any firmware files requested by loaded kernel modules. exiting
6114 #
6115 &lt;/pre&gt;&lt;/p&gt;
6116
6117 &lt;p&gt;It could use some polish, but it is already working well and saving
6118 me some time when setting up new machines. :)&lt;/p&gt;
6119
6120 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6121 kernel modules, and look up each one of them using modinfo, to find
6122 the firmware files listed in the module meta-information. Next, it
6123 download the Contents file from a nearby APT mirror, and search for
6124 the firmware files in this file to locate the package with the
6125 requested firmware file. If the package is in the non-free section, a
6126 non-free APT source is added and the package is installed using
6127 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6128 machine.&lt;/p&gt;
6129
6130 &lt;p&gt;I hope someone find time to implement a more polished version of
6131 this script as part of the hw-detect debian-installer module, to
6132 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6133 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6134 firmware during a PXE install when the packages already are available
6135 from the nearby Debian mirror.&lt;/p&gt;
6136 </description>
6137 </item>
6138
6139 <item>
6140 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6141 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6142 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6143 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6144 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6145 the screen just turn black when Linux boot, either during installation
6146 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6147 last few years, but only recently understood the cause. I&#39;ve seen it
6148 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6149 The reason seem to be in the wiring of some laptops. The system to
6150 control the screen background light is inverted, so when Linux try to
6151 turn the brightness fully on, it end up turning it off instead. I do
6152 not know which Linux drivers are affected, but this post is about the
6153 i915 driver used by the
6154 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6155 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6156
6157 &lt;p&gt;The problem can be worked around two ways. Either by adding
6158 i915.invert_brightness=1 as a kernel option, or by adding a file in
6159 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6160 option when it load the i915 kernel module. On Debian and Ubuntu, it
6161 can be done by running these commands as root:&lt;/p&gt;
6162
6163 &lt;pre&gt;
6164 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6165 update-initramfs -u -k all
6166 &lt;/pre&gt;
6167
6168 &lt;p&gt;Since March 2012 there is
6169 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6170 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6171 hardware have this problem, and get the driver to invert the
6172 brightness setting automatically. To use it, one need to add a row in
6173 &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
6174 intel_quirks array&lt;/a&gt; in the driver source
6175 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6176 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6177 number (vendor number 8086 is assumed) and subdevice vendor and device
6178 number.&lt;/p&gt;
6179
6180 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6181 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6182
6183 &lt;p&gt;&lt;pre&gt;
6184 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6185 3rd Gen Core processor Graphics Controller [8086:0156] \
6186 (rev 09) (prog-if 00 [VGA controller])
6187 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6188 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6189 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6190 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6191 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6192 Latency: 0
6193 Interrupt: pin A routed to IRQ 42
6194 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6195 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6196 Region 4: I/O ports at 4000 [size=64]
6197 Expansion ROM at &lt;unassigned&gt; [disabled]
6198 Capabilities: &lt;access denied&gt;
6199 Kernel driver in use: i915
6200 &lt;/pre&gt;&lt;/p&gt;
6201
6202 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6203
6204 &lt;p&gt;&lt;pre&gt;
6205 struct intel_quirk intel_quirks[] = {
6206 ...
6207 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6208 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6209 ...
6210 }
6211 &lt;/pre&gt;&lt;/p&gt;
6212
6213 &lt;p&gt;According to the kernel module instructions (as seen using
6214 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6215 invert_brightness flag should be sent to the
6216 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6217 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6218 developers. But my email about the laptop sent 2013-06-03 have not
6219 yet shown up in
6220 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6221 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6222 emails from non-subscribers. Because of this, I sent my patch also to
6223 the Debian bug tracking system instead as
6224 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6225 sure the patch is not lost.&lt;/p&gt;
6226
6227 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6228 with this problem working properly with Linux. If you use Gnome, your
6229 worries should be over at this point. But if you use KDE, there is
6230 something in KDE ignoring the invert_brightness setting and turning on
6231 the screen during login. I&#39;ve reported it to Debian as
6232 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6233 have no idea yet how to figure out exactly what subsystem is doing
6234 this. Perhaps you can help? Perhaps you know what the Gnome
6235 developers did to handle this, and this can give a clue to the KDE
6236 developers? Or you know where in KDE the screen brightness is changed
6237 during login? If so, please update the BTS report (or get in touch if
6238 you do not know how to update BTS).&lt;/p&gt;
6239
6240 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6241 acpi_backlight=vendor, to disable ACPI backlight support completely,
6242 as the ACPI information on the machine is trash and it is better to
6243 leave it to the intel video driver to control the screen
6244 backlight.&lt;/p&gt;
6245 </description>
6246 </item>
6247
6248 <item>
6249 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6250 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6251 <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>
6252 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6253 <description>&lt;p&gt;Two days ago, I asked
6254 &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
6255 I could install Linux on a Packard Bell EasyNote LV computer
6256 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6257 with the obstacles put in the way of Linux users on a laptop with UEFI
6258 and Windows 8.&lt;/p&gt;
6259
6260 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6261 secure booting or fast boot. I suspect fast boot was the problem,
6262 causing the firmware to boot directly from HD without considering any
6263 key presses and alternative devices, but do not know UEFI settings
6264 enough to tell.&lt;/p&gt;
6265
6266 &lt;p&gt;There is no way to install Linux on the machine in question without
6267 opening the box and disconnecting the hard drive! This is as far as I
6268 can tell, the only way to get access to the firmware setup menu
6269 without accepting the Windows 8 license agreement. I am told (and
6270 found description on how to) that it is possible to configure the
6271 firmware setup once booted into Windows 8. But as I believe the terms
6272 of that agreement are completely unacceptable, accepting the license
6273 was never an alternative. I do not enter agreements I do not intend
6274 to follow.&lt;/p&gt;
6275
6276 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6277 waste many hours on this, but luckily there was a way to get it to
6278 work. But I would not recommend it to anyone planning to run Linux on
6279 it, and I have become sceptical to Windows 8 certified laptops. Is
6280 this the way Linux will be forced out of the market place, by making
6281 it close to impossible for &quot;normal&quot; users to install Linux without
6282 accepting the Microsoft Windows license terms? Or at least not
6283 without risking to loose the warranty?&lt;/p&gt;
6284
6285 &lt;p&gt;I&#39;ve updated the
6286 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6287 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6288 do not have to struggle as much as I did to get Linux into the
6289 machine.&lt;/p&gt;
6290
6291 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6292 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6293 </description>
6294 </item>
6295
6296 <item>
6297 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6298 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6299 <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>
6300 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6301 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6302 new laptops for my parents and a few others. I bought Packard Bell
6303 Easynote LV to run Kubuntu on and use as their home computer. But I
6304 am completely unable to figure out how to install Linux on it. The
6305 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6306 instead of a BIOS to boot.&lt;/p&gt;
6307
6308 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6309 to get it to boot the Linux installer from my USB stick. I have yet
6310 to try the DVD install, and still hope it will work. when I turn on
6311 the computer, there is no information on what buttons to press to get
6312 the normal boot menu. I expect to get some boot menu to select PXE or
6313 USB stick booting. When booting, it first ask for the language to
6314 use, then for some regional settings, and finally if I will accept the
6315 Windows 8 terms of use. As these terms are completely unacceptable to
6316 me, I have no other choice but to turn off the computer and try again
6317 to get it to boot the Linux installer.&lt;/p&gt;
6318
6319 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6320 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6321 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6322 installed on this machine, please get in touch or update that wiki
6323 page. If I can&#39;t find a way to install Linux, I will have to return
6324 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6325
6326 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6327 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6328 on new Laptops?&lt;/p&gt;
6329 </description>
6330 </item>
6331
6332 <item>
6333 <title>How to transform a Debian based system to a Debian Edu installation</title>
6334 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6335 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6336 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6337 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6338 an operating system based on Debian intended for use in schools. It
6339 contain a turn-key solution for the computer network provided to
6340 pupils in the primary schools. It provide both the central server,
6341 network boot servers and desktop environments with heaps of
6342 educational software. The project was founded almost 12 years ago,
6343 2001-07-02. If you want to support the project, which is in need for
6344 cash to fund developer gatherings and other project related activity,
6345 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6346 donate some money&lt;/a&gt;.
6347
6348 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6349 lists and elsewhere, is the question on how to transform a Debian or
6350 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6351 hard, and last week I wrote a script to replicate the steps done by
6352 the Debian Edu installer.&lt;/p&gt;
6353
6354 &lt;p&gt;The script,
6355 &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;
6356 in the debian-edu-config package, will go through these six steps and
6357 transform an existing Debian Wheezy or Ubuntu (untested) installation
6358 into a Debian Edu Workstation:&lt;/p&gt;
6359
6360 &lt;ol&gt;
6361
6362 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6363 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6364 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6365 our configuration.&lt;/li&gt;
6366 &lt;li&gt;Preseed debconf database with profile setup in
6367 /etc/debian-edu/config, and run tasksel to install packages
6368 according to the profile specified in the config above,
6369 overriding some of the Debian automation machinery.&lt;/li&gt;
6370 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6371 that could not be done using preseeding.&lt;/li&gt;
6372 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6373
6374 &lt;/ol&gt;
6375
6376 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6377 replicated like this. Disk partitioning and LVM setup, for example.
6378 So this script just assume there is enough disk space to install all
6379 the needed packages.&lt;/p&gt;
6380
6381 &lt;p&gt;The script was created to help a Debian Edu student working on
6382 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6383 Debian Edu client, and using it he can take the existing
6384 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6385 transform it into a fully functioning Debian Edu Workstation (or
6386 Roaming Workstation, or whatever :).&lt;/p&gt;
6387
6388 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6389 If a LXDE based Roaming workstation is wanted instead, modify the
6390 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6391
6392 &lt;p&gt;&lt;pre&gt;
6393 PROFILE=&quot;Roaming-Workstation&quot;
6394 DESKTOP=&quot;lxde&quot;
6395 &lt;/pre&gt;&lt;/p&gt;
6396
6397 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6398 the cloud, by starting with a virtual Debian installation at some
6399 virtual hosting service and setting up all the services on first
6400 boot.&lt;/p&gt;
6401 </description>
6402 </item>
6403
6404 <item>
6405 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6406 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6407 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6408 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6409 <description>&lt;P&gt;In January,
6410 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6411 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6412 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6413 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6414 marvellous construction system from Denmark. We also created
6415 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6416 a place to take notes and write down our plans and hopes. And several
6417 people showed up to help. I was very happy to see the effect of my
6418 call. Since the small start, we have a debtags tag
6419 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6420 tag for LEGO related packages, and now count 10 packages related to
6421 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6422
6423 &lt;p&gt;&lt;table&gt;
6424 &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;
6425 &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;
6426 &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;
6427 &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;
6428 &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;
6429 &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;
6430 &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;
6431 &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;
6432 &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;
6433 &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;
6434 &lt;/table&gt;&lt;/p&gt;
6435
6436 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6437 currently available in Jessie/testing. leocad is so far only
6438 available in experimental.&lt;/p&gt;
6439
6440 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6441 adding the rest of the great free software tools available on Linux
6442 for LEGO designers.&lt;/p&gt;
6443 </description>
6444 </item>
6445
6446 <item>
6447 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6448 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6450 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6451 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6452 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6453 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6454 Debian release, and I expect to move my machines at home over to it fairly
6455 soon.&lt;/p&gt;
6456
6457 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6458 in particular make me very happy to see included. The
6459 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6460 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6461 included for the first time. Alongside similar programs like
6462 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6463 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6464 it allow for visual programming where syntax errors can not happen,
6465 and a friendly programming environment for learning to control the
6466 computer. Scratch will also be included in the next release of Debian
6467 Edu.&lt;/a&gt;
6468
6469 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6470 Edu/Skolelinux release too. The
6471 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6472 alpha release&lt;/a&gt; went out last week, and the next should soon
6473 follow.&lt;p&gt;
6474 </description>
6475 </item>
6476
6477 <item>
6478 <title>Isenkram 0.2 finally in the Debian archive</title>
6479 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6480 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6481 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6482 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6483 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6484 for many months. I uploaded it to the Debian experimental suite
6485 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6486
6487 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6488 install to work with a pluggable hardware device. The suggestion pop
6489 up when the device is plugged in. For example if a Lego Mindstorm NXT
6490 is inserted, it will suggest to install the program needed to program
6491 the NXT controller. Give it a go, and report bugs and suggestions to
6492 BTS. :)&lt;/p&gt;
6493 </description>
6494 </item>
6495
6496 <item>
6497 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
6498 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
6499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
6500 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
6501 <description>&lt;p&gt;My
6502 &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
6503 bitcoin related blog post&lt;/a&gt; mentioned that the new
6504 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
6505 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6506 2013-01-19, and have been available in unstable since then. It was
6507 automatically copied to Ubuntu, and is available in their Raring
6508 version too.&lt;/p&gt;
6509
6510 &lt;p&gt;But there is a strange problem with the build that block this new
6511 version from being available on the i386 and kfreebsd-i386
6512 architectures. For some strange reason, the autobuilders in Debian
6513 for these architectures fail to run the test suite on these
6514 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
6515 We are so far unable to reproduce it when building it manually, and
6516 no-one have been able to propose a fix. If you got an idea what is
6517 failing, please let us know via the BTS.&lt;/p&gt;
6518
6519 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
6520 I often run low on disk space, is the fact that the client will exit
6521 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
6522 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
6523 it. :)&lt;/p&gt;
6524
6525 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6526 activities, please send Bitcoin donations to my address
6527 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6528 </description>
6529 </item>
6530
6531 <item>
6532 <title>Welcome to the world, Isenkram!</title>
6533 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
6534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
6535 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
6536 <description>&lt;p&gt;Yesterday, I
6537 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
6538 for testers&lt;/a&gt; for my prototype for making Debian better at handling
6539 pluggable hardware devices, which I
6540 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
6541 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
6542 up, and caused me to really want to to open up the development to more
6543 people. But before I did this, I want to come up with a sensible name
6544 for this project. Today I finally decided on a new name, and I have
6545 renamed the project from hw-support-handler to this new name. In the
6546 process, I moved the source to git and made it available as a
6547 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
6548 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
6549 To fetch and build the latest version of the source, use&lt;/p&gt;
6550
6551 &lt;pre&gt;
6552 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6553 cd isenkram &amp;&amp; git-buildpackage -us -uc
6554 &lt;/pre&gt;
6555
6556 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
6557 want to hack on the source or improve the package, please go ahead.
6558 But please talk to me first on IRC or via email before you do major
6559 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
6560
6561 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
6562 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6563 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
6564 the German word eisenkram, for those that are familiar with that
6565 word.&lt;/p&gt;
6566
6567 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
6568 instructions, to avoid confusing people with an error from the signing
6569 process.&lt;/p&gt;
6570
6571 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
6572 clone argument to avoid the need for authentication.&lt;/p&gt;
6573 </description>
6574 </item>
6575
6576 <item>
6577 <title>First prototype ready making hardware easier to use in Debian</title>
6578 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
6579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
6580 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
6581 <description>&lt;p&gt;Early this month I set out to try to
6582 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
6583 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
6584 prototype is working, and it is ready for a larger audience. To test
6585 it, fetch the
6586 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
6587 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
6588 package. You might have to log out and in again activate the
6589 autostart script.&lt;/p&gt;
6590
6591 &lt;p&gt;The design is simple:&lt;/p&gt;
6592
6593 &lt;ul&gt;
6594
6595 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
6596 hw-support-handlerd to start when the user log in.&lt;/li&gt;
6597
6598 &lt;li&gt;This program listen for kernel events about new hardware (directly
6599 from the kernel like udev does), not using HAL dbus events as I
6600 initially did.&lt;/li&gt;
6601
6602 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
6603 the APT database, a database
6604 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
6605 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
6606
6607 &lt;li&gt;If a package is mapped to the hardware in question, the package
6608 isn&#39;t installed yet and this is the first time the hardware was
6609 plugged in, show a desktop notification suggesting to install the
6610 package or packages.&lt;/li&gt;
6611
6612 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
6613 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
6614
6615 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
6616 package while showing progress information in a window.&lt;/li&gt;
6617
6618 &lt;/ul&gt;
6619
6620 &lt;p&gt;I still need to come up with a better name for the system. Here
6621 are some screen shots showing the prototype in action. First the
6622 notification, then the password request, and finally the request to
6623 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
6624
6625 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
6626 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
6627 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
6628 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
6629 &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;
6630
6631 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
6632 is already useful. The database of hardware to package mappings also
6633 need more work. It is currently compatible with the Ubuntu way of
6634 storing such information in the package control file, but could be
6635 changed to use other formats instead or in addition to the current
6636 method. I&#39;ve dropped the use of discover for this mapping, as the
6637 modalias approach is more flexible and easier to use on Linux as long
6638 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
6639
6640 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
6641 here is the command required to check out and build the source: Use
6642 &#39;&lt;tt&gt;svn checkout
6643 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6644 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
6645 devscripts package.&lt;/p&gt;
6646
6647 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
6648 renamed to Isenkram and the source moved from the Debian Edu
6649 subversion repository to a Debian collab-maint git repository. See
6650 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
6651 instructions&lt;/a&gt; for details.&lt;/p&gt;
6652 </description>
6653 </item>
6654
6655 <item>
6656 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
6657 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
6658 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
6659 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
6660 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
6661 suddenly in bed. With a quiet whimper, it went completely quiet and
6662 black. The power button was no longer able to turn it on. It was a
6663 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6664 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6665 Compaq I had before that. Now I need to find a replacement. To keep
6666 going during Christmas, I moved the one year old SSD disk to my old
6667 X40 where it fitted (only one I had left that could use it), but it is
6668 not a durable solution.
6669
6670 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
6671 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
6672
6673 &lt;ul&gt;
6674
6675 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
6676 than A4).&lt;/li&gt;
6677 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
6678 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
6679 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
6680 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
6681 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
6682 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
6683 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
6684 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
6685 size).&lt;/li&gt;
6686 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
6687 X.org packages.&lt;/li&gt;
6688 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
6689 the time).
6690
6691 &lt;/ul&gt;
6692
6693 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
6694 list. The reason is simply that the specifications on laptops the
6695 last 10-15 years have been sufficient for my needs, and I have to look
6696 at other features to choose my laptop. But are there still made as
6697 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6698 robust, and Thinkpads seem to be heading in the wrong direction since
6699 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
6700 still be useful.&lt;/p&gt;
6701
6702 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
6703 external keyboard? I&#39;ll have to check the
6704 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
6705 well-supported laptops, or perhaps just buy one preinstalled from one
6706 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
6707 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
6708 </description>
6709 </item>
6710
6711 <item>
6712 <title>How to find a browser plugin supporting a given MIME type</title>
6713 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
6714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
6715 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
6716 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
6717 install to get support for a given MIME type. Thanks to
6718 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
6719 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
6720 Unfortunately, not very many packages provide the needed meta
6721 information, Anyway, here is a small script to look up all browser
6722 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
6723
6724 &lt;pre&gt;
6725 #!/usr/bin/python
6726 import sys
6727 import apt
6728 def pkgs_handling_mimetype(mimetype):
6729 cache = apt.Cache()
6730 cache.open(None)
6731 thepkgs = []
6732 for pkg in cache:
6733 version = pkg.candidate
6734 if version is None:
6735 version = pkg.installed
6736 if version is None:
6737 continue
6738 record = version.record
6739 if not record.has_key(&#39;Npp-MimeType&#39;):
6740 continue
6741 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
6742 for t in mime_types:
6743 t = t.rstrip().strip()
6744 if t == mimetype:
6745 thepkgs.append(pkg.name)
6746 return thepkgs
6747 mimetype = &quot;audio/ogg&quot;
6748 if 1 &lt; len(sys.argv):
6749 mimetype = sys.argv[1]
6750 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
6751 for pkg in pkgs_handling_mimetype(mimetype):
6752 print &quot; %s&quot; %pkg
6753 &lt;/pre&gt;
6754
6755 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
6756
6757 &lt;pre&gt;
6758 % ./apt-find-browserplug-for-mimetype
6759 Browser plugin packages supporting audio/ogg:
6760 gecko-mediaplayer
6761 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6762 Browser plugin packages supporting application/x-shockwave-flash:
6763 browser-plugin-gnash
6764 %
6765 &lt;/pre&gt;
6766
6767 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
6768 itself to query for plugins and propose to install the needed
6769 packages. It would be great if Debian supported such feature too. Is
6770 anyone working on adding it?&lt;/p&gt;
6771
6772 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
6773 request for icweasel support for this feature is
6774 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
6775 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
6776 of manpower and wish for a different design is the reason thus feature
6777 is not yet in iceweasel from Debian.&lt;/p&gt;
6778 </description>
6779 </item>
6780
6781 <item>
6782 <title>What is the most supported MIME type in Debian?</title>
6783 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
6784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
6785 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
6786 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
6787 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
6788 proposal to make it possible for a Desktop application to propose to
6789 the user some package to install to gain support for a given MIME
6790 type, font, library etc. that is currently missing. With such
6791 mechanism in place, it would be possible for the desktop to
6792 automatically propose and install leocad if some LDraw file is
6793 downloaded by the browser.&lt;/p&gt;
6794
6795 &lt;p&gt;To get some idea about the current content of the archive, I decided
6796 to write a simple program to extract all .desktop files from the
6797 Debian archive and look up the claimed MIME support there. The result
6798 can be found on the
6799 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
6800 site&lt;/a&gt;. Using the collected information, it become possible to
6801 answer the question in the title. Here are the 20 most supported MIME
6802 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6803 The complete list is available from the link above.&lt;/p&gt;
6804
6805 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
6806
6807 &lt;pre&gt;
6808 count MIME type
6809 ----- -----------------------
6810 32 text/plain
6811 30 audio/mpeg
6812 29 image/png
6813 28 image/jpeg
6814 27 application/ogg
6815 26 audio/x-mp3
6816 25 image/tiff
6817 25 image/gif
6818 22 image/bmp
6819 22 audio/x-wav
6820 20 audio/x-flac
6821 19 audio/x-mpegurl
6822 18 video/x-ms-asf
6823 18 audio/x-musepack
6824 18 audio/x-mpeg
6825 18 application/x-ogg
6826 17 video/mpeg
6827 17 audio/x-scpls
6828 17 audio/ogg
6829 16 video/x-ms-wmv
6830 &lt;/pre&gt;
6831
6832 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
6833
6834 &lt;pre&gt;
6835 count MIME type
6836 ----- -----------------------
6837 33 text/plain
6838 32 image/png
6839 32 image/jpeg
6840 29 audio/mpeg
6841 27 image/gif
6842 26 image/tiff
6843 26 application/ogg
6844 25 audio/x-mp3
6845 22 image/bmp
6846 21 audio/x-wav
6847 19 audio/x-mpegurl
6848 19 audio/x-mpeg
6849 18 video/mpeg
6850 18 audio/x-scpls
6851 18 audio/x-flac
6852 18 application/x-ogg
6853 17 video/x-ms-asf
6854 17 text/html
6855 17 audio/x-musepack
6856 16 image/x-xbitmap
6857 &lt;/pre&gt;
6858
6859 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
6860
6861 &lt;pre&gt;
6862 count MIME type
6863 ----- -----------------------
6864 31 text/plain
6865 31 image/png
6866 31 image/jpeg
6867 29 audio/mpeg
6868 28 application/ogg
6869 27 image/gif
6870 26 image/tiff
6871 26 audio/x-mp3
6872 23 audio/x-wav
6873 22 image/bmp
6874 21 audio/x-flac
6875 20 audio/x-mpegurl
6876 19 audio/x-mpeg
6877 18 video/x-ms-asf
6878 18 video/mpeg
6879 18 audio/x-scpls
6880 18 application/x-ogg
6881 17 audio/x-musepack
6882 16 video/x-ms-wmv
6883 16 video/x-msvideo
6884 &lt;/pre&gt;
6885
6886 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
6887 information mentioned in DEP-11. I have not yet had time to look at
6888 it, but hope the PackageKit people in Debian are on top of these
6889 issues.&lt;/p&gt;
6890
6891 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
6892 discovering a typo in my script.&lt;/p&gt;
6893 </description>
6894 </item>
6895
6896 <item>
6897 <title>Using modalias info to find packages handling my hardware</title>
6898 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
6899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
6900 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
6901 <description>&lt;p&gt;Yesterday, I wrote about the
6902 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
6903 values provided by the Linux kernel&lt;/a&gt; following my hope for
6904 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
6905 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
6906 modalias values attached to package names can be used to map packages
6907 to hardware. This allow the system to look up and suggest relevant
6908 packages when I plug in some new hardware into my machine, and replace
6909 discover and discover-data as the database used to map hardware to
6910 packages.&lt;/p&gt;
6911
6912 &lt;p&gt;I create a modaliases file with entries like the following,
6913 containing package name, kernel module name (if relevant, otherwise
6914 the package name) and globs matching the relevant hardware
6915 modalias.&lt;/p&gt;
6916
6917 &lt;p&gt;&lt;blockquote&gt;
6918 Package: package-name
6919 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
6920 &lt;/blockquote&gt;&lt;/p&gt;
6921
6922 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
6923 for a given modalias value using this file.&lt;/p&gt;
6924
6925 &lt;p&gt;An entry like this would suggest the video and picture application
6926 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
6927
6928 &lt;p&gt;&lt;blockquote&gt;
6929 Package: cheese
6930 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
6931 &lt;/blockquote&gt;&lt;/p&gt;
6932
6933 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
6934 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
6935
6936 &lt;p&gt;&lt;blockquote&gt;
6937 Package: pcmciautils
6938 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6939 &lt;/blockquote&gt;&lt;/p&gt;
6940
6941 &lt;p&gt;An entry like this would suggest the package colorhug-client when
6942 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
6943
6944 &lt;p&gt;&lt;blockquote&gt;
6945 Package: colorhug-client
6946 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
6947 &lt;/blockquote&gt;&lt;/p&gt;
6948
6949 &lt;p&gt;I believe the format is compatible with the format of the Packages
6950 file in the Debian archive. Ubuntu already uses their Packages file
6951 to store their mappings from packages to hardware.&lt;/p&gt;
6952
6953 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
6954 announce the hardware it support in a way my prototype understand.
6955 This allow those publishing packages in an APT source outside the
6956 Debian archive as well as those backporting packages to make sure the
6957 hardware mapping are included in the package meta information. I&#39;ve
6958 tested such header in the pymissile package, and its modalias mapping
6959 is working as it should with my prototype. It even made it to Ubuntu
6960 Raring.&lt;/p&gt;
6961
6962 &lt;p&gt;To test if it was possible to look up supported hardware using only
6963 the shell tools available in the Debian installer, I wrote a shell
6964 implementation of the lookup code. The idea is to create files for
6965 each modalias and let the shell do the matching. Please check out and
6966 try the
6967 &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;
6968 shell script. It run without any extra dependencies and fetch the
6969 hardware mappings from the Debian archive and the subversion
6970 repository where I currently work on my prototype.&lt;/p&gt;
6971
6972 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
6973 install yubikey-personalization:&lt;/p&gt;
6974
6975 &lt;p&gt;&lt;blockquote&gt;
6976 % ./hw-support-lookup
6977 &lt;br&gt;yubikey-personalization
6978 &lt;br&gt;%
6979 &lt;/blockquote&gt;&lt;/p&gt;
6980
6981 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6982 propose to install the pcmciautils package:&lt;/p&gt;
6983
6984 &lt;p&gt;&lt;blockquote&gt;
6985 % ./hw-support-lookup
6986 &lt;br&gt;pcmciautils
6987 &lt;br&gt;%
6988 &lt;/blockquote&gt;&lt;/p&gt;
6989
6990 &lt;p&gt;If you know of any hardware-package mapping that should be added to
6991 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
6992 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
6993
6994 &lt;p&gt;It could be possible to generate several of the mappings between
6995 packages and hardware. One source would be to look at packages with
6996 kernel modules, ie packages with *.ko files in /lib/modules/, and
6997 extract their modalias information. Another would be to look at
6998 packages with udev rules, ie packages with files in
6999 /lib/udev/rules.d/, and extract their vendor/model information to
7000 generate a modalias matching rule. I have not tested any of these to
7001 see if it work.&lt;/p&gt;
7002
7003 &lt;p&gt;If you want to help implementing a system to let us propose what
7004 packages to install when new hardware is plugged into a Debian
7005 machine, please send me an email or talk to me on
7006 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7007 </description>
7008 </item>
7009
7010 <item>
7011 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7012 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7014 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7015 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7016 information, to find the packages that support a given piece of
7017 hardware, I refreshed my memory regarding modalias values, and decided
7018 to document the details. Here are my findings so far, also available
7019 in
7020 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7021 Debian Edu subversion repository&lt;/a&gt;:
7022
7023 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7024
7025 &lt;p&gt;This document try to explain what the different types of modalias
7026 values stands for. It is in part based on information from
7027 &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;,
7028 &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;,
7029 &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
7030 &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;.
7031
7032 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7033 this shell script:&lt;/p&gt;
7034
7035 &lt;pre&gt;
7036 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7037 &lt;/pre&gt;
7038
7039 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7040 using modinfo:&lt;/p&gt;
7041
7042 &lt;pre&gt;
7043 % /sbin/modinfo psmouse | grep alias:
7044 alias: serio:ty05pr*id*ex*
7045 alias: serio:ty01pr*id*ex*
7046 %
7047 &lt;/pre&gt;
7048
7049 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7050
7051 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7052 Bridge memory controller:&lt;/p&gt;
7053
7054 &lt;p&gt;&lt;blockquote&gt;
7055 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7056 &lt;/blockquote&gt;&lt;/p&gt;
7057
7058 &lt;p&gt;This represent these values:&lt;/p&gt;
7059
7060 &lt;pre&gt;
7061 v 00008086 (vendor)
7062 d 00002770 (device)
7063 sv 00001028 (subvendor)
7064 sd 000001AD (subdevice)
7065 bc 06 (bus class)
7066 sc 00 (bus subclass)
7067 i 00 (interface)
7068 &lt;/pre&gt;
7069
7070 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7071 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7072 0600. The 0600 class is a host bridge. Other useful bus values are
7073 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7074
7075 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7076 means.&lt;/p&gt;
7077
7078 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7079
7080 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7081 USB hub in a laptop:&lt;/p&gt;
7082
7083 &lt;p&gt;&lt;blockquote&gt;
7084 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7085 &lt;/blockquote&gt;&lt;/p&gt;
7086
7087 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7088
7089 &lt;pre&gt;
7090 v 1D6B (device vendor)
7091 p 0001 (device product)
7092 d 0206 (bcddevice)
7093 dc 09 (device class)
7094 dsc 00 (device subclass)
7095 dp 00 (device protocol)
7096 ic 09 (interface class)
7097 isc 00 (interface subclass)
7098 ip 00 (interface protocol)
7099 &lt;/pre&gt;
7100
7101 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7102 class is in the interface class section. For a simple USB web camera,
7103 these alias entries show up:&lt;/p&gt;
7104
7105 &lt;p&gt;&lt;blockquote&gt;
7106 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7107 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7108 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7109 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7110 &lt;/blockquote&gt;&lt;/p&gt;
7111
7112 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7113 camera), 0101 is audio control device and 0102 is audio streaming (aka
7114 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7115
7116 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7117
7118 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7119 receiver in a Thinkpad X40:&lt;/p&gt;
7120
7121 &lt;p&gt;&lt;blockquote&gt;
7122 acpi:IBM0071:PNP0511:
7123 &lt;/blockquote&gt;&lt;/p&gt;
7124
7125 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7126
7127 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7128
7129 &lt;p&gt;The DMI table contain lots of information about the computer case
7130 and model. This is an entry for a IBM Thinkpad X40, fetched from
7131 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7132
7133 &lt;p&gt;&lt;blockquote&gt;
7134 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7135 &lt;/blockquote&gt;&lt;/p&gt;
7136
7137 &lt;p&gt;The values present are&lt;/p&gt;
7138
7139 &lt;pre&gt;
7140 bvn IBM (BIOS vendor)
7141 bvr 1UETB6WW(1.66) (BIOS version)
7142 bd 06/15/2005 (BIOS date)
7143 svn IBM (system vendor)
7144 pn 2371H4G (product name)
7145 pvr ThinkPadX40 (product version)
7146 rvn IBM (board vendor)
7147 rn 2371H4G (board name)
7148 rvr NotAvailable (board version)
7149 cvn IBM (chassis vendor)
7150 ct 10 (chassis type)
7151 cvr NotAvailable (chassis version)
7152 &lt;/pre&gt;
7153
7154 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7155 found in the dmidecode source:&lt;/p&gt;
7156
7157 &lt;pre&gt;
7158 3 Desktop
7159 4 Low Profile Desktop
7160 5 Pizza Box
7161 6 Mini Tower
7162 7 Tower
7163 8 Portable
7164 9 Laptop
7165 10 Notebook
7166 11 Hand Held
7167 12 Docking Station
7168 13 All In One
7169 14 Sub Notebook
7170 15 Space-saving
7171 16 Lunch Box
7172 17 Main Server Chassis
7173 18 Expansion Chassis
7174 19 Sub Chassis
7175 20 Bus Expansion Chassis
7176 21 Peripheral Chassis
7177 22 RAID Chassis
7178 23 Rack Mount Chassis
7179 24 Sealed-case PC
7180 25 Multi-system
7181 26 CompactPCI
7182 27 AdvancedTCA
7183 28 Blade
7184 29 Blade Enclosing
7185 &lt;/pre&gt;
7186
7187 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7188 table. For example my home server is a tower, but the DMI modalias
7189 claim it is a desktop.&lt;/p&gt;
7190
7191 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7192
7193 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7194 test machine:&lt;/p&gt;
7195
7196 &lt;p&gt;&lt;blockquote&gt;
7197 serio:ty01pr00id00ex00
7198 &lt;/blockquote&gt;&lt;/p&gt;
7199
7200 &lt;p&gt;The values present are&lt;/p&gt;
7201
7202 &lt;pre&gt;
7203 ty 01 (type)
7204 pr 00 (prototype)
7205 id 00 (id)
7206 ex 00 (extra)
7207 &lt;/pre&gt;
7208
7209 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7210 the valid values are.&lt;/p&gt;
7211
7212 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7213
7214 &lt;p&gt;There are heaps of other modalias subtypes according to
7215 file2alias.c. There is the rest of the list from that source: amba,
7216 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7217 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7218 vmbus, x86cpu and zorro. I did not spend time documenting all of
7219 these, as they do not seem relevant for my intended use with mapping
7220 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7221
7222 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7223
7224 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7225 one can use the following shell script:&lt;/p&gt;
7226
7227 &lt;pre&gt;
7228 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7229 echo &quot;$id&quot; ; \
7230 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7231 done
7232 &lt;/pre&gt;
7233
7234 &lt;p&gt;The output can look like this (only the first few entries as the
7235 list is very long on my test machine):&lt;/p&gt;
7236
7237 &lt;pre&gt;
7238 acpi:ACPI0003:
7239 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7240 acpi:device:
7241 FATAL: Module acpi:device: not found.
7242 acpi:IBM0068:
7243 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7244 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7245 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7246 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7247 acpi:IBM0071:PNP0511:
7248 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7249 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7250 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7251 [...]
7252 &lt;/pre&gt;
7253
7254 &lt;p&gt;If you want to help implementing a system to let us propose what
7255 packages to install when new hardware is plugged into a Debian
7256 machine, please send me an email or talk to me on
7257 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7258
7259 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7260 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7261 in /sys/ with space in them.&lt;/p&gt;
7262 </description>
7263 </item>
7264
7265 <item>
7266 <title>Moved the pymissile Debian packaging to collab-maint</title>
7267 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7269 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7270 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7271 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7272 Launcher and updated the Debian package
7273 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7274 sure udev will fix the device permissions when it is plugged in. I
7275 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7276 hopefully make the package be proposed by jockey in Ubuntu when a user
7277 plug in his rocket launcher. In the process I moved the source to a
7278 git repository under collab-maint, to make it easier for any DD to
7279 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7280 is not very active, but the software still work for me even after five
7281 years of relative silence. The new git repository is not listed in
7282 the uploaded package yet, because I want to test the other changes a
7283 bit more before I upload the new version. If you want to check out
7284 the new version with a .desktop file included, visit the
7285 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7286 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7287 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7288 </description>
7289 </item>
7290
7291 <item>
7292 <title>Lets make hardware dongles easier to use in Debian</title>
7293 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7295 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7296 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7297 general, is that there is a great package management system with the
7298 ability to automatically install software packages by downloading them
7299 from the distribution mirrors, but no way to get it to automatically
7300 install the packages I need to use the hardware I plug into my
7301 machine. Even if the package to use it is easily available from the
7302 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7303 suggest to automatically install the python-nxt, nbc and t2n packages
7304 I need to talk to it. When I plug in a Yubikey, it could propose the
7305 yubikey-personalization package. The information required to do this
7306 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7307
7308 &lt;p&gt;Some years ago, I proposed to
7309 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7310 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7311 simple:
7312
7313 &lt;ul&gt;
7314
7315 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7316 starting when a user log in.&lt;/li&gt;
7317
7318 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7319 hardware is inserted into the computer.&lt;/li&gt;
7320
7321 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7322 database mapping to packages, and take note of any non-installed
7323 packages.&lt;/li&gt;
7324
7325 &lt;li&gt;Show a message to the user proposing to install the discovered
7326 package, and make it easy to install it.&lt;/li&gt;
7327
7328 &lt;/ul&gt;
7329
7330 &lt;p&gt;I am not sure what the best way to implement this is, but my
7331 initial idea was to use dbus events to discover new hardware, the
7332 discover database to find packages and
7333 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7334 packages.&lt;/p&gt;
7335
7336 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7337 draft package is now checked into
7338 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7339 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7340 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7341 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7342 the relevant packages in Debian, and uploaded a new version
7343 2.2013.01.09 to unstable. I also discovered that the current
7344 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7345 package in Debian no longer discovered any USB devices, because
7346 /proc/bus/usb/devices is no longer present. I ported it to use
7347 libusb as a fall back option to get it working. The fixed package
7348 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7349 because of the freeze).&lt;/p&gt;
7350
7351 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7352 desktop notification to show up (only once, the first time it is
7353 inserted):&lt;/p&gt;
7354
7355 &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;
7356
7357 &lt;p&gt;For this prototype to be really useful, some way to automatically
7358 install the proposed packages by pressing the &quot;Please install
7359 program(s)&quot; button should to be implemented.&lt;/p&gt;
7360
7361 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7362 happen, please help me update the discover-data database with mappings
7363 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7364 list the package you would like to have installed when a given
7365 hardware device is inserted into your computer, and report bugs using
7366 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7367 such mapping, please let me know.&lt;/p&gt;
7368
7369 &lt;p&gt;This prototype need more work, and there are several questions that
7370 should be considered before it is ready for production use. Is dbus
7371 the correct way to detect new hardware? At the moment I look for HAL
7372 dbus events on the system bus, because that is the events I could see
7373 on my Debian Squeeze KDE desktop. Are there better events to use?
7374 How should the user be notified? Is the desktop notification
7375 mechanism the best option, or should the background daemon raise a
7376 popup instead? How should packages be installed? When should they
7377 not be installed?&lt;/p&gt;
7378
7379 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7380 please send me an email. :)&lt;/p&gt;
7381 </description>
7382 </item>
7383
7384 <item>
7385 <title>New IRC channel for LEGO designers using Debian</title>
7386 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7388 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7389 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7390 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7391 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7392 discovered I had to build all the tools myself because none were
7393 already in Debian Squeeze. If Debian support for LEGO is something
7394 you care about, please join me on the IRC channel
7395 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7396 irc.debian.org). There is a lot that could be done to improve the
7397 Debian support for LEGO designers. For example both CAD software
7398 and Mindstorm compilers are missing. :)&lt;/p&gt;
7399
7400 &lt;p&gt;Update 2012-01-03: A
7401 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7402 including links to Lego related packages is now available.&lt;/p&gt;
7403 </description>
7404 </item>
7405
7406 <item>
7407 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7408 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7410 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7411 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7412 year! I hope next year will prove to be a good year.&lt;/p&gt;
7413
7414 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7415 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7416 between each other with minimal overhead, is a very interesting
7417 experiment. And as I wrote a few days ago, the bitcoin situation in
7418 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7419 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7420 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7421 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7422 for one of the ftpmasters to approve the new bitcoin-qt package
7423 name.&lt;/p&gt;
7424
7425 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7426 team in Debian, you can easily test the package in Debian Squeeze
7427 using the following steps to get a set of working packages:&lt;/p&gt;
7428
7429 &lt;blockquote&gt;&lt;pre&gt;
7430 git clone git://git.debian.org/git/collab-maint/bitcoin
7431 cd bitcoin
7432 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7433 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7434 &lt;/pre&gt;&lt;/blockquote&gt;
7435
7436 &lt;p&gt;You might have to install some build dependencies as well. The
7437 list of commands should give you two packages, bitcoind and
7438 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7439 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7440 around 5.6 GiB of data on my machine at the moment. Make sure your
7441 ~/.bitcoin/ directory have lots of spare room if you want to download
7442 all the blocks. The client will warn if the disk is getting full, so
7443 there is not really a problem if you got too little room, but you will
7444 not be able to get all the features out of the client.&lt;/p&gt;
7445
7446 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7447 activities, please send Bitcoin donations to my address
7448 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7449 </description>
7450 </item>
7451
7452 <item>
7453 <title>A word on bitcoin support in Debian</title>
7454 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7456 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7457 <description>&lt;p&gt;It has been a while since I wrote about
7458 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7459 peer-to-peer based crypto-currency, and the reason is simply that I
7460 have been busy elsewhere. But two days ago, I started looking at the
7461 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7462 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7463 is now maintained by a
7464 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7465 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7466 owe a huge thank you to all these team members. :)
7467 But I was sad to discover that the bitcoin client is missing in
7468 Wheezy. It is only available in Sid (and an outdated client from
7469 backports). The client had several RC bugs registered in BTS blocking
7470 it from entering testing. To try to help the team and improve the
7471 situation, I spent some time providing patches and triaging the bug
7472 reports. I also had a look at the bitcoin package available from Matt
7473 Corallo in a
7474 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7475 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7476 Debian package.&lt;/p&gt;
7477
7478 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7479 IRC, I pushed several patches into the collab-maint git repository to
7480 improve the package. It now contains fixes for the RC issues (not from
7481 me, but fixed by Scott Howard), build rules for a Qt GUI client
7482 package, konqueror support for the bitcoin: URI and bash completion
7483 setup. As I work on Debian Squeeze, I also created
7484 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7485 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7486 it and try to integrate it into the git repository before uploading a
7487 new version to unstable.
7488
7489 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7490 centralized control currently exercised in the monetary system. I
7491 find it completely unacceptable that the USA government is collecting
7492 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7493 that the major credit card companies can block legal money
7494 transactions to Wikileaks. But for bitcoin to succeed, more people
7495 need to use bitcoins, and more people need to accept bitcoins when
7496 they sell products and services. Improving the bitcoin support in
7497 Debian is a small step in the right direction, but not enough.
7498 Unfortunately the user experience when browsing the web and wanting to
7499 pay with bitcoin is still not very good. The bitcoin: URI is a step
7500 in the right direction, but need to work in most or every browser in
7501 use. Also the bitcoin-qt client is too heavy to fire up to do a
7502 quick transaction. I believe there are other clients available, but
7503 have not tested them.&lt;/p&gt;
7504
7505 &lt;p&gt;My
7506 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
7507 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
7508 I received 20.15 BTC so far on the address I provided in my blog two
7509 years ago, as can be
7510 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
7511 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
7512 donation. The blockexplorer service demonstrates quite well that
7513 bitcoin is not quite anonymous and untracked. :) I wonder if the
7514 number of users have gone up since then. If you use bitcoin and want
7515 to show your support of my activity, please send Bitcoin donations to
7516 the same address as last time,
7517 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7518 </description>
7519 </item>
7520
7521 <item>
7522 <title>Git repository for song book for Computer Scientists</title>
7523 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
7524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
7525 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
7526 <description>&lt;p&gt;As I
7527 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
7528 this summer&lt;/a&gt;, I have created a Computer Science song book a few
7529 years ago, and today I finally found time to create a public
7530 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
7531 repository for the project&lt;/a&gt;.&lt;/p&gt;
7532
7533 &lt;p&gt;If you want to help out, please clone the source and submit patches
7534 to the HTML version. To generate the PDF and PostScript version,
7535 please use prince XML, or let me know about a useful free software
7536 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
7537
7538 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
7539 PostScript formats at
7540 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
7541 Science Songbook&lt;/a&gt;.&lt;/p&gt;
7542 </description>
7543 </item>
7544
7545 <item>
7546 <title>Gratulerer med 19-årsdagen, Debian!</title>
7547 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
7548 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
7549 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
7550 <description>&lt;p&gt;I dag fyller
7551 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
7552 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
7553 si gratulerer med dagen, Debian!&lt;/p&gt;
7554 </description>
7555 </item>
7556
7557 <item>
7558 <title>Song book for Computer Scientists</title>
7559 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
7560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
7561 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
7562 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
7563 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
7564 collecting computer related songs for use at parties. The original
7565 version was written in LaTeX, but a few years ago I got help from
7566 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7567 while keeping the ability to create a nice book in PDF format. I have
7568 not had time to maintain the book for a while now, and guess I should
7569 put it up on some public version control repository where others can
7570 help me extend and update the book. If anyone is volunteering to help
7571 me with this, send me an email. Also let me know if there are songs
7572 missing in my book.&lt;/p&gt;
7573
7574 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
7575 me today that I really should let all my readers share the joys of
7576 singing out load about programming, computers and computer networks.
7577 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
7578 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
7579 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
7580 Computer Science Songbook&lt;/a&gt;.
7581 </description>
7582 </item>
7583
7584 <item>
7585 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
7586 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
7587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
7588 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
7589 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
7590 around 1000 at the moment. To be able to get help from the vendors
7591 when something go wrong, we want to keep the firmware on the servers
7592 up to date. If the firmware isn&#39;t the latest and greatest, the
7593 vendors typically refuse to start debugging any problems until the
7594 firmware is upgraded. So before every reboot, we want to upgrade the
7595 firmware, and we would really like everyone handling servers at the
7596 university to do this themselves when they plan to reboot a machine.
7597 For that to happen we at the unix server admin group need to provide
7598 the tools to do so.&lt;/p&gt;
7599
7600 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
7601 fetch and install the latest firmware for the servers we got. Most of
7602 our hardware are from Dell and HP, so I have focused on these servers
7603 so far. This blog post is about the Dell part.&lt;/P&gt;
7604
7605 &lt;p&gt;On the Dell FTP site I was lucky enough to find
7606 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
7607 with firmware information for all 11th generation servers, listing
7608 which firmware should be used on a given model and where on the FTP
7609 site I can find it. Using a simple perl XML parser I can then
7610 download the shell scripts Dell provides to do firmware upgrades from
7611 within Linux and reboot when all the firmware is primed and ready to
7612 be activated on the first reboot.&lt;/p&gt;
7613
7614 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
7615 Are there anyone working on similar tools for firmware upgrading all
7616 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
7617
7618 &lt;p&gt;&lt;pre&gt;
7619 #!/usr/bin/perl
7620 use strict;
7621 use warnings;
7622 use File::Temp qw(tempdir);
7623 BEGIN {
7624 # Install needed RHEL packages if missing
7625 my %rhelmodules = (
7626 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
7627 );
7628 for my $module (keys %rhelmodules) {
7629 eval &quot;use $module;&quot;;
7630 if ($@) {
7631 my $pkg = $rhelmodules{$module};
7632 system(&quot;yum install -y $pkg&quot;);
7633 eval &quot;use $module;&quot;;
7634 }
7635 }
7636 }
7637 my $errorsto = &#39;pere@hungry.com&#39;;
7638
7639 upgrade_dell();
7640
7641 exit 0;
7642
7643 sub run_firmware_script {
7644 my ($opts, $script) = @_;
7645 unless ($script) {
7646 print STDERR &quot;fail: missing script name\n&quot;;
7647 exit 1
7648 }
7649 print STDERR &quot;Running $script\n\n&quot;;
7650
7651 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
7652 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
7653 } else {
7654 print STDERR &quot;fail: firmware script returned error\n&quot;;
7655 }
7656 }
7657
7658 sub run_firmware_scripts {
7659 my ($opts, @dirs) = @_;
7660 # Run firmware packages
7661 for my $dir (@dirs) {
7662 print STDERR &quot;info: Running scripts in $dir\n&quot;;
7663 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
7664 while (my $s = readdir $dh) {
7665 next if $s =~ m/^\.\.?/;
7666 run_firmware_script($opts, &quot;$dir/$s&quot;);
7667 }
7668 closedir $dh;
7669 }
7670 }
7671
7672 sub download {
7673 my $url = shift;
7674 print STDERR &quot;info: Downloading $url\n&quot;;
7675 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
7676 }
7677
7678 sub upgrade_dell {
7679 my @dirs;
7680 my $product = `dmidecode -s system-product-name`;
7681 chomp $product;
7682
7683 if ($product =~ m/PowerEdge/) {
7684
7685 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7686 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
7687
7688 my $tmpdir = tempdir(
7689 CLEANUP =&gt; 1
7690 );
7691 chdir($tmpdir);
7692 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
7693 system(&#39;gunzip Catalog.xml.gz&#39;);
7694 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
7695 # -q is quiet, disabling interactivity and reducing console output
7696 my $fwopts = &quot;-q&quot;;
7697 if (@paths) {
7698 for my $url (@paths) {
7699 fetch_dell_fw($url);
7700 }
7701 run_firmware_scripts($fwopts, $tmpdir);
7702 } else {
7703 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7704 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7705 }
7706 chdir(&#39;/&#39;);
7707 } else {
7708 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7709 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7710 }
7711 }
7712
7713 sub fetch_dell_fw {
7714 my $path = shift;
7715 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
7716 download($url);
7717 }
7718
7719 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7720 # firmware packages to download from Dell. Only work for Linux
7721 # machines and 11th generation Dell servers.
7722 sub fetch_dell_fw_list {
7723 my $filename = shift;
7724
7725 my $product = `dmidecode -s system-product-name`;
7726 chomp $product;
7727 my ($mybrand, $mymodel) = split(/\s+/, $product);
7728
7729 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
7730
7731 my $xml = XMLin($filename);
7732 my @paths;
7733 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
7734 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
7735 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
7736 my $oscode;
7737 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
7738 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
7739 } else {
7740 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
7741 }
7742 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
7743 {
7744 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
7745 }
7746 }
7747 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
7748 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
7749
7750 # Drop application packages, only firmware and BIOS
7751 next if &#39;APAC&#39; eq $componenttype;
7752
7753 my $cpath = $component-&gt;{path};
7754 for my $path (@paths) {
7755 if ($cpath =~ m%/$path$%) {
7756 push(@paths, $cpath);
7757 }
7758 }
7759 }
7760 return @paths;
7761 }
7762 &lt;/pre&gt;
7763
7764 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
7765 it could work on other platforms with some tweaking. Anyone know a
7766 index like Catalog.xml is available from HP for HP servers? At the
7767 moment I maintain a similar list manually and it is quickly getting
7768 outdated.&lt;/p&gt;
7769 </description>
7770 </item>
7771
7772 <item>
7773 <title>How is booting into runlevel 1 different from single user boots?</title>
7774 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
7775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
7776 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
7777 <description>&lt;p&gt;Wouter Verhelst have some
7778 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
7779 comments and opinions&lt;/a&gt; on my blog post on
7780 &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
7781 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
7782 &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
7783 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
7784 small piece of his comment now, and though it best to address the
7785 misunderstanding he bring forward:&lt;/p&gt;
7786
7787 &lt;p&gt;&lt;blockquote&gt;
7788 Currently, a system admin has four options: [...] boot to a
7789 single-user system (by adding &#39;single&#39; to the kernel command line;
7790 this runs rcS and rc1 scripts)
7791 &lt;/blockquote&gt;&lt;/p&gt;
7792
7793 &lt;p&gt;This make me believe Wouter believe booting into single user mode
7794 and booting into runlevel 1 is the same. I am not surprised he
7795 believe this, because it would make sense and is a quite sensible
7796 thing to believe. But because the boot in Debian is slightly broken,
7797 runlevel 1 do not work properly and it isn&#39;t the same as single user
7798 mode. I&#39;ll try to explain what is actually happing, but it is a bit
7799 hard to explain.&lt;/p&gt;
7800
7801 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
7802 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
7803 executed in single user mode is sulogin. Single user mode is a boot
7804 state &quot;between&quot; the runlevels, and when booting into single user mode,
7805 only the scripts in /etc/rcS.d/ are executed before the init process
7806 enters the single user state. When switching to runlevel 1, the state
7807 is in fact not ending in runlevel 1, but it passes through runlevel 1
7808 and end up in the single user mode (see /etc/rc1.d/S03single, which
7809 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
7810 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
7811 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7812 mode).&lt;/p&gt;
7813
7814 &lt;p&gt;This summary might make it clearer. When booting for the first
7815 time into single user mode, the following commands are executed:
7816 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
7817 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
7818 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
7819 trying to continue after visiting single user mode. Not all services
7820 are started again as they should, causing the machine to end up in an
7821 unpredicatble state. This is why Debian admins recommend rebooting
7822 after visiting single user mode.&lt;/p&gt;
7823
7824 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
7825 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
7826 to runlevel 1, the services started from /etc/rcS.d/ are not properly
7827 stopped when passing through the scripts in /etc/rc1.d/, and not
7828 started again when switching away from runlevel 1 to the runlevels
7829 2-5. I believe the problem is best fixed by moving all the scripts
7830 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
7831 functioning single user mode during boot.&lt;/p&gt;
7832
7833 &lt;p&gt;I have spent several years investigating the Debian boot system,
7834 and discovered this problem a few years ago. I suspect it originates
7835 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
7836 </description>
7837 </item>
7838
7839 <item>
7840 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
7841 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
7842 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
7843 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
7844 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
7845 are started from /etc/rcS.d/. In fact, there is a bite more of them
7846 than make sense, and this causes a few problems. What kind of
7847 problems, you might ask. There are at least two problems. The first
7848 is that it is not possible to recover a machine after switching to
7849 runlevel 1. One need to actually reboot to get the machine back to
7850 the expected state. The other is that single user boot will sometimes
7851 run into problems because some of the subsystems are activated before
7852 the root login is presented, causing problems when trying to recover a
7853 machine from a problem in that subsystem. A minor additional point is
7854 that moving more scripts out of rcS.d/ and into the other rc#.d/
7855 directories will increase the amount of scripts that can run in
7856 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
7857
7858 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
7859 scripts that _have_ to execute before the root login prompt is
7860 presented during a single user boot should go there. Everything else
7861 should go into the numeric runlevels. This means things like
7862 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7863 the numeric runlevels. Today in Debian, there are around 115 init.d
7864 scripts that are started from rcS.d/, and most of them should be moved
7865 out. Do your package have one of them? Please help us make single
7866 user and runlevel 1 better by moving it.&lt;/p&gt;
7867
7868 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
7869 etc. should still be started from rcS.d/, but there is for example no
7870 need to have the network enabled before the single user login prompt
7871 is presented.&lt;/p&gt;
7872
7873 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
7874 Debian systems working while scripts migrate and during upgrades, the
7875 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7876 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7877 and the next ones can only be moved when their dependencies have been
7878 moved first. This migration must be done sequentially while we ensure
7879 that the package system upgrade packages in the right order to keep
7880 the system state correct. This will require some coordination when it
7881 comes to network related packages, but most of the packages with
7882 scripts that should migrate do not have anything in rcS.d/ depending
7883 on them. Some packages have already been updated, like the sudo
7884 package, while others are still left to do. I wish I had time to work
7885 on this myself, but real live constrains make it unlikely that I will
7886 find time to push this forward.&lt;/p&gt;
7887 </description>
7888 </item>
7889
7890 <item>
7891 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
7892 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
7893 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
7894 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
7895 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
7896 mentioned the issues I believe should be improved in Debian for its
7897 desktop to be useful for more people. The use case for this is my
7898 parents, which are currently running Kubuntu which solve the
7899 issues.&lt;/p&gt;
7900
7901 &lt;p&gt;I suspect these four missing features are not very hard to
7902 implement. After all, they are present in Ubuntu, so if we wanted to
7903 do this in Debian we would have a source.&lt;/p&gt;
7904
7905 &lt;ol&gt;
7906
7907 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
7908 are new packages available for upgrades, a icon in the KDE status bar
7909 indicate this, and clicking on it will activate the simple upgrade
7910 tool to handle it. I have no problem guiding both of my parents
7911 through the process over the phone. If a kernel reboot is required,
7912 this too is indicated by the status bars and the upgrade tool. Last
7913 time I checked, nothing with the same features was working in KDE in
7914 Debian.&lt;/li&gt;
7915
7916 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
7917 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
7918 currently have a handler for, it will ask the user if the system
7919 should search for a package that would add support for this MIME type,
7920 and if the user say yes, the APT sources will be searched for packages
7921 advertising the MIME type in their control file (visible in the
7922 Packages file in the APT archive). If one or more packages are found,
7923 it is a simple click of the mouse to add support for the missing mime
7924 type. If the package require the user to accept some non-free
7925 license, this is explained to the user. The entire process make it
7926 more clear to the user why something do not work in the browser, and
7927 make the chances higher for the user to blame the web page authors and
7928 not the browser for any missing features.&lt;/li&gt;
7929
7930 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
7931 handlers.&lt;/strong&gt; When the media players encounter a format or codec
7932 it is not supporting, a dialog pop up asking the user if the system
7933 should search for a package that would add support for it. This
7934 happen with things like MP3, Windows Media or H.264. The selection
7935 and installation procedure is very similar to the Firefox browser
7936 plugin handling. This is as far as I know implemented using a
7937 gstreamer hook. The end result is that the user easily get access to
7938 the codecs that are present from the APT archives available, while
7939 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
7940
7941 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
7942 displaying a text/plain file in my Debian browser, it will propose to
7943 start emacs to show it. If I remember correctly, when doing the same
7944 in Kunbutu it show the file as a text file in the browser. At least I
7945 know Opera will show text files within the browser. I much prefer the
7946 latter behaviour.&lt;/li&gt;
7947
7948 &lt;/ol&gt;
7949
7950 &lt;p&gt;There are other nice features as well, like the simplified suite
7951 upgrader, but given that I am the one mostly doing the dist-upgrade,
7952 it do not matter much.&lt;/p&gt;
7953
7954 &lt;p&gt;I really hope we could get these features in place for the next
7955 Debian release. It would require the coordinated effort of several
7956 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
7957 </description>
7958 </item>
7959
7960 <item>
7961 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
7962 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
7963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
7964 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
7965 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
7966 site is build on Debian/Squeeze, and this platform was chosen because
7967 I am most familiar with Debian (being a Debian Developer for around 10
7968 years) because it is the latest stable Debian release which should get
7969 security support for a few years.&lt;/p&gt;
7970
7971 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
7972 that are missing in Debian at the moment. It would be great if these
7973 modules were added to the Debian archive, allowing anyone to set up
7974 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
7975 in their own country using only Debian packages. The list of modules
7976 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
7977 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
7978 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7979 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7980 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7981 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7982 easier in the future.&lt;/p&gt;
7983
7984 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
7985 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
7986 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
7987 with the responsibility of tracking security problems, which I really
7988 do not have time for.&lt;/p&gt;
7989 </description>
7990 </item>
7991
7992 <item>
7993 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
7994 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
7995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
7996 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
7997 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
7998 posts have been in Norwegian the last few weeks, so here is a short
7999 update in English.&lt;/p&gt;
8000
8001 &lt;p&gt;The kids still keep me too busy to get much free software work
8002 done, but I did manage to organise a project to get a Norwegian port
8003 of the British service
8004 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8005 and it has been running for a month now. The entire project has been
8006 organised by me and two others. Around Christmas we gathered sponsors
8007 to fund the development work. In January I drafted a contract with
8008 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8009 and in February the development took place. Most of it involved
8010 converting the source to use GPS coordinates instead of British
8011 easting/northing, and the resulting code should be a lot easier to get
8012 running in any country by now. The Norwegian
8013 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8014 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8015 source and the source for administrative borders in Norway, and
8016 support for this had to be added/fixed.&lt;/p&gt;
8017
8018 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8019 polishing the system before we announced it March 7th. The system is
8020 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8021 problem reports in a few weeks. Soon we hope to announce the Android
8022 and iPhone versions making it even easier to report problems with the
8023 public infrastructure.&lt;/p&gt;
8024
8025 &lt;p&gt;Perhaps something to consider for those of you in countries without
8026 such service?&lt;/p&gt;
8027 </description>
8028 </item>
8029
8030 <item>
8031 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8032 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8034 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8035 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8036 issues here at my work with the University of Oslo. My idea is that
8037 it should be possible to use the information about security issues
8038 available on the Internet, and check our locally
8039 maintained/distributed software against this information. It should
8040 allow us to verify that no known security issues are forgotten. The
8041 CVE database listing vulnerabilities seem like a great central point,
8042 and by using the package lists from Debian mapped to CVEs provided by
8043 the testing security team, I believed it should be possible to figure
8044 out which security holes were present in our free software
8045 collection.&lt;/p&gt;
8046
8047 &lt;p&gt;After reading up on the topic, it became obvious that the first
8048 building block is to be able to name software packages in a unique and
8049 consistent way across data sources. I considered several ways to do
8050 this, for example coming up with my own naming scheme like using URLs
8051 to project home pages or URLs to the Freshmeat entries, or using some
8052 existing naming scheme. And it seem like I am not the first one to
8053 come across this problem, as MITRE already proposed and implemented a
8054 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8055 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8056 software, hardware and other platform components. The CPE ids are
8057 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8058 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8059 issues for any CPE name. With this in place, all I need to do is to
8060 locate the CPE id for the software packages we use at the university.
8061 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8062 NVD entry if a CVE for the package exist).&lt;/p&gt;
8063
8064 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8065 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8066 check out, one could look up
8067 &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
8068 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8069 The most recent one is
8070 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8071 and at the bottom of the NVD page for this vulnerability the complete
8072 list of affected versions is provided.&lt;/p&gt;
8073
8074 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8075 for offline processing of issues. Using this dump, I&#39;ve written a
8076 small script taking a list of CPEs as input and list all CVEs
8077 affecting the packages represented by these CPEs. One give it CPEs
8078 with version numbers as specified above and get a list of open
8079 security issues out.&lt;/p&gt;
8080
8081 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8082 information need to be high. For that to happen, I believe as many as
8083 possible need to use and contribute to the NVD database. I notice
8084 RHEL is providing
8085 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8086 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8087 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8088
8089 &lt;p&gt;To get an idea about the quality for free software, I spent some
8090 time making it possible to compare the CVE database from Debian with
8091 the CVE database in NVD. The result look fairly good, but there are
8092 some inconsistencies in NVD (same software package having several
8093 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8094 Debian believe are affected by a CVE). Hope to find time to improve
8095 the quality of NVD, but that require being able to get in touch with
8096 someone maintaining it. So far my three emails with questions and
8097 corrections have not seen any reply, but I hope contact can be
8098 established soon.&lt;/p&gt;
8099
8100 &lt;p&gt;An interesting application for CPEs is cross platform package
8101 mapping. It would be useful to know which packages in for example
8102 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8103 this would be trivial if all linux distributions provided CPE entries
8104 for their packages.&lt;/p&gt;
8105 </description>
8106 </item>
8107
8108 <item>
8109 <title>Which module is loaded for a given PCI and USB device?</title>
8110 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8112 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8113 <description>&lt;p&gt;In the
8114 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8115 package in Debian, there is a script to report useful information
8116 about the running hardware for use when people report missing
8117 information. One part of this script that I find very useful when
8118 debugging hardware problems, is the part mapping loaded kernel module
8119 to the PCI device it claims. It allow me to quickly see if the kernel
8120 module I expect is driving the hardware I am struggling with. To see
8121 the output, make sure discover-data is installed and run
8122 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8123 one of my machines like this:&lt;/p&gt;
8124
8125 &lt;pre&gt;
8126 loaded modules:
8127 10de:03eb i2c_nforce2
8128 10de:03f1 ohci_hcd
8129 10de:03f2 ehci_hcd
8130 10de:03f0 snd_hda_intel
8131 10de:03ec pata_amd
8132 10de:03f6 sata_nv
8133 1022:1103 k8temp
8134 109e:036e bttv
8135 109e:0878 snd_bt87x
8136 11ab:4364 sky2
8137 &lt;/pre&gt;
8138
8139 &lt;p&gt;The code in question look like this, slightly modified for
8140 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8141
8142 &lt;pre&gt;
8143 if [ -d /sys/bus/pci/devices/ ] ; then
8144 echo loaded pci modules:
8145 (
8146 cd /sys/bus/pci/devices/
8147 for address in * ; do
8148 if [ -d &quot;$address/driver/module&quot; ] ; then
8149 module=`cd $address/driver/module ; pwd -P | xargs basename`
8150 if grep -q &quot;^$module &quot; /proc/modules ; then
8151 address=$(echo $address |sed s/0000://)
8152 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8153 echo &quot;$id $module&quot;
8154 fi
8155 fi
8156 done
8157 )
8158 echo
8159 fi
8160 &lt;/pre&gt;
8161
8162 &lt;p&gt;Similar code could be used to extract USB device module
8163 mappings:&lt;/p&gt;
8164
8165 &lt;pre&gt;
8166 if [ -d /sys/bus/usb/devices/ ] ; then
8167 echo loaded usb modules:
8168 (
8169 cd /sys/bus/usb/devices/
8170 for address in * ; do
8171 if [ -d &quot;$address/driver/module&quot; ] ; then
8172 module=`cd $address/driver/module ; pwd -P | xargs basename`
8173 if grep -q &quot;^$module &quot; /proc/modules ; then
8174 address=$(echo $address |sed s/0000://)
8175 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8176 if [ &quot;$id&quot; ] ; then
8177 echo &quot;$id $module&quot;
8178 fi
8179 fi
8180 fi
8181 done
8182 )
8183 echo
8184 fi
8185 &lt;/pre&gt;
8186
8187 &lt;p&gt;This might perhaps be something to include in other tools as
8188 well.&lt;/p&gt;
8189 </description>
8190 </item>
8191
8192 <item>
8193 <title>How to test if a laptop is working with Linux</title>
8194 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8195 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8196 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8197 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8198 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8199 batch of computers will work with Linux. Every year for the last few
8200 years the university have organised shared bid of a few thousand
8201 computers, and this year HP won the bid. Two different desktops and
8202 five different laptops are on the list this year. We in the UNIX
8203 group want to know which one of these computers work well with RHEL
8204 and Ubuntu, the two Linux distributions we currently handle at the
8205 university.&lt;/p&gt;
8206
8207 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8208 perhaps inspire others to test hardware as well. To test, I PXE
8209 install the OS version of choice, and log in as my normal user and run
8210 a few applications and plug in selected pieces of hardware. When
8211 something fail, I make a note about this in the test matrix and move
8212 on. If I have some spare time I try to report the bug to the OS
8213 vendor, but as I only have the machines for a short time, I rarely
8214 have the time to do this for all the problems I find.&lt;/p&gt;
8215
8216 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8217 I perform on a new model.&lt;/p&gt;
8218
8219 &lt;ul&gt;
8220
8221 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8222 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8223 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8224
8225 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8226 installation, X.org is working.&lt;/li&gt;
8227
8228 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8229 package mesa-utils on Ubuntu) and writing down the frames per second
8230 reported by the program.&lt;/li&gt;
8231
8232 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8233 logging in, and if I can hear this the test is successful. If there
8234 are several audio exits on the machine, I try them all and check if
8235 the Gnome/KDE audio mixer can control where to send the sound. I
8236 normally test this by playing
8237 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8238 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8239
8240 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8241 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8242
8243 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8244 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8245
8246 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8247 picture from the v4l device show up.&lt;/li&gt;
8248
8249 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8250 any bluetooth devices are discovered. In my office, I normally see a
8251 few.&lt;/li&gt;
8252
8253 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8254 memory modules lying around, and stick them in and see if Gnome/KDE
8255 notice this.&lt;/li&gt;
8256
8257 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8258 special button work, and if the laptop continue to work after
8259 resume.&lt;/li&gt;
8260
8261 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8262 adjusting background light, switching on/off external video output,
8263 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8264 laptop to laptop, so I just write down which are working and which are
8265 not.&lt;/li&gt;
8266
8267 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8268 acceleration sensors etc. I rarely test these, as I do not know how
8269 to quickly test if they are working or not, so I only document their
8270 existence.&lt;/li&gt;
8271
8272 &lt;/ul&gt;
8273
8274 &lt;p&gt;By now I suspect you are really curious what the test results are
8275 for the HP machines I am testing. I&#39;m not done yet, so I will report
8276 the test results later. For now I can report that HP 8100 Elite work
8277 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8278 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8279 can see, I have most machines left to test. One interesting
8280 observation is that Ubuntu Lucid has almost twice the frame rate than
8281 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8282 </description>
8283 </item>
8284
8285 <item>
8286 <title>Some thoughts on BitCoins</title>
8287 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8289 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8290 <description>&lt;p&gt;As I continue to explore
8291 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8292 what properties the system have, and how it will be affected by laws
8293 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8294
8295 &lt;p&gt;One interesting thing to note is that since the transactions are
8296 verified using a peer to peer network, all details about a transaction
8297 is known to everyone. This means that if a BitCoin address has been
8298 published like I did with mine in my initial post about BitCoin, it is
8299 possible for everyone to see how many BitCoins have been transfered to
8300 that address. There is even a web service to look at the details for
8301 all transactions. There I can see that my address
8302 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8303 have received 16.06 Bitcoin, the
8304 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8305 address of Simon Phipps have received 181.97 BitCoin and the address
8306 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8307 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8308 every one of you that donated bitcoins to support my activity. The
8309 fact that anyone can see how much money was transfered to a given
8310 address make it more obvious why the BitCoin community recommend to
8311 generate and hand out a new address for each transaction. I&#39;m told
8312 there is no way to track which addresses belong to a given person or
8313 organisation without the person or organisation revealing it
8314 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8315
8316 &lt;p&gt;In Norway, and in most other countries, there are laws and
8317 regulations limiting how much money one can transfer across the border
8318 without declaring it. There are money laundering, tax and accounting
8319 laws and regulations I would expect to apply to the use of BitCoin.
8320 If the Skolelinux foundation
8321 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8322 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8323 normal bank transfers like EFF is doing, how should this be accounted?
8324 Given that it is impossible to know if money can cross the border or
8325 not, should everything or nothing be declared? What exchange rate
8326 should be used when calculating taxes? Would receivers have to pay
8327 income tax if the foundation were to pay Skolelinux contributors in
8328 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8329
8330 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8331 accepted by a lot of users. It must be possible to get easy access to
8332 the currency (as a wage or using currency exchanges), and it must be
8333 easy to spend it. At the moment BitCoin seem fairly easy to get
8334 access to, but there are very few places to spend it. I am not really
8335 a regular user of any of the vendor types currently accepting BitCoin,
8336 so I wonder when my kind of shop would start accepting BitCoins. I
8337 would like to buy electronics, travels and subway tickets, not herbs
8338 and books. :) The currency is young, and this will improve over time
8339 if it become popular, but I suspect regular banks will start to lobby
8340 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8341 will claim it is helping fund terrorism and money laundering (which
8342 probably would be true, as is any currency in existence), but I
8343 believe the problems should be solved elsewhere and not by blaming
8344 currencies.&lt;/p&gt;
8345
8346 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8347 CPU intensive process that depend on a bit of luck as well (as one is
8348 competing against all the other miners currently spending CPU cycles
8349 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8350 BitCoin when this happen. Yesterday I came across the obvious way to
8351 join forces to increase ones changes of getting at least some coins,
8352 by coordinating the work on mining BitCoins across several machines
8353 and people, and sharing the result if one is lucky and get the 50
8354 BitCoins. Check out
8355 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8356 if this sounds interesting. I have not had time to try to set up a
8357 machine to participate there yet, but have seen that running on ones
8358 own for a few days have not yield any BitCoins througth mining
8359 yet.&lt;/p&gt;
8360
8361 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8362 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8363 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8364 it was interesting to read. The arguments presented seem to be
8365 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8366 </description>
8367 </item>
8368
8369 <item>
8370 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8371 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8373 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8374 <description>&lt;p&gt;With this weeks lawless
8375 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8376 attacks&lt;/a&gt; on Wikileak and
8377 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8378 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8379 not be trusted to handle money transactions.
8380 A blog post from
8381 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8382 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8383 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8384 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8385 some help from my friend to get it all running, and he even handed me
8386 some bitcoins to get started. I even donated a few bitcoins to Simon
8387 for helping me remember BitCoin.&lt;/p&gt;
8388
8389 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8390 crypto-currency, decentralised and handled using peer-to-peer
8391 networks. It allows anonymous transactions and prohibits central
8392 control over the transactions, making it impossible for governments
8393 and companies alike to block donations and other transactions. The
8394 source is free software, and while the key dependency wxWidgets 2.9
8395 for the graphical user interface is missing in Debian, the command
8396 line client builds just fine. Hopefully Jonas
8397 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8398 Debian&lt;/a&gt; soon.&lt;/p&gt;
8399
8400 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8401 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8402 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8403 currency &quot;stock&quot; markets where the exchange rate is decided. There
8404 are not many users so far, but the concept seems promising. If you
8405 want to get started and lack a friend with any bitcoins to spare,
8406 you can even get
8407 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8408 bitcoin at the time of writing). Use
8409 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8410 on the current exchange rates.&lt;/p&gt;
8411
8412 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8413 machines. If you want to support my activity, please send Bitcoin
8414 donations to the address
8415 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8416 </description>
8417 </item>
8418
8419 <item>
8420 <title>Why isn&#39;t Debian Edu using VLC?</title>
8421 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8423 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8424 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8425 presented, and the winner among the multimedia player were VLC.
8426 Personally, I like VLC, and it is my player of choice when I first try
8427 to play a video file or stream. Only if VLC fail will I drag out
8428 gmplayer to see if it can do better. The reason is mostly the failure
8429 model and trust. When VLC fail, it normally pop up a error message
8430 reporting the problem. When mplayer fail, it normally segfault or
8431 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8432
8433 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8434 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8435 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8436 plugin to play web videos seamlessly, and the VLC browser plugin is
8437 not very good. For example, it lack in-line control buttons, so there
8438 is no way for the user to pause the video. Also, when I
8439 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8440 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8441 failed on several video pages where mplayer based plugins worked. If
8442 the browser plugin for VLC was as good as the gecko-mediaplayer
8443 package (which uses mplayer), we would switch.&lt;/P&gt;
8444
8445 &lt;p&gt;While VLC is a good player, its user interface is slightly
8446 annoying. The most annoying feature is its inconsistent use of
8447 keyboard shortcuts. When the player is in full screen mode, its
8448 shortcuts are different from when it is playing the video in a window.
8449 For example, space only work as pause when in full screen mode. I
8450 wish it had consisten shortcuts and that space also would work when in
8451 window mode. Another nice shortcut in gmplayer is [enter] to restart
8452 the current video. It is very nice when playing short videos from the
8453 web and want to restart it when new people arrive to have a look at
8454 what is going on.&lt;/p&gt;
8455 </description>
8456 </item>
8457
8458 <item>
8459 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8460 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8461 <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>
8462 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8463 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8464 upgrade testing of the
8465 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8466 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8467 This seem like a very good idea, so I adjusted by test scripts and
8468 can now present the updated result from today:&lt;/p&gt;
8469
8470 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8471
8472 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8473
8474 &lt;blockquote&gt;&lt;p&gt;
8475 apache2.2-bin
8476 aptdaemon
8477 baobab
8478 binfmt-support
8479 browser-plugin-gnash
8480 cheese-common
8481 cli-common
8482 cups-pk-helper
8483 dmz-cursor-theme
8484 empathy
8485 empathy-common
8486 freedesktop-sound-theme
8487 freeglut3
8488 gconf-defaults-service
8489 gdm-themes
8490 gedit-plugins
8491 geoclue
8492 geoclue-hostip
8493 geoclue-localnet
8494 geoclue-manual
8495 geoclue-yahoo
8496 gnash
8497 gnash-common
8498 gnome
8499 gnome-backgrounds
8500 gnome-cards-data
8501 gnome-codec-install
8502 gnome-core
8503 gnome-desktop-environment
8504 gnome-disk-utility
8505 gnome-screenshot
8506 gnome-search-tool
8507 gnome-session-canberra
8508 gnome-system-log
8509 gnome-themes-extras
8510 gnome-themes-more
8511 gnome-user-share
8512 gstreamer0.10-fluendo-mp3
8513 gstreamer0.10-tools
8514 gtk2-engines
8515 gtk2-engines-pixbuf
8516 gtk2-engines-smooth
8517 hamster-applet
8518 libapache2-mod-dnssd
8519 libapr1
8520 libaprutil1
8521 libaprutil1-dbd-sqlite3
8522 libaprutil1-ldap
8523 libart2.0-cil
8524 libboost-date-time1.42.0
8525 libboost-python1.42.0
8526 libboost-thread1.42.0
8527 libchamplain-0.4-0
8528 libchamplain-gtk-0.4-0
8529 libcheese-gtk18
8530 libclutter-gtk-0.10-0
8531 libcryptui0
8532 libdiscid0
8533 libelf1
8534 libepc-1.0-2
8535 libepc-common
8536 libepc-ui-1.0-2
8537 libfreerdp-plugins-standard
8538 libfreerdp0
8539 libgconf2.0-cil
8540 libgdata-common
8541 libgdata7
8542 libgdu-gtk0
8543 libgee2
8544 libgeoclue0
8545 libgexiv2-0
8546 libgif4
8547 libglade2.0-cil
8548 libglib2.0-cil
8549 libgmime2.4-cil
8550 libgnome-vfs2.0-cil
8551 libgnome2.24-cil
8552 libgnomepanel2.24-cil
8553 libgpod-common
8554 libgpod4
8555 libgtk2.0-cil
8556 libgtkglext1
8557 libgtksourceview2.0-common
8558 libmono-addins-gui0.2-cil
8559 libmono-addins0.2-cil
8560 libmono-cairo2.0-cil
8561 libmono-corlib2.0-cil
8562 libmono-i18n-west2.0-cil
8563 libmono-posix2.0-cil
8564 libmono-security2.0-cil
8565 libmono-sharpzip2.84-cil
8566 libmono-system2.0-cil
8567 libmtp8
8568 libmusicbrainz3-6
8569 libndesk-dbus-glib1.0-cil
8570 libndesk-dbus1.0-cil
8571 libopal3.6.8
8572 libpolkit-gtk-1-0
8573 libpt2.6.7
8574 libpython2.6
8575 librpm1
8576 librpmio1
8577 libsdl1.2debian
8578 libsrtp0
8579 libssh-4
8580 libtelepathy-farsight0
8581 libtelepathy-glib0
8582 libtidy-0.99-0
8583 media-player-info
8584 mesa-utils
8585 mono-2.0-gac
8586 mono-gac
8587 mono-runtime
8588 nautilus-sendto
8589 nautilus-sendto-empathy
8590 p7zip-full
8591 pkg-config
8592 python-aptdaemon
8593 python-aptdaemon-gtk
8594 python-axiom
8595 python-beautifulsoup
8596 python-bugbuddy
8597 python-clientform
8598 python-coherence
8599 python-configobj
8600 python-crypto
8601 python-cupshelpers
8602 python-elementtree
8603 python-epsilon
8604 python-evolution
8605 python-feedparser
8606 python-gdata
8607 python-gdbm
8608 python-gst0.10
8609 python-gtkglext1
8610 python-gtksourceview2
8611 python-httplib2
8612 python-louie
8613 python-mako
8614 python-markupsafe
8615 python-mechanize
8616 python-nevow
8617 python-notify
8618 python-opengl
8619 python-openssl
8620 python-pam
8621 python-pkg-resources
8622 python-pyasn1
8623 python-pysqlite2
8624 python-rdflib
8625 python-serial
8626 python-tagpy
8627 python-twisted-bin
8628 python-twisted-conch
8629 python-twisted-core
8630 python-twisted-web
8631 python-utidylib
8632 python-webkit
8633 python-xdg
8634 python-zope.interface
8635 remmina
8636 remmina-plugin-data
8637 remmina-plugin-rdp
8638 remmina-plugin-vnc
8639 rhythmbox-plugin-cdrecorder
8640 rhythmbox-plugins
8641 rpm-common
8642 rpm2cpio
8643 seahorse-plugins
8644 shotwell
8645 software-center
8646 system-config-printer-udev
8647 telepathy-gabble
8648 telepathy-mission-control-5
8649 telepathy-salut
8650 tomboy
8651 totem
8652 totem-coherence
8653 totem-mozilla
8654 totem-plugins
8655 transmission-common
8656 xdg-user-dirs
8657 xdg-user-dirs-gtk
8658 xserver-xephyr
8659 &lt;/p&gt;&lt;/blockquote&gt;
8660
8661 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8662
8663 &lt;blockquote&gt;&lt;p&gt;
8664 cheese
8665 ekiga
8666 eog
8667 epiphany-extensions
8668 evolution-exchange
8669 fast-user-switch-applet
8670 file-roller
8671 gcalctool
8672 gconf-editor
8673 gdm
8674 gedit
8675 gedit-common
8676 gnome-games
8677 gnome-games-data
8678 gnome-nettool
8679 gnome-system-tools
8680 gnome-themes
8681 gnuchess
8682 gucharmap
8683 guile-1.8-libs
8684 libavahi-ui0
8685 libdmx1
8686 libgalago3
8687 libgtk-vnc-1.0-0
8688 libgtksourceview2.0-0
8689 liblircclient0
8690 libsdl1.2debian-alsa
8691 libspeexdsp1
8692 libsvga1
8693 rhythmbox
8694 seahorse
8695 sound-juicer
8696 system-config-printer
8697 totem-common
8698 transmission-gtk
8699 vinagre
8700 vino
8701 &lt;/p&gt;&lt;/blockquote&gt;
8702
8703 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8704
8705 &lt;blockquote&gt;&lt;p&gt;
8706 gstreamer0.10-gnomevfs
8707 &lt;/p&gt;&lt;/blockquote&gt;
8708
8709 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8710
8711 &lt;blockquote&gt;&lt;p&gt;
8712 [nothing]
8713 &lt;/p&gt;&lt;/blockquote&gt;
8714
8715 &lt;p&gt;This is for KDE:&lt;/p&gt;
8716
8717 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8718
8719 &lt;blockquote&gt;&lt;p&gt;
8720 ksmserver
8721 &lt;/p&gt;&lt;/blockquote&gt;
8722
8723 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8724
8725 &lt;blockquote&gt;&lt;p&gt;
8726 kwin
8727 network-manager-kde
8728 &lt;/p&gt;&lt;/blockquote&gt;
8729
8730 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8731
8732 &lt;blockquote&gt;&lt;p&gt;
8733 arts
8734 dolphin
8735 freespacenotifier
8736 google-gadgets-gst
8737 google-gadgets-xul
8738 kappfinder
8739 kcalc
8740 kcharselect
8741 kde-core
8742 kde-plasma-desktop
8743 kde-standard
8744 kde-window-manager
8745 kdeartwork
8746 kdeartwork-emoticons
8747 kdeartwork-style
8748 kdeartwork-theme-icon
8749 kdebase
8750 kdebase-apps
8751 kdebase-workspace
8752 kdebase-workspace-bin
8753 kdebase-workspace-data
8754 kdeeject
8755 kdelibs
8756 kdeplasma-addons
8757 kdeutils
8758 kdewallpapers
8759 kdf
8760 kfloppy
8761 kgpg
8762 khelpcenter4
8763 kinfocenter
8764 konq-plugins-l10n
8765 konqueror-nsplugins
8766 kscreensaver
8767 kscreensaver-xsavers
8768 ktimer
8769 kwrite
8770 libgle3
8771 libkde4-ruby1.8
8772 libkonq5
8773 libkonq5-templates
8774 libnetpbm10
8775 libplasma-ruby
8776 libplasma-ruby1.8
8777 libqt4-ruby1.8
8778 marble-data
8779 marble-plugins
8780 netpbm
8781 nuvola-icon-theme
8782 plasma-dataengines-workspace
8783 plasma-desktop
8784 plasma-desktopthemes-artwork
8785 plasma-runners-addons
8786 plasma-scriptengine-googlegadgets
8787 plasma-scriptengine-python
8788 plasma-scriptengine-qedje
8789 plasma-scriptengine-ruby
8790 plasma-scriptengine-webkit
8791 plasma-scriptengines
8792 plasma-wallpapers-addons
8793 plasma-widget-folderview
8794 plasma-widget-networkmanagement
8795 ruby
8796 sweeper
8797 update-notifier-kde
8798 xscreensaver-data-extra
8799 xscreensaver-gl
8800 xscreensaver-gl-extra
8801 xscreensaver-screensaver-bsod
8802 &lt;/p&gt;&lt;/blockquote&gt;
8803
8804 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8805
8806 &lt;blockquote&gt;&lt;p&gt;
8807 ark
8808 google-gadgets-common
8809 google-gadgets-qt
8810 htdig
8811 kate
8812 kdebase-bin
8813 kdebase-data
8814 kdepasswd
8815 kfind
8816 klipper
8817 konq-plugins
8818 konqueror
8819 ksysguard
8820 ksysguardd
8821 libarchive1
8822 libcln6
8823 libeet1
8824 libeina-svn-06
8825 libggadget-1.0-0b
8826 libggadget-qt-1.0-0b
8827 libgps19
8828 libkdecorations4
8829 libkephal4
8830 libkonq4
8831 libkonqsidebarplugin4a
8832 libkscreensaver5
8833 libksgrd4
8834 libksignalplotter4
8835 libkunitconversion4
8836 libkwineffects1a
8837 libmarblewidget4
8838 libntrack-qt4-1
8839 libntrack0
8840 libplasma-geolocation-interface4
8841 libplasmaclock4a
8842 libplasmagenericshell4
8843 libprocesscore4a
8844 libprocessui4a
8845 libqalculate5
8846 libqedje0a
8847 libqtruby4shared2
8848 libqzion0a
8849 libruby1.8
8850 libscim8c2a
8851 libsmokekdecore4-3
8852 libsmokekdeui4-3
8853 libsmokekfile3
8854 libsmokekhtml3
8855 libsmokekio3
8856 libsmokeknewstuff2-3
8857 libsmokeknewstuff3-3
8858 libsmokekparts3
8859 libsmokektexteditor3
8860 libsmokekutils3
8861 libsmokenepomuk3
8862 libsmokephonon3
8863 libsmokeplasma3
8864 libsmokeqtcore4-3
8865 libsmokeqtdbus4-3
8866 libsmokeqtgui4-3
8867 libsmokeqtnetwork4-3
8868 libsmokeqtopengl4-3
8869 libsmokeqtscript4-3
8870 libsmokeqtsql4-3
8871 libsmokeqtsvg4-3
8872 libsmokeqttest4-3
8873 libsmokeqtuitools4-3
8874 libsmokeqtwebkit4-3
8875 libsmokeqtxml4-3
8876 libsmokesolid3
8877 libsmokesoprano3
8878 libtaskmanager4a
8879 libtidy-0.99-0
8880 libweather-ion4a
8881 libxklavier16
8882 libxxf86misc1
8883 okteta
8884 oxygencursors
8885 plasma-dataengines-addons
8886 plasma-scriptengine-superkaramba
8887 plasma-widget-lancelot
8888 plasma-widgets-addons
8889 plasma-widgets-workspace
8890 polkit-kde-1
8891 ruby1.8
8892 systemsettings
8893 update-notifier-common
8894 &lt;/p&gt;&lt;/blockquote&gt;
8895
8896 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
8897 aptitude a bit more similar, but there are still quite a lott of
8898 differences. I have no idea what packages should be installed after
8899 the upgrade, but hope those that do can have a look.&lt;/p&gt;
8900 </description>
8901 </item>
8902
8903 <item>
8904 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
8905 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
8906 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
8907 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
8908 <description>&lt;p&gt;Most of the computers in use by the
8909 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
8910 are virtual machines. And they have been Xen machines running on a
8911 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
8912 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
8913 bit harder that it could have been, because we set up the Xen virtual
8914 machines to get the virtual partitions from LVM, which as far as I
8915 know is not supported by KVM. So to migrate, we had to convert
8916 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
8917
8918 &lt;p&gt;I found
8919 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
8920 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
8921 migration. It uses qemu-img from the qemu package to make the disk
8922 image, parted to partition it, losetup and kpartx to present the disk
8923 image partions as devices, and dd to copy the data. I NFS mounted the
8924 new servers storage area on the old server to do the migration.&lt;/p&gt;
8925
8926 &lt;pre&gt;
8927 #!/bin/sh
8928
8929 # Based on
8930 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8931
8932 set -e
8933 set -x
8934
8935 if [ -z &quot;$1&quot; ] ; then
8936 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
8937 exit 1
8938 else
8939 host=&quot;$1&quot;
8940 fi
8941
8942 if [ ! -e /dev/vg_data/$host-disk ] ; then
8943 echo &quot;error: unable to find LVM volume for $host&quot;
8944 exit 1
8945 fi
8946
8947 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8948 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8949 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8950 totalsize=$(( ( $disksize + $swapsize ) ))
8951
8952 img=$host.img
8953 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
8954 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8955
8956 parted $img mklabel msdos
8957 parted $img mkpart primary linux-swap 0 $disksize
8958 parted $img mkpart primary ext2 $disksize $totalsize
8959 parted $img set 1 boot on
8960
8961 modprobe dm-mod
8962 losetup /dev/loop0 $img
8963 kpartx -a /dev/loop0
8964
8965 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
8966 fsck.ext3 -f /dev/mapper/loop0p1 || true
8967 mkswap /dev/mapper/loop0p2
8968
8969 kpartx -d /dev/loop0
8970 losetup -d /dev/loop0
8971 &lt;/pre&gt;
8972
8973 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
8974 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
8975
8976 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
8977 the new disk image attached, installed grub-pc and linux-image-686 and
8978 set up grub to boot from the disk image. After this, the KVM machines
8979 seem to work just fine.&lt;/p&gt;
8980 </description>
8981 </item>
8982
8983 <item>
8984 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
8985 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
8986 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
8987 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
8988 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
8989 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8990 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
8991 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
8992
8993 &lt;p&gt;I still do not know what a correct migration should look like, so I
8994 report any differences between apt and aptitude and hope someone else
8995 can see if anything should be changed.&lt;/p&gt;
8996
8997 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8998
8999 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9000
9001 &lt;blockquote&gt;&lt;p&gt;
9002 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9003 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9004 dmz-cursor-theme empathy empathy-common finger
9005 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9006 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9007 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9008 gnome-cards-data gnome-codec-install gnome-core
9009 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9010 gnome-search-tool gnome-session-canberra gnome-spell
9011 gnome-system-log gnome-themes-extras gnome-themes-more
9012 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9013 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9014 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9015 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9016 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9017 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9018 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9019 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9020 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9021 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9022 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9023 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9024 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9025 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9026 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9027 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9028 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9029 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9030 libmono-security2.0-cil libmono-sharpzip2.84-cil
9031 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9032 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9033 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9034 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9035 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9036 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9037 libxalan2-java libxerces2-java media-player-info mesa-utils
9038 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9039 nautilus-sendto-empathy openoffice.org-writer2latex
9040 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9041 python-aptdaemon python-aptdaemon-gtk python-axiom
9042 python-beautifulsoup python-bugbuddy python-clientform
9043 python-coherence python-configobj python-crypto python-cupshelpers
9044 python-cupsutils python-eggtrayicon python-elementtree
9045 python-epsilon python-evolution python-feedparser python-gdata
9046 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9047 python-gtksourceview2 python-httplib2 python-louie python-mako
9048 python-markupsafe python-mechanize python-nevow python-notify
9049 python-opengl python-openssl python-pam python-pkg-resources
9050 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9051 python-tagpy python-twisted-bin python-twisted-conch
9052 python-twisted-core python-twisted-web python-utidylib python-webkit
9053 python-xdg python-zope.interface remmina remmina-plugin-data
9054 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9055 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9056 software-center svgalibg1 system-config-printer-udev
9057 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9058 totem totem-coherence totem-mozilla totem-plugins
9059 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9060 zip
9061 &lt;/p&gt;&lt;/blockquote&gt;
9062
9063 Installed using apt-get, removed with aptitude
9064
9065 &lt;blockquote&gt;&lt;p&gt;
9066 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9067 epiphany-extensions epiphany-gecko evolution-exchange
9068 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9069 gedit-common gnome-app-install gnome-games gnome-games-data
9070 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9071 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9072 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9073 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9074 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9075 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9076 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9077 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9078 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9079 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9080 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9081 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9082 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9083 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9084 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9085 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9086 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9087 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9088 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9089 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9090 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9091 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9092 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9093 sound-juicer swfdec-gnome system-config-printer totem-common
9094 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9095 &lt;/p&gt;&lt;/blockquote&gt;
9096
9097 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9098
9099 &lt;blockquote&gt;&lt;p&gt;
9100 gstreamer0.10-gnomevfs
9101 &lt;/p&gt;&lt;/blockquote&gt;
9102
9103 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9104
9105 &lt;blockquote&gt;&lt;p&gt;
9106 [nothing]
9107 &lt;/p&gt;&lt;/blockquote&gt;
9108
9109 &lt;p&gt;This is for KDE:&lt;/p&gt;
9110
9111 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9112
9113 &lt;blockquote&gt;&lt;p&gt;
9114 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9115 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9116 ghostscript-x git gnome-audio gnugo granatier gs-common
9117 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9118 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9119 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9120 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9121 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9122 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9123 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9124 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9125 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9126 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9127 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9128 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9129 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9130 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9131 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9132 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9133 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9134 libkrossui4 libmailtools-perl libmime-tools-perl
9135 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9136 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9137 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9138 lirc luatex marble networkstatus noatun-plugins
9139 openoffice.org-writer2latex palapeli palapeli-data parley
9140 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9141 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9142 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9143 ttf-sazanami-gothic
9144 &lt;/p&gt;&lt;/blockquote&gt;
9145
9146 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9147
9148 &lt;blockquote&gt;&lt;p&gt;
9149 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9150 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9151 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9152 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9153 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9154 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9155 kitchensync kiten kjumpingcube klatin klettres klickety klines
9156 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9157 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9158 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9159 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9160 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9161 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9162 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9163 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9164 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9165 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9166 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9167 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9168 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9169 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9170 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9171 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9172 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9173 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9174 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9175 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9176 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9177 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9178 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9179 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9180 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9181 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9182 &lt;/p&gt;&lt;/blockquote&gt;
9183
9184 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9185
9186 &lt;blockquote&gt;&lt;p&gt;
9187 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9188 kdeartwork kdebase kdebase-apps kdebase-workspace
9189 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9190 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9191 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9192 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9193 xscreensaver-screensaver-bsod
9194 &lt;/p&gt;&lt;/blockquote&gt;
9195
9196 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9197
9198 &lt;blockquote&gt;&lt;p&gt;
9199 kdebase-bin konq-plugins konqueror
9200 &lt;/p&gt;&lt;/blockquote&gt;
9201 </description>
9202 </item>
9203
9204 <item>
9205 <title>Gnash buildbot slave and Debian kfreebsd</title>
9206 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9208 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9209 <description>&lt;p&gt;Answering
9210 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9211 call from the Gnash project&lt;/a&gt; for
9212 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9213 current source, I have set up a virtual KVM machine on the Debian
9214 Edu/Skolelinux virtualization host to test the git source on
9215 Debian/Squeeze. I hope this can help the developers in getting new
9216 releases out more often.&lt;/p&gt;
9217
9218 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9219 I have considered setting up a &lt;a
9220 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9221 machine as well. I have also considered using the kfreebsd
9222 architecture in Debian as a file server in NUUG to get access to the 5
9223 TB zfs volume we currently use to store DV video. Because of this, I
9224 finally got around to do a test installation of Debian/Squeeze with
9225 kfreebsd. Installation went fairly smooth, thought I noticed some
9226 visual glitches in the cdebconf dialogs (black cursor left on the
9227 screen at random locations). Have not gotten very far with the
9228 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9229 fatal problem. Have to spend some more time on it to see if it is
9230 useful as a file server for NUUG. Will try to find time to set up a
9231 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9232 </description>
9233 </item>
9234
9235 <item>
9236 <title>Debian in 3D</title>
9237 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9238 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9239 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9240 <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;
9241
9242 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9243 3D linked in from
9244 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9245 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9246 </description>
9247 </item>
9248
9249 <item>
9250 <title>Software updates 2010-10-24</title>
9251 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9252 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9253 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9254 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9255
9256 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9257 raise money for the project is going well. The lower limit of 10
9258 signers was reached in 24 hours, and so far 13 people have signed it.
9259 More signers and more funding is most welcome, and I am really curious
9260 how far we can get before the time limit of December 24 is reached.
9261 :)&lt;/p&gt;
9262
9263 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9264 about what appear to be a great code coverage tool capable of
9265 generating code coverage stats without any changes to the source code.
9266 It is called
9267 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9268 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9269 It is missing in Debian, but the git source built just fine in Squeeze
9270 after I installed libelf-dev, libdwarf-dev, pkg-config and
9271 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9272 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9273
9274 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9275 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9276 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9277 alpha test release of the Squeeze based Debian Edu /
9278 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9279 release. Give it a try if you need a complete linux solution for your
9280 school, including central infrastructure server, workstations, thin
9281 client servers and diskless workstations. A nice touch added
9282 yesterday is RDP support on the thin client servers, for windows
9283 clients to get a Linux desktop on request.&lt;/p&gt;
9284 </description>
9285 </item>
9286
9287 <item>
9288 <title>Some notes on Flash in Debian and Debian Edu</title>
9289 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9291 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9292 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9293 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9294 second most popular used package that is missing in Debian. The sixth
9295 most popular is flashplayer-mozilla. This is a clear indication that
9296 working flash is important for Debian users. Around 10 percent of the
9297 users submitting data to popcon.debian.org have this package
9298 installed.&lt;/p&gt;
9299
9300 &lt;p&gt;In the report written by Lars Risan in August 2008
9301&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
9302 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9303 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9304 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9305 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9306 web sites require Flash to work, and lacking working Flash support in
9307 the web browser and the problems with installing it was perceived as a
9308 good reason to stay with Windows.&lt;/p&gt;
9309
9310 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9311 said to be the retarded cousin that did not really understand
9312 everything you told him but could work fairly well. This was a
9313 comment regarding the problems Linux have with proprietary formats and
9314 non-standard web pages, and is sad because it exposes a fairly common
9315 understanding of whose fault it is if web pages that only work in for
9316 example Internet Explorer 6 fail to work on Firefox, and funny because
9317 it explain very well how annoying it is for users when Linux
9318 distributions do not work with the documents they receive or the web
9319 pages they want to visit.&lt;/p&gt;
9320
9321 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9322 and Debian Edu to have a well working Flash implementation in the
9323 distribution, to get at least popular sites as Youtube and Google
9324 Video to working out of the box. For Squeeze, Debian have the chance
9325 to include the latest version of Gnash that will make this happen, as
9326 the new release 0.8.8 was published a few weeks ago and is resting in
9327 unstable. The new version work with more sites that version 0.8.7.
9328 The Gnash maintainers have asked for a freeze exception, but the
9329 release team have not had time to reply to it yet. I hope they agree
9330 with me that Flash is important for the Debian desktop users, and thus
9331 accept the new package into Squeeze.&lt;/p&gt;
9332 </description>
9333 </item>
9334
9335 <item>
9336 <title>Circular package dependencies harms apt recovery</title>
9337 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9339 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9340 <description>&lt;p&gt;I discovered this while doing
9341 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9342 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9343 in Debian still got circular dependencies, and it is often claimed
9344 that apt and aptitude should be able to handle this just fine, but
9345 some times these dependency loops causes apt to fail.&lt;/p&gt;
9346
9347 &lt;p&gt;An example is from todays
9348 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9349 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9350 causes perl-modules to fail to upgrade. The cause is simple. If a
9351 package fail to unpack, then only part of packages with the circular
9352 dependency might end up being unpacked when unpacking aborts, and the
9353 ones already unpacked will fail to configure in the recovery phase
9354 because its dependencies are unavailable.&lt;/p&gt;
9355
9356 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9357
9358 &lt;blockquote&gt;&lt;pre&gt;
9359 dpkg: dependency problems prevent configuration of perl-modules:
9360 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9361 Version of perl on system is 5.10.0-19lenny2.
9362 dpkg: error processing perl-modules (--configure):
9363 dependency problems - leaving unconfigured
9364 &lt;/pre&gt;&lt;/blockquote&gt;
9365
9366 &lt;p&gt;The perl/perl-modules circular dependency is already
9367 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9368 hopefully be solved as soon as possible, but it is not the only one,
9369 and each one of these loops in the dependency tree can cause similar
9370 failures. Of course, they only occur when there are bugs in other
9371 packages causing the unpacking to fail, but it is rather nasty when
9372 the failure of one package causes the problem to become worse because
9373 of dependency loops.&lt;/p&gt;
9374
9375 &lt;p&gt;Thanks to
9376 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9377 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9378 dependencies
9379 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9380 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9381
9382 &lt;p&gt;Todays testing also exposed a bug in
9383 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9384 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9385 apt-get and aptitude, the latter possibly caused by some circular
9386 dependency. Reported both to BTS to try to get someone to look at
9387 it.&lt;/p&gt;
9388 </description>
9389 </item>
9390
9391 <item>
9392 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9393 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9395 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9396 <description>&lt;p&gt;This is a
9397 &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;
9398 on my
9399 &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
9400 work&lt;/a&gt; on
9401 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9402 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9403
9404 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9405 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9406 and dhcp3-server-ldap in Debian use the LDAP server. The two
9407 implementations are quite different in how they use LDAP.&lt;/p&gt;
9408
9409 To get this information, I started slapd with debugging enabled and
9410 dumped the debug output to a file to get the LDAP searches performed
9411 on a Debian Edu main-server. Here is a summary.
9412
9413 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9414
9415 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9416 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9417 the web.
9418
9419 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9420 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9421 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9422 reverse entries are in two different subtrees in LDAP with a structure
9423 based on the DNS names, as in tjener.intern and
9424 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9425
9426 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9427 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9428 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9429 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9430 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9431 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9432 forward entries, it is looking for attributes named dnsttl, arecord,
9433 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9434 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9435 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9436 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9437 spfrecord and modifytimestamp. For reverse entries it is looking for
9438 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9439 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9440 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9441 ldapsearch commands could look like this:&lt;/p&gt;
9442
9443 &lt;blockquote&gt;&lt;pre&gt;
9444 ldapsearch -h ldap \
9445 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9446 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9447 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9448 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9449 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9450 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9451
9452 ldapsearch -h ldap \
9453 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9454 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9455 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9456 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9457 srvrecord naptrrecord modifytimestamp
9458 &lt;/pre&gt;&lt;/blockquote&gt;
9459
9460 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9461 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9462 example LDAP objects used there. In addition to these objects, the
9463 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9464 also exist.&lt;/p&gt;
9465
9466 &lt;blockquote&gt;&lt;pre&gt;
9467 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9468 objectclass: top
9469 objectclass: dnsdomain
9470 objectclass: domainrelatedobject
9471 dc: tjener
9472 arecord: 10.0.2.2
9473 associateddomain: tjener.intern
9474
9475 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9476 objectclass: top
9477 objectclass: dnsdomain2
9478 objectclass: domainrelatedobject
9479 dc: 2
9480 ptrrecord: tjener.intern
9481 associateddomain: 2.2.0.10.in-addr.arpa
9482 &lt;/pre&gt;&lt;/blockquote&gt;
9483
9484 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9485 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9486 same base as in the tree mode for a object with filter
9487 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9488 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9489 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9490 naptrrecord and modifytimestamp. For reverse entires it also do a
9491 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9492 and the requested attributes are associateddomain, dnsttl and
9493 modifytimestamp. In short, in strict mode the objects with ptrrecord
9494 go away, and the arecord attribute in the forward object is used
9495 instead.&lt;/p&gt;
9496
9497 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
9498 like this:&lt;/p&gt;
9499
9500 &lt;blockquote&gt;&lt;pre&gt;
9501 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9502 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9503 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9504 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9505 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9506 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9507
9508 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9509 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
9510 &lt;/pre&gt;&lt;/blockquote&gt;
9511
9512 &lt;p&gt;In addition to the forward and reverse searches , there is also a
9513 search for SOA records, which behave similar to the forward and
9514 reverse lookups.&lt;/p&gt;
9515
9516 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
9517 specify any objectclass names, and instead look for the attributes it
9518 need to generate a DNS reply. This make it able to work with any
9519 objectclass that provide the needed attributes.&lt;/p&gt;
9520
9521 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
9522 dnsdomain2 schemas. The latter is used for reverse entries like
9523 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
9524
9525 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
9526 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9527 attributes) and domainrelatedobject (for associatedDomain). The use
9528 of structural object classes make it impossible to combine these
9529 classes with the object classes used by DHCP.&lt;/p&gt;
9530
9531 &lt;p&gt;There are other schemas that could be used too, for example the
9532 dnszone structural object class used by Gosa and bind-sdb for the DNS
9533 attributes combined with the domainrelatedobject object class, but in
9534 this case some unused attributes would have to be included as well
9535 (zonename and relativedomainname).&lt;/p&gt;
9536
9537 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
9538 mode and not use any of the existing objectclasses (dnsdomain,
9539 dnsdomain2 and dnszone) when one want to combine the DNS information
9540 with DHCP information, and instead create a auxiliary object class
9541 defined something like this (using the attributes defined for
9542 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
9543
9544 &lt;blockquote&gt;&lt;pre&gt;
9545 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
9546 SUP top
9547 AUXILIARY
9548 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9549 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9550 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9551 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9552 A6Record $ DNAMERecord
9553 ))
9554 &lt;/pre&gt;&lt;/blockquote&gt;
9555
9556 &lt;p&gt;This will allow any object to become a DNS entry when combined with
9557 the domainrelatedobject object class, and allow any entity to include
9558 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
9559 developers asking for their view on this schema and if they are
9560 interested in providing such schema with PowerDNS, and I hope my
9561 message will be accepted into their mailing list soon.&lt;/p&gt;
9562
9563 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
9564
9565 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
9566 the object attributes, and then uses the attributes it want. This
9567 make it harder to figure out exactly what attributes are used, but
9568 thanks to the working example in Debian Edu I can at least get an idea
9569 what is needed without having to read the source code.&lt;/p&gt;
9570
9571 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
9572 search filter to use to locate the correct dhcpServer entity is
9573 stored. These are the relevant entries from
9574 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
9575
9576 &lt;blockquote&gt;&lt;pre&gt;
9577 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
9578 ldap-dhcp-server-cn &quot;dhcp&quot;;
9579 &lt;/pre&gt;&lt;/blockquote&gt;
9580
9581 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
9582 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
9583 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
9584 search result is this entry:&lt;/p&gt;
9585
9586 &lt;blockquote&gt;&lt;pre&gt;
9587 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9588 cn: dhcp
9589 objectClass: top
9590 objectClass: dhcpServer
9591 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9592 &lt;/pre&gt;&lt;/blockquote&gt;
9593
9594 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
9595 subtree with DHCP configuration. The DHCP configuration subtree base
9596 is located using a base scope search with base &quot;cn=DHCP
9597 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
9598 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
9599 The search result is this entry:&lt;/p&gt;
9600
9601 &lt;blockquote&gt;&lt;pre&gt;
9602 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9603 cn: DHCP Config
9604 objectClass: top
9605 objectClass: dhcpService
9606 objectClass: dhcpOptions
9607 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9608 dhcpStatements: ddns-update-style none
9609 dhcpStatements: authoritative
9610 dhcpOption: smtp-server code 69 = array of ip-address
9611 dhcpOption: www-server code 72 = array of ip-address
9612 dhcpOption: wpad-url code 252 = text
9613 &lt;/pre&gt;&lt;/blockquote&gt;
9614
9615 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
9616 all the DHCP configuration is loaded, it is ready to receive requests.
9617 The subtree in Debian Edu contain objects with object classes
9618 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9619 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9620 and information about netmasks, dynamic range etc. Leaving out the
9621 details here because it is not relevant for the focus of my
9622 investigation, which is to see if it is possible to merge dns and dhcp
9623 related computer objects.&lt;/p&gt;
9624
9625 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
9626 of the client (00:00:00:00:00:00 in this example), using a subtree
9627 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
9628 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9629 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
9630 like:&lt;/p&gt;
9631
9632 &lt;blockquote&gt;&lt;pre&gt;
9633 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9634 cn: hostname
9635 objectClass: top
9636 objectClass: dhcpHost
9637 dhcpHWAddress: ethernet 00:00:00:00:00:00
9638 dhcpStatements: fixed-address hostname
9639 &lt;/pre&gt;&lt;/blockquote&gt;
9640
9641 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
9642 The object classes need to have fixed names, and the configuration
9643 need to be stored in a fairly specific LDAP structure. On the
9644 positive side, the invidiual dhcpHost entires can be anywhere without
9645 the DN pointed to by the dhcpServer entries. The latter should make
9646 it possible to group all host entries in a subtree next to the
9647 configuration entries, and this subtree can also be shared with the
9648 DNS server if the schema proposed above is combined with the dhcpHost
9649 structural object class.
9650
9651 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
9652
9653 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
9654 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
9655 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
9656 allowing DNS objects to be stored anywhere under the base cn specified
9657 in the configuration.&lt;/p&gt;
9658
9659 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
9660 regarding which LDAP schemas to use and which LDAP structure to use.
9661 I guess one could implement ones own schema, as long as the
9662 objectclasses and attributes have the names used, but this do not
9663 really help when the DHCP subtree need to have a fairly fixed
9664 structure.&lt;/p&gt;
9665
9666 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
9667 this might work for Debian Edu:&lt;/p&gt;
9668
9669 &lt;blockquote&gt;&lt;pre&gt;
9670 ou=services
9671 cn=machine-info (dhcpService) - dhcpServiceDN points here
9672 cn=dhcp (dhcpServer)
9673 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9674 cn=10.0.2.0 (dhcpSubnet)
9675 cn=group1 (dhcpGroup/dhcpOptions)
9676 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9677 cn=192.168.0.0 (dhcpSubnet)
9678 cn=group1 (dhcpGroup/dhcpOptions)
9679 ou=machines - PowerDNS base points here
9680 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9681 &lt;/pre&gt;&lt;/blockquote&gt;
9682
9683 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
9684 entries to be in the dhcpGroup subtrees, the entries can be stored
9685 there instead of a common machines subtree, and the PowerDNS base
9686 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
9687
9688 &lt;p&gt;The combined object under the machines subtree would look something
9689 like this:&lt;/p&gt;
9690
9691 &lt;blockquote&gt;&lt;pre&gt;
9692 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9693 dc: hostname
9694 objectClass: top
9695 objectClass: dhcpHost
9696 objectclass: domainrelatedobject
9697 objectclass: dnsDomainAux
9698 associateddomain: hostname.intern
9699 arecord: 10.11.12.13
9700 dhcpHWAddress: ethernet 00:00:00:00:00:00
9701 dhcpStatements: fixed-address hostname.intern
9702 &lt;/pre&gt;&lt;/blockquote&gt;
9703
9704 &lt;/p&gt;One could even add the LTSP configuration associated with a given
9705 machine, as long as the required attributes are available in a
9706 auxiliary object class.&lt;/p&gt;
9707 </description>
9708 </item>
9709
9710 <item>
9711 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
9712 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
9713 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
9714 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
9715 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
9716 DHCP services in Debian Edu to use the same LDAP objects for a given
9717 computer, to avoid the possibility of having a inconsistent state for
9718 a computer in LDAP (as in DHCP but no DNS entry or the other way
9719 around) and make it easier to add computers to LDAP.&lt;/p&gt;
9720
9721 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
9722 information finally found a solution that seem to work.&lt;/p&gt;
9723
9724 &lt;p&gt;The old setup required three LDAP objects for a given computer.
9725 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9726 we switch powerdns to use its strict LDAP method (ldap-method=strict
9727 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9728 merged into one while making it impossible to transfer the reverse map
9729 to a slave DNS server.&lt;/p&gt;
9730
9731 &lt;p&gt;If we also replace the object class used to get the DNS related
9732 attributes to one allowing these attributes to be combined with the
9733 dhcphost object class, we can merge the DNS and DHCP entries into one.
9734 I&#39;ve written such object class in the dnsdomainaux.schema file (need
9735 proper OIDs, but that is a minor issue), and tested the setup. It
9736 seem to work.&lt;/p&gt;
9737
9738 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
9739 for both DNS and DHCP, and even the LTSP configuration I suggested in
9740 an earlier email. The combined LDAP object will look something like
9741 this:&lt;/p&gt;
9742
9743 &lt;blockquote&gt;&lt;pre&gt;
9744 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9745 cn: hostname
9746 objectClass: dhcphost
9747 objectclass: domainrelatedobject
9748 objectclass: dnsdomainaux
9749 associateddomain: hostname.intern
9750 arecord: 10.11.12.13
9751 dhcphwaddress: ethernet 00:00:00:00:00:00
9752 dhcpstatements: fixed-address hostname
9753 ldapconfigsound: Y
9754 &lt;/pre&gt;&lt;/blockquote&gt;
9755
9756 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
9757 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9758 before asking DNS to resolve the fixed-adddress. LTSP will use
9759 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
9760
9761 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
9762 dhcphost in a different location, to allow us to put the objects
9763 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
9764 that. If I can&#39;t figure out a way to do that, we can still get rid of
9765 the hosts subtree and move all its content into the DHCP Config tree
9766 (which probably should be renamed to be more related to the new
9767 content. I suspect cn=dnsdhcp,ou=services or something like that
9768 might be a good place to put it.&lt;/p&gt;
9769
9770 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9771 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9772 </description>
9773 </item>
9774
9775 <item>
9776 <title>Idea for storing LTSP configuration in LDAP</title>
9777 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
9778 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
9779 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
9780 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
9781 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9782 clients, and that this can be used to fetch configuration from LDAP if
9783 Debian Edu choose to store configuration there.&lt;/p&gt;
9784
9785 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
9786 to get configuration from LDAP. The idea is to look up the MAC
9787 address of the client in LDAP, and look for attributes on the form
9788 ltspconfigsetting=value, and use this to export SETTING=value to the
9789 LTSP clients.&lt;/p&gt;
9790
9791 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
9792 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
9793 allowing us to store all information about a computer in one place.&lt;/p&gt;
9794
9795 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
9796 this approach. A real LDAP schema for the ltspClientAux objectclass
9797 need to be written. Comments, suggestions, etc?&lt;/p&gt;
9798
9799 &lt;blockquote&gt;&lt;pre&gt;
9800 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9801 #
9802 # Fetch LTSP client settings from LDAP based on MAC address
9803 #
9804 # Uses ethernet address as stored in the dhcpHost objectclass using
9805 # the dhcpHWAddress attribute or ethernet address stored in the
9806 # ieee802Device objectclass with the macAddress attribute.
9807 #
9808 # This module is written to be schema agnostic, and only depend on the
9809 # existence of attribute names.
9810 #
9811 # The LTSP configuration variables are saved directly using a
9812 # ltspConfig prefix and uppercasing the rest of the attribute name.
9813 # To set the SERVER variable, set the ltspConfigServer attribute.
9814 #
9815 # Some LDAP schema should be created with all the relevant
9816 # configuration settings. Something like this should work:
9817 #
9818 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
9819 # SUP top
9820 # AUXILIARY
9821 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9822
9823 LDAPSERVER=$(debian-edu-ldapserver)
9824 if [ &quot;$LDAPSERVER&quot; ] ; then
9825 LDAPBASE=$(debian-edu-ldapserver -b)
9826 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
9827 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
9828 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
9829 grep &#39;^ltspConfig&#39; | while read attr value ; do
9830 # Remove prefix and convert to upper case
9831 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
9832 # bass value on to clients
9833 eval &quot;$attr=$value; export $attr&quot;
9834 done
9835 done
9836 fi
9837 &lt;/pre&gt;&lt;/blockquote&gt;
9838
9839 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
9840 the while block might end up in a subshell causing the variables set
9841 there to not show up in ltsp-config, but if that is the case I am sure
9842 the code can be restructured to make sure the variables are passed on.
9843 I expect that can be solved with some testing. :)&lt;/p&gt;
9844
9845 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9846 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9847
9848 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
9849 configuration in LDAP that was created around year 2000 by
9850 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
9851 Xperience, Inc., 2000&lt;/a&gt;. I found its
9852 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
9853 personal home page over at redhat.com.&lt;/p&gt;
9854 </description>
9855 </item>
9856
9857 <item>
9858 <title>jXplorer, a very nice LDAP GUI</title>
9859 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
9860 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
9861 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
9862 <description>&lt;p&gt;Since
9863 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
9864 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
9865 LDAP GUI that is even better than luma. The java application
9866 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
9867 moving LDAP objects and subtrees using drag-and-drop, and can
9868 authenticate using Kerberos. I have only tested the Kerberos
9869 authentication, but do not have a LDAP setup allowing me to rewrite
9870 LDAP with my test user yet. It is
9871 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
9872 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
9873 have with it is how it handle errors. If something go wrong, its
9874 non-intuitive behaviour require me to go through some query work list
9875 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
9876 </description>
9877 </item>
9878
9879 <item>
9880 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
9881 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
9882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
9883 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
9884 <description>&lt;p&gt;Here is a short update on my &lt;a
9885 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
9886 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
9887 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
9888 not reporting the status for KDE, because the upgrade crashes when
9889 aptitude try because of missing conflicts
9890 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
9891 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
9892
9893 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
9894 complete list of the installed packages. Based on this I see these
9895 differences when I did a test run today. As usual, I do not really
9896 know what the correct set of packages would be, but thought it best to
9897 publish the difference.&lt;/p&gt;
9898
9899 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9900
9901 &lt;blockquote&gt;&lt;p&gt;
9902 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
9903 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
9904 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9905 libgtksourceview-common libpt-1.10.10-plugins-alsa
9906 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9907 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9908 python-4suite-xml python-eggtrayicon python-gtkhtml2
9909 python-gtkmozembed svgalibg1 xserver-xephyr zip
9910 &lt;/p&gt;&lt;/blockquote&gt;
9911
9912 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9913
9914 &lt;blockquote&gt;&lt;p&gt;
9915 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9916 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9917 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
9918 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
9919 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
9920 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
9921 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9922 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9923 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9924 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
9925 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
9926 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
9927 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9928 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
9929 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9930 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
9931 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
9932 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9933 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9934 mysql-common swfdec-gnome totem-gstreamer wodim
9935 &lt;/p&gt;&lt;/blockquote&gt;
9936
9937 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9938
9939 &lt;blockquote&gt;&lt;p&gt;
9940 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9941 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9942 xserver-xorg-input-all xserver-xorg-input-evdev
9943 xserver-xorg-input-kbd xserver-xorg-input-mouse
9944 xserver-xorg-input-synaptics xserver-xorg-video-all
9945 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9946 xserver-xorg-video-chips xserver-xorg-video-cirrus
9947 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9948 xserver-xorg-video-glint xserver-xorg-video-i128
9949 xserver-xorg-video-i740 xserver-xorg-video-mach64
9950 xserver-xorg-video-mga xserver-xorg-video-neomagic
9951 xserver-xorg-video-nouveau xserver-xorg-video-nv
9952 xserver-xorg-video-r128 xserver-xorg-video-radeon
9953 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9954 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9955 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9956 xserver-xorg-video-sis xserver-xorg-video-sisusb
9957 xserver-xorg-video-tdfx xserver-xorg-video-tga
9958 xserver-xorg-video-trident xserver-xorg-video-tseng
9959 xserver-xorg-video-vesa xserver-xorg-video-vmware
9960 xserver-xorg-video-voodoo
9961 &lt;/p&gt;&lt;/blockquote&gt;
9962
9963 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9964
9965 &lt;blockquote&gt;&lt;p&gt;
9966 deskbar-applet xserver-xorg xserver-xorg-core
9967 xserver-xorg-input-wacom xserver-xorg-video-intel
9968 xserver-xorg-video-openchrome
9969 &lt;/p&gt;&lt;/blockquote&gt;
9970
9971 &lt;p&gt;I was told on IRC that the xorg-xserver package was
9972 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
9973 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
9974 No idea when it hits Squeeze, but when it does I hope it will reduce
9975 the difference somewhat.
9976 </description>
9977 </item>
9978
9979 <item>
9980 <title>LUMA, a very nice LDAP GUI</title>
9981 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
9982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
9983 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
9984 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
9985 directory in Debian Edu, and in the process I started to miss a GUI
9986 tool to browse the LDAP tree. The only one I was able to find in
9987 Debian/Squeeze and Lenny is
9988 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
9989 be a great tool to get a overview of the current LDAP directory
9990 populated by default in Skolelinux. Thanks to it, I have been able to
9991 find empty and obsolete subtrees, misplaced objects and duplicate
9992 objects. It will be installed by default in Debian/Squeeze. If you
9993 are working with LDAP, give it a go. :)&lt;/p&gt;
9994
9995 &lt;p&gt;I did notice one problem with it I have not had time to report to
9996 the BTS yet. There is no .desktop file in the package, so the tool do
9997 not show up in the Gnome and KDE menus, but only deep down in in the
9998 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9999 released.&lt;/p&gt;
10000
10001 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10002 like to move objects and remove subtrees directly in the GUI, but have
10003 not found a way to do that with LUMA yet. So in the mean time, I use
10004 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10005
10006 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10007 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10008
10009 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10010 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10011 useful GUI alternative. It seem like a good tool, but is unmaintained
10012 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10013 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10014 </description>
10015 </item>
10016
10017 <item>
10018 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10019 <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>
10020 <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>
10021 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10022 <description>&lt;p&gt;A while back, I
10023 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10024 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10025 for storing DNS and DHCP information in LDAP to combine the two sets
10026 of information into one LDAP object representing a computer.&lt;/p&gt;
10027
10028 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10029 the dhcpHost object class auxiliary, to allow it to be combined with
10030 the dNSDomain object class, and thus forming one object for one
10031 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10032
10033 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10034 without also changing the assigned number for the object class, and I
10035 do not know enough about LDAP schema design to do that properly for
10036 Debian Edu.&lt;/p&gt;
10037
10038 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10039 the
10040 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10041 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10042 available today from IETF.&lt;/p&gt;
10043
10044 &lt;pre&gt;
10045 --- dhcp.schema (revision 65192)
10046 +++ dhcp.schema (working copy)
10047 @@ -376,7 +376,7 @@
10048 objectclass ( 2.16.840.1.113719.1.203.6.6
10049 NAME &#39;dhcpHost&#39;
10050 DESC &#39;This represents information about a particular client&#39;
10051 - SUP top
10052 + SUP top AUXILIARY
10053 MUST cn
10054 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10055 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10056 &lt;/pre&gt;
10057
10058 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10059 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10060 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10061
10062 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10063 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10064 </description>
10065 </item>
10066
10067 <item>
10068 <title>Calling tasksel like the installer, while still getting useful output</title>
10069 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10071 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10072 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10073 installs packages during the normal debian-installer run. Until now,
10074 I have ended up letting tasksel do the work, with the annoying problem
10075 of not getting any feedback at all when something fails (like a
10076 conffile question from dpkg or a download that fails), using code like
10077 this:
10078
10079 &lt;blockquote&gt;&lt;pre&gt;
10080 export DEBIAN_FRONTEND=noninteractive
10081 tasksel --new-install
10082 &lt;/pre&gt;&lt;/blockquote&gt;
10083
10084 This would invoke tasksel, let its automatic task selection pick the
10085 tasks to install, and continue to install the requested tasks without
10086 any output what so ever.
10087
10088 Recently I revisited this problem while working on the automatic
10089 package upgrade testing, because tasksel would some times hang without
10090 any useful feedback, and I want to see what is going on when it
10091 happen. Then it occured to me, I can parse the output from tasksel
10092 when asked to run in test mode, and use that aptitude command line
10093 printed by tasksel then to simulate the tasksel run. I ended up using
10094 code like this:
10095
10096 &lt;blockquote&gt;&lt;pre&gt;
10097 export DEBIAN_FRONTEND=noninteractive
10098 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10099 $cmd
10100 &lt;/pre&gt;&lt;/blockquote&gt;
10101
10102 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10103 --without-recommends -o APT::Install-Recommends=no -y install
10104 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10105 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10106 laptop task and all packages with priority standard , required and
10107 important, just like tasksel would have done it during
10108 installation.&lt;/p&gt;
10109
10110 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10111 install packages without using debconf-apt-progress, for use cases
10112 like this.&lt;/p&gt;
10113 </description>
10114 </item>
10115
10116 <item>
10117 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10118 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10120 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10121 <description>&lt;p&gt;My
10122 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10123 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10124 finally made the upgrade logs available from
10125 &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;.
10126 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10127 apt and aptitude, and found their differences interesting. This time
10128 I will only focus on their removal plans.&lt;/p&gt;
10129
10130 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10131 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10132 surprising part is that it want to remove xorg and all
10133 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10134 sure why. When asking aptitude to do the same, it want to remove 129
10135 packages, but most of them are library packages I suspect are no
10136 longer needed. Both of them want to remove bluetooth packages, which
10137 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10138
10139 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10140 which seem like a bad idea and xorg the same way as with Gnome. Asking
10141 aptitude for the same, it wants to remove 192 packages, none which are
10142 too surprising.&lt;/p&gt;
10143
10144 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10145 and avoided, and perhaps others as well. Here are the complete list
10146 of planned removals. The complete logs is available from the URL
10147 above. Note if you want to repeat these tests, that the upgrade test
10148 for kde+apt-get hung in the tasksel setup because of dpkg asking
10149 conffile questions. No idea why. I worked around it by using
10150 &#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
10151 continue.&lt;/p&gt;
10152
10153 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10154 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10155 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10156 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10157 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10158 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10159 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10160 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10161 xserver-xorg-input-kbd xserver-xorg-input-mouse
10162 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10163 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10164 xserver-xorg-video-ati xserver-xorg-video-chips
10165 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10166 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10167 xserver-xorg-video-glint xserver-xorg-video-i128
10168 xserver-xorg-video-i740 xserver-xorg-video-imstt
10169 xserver-xorg-video-intel xserver-xorg-video-mach64
10170 xserver-xorg-video-mga xserver-xorg-video-neomagic
10171 xserver-xorg-video-nsc xserver-xorg-video-nv
10172 xserver-xorg-video-openchrome xserver-xorg-video-r128
10173 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10174 xserver-xorg-video-rendition xserver-xorg-video-s3
10175 xserver-xorg-video-s3virge xserver-xorg-video-savage
10176 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10177 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10178 xserver-xorg-video-tga xserver-xorg-video-trident
10179 xserver-xorg-video-tseng xserver-xorg-video-v4l
10180 xserver-xorg-video-vesa xserver-xorg-video-vga
10181 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10182 xulrunner-1.9-gnome-support&lt;/p&gt;
10183
10184 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10185
10186 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10187 djvulibre-desktop finger gnome-app-install gnome-mount
10188 gnome-network-admin gnome-spell gnome-vfs-obexftp
10189 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10190 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10191 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10192 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10193 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10194 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10195 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10196 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10197 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10198 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10199 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10200 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10201 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10202 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10203 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10204 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10205 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10206 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10207 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10208 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10209 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10210 openoffice.org-writer2latex openssl-blacklist p7zip
10211 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10212 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10213 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10214 swfdec-mozilla totem-gstreamer update-manager wodim
10215 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10216 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10217 zip&lt;/p&gt;
10218
10219 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10220
10221 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10222 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10223 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10224 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10225 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10226 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10227 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10228 xserver-xorg-input-kbd xserver-xorg-input-mouse
10229 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10230 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10231 xserver-xorg-video-ati xserver-xorg-video-chips
10232 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10233 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10234 xserver-xorg-video-glint xserver-xorg-video-i128
10235 xserver-xorg-video-i740 xserver-xorg-video-imstt
10236 xserver-xorg-video-intel xserver-xorg-video-mach64
10237 xserver-xorg-video-mga xserver-xorg-video-neomagic
10238 xserver-xorg-video-nsc xserver-xorg-video-nv
10239 xserver-xorg-video-openchrome xserver-xorg-video-r128
10240 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10241 xserver-xorg-video-rendition xserver-xorg-video-s3
10242 xserver-xorg-video-s3virge xserver-xorg-video-savage
10243 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10244 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10245 xserver-xorg-video-tga xserver-xorg-video-trident
10246 xserver-xorg-video-tseng xserver-xorg-video-v4l
10247 xserver-xorg-video-vesa xserver-xorg-video-vga
10248 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10249
10250 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10251 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10252 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10253 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10254 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10255 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10256 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10257 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10258 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10259 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10260 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10261 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10262 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10263 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10264 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10265 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10266 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10267 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10268 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10269 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10270 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10271 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10272 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10273 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10274 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10275 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10276 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10277 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10278 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10279 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10280 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10281 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10282 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10283 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10284 texlive-common texlive-doc-base texlive-fonts-recommended
10285 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10286 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10287 xulrunner-1.9&lt;/p&gt;
10288
10289 </description>
10290 </item>
10291
10292 <item>
10293 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10294 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10295 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10296 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10297 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10298 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10299 have been discovered and reported in the process
10300 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10301 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10302 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10303 kdebase-workspace-data), and to get a more regular testing going on, I
10304 am working on a script to automate the test.&lt;/p&gt;
10305
10306 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10307 Gnome or KDE desktop installation inside the chroot before upgrading
10308 it. To ensure no services are started in the chroot, a policy-rc.d
10309 script is inserted. To make sure tasksel believe it is to install a
10310 desktop on a laptop, the tasksel tests are replaced in the chroot
10311 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10312
10313 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10314 currently always fail because udev refuses to upgrade with the kernel
10315 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10316 is created. The bug report
10317 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10318 this problem do not trigger in a chroot, but I touch the file anyway
10319 to make sure the upgrade go well. Testing on virtual and real
10320 hardware have failed me because of udev so far, and creating this file
10321 do the trick in such settings anyway. This is a
10322 &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
10323 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10324 maintainer because he lack the resources to rewrite udev to keep
10325 working with old kernels or something like that. I really wish the
10326 udev upstream would keep udev backwards compatible, to avoid such
10327 upgrade problem, but given that they fail to do so, I guess
10328 documenting the way out of this mess is the best option we got for
10329 Debian Squeeze.&lt;/p&gt;
10330
10331 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10332 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10333 trick:&lt;/p&gt;
10334
10335 &lt;blockquote&gt;&lt;pre&gt;
10336 #!/bin/sh
10337 set -ex
10338
10339 if [ &quot;$1&quot; ] ; then
10340 desktop=$1
10341 else
10342 desktop=gnome
10343 fi
10344
10345 from=lenny
10346 to=squeeze
10347
10348 exec &amp;lt; /dev/null
10349 unset LANG
10350 mirror=http://ftp.skolelinux.org/debian
10351 tmpdir=chroot-$from-upgrade-$to-$desktop
10352 fuser -mv .
10353 debootstrap $from $tmpdir $mirror
10354 chroot $tmpdir aptitude update
10355 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10356 #!/bin/sh
10357 exit 101
10358 EOF
10359 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10360 exit_cleanup() {
10361 umount $tmpdir/proc
10362 }
10363 mount -t proc proc $tmpdir/proc
10364 # Make sure proc is unmounted also on failure
10365 trap exit_cleanup EXIT INT
10366
10367 chroot $tmpdir aptitude -y install debconf-utils
10368
10369 # Make sure tasksel autoselection trigger. It need the test scripts
10370 # to return the correct answers.
10371 echo tasksel tasksel/desktop multiselect $desktop | \
10372 chroot $tmpdir debconf-set-selections
10373
10374 # Include the desktop and laptop task
10375 for test in desktop laptop ; do
10376 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10377 #!/bin/sh
10378 exit 2
10379 EOF
10380 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10381 done
10382
10383 DEBIAN_FRONTEND=noninteractive
10384 DEBIAN_PRIORITY=critical
10385 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10386 chroot $tmpdir tasksel --new-install
10387
10388 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10389 chroot $tmpdir aptitude update
10390 touch $tmpdir/etc/udev/kernel-upgrade
10391 chroot $tmpdir aptitude -y dist-upgrade
10392 fuser -mv
10393 &lt;/pre&gt;&lt;/blockquote&gt;
10394
10395 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10396 with aptitude, but I have not had time to look at how they behave
10397 differently so far. I hope to get a cron job running to do the test
10398 regularly and post the result on the web. The Gnome upgrade currently
10399 work, while the KDE upgrade fail because of the bug in
10400 kdebase-workspace-data&lt;/p&gt;
10401
10402 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10403 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10404 post, so I will refrain from trying. I can report that for Gnome,
10405 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10406 remove and 1 not upgraded and 1024MB need to be downloaded while for
10407 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10408 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10409
10410 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10411 is able to migrate to dependency based boot sequencing and parallel
10412 booting without a hitch. Was unsure if there were still bugs with
10413 packages failing to clean up their obsolete init.d script during
10414 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10415 packages.&lt;/p&gt;
10416 </description>
10417 </item>
10418
10419 <item>
10420 <title>Upstart or sysvinit - as init.d scripts see it</title>
10421 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10423 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10424 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10425 scripts to migrate (some of) their operations to upstart job while
10426 keeping the init.d for hurd and kfreebsd. The packages with such
10427 needs will need a way to get their init.d scripts to behave
10428 differently when used with sysvinit and with upstart. Because of
10429 this, I had a look at the environment variables set when a init.d
10430 script is running under upstart, and when it is not.&lt;/p&gt;
10431
10432 &lt;p&gt;With upstart, I notice these environment variables are set when a
10433 script is started from rcS.d/ (ignoring some irrelevant ones like
10434 COLUMNS):&lt;/p&gt;
10435
10436 &lt;blockquote&gt;&lt;pre&gt;
10437 DEFAULT_RUNLEVEL=2
10438 previous=N
10439 PREVLEVEL=
10440 RUNLEVEL=
10441 runlevel=S
10442 UPSTART_EVENTS=startup
10443 UPSTART_INSTANCE=
10444 UPSTART_JOB=rc-sysinit
10445 &lt;/pre&gt;&lt;/blockquote&gt;
10446
10447 &lt;p&gt;With sysvinit, these environment variables are set for the same
10448 script.&lt;/p&gt;
10449
10450 &lt;blockquote&gt;&lt;pre&gt;
10451 INIT_VERSION=sysvinit-2.88
10452 previous=N
10453 PREVLEVEL=N
10454 RUNLEVEL=S
10455 runlevel=S
10456 &lt;/pre&gt;&lt;/blockquote&gt;
10457
10458 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10459 sysvinit are not set by upstart. Not sure if it is intentional or not
10460 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10461
10462 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10463 looking for the UPSTART_JOB environment variable seem to be a good
10464 choice.&lt;/p&gt;
10465 </description>
10466 </item>
10467
10468 <item>
10469 <title>A manual for standards wars...</title>
10470 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10471 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10472 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10473 <description>&lt;p&gt;Via the
10474 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10475 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10476 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10477 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10478 following the standards wars of today.&lt;/p&gt;
10479 </description>
10480 </item>
10481
10482 <item>
10483 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10484 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10486 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10487 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10488 to get a list of the machine types in use thanks to the DMI
10489 information extracted from each machine. The script to do so is
10490 included in the sitesummary package, and here is example output from
10491 the Skolelinux build servers:&lt;/p&gt;
10492
10493 &lt;blockquote&gt;&lt;pre&gt;
10494 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10495 vendor count
10496 Dell Computer Corporation 1
10497 PowerEdge 1750 1
10498 IBM 1
10499 eserver xSeries 345 -[8670M1X]- 1
10500 Intel 2
10501 [no-dmi-info] 3
10502 maintainer:~#
10503 &lt;/pre&gt;&lt;/blockquote&gt;
10504
10505 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
10506 provided in each machine. Here there are Intel machines without model
10507 information listed with Intel as vendor and no model, and virtual Xen
10508 machines listed as [no-dmi-info]. One can add -l as a command line
10509 option to list the individual machines.&lt;/p&gt;
10510
10511 &lt;p&gt;A larger list is
10512 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
10513 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
10514 provide the basic sitesummary report publicly. In their report there
10515 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
10516 their machines, and as sitesummary is available in both distributions,
10517 it is trivial to get all of them to report to the same central
10518 collector.&lt;/p&gt;
10519 </description>
10520 </item>
10521
10522 <item>
10523 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
10524 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
10525 <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>
10526 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
10527 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
10528 start at boot when an NVidia video card is used is handled. The
10529 problem seem to be that the nvidia X.org driver uses a long time to
10530 initialize, and this duration is longer than kdm is configured to
10531 wait.&lt;/p&gt;
10532
10533 &lt;p&gt;I came across two bugs related to this issue,
10534 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
10535 against initscripts and passed on to nvidia-glx when it became obvious
10536 that the nvidia drivers were involved, and
10537 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
10538 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
10539
10540 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
10541 problem nvidia video card owners experience and make sure the Debian
10542 distribution work out of the box for these users. The nvidia driver
10543 maintainers expect kdm to be set up to wait longer, while kdm expect
10544 the nvidia driver maintainers to fix the driver to start faster, and
10545 while they wait for each other I guess the users end up switching to a
10546 distribution that work for them. I have no idea what the solution is,
10547 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
10548
10549 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
10550 </description>
10551 </item>
10552
10553 <item>
10554 <title>Parallellized boot seem to hold up well in Debian/testing</title>
10555 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
10556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
10557 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
10558 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
10559 The feature seem to hold up pretty well, but three fairly serious
10560 issues are known and should be solved:
10561
10562 &lt;p&gt;&lt;ul&gt;
10563
10564 &lt;li&gt;The wicd package seen to
10565 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
10566 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
10567 parallel booting is enabled. No idea why, but the wicd maintainer
10568 seem to be on the case.&lt;/li&gt;
10569
10570 &lt;li&gt;The nvidia X driver seem to
10571 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
10572 triggered more easily when parallel booting is in effect. The
10573 maintainer is on the case.&lt;/li&gt;
10574
10575 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
10576 sequencing (the shutdown is broken) when old file-rc users
10577 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
10578 sysv-rc. One way to solve it would be for file-rc to create
10579 /etc/init.d/.legacy-bootordering, and another is to try to make
10580 sysv-rc more robust. Will investigate some more and probably upload a
10581 workaround in sysv-rc to help those trying to move from file-rc to
10582 sysv-rc get a working shutdown.&lt;/li&gt;
10583
10584 &lt;/ul&gt;&lt;/p&gt;
10585
10586 &lt;p&gt;All in all not many surprising issues, and all of them seem
10587 solvable before Squeeze is released. In addition to these there are
10588 some packages with bugs in their dependencies and run level settings,
10589 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
10590
10591 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10592 the BTS, please usertag the report to get it to show up at
10593 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10594 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10595
10596 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
10597 </description>
10598 </item>
10599
10600 <item>
10601 <title>More flexible firmware handling in debian-installer</title>
10602 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
10603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
10604 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
10605 <description>&lt;p&gt;After a long break from debian-installer development, I finally
10606 found time today to return to the project. Having to spend less time
10607 working dependency based boot in debian, as it is almost complete now,
10608 definitely helped freeing some time.&lt;/p&gt;
10609
10610 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
10611 include some firmware packages on the Debian Edu CDs, those needed to
10612 get disk and network controllers working. Without having these
10613 firmware packages available during installation, it is impossible to
10614 install Debian Edu on the given machine, and because our target group
10615 are non-technical people, asking them to provide firmware packages on
10616 an external medium is a support pain. Initially, I expected it to be
10617 enough to include the firmware packages on the CD to get
10618 debian-installer to find and use them. This proved to be wrong.
10619 Next, I hoped it was enough to symlink the relevant firmware packages
10620 to some useful location on the CD (tried /cdrom/ and
10621 /cdrom/firmware/). This also proved to not work, and at this point I
10622 found time to look at the debian-installer code to figure out what was
10623 going to work.&lt;/p&gt;
10624
10625 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
10626 look revealed that it would only look for firmware packages outside
10627 the installation media, so the CD was never checked for firmware
10628 packages. It would only check USB sticks, floppies and other
10629 &quot;external&quot; media devices. Today I changed it to also look in the
10630 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10631 solve the problem I ran into with Debian edu. I also changed it to
10632 look in /firmware/, to make sure the installer also find firmware
10633 provided in the initrd when booting the installer via PXE, to allow us
10634 to provide the same feature in the PXE setup included in Debian
10635 Edu.&lt;/p&gt;
10636
10637 &lt;p&gt;To make sure firmware deb packages with a license questions are not
10638 activated without asking if the license is accepted, I extended
10639 hw-detect to look for preinst scripts in the firmware packages, and
10640 run these before activating the firmware during installation. The
10641 license question is asked using debconf in the preinst, so this should
10642 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
10643
10644 &lt;p&gt;If you want to discuss the details of these features, please
10645 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
10646 </description>
10647 </item>
10648
10649 <item>
10650 <title>Parallellized boot is now the default in Debian/unstable</title>
10651 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
10652 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
10653 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
10654 <description>&lt;p&gt;Since this evening, parallel booting is the default in
10655 Debian/unstable for machines using dependency based boot sequencing.
10656 Apparently the testing of concurrent booting has been wider than
10657 expected, if I am to believe the
10658 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10659 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
10660 with the feature this weekend, to give us some time to detect any
10661 remaining problems before Squeeze is frozen. If serious problems are
10662 detected, it is simple to change the default back to sequential boot.
10663 The upload of the new sysvinit package also activate a new upstream
10664 version.&lt;/p&gt;
10665
10666 More information about
10667 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10668 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
10669 currently possible to disable parallel booting when one run into
10670 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
10671
10672 &lt;blockquote&gt;&lt;pre&gt;
10673 CONCURRENCY=none
10674 &lt;/pre&gt;&lt;/blockquote&gt;
10675
10676 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10677 the BTS, please usertag the report to get it to show up at
10678 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10679 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10680 </description>
10681 </item>
10682
10683 <item>
10684 <title>Sitesummary tip: Listing MAC address of all clients</title>
10685 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
10686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
10687 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
10688 <description>&lt;p&gt;In the recent Debian Edu versions, the
10689 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
10690 system&lt;/a&gt; is used to keep track of the machines in the school
10691 network. Each machine will automatically report its status to the
10692 central server after boot and once per night. The network setup is
10693 also reported, and using this information it is possible to get the
10694 MAC address of all network interfaces in the machines. This is useful
10695 to update the DHCP configuration.&lt;/p&gt;
10696
10697 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
10698 ist all MAC addresses of all machines reporting to sitesummary. Run
10699 this on the collector host:&lt;/p&gt;
10700
10701 &lt;blockquote&gt;&lt;pre&gt;
10702 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
10703 &lt;/pre&gt;&lt;/blockquote&gt;
10704
10705 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
10706 line per machine and with space between the MAC addresses.&lt;/p&gt;
10707
10708 &lt;p&gt;To allow system administrators easier job at adding static DHCP
10709 addresses for hosts, it would be possible to extend this to fetch
10710 machine information from sitesummary and update the DHCP and DNS
10711 tables in LDAP using this information. Such tool is unfortunately not
10712 written yet.&lt;/p&gt;
10713 </description>
10714 </item>
10715
10716 <item>
10717 <title>systemd, an interesting alternative to upstart</title>
10718 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
10719 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
10720 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
10721 <description>&lt;p&gt;The last few days a new boot system called
10722 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
10723 has been
10724 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
10725
10726 to the free software world. I have not yet had time to play around
10727 with it, but it seem to be a very interesting alternative to
10728 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
10729 a good alternative for Debian when we are able to switch to an event
10730 based boot system. Tollef is
10731 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
10732 systemd into Debian, and I look forward to seeing how well it work. I
10733 like the fact that systemd handles init.d scripts with dependency
10734 information natively, allowing them to run in parallel where upstart
10735 at the moment do not.&lt;/p&gt;
10736
10737 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
10738 platform support. It only work on recent Linux kernels, and also need
10739 some new kernel features enabled to function properly. This means
10740 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10741 system. Not sure how that will be handled if systemd proves to be the
10742 way forward.&lt;/p&gt;
10743
10744 &lt;p&gt;In the mean time, based on the
10745 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10746 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
10747 decided to enable full parallel booting as the default in Debian as
10748 soon as possible (probably this weekend or early next week), to see if
10749 there are any remaining serious bugs in the init.d dependencies. A
10750 new version of the sysvinit package implementing this change is
10751 already in experimental. If all go well, Squeeze will be released
10752 with parallel booting enabled by default.&lt;/p&gt;
10753 </description>
10754 </item>
10755
10756 <item>
10757 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
10758 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
10759 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
10760 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
10761 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
10762 complete, so complete that it is actually possible to run all the
10763 init.d scripts in parallell based on these dependencies. If you want
10764 to test your Squeeze system, make sure
10765 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10766 based boot sequencing&lt;/a&gt; is enabled, and add this line to
10767 /etc/default/rcS:&lt;/p&gt;
10768
10769 &lt;blockquote&gt;&lt;pre&gt;
10770 CONCURRENCY=makefile
10771 &lt;/pre&gt;&lt;/blockquote&gt;
10772
10773 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
10774 scripts in parallel using the dependency information stored in
10775 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10776 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10777 to try to start the kdm and gdm scripts as early as possible, and will
10778 start the facilities required by kdm or gdm as early as possible to
10779 make this happen.&lt;/p&gt;
10780
10781 &lt;p&gt;Give it a try, and see if you like the result. If some services
10782 fail to start properly, it is most likely because they have incomplete
10783 init.d script dependencies in their startup script (or some of their
10784 dependent scripts have incomplete dependencies). Report bugs and get
10785 the package maintainers to fix it. :)&lt;/p&gt;
10786
10787 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
10788 manage to get the init.d script dependencies complete and correct. I
10789 expect we will get there in Squeeze+1, if we get manage to test and
10790 fix the remaining issues.&lt;/p&gt;
10791
10792 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10793 the BTS, please usertag the report to get it to show up at
10794 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10795 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10796 </description>
10797 </item>
10798
10799 <item>
10800 <title>Debian has switched to dependency based boot sequencing</title>
10801 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
10802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
10803 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
10804 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
10805 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
10806 have been migrated to using dependency based boot sequencing. This
10807 conclude work me and others have been doing for the last three days.
10808 It feels great to see this finally part of the default Debian
10809 installation. Now we just need to weed out the last few problems that
10810 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
10811
10812 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
10813 fixing the more fundamental problem of handing the event based
10814 non-predictable kernel in the early boot.&lt;/p&gt;
10815 </description>
10816 </item>
10817
10818 <item>
10819 <title>Taking over sysvinit development</title>
10820 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
10821 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
10822 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
10823 <description>&lt;p&gt;After several years of frustration with the lack of activity from
10824 the existing sysvinit upstream developer, I decided a few weeks ago to
10825 take over the package and become the new upstream. The number of
10826 patches to track for the Debian package was becoming a burden, and the
10827 lack of synchronization between the distribution made it hard to keep
10828 the package up to date.&lt;/p&gt;
10829
10830 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10831 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
10832 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
10833 and Fedora), based on the patches currently in use in these
10834 distributions. We Debian maintainers plan to move to this tarball as
10835 the new upstream as soon as we find time to do the merge. Since the
10836 new tarball was created, we agreed with Werner at SuSe to make a new
10837 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
10838 development there. The project is registered and currently waiting
10839 for approval by the Savannah administrators, and as soon as it is
10840 approved, we will import the old versions from svn and continue
10841 working on the future release.&lt;/p&gt;
10842
10843 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
10844 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
10845 </description>
10846 </item>
10847
10848 <item>
10849 <title>Debian boots quicker and quicker</title>
10850 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
10851 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
10852 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
10853 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
10854 people involved in the boot system on Debian and Ubuntu, to see if we
10855 could find more ways to speed up the boot system. This was an Ubuntu
10856 funded
10857 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
10858 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
10859 of boot systems, and ways to handle the increasing number of boot
10860 issues introduced by the Linux kernel becoming more and more
10861 asynchronous and event base. The Ubuntu approach using udev and
10862 upstart might be a good way forward. Time will show.&lt;/p&gt;
10863
10864 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
10865 process in Debian. All of these should be applied to get a quick
10866 boot:&lt;/p&gt;
10867
10868 &lt;ul&gt;
10869
10870 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
10871
10872 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
10873 clock is in UTC.&lt;/li&gt;
10874
10875 &lt;li&gt;Install and activate the insserv package to enable
10876 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10877 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
10878
10879 &lt;/ul&gt;
10880
10881 These points are based on the Google summer of code work done by
10882 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
10883 Villegas&lt;/a&gt;.
10884
10885 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
10886 unstable yesterday. When we tested it, we were able to cut 6 seconds
10887 from the boot sequence. It depend on very correct dependency
10888 declaration in all init.d scripts, so I expect us to find edge cases
10889 where the dependences in some scripts are slightly wrong when we start
10890 using this.&lt;/p&gt;
10891
10892 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10893 introduced by Raphael Geissert today, one that could affect the
10894 startup speed as well. Instead of starting some scripts concurrently
10895 from rcS.d/ and another set of scripts from rc2.d/, it would be
10896 possible to run a of them in the same process. A quick way to test
10897 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
10898 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
10899 </description>
10900 </item>
10901
10902 <item>
10903 <title>BSAs påstander om piratkopiering møter motstand</title>
10904 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
10905 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
10906 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
10907 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
10908 programvareselskapene som Microsoft og Apple, publisert en rapport der
10909 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10910 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10911 dager siden kom
10912 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
10913 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
10914 dagene. Et spesielt interessant kommentar fra Sverige,
10915 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
10916 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
10917
10918 &lt;blockquote&gt;
10919 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
10920 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10921 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
10922 exakta&quot;, säger BSAs Sverigechef John Hugosson.
10923 &lt;/blockquote&gt;
10924
10925 &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
10926 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
10927 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
10928 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
10929 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
10930
10931 &lt;p&gt;Fant lenkene via &lt;a
10932 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
10933 på Slashdot&lt;/a&gt;.&lt;/p&gt;
10934 </description>
10935 </item>
10936
10937 <item>
10938 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
10939 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
10940 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
10941 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
10942 <description>&lt;p&gt;Kom over
10943 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
10944 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10945 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10946 jobber til daglig. En rask opptelling forteller meg at vi har 490
10947 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
10948 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
10949 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
10950 </description>
10951 </item>
10952
10953 <item>
10954 <title>Kryptert harddisk - naturligvis</title>
10955 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
10956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
10957 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
10958 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
10959 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
10960 når en tar tap av arbeidstid, fortrolige dokumenter,
10961 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10962 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10963 til at jeg har kryptert harddisken på både kontormaskinen og min
10964 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10965 komme på avveie, den første informasjon relatert til jobben min ved
10966 Universitetet i Oslo, og den andre relatert til blant annet
10967 foreningsarbeide. Kryptering av diskene gjør at det er lite
10968 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10969 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10970 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10971 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10972 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10973 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10974 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10975 det er gjort slik jeg gjør det er minimale, og gevinstene er
10976 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10977 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
10978
10979 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10980 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10981 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10982 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10983 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10984 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10985 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10986 betydelige.&lt;/p&gt;
10987 </description>
10988 </item>
10989
10990 <item>
10991 <title>Two projects that have improved the quality of free software a lot</title>
10992 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
10993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
10994 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
10995 <description>&lt;p&gt;There are two software projects that have had huge influence on the
10996 quality of free software, and I wanted to mention both in case someone
10997 do not yet know them.&lt;/p&gt;
10998
10999 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11000 tool to detect and expose errors in the memory handling of programs.
11001 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11002 and it will report any problems on stdout. It is even better if the
11003 program include debug information. With debug information, it is able
11004 to report the source file name and line number where the problem
11005 occurs. It can report things like &#39;reading past memory block in file
11006 X line N, the memory block was allocated in file Y, line M&#39;, and
11007 &#39;using uninitialised value in control logic&#39;. This tool has made it
11008 trivial to investigate reproducible crash bugs in programs, and have
11009 reduced the number of this kind of bugs in free software a lot.
11010
11011 &lt;p&gt;The second one is
11012 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11013 a source code checker. It is able to process the source of a program
11014 and find problems in the logic without running the program. It
11015 started out as the Stanford Checker and became well known when it was
11016 used to find bugs in the Linux kernel. It is now a commercial tool
11017 and the company behind it is running
11018 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11019 free software community, where a lot of free software projects get
11020 their source checked for free. Several thousand defects have been
11021 found and fixed so far. It can find errors like &#39;lock L taken in file
11022 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11023 Y lines O to P can never be executed&#39;. The projects included in the
11024 community service project have managed to get rid of a lot of
11025 reliability problems thanks to Coverity.&lt;/p&gt;
11026
11027 &lt;p&gt;I believe tools like this, that are able to automatically find
11028 errors in the source, are vital to improve the quality of software and
11029 make sure we can get rid of the crashing and failing software we are
11030 surrounded by today.&lt;/p&gt;
11031 </description>
11032 </item>
11033
11034 <item>
11035 <title>No patch is not better than a useless patch</title>
11036 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11037 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11038 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11039 <description>&lt;p&gt;Julien Blache
11040 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11041 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11042 patch allow one to discuss a concrete and proposed solution, and also
11043 prove that the issue at hand is important enough for someone to spent
11044 time on fixing it. No patch do not provide any of these positive
11045 properties.&lt;/p&gt;
11046 </description>
11047 </item>
11048
11049 <item>
11050 <title>Standardize on protocols and formats, not vendors and applications</title>
11051 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11053 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11054 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11055 very good one to form a long lived computer infrastructure. It is the
11056 simple one, lost by many in todays computer industry: Standardize on
11057 open network protocols and open exchange/storage formats, not applications.
11058 Applications come and go, while protocols and files tend to stay, and
11059 thus one want to make it easy to change application and vendor, while
11060 avoiding conversion costs and locking users to a specific platform or
11061 application.&lt;/p&gt;
11062
11063 &lt;p&gt;This approach make it possible to replace the client applications
11064 independently of the server applications. One can even allow users to
11065 use several different applications as long as they handle the selected
11066 protocol and format. In the normal case, only one client application
11067 is recommended and users only get help if they choose to use this
11068 application, but those that want to deviate from the easy path are not
11069 blocked from doing so.&lt;/p&gt;
11070
11071 &lt;p&gt;It also allow us to replace the server side without forcing the
11072 users to replace their applications, and thus allow us to select the
11073 best server implementation at any moment, when scale and resouce
11074 requirements change.&lt;/p&gt;
11075
11076 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11077 open formats, but I would never recommend standardizing on a single
11078 application that do not use open network protocol or open formats.&lt;/p&gt;
11079 </description>
11080 </item>
11081
11082 <item>
11083 <title>Returning from Skolelinux developer gathering</title>
11084 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11086 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11087 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11088 Edu/Skolelinux development gathering. I got a bit done tuning the
11089 desktop, and looked into the dynamic service location protocol
11090 implementation avahi. It look like it could be useful for us. Almost
11091 30 people participated, and I believe it was a great environment to
11092 get to know the Skolelinux system. Walter Bender, involved in the
11093 development of the Sugar educational platform, presented his stuff and
11094 also helped me improve my OLPC installation. He also showed me that
11095 his Turtle Art application can be used in standalone mode, and we
11096 agreed that I would help getting it packaged for Debian. As a
11097 standalone application it would be great for Debian Edu. We also
11098 tried to get the video conferencing working with two OLPCs, but that
11099 proved to be too hard for us. The application seem to need more work
11100 before it is ready for me. I look forward to getting home and relax
11101 now. :)&lt;/p&gt;
11102 </description>
11103 </item>
11104
11105 <item>
11106 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11107 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11109 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11110 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11111 optimal. There is RFC 2307 documenting one way to store NIS maps in
11112 LDAP, and a modified version of this normally called RFC 2307bis, with
11113 some modifications to be compatible with Active Directory. The RFC
11114 specification handle the content of a lot of system databases, but do
11115 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11116
11117 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11118 we would like to store information about users, SMB clients/hosts,
11119 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11120 and LTSP configuration in LDAP. These objects have a lot in common,
11121 but with the current LDAP schemas it is not possible to have one
11122 object per entity. For example, one need to have at least three LDAP
11123 objects for a given computer, one with the SMB related stuff, one with
11124 DNS information and another with DHCP information. The schemas
11125 provided for DNS and DHCP are impossible to combine into one LDAP
11126 object. In addition, it is impossible to implement quick queries for
11127 netgroup membership, because of the way NIS triples are implemented.
11128 It just do not scale. I believe it is time for a few RFC
11129 specifications to cleam up this mess.&lt;/p&gt;
11130
11131 &lt;p&gt;I would like to have one LDAP object representing each computer in
11132 the network, and this object can then keep the SMB (ie host key), DHCP
11133 (mac address/name) and DNS (name/IP address) settings in one place.
11134 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11135
11136 &lt;p&gt;I would also like to have a quick way to map from a user or
11137 computer and to the net group this user or computer is a member.&lt;/p&gt;
11138
11139 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11140 in this regard, and the unix side need to catch up. Time to start a
11141 new IETF work group?&lt;/p&gt;
11142 </description>
11143 </item>
11144
11145 <item>
11146 <title>Endelig er Debian Lenny gitt ut</title>
11147 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11149 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11150 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11151 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11152 Et langt steg videre for Debian-prosjektet, og en rekke nye
11153 programpakker blir nå tilgjengelig for de av oss som bruker den
11154 stabile utgaven av Debian. Neste steg er nå å få
11155 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11156 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11157 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11158 slippes løs på skolene. Takk til alle debian-utviklerne som har
11159 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11160 bootsekvens tilgjengelig i stabil utgave, vha pakken
11161 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11162 </description>
11163 </item>
11164
11165 <item>
11166 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11167 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11168 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11169 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11170 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11171 Oslo. Most of Saturday was used for the general assemly for the
11172 member organization, but the rest of the weekend I used to tune the
11173 LTSP installation. LTSP now work out of the box on the 10-network.
11174 Acer Aspire One proved to be a very nice thin client, with both
11175 screen, mouse and keybard in a small box. Was working on getting the
11176 diskless workstation setup configured out of the box, but did not
11177 finish it before the weekend was up.&lt;/p&gt;
11178
11179 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11180 the Brazilian group, so that will have to wait for the next
11181 development gathering. Would love to have the Debian Edu installer
11182 automatically detect and configure a multiseat setup when it find one
11183 of these cards.&lt;/p&gt;
11184 </description>
11185 </item>
11186
11187 <item>
11188 <title>The sorry state of multimedia browser plugins in Debian</title>
11189 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11190 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11191 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11192 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11193 plugins available in Debian Lenny, to see which one we should use by
11194 default in Debian Edu. We need an embedded video playing plugin with
11195 control buttons to pause or stop the video, and capable of streaming
11196 all the multimedia content available on the web. The test results and
11197 notes are available on
11198 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11199 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11200 fill this need. My personal video player favorite, VLC, has a really
11201 bad plugin which fail on a lot of the test pages. A lot of the MIME
11202 types I would expect to work with any free software player (like
11203 video/ogg), just do not work. And simple formats like the
11204 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11205 totem and vlc plugins. I hope the situation will improve soon. No
11206 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11207
11208 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11209 be the only one fitting our needs. :/&lt;/p&gt;
11210 </description>
11211 </item>
11212
11213 </channel>
11214 </rss>