]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
d1f8e52bb2bb16073ffe3dc6da8cabbb6caa206d
[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>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
11 <link>http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
13 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
14 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
15 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
16 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
17 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
18 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
19 nye versjonen kom på nyåret, og ble
20 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
21 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
22 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
23 måtte justeres, men ikke noe alvorlig. Har oppdatert
24 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
25 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
26
27 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
28 å spille for oss som liker slikt. :)&lt;/p&gt;
29
30 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
31 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
32 til min adresse
33 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
34 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
35 </description>
36 </item>
37
38 <item>
39 <title>Debian now got everything you need to program Micro:bit</title>
40 <link>http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
41 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
42 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
43 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
44 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
45 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
46 thanks to the hard work of Nick Morrott and the Debian python
47 packaging team. The micro:bit project recommend the mu-editor to
48 program the microcomputer, as this editor will take care of all the
49 machinery required to injekt/flash micropython alongside the program
50 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
51
52 &lt;p&gt;There are three main pieces involved. The first to enter Debian
53 was
54 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
55 which was accepted into the archive 2019-01-12. The next one was
56 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
57 showed up 2019-01-13. The final and hardest part to to into the
58 archive was
59 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
60 which needed to get its build system and dependencies into Debian
61 before it was accepted 2019-01-20. The last one is already in Debian
62 Unstable and should enter Debian Testing / Buster in three days. This
63 all allow any user of the micro:bit to get going by simply running
64 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
65 Buster is released as stable, all the users of Debian stable will be
66 catered for.&lt;/p&gt;
67
68 &lt;p&gt;As a minor final touch, I added rules to
69 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
70 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
71 package. This make sure any user of the isenkram desktop daemon will
72 get a popup suggesting to install mu-editor then the USB cable from
73 the micro:bit is inserted for the first time.&lt;/p&gt;
74
75 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
76
77 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
78 activities, please send Bitcoin donations to my address
79 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
80 </description>
81 </item>
82
83 <item>
84 <title>Learn to program with Minetest on Debian</title>
85 <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
86 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
87 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
88 <description>&lt;p&gt;A fun way to learn how to program
89 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
90 instructions in the book
91 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
92 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
93 who like to play with Minecraft. The book uses a Python library to
94 talk to a TCP/IP socket with an API accepting build instructions and
95 providing information about the current players in a Minecraft world.
96 The TCP/IP API was first created for the Minecraft implementation for
97 Raspberry Pi, and has since been ported to some server versions of
98 Minecraft. The book contain recipes for those using Windows, MacOSX
99 and Raspian. But a little known fact is that you can follow the same
100 recipes using the free software construction game
101 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
102
103 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
104 Minetest module implementing the same API&lt;/a&gt;, making it possible to
105 use the Python programs coded to talk to Minecraft with Minetest too.
106 I
107 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
108 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
109 FTP masters NEW queue, learning to program Python with Minetest on
110 Debian will be a simple &#39;apt install&#39; away. The Debian package is
111 maintained as part of the Debian Games team, and
112 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
113 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
114 Salsa.&lt;/p&gt;
115
116 &lt;p&gt;You will most likely need to install several of the Minetest
117 modules in Debian for the examples included with the library to work
118 well, as there are several blocks used by the example scripts that are
119 provided via modules in Minetest. Without the required blocks, a
120 simple stone block is used instead. My initial testing with a analog
121 clock did not get gold arms as instructed in the python library, but
122 instead used stone arms.&lt;/p&gt;
123
124 &lt;p&gt;I tried to find a way to add the API to the desktop version of
125 Minecraft, but were unable to find any working recipes. The
126 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
127 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
128 working with a standalone Minecraft server setup. Are there any
129 options to use with the normal desktop version?&lt;/p&gt;
130
131 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
132 activities, please send Bitcoin donations to my address
133 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
134 </description>
135 </item>
136
137 <item>
138 <title>Time for an official MIME type for patches?</title>
139 <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
140 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
141 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
142 <description>&lt;p&gt;As part of my involvement in
143 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
144 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
145 emails into a test instance of the archive to see how well this would
146 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
147 notmuch email database&lt;/a&gt;, all public emails sent to me via
148 @lists.debian.org, giving me a set of around 216 000 emails to import.
149 In the process, I had a look at the various attachments included in
150 these emails, to figure out what to do with attachments, and noticed
151 that one of the most common attachment formats do not have
152 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
153 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
154 diff, ie the input for patch, is on the top 10 list of formats
155 included in these emails. At the moment people seem to use either
156 text/x-patch or text/x-diff, but neither is officially registered. It
157 would be better if one official MIME type were registered and used
158 everywhere.&lt;/p&gt;
159
160 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
161 up the topic on
162 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
163 media-types mailing list&lt;/a&gt;. If you are interested in discussion
164 which MIME type to use as the official for patch files, or involved in
165 making software using a MIME type for patches, perhaps you would like
166 to join the discussion?&lt;/p&gt;
167
168 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
169 activities, please send Bitcoin donations to my address
170 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
171 </description>
172 </item>
173
174 <item>
175 <title>Automatic Google Drive sync using grive in Debian</title>
176 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
178 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
179 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
180 rescue the remains, I helped set up automatic sync with Google Drive.
181 I did not find any sensible Debian package handling this
182 automatically, so I rebuild the grive2 source from
183 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
184 task and added a autostart desktop entry and a small shell script to
185 run in the background while the user is logged in to do the sync.
186 Here is a sketch of the setup for future reference.&lt;/p&gt;
187
188 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
189 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
190 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
191 to start the sync when the user log in:&lt;/p&gt;
192
193 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
194 [Desktop Entry]
195 Name=Google drive autosync
196 Type=Application
197 Exec=/home/user/bin/grive-sync
198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
199
200 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
201 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
202
203 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
204 #!/bin/sh
205 set -e
206 cd ~/
207 cleanup() {
208 if [ &quot;$syncpid&quot; ] ; then
209 kill $syncpid
210 fi
211 }
212 trap cleanup EXIT INT QUIT
213 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
214 syncpdi=$!
215 while true; do
216 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
217 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
218 exit 1
219 fi
220 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
221 /usr/lib/grive/grive-sync.sh sync googledrive
222 fi
223 sleep 300
224 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
225 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
226
227 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
228 GNU GPL v2 licensed (or any later version, at your leisure), but I
229 doubt this code is possible to claim copyright on.&lt;/p&gt;
230
231 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
232 activities, please send Bitcoin donations to my address
233 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
234 </description>
235 </item>
236
237 <item>
238 <title>Using the Kodi API to play Youtube videos</title>
239 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
241 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
242 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
243 tell it to play a youtube URL I received in a chat, without having to
244 insert search terms using the on-screen keyboard. After searching the
245 web for API access to the Youtube plugin and testing a bit, I managed
246 to find a recipe that worked. If you got a kodi instance with its API
247 available from http://kodihost/jsonrpc, you can try the following to
248 have check out a nice cover band.&lt;/p&gt;
249
250 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
251 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
252 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
253 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
254 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
255
256 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
257 first argument. It can now handle direct video links, youtube links
258 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
259 Chromecast. :)&lt;/p&gt;
260
261 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
262 activities, please send Bitcoin donations to my address
263 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
264 </description>
265 </item>
266
267 <item>
268 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
269 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
271 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
272 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
273 with my family using a self hosted solution, as it is unacceptable to
274 place images from my personal life under the control of strangers
275 working for data hoarders like Google or Dropbox. The last few days I
276 have drafted an approach that might work out, and I would like to
277 share it with you. I would like to publish images on a server under
278 my control, and point some Internet connected display units using some
279 free and open standard to the images I published. As my primary
280 language is not limited to ASCII, I need to store metadata using
281 UTF-8. Many years ago, I hoped to find a digital photo frame capable
282 of reading a RSS feed with image references (aka using the
283 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
284 of such frames. In the end I gave up that approach.&lt;/p&gt;
285
286 &lt;p&gt;Some months ago, I discovered that
287 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
288 read images from a RSS feed, and used it to set up a screen saver on
289 my home info screen, showing images from the Daily images feed from
290 NASA. This proved to work well. More recently I discovered that
291 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
292 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
293 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
294 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
295 screen saver capable of reading a RSS feed with images and news. For
296 fun, I used it this summer to test Kodi on my parents TV by hooking up
297 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
298 screen saver showing selected pictures from my selection.&lt;/p&gt;
299
300 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
301 a RSS feed for the Kodi instance. I adjusted my &lt;a
302 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
303 /var/www/html/privatepictures/, wrote a small Perl script to extract
304 title and description metadata from the photo files and generate the
305 RSS file. I ended up using Perl instead of python, as the
306 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
307 tags I ended up using, while python3-exif did not. The relevant EXIF
308 tags only support ASCII, so I had to find better alternatives. XMP
309 seem to have the support I need.&lt;/p&gt;
310
311 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
312 use tags that can be easily added/updated using normal free software
313 photo managing software. I ended up using the tags set using this
314 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
315
316 &lt;blockquote&gt;&lt;pre&gt;
317 exiftool -headline=&#39;The RSS image title&#39; \
318 -description=&#39;The RSS image description.&#39; \
319 -subject+=for-family photo.jpeg
320 &lt;/pre&gt;&lt;/blockquote&gt;
321
322 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
323 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
324 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
325 shared with my family. Images with this keyword set are located and
326 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
327
328 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
329 suggestions.&lt;/p&gt;
330
331 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
332 activities, please send Bitcoin donations to my address
333 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
334 </description>
335 </item>
336
337 <item>
338 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
339 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
341 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
342 <description>&lt;p&gt;Last night, I wrote
343 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
344 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
345 During the day I received valuable feedback, and thanks to the
346 suggestions I have been able to rewrite the recipe into a much simpler
347 approach requiring no setup at all. It is a single script that take
348 care of it all.&lt;/p&gt;
349
350 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
351 desktop and stream it to Kodi. This fixed the video quality issue I
352 saw initially. It further removes the need to add a m3u file on the
353 Kodi machine, as it instead connects to
354 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
355 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
356 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
357 the script below, run it with the DNS name or IP address of the kodi
358 server to stream to as the only argument, and watch your screen show
359 up on the Kodi screen. Note, it depend on multicast on the local
360 network, so if you need to stream outside the local network, the
361 script must be modified. Also note, I have no idea if audio work, as
362 I only care about the picture part.&lt;/p&gt;
363
364 &lt;blockquote&gt;&lt;pre&gt;
365 #!/bin/sh
366 #
367 # Stream the Linux desktop view to Kodi. See
368 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
369 # for backgorund information.
370
371 # Make sure the stream is stopped in Kodi and the gstreamer process is
372 # killed if something go wrong (for example if curl is unable to find the
373 # kodi server). Do the same when interrupting this script.
374 kodicmd() {
375 host=&quot;$1&quot;
376 cmd=&quot;$2&quot;
377 params=&quot;$3&quot;
378 curl --silent --header &#39;Content-Type: application/json&#39; \
379 --data-binary &quot;{ \&quot;id\&quot;: 1, \&quot;jsonrpc\&quot;: \&quot;2.0\&quot;, \&quot;method\&quot;: \&quot;$cmd\&quot;, \&quot;params\&quot;: $params }&quot; \
380 &quot;http://$host/jsonrpc&quot;
381 }
382 cleanup() {
383 if [ -n &quot;$kodihost&quot; ] ; then
384 # Stop the playing when we end
385 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
386 jq .result[].playerid)
387 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
388 fi
389 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
390 kill &quot;$gstpid&quot;
391 fi
392 }
393 trap cleanup EXIT INT
394
395 if [ -n &quot;$1&quot; ]; then
396 kodihost=$1
397 shift
398 else
399 kodihost=kodi.local
400 fi
401
402 mcast=239.255.0.1
403 mcastport=1234
404 mcastttl=1
405
406 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
407 cut -d&quot; &quot; -f2|head -1)
408 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
409 videoconvert ! queue2 ! \
410 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
411 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
412 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
413 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
414 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
415 &gt; /dev/null 2&gt;&amp;1 &amp;
416 gstpid=$!
417
418 # Give stream a second to get going
419 sleep 1
420
421 # Ask kodi to start streaming using its JSON-RPC API
422 kodicmd &quot;$kodihost&quot; Player.Open \
423 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
424
425 # wait for gst to end
426 wait &quot;$gstpid&quot;
427 &lt;/pre&gt;&lt;/blockquote&gt;
428
429 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
430
431 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
432 activities, please send Bitcoin donations to my address
433 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
434 </description>
435 </item>
436
437 <item>
438 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
439 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
440 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
441 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
442 <description>&lt;p&gt;PS: See
443 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
444 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
445
446 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
447 my projector connected to Kodi. I sadly had to admit that I had no
448 idea, as it was a task I never had tried. Since then, I have been
449 looking for a way to do so, preferable without much extra software to
450 install on either side. Today I found a way that seem to kind of
451 work. Not great, but it is a start.&lt;/p&gt;
452
453 &lt;p&gt;I had a look at several approaches, for example
454 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
455 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
456 local storage enough to store the stream locally. This is not going
457 to work well for me, lacking enough free space, and it would
458 impossible for my friend to get working.&lt;/p&gt;
459
460 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
461 video stream that Kodi could play. Preferably using
462 broadcast/multicast, to avoid having to change any setup on the Kodi
463 side when starting such stream. Unfortunately, the only recipe I
464 could find using multicast used the rtp protocol, and this protocol
465 seem to not be supported by Kodi.&lt;/p&gt;
466
467 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
468 have to specify the IP address of the streaming machine in both the
469 sending command and the file on the Kodi server. But it is showing my
470 desktop, and thus allow us to have a shared look on the big screen at
471 the programs I work on.&lt;/p&gt;
472
473 &lt;p&gt;I did not spend much time investigating codeces. I combined the
474 rtp and rtsp recipes from
475 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
476 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
477 this working on the desktop/streaming end.&lt;/p&gt;
478
479 &lt;blockquote&gt;&lt;pre&gt;
480 vlc screen:// --sout \
481 &#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;
482 &lt;/pre&gt;&lt;/blockquote&gt;
483
484 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
485 same IP address:&lt;/p&gt;
486
487 &lt;blockquote&gt;&lt;pre&gt;
488 echo rtsp://192.168.11.4:8080/test.sdp \
489 &gt; /storage/videos/screenstream.m3u
490 &lt;/pre&gt;&lt;/blockquote&gt;
491
492 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
493 as I can tell the IP must be hardcoded for this to work. In other
494 words, if someone elses machine is going to do the steaming, you have
495 to update screenstream.m3u on the Kodi machine and adjust the vlc
496 recipe. To get started, locate the file in Kodi and select the m3u
497 file while the VLC stream is running. The desktop then show up in my
498 big screen. :)&lt;/p&gt;
499
500 &lt;p&gt;When using the same technique to stream a video file with audio,
501 the audio quality is really bad. No idea if the problem is package
502 loss or bad parameters for the transcode. I do not know VLC nor Kodi
503 enough to tell.&lt;/p&gt;
504
505 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
506 succestions and reminded me about an important step. The &quot;screen:&quot;
507 input source is only available once the vlc-plugin-access-extra
508 package is installed on Debian. Without it, you will see this error
509 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
510 for details.&quot; He further found that it is possible to drop some parts
511 of the VLC command line to reduce the amount of hardcoded information.
512 It is also useful to consider using cvlc to avoid having the VLC
513 window in the desktop view. In sum, this give us this command line on
514 the source end
515
516 &lt;blockquote&gt;&lt;pre&gt;
517 cvlc screen:// --sout \
518 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
519 &lt;/pre&gt;&lt;/blockquote&gt;
520
521 &lt;p&gt;and this on the Kodi end&lt;p&gt;
522
523 &lt;blockquote&gt;&lt;pre&gt;
524 echo rtsp://192.168.11.4:8080/ \
525 &gt; /storage/videos/screenstream.m3u
526 &lt;/pre&gt;&lt;/blockquote&gt;
527
528 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
529 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
530 audio quality, so I guess the issue is in the input or transcoding
531 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
532 parameters to use more bandwidth, but it did not make a
533 difference.&lt;/p&gt;
534
535 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
536 gstreamer instead of VLC, and this proved to work great! He also
537 provided me with the trick to get Kodi to use a multicast stream as
538 its source. By using this monstrous oneliner, I can stream my desktop
539 with good video quality in reasonable framerate to the 239.255.0.1
540 multicast address on port 1234:
541
542 &lt;blockquote&gt;&lt;pre&gt;
543 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
544 videoconvert ! queue2 ! \
545 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
546 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
547 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
548 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
549 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
550 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
551 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
552 &lt;/pre&gt;&lt;/blockquote&gt;
553
554 &lt;p&gt;and this on the Kodi end&lt;p&gt;
555
556 &lt;blockquote&gt;&lt;pre&gt;
557 echo udp://@239.255.0.1:1234 \
558 &gt; /storage/videos/screenstream.m3u
559 &lt;/pre&gt;&lt;/blockquote&gt;
560
561 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
562 pick the one you need. This approach will of course lead to trouble
563 if more than one source uses the same multicast port and address.
564 Note the ttl-mc=1 setting, which limit the multicast packages to the
565 local network. If the value is increased, your screen will be
566 broadcasted further, one network &quot;hop&quot; for each increase (read up on
567 multicast to learn more. :)!&lt;/p&gt;
568
569 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
570 could use this VLC command to stream to the same multicast address.
571 The image quality is way better than the rtsp approach, but gstreamer
572 seem to be doing a better job.&lt;/p&gt;
573
574 &lt;blockquote&gt;&lt;pre&gt;
575 cvlc screen:// --sout &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}&#39;
576 &lt;/pre&gt;&lt;/blockquote&gt;
577
578 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
579 activities, please send Bitcoin donations to my address
580 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
581 </description>
582 </item>
583
584 <item>
585 <title>What is the most supported MIME type in Debian in 2018?</title>
586 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
588 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
589 <description>&lt;p&gt;Five years ago,
590 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
591 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
592 analysing the desktop files in all packages in the archive. Since
593 then, the DEP-11 AppStream system has been put into production, making
594 the task a lot easier. This made me want to repeat the measurement,
595 to see how much things changed. Here are the new numbers, for
596 unstable only this time:
597
598 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
599
600 &lt;pre&gt;
601 count MIME type
602 ----- -----------------------
603 56 image/jpeg
604 55 image/png
605 49 image/tiff
606 48 image/gif
607 39 image/bmp
608 38 text/plain
609 37 audio/mpeg
610 34 application/ogg
611 33 audio/x-flac
612 32 audio/x-mp3
613 30 audio/x-wav
614 30 audio/x-vorbis+ogg
615 29 image/x-portable-pixmap
616 27 inode/directory
617 27 image/x-portable-bitmap
618 27 audio/x-mpeg
619 26 application/x-ogg
620 25 audio/x-mpegurl
621 25 audio/ogg
622 24 text/html
623 &lt;/pre&gt;
624
625 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
626 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
627 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
628
629 &lt;p&gt;It is interesting to see how image formats have passed text/plain
630 as the most announced supported MIME type. These days, thanks to the
631 AppStream system, if you run into a file format you do not know, and
632 want to figure out which packages support the format, you can find the
633 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
634 look up all packages announcing support for this format in their
635 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
636 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
637 me, want to know which packages support inode/directory, you can get a
638 list like this:&lt;/p&gt;
639
640 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
641 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
642 Package: anjuta
643 Package: audacious
644 Package: baobab
645 Package: cervisia
646 Package: chirp
647 Package: dolphin
648 Package: doublecmd-common
649 Package: easytag
650 Package: enlightenment
651 Package: ephoto
652 Package: filelight
653 Package: gwenview
654 Package: k4dirstat
655 Package: kaffeine
656 Package: kdesvn
657 Package: kid3
658 Package: kid3-qt
659 Package: nautilus
660 Package: nemo
661 Package: pcmanfm
662 Package: pcmanfm-qt
663 Package: qweborf
664 Package: ranger
665 Package: sirikali
666 Package: spacefm
667 Package: spacefm
668 Package: vifm
669 %
670 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
671
672 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
673 format is not yet supported by any package in Debian:&lt;/p&gt;
674
675 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
676 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
677 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
678 %
679 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
680
681 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
682 format:&lt;/p&gt;
683
684 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
685 % appstreamcli what-provides mimetype application/sla|grep Package
686 Package: cura
687 Package: meshlab
688 Package: printrun
689 %
690 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
691
692 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
693
694 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
695 activities, please send Bitcoin donations to my address
696 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
697 </description>
698 </item>
699
700 <item>
701 <title>Debian APT upgrade without enough free space on the disk...</title>
702 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
704 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
705 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
706 for a while, and when I need to update it there is not enough free
707 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
708 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
709 upgrade only some of the packages in one batch, until the amount of
710 packages to download fall below the amount of free space available.
711 Today, I had about 500 packages to upgrade, and after a while I got
712 tired of trying to install chunks of packages manually. I concluded
713 that I did not have the spare hours required to complete the task, and
714 decided to see if I could automate it. I came up with this small
715 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
716
717 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
718 #!/bin/sh
719 #
720 # Upgrade packages when the disk is too full to upgrade every
721 # upgradable package in one lump. Fetching packages to upgrade using
722 # apt, and then installing using dpkg, to avoid changing the package
723 # flag for manual/automatic.
724
725 set -e
726
727 ignore() {
728 if [ &quot;$1&quot; ]; then
729 grep -v &quot;$1&quot;
730 else
731 cat
732 fi
733 }
734
735 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
736 echo &quot;Upgrading $p&quot;
737 apt clean
738 apt install --download-only -y $p
739 for f in /var/cache/apt/archives/*.deb; do
740 if [ -e &quot;$f&quot; ]; then
741 dpkg -i /var/cache/apt/archives/*.deb
742 break
743 fi
744 done
745 done
746 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
747
748 &lt;p&gt;The script will extract the list of packages to upgrade, try to
749 download the packages needed to upgrade one package, install the
750 downloaded packages using dpkg. The idea is to upgrade packages
751 without changing the APT mark for the package (ie the one recording of
752 the package was manually requested or pulled in as a dependency). To
753 use it, simply run it as root from the command line. If it fail, try
754 &#39;apt install -f&#39; to clean up the mess and run the script again. This
755 might happen if the new packages conflict with one of the old
756 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
757
758 &lt;p&gt;It take one option, a package to ignore in the list of packages to
759 upgrade. The option to ignore a package is there to be able to skip
760 the packages that are simply too large to unpack. Today this was
761 &#39;ghc&#39;, but I have run into other large packages causing similar
762 problems earlier (like TeX).&lt;/p&gt;
763
764 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
765 alternative ways to handle this. The &quot;unattended-upgrades
766 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
767 each package to upgrade, and then upgrade them in order, smallest set
768 first. It might be a better option than my above mentioned script.
769 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
770 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
771
772 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
773 activities, please send Bitcoin donations to my address
774 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
775 </description>
776 </item>
777
778 <item>
779 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
780 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
781 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
782 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
783 <description>&lt;p&gt;A new version of the
784 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
785 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
786 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
787 useful. It was uploaded the last few days, and the last update will
788 enter testing tomorrow. See the
789 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
790 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
791 was announced 6 days ago. We will try to get it into Debian as
792 well.&lt;/p&gt;
793
794 &lt;p&gt;More information related to 3D printing is available on the
795 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
796 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
797 in Debian.&lt;/p&gt;
798
799 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
800 activities, please send Bitcoin donations to my address
801 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
802 </description>
803 </item>
804
805 <item>
806 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
807 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
809 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
810 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
811 that the nice and user friendly 3D printer slicer software Cura just
812 entered Debian Unstable. It consist of five packages,
813 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
814 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
815 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
816 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
817 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
818 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
819 two, uranium and cura, entered Unstable yesterday. This should make
820 it easier for Debian users to print on at least the Ultimaker class of
821 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
822 make life easier for at least me. :)&lt;/p&gt;
823
824 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
825 happy to assist him in sponsoring the packages. With the introduction
826 of Cura, Debian is up to three 3D printer slicers at your service,
827 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
828 printer, give it a go. :)&lt;/p&gt;
829
830 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
831 team, flocking together on the
832 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
833 mailing list and the
834 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
835 IRC channel.&lt;/p&gt;
836
837 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
838 version 3.0.3 and then update the entire set of packages to version
839 3.1.0 which showed up the last few days.&lt;/p&gt;
840 </description>
841 </item>
842
843 <item>
844 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
845 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
846 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
847 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
848 <description>&lt;p&gt;At my nearby maker space,
849 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
850 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
851 on Windows and MacOS X than Linux, because the software involved had
852 to be manually compiled and set up on Linux while premade packages
853 worked out of the box on Windows and MacOS X. I found this annoying,
854 as the software involved,
855 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
856 and should be trivial to get up and running on Linux if someone took
857 the time to package it for the relevant distributions. I even found
858 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
859 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
860 never resulted in the software showing up in Debian. So a few days
861 ago I offered my help to try to improve the situation.&lt;/p&gt;
862
863 &lt;p&gt;Now I am very happy to see that all the packages required by a
864 working Cura in Debian are uploaded into Debian and waiting in the NEW
865 queue for the ftpmasters to have a look. You can track the progress
866 on
867 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
868 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
869
870 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
871 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
872 queue&lt;/a&gt; while we work up updating the packages to the latest
873 upstream version.&lt;/p&gt;
874
875 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
876 to use and was unable to configure correctly for Ultimaker 2+ in the
877 short time I spent on it, are already in Debian. If you are looking
878 for 3D printer &quot;slicers&quot; and want something already available in
879 Debian, check out
880 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
881 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
882 The latter is a fork of the former.&lt;/p&gt;
883
884 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
885 activities, please send Bitcoin donations to my address
886 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
887 </description>
888 </item>
889
890 <item>
891 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
892 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
893 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
894 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
895 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
896 mobile cell towers. And this radio chatter is available for anyone
897 with a radio receiver capable of receiving them. Details about the
898 mobile phones with very good accuracy is of course collected by the
899 phone companies, but this is not the topic of this blog post. The
900 mobile phone radio chatter make it possible to figure out when a cell
901 phone is nearby, as it include the SIM card ID (IMSI). By paying
902 attention over time, one can see when a phone arrive and when it leave
903 an area. I believe it would be nice to make this information more
904 available to the general public, to make more people aware of how
905 their phones are announcing their whereabouts to anyone that care to
906 listen.&lt;/p&gt;
907
908 &lt;p&gt;I am very happy to report that we managed to get something
909 visualizing this information up and running for
910 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
911 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
912 library. The solution is based on the
913 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
914 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
915 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
916 Sone from the Computer Science department of the University of
917 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
918 IMSIs) as dots in a web browser graph, with lines to the dot
919 representing mobile base station it is talking to. It was working in
920 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
921
922 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
923 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
924 connected and visualize the visible cell phone towers using an
925 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
926 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
927 grgsm_livemon_headless processes from
928 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
929 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
930
931 &lt;p&gt;The frequencies to listen to, are identified using a slightly
932 patched scan-and-livemon (to set the --args values for each receiver),
933 and the Hopglass data is generated using the
934 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
935 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
936 more than four SDRs working. There is also a geographical map trying
937 to show the location of the base stations, but I believe their
938 coordinates are hardcoded to some random location in Germany, I
939 believe. The code should be replaced with code to look up location in
940 a text file, a sqlite database or one of the online databases
941 mentioned in
942 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
943 issue for the topic&lt;/a&gt;.
944
945 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
946 </description>
947 </item>
948
949 <item>
950 <title>Easier recipe to observe the cell phones around you</title>
951 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
952 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
953 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
954 <description>&lt;p&gt;A little more than a month ago I wrote
955 &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
956 to observe the SIM card ID (aka IMSI number) of mobile phones talking
957 to nearby mobile phone base stations using Debian GNU/Linux and a
958 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
959 the location of people and equipment (like cars and trains) with an
960 accuracy of a few kilometer. Since then we have worked to make the
961 procedure even simpler, and it is now possible to do this without any
962 manual frequency tuning and without building your own packages.&lt;/p&gt;
963
964 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
965 package is now included in Debian testing and unstable, and the
966 IMSI-catcher code no longer require root access to fetch and decode
967 the GSM data collected using gr-gsm.&lt;/p&gt;
968
969 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
970 clone of two python scripts:&lt;/p&gt;
971
972 &lt;ol&gt;
973
974 &lt;li&gt;Start with a Debian machine running the Buster version (aka
975 testing).&lt;/li&gt;
976
977 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
978 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
979
980 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
981 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
982
983 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
984
985 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
986 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
987 stations and start listening for GSM packages on one of them.&lt;/li&gt;
988
989 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
990 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
991
992 &lt;/ol&gt;
993
994 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
995 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
996 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
997 work with RTL 8232 and other similar USB radio receivers you can get
998 very cheaply
999 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
1000 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
1001 and only use HackRF for fetching GSM data.&lt;/p&gt;
1002
1003 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
1004 frequencies at the time, so if you are going to track and count every
1005 cell phone around you, you need to listen to all the frequencies used.
1006 To listen to several frequencies, use the --numrecv argument to
1007 scan-and-livemon to use several receivers. Further, I am not sure if
1008 phones using 3G or 4G will show as talking GSM to base stations, so
1009 this approach might not see all phones around you. I typically see
1010 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
1011
1012 &lt;p&gt;I&#39;ve tried to run the scanner on a
1013 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
1014 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
1015 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
1016 stdout, I am told there it is caused by a buffer overflow between the
1017 radio and GNU Radio, caused by the program being unable to read the
1018 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
1019 where you started scan-and-livemon, you need a give the process more
1020 CPU power. Perhaps someone are able to optimize the code to a point
1021 where it become possible to set up RPi3 based GSM sniffers? I tried
1022 using Raspbian instead of Debian, but there seem to be something wrong
1023 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
1024 </description>
1025 </item>
1026
1027 <item>
1028 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
1029 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
1030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
1031 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
1032 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
1033 web based ICT news magazine digi.no on
1034 &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
1035 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
1036 DVB-T software defined radios. The article refered to instructions
1037 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
1038 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;
1039
1040 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
1041 bypass apt), use pip to install pybombs (to bypass both apt and pip),
1042 and the ask pybombs to fetch and build everything you need from
1043 scratch. I wanted to see if I could do the same on the most recent
1044 Debian packages, but this did not work because pybombs tried to build
1045 stuff that no longer build with the most recent openssl library or
1046 some other version skew problem. While trying to get this recipe
1047 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
1048 and the only piece of software dependency missing in Debian was the
1049 gr-gsm package. I also found out that the lead upstream developer of
1050 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
1051 Debian packages provided in an Ubuntu PPA repository. All I needed to
1052 do was to dget the Debian source package and built it.&lt;/p&gt;
1053
1054 &lt;p&gt;The IMSI collector is a python script listening for packages on the
1055 loopback network device and printing to the terminal some specific GSM
1056 packages with IMSI numbers in them. The code is fairly short and easy
1057 to understand. The reason this work is because gr-gsm include a tool
1058 to read GSM data from a software defined radio like a DVB-T USB stick
1059 and other software defined radios, decode them and inject them into a
1060 network device on your Linux machine (using the loopback device by
1061 default). This proved to work just fine, and I&#39;ve been testing the
1062 collector for a few days now.&lt;/p&gt;
1063
1064 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
1065
1066 &lt;ol&gt;
1067
1068 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
1069
1070 &lt;li&gt;build and install the gr-gsm package available from
1071 &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;
1072
1073 &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;
1074
1075 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
1076 where it was started is filled with a stream of text (meaning you
1077 found a GSM station).&lt;/li&gt;
1078
1079 &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;
1080
1081 &lt;/ol&gt;
1082
1083 &lt;p&gt;To make it even easier in the future to get this sniffer up and
1084 running, I decided to package
1085 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
1086 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
1087 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
1088 Luckily the gnuradio maintainer has promised to help me, as I do not
1089 know much about gnuradio stuff yet.&lt;/p&gt;
1090
1091 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
1092 commercial tools like
1093 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
1094 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
1095 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
1096 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
1097 more people realise how their whereabouts when carrying a cell phone
1098 is easily tracked. Seeing the data flow on the screen, realizing that
1099 I live close to a police station and knowing that the police is also
1100 wearing cell phones, I wonder how hard it would be for criminals to
1101 track the position of the police officers to discover when there are
1102 police near by, or for foreign military forces to track the location
1103 of the Norwegian military forces, or for anyone to track the location
1104 of government officials...&lt;/p&gt;
1105
1106 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
1107 script mentioned above is only a fraction of the data broadcasted on
1108 the GSM network. It will only collect one frequency at the time,
1109 while a typical phone will be using several frequencies, and not all
1110 phones will be using the frequencies tracked by the grgsm_livemod
1111 program. Also, there is a lot of radio chatter being ignored by the
1112 simple_IMSI-catcher script, which would be collected by extending the
1113 parser code. I wonder if gr-gsm can be set up to listen to more than
1114 one frequency?&lt;/p&gt;
1115 </description>
1116 </item>
1117
1118 <item>
1119 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
1120 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
1121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
1122 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
1123 <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;
1124
1125 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
1126 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1127 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
1128 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
1129 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
1130 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
1131 price. The book is also available for download in electronic form as
1132 PDF, EPUB and Mobipocket, as can be
1133 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
1134 as a web page&lt;/a&gt;.&lt;/p&gt;
1135
1136 &lt;p&gt;This is the second book I publish (the first was the book
1137 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
1138 in
1139 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
1140 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
1141 and
1142 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
1143 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
1144 project. I hope
1145 &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
1146 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
1147 </description>
1148 </item>
1149
1150 <item>
1151 <title>Når nynorskoversettelsen svikter til eksamen...</title>
1152 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
1153 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
1154 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
1155 <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
1156 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
1157 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
1158 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
1159 på om den fri oversetterløsningen
1160 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
1161 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
1162
1163 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
1164
1165 &lt;blockquote&gt;
1166 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1167 rolle og muligheter til å håndtere internasjonale utfordringer, som
1168 for eksempel flykningekrisen.&lt;/p&gt;
1169
1170 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1171 på temaet:&lt;/p&gt;
1172 &lt;ol&gt;
1173 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
1174 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
1175 &lt;/ol&gt;
1176
1177 &lt;/blockquote&gt;
1178
1179 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
1180
1181 &lt;blockquote&gt;
1182 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1183 andre aktørar og høve til å handtera internasjonale utfordringar, som
1184 til dømes *flykningekrisen.&lt;/p&gt;
1185
1186 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
1187 temaet:&lt;/p&gt;
1188
1189 &lt;ol&gt;
1190 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
1191 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
1192 &lt;/ol&gt;
1193
1194 &lt;/blockquote&gt;
1195
1196 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
1197 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1198 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1199 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
1200 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
1201 det er kanskje flisespikking. Det understreker vel bare at det alltid
1202 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
1203 </description>
1204 </item>
1205
1206 <item>
1207 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
1208 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
1209 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
1210 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
1211 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
1212 computers at the time, I often needed a way to detect if the machine
1213 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
1214 file or directory affected by the hang, the process (and possibly the
1215 shell) will hang too. So you want to be able to detect this without
1216 risking the detection process getting stuck too. It has not been
1217 obvious how to do this. When the hang has lasted a while, it is
1218 possible to find messages like these in dmesg:&lt;/p&gt;
1219
1220 &lt;p&gt;&lt;blockquote&gt;
1221 nfs: server nfsserver not responding, still trying
1222 &lt;br&gt;nfs: server nfsserver OK
1223 &lt;/blockquote&gt;&lt;/p&gt;
1224
1225 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
1226 be sure looking in dmesg is going to work. If there are lots of other
1227 messages in dmesg the lines might have rotated out of site before they
1228 are noticed.&lt;/p&gt;
1229
1230 &lt;p&gt;While reading through the nfs client implementation in linux kernel
1231 code, I came across some statistics that seem to give a way to detect
1232 it. The om_timeouts sunrpc value in the kernel will increase every
1233 time the above log entry is inserted into dmesg. And after digging a
1234 bit further, I discovered that this value show up in
1235 /proc/self/mountstats on Linux.&lt;/p&gt;
1236
1237 &lt;p&gt;The mountstats content seem to be shared between files using the
1238 same file system context, so it is enough to check one of the
1239 mountstats files to get the state of the mount point for the machine.
1240 I assume this will not show lazy umounted NFS points, nor NFS mount
1241 points in a different process context (ie with a different filesystem
1242 view), but that does not worry me.&lt;/p&gt;
1243
1244 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
1245
1246 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1247 [...]
1248 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1249 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
1250 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
1251 age: 7863311
1252 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
1253 sec: flavor=1,pseudoflavor=1
1254 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
1255 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1256 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
1257 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1258 per-op statistics
1259 NULL: 0 0 0 0 0 0 0 0
1260 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1261 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
1262 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1263 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1264 READLINK: 125 125 0 20472 18620 0 1112 1118
1265 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1266 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1267 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
1268 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
1269 SYMLINK: 903 903 0 233428 245488 6 5865 5917
1270 MKNOD: 80 80 0 20148 21760 0 299 304
1271 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
1272 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
1273 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
1274 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
1275 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1276 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1277 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
1278 FSINFO: 2 2 0 232 328 0 1 1
1279 PATHCONF: 1 1 0 116 140 0 0 0
1280 COMMIT: 0 0 0 0 0 0 0 0
1281
1282 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1283 [...]
1284 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1285
1286 &lt;p&gt;The key number to look at is the third number in the per-op list.
1287 It is the number of NFS timeouts experiences per file system
1288 operation. Here 22 write timeouts and 5 access timeouts. If these
1289 numbers are increasing, I believe the machine is experiencing NFS
1290 hang. Unfortunately the timeout value do not start to increase right
1291 away. The NFS operations need to time out first, and this can take a
1292 while. The exact timeout value depend on the setup. For example the
1293 defaults for TCP and UDP mount points are quite different, and the
1294 timeout value is affected by the soft, hard, timeo and retrans NFS
1295 mount options.&lt;/p&gt;
1296
1297 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
1298 Enterprise Linux for getting the timeout count is to peek in /proc/.
1299 But according to
1300 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
1301 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
1302 command can be used to get these timeout values. But this do not work
1303 on Linux, as far as I can tell. I
1304 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
1305 but have not seen any replies yet.&lt;/p&gt;
1306
1307 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
1308 experiencing NFS hangs? Is there a way to detect which processes are
1309 affected? Is there a way to get the NFS mount going quickly once the
1310 network problem causing the NFS hang has been cleared? I would very
1311 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
1312 </description>
1313 </item>
1314
1315 <item>
1316 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
1317 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
1318 <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>
1319 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
1320 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
1321 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1322 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
1323 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1324 we are working on the proof reading to ensure consistent language and
1325 use of correct computer science terms. The plan is to make the book
1326 available on paper, as well as in electronic form. For that to
1327 happen, the proof reading must be completed and all the figures need
1328 to be translated. If you want to help out, get in touch.&lt;/p&gt;
1329
1330 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
1331
1332 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
1333 pages) of the book created every morning is available for
1334 proofreading. If you find any errors, please
1335 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
1336 Weblate and correct the error&lt;/a&gt;. The
1337 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
1338 of the translation including figures&lt;/a&gt; is a useful source for those
1339 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
1340 </description>
1341 </item>
1342
1343 <item>
1344 <title>Unlimited randomness with the ChaosKey?</title>
1345 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
1346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
1347 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
1348 <description>&lt;p&gt;A few days ago I ordered a small batch of
1349 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
1350 USB dongle for generating entropy created by Bdale Garbee and Keith
1351 Packard. Yesterday it arrived, and I am very happy to report that it
1352 work great! According to its designers, to get it to work out of the
1353 box, you need the Linux kernel version 4.1 or later. I tested on a
1354 Debian Stretch machine (kernel version 4.9), and there it worked just
1355 fine, increasing the available entropy very quickly. I wrote a small
1356 test oneliner to test. It first print the current entropy level,
1357 drain /dev/random, and then print the entropy level for five seconds.
1358 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
1359
1360 &lt;blockquote&gt;&lt;pre&gt;
1361 % cat /proc/sys/kernel/random/entropy_avail; \
1362 dd bs=1M if=/dev/random of=/dev/null count=1; \
1363 for n in $(seq 1 5); do \
1364 cat /proc/sys/kernel/random/entropy_avail; \
1365 sleep 1; \
1366 done
1367 300
1368 0+1 oppføringer inn
1369 0+1 oppføringer ut
1370 28 byte kopiert, 0,000264565 s, 106 kB/s
1371 4
1372 8
1373 12
1374 17
1375 21
1376 %
1377 &lt;/pre&gt;&lt;/blockquote&gt;
1378
1379 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
1380 application requiring random bits (like a HTTPS enabled web server)
1381 will halt and wait for more entrpy. And here is the situation with
1382 the ChaosKey inserted:&lt;/p&gt;
1383
1384 &lt;blockquote&gt;&lt;pre&gt;
1385 % cat /proc/sys/kernel/random/entropy_avail; \
1386 dd bs=1M if=/dev/random of=/dev/null count=1; \
1387 for n in $(seq 1 5); do \
1388 cat /proc/sys/kernel/random/entropy_avail; \
1389 sleep 1; \
1390 done
1391 1079
1392 0+1 oppføringer inn
1393 0+1 oppføringer ut
1394 104 byte kopiert, 0,000487647 s, 213 kB/s
1395 433
1396 1028
1397 1031
1398 1035
1399 1038
1400 %
1401 &lt;/pre&gt;&lt;/blockquote&gt;
1402
1403 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
1404 someone want to buy one here in Norway. :)&lt;/p&gt;
1405
1406 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
1407 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
1408 recording illuminating&lt;/a&gt;. It explains exactly what the source of
1409 randomness is, if you are unable to spot it from the schema drawing
1410 available from the ChaosKey web site linked at the start of this blog
1411 post.&lt;/p&gt;
1412 </description>
1413 </item>
1414
1415 <item>
1416 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
1417 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
1418 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
1419 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
1420 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
1421 web servers, and who own the network equipment it is flowing through?
1422 It is possible to get a glimpse of this from using traceroute, but it
1423 is hard to find all the details. Many years ago, I wrote a system to
1424 map the Norwegian Internet (trying to figure out if our plans for a
1425 network game service would get low enough latency, and who we needed
1426 to talk to about setting up game servers close to the users. Back
1427 then I used traceroute output from many locations (I asked my friends
1428 to run a script and send me their traceroute output) to create the
1429 graph and the map. The output from traceroute typically look like
1430 this:
1431
1432 &lt;p&gt;&lt;pre&gt;
1433 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
1434 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
1435 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
1436 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
1437 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
1438 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
1439 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
1440 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
1441 8 * * *
1442 9 * * *
1443 [...]
1444 &lt;/pre&gt;&lt;/p&gt;
1445
1446 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
1447 network equipment involved in getting the data traffic from me to the
1448 www.stortinget.no server, and how long it took in milliseconds for a
1449 package to reach the equipment and return to me. Three packages are
1450 sent, and some times the packages do not follow the same path. This
1451 is shown for hop 5, where three different IP addresses replied to the
1452 traceroute request.&lt;/p&gt;
1453
1454 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
1455 implementations I use are traceroute (using ICMP packages) mtr (can do
1456 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1457 traceroute and a lot of other capabilities). All of them are easily
1458 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
1459
1460 &lt;p&gt;This time around, I wanted to know the geographic location of
1461 different route points, to visualize how visiting a web page spread
1462 information about the visit to a lot of servers around the globe. The
1463 background is that a web site today often will ask the browser to get
1464 from many servers the parts (for example HTML, JSON, fonts,
1465 JavaScript, CSS, video) required to display the content. This will
1466 leak information about the visit to those controlling these servers
1467 and anyone able to peek at the data traffic passing by (like your ISP,
1468 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
1469
1470 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
1471 www.stortinget.no. It is read daily by all members of parliament and
1472 their staff, as well as political journalists, activits and many other
1473 citizens of Norway. A visit to the www.stortinget.no web site will
1474 ask your browser to contact 8 other servers: ajax.googleapis.com,
1475 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1476 stats.g.doubleclick.net, www.google-analytics.com,
1477 www.googletagmanager.com and www.netigate.se. I extracted this by
1478 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
1479 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1480 render the page (in HAR format using
1481 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
1482 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
1483 to do this). My goal is to visualize network traces to all IP
1484 addresses behind these DNS names, do show where visitors personal
1485 information is spread when visiting the page.&lt;/p&gt;
1486
1487 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
1488 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;
1489
1490 &lt;p&gt;When I had a look around for options, I could not find any good
1491 free software tools to do this, and decided I needed my own traceroute
1492 wrapper outputting KML based on locations looked up using GeoIP. KML
1493 is easy to work with and easy to generate, and understood by several
1494 of the GIS tools I have available. I got good help from by NUUG
1495 colleague Anders Einar with this, and the result can be seen in
1496 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
1497 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
1498 free GeoIP databases I could find (and the for-pay databases my
1499 friends had access to) is not up to the task. The IP addresses of
1500 central Internet infrastructure would typically be placed near the
1501 controlling companies main office, and not where the router is really
1502 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
1503 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
1504
1505 &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
1506 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;
1507
1508 &lt;p&gt;I also had a look at the visual traceroute graph created by
1509 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1510 showing IP network ownership (aka AS owner) for the IP address in
1511 question.
1512 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1513 graph display a lot of useful information about the traceroute in SVG
1514 format&lt;/a&gt;, and give a good indication on who control the network
1515 equipment involved, but it do not include geolocation. This graph
1516 make it possible to see the information is made available at least for
1517 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1518 3 Communications and NetDNA.&lt;/p&gt;
1519
1520 &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
1521 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;
1522
1523 &lt;p&gt;In the process, I came across the
1524 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1525 Salim Gasmi. Its methology of combining guesses based on DNS names,
1526 various location databases and finally use latecy times to rule out
1527 candidate locations seemed to do a very good job of guessing correct
1528 geolocation. But it could only do one trace at the time, did not have
1529 a sensor in Norway and did not make the geolocations easily available
1530 for postprocessing. So I contacted the developer and asked if he
1531 would be willing to share the code (he refused until he had time to
1532 clean it up), but he was interested in providing the geolocations in a
1533 machine readable format, and willing to set up a sensor in Norway. So
1534 since yesterday, it is possible to run traces from Norway in this
1535 service thanks to a sensor node set up by
1536 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1537 trace in KML format for further processing.&lt;/p&gt;
1538
1539 &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
1540 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;
1541
1542 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1543 Denmark, Germany, Holland and Ireland. Plenty of places where the
1544 Snowden confirmations verified the traffic is read by various actors
1545 without your best interest as their top priority.&lt;/p&gt;
1546
1547 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1548 over all the hosts behind the urls imported by www.stortinget.no and
1549 ask for the KML file from GeoTraceroute, and create a combined KML
1550 file with all the traces (unfortunately only one of the IP addresses
1551 behind the DNS name is traced this time. To get them all, one would
1552 have to request traces using IP number instead of DNS names from
1553 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1554
1555 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1556 the IP traffic moves and who control the boxes involved in moving it.
1557 And every time the link crosses for example the Swedish border, we can
1558 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1559 Britain and NSA in USA and cables around the globe. (Hm, what should
1560 we tell them? :) Keep that in mind if you ever send anything
1561 unencrypted over the Internet.&lt;/p&gt;
1562
1563 &lt;p&gt;PS: KML files are drawn using
1564 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1565 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1566 Marble. There are heaps of other options too.&lt;/p&gt;
1567
1568 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1569 activities, please send Bitcoin donations to my address
1570 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1571 </description>
1572 </item>
1573
1574 <item>
1575 <title>Appstream just learned how to map hardware to packages too!</title>
1576 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1577 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1578 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1579 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1580 readers probably know, I have been working on the
1581 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1582 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1583 it easier for users to figure out what to install to get a given piece
1584 of hardware to work in Debian, and a key part of this system is a way
1585 to map hardware to packages. Isenkram have its own mapping database,
1586 and also uses data provided by each package using the AppStream
1587 metadata format. And today,
1588 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1589 Debian learned to look up hardware the same way Isenkram is doing it,
1590 ie using fnmatch():&lt;/p&gt;
1591
1592 &lt;p&gt;&lt;pre&gt;
1593 % appstreamcli what-provides modalias \
1594 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1595 Identifier: pymissile [generic]
1596 Name: pymissile
1597 Summary: Control original Striker USB Missile Launcher
1598 Package: pymissile
1599 % appstreamcli what-provides modalias usb:v0694p0002d0000
1600 Identifier: libnxt [generic]
1601 Name: libnxt
1602 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1603 Package: libnxt
1604 ---
1605 Identifier: t2n [generic]
1606 Name: t2n
1607 Summary: Simple command-line tool for Lego NXT
1608 Package: t2n
1609 ---
1610 Identifier: python-nxt [generic]
1611 Name: python-nxt
1612 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1613 Package: python-nxt
1614 ---
1615 Identifier: nbc [generic]
1616 Name: nbc
1617 Summary: C compiler for LEGO Mindstorms NXT bricks
1618 Package: nbc
1619 %
1620 &lt;/pre&gt;&lt;/p&gt;
1621
1622 &lt;p&gt;A similar query can be done using the combined AppStream and
1623 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1624
1625 &lt;p&gt;&lt;pre&gt;
1626 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1627 pymissile
1628 % isenkram-lookup usb:v0694p0002d0000
1629 libnxt
1630 nbc
1631 python-nxt
1632 t2n
1633 %
1634 &lt;/pre&gt;&lt;/p&gt;
1635
1636 &lt;p&gt;You can find modalias values relevant for your machine using
1637 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1638
1639 &lt;p&gt;If you want to make this system a success and help Debian users
1640 make the most of the hardware they have, please
1641 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1642 AppStream metadata for your package following the guidelines&lt;/a&gt;
1643 documented in the wiki. So far only 11 packages provide such
1644 information, among the several hundred hardware specific packages in
1645 Debian. The Isenkram database on the other hand contain 101 packages,
1646 mostly related to USB dongles. Most of the packages with hardware
1647 mapping in AppStream are LEGO Mindstorms related, because I have, as
1648 part of my involvement in
1649 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1650 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1651 complete set of packages in Debian for that particular hardware. The
1652 team also got a nice Christmas present today. The
1653 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1654 package&lt;/a&gt; made it into Debian. With this package in place, it is
1655 now possible to use the LEGO Mindstorms NXT unit with only free
1656 software, as the nxt-firmware package contain the source and firmware
1657 binaries for the NXT brick.&lt;/p&gt;
1658
1659 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1660 activities, please send Bitcoin donations to my address
1661 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1662 </description>
1663 </item>
1664
1665 <item>
1666 <title>Isenkram updated with a lot more hardware-package mappings</title>
1667 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1668 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1669 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1670 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1671 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1672 and install packages to get your hardware dongles to work, is still
1673 going strong. It is a system to look up the hardware present on or
1674 connected to the current system, and map the hardware to Debian
1675 packages. It can either be done using the tools in isenkram-cli or
1676 using the user space daemon in the isenkram package. The latter will
1677 notify you, when inserting new hardware, about what packages to
1678 install to get the dongle working. It will even provide a button to
1679 click on to ask packagekit to install the packages.&lt;/p&gt;
1680
1681 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1682
1683 &lt;p&gt;&lt;pre&gt;
1684 % isenkram-lookup
1685 bluez
1686 cheese
1687 ethtool
1688 fprintd
1689 fprintd-demo
1690 gkrellm-thinkbat
1691 hdapsd
1692 libpam-fprintd
1693 pidgin-blinklight
1694 thinkfan
1695 tlp
1696 tp-smapi-dkms
1697 tp-smapi-source
1698 tpb
1699 %
1700 &lt;/pre&gt;&lt;/p&gt;
1701
1702 &lt;p&gt;It can also list the firware package providing firmware requested
1703 by the load kernel modules, which in my case is an empty list because
1704 I have all the firmware my machine need:
1705
1706 &lt;p&gt;&lt;pre&gt;
1707 % /usr/sbin/isenkram-autoinstall-firmware -l
1708 info: did not find any firmware files requested by loaded kernel modules. exiting
1709 %
1710 &lt;/pre&gt;&lt;/p&gt;
1711
1712 &lt;p&gt;The last few days I had a look at several of the around 250
1713 packages in Debian with udev rules. These seem like good candidates
1714 to install when a given hardware dongle is inserted, and I found
1715 several that should be proposed by isenkram. I have not had time to
1716 check all of them, but am happy to report that now there are 97
1717 packages packages mapped to hardware by Isenkram. 11 of these
1718 packages provide hardware mapping using AppStream, while the rest are
1719 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1720
1721 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1722 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1723 support using AppStream, for everyone to use:&lt;/p&gt;
1724
1725 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1726 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1727 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1728 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1729 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1730 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1731 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1732 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1733 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1734 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1735 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1736 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1737 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1738 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1739 pcscd, pidgin-blinklight, printer-driver-splix,
1740 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1741 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1742 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1743 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1744 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1745 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1746 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1747 xserver-xorg-video-vmware, yubikey-personalization and
1748 zd1211-firmware&lt;/p&gt;
1749
1750 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1751 bug report against the isenkram-cli package, and ask the package
1752 maintainer to
1753 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1754 metadata according to the guidelines&lt;/a&gt; to provide the information
1755 for everyone. In time, I hope to get rid of the isenkram specific
1756 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1757
1758 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1759 much hardware, and suggest that the package with with any ethernet
1760 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1761 the details. I hope the maintainer find time to address it soon. In
1762 the mean time I provide an override in isenkram.&lt;/p&gt;
1763 </description>
1764 </item>
1765
1766 <item>
1767 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1768 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1770 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1771 <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;
1772
1773 &lt;p&gt;In my early years, I played
1774 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1775 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1776 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1777 original Elite game was available on Commodore 64 and the IBM PC
1778 edition I played had a 64 KB executable. I am still impressed today
1779 that the authors managed to squeeze both a 3D engine and details about
1780 more than 2000 planet systems across 7 galaxies into a binary so
1781 small.&lt;/p&gt;
1782
1783 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1784 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1785 really have time to test it properly until a few days ago. It was
1786 great to discover that my old knowledge about trading routes were
1787 still valid. But my fighting and flying abilities were gone, so I had
1788 to retrain to be able to dock on a space station. And I am still not
1789 able to make much resistance when I am attacked by pirates, so I
1790 bougth and mounted the most powerful laser in the rear to be able to
1791 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1792
1793 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1794 everything on my own, and I had long lists of prices seen on different
1795 planets to be able to decide where to trade what. This time I had the
1796 advantages of the
1797 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1798 where information about each planet is easily available with common
1799 price ranges and suggested trading routes. This improved my ability
1800 to earn money and I have been able to earn enough to buy a lot of
1801 useful equipent in a few days. I believe I originally played for
1802 months before I could get a docking computer, while now I could get it
1803 after less then a week.&lt;/p&gt;
1804
1805 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1806 space, you should try out Oolite. It is available for Linux, MacOSX
1807 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1808
1809 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1810 activities, please send Bitcoin donations to my address
1811 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1812 </description>
1813 </item>
1814
1815 <item>
1816 <title>Quicker Debian installations using eatmydata</title>
1817 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1818 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1819 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1820 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1821 installation system, observing how using
1822 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1823 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1824 speedup around 20-40 percent for Debian Edu, where we install around
1825 1000 packages from within the installer. The eatmydata package
1826 provide a way to disable/delay file system flushing. This is a bit
1827 risky in the general case, as files that should be stored on disk will
1828 stay only in memory a bit longer than expected, causing problems if a
1829 machine crashes at an inconvenient time. But for an installation, if
1830 the machine crashes during installation the process is normally
1831 restarted, and avoiding disk operations as much as possible to speed
1832 up the process make perfect sense.
1833
1834 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1835 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1836 but did not have time to push it any further. But a few months ago I
1837 picked it up again and worked with the libeatmydata package maintainer
1838 Mattia Rizzolo to make it easier for everyone to get this installation
1839 speedup in Debian. Thanks to our cooperation There is now an
1840 eatmydata-udeb package in Debian testing and unstable, and simply
1841 enabling/installing it in debian-installer (d-i) is enough to get the
1842 quicker installations. It can be enabled using preseeding. The
1843 following untested kernel argument should do the trick:&lt;/p&gt;
1844
1845 &lt;blockquote&gt;&lt;pre&gt;
1846 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1847 &lt;/pre&gt;&lt;/blockquote&gt;
1848
1849 &lt;p&gt;This should ask d-i to install the package inside the d-i
1850 environment early in the installation sequence. Having it installed
1851 in d-i in turn will make sure the relevant scripts are called just
1852 after debootstrap filled /target/ with the freshly installed Debian
1853 system to configure apt to run dpkg with eatmydata. This is enough to
1854 speed up the installation process. There is a proposal to
1855 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1856 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1857 tested its impact.&lt;/p&gt;
1858
1859 </description>
1860 </item>
1861
1862 <item>
1863 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1864 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1866 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1867 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1868 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1869 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1870 elever over det ganske land skal levere inn hvert år. Det mange ikke
1871 vet er at selv om de kommersielle alternativene
1872 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1873 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1874 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1875 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1876 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1877 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1878 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1879 nynorsk, og få den automatoversatt til det andre skriftspråket.
1880 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1881 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1882 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1883 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1884 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1885 teksten din i webskjemaet der.
1886
1887 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1888 teknologien kan du enten installere pakken
1889 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1890 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1891 api.apertium.org. Se
1892 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1893 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1894 denne teksten som ble skrevet på bokmål over maskinoversatt til
1895 nynorsk.&lt;/p&gt;
1896
1897 &lt;hr/&gt;
1898
1899 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1900 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1901 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1902 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1903 veit er at sjølv om dei kommersielle alternativa
1904 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1905 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1906 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1907 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1908 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1909 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1910 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1911 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1912 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1913 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1914 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1915 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1916 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1917 teksta di i *webskjemaet der.
1918
1919 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1920 teknologien kan du anten installera pakken
1921 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1922 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1923 *api.*apertium.org. Sjå
1924 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1925 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1926 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1927 nynorsk.&lt;/p&gt;
1928 </description>
1929 </item>
1930
1931 <item>
1932 <title>Coz profiler for multi-threaded software is now in Debian</title>
1933 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1934 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1935 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1936 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1937 profiler able to run benchmarking experiments on the instrumented
1938 multi-threaded program, finally
1939 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1940 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1941 months since
1942 &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
1943 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1944 it suitable for Debian. There are still issues with clang
1945 compatibility, inline assembly only working x86 and minimized
1946 JavaScript libraries.&lt;/p&gt;
1947
1948 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1949
1950 &lt;p&gt;&lt;blockquote&gt;
1951 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1952 &lt;/blockquote&gt;&lt;/p&gt;
1953
1954 &lt;p&gt;This will produce a profile.coz file in the current working
1955 directory with the profiling information. This is then given to a
1956 JavaScript application provided in the package and available from
1957 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1958 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1959
1960 &lt;p&gt;&lt;blockquote&gt;
1961 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1962 &lt;/blockquote&gt;&lt;/p&gt;
1963
1964 &lt;p&gt;See the project home page and the
1965 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1966 ;login: article on Coz&lt;/a&gt; for more information on how it is
1967 working.&lt;/p&gt;
1968 </description>
1969 </item>
1970
1971 <item>
1972 <title>My own self balancing Lego Segway</title>
1973 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1975 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1976 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1977 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1978 present. It had been on my wishlist for a while, because I wanted to
1979 build a Segway like balancing lego robot. I had already built
1980 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1981 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1982 NXT kit as the balance sensor, but it was not working very well. It
1983 could balance for a while, but was very sensitive to the light
1984 condition in the room and the reflective properties of the surface and
1985 would fall over after a short while. I wanted something more robust,
1986 and had
1987 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1988 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1989 wishlist for some years before it suddenly showed up as a gift from my
1990 loved ones. :)&lt;/p&gt;
1991
1992 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1993 since then. But that changed some days ago, when I was searching for
1994 lego segway information and came across a recipe from HiTechnic for
1995 building
1996 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1997 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1998 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1999 code&lt;/a&gt; was included, so it was just a question of putting it all
2000 together. And thanks to the great work of many Debian developers, the
2001 compiler needed to build the source for the NXT is already included in
2002 Debian, so I was read to go in less than an hour. The resulting robot
2003 do not look very impressive in its simplicity:&lt;/p&gt;
2004
2005 &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;
2006
2007 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
2008 design from HiTechnic, I had to comment out the last task
2009 (taskControl). I simply placed /* and */ around it get the program
2010 working without that sensor present. Now it balances just fine until
2011 the battery status run low:&lt;/p&gt;
2012
2013 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
2014 &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;
2015 &lt;/video&gt;&lt;/p&gt;
2016
2017 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
2018 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
2019
2020 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
2021 they need to work with LEGO in Debian and all our derivative
2022 distributions like Ubuntu, check out
2023 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
2024 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
2025 RCX and NXT controller (no EV3), and would like to make sure the
2026 Debian tools needed to program the systems I own work as they
2027 should.&lt;/p&gt;
2028 </description>
2029 </item>
2030
2031 <item>
2032 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
2033 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
2034 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
2035 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
2036 <description>&lt;p&gt;In July
2037 &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
2038 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
2039 the ability to receive SMS messages (aka without a cell phone). It is
2040 time to share some experiences and provide an updated setup.&lt;/p&gt;
2041
2042 &lt;p&gt;The Signal app have worked fine for several months now, and I use
2043 it regularly to chat with my loved ones. I had a major snag at the
2044 end of my summer vacation, when the the app completely forgot my
2045 setup, identity and keys. The reason behind this major mess was
2046 running out of disk space. To avoid that ever happening again I have
2047 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
2048 roll back to an earlier version if the files are wiped by mistake. I
2049 had to use it once after introducing the git backup. When rolling
2050 back to an earlier version, one need to use the &#39;reset session&#39; option
2051 in Signal to get going, and notify the people you talk with about the
2052 problem. I assume there is some sequence number tracking in the
2053 protocol to detect rollback attacks. The git repository is rather big
2054 (674 MiB so far), but I have not tried to figure out if some of the
2055 content can be added to a .gitignore file due to lack of spare
2056 time.&lt;/p&gt;
2057
2058 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
2059 make it impossible to send messages using Signal. I could still
2060 receive them, but had to patch the code with a new timestamp to send.
2061 I believe the timeout is added by the developers to force people to
2062 upgrade to the latest version of the app, even when there is no
2063 protocol changes, to reduce the version skew among the user base and
2064 thus try to keep the number of support requests down.&lt;/p&gt;
2065
2066 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
2067 making the old patch fail to apply cleanly. Below is an updated
2068 patch, including the shell wrapper I use to start Signal. The
2069 original version required a new user to locate the JavaScript console
2070 and call a function from there. I got help from a friend with more
2071 JavaScript knowledge than me to modify the code to provide a GUI
2072 button instead. This mean that to get started you just need to run
2073 the wrapper and click the &#39;Register without mobile phone&#39; to get going
2074 now. I&#39;ve also modified the timeout code to always set it to 90 days
2075 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
2076
2077 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
2078
2079 &lt;ol&gt;
2080
2081 &lt;li&gt;First, install required packages to get the source code and the
2082 browser you need. Signal only work with Chrome/Chromium, as far as I
2083 know, so you need to install it.
2084
2085 &lt;pre&gt;
2086 apt install git tor chromium
2087 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2088 &lt;/pre&gt;&lt;/li&gt;
2089
2090 &lt;li&gt;Modify the source code using command listed in the the patch
2091 block below.&lt;/li&gt;
2092
2093 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
2094 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
2095
2096 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
2097 number you can receive calls to the next minute, receive the
2098 verification code and enter it into the form field and press
2099 &#39;Register&#39;. Note, the phone number you use will be user Signal
2100 username, ie the way others can find you on Signal.&lt;/li&gt;
2101
2102 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
2103 not show up in the contact list until you restart Signal, and there is
2104 no way to assign names to Contacts. There is also no way to create or
2105 update chat groups. I suspect this is because the web app do not have
2106 a associated contact database.&lt;/li&gt;
2107
2108 &lt;/ol&gt;
2109
2110 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
2111 main author moxie0 reject federation and accept dependencies to major
2112 corporations like Google (part of the code is fetched from Google) and
2113 Amazon (the central coordination point is owned by Amazon). See for
2114 example
2115 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
2116 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
2117 view on these issues. But the network effect is strong in this case,
2118 and several of the people I want to communicate with already use
2119 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
2120 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
2121 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
2122 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
2123 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
2124 working on Debian Stable.&lt;/p&gt;
2125
2126 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
2127 working. It switch to the production servers, disable to timeout,
2128 make registration easier and add the shell wrapper:&lt;/p&gt;
2129
2130 &lt;pre&gt;
2131 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
2132 diff --git a/js/background.js b/js/background.js
2133 index 24b4c1d..579345f 100644
2134 --- a/js/background.js
2135 +++ b/js/background.js
2136 @@ -33,9 +33,9 @@
2137 });
2138 });
2139
2140 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2141 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
2142 var SERVER_PORTS = [80, 4433, 8443];
2143 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2144 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2145 var messageReceiver;
2146 window.getSocketStatus = function() {
2147 if (messageReceiver) {
2148 diff --git a/js/expire.js b/js/expire.js
2149 index 639aeae..beb91c3 100644
2150 --- a/js/expire.js
2151 +++ b/js/expire.js
2152 @@ -1,6 +1,6 @@
2153 ;(function() {
2154 &#39;use strict&#39;;
2155 - var BUILD_EXPIRATION = 0;
2156 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
2157
2158 window.extension = window.extension || {};
2159
2160 diff --git a/js/views/install_view.js b/js/views/install_view.js
2161 index 7816f4f..1d6233b 100644
2162 --- a/js/views/install_view.js
2163 +++ b/js/views/install_view.js
2164 @@ -38,7 +38,8 @@
2165 return {
2166 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
2167 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
2168 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
2169 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
2170 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
2171 };
2172 },
2173 clearQR: function() {
2174 diff --git a/options.html b/options.html
2175 index dc0f28e..8d709f6 100644
2176 --- a/options.html
2177 +++ b/options.html
2178 @@ -14,7 +14,10 @@
2179 &amp;lt;div class=&#39;nav&#39;&gt;
2180 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
2181 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
2182 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
2183 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
2184 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
2185 +
2186 + &amp;lt;/div&gt;
2187 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
2188 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
2189 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
2190 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
2191 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
2192 @@ -0,0 +1,12 @@
2193 +#!/bin/sh
2194 +set -e
2195 +cd $(dirname $0)
2196 +mkdir -p userdata
2197 +userdata=&quot;`pwd`/userdata&quot;
2198 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
2199 + (cd $userdata &amp;&amp; git init)
2200 +fi
2201 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
2202 +exec chromium \
2203 + --proxy-server=&quot;socks://localhost:9050&quot; \
2204 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2205 EOF
2206 chmod a+rx run-signal-app
2207 &lt;/pre&gt;
2208
2209 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2210 activities, please send Bitcoin donations to my address
2211 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2212 </description>
2213 </item>
2214
2215 <item>
2216 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
2217 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
2218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
2219 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
2220 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2221 system&lt;/a&gt; provide a practical and easy way to figure out which
2222 packages support the hardware in a given machine. The command line
2223 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
2224 convenient way to list and install packages relevant for the current
2225 hardware during system installation, both user space packages and
2226 firmware packages. The GUI background daemon on the other hand provide
2227 a pop-up proposing to install packages when a new dongle is inserted
2228 while using the computer. For example, if you plug in a smart card
2229 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
2230 that package isn&#39;t already installed, and if you plug in a USB video
2231 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
2232 cheese is currently missing. This already work just fine.&lt;/p&gt;
2233
2234 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
2235 package names. When I started no such database existed in Debian, so
2236 I made my own data set and included it with the isenkram package and
2237 made isenkram fetch the latest version of this database from git using
2238 http. This way the isenkram users would get updated package proposals
2239 as soon as I learned more about hardware related packages.&lt;/p&gt;
2240
2241 &lt;p&gt;The hardware is identified using modalias strings. The modalias
2242 design is from the Linux kernel where most hardware descriptors are
2243 made available as a strings that can be matched using filename style
2244 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2245 identifiers.&lt;/p&gt;
2246
2247 &lt;p&gt;The downside to the Isenkram specific database is that there is no
2248 information about relevant distribution / Debian version, making
2249 isenkram propose obsolete packages too. But along came AppStream, a
2250 cross distribution mechanism to store and collect metadata about
2251 software packages. When I heard about the proposal, I contacted the
2252 people involved and suggested to add a hardware matching rule using
2253 modalias strings in the specification, to be able to use AppStream for
2254 mapping hardware to packages. This idea was accepted and AppStream is
2255 now a great way for a package to announce the hardware it support in a
2256 distribution neutral way. I wrote
2257 &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
2258 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
2259 December. If you have a hardware related package in Debian, please
2260 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
2261
2262 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
2263 RCX or NXT unit, announce this support using AppStream. The effect is
2264 that when you insert such LEGO robot controller into your Debian
2265 machine, Isenkram will propose to install the packages needed to get
2266 it working. The intention is that this should allow the local user to
2267 start programming his robot controller right away without having to
2268 guess what packages to use or which permissions to fix.&lt;/p&gt;
2269
2270 &lt;p&gt;But when I sat down with my son the other day to program our NXT
2271 unit using his Debian Stretch computer, I discovered something
2272 annoying. The local console user (ie my son) did not get access to
2273 the USB device for programming the unit. This used to work, but no
2274 longer in Jessie and Stretch. After some investigation and asking
2275 around on #debian-devel, I discovered that this was because udev had
2276 changed the mechanism used to grant access to local devices. The
2277 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
2278 no longer applied, because LDAP users no longer was added to the
2279 plugdev group during login. Michael Biebl told me that this method
2280 was obsolete and the new method used ACLs instead. This was good
2281 news, as the plugdev mechanism is a mess when using a remote user
2282 directory like LDAP. Using ACLs would make sure a user lost device
2283 access when she logged out, even if the user left behind a background
2284 process which would retain the plugdev membership with the ConsoleKit
2285 setup. Armed with this knowledge I moved on to fix the access problem
2286 for the LEGO Mindstorms related packages.&lt;/p&gt;
2287
2288 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
2289 applied directly for a device, or is applied in
2290 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
2291 LEGO Mindstorms udev rules did not have a class, I decided to add the
2292 tag directly in the udev rules files included in the packages. Here
2293 is one example. For the nqc C compiler for the RCX, the
2294 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
2295
2296 &lt;p&gt;&lt;pre&gt;
2297 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
2298 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
2299 &lt;/pre&gt;&lt;/p&gt;
2300
2301 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
2302 packages using plugdev in their /lib/udev/rules.d/ files should be
2303 changed to use this tag (either directly or indirectly via
2304 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
2305 to detect this?&lt;/p&gt;
2306
2307 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
2308 It is unclear to me if the uaccess tag is an internal implementation
2309 detail like the udev-acl tag used by
2310 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
2311 indirect method is the preferred way. Michael
2312 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
2313 documentation from the systemd project&lt;/a&gt; and I hope it will make
2314 this clearer. For now I use the generic classes when they exist and
2315 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
2316 directly if no such class exist.&lt;/p&gt;
2317
2318 &lt;p&gt;To learn more about the isenkram system, please check out
2319 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2320 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2321
2322 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
2323 please join us on our IRC channel
2324 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
2325 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
2326 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
2327 list is not yet created, but we are working on it. :)&lt;/p&gt;
2328
2329 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2330 activities, please send Bitcoin donations to my address
2331 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2332 </description>
2333 </item>
2334
2335 <item>
2336 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
2337 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
2338 <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>
2339 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
2340 <description>&lt;p&gt;In April we
2341 &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
2342 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
2343 how to set up and administrate a Debian system. Today I am happy to
2344 report that the first draft is now publicly available. You can find
2345 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
2346 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
2347 eight chapters have a first draft translation, and we are working on
2348 proofreading the content. If you want to help out, please start
2349 contributing using
2350 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2351 hosted weblate project page&lt;/a&gt;, and get in touch using
2352 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2353 translators mailing list&lt;/a&gt;. Please also check out
2354 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2355 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
2356 and update weblate if you find errors.&lt;/p&gt;
2357
2358 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
2359 electronic form.&lt;/p&gt;
2360 </description>
2361 </item>
2362
2363 <item>
2364 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
2365 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
2366 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
2367 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
2368 <description>&lt;p&gt;This summer, I read a great article
2369 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
2370 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
2371 how to profile multi-threaded programs. It presented a system for
2372 profiling software by running experiences in the running program,
2373 testing how run time performance is affected by &quot;speeding up&quot; parts of
2374 the code to various degrees compared to a normal run. It does this by
2375 slowing down parallel threads while the &quot;faster up&quot; code is running
2376 and measure how this affect processing time. The processing time is
2377 measured using probes inserted into the code, either using progress
2378 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2379 can also measure unmodified code by measuring complete the program
2380 runtime and running the program several times instead.&lt;/p&gt;
2381
2382 &lt;p&gt;The project and presentation was so inspiring that I would like to
2383 get the system into Debian. I
2384 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
2385 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
2386 system ready for Debian by sending patches. The build process need to
2387 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
2388 to include the JavaScript web page used to visualize the collected
2389 profiling information included in the source package.
2390 But I expect that should work out fairly soon.&lt;/p&gt;
2391
2392 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
2393 on a binary with debug symbols available, start the program like this:
2394
2395 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2396 coz run --- program-to-run
2397 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2398
2399 &lt;p&gt;This will create a text file profile.coz with the instrumentation
2400 information. To show what part of the code affect the performance
2401 most, use a web browser and either point it to
2402 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
2403 or use the copy from git (in the gh-pages branch). Check out this web
2404 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
2405 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
2406 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2407 code, rebuild and run the profiler. This allow coz to do more
2408 targeted experiments.&lt;/p&gt;
2409
2410 &lt;p&gt;A video published by ACM
2411 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
2412 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
2413 from the 25th Symposium on Operating Systems Principles available
2414 titled
2415 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
2416 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
2417
2418 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
2419 for Coz is available from github. It will only build with clang
2420 because it uses a
2421 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
2422 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
2423 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
2424 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
2425
2426 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
2427 of software in Debian. I would very much like some help with the
2428 packaging effort, as I lack the in depth knowledge on how to package
2429 C++ libraries.&lt;/p&gt;
2430 </description>
2431 </item>
2432
2433 <item>
2434 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
2435 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
2436 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
2437 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
2438 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2439 to be a slight challenge. Here is the recipe if I ever need to do it
2440 again. It all started by me wanting to try the recipe to set up
2441 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
2442 hardened Android installation&lt;/a&gt; from the Tor project blog on a
2443 device I had access to. It is a old mobile phone with a broken
2444 microphone The initial idea had been to just
2445 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
2446 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
2447 until a few days ago.&lt;/p&gt;
2448
2449 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
2450 loader (press volume down and power at the same time), (2) select
2451 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
2452 machine, (4) request the device identifier token by running &#39;fastboot
2453 oem get_identifier_token&#39;, (5) request the device unlocking key using
2454 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
2455 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
2456
2457 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
2458 or newer, and the device I was working on had 2.00.0027. This
2459 apparently can be easily fixed by downloading a Windows program and
2460 running it on your Windows machine, if you accept the terms Microsoft
2461 require you to accept to use Windows - which I do not. So I had to
2462 come up with a different approach. I got a lot of help from AndyCap
2463 on #nuug, and would not have been able to get this working without
2464 him.&lt;/p&gt;
2465
2466 &lt;p&gt;First I needed to extract the hboot firmware from
2467 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
2468 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
2469 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
2470 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
2471 recognise the file format, but unruu worked and extracted rom.zip,
2472 containing the new hboot firmware and a text file describing which
2473 devices it would work for.&lt;/p&gt;
2474
2475 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
2476 followed some instructions
2477 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
2478 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
2479 machine with Debian testing:&lt;/p&gt;
2480
2481 &lt;p&gt;&lt;pre&gt;
2482 adb reboot-bootloader
2483 fastboot oem rebootRUU
2484 fastboot flash zip rom.zip
2485 fastboot flash zip rom.zip
2486 fastboot reboot
2487 &lt;/pre&gt;&lt;/p&gt;
2488
2489 &lt;p&gt;The flash command apparently need to be done twice to take effect,
2490 as the first is just preparations and the second one do the flashing.
2491 The adb command is just to get to the boot loader menu, so turning the
2492 device on while holding volume down and the power button should work
2493 too.&lt;/p&gt;
2494
2495 &lt;p&gt;With the new hboot version in place I could start following the
2496 instructions on the HTC developer web site. I got the device token
2497 like this:&lt;/p&gt;
2498
2499 &lt;p&gt;&lt;pre&gt;
2500 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
2501 &lt;/pre&gt;
2502
2503 &lt;p&gt;And once I got the unlock code via email, I could use it like
2504 this:&lt;/p&gt;
2505
2506 &lt;p&gt;&lt;pre&gt;
2507 fastboot flash unlocktoken Unlock_code.bin
2508 &lt;/pre&gt;&lt;/p&gt;
2509
2510 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2511 could start stuffing the software of my own choosing into the device.
2512 So far I only inserted a replacement recovery image to wipe the phone
2513 before I start. We will see what happen next. Perhaps I should
2514 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2515 </description>
2516 </item>
2517
2518 <item>
2519 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2520 <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>
2521 <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>
2522 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2523 <description>&lt;p&gt;For a while now, I have wanted to test
2524 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2525 said to provide end to end encrypted communication and several of my
2526 friends and family are already using it. As I by choice do not own a
2527 mobile phone, this proved to be harder than expected. And I wanted to
2528 have the source of the client and know that it was the code used on my
2529 machine. But yesterday I managed to get it working. I used the
2530 Github source, compared it to the source in
2531 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2532 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2533 patches to use the production Signal servers, started the app and
2534 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2535 the recipe how I did it.&lt;/p&gt;
2536
2537 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2538
2539 &lt;pre&gt;
2540 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2541 &lt;/pre&gt;
2542
2543 &lt;p&gt;Next, I patched the source to use the production servers, to be
2544 able to talk to other Signal users:&lt;/p&gt;
2545
2546 &lt;pre&gt;
2547 cat &amp;lt;&amp;lt;EOF | patch -p0
2548 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2549 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2550 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2551 @@ -47,8 +47,8 @@
2552 });
2553 });
2554
2555 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2556 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2557 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2558 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2559 var messageReceiver;
2560 window.getSocketStatus = function() {
2561 if (messageReceiver) {
2562 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2563 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2564 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2565 @@ -1,6 +1,6 @@
2566 ;(function() {
2567 &#39;use strict&#39;;
2568 - var BUILD_EXPIRATION = 0;
2569 + var BUILD_EXPIRATION = 1474492690000;
2570
2571 window.extension = window.extension || {};
2572
2573 EOF
2574 &lt;/pre&gt;
2575
2576 &lt;p&gt;The first part is changing the servers, and the second is updating
2577 an expiration timestamp. This timestamp need to be updated regularly.
2578 It is set 90 days in the future by the build process (Gruntfile.js).
2579 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2580
2581 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2582 script to launch Signal in Chromium.&lt;/p&gt;
2583
2584 &lt;pre&gt;
2585 #!/bin/sh
2586 cd $(dirname $0)
2587 mkdir -p userdata
2588 exec chromium \
2589 --proxy-server=&quot;socks://localhost:9050&quot; \
2590 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2591 &lt;/pre&gt;
2592
2593 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2594 SOCKS5 proxy to make sure those controlling the Signal servers (today
2595 Amazon and Whisper Systems) as well as those listening on the lines
2596 will have a harder time location my laptop based on the Signal
2597 connections if they use source IP address.&lt;/p&gt;
2598
2599 &lt;p&gt;When the script starts, one need to follow the instructions under
2600 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2601 repository. I right clicked on the Signal window to get up the
2602 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2603 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2604 registration form. Then I entered by land line phone number and
2605 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2606 repeated the verification code three times. After entering the number
2607 into the verification code field in the form, I could start using
2608 Signal from my laptop.
2609
2610 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2611 whom and thus who know who to those controlling the central server,
2612 but such leakage is hard to avoid with a centrally controlled server
2613 setup. It is something to keep in mind when using Signal - the
2614 content of your chats are harder to intercept, but the meta data
2615 exposing your contact network is available to people you do not know.
2616 So better than many options, but not great. And sadly the usage is
2617 connected to my land line, thus allowing those controlling the server
2618 to associate it to my home and person. I would prefer it if only
2619 those I knew could tell who I was on Signal. There are options
2620 avoiding such information leakage, but most of my friends are not
2621 using them, so I am stuck with Signal for now.&lt;/p&gt;
2622
2623 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2624 on this topic in
2625 &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
2626 and updated recipe for using the Signal app without a mobile
2627 phone&lt;/a&gt;.&lt;/p&gt;
2628 </description>
2629 </item>
2630
2631 <item>
2632 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2633 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2634 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2635 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2636 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2637 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2638 multimedia player in Debian claimed to support most file formats /
2639 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2640 the various players claimed support for. The range was from 55 to 130
2641 MIME types. I suspect most media formats are supported by all
2642 players, but this is not really reflected in the MimeTypes values in
2643 their desktop files. There are probably also some bogus MIME types
2644 listed, but it is hard to identify which one this is.&lt;/p&gt;
2645
2646 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2647 the players suggesting to add more MIME types to their desktop files,
2648 and decided to spend some time myself improving the situation for my
2649 favorite media player VLC. The fixes for VLC entered Debian unstable
2650 yesterday. The complete list of MIME types can be seen on the
2651 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2652 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2653
2654 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2655 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2656 kmplayer. I am sure some of the other players desktop files support
2657 several of the formats currently listed as working only with vlc,
2658 toten and parole.&lt;/p&gt;
2659
2660 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2661 supported by all the tested multimedia players in Debian in their
2662 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2663 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2664 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2665 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2666 it sad that video/ogg and video/webm is not supported by all the media
2667 players in Debian. As far as I can tell, all of them can handle both
2668 formats.&lt;/p&gt;
2669 </description>
2670 </item>
2671
2672 <item>
2673 <title>A program should be able to open its own files on Linux</title>
2674 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2675 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2676 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2677 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2678 decided to test its presentation tool when making the slides for a
2679 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2680 wrote the first draft of the slides, saved the result and went to bed
2681 the day before I would give the talk. The next day I took a plane to
2682 the location where the meeting should take place, and on the plane I
2683 started up koffice again to polish the talk a bit, only to discover
2684 that kpresenter refused to load its own data file. I cursed a bit and
2685 started making the slides again from memory, to have something to
2686 present when I arrived. I tested that the saved files could be
2687 loaded, and the day seemed to be rescued. I continued to polish the
2688 slides until I suddenly discovered that the saved file could no longer
2689 be loaded into kpresenter. In the end I had to rewrite the slides
2690 three times, condensing the content until the talk became shorter and
2691 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2692 kpresenter wrote inline images in a way itself could not understand.
2693 Eventually that bug was fixed and kpresenter ended up being a great
2694 program to make slides. The point I&#39;m trying to make is that we
2695 expect a program to be able to load its own data files, and it is
2696 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2697
2698 &lt;p&gt;Did you ever experience a program failing to load its own data
2699 files from the desktop file browser? It is not a uncommon problem. A
2700 while back I discovered that the screencast recorder
2701 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2702 browser would refuse to open. No video player claimed to understand
2703 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2704 returning the application/ogg MIME type, which no video player I had
2705 installed listed as a MIME type they would understand. I asked for
2706 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2707 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2708 several video players to add video/ogg to their desktop files, to give
2709 the file browser an idea what to do about Ogg Theora files. After a
2710 while, the desktop file browsers in Debian started to handle the
2711 output from gtk-recordmydesktop properly.&lt;/p&gt;
2712
2713 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2714 system Rosegarden again, and I discovered that the KDE and xfce file
2715 browsers did not know what to do with the Rosegarden project files
2716 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2717 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2718 included in the next upload. To increase the chance of me remembering
2719 how to fix the problem next time some program fail to load its files
2720 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2721
2722 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2723 There are two sources for the MIME type of a given file. The output from
2724 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2725 shared MIME type registry (under /usr/share/mime/). The file MIME
2726 type is mapped to programs supporting the MIME type, and this
2727 information is collected from
2728 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2729 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2730 one desktop file claiming support for the MIME type of the file, it is
2731 activated when asking to open a given file. If there are more, one
2732 can normally select which one to use by right-clicking on the file and
2733 selecting the wanted one using &#39;Open with&#39; or similar. In general
2734 this work well. But it depend on each program picking a good MIME
2735 type (preferably
2736 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2737 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2738 registry recognizing the file and the desktop file to list the MIME
2739 type in its list of supported MIME types.&lt;/p&gt;
2740
2741 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2742 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2743 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2744
2745 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2746 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2747 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2748 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2749 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2750 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2751 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2752 &amp;lt;/mime-type&amp;gt;
2753 &amp;lt;/mime-info&amp;gt;
2754 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2755
2756 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2757 (it is a gzipped XML file). Note, it is much better to use an
2758 official MIME type registered with IANA than it is to make up ones own
2759 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2760
2761 &lt;p&gt;The desktop file of the rosegarden program failed to list
2762 audio/x-rosegarden in its list of supported MIME types, causing the
2763 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2764
2765 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2766 % grep Mime /usr/share/applications/rosegarden.desktop
2767 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2768 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2769 %
2770 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2771
2772 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2773 MimeType= line.&lt;/p&gt;
2774
2775 &lt;p&gt;If you run into a file which fail to open the correct program when
2776 selected from the file browser, please check out the output from
2777 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2778 MIME type is registered somewhere under /usr/share/mime/ and check
2779 that some desktop file under /usr/share/applications/ is claiming
2780 support for this MIME type. If not, please report a bug to have it
2781 fixed. :)&lt;/p&gt;
2782 </description>
2783 </item>
2784
2785 <item>
2786 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2787 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2789 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2790 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2791 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2792 related packages. The idea is to have a database of mappings between
2793 hardware and packages, and pop up a dialog suggesting for the user to
2794 install the packages to use a given hardware dongle. Some use cases
2795 are when you insert a Yubikey, it proposes to install the software
2796 needed to control it; when you insert a braille reader list it
2797 proposes to install the packages needed to send text to the reader;
2798 and when you insert a ColorHug screen calibrator it suggests to
2799 install the driver for it. The system work well, and even have a few
2800 command line tools to install firmware packages and packages for the
2801 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2802
2803 &lt;p&gt;The system was initially written using aptdaemon, because I found
2804 good documentation and example code on how to use it. But aptdaemon
2805 is going away and is generally being replaced by
2806 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2807 so Isenkram needed a rewrite. And today, thanks to the great patch
2808 from my college Sunil Mohan Adapa in the FreedomBox project, the
2809 rewrite finally took place. I&#39;ve just uploaded a new version of
2810 Isenkram into Debian Unstable with the patch included, and the default
2811 for the background daemon is now to use PackageKit. To check it out,
2812 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2813 and see if it is recognised.&lt;/p&gt;
2814
2815 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2816 the machine it is running on, you can check out the isenkram-lookup
2817 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2818
2819 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2820 % isenkram-lookup
2821 bluez
2822 cheese
2823 fprintd
2824 fprintd-demo
2825 gkrellm-thinkbat
2826 hdapsd
2827 libpam-fprintd
2828 pidgin-blinklight
2829 thinkfan
2830 tleds
2831 tp-smapi-dkms
2832 tp-smapi-source
2833 tpb
2834 %p
2835 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2836
2837 &lt;p&gt;The hardware mappings come from several places. The preferred way
2838 is for packages to announce their hardware support using
2839 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2840 cross distribution appstream system&lt;/a&gt;.
2841 See
2842 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2843 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2844 </description>
2845 </item>
2846
2847 <item>
2848 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2849 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2850 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2851 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2852 <description>&lt;p&gt;Yesterday I updated the
2853 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2854 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2855 enterprising users. There were some nice user and visible changes.
2856 First of all, both desktop menu entries now work. A design flaw in
2857 one of the script made the history graph fail to show up (its PNG was
2858 dumped in ~/.xsession-errors) if no controlling TTY was available.
2859 The script worked when called from the command line, but not when
2860 called from the desktop menu. I changed this to look for a DISPLAY
2861 variable or a TTY before deciding where to draw the graph, and now the
2862 graph window pop up as expected.&lt;/p&gt;
2863
2864 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2865 graphs (the one showing the last few hours). New is also the user of
2866 colours showing charging in blue and discharge in red. The percentages
2867 of this graph is relative to last full charge, not battery design
2868 capacity.&lt;/p&gt;
2869
2870 &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;
2871
2872 &lt;p&gt;The other graph show the entire history of the collected battery
2873 statistics, comparing it to the design capacity of the battery to
2874 visualise how the battery life time get shorter over time. The red
2875 line in this graph is what the previous graph considers 100 percent:
2876
2877 &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;
2878
2879 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2880 percent of last full capacity, and how the capacity of the battery is
2881 shrinking. :(&lt;/p&gt;
2882
2883 &lt;p&gt;The last new feature is in the collector, which now will handle
2884 more hardware models. On some hardware, Linux power supply
2885 information is stored in /sys/class/power_supply/ACAD/, while the
2886 collector previously only looked in /sys/class/power_supply/AC/. Now
2887 both are checked to figure if there is power connected to the
2888 machine.&lt;/p&gt;
2889
2890 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2891 check out the
2892 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2893 in Debian unstable, or rebuild it on Jessie to get it working on
2894 Debian stable. :) The upstream source is available from &lt;a
2895 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2896 Patches are very welcome.&lt;/p&gt;
2897
2898 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2899 activities, please send Bitcoin donations to my address
2900 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2901 </description>
2902 </item>
2903
2904 <item>
2905 <title>Debian now with ZFS on Linux included</title>
2906 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2908 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2909 <description>&lt;p&gt;Today, after many years of hard work from many people,
2910 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2911 Debian. The package status can be seen on
2912 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2913 for zfs-linux&lt;/a&gt;. and
2914 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2915 team status page&lt;/a&gt;. If you want to help out, please join us.
2916 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2917 source code&lt;/a&gt; is available via git on Alioth. It would also be
2918 great if you could help out with
2919 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2920 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2921 </description>
2922 </item>
2923
2924 <item>
2925 <title>What is the best multimedia player in Debian?</title>
2926 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2928 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2929 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2930 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2931
2932 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2933 plugins in Debian, to get an idea which plugins to include in Debian
2934 Edu. I created a script to extract the set of supported MIME types
2935 for each plugin, and used this to find out which multimedia browser
2936 plugin supported most file formats / media types.
2937 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2938 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2939 not been updated for a while. But browser plugins are less relevant
2940 these days, so I thought it was time to look at standalone
2941 players.&lt;/p&gt;
2942
2943 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2944 player when I wanted to play videos from the Norwegian National
2945 Broadcasting Company, and decided to investigate why. The cause is a
2946 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2947 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2948 of MIME types announced in the desktop file and the browser plugin,
2949 only to discover that there is quite a large difference between the
2950 two for VLC. This discovery made me dig up the script I used to
2951 compare browser plugins, and adjust it to compare desktop files
2952 instead, to try to figure out which multimedia player in Debian
2953 support most file formats.&lt;/p&gt;
2954
2955 &lt;p&gt;The result can be seen on the Debian Wiki, as
2956 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2957 table listing all MIME types supported by one of the packages included
2958 in the table&lt;/a&gt;, with the package supporting most MIME types being
2959 listed first in the table.&lt;/p&gt;
2960
2961 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2962 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2963 kmplayer. Time for the other players to update their announced MIME
2964 support?&lt;/p&gt;
2965 </description>
2966 </item>
2967
2968 <item>
2969 <title>The Pyra - handheld computer with Debian preinstalled</title>
2970 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2971 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2972 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2973 <description>A friend of mine made me aware of
2974 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2975 handheld computer which will be delivered with Debian preinstalled. I
2976 would love to get one of those for my birthday. :)&lt;/p&gt;
2977
2978 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2979 plugs and many others connectors, and include a full keyboard and a 5&quot;
2980 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2981 day of battery life time, but I have not seen any independent tests
2982 confirming this. The vendor is still collecting preorders, and the
2983 last I heard last night was that 22 more orders were needed before
2984 production started.&lt;/p&gt;
2985
2986 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2987 Debian. Please let me know if you know of any others. Is it the
2988 first computer being sold with Debian preinstalled?&lt;/p&gt;
2989 </description>
2990 </item>
2991
2992 <item>
2993 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2994 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2996 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2997 <description>&lt;p&gt;During this weekends
2998 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2999 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
3000 to make sure there are good books about Debian available in Norwegian
3001 Bokmål, and got in touch with the people behind the
3002 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
3003 project&lt;/a&gt; to get started. If you want to help out, please start
3004 contributing using
3005 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3006 hosted weblate project page&lt;/a&gt;, and get in touch using
3007 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3008 translators mailing list&lt;/a&gt;. Please also check out
3009 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3010 contributors&lt;/a&gt;.&lt;/p&gt;
3011
3012 &lt;p&gt;The book is already available on paper in English, French and
3013 Japanese, and our goal is to get it available on paper in Norwegian
3014 Bokmål too. In addition to the paper edition, there are also EPUB and
3015 Mobi versions available. And there are incomplete translations
3016 available for many more languages.&lt;/p&gt;
3017 </description>
3018 </item>
3019
3020 <item>
3021 <title>One in two hundred Debian users using ZFS on Linux?</title>
3022 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
3023 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
3024 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
3025 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
3026 packages in Debian, and was quite surprised with what I found. I use
3027 ZFS myself at home, but did not really expect many others to do so.
3028 But I might be wrong.&lt;/p&gt;
3029
3030 &lt;p&gt;According to
3031 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
3032 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
3033 0.53% of the population, with the package installed. As far as I know
3034 the only use of the spl-linux package is as a support library for ZFS
3035 on Linux, so I use it here as proxy for measuring the number of ZFS
3036 installation on Linux in Debian. In the kFreeBSD variant of Debian
3037 the ZFS feature is already available, and there
3038 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
3039 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
3040 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
3041
3042 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
3043 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
3044 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
3045 cleared, the package is still not in Debian. The package is again in
3046 the NEW queue. Several uploads have been rejected so far because the
3047 debian/copyright file was incomplete or wrong, but there is no reason
3048 to give up. The current status can be seen on
3049 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3050 team status page&lt;/a&gt;, and
3051 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
3052 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
3053
3054 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
3055 my home server can function in the future using only official Debian
3056 packages, and the current blocker is to get the debian/copyright file
3057 accepted by the FTP masters in Debian, I decided a while back to try
3058 to help out the team. This was the background for my blog post about
3059 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
3060 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
3061 used the techniques I explored there to try to find any errors in the
3062 copyright file. It is not very easy to check every one of the around
3063 2000 files in the source package, but I hope we this time got it
3064 right. If you want to help out, check out the git source and try to
3065 find missing entries in the debian/copyright file.&lt;/p&gt;
3066 </description>
3067 </item>
3068
3069 <item>
3070 <title>Full battery stats collector is now available in Debian</title>
3071 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
3072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
3073 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
3074 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
3075 extended collector that will collect the complete battery history for
3076 later processing and graphing. The original collector store the
3077 battery level as percentage of last full level, while the new
3078 collector also record battery vendor, model, serial number, design
3079 full level, last full level and current battery level. This make it
3080 possible to predict the lifetime of the battery as well as visualise
3081 the energy flow when the battery is charging or discharging.&lt;/p&gt;
3082
3083 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
3084 in the version 0.5.1 package in unstable. Get the new battery level graph
3085 and lifetime prediction by running:
3086
3087 &lt;p&gt;&lt;pre&gt;
3088 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3089 &lt;/pre&gt;&lt;/p&gt;
3090
3091 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
3092
3093 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
3094 entry yet):&lt;/p&gt;
3095
3096 &lt;p&gt;&lt;pre&gt;
3097 /usr/share/battery-stats/battery-stats-graph-flow
3098 &lt;/pre&gt;&lt;/p&gt;
3099
3100 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
3101 when there are few data points. The graphs look a bit better with a
3102 few years of data.&lt;/p&gt;
3103
3104 &lt;p&gt;A while back one important feature I use in the battery stats
3105 collector broke in Debian. The scripts in
3106 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
3107 suspect it happened when Jessie started using systemd, but I do not
3108 know. The issue is reported as
3109 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
3110 pm-utils. I managed to work around it by adding an udev rule to call
3111 the collector script every time the power connector is connected and
3112 disconnected. With this fix in place it was finally time to make a
3113 new release of the package, and get it into Debian.&lt;/p&gt;
3114
3115 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3116 check out the
3117 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3118 in Debian unstable, or rebuild it on Jessie to get it working on
3119 Debian stable. :) The upstream source is available from
3120 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3121 As always, patches are very welcome.&lt;/p&gt;
3122 </description>
3123 </item>
3124
3125 <item>
3126 <title>Making battery measurements a little easier in Debian</title>
3127 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
3128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
3129 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
3130 <description>&lt;p&gt;Back in September, I blogged about
3131 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
3132 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
3133 how it showed the decay and death of this battery (now replaced). I
3134 created a simple deb package to handle the collection and graphing,
3135 but did not want to upload it to Debian as there were already
3136 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
3137 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
3138 a point of uploading a competing package when battery-stats could be
3139 fixed instead. I reported a few bugs about its non-function, and
3140 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
3141
3142 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
3143 hands. The end result is that I am now the new upstream developer of
3144 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
3145 battery-stats in Debian, and the package in Debian unstable is finally
3146 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
3147 information provided by the Linux kernel. If you install the
3148 battery-stats package from unstable now, you will be able to get a
3149 graph of the current battery fill level, to get some idea about the
3150 status of the battery. The source package build and work just fine in
3151 Debian testing and stable (and probably oldstable too, but I have not
3152 tested). The default graph you get for that system look like this:&lt;/p&gt;
3153
3154 &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;
3155
3156 &lt;p&gt;My plans for the future is to merge my old scripts into the
3157 battery-stats package, as my old scripts collected a lot more details
3158 about the battery. The scripts are merged into the upstream
3159 battery-stats git repository already, but I am not convinced they work
3160 yet, as I changed a lot of paths along the way. Will have to test a
3161 bit more before I make a new release.&lt;/p&gt;
3162
3163 &lt;p&gt;I will also consider changing the file format slightly, as I
3164 suspect the way I combine several values into one field might make it
3165 impossible to know the type of the value when using it for processing
3166 and graphing.&lt;/p&gt;
3167
3168 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
3169 battery, check out the battery-stats package in
3170 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
3171 on
3172 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3173 I would love some help to improve the system further.&lt;/p&gt;
3174 </description>
3175 </item>
3176
3177 <item>
3178 <title>Creating, updating and checking debian/copyright semi-automatically</title>
3179 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
3180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
3181 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
3182 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
3183 details. And one of the details is the content of the
3184 debian/copyright file, which should list all relevant licenses used by
3185 the code in the package in question, preferably in
3186 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
3187 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
3188
3189 &lt;p&gt;For large packages with lots of contributors it is hard to write
3190 and update this file manually, and if you get some detail wrong, the
3191 package is normally rejected by the ftpmasters. So getting it right
3192 the first time around get the package into Debian faster, and save
3193 both you and the ftpmasters some work.. Today, while trying to figure
3194 out what was wrong with
3195 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
3196 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
3197 figuring out the options for doing this job automatically, or at least
3198 semi-automatically.&lt;/p&gt;
3199
3200 &lt;p&gt;Lucikly, there are at least two tools available for generating the
3201 file based on the code in the source package,
3202 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
3203 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
3204 not sure which one of them came first, but both seem to be able to
3205 create a sensible draft file. As far as I can tell, none of them can
3206 be trusted to get the result just right, so the content need to be
3207 polished a bit before the file is OK to upload. I found the debmake
3208 option in
3209 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
3210 blog posts from 2014&lt;/a&gt;.
3211
3212 &lt;p&gt;To generate using debmake, use the -cc option:
3213
3214 &lt;p&gt;&lt;pre&gt;
3215 debmake -cc &gt; debian/copyright
3216 &lt;/pre&gt;&lt;/p&gt;
3217
3218 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
3219 this might not be the best option.&lt;/p&gt;
3220
3221 &lt;p&gt;The cme option is based on a config parsing library, and I found
3222 this approach in
3223 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
3224 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
3225 dpkg-copyright&#39; option:
3226
3227 &lt;p&gt;&lt;pre&gt;
3228 cme update dpkg-copyright
3229 &lt;/pre&gt;&lt;/p&gt;
3230
3231 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
3232 handle UTF-8 names better than debmake.&lt;/p&gt;
3233
3234 &lt;p&gt;When the copyright file is created, I would also like some help to
3235 check if the file is correct. For this I found two good options,
3236 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
3237 to focus on license types and file matching, and is able to detect
3238 ineffective blocks in the copyright file. The latter reports missing
3239 copyright holders and years, but was confused by inconsistent license
3240 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
3241 fix all issues reported by them before uploading. But I do not know
3242 if the tools and the ftpmasters agree on what is important to fix in a
3243 copyright file, so the package might still be rejected.&lt;/p&gt;
3244
3245 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
3246 will read through the source and try to find all copyright statements.
3247 It is not comparing the result to the content of debian/copyright, but
3248 can be useful when verifying the content of the copyright file.&lt;/p&gt;
3249
3250 &lt;p&gt;Are you aware of better tools in Debian to create and update
3251 debian/copyright file. Please let me know, or blog about it on
3252 planet.debian.org.&lt;/p&gt;
3253
3254 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3255 activities, please send Bitcoin donations to my address
3256 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3257
3258 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
3259 on how to use licensecheck and cdbs to create a draft copyright file
3260
3261 &lt;p&gt;&lt;pre&gt;
3262 licensecheck --copyright -r `find * -type f` | \
3263 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
3264 &lt;/pre&gt;&lt;/p&gt;
3265
3266 &lt;p&gt;He mentioned that he normally check the generated file into the
3267 version control system to make it easier to discover license and
3268 copyright changes in the upstream source. I will try to do the same
3269 with my packages in the future.&lt;/p&gt;
3270
3271 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
3272 against using -quiet for new users, so I removed it from the proposed
3273 command line.&lt;/p&gt;
3274 </description>
3275 </item>
3276
3277 <item>
3278 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
3279 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
3280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
3281 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
3282 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
3283 is taking shape in Debian, and one provided feature is a very
3284 convenient way to tell you which package to install to make a given
3285 firmware file available when the kernel is looking for it. This can
3286 be done using apt-file too, but that is for someone else to blog
3287 about. :)&lt;/p&gt;
3288
3289 &lt;p&gt;Here is a small recipe to find the package with a given firmware
3290 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
3291 picked from the set of firmware announced using appstream in Debian
3292 unstable. In general you would be looking for the firmware requested
3293 by the kernel during kernel module loading. To find the package
3294 providing the example file, do like this:&lt;/p&gt;
3295
3296 &lt;blockquote&gt;&lt;pre&gt;
3297 % apt install appstream
3298 [...]
3299 % apt update
3300 [...]
3301 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
3302 awk &#39;/Package:/ {print $2}&#39;
3303 firmware-qlogic
3304 %
3305 &lt;/pre&gt;&lt;/blockquote&gt;
3306
3307 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
3308 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
3309 a way appstream can use.&lt;/p&gt;
3310
3311 &lt;p&gt;This same approach can be used to find any package supporting a
3312 given MIME type. This is very useful when you get a file you do not
3313 know how to handle. First find the mime type using &lt;tt&gt;file
3314 --mime-type&lt;/tt&gt;, and next look up the package providing support for
3315 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3316 and you can find all packages handling this type like this:&lt;/p&gt;
3317
3318 &lt;blockquote&gt;&lt;pre&gt;
3319 % apt install appstream
3320 [...]
3321 % apt update
3322 [...]
3323 % appstreamcli what-provides mimetype image/svg+xml | \
3324 awk &#39;/Package:/ {print $2}&#39;
3325 bkchem
3326 phototonic
3327 inkscape
3328 shutter
3329 tetzle
3330 geeqie
3331 xia
3332 pinta
3333 gthumb
3334 karbon
3335 comix
3336 mirage
3337 viewnior
3338 postr
3339 ristretto
3340 kolourpaint4
3341 eog
3342 eom
3343 gimagereader
3344 midori
3345 %
3346 &lt;/pre&gt;&lt;/blockquote&gt;
3347
3348 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
3349 packages providing appstream metadata.&lt;/p&gt;
3350 </description>
3351 </item>
3352
3353 <item>
3354 <title>Creepy, visualise geotagged social media information - nice free software</title>
3355 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
3356 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
3357 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
3358 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
3359 with the computerised radio beacon known as a mobile phone their
3360 position is tracked by the phone company and often stored for a long
3361 time (like every time a SMS is received or sent). And if their
3362 computerised radio beacon is capable of running programs (often called
3363 mobile apps) downloaded from the Internet, these programs are often
3364 also capable of tracking their location (if the app requested access
3365 during installation). And when these programs send out information to
3366 central collection points, the location is often included, unless
3367 extra care is taken to not send the location. The provided
3368 information is used by several entities, for good and bad (what is
3369 good and bad, depend on your point of view). What is certain, is that
3370 the private sphere and the right to free movement is challenged and
3371 perhaps even eradicated for those announcing their location this way,
3372 when they share their whereabouts with private and public
3373 entities.&lt;/p&gt;
3374
3375 &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;
3376
3377 &lt;p&gt;The phone company logs provide a register of locations to check out
3378 when one want to figure out what the tracked person was doing. It is
3379 unavailable for most of us, but provided to selected government
3380 officials, company staff, those illegally buying information from
3381 unfaithful servants and crackers stealing the information. But the
3382 public information can be collected and analysed, and a free software
3383 tool to do so is called
3384 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
3385 discovered it when I read
3386 &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
3387 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
3388 November 2014, and decided to check if it was available in Debian.
3389 The python program was in Debian, but
3390 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
3391 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
3392 uploaded a new version which did not work quite right, but did not
3393 have time to fix it then. This Christmas I decided to finally try to
3394 get Creepy operational in Debian. Now a fixed version is available in
3395 Debian unstable and testing, and almost all Debian specific patches
3396 are now included
3397 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
3398
3399 &lt;p&gt;The Creepy program visualises geolocation information fetched from
3400 Twitter, Instagram, Flickr and Google+, and allow one to get a
3401 complete picture of every social media message posted recently in a
3402 given area, or track the movement of a given individual across all
3403 these services. Earlier it was possible to use the search API of at
3404 least some of these services without identifying oneself, but these
3405 days it is impossible. This mean that to use Creepy, you need to
3406 configure it to log in as yourself on these services, and provide
3407 information to them about your search interests. This should be taken
3408 into account when using Creepy, as it will also share information
3409 about yourself with the services.&lt;/p&gt;
3410
3411 &lt;p&gt;The picture above show the twitter messages sent from (or at least
3412 geotagged with a position from) the city centre of Oslo, the capital
3413 of Norway. One useful way to use Creepy is to first look at
3414 information tagged with an area of interest, and next look at all the
3415 information provided by one or more individuals who was in the area.
3416 I tested it by checking out which celebrity provide their location in
3417 twitter messages by checkout out who sent twitter messages near a
3418 Norwegian TV station, and next could track their position over time,
3419 making it possible to locate their home and work place, among other
3420 things. A similar technique have been
3421 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
3422 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
3423 tool to discover lying governments, and a useful tool to help people
3424 understand the value of the private information they provide to the
3425 public.&lt;/p&gt;
3426
3427 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
3428 it depend on several python modules currently missing in Jessie (at
3429 least python-instagram, python-flickrapi and
3430 python-requests-toolbelt).&lt;/p&gt;
3431
3432 &lt;p&gt;(I have uploaded
3433 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
3434 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
3435 Creepy program in Debian.)&lt;/p&gt;
3436 </description>
3437 </item>
3438
3439 <item>
3440 <title>Always download Debian packages using Tor - the simple recipe</title>
3441 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
3442 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
3443 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
3444 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
3445 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
3446 that those listening on the Internet lines would have good reason to
3447 believe a computer have a given security hole&lt;/a&gt; if it download a
3448 security fix from a Debian mirror. This is a good reason to always
3449 use encrypted connections to the Debian mirror, to make sure those
3450 listening do not know which IP address to attack. In August, Richard
3451 Hartmann observed that encryption was not enough, when it was possible
3452 to interfere download size to security patches or the fact that
3453 download took place shortly after a security fix was released, and
3454 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
3455 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
3456 was not the first to propose this, as the
3457 &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;
3458 package by Tim Retout already existed to make it easy to convince apt
3459 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
3460 aware of that package when I read the blog post from Richard.&lt;/p&gt;
3461
3462 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
3463 sysadmins, and he set up a Tor hidden service on one of the central
3464 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3465 it possible to download packages directly between two tor nodes,
3466 making sure the network traffic always were encrypted.&lt;/p&gt;
3467
3468 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
3469 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
3470 urls with tor+http and tor+https, and using the hidden service instead
3471 of the official Debian mirror site. I recommend installing
3472 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
3473 done in /etc/.&lt;/p&gt;
3474
3475 &lt;blockquote&gt;&lt;pre&gt;
3476 apt install apt-transport-tor
3477 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
3478 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
3479 &lt;/pre&gt;&lt;/blockquote&gt;
3480
3481 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
3482 the sed commands for these too. The sed command is assuming your are
3483 using the ftp.debian.org Debian mirror. Adjust the command (or just
3484 edit the file manually) to match your mirror.&lt;/p&gt;
3485
3486 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
3487 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
3488 system, and do not work with these tor+http URLs. For
3489 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
3490 which need a recent apt version currently only in unstable. So if you
3491 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
3492
3493 &lt;p&gt;Another advantage from this change is that your machine will start
3494 using Tor regularly and at fairly random intervals (every time you
3495 update the package lists or upgrade or install a new package), thus
3496 masking other Tor traffic done from the same machine. Using Tor will
3497 become normal for the machine in question.&lt;/p&gt;
3498
3499 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
3500 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
3501 enabled. It would be great if it was the default on any Debian
3502 system.&lt;/p&gt;
3503 </description>
3504 </item>
3505
3506 <item>
3507 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3508 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3510 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3511 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3512 call the car license plate numbers in those days. I would write the
3513 numbers down in my little book and compare notes with the other kids
3514 to see how many region codes we had seen and if we had seen some
3515 exotic or special region codes and numbers. It was a fun game to pass
3516 time, as we kids have plenty of it.&lt;/p&gt;
3517
3518 &lt;p&gt;A few days I came across
3519 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3520 project&lt;/a&gt;, a free software project to automatically discover and
3521 report license plates in images and video streams, and provide the
3522 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3523 such system for a while now, because I believe it is a bad idea that the
3524 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3525 number plate recognition&lt;/a&gt; tool only is available in the hands of
3526 the powerful, and want it to be available also for the powerless to
3527 even the score when it comes to surveillance and sousveillance. I
3528 discovered the developer
3529 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3530 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3531 help him get it into shape to get the package uploaded into the Debian
3532 archive.&lt;/p&gt;
3533
3534 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3535 it into Debian, where it currently
3536 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3537 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3538
3539 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3540 for the common folks, ie those not running a large government
3541 surveillance system? Well, I plan to put it in a computer on my bike
3542 and in my car, tracking the cars nearby and allowing me to be notified
3543 when number plates on my watch list are discovered. Another use case
3544 was suggested by a friend of mine, who wanted to set it up at his home
3545 to open the car port automatically when it discovered the plate on his
3546 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3547 capable of placing his license plate number of a piece of cardboard to
3548 open his car port, men replied that it was always unlocked anyway. I
3549 guess for such use case it make sense. I am sure there are other use
3550 cases too, for those with imagination and a vision.&lt;/p&gt;
3551
3552 &lt;p&gt;If you want to build your own version of the Debian package, check
3553 out the upstream git source and symlink ./distros/debian to ./debian/
3554 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3555 package show up in unstable.&lt;/p&gt;
3556 </description>
3557 </item>
3558
3559 <item>
3560 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3561 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3562 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3563 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3564 <description>&lt;p&gt;Around three years ago, I created
3565 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3566 system&lt;/a&gt; to get a more practical solution in Debian for handing
3567 hardware related packages. A GUI system in the isenkram package will
3568 present a pop-up dialog when some hardware dongle supported by
3569 relevant packages in Debian is inserted into the machine. The same
3570 lookup mechanism to detect packages is available as command line
3571 tools in the isenkram-cli package. In addition to mapping hardware,
3572 it will also map kernel firmware files to packages and make it easy to
3573 install needed firmware packages automatically. The key for this
3574 system to work is a good way to map hardware to packages, in other
3575 words, allow packages to announce what hardware they will work
3576 with.&lt;/p&gt;
3577
3578 &lt;p&gt;I started by providing data files in the isenkram source, and
3579 adding code to download the latest version of these data files at run
3580 time, to ensure every user had the most up to date mapping available.
3581 I also added support for storing the mapping in the Packages file in
3582 the apt repositories, but did not push this approach because while I
3583 was trying to figure out how to best store hardware/package mappings,
3584 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3585 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3586 add the hardware mapping into that data set to be able to use
3587 appstream as a data source, and this was accepted at least for the
3588 Debian version of appstream.&lt;/p&gt;
3589
3590 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3591 and today I uploaded a new version 0.20 of isenkram adding support for
3592 appstream as a data source for mapping hardware to packages. The only
3593 package so far using appstream to announce its hardware support is my
3594 pymissile package. I got help from Matthias Klumpp with figuring out
3595 how do add the required
3596 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3597 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3598 this content:&lt;/p&gt;
3599
3600 &lt;blockquote&gt;&lt;pre&gt;
3601 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3602 &amp;lt;component&amp;gt;
3603 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3604 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3605 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3606 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3607 &amp;lt;description&amp;gt;
3608 &amp;lt;p&amp;gt;
3609 Pymissile provides a curses interface to control an original
3610 Marks and Spencer / Striker USB Missile Launcher, as well as a
3611 motion control script to allow a webcamera to control the
3612 launcher.
3613 &amp;lt;/p&amp;gt;
3614 &amp;lt;/description&amp;gt;
3615 &amp;lt;provides&amp;gt;
3616 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3617 &amp;lt;/provides&amp;gt;
3618 &amp;lt;/component&amp;gt;
3619 &lt;/pre&gt;&lt;/blockquote&gt;
3620
3621 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3622 which is a glob style match rule for hardware specific strings
3623 (modalias strings) provided by the Linux kernel. In this case, it
3624 will map to all USB devices with vendor code 1130 and product code
3625 0202.&lt;/p&gt;
3626
3627 &lt;p&gt;Note, it is important that the license of all the metadata files
3628 are compatible to have permissions to aggregate them into archive wide
3629 appstream files. Matthias suggested to use MIT or BSD licenses for
3630 these files. A challenge is figuring out a good id for the data, as
3631 it is supposed to be globally unique and shared across distributions
3632 (in other words, best to coordinate with upstream what to use). But
3633 it can be changed later or, so we went with the package name as
3634 upstream for this project is dormant.&lt;/p&gt;
3635
3636 &lt;p&gt;To get the metadata file installed in the correct location for the
3637 mirror update scripts to pick it up and include its content the
3638 appstream data source, the file must be installed in the binary
3639 package under /usr/share/appdata/. I did this by adding the following
3640 line to debian/pymissile.install:&lt;/p&gt;
3641
3642 &lt;blockquote&gt;&lt;pre&gt;
3643 debian/pymissile.metainfo.xml usr/share/appdata
3644 &lt;/pre&gt;&lt;/blockquote&gt;
3645
3646 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3647 all packages useful on the current computer automatically, and the GUI
3648 pop-up handler will propose to install the package not already
3649 installed if a hardware dongle is inserted into the machine in
3650 question.&lt;/p&gt;
3651
3652 &lt;p&gt;Details of the modalias field in appstream is available from the
3653 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3654
3655 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3656 try running this command on the command line:&lt;/p&gt;
3657
3658 &lt;blockquote&gt;&lt;pre&gt;
3659 cat $(find /sys/devices/|grep modalias)
3660 &lt;/pre&gt;&lt;/blockquote&gt;
3661
3662 &lt;p&gt;To learn more about the isenkram system, please check out
3663 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3664 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3665 </description>
3666 </item>
3667
3668 <item>
3669 <title>The GNU General Public License is not magic pixie dust</title>
3670 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3671 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3672 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3673 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3674 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3675 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3676 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3677 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3678
3679 &lt;blockquote&gt;
3680
3681 &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;
3682
3683 &lt;blockquote&gt;
3684 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3685
3686 The first step is to choose a
3687 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3688 code.&lt;br/&gt;
3689
3690 The next step is, when someone fails to follow that copyleft license,
3691 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3692
3693 and its a simple fact of our modern society that such type of
3694 work&lt;br/&gt;
3695
3696 is incredibly expensive to do and incredibly difficult to do.
3697 &lt;/blockquote&gt;
3698
3699 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3700 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3701 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3702 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3703
3704 &lt;p&gt;As the Debian Website
3705 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3706 &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;
3707 imply, public domain and permissively licensed software can lead to
3708 the production of more proprietary software as people discover useful
3709 software, extend it and or incorporate it into their hardware or
3710 software products. Copyleft licenses such as the GNU GPL were created
3711 to close off this avenue to the production of proprietary software but
3712 such licenses are not enough. With the ongoing adoption of Free
3713 Software by individuals and groups, inevitably the community&#39;s
3714 expectations of license compliance are violated, usually out of
3715 ignorance of the way Free Software works, but not always. As Karen
3716 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3717 Freedom&quot;&gt;FaiF&lt;/a&gt;
3718 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3719 copyleft is nothing if no-one is willing and able to stand up in court
3720 to protect it. The reality of today&#39;s world is that legal
3721 representation is expensive, difficult and time consuming. With
3722 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3723 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3724 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3725 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3726 of the Linux project, Debian and other groups against GPL violations.
3727 In March the SFC supported a
3728 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3729 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3730 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3731 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3732 kernel. Since then two of their sponsors pulled corporate funding and
3733 conferences
3734 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3735 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3736 less on corporate funding and more on the broad community of
3737 individuals who support Free Software and copyleft. So the SFC has
3738 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3739 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3740 a community of folks who stand up for copyleft and the GPL by
3741 supporting their work on promoting and supporting copyleft and Free
3742 Software.&lt;/p&gt;
3743
3744 &lt;p&gt;If you support Free Software,
3745 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3746 what the SFC do, agree with their
3747 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3748 principles&lt;/a&gt;, are happy about their
3749 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3750 work on a project that is an SFC
3751 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3752 just want to stand up for copyleft, please join
3753 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3754 Allan Webber&lt;/a&gt;,
3755 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3756 Smith&lt;/a&gt;,
3757 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3758 Bacon&lt;/a&gt;, myself and
3759 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3760 becoming a
3761 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3762 next week your donation will be
3763 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3764 by an anonymous donor. Please also consider asking your employer to
3765 match your donation or become a sponsor of SFC. Don&#39;t forget to
3766 spread the word about your support for SFC via email, your blog and or
3767 social media accounts.&lt;/p&gt;
3768
3769 &lt;/blockquote&gt;
3770
3771 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3772 of Software Freedom Conservancy myself. Perhaps you should be a
3773 supporter too?&lt;/p&gt;
3774 </description>
3775 </item>
3776
3777 <item>
3778 <title>PGP key transition statement for key EE4E02F9</title>
3779 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3780 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3781 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3782 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3783 set it up properly. I wanted to generate it offline and have it
3784 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3785 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3786 time to sit down with an offline machine almost took forever. But
3787 finally I&#39;ve been able to complete the process, and have now moved
3788 from my old GPG key to a new GPG key. See
3789 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3790 full transition statement, signed with both my old and new key&lt;/a&gt; for
3791 the details. This is my new key:&lt;/p&gt;
3792
3793 &lt;pre&gt;
3794 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]
3795 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3796 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3797 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3798 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3799 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3800 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3801 &lt;/pre&gt;
3802
3803 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3804 my old key.&lt;/p&gt;
3805
3806 &lt;p&gt;If you signed my old key
3807 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3808 I&#39;d very much appreciate a signature on my new key, details and
3809 instructions in the transition statement. I m happy to reciprocate if
3810 you have a similarly signed transition statement to present.&lt;/p&gt;
3811 </description>
3812 </item>
3813
3814 <item>
3815 <title>The life and death of a laptop battery</title>
3816 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3817 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3818 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3819 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3820 But this do not last. The last few laptops gave me a feeling that
3821 within a year, the life time is just a fraction of what it used to be,
3822 and it slowly become painful to use the laptop without power connected
3823 all the time. Because of this, when I got a new Thinkpad X230 laptop
3824 about two years ago, I decided to monitor its battery state to have
3825 more hard facts when the battery started to fail.&lt;/p&gt;
3826
3827 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3828
3829 &lt;p&gt;First I tried to find a sensible Debian package to record the
3830 battery status, assuming that this must be a problem already handled
3831 by someone else. I found
3832 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3833 which collects statistics from the battery, but it was completely
3834 broken. I sent a few suggestions to the maintainer, but decided to
3835 write my own collector as a shell script while I waited for feedback
3836 from him. Via
3837 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3838 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3839 discovered
3840 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3841 available in Debian.&lt;/p&gt;
3842
3843 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3844 battery stats ever since. Now my
3845 /var/log/hjemmenett-battery-status.log file contain around 115,000
3846 measurements, from the time the battery was working great until now,
3847 when it is unable to charge above 7% of original capacity. My
3848 collector shell script is quite simple and look like this:&lt;/p&gt;
3849
3850 &lt;pre&gt;
3851 #!/bin/sh
3852 # Inspired by
3853 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3854 # See also
3855 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3856 logfile=/var/log/hjemmenett-battery-status.log
3857
3858 files=&quot;manufacturer model_name technology serial_number \
3859 energy_full energy_full_design energy_now cycle_count status&quot;
3860
3861 if [ ! -e &quot;$logfile&quot; ] ; then
3862 (
3863 printf &quot;timestamp,&quot;
3864 for f in $files; do
3865 printf &quot;%s,&quot; $f
3866 done
3867 echo
3868 ) &gt; &quot;$logfile&quot;
3869 fi
3870
3871 log_battery() {
3872 # Print complete message in one echo call, to avoid race condition
3873 # when several log processes run in parallel.
3874 msg=$(printf &quot;%s,&quot; $(date +%s); \
3875 for f in $files; do \
3876 printf &quot;%s,&quot; $(cat $f); \
3877 done)
3878 echo &quot;$msg&quot;
3879 }
3880
3881 cd /sys/class/power_supply
3882
3883 for bat in BAT*; do
3884 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3885 done
3886 &lt;/pre&gt;
3887
3888 &lt;p&gt;The script is called when the power management system detect a
3889 change in the power status (power plug in or out), and when going into
3890 and out of hibernation and suspend. In addition, it collect a value
3891 every 10 minutes. This make it possible for me know when the battery
3892 is discharging, charging and how the maximum charge change over time.
3893 The code for the Debian package
3894 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3895 available on github&lt;/a&gt;.&lt;/p&gt;
3896
3897 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3898
3899 &lt;pre&gt;
3900 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3901 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3902 [...]
3903 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3904 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3905 &lt;/pre&gt;
3906
3907 &lt;p&gt;I wrote a small script to create a graph of the charge development
3908 over time. This graph depicted above show the slow death of my laptop
3909 battery.&lt;/p&gt;
3910
3911 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3912 dying in a year or two, while the batteries of space probes and
3913 satellites keep working year after year. If we are to believe
3914 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3915 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3916 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3917 all the time, but to stay below 90% of full charge most of the time.
3918 I&#39;ve been told that the Tesla electric cars
3919 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3920 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3921 100% when preparing for a longer trip (not that I would want a car
3922 like Tesla where rights to privacy is abandoned, but that is another
3923 story), which I guess is the option we should have for laptops on
3924 Linux too.&lt;/p&gt;
3925
3926 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3927 stop charging at 80%, unless requested to charge to 100% once in
3928 preparation for a longer trip? I found
3929 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3930 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3931 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3932 load).&lt;/p&gt;
3933
3934 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3935 at the start. I also wonder why the &quot;full capacity&quot; increases some
3936 times, and if it is possible to repeat the process to get the battery
3937 back to design capacity. And I wonder if the discharge and charge
3938 speed change over time, or if this stay the same. I did not yet try
3939 to write a tool to calculate the derivative values of the battery
3940 level, but suspect some interesting insights might be learned from
3941 those.&lt;/p&gt;
3942
3943 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3944 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3945 packages instead of the tp-smapi-dkms package I had tried to use
3946 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3947 and stop. I&#39;ve done so now, but expect my existing battery is toast
3948 and need to be replaced. The proposal is unfortunately Thinkpad
3949 specific.&lt;/p&gt;
3950 </description>
3951 </item>
3952
3953 <item>
3954 <title>New laptop - some more clues and ideas based on feedback</title>
3955 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3957 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3958 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3959 need for a new laptop, and provided very useful feedback. I wish to
3960 thank every one of these. Several pointed me to the possibility of
3961 fixing my X230, and I am already in the process of getting Lenovo to
3962 do so thanks to the on site, next day support contract covering the
3963 machine. But the battery is almost useless (I expect to replace it
3964 with a non-official battery) and I do not expect the machine to live
3965 for many more years, so it is time to plan its replacement. If I did
3966 not have a support contract, it was suggested to find replacement parts
3967 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3968 might present a language barrier as I do not understand French.&lt;/p&gt;
3969
3970 &lt;p&gt;One tip I got was to use the
3971 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3972 compare laptop models. It seem to have more models available than
3973 prisjakt.no. Another tip I got from someone I know have similar
3974 keyboard preferences was that the HP EliteBook 840 keyboard is not
3975 very good, and this matches my experience with earlier EliteBook
3976 keyboards I tested. Because of this, I will not consider it any further.
3977
3978 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3979 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3980 (which is missing from the X240), and is working fairly well with
3981 Debian Sid/Unstable according to
3982 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3983 got on the keyboard quality are not consistent. Some say the keyboard
3984 is good, others say it is ok, while others say it is not very good.
3985 Those with experience from X41 and and X60 agree that the X250
3986 keyboard is not as good as those trusty old laptops, and suggest I
3987 keep and fix my X230 instead of upgrading, or get a used X230 to
3988 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3989 activity and battery status, which is very convenient on my X230. I&#39;m
3990 also told that the CPU fan is running very often, making it a bit
3991 noisy. In any case, the X250 do not work out of the box with Debian
3992 Stable/Jessie, one of my requirements.&lt;/p&gt;
3993
3994 &lt;p&gt;I have also gotten a few vendor proposals, one was
3995 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3996 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3997 The latter look very attractive to me.&lt;/p&gt;
3998
3999 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
4000 as I keep looking for a replacement.&lt;/p&gt;
4001
4002 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
4003 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
4004 different
4005 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
4006 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
4007 </description>
4008 </item>
4009
4010 <item>
4011 <title>Time to find a new laptop, as the old one is broken after only two years</title>
4012 <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>
4013 <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>
4014 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
4015 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
4016 replacement soon. The left 5 cm of the screen on my Thinkpad X230
4017 started flickering yesterday, and I suspect the cause is a broken
4018 cable, as changing the angle of the screen some times get rid of the
4019 flickering.&lt;/p&gt;
4020
4021 &lt;p&gt;My requirements have not really changed since I bought it, and is
4022 still as
4023 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
4024 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
4025 good help from
4026 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
4027 where I could select at least a few of the requirements (mouse pin,
4028 wifi, weight) and go through the rest manually. Three button mouse
4029 and a good keyboard is not available as an option, and all the three
4030 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
4031 G2) lack three mouse buttons). It is also unclear to me how good the
4032 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
4033 the keyboard, even if the quality and robustness in the X series have
4034 deteriorated since X41.&lt;/p&gt;
4035
4036 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
4037 seem sensible to me? Are there better services around to search the
4038 set of available laptops for features? Please send me an email if you
4039 have suggestions.&lt;/p&gt;
4040
4041 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
4042 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
4043 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
4044 </description>
4045 </item>
4046
4047 <item>
4048 <title>How to stay with sysvinit in Debian Jessie</title>
4049 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
4050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
4051 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
4052 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
4053 sysvinit as its boot system by default. But how can one keep using
4054 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
4055 courtesy of
4056 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
4057 Schubert&lt;/a&gt; and
4058 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
4059 McVittie&lt;/a&gt;.
4060
4061 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
4062 keep sysvinit as your boot system, create a file
4063 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
4064 you upgrade:&lt;/p&gt;
4065
4066 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4067 Package: systemd-sysv
4068 Pin: release o=Debian
4069 Pin-Priority: -1
4070 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4071
4072 &lt;p&gt;This file content will tell apt and aptitude to not consider
4073 installing systemd-sysv as part of any installation and upgrade
4074 solution when resolving dependencies, and thus tell it to avoid
4075 systemd as a default boot system. The end result should be that the
4076 upgraded system keep using sysvinit.&lt;/p&gt;
4077
4078 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
4079 get sysvinit installed by default (debootstrap used by
4080 debian-installer have no option for this), but one can tell the
4081 installer to switch to sysvinit before the first boot. Either by
4082 using a kernel argument to the installer, or by adding a line to the
4083 preseed file used. First, the kernel command line argument:
4084
4085 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4086 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
4087 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4088
4089 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
4090
4091 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4092 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4093 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4094
4095 &lt;p&gt;One can of course also do this after the first boot by installing
4096 the sysvinit-core package.&lt;/p&gt;
4097
4098 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
4099 sysvinit boot sequence in Debian have several hardware specific bugs
4100 on Linux caused by the fact that it is unpredictable when hardware
4101 devices show up during boot. But on the other hand, the new default
4102 boot system still have a few rough edges I hope will be fixed before
4103 Jessie is released.&lt;/p&gt;
4104
4105 &lt;p&gt;Update 2014-11-26: Inspired by
4106 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
4107 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
4108 line.&lt;/p&gt;
4109 </description>
4110 </item>
4111
4112 <item>
4113 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
4114 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
4115 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
4116 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
4117 <description>&lt;p&gt;The right to communicate with your friends and family in private,
4118 without anyone snooping, is a right every citicen have in a liberal
4119 democracy. But this right is under serious attack these days.&lt;/p&gt;
4120
4121 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
4122 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
4123 the whisleblower Snowden) more expensive for Internet email,
4124 is to deliver all email using SMTP via Tor. Such SMTP option would be
4125 a nice addition to the FreedomBox project if we could send email
4126 between FreedomBox machines without leaking metadata about the emails
4127 to the people peeking on the wire. I
4128 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
4129 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
4130 lot of useful feedback and suggestions. It also became obvious to me
4131 that this was not a novel idea, as the same idea was tested and
4132 documented by Johannes Berg as early as 2006, and both
4133 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
4134 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
4135 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
4136
4137 &lt;p&gt;To implement such system one need to set up a Tor hidden service
4138 providing the SMTP protocol on port 25, and use email addresses
4139 looking like username@hidden-service-name.onion. With such addresses
4140 the connections to port 25 on hidden-service-name.onion using Tor will
4141 go to the correct SMTP server. To do this, one need to configure the
4142 Tor daemon to provide the hidden service and the mail server to accept
4143 emails for this .onion domain. To learn more about Exim configuration
4144 in Debian and test the design provided by Johannes Berg in his FAQ, I
4145 set out yesterday to create a Debian package for making it trivial to
4146 set up such SMTP over Tor service based on Debian. Getting it to work
4147 were fairly easy, and
4148 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
4149 source code for the Debian package&lt;/a&gt; is available from github. I
4150 plan to move it into Debian if further testing prove this to be a
4151 useful approach.&lt;/p&gt;
4152
4153 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
4154 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
4155 get rid of exim4). Install tor, clone the git repository mentioned
4156 above, build the deb and install it on the machine. Next, run
4157 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
4158 the instructions to get the service up and running. Restart tor and
4159 exim when it is done, and test mail delivery using swaks like
4160 this:&lt;/p&gt;
4161
4162 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4163 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
4164 --to fbx@dutlqrrmjhtfa3vp.onion
4165 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4166
4167 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
4168 address with your own address to test your server. :)&lt;/p&gt;
4169
4170 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
4171 easier and more automatic. Especially the tor setup need more work.
4172 Also, the package include a tor-smtp tool written in C, but its task
4173 should probably be rewritten in some script language to make the deb
4174 architecture independent. It would probably also make the code easier
4175 to review. The tor-smtp tool currently need to listen on a socket for
4176 exim to talk to it and is started using xinetd. It would be better if
4177 no daemon and no socket is needed. I suspect it is possible to get
4178 exim to run a command line tool for delivery instead of talking to a
4179 socket, and hope to figure out how in a future version of this
4180 system.&lt;/p&gt;
4181
4182 &lt;p&gt;Until I wipe my test machine, I can be reached using the
4183 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
4184 SMTorP. :)&lt;/p&gt;
4185 </description>
4186 </item>
4187
4188 <item>
4189 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
4190 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
4191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
4192 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
4193 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
4194 alioth.debian.org, you know the web interface is fairly slow to
4195 operate. First you visit one web page, enter the moderation password
4196 and get a new page shown with a list of all the messages to moderate
4197 and various options for each email address. This take a while for
4198 every list you moderate, and you need to do it regularly to do a good
4199 job as a list moderator. But there is a quick alternative,
4200 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
4201 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
4202 to moderate in a fraction of a second. Here is a test run on two
4203 lists I recently took over:&lt;/p&gt;
4204
4205 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4206 % time listadmin xiph
4207 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4208 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4209
4210 real 0m1.709s
4211 user 0m0.232s
4212 sys 0m0.012s
4213 %
4214 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4215
4216 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
4217 there are no message in the moderation queue. Every morning I
4218 currently moderate 68 mailman lists, and it normally take around two
4219 minutes. When I took over the two pkg-xiph lists above a few days
4220 ago, there were 400 emails waiting in the moderator queue. It took me
4221 less than 15 minutes to process them all using the listadmin
4222 program.&lt;/p&gt;
4223
4224 &lt;p&gt;If you install
4225 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
4226 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
4227 with content like this, the moderation task is a breeze:&lt;/p&gt;
4228
4229 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4230 username username@example.org
4231 spamlevel 23
4232 default discard
4233 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
4234
4235 password secret
4236 adminurl https://{domain}/mailman/admindb/{list}
4237 mailman-list@lists.example.com
4238
4239 password hidden
4240 other-list@otherserver.example.org
4241 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4242
4243 &lt;p&gt;There are other options to set as well. Check the manual page to
4244 learn the details.&lt;/p&gt;
4245
4246 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
4247 the SSL certificate is self signed or not properly signed by a
4248 generally accepted signing authority, you can set a environment
4249 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
4250
4251 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4252 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
4253 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4254
4255 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
4256 can provide an argument to the listadmin script like I do in the
4257 initial screen dump (the xiph argument). Using an argument, only
4258 lists matching the argument string will be processed. This make it
4259 quick to accept messages if you notice the moderation request in your
4260 email.&lt;/p&gt;
4261
4262 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
4263 mailing lists, as I simply do not have time to spend on that if the
4264 process was any slower. The listadmin program have saved me hours of
4265 time I could spend elsewhere over the years. It truly is nice free
4266 software.&lt;/p&gt;
4267
4268 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4269 activities, please send Bitcoin donations to my address
4270 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4271
4272 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
4273 configuration example. Also, I&#39;ve been told that the
4274 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
4275 sure why.&lt;/p&gt;
4276 </description>
4277 </item>
4278
4279 <item>
4280 <title>Debian Jessie, PXE and automatic firmware installation</title>
4281 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
4282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
4283 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
4284 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
4285 problem that the WiFi card require some firmware to work properly.
4286 And it has been a pain to fix this using preseeding in Debian.
4287 Normally something more is needed. But thanks to
4288 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
4289 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
4290 to do this using simple preseeding.&lt;/p&gt;
4291
4292 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
4293 firmware for the hardware found in the machine (actually, requested by
4294 the kernel modules for the hardware). (It can also install user space
4295 programs supporting the hardware detected, but that is not the focus
4296 of this story.)&lt;/p&gt;
4297
4298 &lt;p&gt;To get this working in the default installation, two preeseding
4299 values are needed. First, the isenkram-cli package must be installed
4300 into the target chroot (aka the hard drive) before tasksel is executed
4301 in the pkgsel step of the debian-installer system. This is done by
4302 preseeding the base-installer/includes debconf value to include the
4303 isenkram-cli package. The package name is next passed to debootstrap
4304 for installation. With the isenkram-cli package in place, tasksel
4305 will automatically use the isenkram tasks to detect hardware specific
4306 packages for the machine being installed and install them, because
4307 isenkram-cli contain tasksel tasks.&lt;/p&gt;
4308
4309 &lt;p&gt;Second, one need to enable the non-free APT repository, because
4310 most firmware unfortunately is non-free. This is done by preseeding
4311 the apt-mirror-setup step. This is unfortunate, but for a lot of
4312 hardware it is the only option in Debian.&lt;/p&gt;
4313
4314 &lt;p&gt;The end result is two lines needed in your preseeding file to get
4315 firmware installed automatically by the installer:&lt;/p&gt;
4316
4317 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4318 base-installer base-installer/includes string isenkram-cli
4319 apt-mirror-setup apt-setup/non-free boolean true
4320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4321
4322 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
4323 both firmware and user space packages when using this method. It also
4324 do not work well, so use version 0.15 or later. Installing both
4325 firmware and user space packages might give you a bit more than you
4326 want, so I decided to split the tasksel task in two, one for firmware
4327 and one for user space programs. The firmware task is enabled by
4328 default, while the one for user space programs is not. This split is
4329 implemented in the package currently in unstable.&lt;/p&gt;
4330
4331 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
4332 this recipe work for you. :)&lt;/p&gt;
4333
4334 &lt;p&gt;So, I bet you are wondering, how can this work. First and
4335 foremost, it work because tasksel is modular, and driven by whatever
4336 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4337 isenkram-cli package place two files for tasksel to find. First there
4338 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
4339
4340 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4341 Task: isenkram-packages
4342 Section: hardware
4343 Description: Hardware specific packages (autodetected by isenkram)
4344 Based on the detected hardware various hardware specific packages are
4345 proposed.
4346 Test-new-install: show show
4347 Relevance: 8
4348 Packages: for-current-hardware
4349
4350 Task: isenkram-firmware
4351 Section: hardware
4352 Description: Hardware specific firmware packages (autodetected by isenkram)
4353 Based on the detected hardware various hardware specific firmware
4354 packages are proposed.
4355 Test-new-install: mark show
4356 Relevance: 8
4357 Packages: for-current-hardware-firmware
4358 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4359
4360 &lt;p&gt;The key parts are Test-new-install which indicate how the task
4361 should be handled and the Packages line referencing to a script in
4362 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4363 list of packages to install. The for-current-hardware-firmware script
4364 look like this to list relevant firmware for the machine:
4365
4366 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4367 #!/bin/sh
4368 #
4369 PATH=/usr/sbin:$PATH
4370 export PATH
4371 isenkram-autoinstall-firmware -l
4372 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4373
4374 &lt;p&gt;With those two pieces in place, the firmware is installed by
4375 tasksel during the normal d-i run. :)&lt;/p&gt;
4376
4377 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
4378 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
4379 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
4380 install.&lt;/p&gt;
4381
4382 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
4383 pilots in testing this feature, as isenkram is used there now to
4384 install firmware, replacing the earlier scripts.&lt;/p&gt;
4385 </description>
4386 </item>
4387
4388 <item>
4389 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
4390 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
4391 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
4392 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
4393 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
4394 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4395 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
4396 on a screen normally showing the bread types and prizes:&lt;/p&gt;
4397
4398 &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;
4399
4400 &lt;p&gt;If it had booted as it was supposed to, I would never had known
4401 about this hidden Linux installation. It is interesting what
4402 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
4403 </description>
4404 </item>
4405
4406 <item>
4407 <title>New lsdvd release version 0.17 is ready</title>
4408 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
4409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
4410 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
4411 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
4412 got a new set of developers a few weeks ago, after the original
4413 developer decided to step down and pass the project to fresh blood.
4414 This project is now maintained by Petter Reinholdtsen and Steve
4415 Dibb.&lt;/p&gt;
4416
4417 &lt;p&gt;I just wrapped up
4418 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
4419 new lsdvd release&lt;/a&gt;, available in git or from
4420 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
4421 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
4422 0.17.&lt;/p&gt;
4423
4424 &lt;ul&gt;
4425
4426 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
4427 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
4428 non-existant, to work around additional copy protection&lt;/li&gt;
4429 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
4430 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
4431 &lt;li&gt;Fix include orders&lt;/li&gt;
4432 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
4433 &lt;li&gt;Fix the chapter count&lt;/li&gt;
4434 &lt;li&gt;Make sure the array size and the array limit used when initialising
4435 the palette size is the same.&lt;/li&gt;
4436 &lt;li&gt;Fix array printing.&lt;/li&gt;
4437 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
4438 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
4439 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
4440 with more GCC compiler warnings.&lt;/li&gt;
4441
4442 &lt;/ul&gt;
4443
4444 &lt;p&gt;This change bring together patches for lsdvd in use in various
4445 Linux and Unix distributions, as well as patches submitted to the
4446 project the last nine years. Please check it out. :)&lt;/p&gt;
4447 </description>
4448 </item>
4449
4450 <item>
4451 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
4452 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
4453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
4454 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
4455 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4456 project&lt;/a&gt; provide a Linux solution for schools, including a
4457 powerful desktop with education software, a central server providing
4458 web pages, user database, user home directories, central login and PXE
4459 boot of both clients without disk and the installation to install Debian
4460 Edu on machines with disk (and a few other services perhaps to small
4461 to mention here). We in the Debian Edu team are currently working on
4462 the Jessie based version, trying to get everything in shape before the
4463 freeze, to avoid having to maintain our own package repository in the
4464 future. The
4465 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
4466 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
4467 work left. Some fatal problems block testing, breaking the installer,
4468 but it is possible to work around these to get anyway. Here is a
4469 recipe on how to get the installation limping along.&lt;/p&gt;
4470
4471 &lt;p&gt;First, download the test ISO via
4472 &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;,
4473 &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;
4474 or rsync (use
4475 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
4476 The ISO build was broken on Tuesday, so we do not get a new ISO every
4477 12 hours or so, but thankfully the ISO we already got we are able to
4478 install with some tweaking.&lt;/p&gt;
4479
4480 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
4481 (use Alt-Ctrl-F2), run&lt;/p&gt;
4482
4483 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4484 nano /usr/bin/edu-eatmydata-install
4485 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4486
4487 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
4488 optimization. Return to the installation, select the profile you want
4489 and continue. Without this change, exim4-config will fail to install
4490 due to a known bug in eatmydata.&lt;/p&gt;
4491
4492 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
4493 this do not work, figure out what your correct value would be. All my
4494 test machines need /dev/sda, so I have no advice if it do not fit
4495 your need.&lt;/p&gt;
4496
4497 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
4498 root after the initial boot from hard drive, and install the
4499 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4500 or mate. If you want several desktop options, install more than one
4501 metapackage. Once this is done, reboot and you should have a working
4502 graphical login screen. This workaround should no longer be needed
4503 once the education-tasks package version 1.801 enter testing in two
4504 days.&lt;/p&gt;
4505
4506 &lt;p&gt;I believe the ISO build will start working on two days when the new
4507 tasksel package enter testing and Steve McIntyre get a chance to
4508 update the debian-cd git repository. The eatmydata, grub and desktop
4509 issues are already fixed in unstable and testing, and should show up
4510 on the ISO as soon as the ISO build start working again. Well the
4511 eatmydata optimization is really just disabled. The proper fix
4512 require an upload by the eatmydata maintainer applying the patch
4513 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4514 The rest have proper fixes in unstable.&lt;/p&gt;
4515
4516 &lt;p&gt;I hope this get you going with the installation testing, as we are
4517 quickly running out of time trying to get our Jessie based
4518 installation ready before the distribution freeze in a month.&lt;/p&gt;
4519 </description>
4520 </item>
4521
4522 <item>
4523 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4524 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4526 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4527 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4528 to handle my fairly large DVD collection. It is a nice command line
4529 tool to get details about a DVD, like title, tracks, track length,
4530 etc, in XML, Perl or human readable format. But lsdvd have not seen
4531 any new development since 2006 and had a few irritating bugs affecting
4532 its use with some DVDs. Upstream seemed to be dead, and in January I
4533 sent a small probe asking for a version control repository for the
4534 project, without any reply. But I use it regularly and would like to
4535 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4536 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4537 the project admin, and after getting a reply from him explaining that
4538 he was no longer interested in the project, I asked if I could take
4539 over. And yesterday, I became project admin.&lt;/p&gt;
4540
4541 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4542 maintainer interested in joining forces to maintain the upstream
4543 project, and I hope we can get a new release out fairly quickly,
4544 collecting the patches spread around on the internet into on place.
4545 I&#39;ve added the relevant Debian patches to the freshly created git
4546 repository, and expect the Gentoo patches to make it too. If you got
4547 a DVD collection and care about command line tools, check out
4548 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4549 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4550 list&lt;/a&gt;. :)&lt;/p&gt;
4551 </description>
4552 </item>
4553
4554 <item>
4555 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4556 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4558 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4559 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4560 a lot quicker. When we install more than 2000 packages in
4561 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4562 tasksel in the installer, unpacking the binary packages take forever.
4563 A part of the slow I/O issue was discussed in
4564 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4565 much file system sync-ing done by dpkg, which is the package
4566 responsible for unpacking the binary packages. Other parts (like code
4567 executed by postinst scripts) might also sync to disk during
4568 installation. All this sync-ing to disk do not really make sense to
4569 me. If the machine crash half-way through, I start over, I do not try
4570 to salvage the half installed system. So the failure sync-ing is
4571 supposed to protect against, hardware or system crash, is not really
4572 relevant while the installer is running.&lt;/p&gt;
4573
4574 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4575 system sync()-ing in a fairly non-intrusive way, without the need to
4576 change the code in several packages. The idea is not new, but I have
4577 not heard anyone propose the approach using dpkg-divert before. It
4578 depend on the small and clever package
4579 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4580 uses LD_PRELOAD to replace the system functions for syncing data to
4581 disk with functions doing nothing, thus allowing programs to live
4582 dangerous while speeding up disk I/O significantly. Instead of
4583 modifying the implementation of dpkg, apt and tasksel (which are the
4584 packages responsible for selecting, fetching and installing packages),
4585 it occurred to me that we could just divert the programs away, replace
4586 them with a simple shell wrapper calling
4587 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4588 Two days ago I decided to test the idea, and wrapped up a simple
4589 implementation for the Debian Edu udeb.&lt;/p&gt;
4590
4591 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4592 time of the pkgsel step (installing tasks) from 64 to less than 44
4593 minutes (20 minutes shaved off the installation) on an old Dell
4594 Latitude D505 machine. I am not quite sure what the optimised time
4595 would have been, as I messed up the testing a bit, causing the debconf
4596 priority to get low enough for two questions to pop up during
4597 installation. As soon as I saw the questions I moved the installation
4598 along, but do not know how long the question were holding up the
4599 installation. I did some more measurements using Debian Edu Jessie,
4600 and got these results. The time measured is the time stamp in
4601 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4602 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4603 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4604 timing thus do not depend on how quickly the user handle the tasksel
4605 dialog.&lt;/p&gt;
4606
4607 &lt;p&gt;&lt;table&gt;
4608
4609 &lt;tr&gt;
4610 &lt;th&gt;Machine/setup&lt;/th&gt;
4611 &lt;th&gt;Original tasksel&lt;/th&gt;
4612 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4613 &lt;th&gt;Reduction&lt;/th&gt;
4614 &lt;/tr&gt;
4615
4616 &lt;tr&gt;
4617 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4618 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4619 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4620 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4621 &lt;/tr&gt;
4622
4623 &lt;tr&gt;
4624 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4625 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4626 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4627 &lt;td&gt;23 min 40%&lt;/td&gt;
4628 &lt;/tr&gt;
4629
4630 &lt;tr&gt;
4631 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4632 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4633 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4634 &lt;td&gt;11 min 50%&lt;/td&gt;
4635 &lt;/tr&gt;
4636
4637 &lt;tr&gt;
4638 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4639 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4640 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4641 &lt;td&gt;2 min 33%&lt;/td&gt;
4642 &lt;/tr&gt;
4643
4644 &lt;tr&gt;
4645 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4646 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4647 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4648 &lt;td&gt;4 min 21%&lt;/td&gt;
4649 &lt;/tr&gt;
4650
4651 &lt;/table&gt;&lt;/p&gt;
4652
4653 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4654 time is spent downloading packages. The connection to the Internet
4655 was 100Mbit/s during testing, so downloading should not be a
4656 significant factor in the measurement. Download typically took a few
4657 seconds to a few minutes, depending on the amount of packages being
4658 installed.&lt;/p&gt;
4659
4660 &lt;p&gt;The speedup is implemented by using two hooks in
4661 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4662 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4663 finish-install.d hook to remove the divert at the end of the
4664 installation. I picked the pre-pkgsel.d hook instead of the
4665 post-base-installer.d hook because I test using an ISO without the
4666 eatmydata package included, and the post-base-installer.d hook in
4667 Debian Edu can only operate on packages included in the ISO. The
4668 negative effect of this is that I am unable to activate this
4669 optimization for the kernel installation step in d-i. If the code is
4670 moved to the post-base-installer.d hook, the speedup would be larger
4671 for the entire installation.&lt;/p&gt;
4672
4673 &lt;p&gt;I&#39;ve implemented this in the
4674 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4675 git repository, and plan to provide the optimization as part of the
4676 Debian Edu installation. If you want to test this yourself, you can
4677 create two files in the installer (or in an udeb). One shell script
4678 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4679
4680 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4681 #!/bin/sh
4682 set -e
4683 . /usr/share/debconf/confmodule
4684 info() {
4685 logger -t my-pkgsel &quot;info: $*&quot;
4686 }
4687 error() {
4688 logger -t my-pkgsel &quot;error: $*&quot;
4689 }
4690 override_install() {
4691 apt-install eatmydata || true
4692 if [ -x /target/usr/bin/eatmydata ] ; then
4693 for bin in dpkg apt-get aptitude tasksel ; do
4694 file=/usr/bin/$bin
4695 # Test that the file exist and have not been diverted already.
4696 if [ -f /target$file ] ; then
4697 info &quot;diverting $file using eatmydata&quot;
4698 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4699 &gt; /target$file.edu
4700 chmod 755 /target$file.edu
4701 in-target dpkg-divert --package debian-edu-config \
4702 --rename --quiet --add $file
4703 ln -sf ./$bin.edu /target$file
4704 else
4705 error &quot;unable to divert $file, as it is missing.&quot;
4706 fi
4707 done
4708 else
4709 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4710 fi
4711 }
4712
4713 override_install
4714 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4715
4716 &lt;p&gt;To clean up, another shell script should go into
4717 /usr/lib/finish-install.d/ with code like this:
4718
4719 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4720 #! /bin/sh -e
4721 . /usr/share/debconf/confmodule
4722 error() {
4723 logger -t my-finish-install &quot;error: $@&quot;
4724 }
4725 remove_install_override() {
4726 for bin in dpkg apt-get aptitude tasksel ; do
4727 file=/usr/bin/$bin
4728 if [ -x /target$file.edu ] ; then
4729 rm /target$file
4730 in-target dpkg-divert --package debian-edu-config \
4731 --rename --quiet --remove $file
4732 rm /target$file.edu
4733 else
4734 error &quot;Missing divert for $file.&quot;
4735 fi
4736 done
4737 sync # Flush file buffers before continuing
4738 }
4739
4740 remove_install_override
4741 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4742
4743 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4744 edu-eatmydata-install and call it from the pre-pkgsel.d and
4745 finish-install.d scripts.&lt;/p&gt;
4746
4747 &lt;p&gt;By now you might ask if this change should get into the normal
4748 Debian installer too? I suspect it should, but am not sure the
4749 current debian-installer coordinators find it useful enough. It also
4750 depend on the side effects of the change. I&#39;m not aware of any, but I
4751 guess we will see if the change is safe after some more testing.
4752 Perhaps there is some package in Debian depending on sync() and
4753 fsync() having effect? Perhaps it should go into its own udeb, to
4754 allow those of us wanting to enable it to do so without affecting
4755 everyone.&lt;/p&gt;
4756
4757 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4758 will break installation of all programs using gnutls because of
4759 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4760 eatmydata package in Debian will solve it.&lt;/p&gt;
4761
4762 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4763 the optimization work again. And I have discovered that the
4764 dpkg-divert trick is not really needed and implemented a slightly
4765 simpler approach as part of the debian-edu-install package. See
4766 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4767
4768 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4769 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4770 triggering on i386 made it into testing, and broke this installation
4771 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4772 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4773 </description>
4774 </item>
4775
4776 <item>
4777 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4778 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4779 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4780 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4781 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4782 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4783 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4784 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4785 learn that there is a large set of publicly available key servers to
4786 use when looking for peoples public key. So far I have used
4787 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4788 were misbehaving, but those days are ended. The servers I have used
4789 up until yesterday have been slow and some times unavailable. I hope
4790 those problems are gone now.&lt;/p&gt;
4791
4792 &lt;p&gt;Behind the round robin DNS entry of the
4793 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4794 there is a pool of more than 100 keyservers which are checked every
4795 day to ensure they are well connected and up to date. It must be
4796 better than what I have used so far. :)&lt;/p&gt;
4797
4798 &lt;p&gt;Yesterdays speaker told me that the service is the default
4799 keyserver provided by the default configuration in GnuPG, but this do
4800 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4801
4802 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4803 line:&lt;/p&gt;
4804
4805 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4806 keyserver pool.sks-keyservers.net
4807 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4808
4809 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4810 entries in DNS. Just for fun, I did just that at work, so now every
4811 user of GnuPG at the University of Oslo should find a OpenGPG
4812 keyserver automatically should their need it:&lt;/p&gt;
4813
4814 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4815 % host -t srv _pgpkey-http._tcp.uio.no
4816 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4817 %
4818 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4819
4820 &lt;p&gt;Now if only
4821 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4822 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4823 very happy. It can look up a given key or search for a user ID, but I
4824 normally do not want that, but to find a trust path from my key to
4825 another key. Given a user ID or key ID, I would like to find (and
4826 download) the keys representing a signature path from my key to the
4827 key in question, to be able to get a trust path between the two keys.
4828 This is as far as I can tell not possible today. Perhaps something
4829 for a future version of the protocol?&lt;/p&gt;
4830 </description>
4831 </item>
4832
4833 <item>
4834 <title>From English wiki to translated PDF and epub via Docbook</title>
4835 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4836 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4837 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4838 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4839 project&lt;/a&gt; provide an instruction manual for teachers, system
4840 administrators and other users that contain useful tips for setting up
4841 and maintaining a Debian Edu installation. This text is about how the
4842 text processing of this manual is handled in the project.&lt;/p&gt;
4843
4844 &lt;p&gt;One goal of the project is to provide information in the native
4845 language of its users, and for this we need to handle translations.
4846 But we also want to make sure each language contain the same
4847 information, so for this we need a good way to keep the translations
4848 in sync. And we want it to be easy for our users to improve the
4849 documentation, avoiding the need to learn special formats or tools to
4850 contribute, and the obvious way to do this is to make it possible to
4851 edit the documentation using a web browser. We also want it to be
4852 easy for translators to keep the translation up to date, and give them
4853 help in figuring out what need to be translated. Here is the list of
4854 tools and the process we have found trying to reach all these
4855 goals.&lt;/p&gt;
4856
4857 &lt;p&gt;We maintain the authoritative source of our manual in the
4858 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4859 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4860 front page with references to the different chapters, several pages
4861 for each chapter, and finally one &quot;collection page&quot; gluing all the
4862 chapters together into one large web page (aka
4863 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4864 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4865 processing and translations. Thanks to the fact that the
4866 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4867 wiki.debian.org support exporting pages in
4868 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4869 the list of pages to export using the raw version of the AllInOne
4870 page, loop over each of them to generate a Docbook XML version of the
4871 manual. This process also download images and transform image
4872 references to use the locally downloaded images. The generated
4873 Docbook XML files are slightly broken, so some post-processing is done
4874 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4875 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4876 a handfull of images. The XML file can now be used to generate PDF, HTML
4877 and epub versions of the English manual. This is the basic step of
4878 our process, making PDF (using dblatex), HTML (using xsltproc) and
4879 epub (using dbtoepub) version from Docbook XML, and the resulting files
4880 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4881
4882 &lt;p&gt;But English documentation is not enough for us. We want translated
4883 documentation too, and we want to make it easy for translators to
4884 track the English original. For this we use the
4885 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4886 which allow us to transform the English Docbook XML file into a
4887 translation file (a .pot file), usable with the normal gettext based
4888 translation tools used by those translating free software. The pot
4889 file is used to create and maintain translation files (several .po
4890 files), which the translations update with the native language
4891 translations of all titles, paragraphs and blocks of text in the
4892 original. The next step is combining the original English Docbook XML
4893 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4894 create a translated Docbook XML file (in this case
4895 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4896 translated, if the translation is not complete) Docbook XML file can
4897 then be used like the original to create a PDF, HTML and epub version
4898 of the documentation.&lt;/p&gt;
4899
4900 &lt;p&gt;The translators use different tools to edit the .po files. We
4901 recommend using
4902 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4903 while some use emacs and vi, others can use web based editors like
4904 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4905 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4906 is where the .po file end up, in our git repository. Updated
4907 translations can either be committed directly to git, or submitted as
4908 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4909 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4910
4911 &lt;p&gt;One challenge is images, which both might need to be translated (if
4912 they show translated user applications), and are needed in different
4913 formats when creating PDF and HTML versions (epub is a HTML version in
4914 this regard). For this we transform the original PNG images to the
4915 needed density and format during build, and have a way to provide
4916 translated images by storing translated versions in
4917 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4918 package maintainers know more.&lt;/p&gt;
4919
4920 &lt;p&gt;If you wonder what the result look like, we provide
4921 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4922 of the documentation packages on the web&lt;/a&gt;. See for example the
4923 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4924 PDF version&lt;/a&gt; or the
4925 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4926 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4927 but perhaps it will be done in the future.&lt;/p&gt;
4928
4929 &lt;p&gt;To learn more, check out
4930 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4931 debian-edu-doc package&lt;/a&gt;,
4932 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4933 manual on the wiki&lt;/a&gt; and
4934 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4935 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4936 </description>
4937 </item>
4938
4939 <item>
4940 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4941 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4942 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4943 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4944 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4945 related packages relevant for the computer installed automatically.
4946 So I implemented one, using
4947 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4948 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4949 run tasksel as user root. You should be presented with a new option,
4950 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4951 select it, tasksel will install the packages isenkram claim is fit for
4952 the current hardware, hot pluggable or not.&lt;p&gt;
4953
4954 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4955 description, and the other is the script used to extract the list of
4956 packages to install. The first part is in
4957 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4958 this:&lt;/p&gt;
4959
4960 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4961 Task: isenkram
4962 Section: hardware
4963 Description: Hardware specific packages (autodetected by isenkram)
4964 Based on the detected hardware various hardware specific packages are
4965 proposed.
4966 Test-new-install: mark show
4967 Relevance: 8
4968 Packages: for-current-hardware
4969 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4970
4971 &lt;p&gt;The second part is in
4972 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4973 this:&lt;/p&gt;
4974
4975 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4976 #!/bin/sh
4977 #
4978 (
4979 isenkram-lookup
4980 isenkram-autoinstall-firmware -l
4981 ) | sort -u
4982 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4983
4984 &lt;p&gt;All in all, a very short and simple implementation making it
4985 trivial to install the hardware dependent package we all may want to
4986 have installed on our machines. I&#39;ve not been able to find a way to
4987 get tasksel to tell you exactly which packages it plan to install
4988 before doing the installation. So if you are curious or careful,
4989 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4990
4991 &lt;p&gt;The information about which packages are handling which hardware is
4992 fetched either from the isenkram package itself in
4993 /usr/share/isenkram/, from git.debian.org or from the APT package
4994 database (using the Modaliases header). The APT package database
4995 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4996 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4997 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4998 the python-apt code (bug
4999 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
5000 workaround I was able to get rid of the file descriptor leak and
5001 reduce the memory leak from ~30 MiB per hardware detection down to
5002 around 2 MiB per hardware detection. It should make the desktop
5003 daemon a lot more useful. The fix is in version 0.7 uploaded to
5004 unstable today.&lt;/p&gt;
5005
5006 &lt;p&gt;I believe the current way of mapping hardware to packages in
5007 Isenkram is is a good draft, but in the future I expect isenkram to
5008 use the AppStream data source for this. A proposal for getting proper
5009 AppStream support into Debian is floating around as
5010 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
5011 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
5012 project&lt;/a&gt; will take place this summer to improve the situation. I
5013 look forward to seeing the result, and welcome patches for isenkram to
5014 start using the information when it is ready.&lt;/p&gt;
5015
5016 &lt;p&gt;If you want your package to map to some specific hardware, either
5017 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
5018 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
5019 package&lt;/a&gt; or submit a bug report with the details to the isenkram
5020 package. See also
5021 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
5022 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
5023 the information will be migrated to AppStream eventually, but for the
5024 moment I got no better place to store it.&lt;/p&gt;
5025 </description>
5026 </item>
5027
5028 <item>
5029 <title>FreedomBox milestone - all packages now in Debian Sid</title>
5030 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
5031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
5032 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
5033 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5034 project&lt;/a&gt; is working on providing the software and hardware to make
5035 it easy for non-technical people to host their data and communication
5036 at home, and being able to communicate with their friends and family
5037 encrypted and away from prying eyes. It is still going strong, and
5038 today a major mile stone was reached.&lt;/p&gt;
5039
5040 &lt;p&gt;Today, the last of the packages currently used by the project to
5041 created the system images were accepted into Debian Unstable. It was
5042 the freedombox-setup package, which is used to configure the images
5043 during build and on the first boot. Now all one need to get going is
5044 the build code from the freedom-maker git repository and packages from
5045 Debian. And once the freedombox-setup package enter testing, we can
5046 build everything directly from Debian. :)&lt;/p&gt;
5047
5048 &lt;p&gt;Some key packages used by Freedombox are
5049 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
5050 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
5051 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
5052 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
5053 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
5054 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
5055 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
5056 are plans to integrate more packages into the setup. User
5057 documentation is maintained on the Debian wiki. Please
5058 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
5059 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
5060
5061 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
5062 setup, run this on a Debian machine using a user with sudo rights to
5063 become root:&lt;/p&gt;
5064
5065 &lt;p&gt;&lt;pre&gt;
5066 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5067 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5068 u-boot-tools
5069 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5070 freedom-maker
5071 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5072 &lt;/pre&gt;&lt;/p&gt;
5073
5074 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5075 devices. See the README in the freedom-maker git repo for more
5076 details on the build. If you do not want all three images, trim the
5077 make line. Note that the virtualbox-image target is not really
5078 virtualbox specific. It create a x86 image usable in kvm, qemu,
5079 vmware and any other x86 virtual machine environment. You might need
5080 the version of vmdebootstrap in Jessie to get the build working, as it
5081 include fixes for a race condition with kpartx.&lt;/p&gt;
5082
5083 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5084 method, boot a Debian Wheezy ISO and use this boot argument to load
5085 the preseed values:&lt;/p&gt;
5086
5087 &lt;p&gt;&lt;pre&gt;
5088 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;
5089 &lt;/pre&gt;&lt;/p&gt;
5090
5091 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
5092 it still work.&lt;/p&gt;
5093
5094 &lt;p&gt;If you wonder how to help, one task you could look at is using
5095 systemd as the boot system. It will become the default for Linux in
5096 Jessie, so we need to make sure it is usable on the Freedombox. I did
5097 a simple test a few weeks ago, and noticed dnsmasq failed to start
5098 during boot when using systemd. I suspect there are other problems
5099 too. :) To detect problems, there is a test suite included, which can
5100 be run from the plinth web interface.&lt;/p&gt;
5101
5102 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5103 us get the new release published. :) Please join us on
5104 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5105 irc.debian.org)&lt;/a&gt; and
5106 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5107 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5108 </description>
5109 </item>
5110
5111 <item>
5112 <title>S3QL, a locally mounted cloud file system - nice free software</title>
5113 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
5114 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
5115 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
5116 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
5117 solution for use at home. My requirements are simple, it must be
5118 cheap and locally encrypted (in other words, I keep the encryption
5119 keys, the storage provider do not have access to my private files).
5120 One idea me and my friends had many years ago, before the cloud
5121 storage providers showed up, was to use Google mail as storage,
5122 writing a Linux block device storing blocks as emails in the mail
5123 service provided by Google, and thus get heaps of free space. On top
5124 of this one can add encryption, RAID and volume management to have
5125 lots of (fairly slow, I admit that) cheap and encrypted storage. But
5126 I never found time to implement such system. But the last few weeks I
5127 have looked at a system called
5128 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
5129 mounted network backed file system with the features I need.&lt;/p&gt;
5130
5131 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
5132 handling several different storage providers, any with Amazon S3,
5133 Google Drive or OpenStack API. There are heaps of such storage
5134 providers. S3QL can also use a local directory as storage, which
5135 combined with sshfs allow for file storage on any ssh server. S3QL
5136 include support for encryption, compression, de-duplication, snapshots
5137 and immutable file systems, allowing me to mount the remote storage as
5138 a local mount point, look at and use the files as if they were local,
5139 while the content is stored in the cloud as well. This allow me to
5140 have a backup that should survive fire. The file system can not be
5141 shared between several machines at the same time, as only one can
5142 mount it at the time, but any machine with the encryption key and
5143 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
5144
5145 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
5146 package is included already. So to get started, run &lt;tt&gt;apt-get
5147 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
5148 Greenqloud, after reading their nice recipe on
5149 &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
5150 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
5151 in Iceland more than those in USA when it come to keeping my personal
5152 data safe and private, and thus would rather spend money on a company
5153 in Iceland. Another nice recipe is available from the article
5154 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
5155 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
5156 Admin magazine. When the provider is picked, figure out how to get
5157 the API key needed to connect to the storage API. With Greencloud,
5158 the key did not show up until I had added payment details to my
5159 account.&lt;/p&gt;
5160
5161 &lt;p&gt;Armed with the API access details, it is time to create the file
5162 system. First, create a new bucket in the cloud. This bucket is the
5163 file system storage area. I picked a bucket name reflecting the
5164 machine that was going to store data there, but any name will do.
5165 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
5166 the API login and password, and a locally created password. Store it
5167 all in ~root/.s3ql/authinfo2 like this:
5168
5169 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5170 [s3c]
5171 storage-url: s3c://s.greenqloud.com:443/bucket-name
5172 backend-login: API-login
5173 backend-password: API-password
5174 fs-passphrase: local-password
5175 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5176
5177 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
5178 but any sensible way to create a fairly random password should do it.
5179 Armed with these details, it is now time to run mkfs, entering the API
5180 details and password to create it:&lt;/p&gt;
5181
5182 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5183 # mkdir -m 700 /var/lib/s3ql-cache
5184 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5185 --ssl s3c://s.greenqloud.com:443/bucket-name
5186 Enter backend login:
5187 Enter backend password:
5188 Before using S3QL, make sure to read the user&#39;s guide, especially
5189 the &#39;Important Rules to Avoid Loosing Data&#39; section.
5190 Enter encryption password:
5191 Confirm encryption password:
5192 Generating random encryption key...
5193 Creating metadata tables...
5194 Dumping metadata...
5195 ..objects..
5196 ..blocks..
5197 ..inodes..
5198 ..inode_blocks..
5199 ..symlink_targets..
5200 ..names..
5201 ..contents..
5202 ..ext_attributes..
5203 Compressing and uploading metadata...
5204 Wrote 0.00 MB of compressed metadata.
5205 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5206
5207 &lt;p&gt;The next step is mounting the file system to make the storage available.
5208
5209 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5210 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5211 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5212 Using 4 upload threads.
5213 Downloading and decompressing metadata...
5214 Reading metadata...
5215 ..objects..
5216 ..blocks..
5217 ..inodes..
5218 ..inode_blocks..
5219 ..symlink_targets..
5220 ..names..
5221 ..contents..
5222 ..ext_attributes..
5223 Mounting filesystem...
5224 # df -h /s3ql
5225 Filesystem Size Used Avail Use% Mounted on
5226 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
5227 #
5228 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5229
5230 &lt;p&gt;The file system is now ready for use. I use rsync to store my
5231 backups in it, and as the metadata used by rsync is downloaded at
5232 mount time, no network traffic (and storage cost) is triggered by
5233 running rsync. To unmount, one should not use the normal umount
5234 command, as this will not flush the cache to the cloud storage, but
5235 instead running the umount.s3ql command like this:
5236
5237 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5238 # umount.s3ql /s3ql
5239 #
5240 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5241
5242 &lt;p&gt;There is a fsck command available to check the file system and
5243 correct any problems detected. This can be used if the local server
5244 crashes while the file system is mounted, to reset the &quot;already
5245 mounted&quot; flag. This is what it look like when processing a working
5246 file system:&lt;/p&gt;
5247
5248 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5249 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
5250 Using cached metadata.
5251 File system seems clean, checking anyway.
5252 Checking DB integrity...
5253 Creating temporary extra indices...
5254 Checking lost+found...
5255 Checking cached objects...
5256 Checking names (refcounts)...
5257 Checking contents (names)...
5258 Checking contents (inodes)...
5259 Checking contents (parent inodes)...
5260 Checking objects (reference counts)...
5261 Checking objects (backend)...
5262 ..processed 5000 objects so far..
5263 ..processed 10000 objects so far..
5264 ..processed 15000 objects so far..
5265 Checking objects (sizes)...
5266 Checking blocks (referenced objects)...
5267 Checking blocks (refcounts)...
5268 Checking inode-block mapping (blocks)...
5269 Checking inode-block mapping (inodes)...
5270 Checking inodes (refcounts)...
5271 Checking inodes (sizes)...
5272 Checking extended attributes (names)...
5273 Checking extended attributes (inodes)...
5274 Checking symlinks (inodes)...
5275 Checking directory reachability...
5276 Checking unix conventions...
5277 Checking referential integrity...
5278 Dropping temporary indices...
5279 Backing up old metadata...
5280 Dumping metadata...
5281 ..objects..
5282 ..blocks..
5283 ..inodes..
5284 ..inode_blocks..
5285 ..symlink_targets..
5286 ..names..
5287 ..contents..
5288 ..ext_attributes..
5289 Compressing and uploading metadata...
5290 Wrote 0.89 MB of compressed metadata.
5291 #
5292 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5293
5294 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
5295 quick, about the same speed as local file access. Uploading large
5296 amount of data is to me limited by the bandwidth out of and into my
5297 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
5298 which is very close to my upload speed, and downloading the same
5299 Debian installation ISO gave me 610 kiB/s, close to my download speed.
5300 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
5301 network, not the file system code. I do not know what a good cache
5302 size would be, but suspect that the cache should e larger than your
5303 working set.&lt;/p&gt;
5304
5305 &lt;p&gt;I mentioned that only one machine can mount the file system at the
5306 time. If another machine try, it is told that the file system is
5307 busy:&lt;/p&gt;
5308
5309 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5310 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5311 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5312 Using 8 upload threads.
5313 Backend reports that fs is still mounted elsewhere, aborting.
5314 #
5315 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5316
5317 &lt;p&gt;The file content is uploaded when the cache is full, while the
5318 metadata is uploaded once every 24 hour by default. To ensure the
5319 file system content is flushed to the cloud, one can either umount the
5320 file system, or ask S3QL to flush the cache and metadata using
5321 s3qlctrl:
5322
5323 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5324 # s3qlctrl upload-meta /s3ql
5325 # s3qlctrl flushcache /s3ql
5326 #
5327 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5328
5329 &lt;p&gt;If you are curious about how much space your data uses in the
5330 cloud, and how much compression and deduplication cut down on the
5331 storage usage, you can use s3qlstat on the mounted file system to get
5332 a report:&lt;/p&gt;
5333
5334 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5335 # s3qlstat /s3ql
5336 Directory entries: 9141
5337 Inodes: 9143
5338 Data blocks: 8851
5339 Total data size: 22049.38 MB
5340 After de-duplication: 21955.46 MB (99.57% of total)
5341 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
5342 Database size: 2.39 MB (uncompressed)
5343 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5344 #
5345 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5346
5347 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
5348 storage. I did not try to locate them all, but am aware of at least
5349 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
5350 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
5351 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
5352 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
5353 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
5354 accept payment in Bitcoin. Pick one that suit your need. Some of
5355 them provide several GiB of free storage, but the prize models are
5356 quite different and you will have to figure out what suits you
5357 best.&lt;/p&gt;
5358
5359 &lt;p&gt;While researching this blog post, I had a look at research papers
5360 and posters discussing the S3QL file system. There are several, which
5361 told me that the file system is getting a critical check by the
5362 science community and increased my confidence in using it. One nice
5363 poster is titled
5364 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
5365 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5366 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
5367 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5368 and Pamela Smith. Please have a look.&lt;/p&gt;
5369
5370 &lt;p&gt;Given my problems with different file systems earlier, I decided to
5371 check out the mounted S3QL file system to see if it would be usable as
5372 a home directory (in other word, that it provided POSIX semantics when
5373 it come to locking and umask handling etc). Running
5374 &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
5375 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
5376 no error was found. So the file system can be used for home
5377 directories, if one chooses to do so.&lt;/p&gt;
5378
5379 &lt;p&gt;If you do not want a locally file system, and want something that
5380 work without the Linux fuse file system, I would like to mention the
5381 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
5382 provide locally encrypted backup using a command line client. It have
5383 a nicer access control system, where one can split out read and write
5384 access, allowing some systems to write to the backup and others to
5385 only read from it.&lt;/p&gt;
5386
5387 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5388 activities, please send Bitcoin donations to my address
5389 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5390 </description>
5391 </item>
5392
5393 <item>
5394 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
5395 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
5396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
5397 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
5398 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5399 project&lt;/a&gt; is working on providing the software and hardware for
5400 making it easy for non-technical people to host their data and
5401 communication at home, and being able to communicate with their
5402 friends and family encrypted and away from prying eyes. It has been
5403 going on for a while, and is slowly progressing towards a new test
5404 release (0.2).&lt;/p&gt;
5405
5406 &lt;p&gt;And what day could be better than the Pi day to announce that the
5407 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
5408 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5409 system), and can also be installed using a Debian installer preseed
5410 file. The Debian based Freedombox is now based on Debian Jessie,
5411 where most of the needed packages used are already present. Only one,
5412 the freedombox-setup package, is missing. To try to build your own
5413 boot image to test the current status, fetch the freedom-maker scripts
5414 and build using
5415 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
5416 with a user with sudo access to become root:
5417
5418 &lt;pre&gt;
5419 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5420 freedom-maker
5421 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5422 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5423 u-boot-tools
5424 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5425 &lt;/pre&gt;
5426
5427 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5428 devices. See the README for more details on the build. If you do not
5429 want all three images, trim the make line. But note that thanks to &lt;a
5430 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
5431 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
5432 kpartx call.&lt;/p&gt;
5433
5434 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5435 method, boot a Debian Wheezy ISO and use this boot argument to load
5436 the preseed values:&lt;/p&gt;
5437
5438 &lt;pre&gt;
5439 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;
5440 &lt;/pre&gt;
5441
5442 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
5443 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
5444 currently hang while setting up APT sources. Killing the
5445 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
5446 installation will get the installation going. This affect all
5447 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
5448
5449 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5450 us get the new release published. :) Please join us on
5451 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5452 irc.debian.org)&lt;/a&gt; and
5453 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5454 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5455 </description>
5456 </item>
5457
5458 <item>
5459 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
5460 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
5461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
5462 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
5463 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
5464 innetgr tools, because I needed them in
5465 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
5466 ng-utils, and it has served me well. I placed the project under the
5467 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
5468 repository. But many years ago, the CVS repository was dropped (lost,
5469 not migrated to new hardware, not sure), and the project have lacked a
5470 proper home since then.&lt;/p&gt;
5471
5472 &lt;p&gt;Last summer, I had a look at the package and made a new release
5473 fixing a irritating crash bug, but was unable to store the changes in
5474 a proper source control system. I applied for a project on
5475 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
5476 to follow up on it. Until today. :)&lt;/p&gt;
5477
5478 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
5479 now have a new home, and a git repository with the highlight of the
5480 history of the project. I published all release tarballs and imported
5481 them into the git repository. As the project is really stable and not
5482 expected to gain new features any time soon, I decided to make a new
5483 release and call it 1.0. Visit the new project home on
5484 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
5485 if you want to check it out. The new version is also uploaded into
5486 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
5487 </description>
5488 </item>
5489
5490 <item>
5491 <title>Testing sysvinit from experimental in Debian Hurd</title>
5492 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
5493 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
5494 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
5495 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
5496 their changes into sysvinit, to allow them to use the normal sysvinit
5497 boot system instead of their old one. This follow up on the
5498 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
5499 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
5500 get Debian on Hurd working more like Debian on Linux. To get started,
5501 I downloaded a prebuilt hard disk image from
5502 &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;,
5503 and started it using virt-manager.&lt;/p&gt;
5504
5505 &lt;p&gt;The first think I had to do after logging in (root without any
5506 password) was to get the network operational. I followed
5507 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5508 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5509 commands as root to get the machine to accept a IP address from the
5510 kvm internal DHCP server:&lt;/p&gt;
5511
5512 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5513 settrans -fgap /dev/netdde /hurd/netdde
5514 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5515 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5516 dhclient /dev/eth0
5517 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5518
5519 &lt;p&gt;After this, the machine had internet connectivity, and I could
5520 upgrade it and install the sysvinit packages from experimental and
5521 enable it as the default boot system in Hurd.&lt;/p&gt;
5522
5523 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5524 running on the machine it for ssh login to work a password need to be
5525 set. Also, note that a bug somewhere in openssh on Hurd block
5526 compression from working. Remember to turn that off on the client
5527 side.&lt;/p&gt;
5528
5529 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5530 stuff:&lt;/p&gt;
5531
5532 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5533 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5534 deb http://http.debian.net/debian/ experimental main
5535 EOF
5536 apt-get update
5537 apt-get dist-upgrade
5538 apt-get install -t experimental initscripts sysv-rc sysvinit \
5539 sysvinit-core sysvinit-utils
5540 update-alternatives --config runsystem
5541 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5542
5543 &lt;p&gt;To reboot after switching boot system, you have to use
5544 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5545 yet a sysvinit process able to receive the signals from the normal
5546 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5547 upgrading every package and rebooting, the network come up with DHCP
5548 after boot as it should, and the settrans/pkill hack mentioned at the
5549 start is no longer needed. But for some strange reason, there are no
5550 longer any login prompt in the virtual console, so I logged in using
5551 ssh instead.
5552
5553 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5554 fail some times. No idea what the cause is, but hope the Hurd porters
5555 figure it out. At least Justus said on IRC (#debian-hurd on
5556 irc.debian.org) that they are aware of the problem. A way to reduce
5557 the impact is to upgrade to the Hurd packages built by Justus by
5558 adding this repository to the machine:&lt;/p&gt;
5559
5560 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5561 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5562 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5563 EOF
5564 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5565
5566 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5567 http://ftp.debian-ports.org/debian, because some of the packages in
5568 unstable do not yet include the required patches that are lingering in
5569 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5570
5571 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5572 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5573 i emacs - GNU Emacs editor (metapackage)
5574 i gdb - GNU Debugger
5575 i hurd-recommended - Miscellaneous translators
5576 i isc-dhcp-client - ISC DHCP client
5577 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5578 i libc-bin - Embedded GNU C Library: Binaries
5579 i libc-dev-bin - Embedded GNU C Library: Development binaries
5580 i libc0.3 - Embedded GNU C Library: Shared libraries
5581 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5582 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5583 i multiarch-support - Transitional package to ensure multiarch compatibilit
5584 i A x11-common - X Window System (X.Org) infrastructure
5585 i xorg - X.Org X Window System
5586 i A xserver-xorg - X.Org X server
5587 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5588 #
5589 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5590
5591 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5592 X.org did not work out of the box and I never took the time to follow
5593 the porters instructions to fix it. This time I was interested in the
5594 command line stuff.&lt;p&gt;
5595 </description>
5596 </item>
5597
5598 <item>
5599 <title>New chrpath release 0.16</title>
5600 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5601 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5602 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5603 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5604 find problems in C, C++ and Java code using static source code
5605 analysis. It can detect a lot of different problems, and is very
5606 useful to find memory and locking bugs in the error handling part of
5607 the source. The company behind it provide
5608 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5609 a community service&lt;/a&gt;, and many hundred free software projects are
5610 already checked. A few days ago I decided to have a closer look at
5611 the Coverity system, and discovered that the
5612 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5613 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5614 projects I am involved with was already registered. But these are
5615 fairly big, and I would also like to have a small and easy project to
5616 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5617 checking of the chrpath project&lt;/a&gt;. It was
5618 added to the checker and discovered seven potential defects. Six of
5619 these were real, mostly resource &quot;leak&quot; when the program detected an
5620 error. Nothing serious, as the resources would be released a fraction
5621 of a second later when the program exited because of the error, but it
5622 is nice to do it right in case the source of the program some time in
5623 the future end up in a library. Having fixed all defects and added
5624 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5625 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5626 publish a new release. These are the release notes:&lt;/p&gt;
5627
5628 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5629
5630 &lt;ul&gt;
5631
5632 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5633 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5634 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5635
5636 &lt;/ul&gt;
5637
5638 &lt;p&gt;You can
5639 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5640 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5641 project if something is wrong with the new release. The test suite
5642 did not discover any old errors, so if you find a new one, please also
5643 include a test suite check.&lt;/p&gt;
5644 </description>
5645 </item>
5646
5647 <item>
5648 <title>New chrpath release 0.15</title>
5649 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5650 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5651 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5652 <description>&lt;p&gt;After many years break from the package and a vain hope that
5653 development would be continued by someone else, I finally pulled my
5654 acts together this morning and wrapped up a new release of chrpath,
5655 the command line tool to modify the rpath and runpath of already
5656 compiled ELF programs. The update was triggered by the persistence of
5657 Isha Vishnoi at IBM, which needed a new config.guess file to get
5658 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5659 is working on. I checked the
5660 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5661 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5662 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5663 packages for interesting patches (failed to find the source from
5664 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5665 These are the release notes:&lt;/p&gt;
5666
5667 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5668
5669 &lt;ul&gt;
5670
5671 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5672 with newer architectures. Thanks to isha vishnoi for the heads
5673 up.&lt;/li&gt;
5674
5675 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5676
5677 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5678 Matthias Klose.&lt;/li&gt;
5679
5680 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5681 Petr Machata found in Fedora.&lt;/li&gt;
5682
5683 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5684 .dynamic is a NULL terminated string. Based on patch found in
5685 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5686
5687 &lt;/ul&gt;
5688
5689 &lt;p&gt;You can
5690 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5691 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5692 project if something is wrong with the new release. The test suite
5693 did not discover any old errors, so if you find a new one, please also
5694 include a testsuite check.&lt;/p&gt;
5695 </description>
5696 </item>
5697
5698 <item>
5699 <title>Debian init.d boot script example for rsyslog</title>
5700 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5701 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5702 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5703 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5704 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5705 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5706 init.d scripts at all. Here is an example init.d script, ie a rewrite
5707 of /etc/init.d/rsyslog:&lt;/p&gt;
5708
5709 &lt;p&gt;&lt;pre&gt;
5710 #!/lib/init/init-d-script
5711 ### BEGIN INIT INFO
5712 # Provides: rsyslog
5713 # Required-Start: $remote_fs $time
5714 # Required-Stop: umountnfs $time
5715 # X-Stop-After: sendsigs
5716 # Default-Start: 2 3 4 5
5717 # Default-Stop: 0 1 6
5718 # Short-Description: enhanced syslogd
5719 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5720 # It is quite compatible to stock sysklogd and can be
5721 # used as a drop-in replacement.
5722 ### END INIT INFO
5723 DESC=&quot;enhanced syslogd&quot;
5724 DAEMON=/usr/sbin/rsyslogd
5725 &lt;/pre&gt;&lt;/p&gt;
5726
5727 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5728 script was 137 lines, and the above is just 15 lines, most of it meta
5729 info/comments.&lt;/p&gt;
5730
5731 &lt;p&gt;How to do this, you ask? Well, one create a new script
5732 /lib/init/init-d-script looking something like this:
5733
5734 &lt;p&gt;&lt;pre&gt;
5735 #!/bin/sh
5736
5737 # Define LSB log_* functions.
5738 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5739 # and status_of_proc is working.
5740 . /lib/lsb/init-functions
5741
5742 #
5743 # Function that starts the daemon/service
5744
5745 #
5746 do_start()
5747 {
5748 # Return
5749 # 0 if daemon has been started
5750 # 1 if daemon was already running
5751 # 2 if daemon could not be started
5752 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5753 || return 1
5754 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5755 $DAEMON_ARGS \
5756 || return 2
5757 # Add code here, if necessary, that waits for the process to be ready
5758 # to handle requests from services started subsequently which depend
5759 # on this one. As a last resort, sleep for some time.
5760 }
5761
5762 #
5763 # Function that stops the daemon/service
5764 #
5765 do_stop()
5766 {
5767 # Return
5768 # 0 if daemon has been stopped
5769 # 1 if daemon was already stopped
5770 # 2 if daemon could not be stopped
5771 # other if a failure occurred
5772 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5773 RETVAL=&quot;$?&quot;
5774 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5775 # Wait for children to finish too if this is a daemon that forks
5776 # and if the daemon is only ever run from this initscript.
5777 # If the above conditions are not satisfied then add some other code
5778 # that waits for the process to drop all resources that could be
5779 # needed by services started subsequently. A last resort is to
5780 # sleep for some time.
5781 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5782 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5783 # Many daemons don&#39;t delete their pidfiles when they exit.
5784 rm -f $PIDFILE
5785 return &quot;$RETVAL&quot;
5786 }
5787
5788 #
5789 # Function that sends a SIGHUP to the daemon/service
5790 #
5791 do_reload() {
5792 #
5793 # If the daemon can reload its configuration without
5794 # restarting (for example, when it is sent a SIGHUP),
5795 # then implement that here.
5796 #
5797 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5798 return 0
5799 }
5800
5801 SCRIPTNAME=$1
5802 scriptbasename=&quot;$(basename $1)&quot;
5803 echo &quot;SN: $scriptbasename&quot;
5804 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5805 script=&quot;$1&quot;
5806 shift
5807 . $script
5808 else
5809 exit 0
5810 fi
5811
5812 NAME=$(basename $DAEMON)
5813 PIDFILE=/var/run/$NAME.pid
5814
5815 # Exit if the package is not installed
5816 #[ -x &quot;$DAEMON&quot; ] || exit 0
5817
5818 # Read configuration variable file if it is present
5819 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5820
5821 # Load the VERBOSE setting and other rcS variables
5822 . /lib/init/vars.sh
5823
5824 case &quot;$1&quot; in
5825 start)
5826 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5827 do_start
5828 case &quot;$?&quot; in
5829 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5830 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5831 esac
5832 ;;
5833 stop)
5834 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5835 do_stop
5836 case &quot;$?&quot; in
5837 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5838 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5839 esac
5840 ;;
5841 status)
5842 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5843 ;;
5844 #reload|force-reload)
5845 #
5846 # If do_reload() is not implemented then leave this commented out
5847 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5848 #
5849 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5850 #do_reload
5851 #log_end_msg $?
5852 #;;
5853 restart|force-reload)
5854 #
5855 # If the &quot;reload&quot; option is implemented then remove the
5856 # &#39;force-reload&#39; alias
5857 #
5858 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5859 do_stop
5860 case &quot;$?&quot; in
5861 0|1)
5862 do_start
5863 case &quot;$?&quot; in
5864 0) log_end_msg 0 ;;
5865 1) log_end_msg 1 ;; # Old process is still running
5866 *) log_end_msg 1 ;; # Failed to start
5867 esac
5868 ;;
5869 *)
5870 # Failed to stop
5871 log_end_msg 1
5872 ;;
5873 esac
5874 ;;
5875 *)
5876 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5877 exit 3
5878 ;;
5879 esac
5880
5881 :
5882 &lt;/pre&gt;&lt;/p&gt;
5883
5884 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5885 lot. I did not really polish the approach, so it might not always
5886 work out of the box, but you get the idea. I did not try very hard to
5887 optimize it nor make it more robust either.&lt;/p&gt;
5888
5889 &lt;p&gt;A better argument for switching init system in Debian than reducing
5890 the size of init scripts (which is a good thing to do anyway), is to
5891 get boot system that is able to handle the kernel events sensibly and
5892 robustly, and do not depend on the boot to run sequentially. The boot
5893 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5894 </description>
5895 </item>
5896
5897 <item>
5898 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5899 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5901 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5902 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5903 remote display access is the preferred solution with oVirt and RedHat
5904 Enterprise Virtualization, and I was sad to discover the other day
5905 that the browser plugin needed to use these systems seamlessly was
5906 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5907 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5908 2013-04-01, so I decided to wrap up a package based on the great work
5909 from Cajus Pollmeier and put it in a collab-maint maintained git
5910 repository to get a package I could use. I would very much like
5911 others to help me maintain the package (or just take over, I do not
5912 mind), but as no-one had volunteered so far, I just uploaded it to
5913 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5914
5915 &lt;p&gt;The source is now available from
5916 &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;
5917 </description>
5918 </item>
5919
5920 <item>
5921 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5922 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5924 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5925 <description>&lt;p&gt;The
5926 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5927 program is a a very nice system to create virtual machine images. It
5928 create a image file, add a partition table, mount it and run
5929 debootstrap in the mounted directory to create a Debian system on a
5930 stick. Yesterday, I decided to try to teach it how to make images for
5931 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5932 of a plan to simplify the build system for
5933 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5934 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5935 the virtualbox images, but its current build system made multistrap
5936 based system for Dreamplug images, and it is lacking support for
5937 Raspberry Pi.&lt;/p&gt;
5938
5939 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5940 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5941 code and adjusted it to be able to build armel images on my amd64
5942 Debian laptop. I ended up giving vmdebootstrap five new options,
5943 allowing me to replicate the image creation process I use to make
5944 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5945 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5946 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5947 call debootstrap with --foreign and to copy the handler into the
5948 generated chroot before running the second stage. This allow
5949 vmdebootstrap to create armel images on an amd64 host. Next I added
5950 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5951 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5952 given file system type, allowing me to create an image with a vfat
5953 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5954 variant&lt;/tt&gt; option to allow me to create smaller images without the
5955 Debian base system packages installed. Finally, I added an option
5956 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5957 as a boot loader. It is not needed on the Raspberry Pi and probably
5958 most other non-x86 architectures. The changes were accepted by the
5959 upstream author of vmdebootstrap yesterday and today, and is now
5960 available from
5961 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5962 upstream project page&lt;/a&gt;.&lt;/p&gt;
5963
5964 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5965 create a small script (the customize script) to add the non-free
5966 binary blob needed to boot the Raspberry Pi and the APT source
5967 list:&lt;/p&gt;
5968
5969 &lt;p&gt;&lt;pre&gt;
5970 #!/bin/sh
5971 set -e # Exit on first error
5972 rootdir=&quot;$1&quot;
5973 cd &quot;$rootdir&quot;
5974 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5975 deb http://http.debian.net/debian/ jessie main contrib non-free
5976 EOF
5977 # Install non-free binary blob needed to boot Raspberry Pi. This
5978 # install a kernel somewhere too.
5979 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5980 -O $rootdir/usr/bin/rpi-update
5981 chmod a+x $rootdir/usr/bin/rpi-update
5982 mkdir -p $rootdir/lib/modules
5983 touch $rootdir/boot/start.elf
5984 chroot $rootdir rpi-update
5985 &lt;/pre&gt;&lt;/p&gt;
5986
5987 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5988 to build the image:&lt;/p&gt;
5989
5990 &lt;pre&gt;
5991 sudo ./vmdebootstrap \
5992 --variant minbase \
5993 --arch armel \
5994 --distribution jessie \
5995 --mirror http://http.debian.net/debian \
5996 --image test.img \
5997 --size 600M \
5998 --bootsize 64M \
5999 --boottype vfat \
6000 --log-level debug \
6001 --verbose \
6002 --no-kernel \
6003 --no-extlinux \
6004 --root-password raspberry \
6005 --hostname raspberrypi \
6006 --foreign /usr/bin/qemu-arm-static \
6007 --customize `pwd`/customize \
6008 --package netbase \
6009 --package git-core \
6010 --package binutils \
6011 --package ca-certificates \
6012 --package wget \
6013 --package kmod
6014 &lt;/pre&gt;&lt;/p&gt;
6015
6016 &lt;p&gt;The list of packages being installed are the ones needed by
6017 rpi-update to make the image bootable on the Raspberry Pi, with the
6018 exception of netbase, which is needed by debootstrap to find
6019 /etc/hosts with the minbase variant. I really wish there was a way to
6020 set up an Raspberry Pi using only packages in the Debian archive, but
6021 that is not possible as far as I know, because it boots from the GPU
6022 using a non-free binary blob.&lt;/p&gt;
6023
6024 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
6025 probably a few others installed. I have not checked the complete
6026 build dependency list.&lt;/p&gt;
6027
6028 &lt;p&gt;The resulting image will not use the hardware floating point unit
6029 on the Raspberry PI, because the armel architecture in Debian is not
6030 optimized for that use. So the images created will be a bit slower
6031 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
6032 </description>
6033 </item>
6034
6035 <item>
6036 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
6037 <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>
6038 <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>
6039 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
6040 <description>&lt;p&gt;The last few days I came across a few good causes that should get
6041 wider attention. I recommend signing and donating to each one of
6042 these. :)&lt;/p&gt;
6043
6044 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
6045 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
6046 Women program which is a Google Summer of Code like initiative to get
6047 more women involved in free software. One debian sponsor has offered
6048 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
6049 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
6050 hope you will to. :)&lt;/p&gt;
6051
6052 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
6053 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
6054 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
6055 take place these days, and their need to fund the work. I&#39;ve already
6056 donated. Are you next?&lt;/p&gt;
6057
6058 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
6059 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
6060 statement under the heading
6061 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
6062 Access&lt;/a&gt; for those of us asking for more focus on open access in the
6063 Norwegian government. So far 499 signatures. I hope you will sign it
6064 too.&lt;/p&gt;
6065 </description>
6066 </item>
6067
6068 <item>
6069 <title>Videos about the Freedombox project - for inspiration and learning</title>
6070 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
6071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
6072 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
6073 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
6074 project&lt;/a&gt; have been going on for a while, and have presented the
6075 vision, ideas and solution several places. Here is a little
6076 collection of videos of talks and presentation of the project.&lt;/p&gt;
6077
6078 &lt;ul&gt;
6079
6080 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
6081 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
6082
6083 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
6084 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6085
6086 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
6087 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6088 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
6089 (Youtube)&lt;/li&gt;
6090
6091 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
6092 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
6093
6094 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
6095 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6096
6097 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
6098 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6099 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
6100
6101 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
6102 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
6103 (Youtube)&lt;/li&gt;
6104
6105 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
6106 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
6107
6108 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
6109 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
6110
6111 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
6112 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
6113 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
6114
6115 &lt;/ul&gt;
6116
6117 &lt;p&gt;A larger list is available from
6118 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
6119 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
6120
6121 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
6122 Jessie is coming along quite well, and soon both Owncloud and using
6123 Tor should be available for testers of the Freedombox solution. :) In
6124 a few weeks I hope everything needed to test it is included in Debian.
6125 The withsqlite package is already in Debian, and the plinth package is
6126 pending in NEW. The third and vital part of that puzzle is the
6127 metapackage/setup framework, which is still pending an upload. Join
6128 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
6129 (#freedombox on irc.debian.org)&lt;/a&gt; and
6130 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6131 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6132 </description>
6133 </item>
6134
6135 <item>
6136 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
6137 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
6138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
6139 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
6140 <description>&lt;p&gt;I was introduced to the
6141 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
6142 in 2010, when Eben Moglen presented his vision about serving the need
6143 of non-technical people to keep their personal information private and
6144 within the legal protection of their own homes. The idea is to give
6145 people back the power over their network and machines, and return
6146 Internet back to its intended peer-to-peer architecture. Instead of
6147 depending on a central service, the Freedombox will give everyone
6148 control over their own basic infrastructure.&lt;/p&gt;
6149
6150 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
6151 taken priority. But this summers nasty news about the misuse of trust
6152 and privilege exercised by the &quot;western&quot; intelligence gathering
6153 communities increased my eagerness to contribute to a point where I
6154 actually started working on the project a while back.&lt;/p&gt;
6155
6156 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
6157 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
6158 create a simple and cheap Debian based appliance that anyone can hook
6159 up in their home and get access to secure and private services and
6160 communication. The initial deployment platform have been the
6161 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
6162 which is a piece of hardware I do not own. So to be able to test what
6163 the current Freedombox setup look like, I had to come up with a way to install
6164 it on some hardware I do have access to. I have rewritten the
6165 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
6166 image build framework to use .deb packages instead of only copying
6167 setup into the boot images, and thanks to this rewrite I am able to
6168 set up any machine supported by Debian Wheezy as a Freedombox, using
6169 the previously mentioned deb (and a few support debs for packages
6170 missing in Debian).&lt;/p&gt;
6171
6172 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
6173 scripts
6174 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
6175 and a administrative web interface
6176 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
6177 withsqlite), as well as a privacy enhancing proxy based on
6178 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
6179 (freedombox-privoxy). There is also a web/javascript based XMPP
6180 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
6181 trying (unsuccessfully so far) to talk to the XMPP server
6182 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
6183 web interface is pluggable, and the goal is to use it to enable OpenID
6184 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6185 this is really working yet, see
6186 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
6187 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
6188 on github at the moment. The HTTP proxy is operational out of the
6189 box, and the admin web interface can be used to add/remove plinth
6190 users. I&#39;ve not been able to do anything else with it so far, but
6191 know there are several branches spread around github and other places
6192 with lots of half baked features.&lt;/p&gt;
6193
6194 &lt;p&gt;Anyway, if you want to have a look at the current state, the
6195 following recipes should work to give you a test machine to poke
6196 at.&lt;/p&gt;
6197
6198 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
6199
6200 &lt;ol&gt;
6201
6202 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
6203 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
6204 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
6205 to the Debian installer:&lt;p&gt;
6206 &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;
6207
6208 &lt;li&gt;Answer the few language/region/password questions and pick disk to
6209 install on.&lt;/li&gt;
6210
6211 &lt;li&gt;When the installation is finished and the machine have rebooted a
6212 few times, your Freedombox is ready for testing.&lt;/li&gt;
6213
6214 &lt;/ol&gt;
6215
6216 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
6217
6218 &lt;ol&gt;
6219
6220 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
6221 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
6222 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
6223 &lt;pre&gt;
6224 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
6225 &lt;/pre&gt;&lt;/li&gt;
6226 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
6227 &lt;pre&gt;
6228 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6229 apt-key add -
6230 apt-get update
6231 apt-get install freedombox-setup
6232 /usr/lib/freedombox/setup
6233 &lt;/pre&gt;&lt;/li&gt;
6234 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
6235
6236 &lt;/ol&gt;
6237
6238 &lt;p&gt;You can test it on other architectures too, but because the
6239 freedombox-privoxy package is binary, it will only work as intended on
6240 the architectures where I have had time to build the binary and put it
6241 in my APT repository. But do not let this stop you. It is only a
6242 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
6243
6244 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
6245 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
6246 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
6247 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
6248
6249 &lt;p&gt;Please let me know if this works for you, or if you have any
6250 problems. We gather on the IRC channel
6251 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
6252 irc.debian.org and the
6253 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
6254 mailing list&lt;/a&gt;.&lt;/p&gt;
6255
6256 &lt;p&gt;Once you get your freedombox operational, you can visit
6257 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
6258 welcome screen (dead end - do not be surprised if you are unable to
6259 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
6260 to look at the rest of plinth. The default user is &#39;admin&#39; and the
6261 default password is &#39;secret&#39;.&lt;/p&gt;
6262 </description>
6263 </item>
6264
6265 <item>
6266 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
6267 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
6268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
6269 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
6270 <description>&lt;p&gt;Earlier, I reported about
6271 &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
6272 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
6273 told by IBM that the original disk should be thrown away. And as
6274 there no longer was a problem if I bricked the firmware, I decided
6275 today to try to install Intel firmware to replace the Lenovo firmware
6276 currently on the disk.&lt;/p&gt;
6277
6278 &lt;p&gt;I searched the Intel site for firmware, and found
6279 &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;
6280 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6281 according to the site should contain the latest firmware for SSD
6282 disks. I inserted the broken disk in one of my spare laptops and
6283 booted the ISO from a USB stick. The disk was recognized, but the
6284 program claimed the newest firmware already were installed and refused
6285 to insert any Intel firmware. So no change, and the disk is still
6286 unable to handle write load. :( I guess the only way to get them
6287 working would be if Lenovo releases new firmware. No idea how likely
6288 that is. Anyway, just blogging about this test for completeness. I
6289 got a working Samsung disk, and see no point in spending more time on
6290 the broken disks.&lt;/p&gt;
6291 </description>
6292 </item>
6293
6294 <item>
6295 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
6296 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
6297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
6298 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
6299 <description>&lt;p&gt;Today I switched to
6300 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
6301 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
6302 my new Thinkpad X230, which was delivered with an
6303 &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
6304 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
6305 sustained writes. My hardware supplier have been very forthcoming in
6306 trying to find a solution, and after first trying with another
6307 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
6308 disk instead to fix it once and for all. The Samsung disk survived
6309 the installation of Debian with encrypted disks (filling the disk with
6310 random data during installation killed the first two), and I thus
6311 decided to trust it with my data. I have installed it as a Debian Edu
6312 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6313 server at home using Kerberos and LDAP, and will use it as my work
6314 station from now on.&lt;/p&gt;
6315
6316 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
6317 Debian Wheezy default installation need to be tuned a bit to increase
6318 performance and increase life time of the disk. The Linux kernel and
6319 user space applications do not yet adjust automatically to such
6320 environment. To make it easier for my self, I created a draft Debian
6321 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
6322 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
6323 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
6324 is set up to adjust the setup of the machine by just installing the
6325 package. If there is any non-SSD disk in the machine, the package
6326 will refuse to install, as I did not try to write any logic to sort
6327 file systems in SSD and non-SSD file systems.&lt;/p&gt;
6328
6329 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
6330 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6331 where I set up the machine with one large encrypted partition (in
6332 addition to /boot), put LVM on top of this and set up partitions on
6333 top of this again. See the README file in the package source for the
6334 references I used to pick the settings. At the moment these
6335 parameters are tuned:&lt;/p&gt;
6336
6337 &lt;ul&gt;
6338
6339 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
6340 (adding discard to /etc/crypttab)&lt;/li&gt;
6341
6342 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
6343 this case a cryptsetup partition) by changing issue_discards from
6344 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
6345
6346 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
6347 systems.&lt;/li&gt;
6348
6349 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
6350 /etc/fstab.&lt;/li&gt;
6351
6352 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
6353
6354 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
6355 cron.daily).&lt;/li&gt;
6356
6357 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
6358 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
6359
6360 &lt;/ul&gt;
6361
6362 &lt;p&gt;During installation, I cancelled the part where the installer fill
6363 the disk with random data, as this would kill the SSD performance for
6364 little gain. My goal with the encrypted file system is to ensure
6365 those stealing my laptop end up with a brick and not a working
6366 computer. I have no hope in keeping the really resourceful people
6367 from getting the data on the disk (see
6368 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
6369 Thus I concluded that adding the discard option to crypttab is the
6370 right thing to do.&lt;/p&gt;
6371
6372 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
6373 it for SSD, but others recommended deadline and a benchmark I found
6374 indicated that deadline might be better for interactive use.&lt;/p&gt;
6375
6376 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
6377 and ext4, but read that it would give a performance hit ever time a
6378 file is removed, and thought it best to that that slowdown once a day
6379 instead of during my work.&lt;/p&gt;
6380
6381 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6382 this is already done by Debian Edu.&lt;/p&gt;
6383
6384 &lt;p&gt;I have not yet started on the user space tuning. I expect
6385 iceweasel need some tuning, and perhaps other applications too, but
6386 have not yet had time to investigate those parts.&lt;/p&gt;
6387
6388 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
6389 there.&lt;/p&gt;
6390
6391 &lt;p&gt;As for the answer to the question in the title of this blog post,
6392 as far as I know, the only solution I know about is to replace the
6393 disk. It might be possible to flash it with Intel firmware instead of
6394 the Lenovo firmware. But I have not tried and did not want to do so
6395 without approval from Lenovo as I wanted to keep the warranty on the
6396 disk until a solution was found and they wanted the broken disks
6397 back.&lt;/p&gt;
6398 </description>
6399 </item>
6400
6401 <item>
6402 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
6403 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
6404 <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>
6405 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
6406 <description>&lt;p&gt;A few days ago, I wrote about
6407 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
6408 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
6409 was dying during installation because it is unable to cope with
6410 sustained write. My supplier is in contact with
6411 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
6412 replacement disk to try to fix the problem. They decided to send an
6413 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
6414
6415 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
6416 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6417 same firmware version as the original. This time my hope raised
6418 slightly as the installation progressed, as the original disk used to
6419 die after 4-7% of the disk was written to, while this time it kept
6420 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
6421 died again and I was back on square one. I still do not have a new
6422 laptop with a disk I can trust. I can not live with a disk that might
6423 lock up when I download a new
6424 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
6425 other large files. I look forward to hearing from my supplier with
6426 the next proposal from Lenovo.&lt;/p&gt;
6427
6428 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
6429 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6430 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6431 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
6432 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6433 P/N 45N8295, P0C38732.&lt;/p&gt;
6434
6435 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
6436 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
6437 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6438 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
6439 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6440 P/N 45N8295, P0C38732.&lt;/p&gt;
6441
6442 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
6443 SA, date and WNPP values. Mentioning all the details here in case
6444 someone is able to use the information to find a way to identify the
6445 failing disk among working ones (if any such working disk actually
6446 exist).&lt;/p&gt;
6447 </description>
6448 </item>
6449
6450 <item>
6451 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
6452 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
6453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
6454 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
6455 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
6456 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6457 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
6458 member assosiation NUUG&lt;/a&gt; and
6459 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
6460 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
6461 Bitraf&lt;/a&gt;.&lt;/p&gt;
6462
6463 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
6464 welcome, and there is no fee to participate. There is on the other
6465 hand limited space, and only room for 30 people. Please put your name
6466 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
6467 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
6468 </description>
6469 </item>
6470
6471 <item>
6472 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
6473 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
6474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
6475 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
6476 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
6477 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
6478 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
6479 time to spend on it, and it took a while to find a model I believe
6480 will do the job, but two days ago the replacement finally arrived. I
6481 ended up picking a
6482 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
6483 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6484 a roaming workstation, and it seemed to work flawlessly. But my
6485 second installation with encrypted disk was not as successful. More
6486 on that below.&lt;/p&gt;
6487
6488 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6489 important requirements (robust and with a good keyboard) are never
6490 listed in the feature list. But I did get good help from the search
6491 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6492 allowed me to limit the list of interesting laptops based on my other
6493 requirements. A bit surprising that SSD disk are not disks according
6494 to that search interface, so I had to drop specifying the number of
6495 disks from my search parameters. I also asked around among friends to
6496 get their impression on keyboards and robustness.&lt;/p&gt;
6497
6498 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
6499 X41. I am not quite convinced about the keyboard, as it is
6500 significantly wider than my old keyboard, and I have to stretch my
6501 hand a lot more to reach the edges. But the key response is fairly
6502 good and the individual key shape is fairly easy to handle, so I hope
6503 I will get used to it. My old X40 was starting to fail, and I really
6504 needed a new laptop now. :)&lt;/p&gt;
6505
6506 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6507 visit to the BIOS during boot it disable it.&lt;/p&gt;
6508
6509 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6510 lock up during load. And this happen when installing Debian Wheezy
6511 with encrypted disk, while the disk is being filled with random data.
6512 I also tested to install Ubuntu Raring, and it happen there too if I
6513 reenable the code to fill the disk with random data (it is disabled by
6514 default in Ubuntu). And the bug with is already known. It was
6515 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6516 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6517 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6518 kernel developers as
6519 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6520 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6521 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6522 Lenovo forums, both for
6523 &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
6524 2012-11-10&lt;/a&gt; and for
6525 &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
6526 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6527 reports state that the disk lock up during use if many writes are done
6528 on the disk, so it is much no use to work around the installation
6529 problem and end up with a computer that can lock up at any moment.
6530 There is even a
6531 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6532 available&lt;/a&gt; that will lock up the hard drive after running a few
6533 minutes by writing to a file.&lt;/p&gt;
6534
6535 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6536 contacting PCHELP Norway (request 01D1FDP) which handle support
6537 requests for Lenovo, his first suggestion was to upgrade the disk
6538 firmware. Unfortunately there is no newer firmware available from
6539 Lenovo, as my disk already have the most recent one (version LF1i). I
6540 hope to hear more from him today and hope the problem can be
6541 fixed. :)&lt;/p&gt;
6542 </description>
6543 </item>
6544
6545 <item>
6546 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6547 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6548 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6549 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6550 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6551 trusty old Thinkpad X41. Unfortunately I did not have much time to
6552 spend on it, but today the replacement finally arrived. I ended up
6553 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6554 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6555 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6556 this, it is installing what I hope will be a more final installation,
6557 with a encrypted hard drive to ensure any dope head stealing it end up
6558 with an expencive door stop.&lt;/p&gt;
6559
6560 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6561 important requirements (robust and with a good keyboard) are never
6562 listed in the feature list. But I did get good help from the search
6563 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6564 allowed me to limit the list of interesting laptops based on my other
6565 requirements. A bit surprising that SSD disk are not disks, so I had
6566 to drop number of disks from my search parameters.&lt;/p&gt;
6567
6568 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6569 wider than my old keyboard, and I have to stretch my hand a lot more
6570 to reach the edges. But the key response is fairly good and the
6571 individual key shape is fairly easy to handle, so I hope I will get
6572 used to it. My old X40 was starting to fail, and I really needed a
6573 new laptop now. :)&lt;/p&gt;
6574
6575 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6576 </description>
6577 </item>
6578
6579 <item>
6580 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6581 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6582 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6583 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6584 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6585 perfectly capable of, and I have to do it manually to get things
6586 working. One such task is to find out what firmware packages are
6587 needed to get the hardware on my computer working. Most often this
6588 affect the wifi card, but some times it even affect the RAID
6589 controller or the ethernet card. Today I pushed version 0.4 of the
6590 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6591 including a new script isenkram-autoinstall-firmware handling the
6592 process of asking all the loaded kernel modules what firmware files
6593 they want, find debian packages providing these files and install the
6594 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6595
6596 &lt;p&gt;&lt;pre&gt;
6597 # isenkram-autoinstall-firmware
6598 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6599 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6600 info: locating packages with the requested firmware files
6601 info: Updating APT sources after adding non-free APT source
6602 info: trying to install firmware-ipw2x00
6603 firmware-ipw2x00
6604 firmware-ipw2x00
6605 Preconfiguring packages ...
6606 Selecting previously deselected package firmware-ipw2x00.
6607 (Reading database ... 259727 files and directories currently installed.)
6608 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6609 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6610 #
6611 &lt;/pre&gt;&lt;/p&gt;
6612
6613 &lt;p&gt;When all the requested firmware is present, a simple message is
6614 printed instead:&lt;/p&gt;
6615
6616 &lt;p&gt;&lt;pre&gt;
6617 # isenkram-autoinstall-firmware
6618 info: did not find any firmware files requested by loaded kernel modules. exiting
6619 #
6620 &lt;/pre&gt;&lt;/p&gt;
6621
6622 &lt;p&gt;It could use some polish, but it is already working well and saving
6623 me some time when setting up new machines. :)&lt;/p&gt;
6624
6625 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6626 kernel modules, and look up each one of them using modinfo, to find
6627 the firmware files listed in the module meta-information. Next, it
6628 download the Contents file from a nearby APT mirror, and search for
6629 the firmware files in this file to locate the package with the
6630 requested firmware file. If the package is in the non-free section, a
6631 non-free APT source is added and the package is installed using
6632 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6633 machine.&lt;/p&gt;
6634
6635 &lt;p&gt;I hope someone find time to implement a more polished version of
6636 this script as part of the hw-detect debian-installer module, to
6637 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6638 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6639 firmware during a PXE install when the packages already are available
6640 from the nearby Debian mirror.&lt;/p&gt;
6641 </description>
6642 </item>
6643
6644 <item>
6645 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6646 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6647 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6648 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6649 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6650 the screen just turn black when Linux boot, either during installation
6651 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6652 last few years, but only recently understood the cause. I&#39;ve seen it
6653 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6654 The reason seem to be in the wiring of some laptops. The system to
6655 control the screen background light is inverted, so when Linux try to
6656 turn the brightness fully on, it end up turning it off instead. I do
6657 not know which Linux drivers are affected, but this post is about the
6658 i915 driver used by the
6659 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6660 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6661
6662 &lt;p&gt;The problem can be worked around two ways. Either by adding
6663 i915.invert_brightness=1 as a kernel option, or by adding a file in
6664 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6665 option when it load the i915 kernel module. On Debian and Ubuntu, it
6666 can be done by running these commands as root:&lt;/p&gt;
6667
6668 &lt;pre&gt;
6669 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6670 update-initramfs -u -k all
6671 &lt;/pre&gt;
6672
6673 &lt;p&gt;Since March 2012 there is
6674 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6675 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6676 hardware have this problem, and get the driver to invert the
6677 brightness setting automatically. To use it, one need to add a row in
6678 &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
6679 intel_quirks array&lt;/a&gt; in the driver source
6680 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6681 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6682 number (vendor number 8086 is assumed) and subdevice vendor and device
6683 number.&lt;/p&gt;
6684
6685 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6686 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6687
6688 &lt;p&gt;&lt;pre&gt;
6689 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6690 3rd Gen Core processor Graphics Controller [8086:0156] \
6691 (rev 09) (prog-if 00 [VGA controller])
6692 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6693 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6694 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6695 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6696 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6697 Latency: 0
6698 Interrupt: pin A routed to IRQ 42
6699 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6700 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6701 Region 4: I/O ports at 4000 [size=64]
6702 Expansion ROM at &lt;unassigned&gt; [disabled]
6703 Capabilities: &lt;access denied&gt;
6704 Kernel driver in use: i915
6705 &lt;/pre&gt;&lt;/p&gt;
6706
6707 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6708
6709 &lt;p&gt;&lt;pre&gt;
6710 struct intel_quirk intel_quirks[] = {
6711 ...
6712 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6713 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6714 ...
6715 }
6716 &lt;/pre&gt;&lt;/p&gt;
6717
6718 &lt;p&gt;According to the kernel module instructions (as seen using
6719 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6720 invert_brightness flag should be sent to the
6721 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6722 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6723 developers. But my email about the laptop sent 2013-06-03 have not
6724 yet shown up in
6725 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6726 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6727 emails from non-subscribers. Because of this, I sent my patch also to
6728 the Debian bug tracking system instead as
6729 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6730 sure the patch is not lost.&lt;/p&gt;
6731
6732 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6733 with this problem working properly with Linux. If you use Gnome, your
6734 worries should be over at this point. But if you use KDE, there is
6735 something in KDE ignoring the invert_brightness setting and turning on
6736 the screen during login. I&#39;ve reported it to Debian as
6737 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6738 have no idea yet how to figure out exactly what subsystem is doing
6739 this. Perhaps you can help? Perhaps you know what the Gnome
6740 developers did to handle this, and this can give a clue to the KDE
6741 developers? Or you know where in KDE the screen brightness is changed
6742 during login? If so, please update the BTS report (or get in touch if
6743 you do not know how to update BTS).&lt;/p&gt;
6744
6745 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6746 acpi_backlight=vendor, to disable ACPI backlight support completely,
6747 as the ACPI information on the machine is trash and it is better to
6748 leave it to the intel video driver to control the screen
6749 backlight.&lt;/p&gt;
6750 </description>
6751 </item>
6752
6753 <item>
6754 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6755 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6756 <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>
6757 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6758 <description>&lt;p&gt;Two days ago, I asked
6759 &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
6760 I could install Linux on a Packard Bell EasyNote LV computer
6761 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6762 with the obstacles put in the way of Linux users on a laptop with UEFI
6763 and Windows 8.&lt;/p&gt;
6764
6765 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6766 secure booting or fast boot. I suspect fast boot was the problem,
6767 causing the firmware to boot directly from HD without considering any
6768 key presses and alternative devices, but do not know UEFI settings
6769 enough to tell.&lt;/p&gt;
6770
6771 &lt;p&gt;There is no way to install Linux on the machine in question without
6772 opening the box and disconnecting the hard drive! This is as far as I
6773 can tell, the only way to get access to the firmware setup menu
6774 without accepting the Windows 8 license agreement. I am told (and
6775 found description on how to) that it is possible to configure the
6776 firmware setup once booted into Windows 8. But as I believe the terms
6777 of that agreement are completely unacceptable, accepting the license
6778 was never an alternative. I do not enter agreements I do not intend
6779 to follow.&lt;/p&gt;
6780
6781 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6782 waste many hours on this, but luckily there was a way to get it to
6783 work. But I would not recommend it to anyone planning to run Linux on
6784 it, and I have become sceptical to Windows 8 certified laptops. Is
6785 this the way Linux will be forced out of the market place, by making
6786 it close to impossible for &quot;normal&quot; users to install Linux without
6787 accepting the Microsoft Windows license terms? Or at least not
6788 without risking to loose the warranty?&lt;/p&gt;
6789
6790 &lt;p&gt;I&#39;ve updated the
6791 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6792 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6793 do not have to struggle as much as I did to get Linux into the
6794 machine.&lt;/p&gt;
6795
6796 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6797 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6798 </description>
6799 </item>
6800
6801 <item>
6802 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6803 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6804 <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>
6805 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6806 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6807 new laptops for my parents and a few others. I bought Packard Bell
6808 Easynote LV to run Kubuntu on and use as their home computer. But I
6809 am completely unable to figure out how to install Linux on it. The
6810 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6811 instead of a BIOS to boot.&lt;/p&gt;
6812
6813 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6814 to get it to boot the Linux installer from my USB stick. I have yet
6815 to try the DVD install, and still hope it will work. when I turn on
6816 the computer, there is no information on what buttons to press to get
6817 the normal boot menu. I expect to get some boot menu to select PXE or
6818 USB stick booting. When booting, it first ask for the language to
6819 use, then for some regional settings, and finally if I will accept the
6820 Windows 8 terms of use. As these terms are completely unacceptable to
6821 me, I have no other choice but to turn off the computer and try again
6822 to get it to boot the Linux installer.&lt;/p&gt;
6823
6824 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6825 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6826 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6827 installed on this machine, please get in touch or update that wiki
6828 page. If I can&#39;t find a way to install Linux, I will have to return
6829 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6830
6831 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6832 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6833 on new Laptops?&lt;/p&gt;
6834 </description>
6835 </item>
6836
6837 <item>
6838 <title>How to transform a Debian based system to a Debian Edu installation</title>
6839 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6841 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6842 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6843 an operating system based on Debian intended for use in schools. It
6844 contain a turn-key solution for the computer network provided to
6845 pupils in the primary schools. It provide both the central server,
6846 network boot servers and desktop environments with heaps of
6847 educational software. The project was founded almost 12 years ago,
6848 2001-07-02. If you want to support the project, which is in need for
6849 cash to fund developer gatherings and other project related activity,
6850 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6851 donate some money&lt;/a&gt;.
6852
6853 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6854 lists and elsewhere, is the question on how to transform a Debian or
6855 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6856 hard, and last week I wrote a script to replicate the steps done by
6857 the Debian Edu installer.&lt;/p&gt;
6858
6859 &lt;p&gt;The script,
6860 &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;
6861 in the debian-edu-config package, will go through these six steps and
6862 transform an existing Debian Wheezy or Ubuntu (untested) installation
6863 into a Debian Edu Workstation:&lt;/p&gt;
6864
6865 &lt;ol&gt;
6866
6867 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6868 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6869 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6870 our configuration.&lt;/li&gt;
6871 &lt;li&gt;Preseed debconf database with profile setup in
6872 /etc/debian-edu/config, and run tasksel to install packages
6873 according to the profile specified in the config above,
6874 overriding some of the Debian automation machinery.&lt;/li&gt;
6875 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6876 that could not be done using preseeding.&lt;/li&gt;
6877 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6878
6879 &lt;/ol&gt;
6880
6881 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6882 replicated like this. Disk partitioning and LVM setup, for example.
6883 So this script just assume there is enough disk space to install all
6884 the needed packages.&lt;/p&gt;
6885
6886 &lt;p&gt;The script was created to help a Debian Edu student working on
6887 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6888 Debian Edu client, and using it he can take the existing
6889 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6890 transform it into a fully functioning Debian Edu Workstation (or
6891 Roaming Workstation, or whatever :).&lt;/p&gt;
6892
6893 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6894 If a LXDE based Roaming workstation is wanted instead, modify the
6895 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6896
6897 &lt;p&gt;&lt;pre&gt;
6898 PROFILE=&quot;Roaming-Workstation&quot;
6899 DESKTOP=&quot;lxde&quot;
6900 &lt;/pre&gt;&lt;/p&gt;
6901
6902 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6903 the cloud, by starting with a virtual Debian installation at some
6904 virtual hosting service and setting up all the services on first
6905 boot.&lt;/p&gt;
6906 </description>
6907 </item>
6908
6909 <item>
6910 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6911 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6913 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6914 <description>&lt;P&gt;In January,
6915 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6916 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6917 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6918 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6919 marvellous construction system from Denmark. We also created
6920 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6921 a place to take notes and write down our plans and hopes. And several
6922 people showed up to help. I was very happy to see the effect of my
6923 call. Since the small start, we have a debtags tag
6924 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6925 tag for LEGO related packages, and now count 10 packages related to
6926 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6927
6928 &lt;p&gt;&lt;table&gt;
6929 &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;
6930 &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;
6931 &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;
6932 &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;
6933 &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;
6934 &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;
6935 &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;
6936 &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;
6937 &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;
6938 &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;
6939 &lt;/table&gt;&lt;/p&gt;
6940
6941 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6942 currently available in Jessie/testing. leocad is so far only
6943 available in experimental.&lt;/p&gt;
6944
6945 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6946 adding the rest of the great free software tools available on Linux
6947 for LEGO designers.&lt;/p&gt;
6948 </description>
6949 </item>
6950
6951 <item>
6952 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6953 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6954 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6955 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6956 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6957 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6958 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6959 Debian release, and I expect to move my machines at home over to it fairly
6960 soon.&lt;/p&gt;
6961
6962 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6963 in particular make me very happy to see included. The
6964 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6965 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6966 included for the first time. Alongside similar programs like
6967 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6968 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6969 it allow for visual programming where syntax errors can not happen,
6970 and a friendly programming environment for learning to control the
6971 computer. Scratch will also be included in the next release of Debian
6972 Edu.&lt;/a&gt;
6973
6974 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6975 Edu/Skolelinux release too. The
6976 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6977 alpha release&lt;/a&gt; went out last week, and the next should soon
6978 follow.&lt;p&gt;
6979 </description>
6980 </item>
6981
6982 <item>
6983 <title>Isenkram 0.2 finally in the Debian archive</title>
6984 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6985 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6986 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6987 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6988 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6989 for many months. I uploaded it to the Debian experimental suite
6990 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6991
6992 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6993 install to work with a pluggable hardware device. The suggestion pop
6994 up when the device is plugged in. For example if a Lego Mindstorm NXT
6995 is inserted, it will suggest to install the program needed to program
6996 the NXT controller. Give it a go, and report bugs and suggestions to
6997 BTS. :)&lt;/p&gt;
6998 </description>
6999 </item>
7000
7001 <item>
7002 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
7003 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
7004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
7005 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
7006 <description>&lt;p&gt;My
7007 &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
7008 bitcoin related blog post&lt;/a&gt; mentioned that the new
7009 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
7010 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7011 2013-01-19, and have been available in unstable since then. It was
7012 automatically copied to Ubuntu, and is available in their Raring
7013 version too.&lt;/p&gt;
7014
7015 &lt;p&gt;But there is a strange problem with the build that block this new
7016 version from being available on the i386 and kfreebsd-i386
7017 architectures. For some strange reason, the autobuilders in Debian
7018 for these architectures fail to run the test suite on these
7019 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
7020 We are so far unable to reproduce it when building it manually, and
7021 no-one have been able to propose a fix. If you got an idea what is
7022 failing, please let us know via the BTS.&lt;/p&gt;
7023
7024 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
7025 I often run low on disk space, is the fact that the client will exit
7026 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
7027 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
7028 it. :)&lt;/p&gt;
7029
7030 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7031 activities, please send Bitcoin donations to my address
7032 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7033 </description>
7034 </item>
7035
7036 <item>
7037 <title>Welcome to the world, Isenkram!</title>
7038 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
7039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
7040 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
7041 <description>&lt;p&gt;Yesterday, I
7042 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
7043 for testers&lt;/a&gt; for my prototype for making Debian better at handling
7044 pluggable hardware devices, which I
7045 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
7046 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
7047 up, and caused me to really want to to open up the development to more
7048 people. But before I did this, I want to come up with a sensible name
7049 for this project. Today I finally decided on a new name, and I have
7050 renamed the project from hw-support-handler to this new name. In the
7051 process, I moved the source to git and made it available as a
7052 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
7053 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
7054 To fetch and build the latest version of the source, use&lt;/p&gt;
7055
7056 &lt;pre&gt;
7057 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
7058 cd isenkram &amp;&amp; git-buildpackage -us -uc
7059 &lt;/pre&gt;
7060
7061 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
7062 want to hack on the source or improve the package, please go ahead.
7063 But please talk to me first on IRC or via email before you do major
7064 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
7065
7066 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
7067 stuff, typically meaning tools, nails, screws, etc. Typical hardware
7068 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
7069 the German word eisenkram, for those that are familiar with that
7070 word.&lt;/p&gt;
7071
7072 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
7073 instructions, to avoid confusing people with an error from the signing
7074 process.&lt;/p&gt;
7075
7076 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
7077 clone argument to avoid the need for authentication.&lt;/p&gt;
7078 </description>
7079 </item>
7080
7081 <item>
7082 <title>First prototype ready making hardware easier to use in Debian</title>
7083 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
7084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
7085 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
7086 <description>&lt;p&gt;Early this month I set out to try to
7087 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
7088 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
7089 prototype is working, and it is ready for a larger audience. To test
7090 it, fetch the
7091 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
7092 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
7093 package. You might have to log out and in again activate the
7094 autostart script.&lt;/p&gt;
7095
7096 &lt;p&gt;The design is simple:&lt;/p&gt;
7097
7098 &lt;ul&gt;
7099
7100 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
7101 hw-support-handlerd to start when the user log in.&lt;/li&gt;
7102
7103 &lt;li&gt;This program listen for kernel events about new hardware (directly
7104 from the kernel like udev does), not using HAL dbus events as I
7105 initially did.&lt;/li&gt;
7106
7107 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
7108 the APT database, a database
7109 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
7110 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
7111
7112 &lt;li&gt;If a package is mapped to the hardware in question, the package
7113 isn&#39;t installed yet and this is the first time the hardware was
7114 plugged in, show a desktop notification suggesting to install the
7115 package or packages.&lt;/li&gt;
7116
7117 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
7118 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
7119
7120 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
7121 package while showing progress information in a window.&lt;/li&gt;
7122
7123 &lt;/ul&gt;
7124
7125 &lt;p&gt;I still need to come up with a better name for the system. Here
7126 are some screen shots showing the prototype in action. First the
7127 notification, then the password request, and finally the request to
7128 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
7129
7130 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
7131 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
7132 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
7133 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
7134 &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;
7135
7136 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
7137 is already useful. The database of hardware to package mappings also
7138 need more work. It is currently compatible with the Ubuntu way of
7139 storing such information in the package control file, but could be
7140 changed to use other formats instead or in addition to the current
7141 method. I&#39;ve dropped the use of discover for this mapping, as the
7142 modalias approach is more flexible and easier to use on Linux as long
7143 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
7144
7145 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
7146 here is the command required to check out and build the source: Use
7147 &#39;&lt;tt&gt;svn checkout
7148 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
7149 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
7150 devscripts package.&lt;/p&gt;
7151
7152 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
7153 renamed to Isenkram and the source moved from the Debian Edu
7154 subversion repository to a Debian collab-maint git repository. See
7155 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
7156 instructions&lt;/a&gt; for details.&lt;/p&gt;
7157 </description>
7158 </item>
7159
7160 <item>
7161 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
7162 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
7163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
7164 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
7165 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
7166 suddenly in bed. With a quiet whimper, it went completely quiet and
7167 black. The power button was no longer able to turn it on. It was a
7168 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7169 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7170 Compaq I had before that. Now I need to find a replacement. To keep
7171 going during Christmas, I moved the one year old SSD disk to my old
7172 X40 where it fitted (only one I had left that could use it), but it is
7173 not a durable solution.
7174
7175 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
7176 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
7177
7178 &lt;ul&gt;
7179
7180 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
7181 than A4).&lt;/li&gt;
7182 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
7183 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
7184 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
7185 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
7186 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
7187 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
7188 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
7189 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
7190 size).&lt;/li&gt;
7191 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
7192 X.org packages.&lt;/li&gt;
7193 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
7194 the time).
7195
7196 &lt;/ul&gt;
7197
7198 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
7199 list. The reason is simply that the specifications on laptops the
7200 last 10-15 years have been sufficient for my needs, and I have to look
7201 at other features to choose my laptop. But are there still made as
7202 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7203 robust, and Thinkpads seem to be heading in the wrong direction since
7204 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
7205 still be useful.&lt;/p&gt;
7206
7207 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
7208 external keyboard? I&#39;ll have to check the
7209 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
7210 well-supported laptops, or perhaps just buy one preinstalled from one
7211 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
7212 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
7213 </description>
7214 </item>
7215
7216 <item>
7217 <title>How to find a browser plugin supporting a given MIME type</title>
7218 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
7219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
7220 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
7221 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
7222 install to get support for a given MIME type. Thanks to
7223 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
7224 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
7225 Unfortunately, not very many packages provide the needed meta
7226 information, Anyway, here is a small script to look up all browser
7227 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
7228
7229 &lt;pre&gt;
7230 #!/usr/bin/python
7231 import sys
7232 import apt
7233 def pkgs_handling_mimetype(mimetype):
7234 cache = apt.Cache()
7235 cache.open(None)
7236 thepkgs = []
7237 for pkg in cache:
7238 version = pkg.candidate
7239 if version is None:
7240 version = pkg.installed
7241 if version is None:
7242 continue
7243 record = version.record
7244 if not record.has_key(&#39;Npp-MimeType&#39;):
7245 continue
7246 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
7247 for t in mime_types:
7248 t = t.rstrip().strip()
7249 if t == mimetype:
7250 thepkgs.append(pkg.name)
7251 return thepkgs
7252 mimetype = &quot;audio/ogg&quot;
7253 if 1 &lt; len(sys.argv):
7254 mimetype = sys.argv[1]
7255 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
7256 for pkg in pkgs_handling_mimetype(mimetype):
7257 print &quot; %s&quot; %pkg
7258 &lt;/pre&gt;
7259
7260 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
7261
7262 &lt;pre&gt;
7263 % ./apt-find-browserplug-for-mimetype
7264 Browser plugin packages supporting audio/ogg:
7265 gecko-mediaplayer
7266 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7267 Browser plugin packages supporting application/x-shockwave-flash:
7268 browser-plugin-gnash
7269 %
7270 &lt;/pre&gt;
7271
7272 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
7273 itself to query for plugins and propose to install the needed
7274 packages. It would be great if Debian supported such feature too. Is
7275 anyone working on adding it?&lt;/p&gt;
7276
7277 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
7278 request for icweasel support for this feature is
7279 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
7280 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
7281 of manpower and wish for a different design is the reason thus feature
7282 is not yet in iceweasel from Debian.&lt;/p&gt;
7283 </description>
7284 </item>
7285
7286 <item>
7287 <title>What is the most supported MIME type in Debian?</title>
7288 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
7289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
7290 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
7291 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
7292 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
7293 proposal to make it possible for a Desktop application to propose to
7294 the user some package to install to gain support for a given MIME
7295 type, font, library etc. that is currently missing. With such
7296 mechanism in place, it would be possible for the desktop to
7297 automatically propose and install leocad if some LDraw file is
7298 downloaded by the browser.&lt;/p&gt;
7299
7300 &lt;p&gt;To get some idea about the current content of the archive, I decided
7301 to write a simple program to extract all .desktop files from the
7302 Debian archive and look up the claimed MIME support there. The result
7303 can be found on the
7304 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
7305 site&lt;/a&gt;. Using the collected information, it become possible to
7306 answer the question in the title. Here are the 20 most supported MIME
7307 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7308 The complete list is available from the link above.&lt;/p&gt;
7309
7310 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
7311
7312 &lt;pre&gt;
7313 count MIME type
7314 ----- -----------------------
7315 32 text/plain
7316 30 audio/mpeg
7317 29 image/png
7318 28 image/jpeg
7319 27 application/ogg
7320 26 audio/x-mp3
7321 25 image/tiff
7322 25 image/gif
7323 22 image/bmp
7324 22 audio/x-wav
7325 20 audio/x-flac
7326 19 audio/x-mpegurl
7327 18 video/x-ms-asf
7328 18 audio/x-musepack
7329 18 audio/x-mpeg
7330 18 application/x-ogg
7331 17 video/mpeg
7332 17 audio/x-scpls
7333 17 audio/ogg
7334 16 video/x-ms-wmv
7335 &lt;/pre&gt;
7336
7337 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
7338
7339 &lt;pre&gt;
7340 count MIME type
7341 ----- -----------------------
7342 33 text/plain
7343 32 image/png
7344 32 image/jpeg
7345 29 audio/mpeg
7346 27 image/gif
7347 26 image/tiff
7348 26 application/ogg
7349 25 audio/x-mp3
7350 22 image/bmp
7351 21 audio/x-wav
7352 19 audio/x-mpegurl
7353 19 audio/x-mpeg
7354 18 video/mpeg
7355 18 audio/x-scpls
7356 18 audio/x-flac
7357 18 application/x-ogg
7358 17 video/x-ms-asf
7359 17 text/html
7360 17 audio/x-musepack
7361 16 image/x-xbitmap
7362 &lt;/pre&gt;
7363
7364 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
7365
7366 &lt;pre&gt;
7367 count MIME type
7368 ----- -----------------------
7369 31 text/plain
7370 31 image/png
7371 31 image/jpeg
7372 29 audio/mpeg
7373 28 application/ogg
7374 27 image/gif
7375 26 image/tiff
7376 26 audio/x-mp3
7377 23 audio/x-wav
7378 22 image/bmp
7379 21 audio/x-flac
7380 20 audio/x-mpegurl
7381 19 audio/x-mpeg
7382 18 video/x-ms-asf
7383 18 video/mpeg
7384 18 audio/x-scpls
7385 18 application/x-ogg
7386 17 audio/x-musepack
7387 16 video/x-ms-wmv
7388 16 video/x-msvideo
7389 &lt;/pre&gt;
7390
7391 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
7392 information mentioned in DEP-11. I have not yet had time to look at
7393 it, but hope the PackageKit people in Debian are on top of these
7394 issues.&lt;/p&gt;
7395
7396 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
7397 discovering a typo in my script.&lt;/p&gt;
7398 </description>
7399 </item>
7400
7401 <item>
7402 <title>Using modalias info to find packages handling my hardware</title>
7403 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
7404 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
7405 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
7406 <description>&lt;p&gt;Yesterday, I wrote about the
7407 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
7408 values provided by the Linux kernel&lt;/a&gt; following my hope for
7409 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
7410 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
7411 modalias values attached to package names can be used to map packages
7412 to hardware. This allow the system to look up and suggest relevant
7413 packages when I plug in some new hardware into my machine, and replace
7414 discover and discover-data as the database used to map hardware to
7415 packages.&lt;/p&gt;
7416
7417 &lt;p&gt;I create a modaliases file with entries like the following,
7418 containing package name, kernel module name (if relevant, otherwise
7419 the package name) and globs matching the relevant hardware
7420 modalias.&lt;/p&gt;
7421
7422 &lt;p&gt;&lt;blockquote&gt;
7423 Package: package-name
7424 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
7425 &lt;/blockquote&gt;&lt;/p&gt;
7426
7427 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
7428 for a given modalias value using this file.&lt;/p&gt;
7429
7430 &lt;p&gt;An entry like this would suggest the video and picture application
7431 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
7432
7433 &lt;p&gt;&lt;blockquote&gt;
7434 Package: cheese
7435 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
7436 &lt;/blockquote&gt;&lt;/p&gt;
7437
7438 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
7439 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
7440
7441 &lt;p&gt;&lt;blockquote&gt;
7442 Package: pcmciautils
7443 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7444 &lt;/blockquote&gt;&lt;/p&gt;
7445
7446 &lt;p&gt;An entry like this would suggest the package colorhug-client when
7447 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
7448
7449 &lt;p&gt;&lt;blockquote&gt;
7450 Package: colorhug-client
7451 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
7452 &lt;/blockquote&gt;&lt;/p&gt;
7453
7454 &lt;p&gt;I believe the format is compatible with the format of the Packages
7455 file in the Debian archive. Ubuntu already uses their Packages file
7456 to store their mappings from packages to hardware.&lt;/p&gt;
7457
7458 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
7459 announce the hardware it support in a way my prototype understand.
7460 This allow those publishing packages in an APT source outside the
7461 Debian archive as well as those backporting packages to make sure the
7462 hardware mapping are included in the package meta information. I&#39;ve
7463 tested such header in the pymissile package, and its modalias mapping
7464 is working as it should with my prototype. It even made it to Ubuntu
7465 Raring.&lt;/p&gt;
7466
7467 &lt;p&gt;To test if it was possible to look up supported hardware using only
7468 the shell tools available in the Debian installer, I wrote a shell
7469 implementation of the lookup code. The idea is to create files for
7470 each modalias and let the shell do the matching. Please check out and
7471 try the
7472 &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;
7473 shell script. It run without any extra dependencies and fetch the
7474 hardware mappings from the Debian archive and the subversion
7475 repository where I currently work on my prototype.&lt;/p&gt;
7476
7477 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
7478 install yubikey-personalization:&lt;/p&gt;
7479
7480 &lt;p&gt;&lt;blockquote&gt;
7481 % ./hw-support-lookup
7482 &lt;br&gt;yubikey-personalization
7483 &lt;br&gt;%
7484 &lt;/blockquote&gt;&lt;/p&gt;
7485
7486 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7487 propose to install the pcmciautils package:&lt;/p&gt;
7488
7489 &lt;p&gt;&lt;blockquote&gt;
7490 % ./hw-support-lookup
7491 &lt;br&gt;pcmciautils
7492 &lt;br&gt;%
7493 &lt;/blockquote&gt;&lt;/p&gt;
7494
7495 &lt;p&gt;If you know of any hardware-package mapping that should be added to
7496 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
7497 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
7498
7499 &lt;p&gt;It could be possible to generate several of the mappings between
7500 packages and hardware. One source would be to look at packages with
7501 kernel modules, ie packages with *.ko files in /lib/modules/, and
7502 extract their modalias information. Another would be to look at
7503 packages with udev rules, ie packages with files in
7504 /lib/udev/rules.d/, and extract their vendor/model information to
7505 generate a modalias matching rule. I have not tested any of these to
7506 see if it work.&lt;/p&gt;
7507
7508 &lt;p&gt;If you want to help implementing a system to let us propose what
7509 packages to install when new hardware is plugged into a Debian
7510 machine, please send me an email or talk to me on
7511 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7512 </description>
7513 </item>
7514
7515 <item>
7516 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7517 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7518 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7519 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7520 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7521 information, to find the packages that support a given piece of
7522 hardware, I refreshed my memory regarding modalias values, and decided
7523 to document the details. Here are my findings so far, also available
7524 in
7525 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7526 Debian Edu subversion repository&lt;/a&gt;:
7527
7528 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7529
7530 &lt;p&gt;This document try to explain what the different types of modalias
7531 values stands for. It is in part based on information from
7532 &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;,
7533 &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;,
7534 &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
7535 &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;.
7536
7537 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7538 this shell script:&lt;/p&gt;
7539
7540 &lt;pre&gt;
7541 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7542 &lt;/pre&gt;
7543
7544 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7545 using modinfo:&lt;/p&gt;
7546
7547 &lt;pre&gt;
7548 % /sbin/modinfo psmouse | grep alias:
7549 alias: serio:ty05pr*id*ex*
7550 alias: serio:ty01pr*id*ex*
7551 %
7552 &lt;/pre&gt;
7553
7554 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7555
7556 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7557 Bridge memory controller:&lt;/p&gt;
7558
7559 &lt;p&gt;&lt;blockquote&gt;
7560 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7561 &lt;/blockquote&gt;&lt;/p&gt;
7562
7563 &lt;p&gt;This represent these values:&lt;/p&gt;
7564
7565 &lt;pre&gt;
7566 v 00008086 (vendor)
7567 d 00002770 (device)
7568 sv 00001028 (subvendor)
7569 sd 000001AD (subdevice)
7570 bc 06 (bus class)
7571 sc 00 (bus subclass)
7572 i 00 (interface)
7573 &lt;/pre&gt;
7574
7575 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7576 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7577 0600. The 0600 class is a host bridge. Other useful bus values are
7578 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7579
7580 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7581 means.&lt;/p&gt;
7582
7583 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7584
7585 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7586 USB hub in a laptop:&lt;/p&gt;
7587
7588 &lt;p&gt;&lt;blockquote&gt;
7589 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7590 &lt;/blockquote&gt;&lt;/p&gt;
7591
7592 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7593
7594 &lt;pre&gt;
7595 v 1D6B (device vendor)
7596 p 0001 (device product)
7597 d 0206 (bcddevice)
7598 dc 09 (device class)
7599 dsc 00 (device subclass)
7600 dp 00 (device protocol)
7601 ic 09 (interface class)
7602 isc 00 (interface subclass)
7603 ip 00 (interface protocol)
7604 &lt;/pre&gt;
7605
7606 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7607 class is in the interface class section. For a simple USB web camera,
7608 these alias entries show up:&lt;/p&gt;
7609
7610 &lt;p&gt;&lt;blockquote&gt;
7611 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7612 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7613 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7614 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7615 &lt;/blockquote&gt;&lt;/p&gt;
7616
7617 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7618 camera), 0101 is audio control device and 0102 is audio streaming (aka
7619 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7620
7621 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7622
7623 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7624 receiver in a Thinkpad X40:&lt;/p&gt;
7625
7626 &lt;p&gt;&lt;blockquote&gt;
7627 acpi:IBM0071:PNP0511:
7628 &lt;/blockquote&gt;&lt;/p&gt;
7629
7630 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7631
7632 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7633
7634 &lt;p&gt;The DMI table contain lots of information about the computer case
7635 and model. This is an entry for a IBM Thinkpad X40, fetched from
7636 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7637
7638 &lt;p&gt;&lt;blockquote&gt;
7639 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7640 &lt;/blockquote&gt;&lt;/p&gt;
7641
7642 &lt;p&gt;The values present are&lt;/p&gt;
7643
7644 &lt;pre&gt;
7645 bvn IBM (BIOS vendor)
7646 bvr 1UETB6WW(1.66) (BIOS version)
7647 bd 06/15/2005 (BIOS date)
7648 svn IBM (system vendor)
7649 pn 2371H4G (product name)
7650 pvr ThinkPadX40 (product version)
7651 rvn IBM (board vendor)
7652 rn 2371H4G (board name)
7653 rvr NotAvailable (board version)
7654 cvn IBM (chassis vendor)
7655 ct 10 (chassis type)
7656 cvr NotAvailable (chassis version)
7657 &lt;/pre&gt;
7658
7659 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7660 found in the dmidecode source:&lt;/p&gt;
7661
7662 &lt;pre&gt;
7663 3 Desktop
7664 4 Low Profile Desktop
7665 5 Pizza Box
7666 6 Mini Tower
7667 7 Tower
7668 8 Portable
7669 9 Laptop
7670 10 Notebook
7671 11 Hand Held
7672 12 Docking Station
7673 13 All In One
7674 14 Sub Notebook
7675 15 Space-saving
7676 16 Lunch Box
7677 17 Main Server Chassis
7678 18 Expansion Chassis
7679 19 Sub Chassis
7680 20 Bus Expansion Chassis
7681 21 Peripheral Chassis
7682 22 RAID Chassis
7683 23 Rack Mount Chassis
7684 24 Sealed-case PC
7685 25 Multi-system
7686 26 CompactPCI
7687 27 AdvancedTCA
7688 28 Blade
7689 29 Blade Enclosing
7690 &lt;/pre&gt;
7691
7692 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7693 table. For example my home server is a tower, but the DMI modalias
7694 claim it is a desktop.&lt;/p&gt;
7695
7696 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7697
7698 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7699 test machine:&lt;/p&gt;
7700
7701 &lt;p&gt;&lt;blockquote&gt;
7702 serio:ty01pr00id00ex00
7703 &lt;/blockquote&gt;&lt;/p&gt;
7704
7705 &lt;p&gt;The values present are&lt;/p&gt;
7706
7707 &lt;pre&gt;
7708 ty 01 (type)
7709 pr 00 (prototype)
7710 id 00 (id)
7711 ex 00 (extra)
7712 &lt;/pre&gt;
7713
7714 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7715 the valid values are.&lt;/p&gt;
7716
7717 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7718
7719 &lt;p&gt;There are heaps of other modalias subtypes according to
7720 file2alias.c. There is the rest of the list from that source: amba,
7721 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7722 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7723 vmbus, x86cpu and zorro. I did not spend time documenting all of
7724 these, as they do not seem relevant for my intended use with mapping
7725 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7726
7727 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7728
7729 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7730 one can use the following shell script:&lt;/p&gt;
7731
7732 &lt;pre&gt;
7733 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7734 echo &quot;$id&quot; ; \
7735 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7736 done
7737 &lt;/pre&gt;
7738
7739 &lt;p&gt;The output can look like this (only the first few entries as the
7740 list is very long on my test machine):&lt;/p&gt;
7741
7742 &lt;pre&gt;
7743 acpi:ACPI0003:
7744 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7745 acpi:device:
7746 FATAL: Module acpi:device: not found.
7747 acpi:IBM0068:
7748 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7749 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7750 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7751 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7752 acpi:IBM0071:PNP0511:
7753 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7754 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7755 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7756 [...]
7757 &lt;/pre&gt;
7758
7759 &lt;p&gt;If you want to help implementing a system to let us propose what
7760 packages to install when new hardware is plugged into a Debian
7761 machine, please send me an email or talk to me on
7762 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7763
7764 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7765 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7766 in /sys/ with space in them.&lt;/p&gt;
7767 </description>
7768 </item>
7769
7770 <item>
7771 <title>Moved the pymissile Debian packaging to collab-maint</title>
7772 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7773 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7774 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7775 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7776 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7777 Launcher and updated the Debian package
7778 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7779 sure udev will fix the device permissions when it is plugged in. I
7780 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7781 hopefully make the package be proposed by jockey in Ubuntu when a user
7782 plug in his rocket launcher. In the process I moved the source to a
7783 git repository under collab-maint, to make it easier for any DD to
7784 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7785 is not very active, but the software still work for me even after five
7786 years of relative silence. The new git repository is not listed in
7787 the uploaded package yet, because I want to test the other changes a
7788 bit more before I upload the new version. If you want to check out
7789 the new version with a .desktop file included, visit the
7790 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7791 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7792 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7793 </description>
7794 </item>
7795
7796 <item>
7797 <title>Lets make hardware dongles easier to use in Debian</title>
7798 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7799 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7800 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7801 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7802 general, is that there is a great package management system with the
7803 ability to automatically install software packages by downloading them
7804 from the distribution mirrors, but no way to get it to automatically
7805 install the packages I need to use the hardware I plug into my
7806 machine. Even if the package to use it is easily available from the
7807 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7808 suggest to automatically install the python-nxt, nbc and t2n packages
7809 I need to talk to it. When I plug in a Yubikey, it could propose the
7810 yubikey-personalization package. The information required to do this
7811 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7812
7813 &lt;p&gt;Some years ago, I proposed to
7814 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7815 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7816 simple:
7817
7818 &lt;ul&gt;
7819
7820 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7821 starting when a user log in.&lt;/li&gt;
7822
7823 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7824 hardware is inserted into the computer.&lt;/li&gt;
7825
7826 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7827 database mapping to packages, and take note of any non-installed
7828 packages.&lt;/li&gt;
7829
7830 &lt;li&gt;Show a message to the user proposing to install the discovered
7831 package, and make it easy to install it.&lt;/li&gt;
7832
7833 &lt;/ul&gt;
7834
7835 &lt;p&gt;I am not sure what the best way to implement this is, but my
7836 initial idea was to use dbus events to discover new hardware, the
7837 discover database to find packages and
7838 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7839 packages.&lt;/p&gt;
7840
7841 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7842 draft package is now checked into
7843 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7844 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7845 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7846 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7847 the relevant packages in Debian, and uploaded a new version
7848 2.2013.01.09 to unstable. I also discovered that the current
7849 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7850 package in Debian no longer discovered any USB devices, because
7851 /proc/bus/usb/devices is no longer present. I ported it to use
7852 libusb as a fall back option to get it working. The fixed package
7853 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7854 because of the freeze).&lt;/p&gt;
7855
7856 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7857 desktop notification to show up (only once, the first time it is
7858 inserted):&lt;/p&gt;
7859
7860 &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;
7861
7862 &lt;p&gt;For this prototype to be really useful, some way to automatically
7863 install the proposed packages by pressing the &quot;Please install
7864 program(s)&quot; button should to be implemented.&lt;/p&gt;
7865
7866 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7867 happen, please help me update the discover-data database with mappings
7868 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7869 list the package you would like to have installed when a given
7870 hardware device is inserted into your computer, and report bugs using
7871 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7872 such mapping, please let me know.&lt;/p&gt;
7873
7874 &lt;p&gt;This prototype need more work, and there are several questions that
7875 should be considered before it is ready for production use. Is dbus
7876 the correct way to detect new hardware? At the moment I look for HAL
7877 dbus events on the system bus, because that is the events I could see
7878 on my Debian Squeeze KDE desktop. Are there better events to use?
7879 How should the user be notified? Is the desktop notification
7880 mechanism the best option, or should the background daemon raise a
7881 popup instead? How should packages be installed? When should they
7882 not be installed?&lt;/p&gt;
7883
7884 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7885 please send me an email. :)&lt;/p&gt;
7886 </description>
7887 </item>
7888
7889 <item>
7890 <title>New IRC channel for LEGO designers using Debian</title>
7891 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7892 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7893 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7894 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7895 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7896 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7897 discovered I had to build all the tools myself because none were
7898 already in Debian Squeeze. If Debian support for LEGO is something
7899 you care about, please join me on the IRC channel
7900 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7901 irc.debian.org). There is a lot that could be done to improve the
7902 Debian support for LEGO designers. For example both CAD software
7903 and Mindstorm compilers are missing. :)&lt;/p&gt;
7904
7905 &lt;p&gt;Update 2012-01-03: A
7906 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7907 including links to Lego related packages is now available.&lt;/p&gt;
7908 </description>
7909 </item>
7910
7911 <item>
7912 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7913 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7914 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7915 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7916 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7917 year! I hope next year will prove to be a good year.&lt;/p&gt;
7918
7919 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7920 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7921 between each other with minimal overhead, is a very interesting
7922 experiment. And as I wrote a few days ago, the bitcoin situation in
7923 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7924 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7925 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7926 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7927 for one of the ftpmasters to approve the new bitcoin-qt package
7928 name.&lt;/p&gt;
7929
7930 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7931 team in Debian, you can easily test the package in Debian Squeeze
7932 using the following steps to get a set of working packages:&lt;/p&gt;
7933
7934 &lt;blockquote&gt;&lt;pre&gt;
7935 git clone git://git.debian.org/git/collab-maint/bitcoin
7936 cd bitcoin
7937 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7938 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7939 &lt;/pre&gt;&lt;/blockquote&gt;
7940
7941 &lt;p&gt;You might have to install some build dependencies as well. The
7942 list of commands should give you two packages, bitcoind and
7943 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7944 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7945 around 5.6 GiB of data on my machine at the moment. Make sure your
7946 ~/.bitcoin/ directory have lots of spare room if you want to download
7947 all the blocks. The client will warn if the disk is getting full, so
7948 there is not really a problem if you got too little room, but you will
7949 not be able to get all the features out of the client.&lt;/p&gt;
7950
7951 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7952 activities, please send Bitcoin donations to my address
7953 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7954 </description>
7955 </item>
7956
7957 <item>
7958 <title>A word on bitcoin support in Debian</title>
7959 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7961 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7962 <description>&lt;p&gt;It has been a while since I wrote about
7963 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7964 peer-to-peer based crypto-currency, and the reason is simply that I
7965 have been busy elsewhere. But two days ago, I started looking at the
7966 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7967 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7968 is now maintained by a
7969 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7970 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7971 owe a huge thank you to all these team members. :)
7972 But I was sad to discover that the bitcoin client is missing in
7973 Wheezy. It is only available in Sid (and an outdated client from
7974 backports). The client had several RC bugs registered in BTS blocking
7975 it from entering testing. To try to help the team and improve the
7976 situation, I spent some time providing patches and triaging the bug
7977 reports. I also had a look at the bitcoin package available from Matt
7978 Corallo in a
7979 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7980 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7981 Debian package.&lt;/p&gt;
7982
7983 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7984 IRC, I pushed several patches into the collab-maint git repository to
7985 improve the package. It now contains fixes for the RC issues (not from
7986 me, but fixed by Scott Howard), build rules for a Qt GUI client
7987 package, konqueror support for the bitcoin: URI and bash completion
7988 setup. As I work on Debian Squeeze, I also created
7989 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7990 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7991 it and try to integrate it into the git repository before uploading a
7992 new version to unstable.
7993
7994 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7995 centralized control currently exercised in the monetary system. I
7996 find it completely unacceptable that the USA government is collecting
7997 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7998 that the major credit card companies can block legal money
7999 transactions to Wikileaks. But for bitcoin to succeed, more people
8000 need to use bitcoins, and more people need to accept bitcoins when
8001 they sell products and services. Improving the bitcoin support in
8002 Debian is a small step in the right direction, but not enough.
8003 Unfortunately the user experience when browsing the web and wanting to
8004 pay with bitcoin is still not very good. The bitcoin: URI is a step
8005 in the right direction, but need to work in most or every browser in
8006 use. Also the bitcoin-qt client is too heavy to fire up to do a
8007 quick transaction. I believe there are other clients available, but
8008 have not tested them.&lt;/p&gt;
8009
8010 &lt;p&gt;My
8011 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
8012 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
8013 I received 20.15 BTC so far on the address I provided in my blog two
8014 years ago, as can be
8015 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
8016 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
8017 donation. The blockexplorer service demonstrates quite well that
8018 bitcoin is not quite anonymous and untracked. :) I wonder if the
8019 number of users have gone up since then. If you use bitcoin and want
8020 to show your support of my activity, please send Bitcoin donations to
8021 the same address as last time,
8022 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8023 </description>
8024 </item>
8025
8026 <item>
8027 <title>Git repository for song book for Computer Scientists</title>
8028 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
8029 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
8030 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
8031 <description>&lt;p&gt;As I
8032 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
8033 this summer&lt;/a&gt;, I have created a Computer Science song book a few
8034 years ago, and today I finally found time to create a public
8035 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
8036 repository for the project&lt;/a&gt;.&lt;/p&gt;
8037
8038 &lt;p&gt;If you want to help out, please clone the source and submit patches
8039 to the HTML version. To generate the PDF and PostScript version,
8040 please use prince XML, or let me know about a useful free software
8041 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
8042
8043 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
8044 PostScript formats at
8045 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
8046 Science Songbook&lt;/a&gt;.&lt;/p&gt;
8047 </description>
8048 </item>
8049
8050 <item>
8051 <title>Gratulerer med 19-årsdagen, Debian!</title>
8052 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
8053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
8054 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
8055 <description>&lt;p&gt;I dag fyller
8056 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
8057 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
8058 si gratulerer med dagen, Debian!&lt;/p&gt;
8059 </description>
8060 </item>
8061
8062 <item>
8063 <title>Song book for Computer Scientists</title>
8064 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
8065 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
8066 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
8067 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
8068 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
8069 collecting computer related songs for use at parties. The original
8070 version was written in LaTeX, but a few years ago I got help from
8071 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
8072 while keeping the ability to create a nice book in PDF format. I have
8073 not had time to maintain the book for a while now, and guess I should
8074 put it up on some public version control repository where others can
8075 help me extend and update the book. If anyone is volunteering to help
8076 me with this, send me an email. Also let me know if there are songs
8077 missing in my book.&lt;/p&gt;
8078
8079 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
8080 me today that I really should let all my readers share the joys of
8081 singing out load about programming, computers and computer networks.
8082 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
8083 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
8084 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
8085 Computer Science Songbook&lt;/a&gt;.
8086 </description>
8087 </item>
8088
8089 <item>
8090 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
8091 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
8092 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
8093 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
8094 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
8095 around 1000 at the moment. To be able to get help from the vendors
8096 when something go wrong, we want to keep the firmware on the servers
8097 up to date. If the firmware isn&#39;t the latest and greatest, the
8098 vendors typically refuse to start debugging any problems until the
8099 firmware is upgraded. So before every reboot, we want to upgrade the
8100 firmware, and we would really like everyone handling servers at the
8101 university to do this themselves when they plan to reboot a machine.
8102 For that to happen we at the unix server admin group need to provide
8103 the tools to do so.&lt;/p&gt;
8104
8105 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
8106 fetch and install the latest firmware for the servers we got. Most of
8107 our hardware are from Dell and HP, so I have focused on these servers
8108 so far. This blog post is about the Dell part.&lt;/P&gt;
8109
8110 &lt;p&gt;On the Dell FTP site I was lucky enough to find
8111 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
8112 with firmware information for all 11th generation servers, listing
8113 which firmware should be used on a given model and where on the FTP
8114 site I can find it. Using a simple perl XML parser I can then
8115 download the shell scripts Dell provides to do firmware upgrades from
8116 within Linux and reboot when all the firmware is primed and ready to
8117 be activated on the first reboot.&lt;/p&gt;
8118
8119 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
8120 Are there anyone working on similar tools for firmware upgrading all
8121 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
8122
8123 &lt;p&gt;&lt;pre&gt;
8124 #!/usr/bin/perl
8125 use strict;
8126 use warnings;
8127 use File::Temp qw(tempdir);
8128 BEGIN {
8129 # Install needed RHEL packages if missing
8130 my %rhelmodules = (
8131 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
8132 );
8133 for my $module (keys %rhelmodules) {
8134 eval &quot;use $module;&quot;;
8135 if ($@) {
8136 my $pkg = $rhelmodules{$module};
8137 system(&quot;yum install -y $pkg&quot;);
8138 eval &quot;use $module;&quot;;
8139 }
8140 }
8141 }
8142 my $errorsto = &#39;pere@hungry.com&#39;;
8143
8144 upgrade_dell();
8145
8146 exit 0;
8147
8148 sub run_firmware_script {
8149 my ($opts, $script) = @_;
8150 unless ($script) {
8151 print STDERR &quot;fail: missing script name\n&quot;;
8152 exit 1
8153 }
8154 print STDERR &quot;Running $script\n\n&quot;;
8155
8156 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
8157 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
8158 } else {
8159 print STDERR &quot;fail: firmware script returned error\n&quot;;
8160 }
8161 }
8162
8163 sub run_firmware_scripts {
8164 my ($opts, @dirs) = @_;
8165 # Run firmware packages
8166 for my $dir (@dirs) {
8167 print STDERR &quot;info: Running scripts in $dir\n&quot;;
8168 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
8169 while (my $s = readdir $dh) {
8170 next if $s =~ m/^\.\.?/;
8171 run_firmware_script($opts, &quot;$dir/$s&quot;);
8172 }
8173 closedir $dh;
8174 }
8175 }
8176
8177 sub download {
8178 my $url = shift;
8179 print STDERR &quot;info: Downloading $url\n&quot;;
8180 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
8181 }
8182
8183 sub upgrade_dell {
8184 my @dirs;
8185 my $product = `dmidecode -s system-product-name`;
8186 chomp $product;
8187
8188 if ($product =~ m/PowerEdge/) {
8189
8190 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8191 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
8192
8193 my $tmpdir = tempdir(
8194 CLEANUP =&gt; 1
8195 );
8196 chdir($tmpdir);
8197 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
8198 system(&#39;gunzip Catalog.xml.gz&#39;);
8199 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
8200 # -q is quiet, disabling interactivity and reducing console output
8201 my $fwopts = &quot;-q&quot;;
8202 if (@paths) {
8203 for my $url (@paths) {
8204 fetch_dell_fw($url);
8205 }
8206 run_firmware_scripts($fwopts, $tmpdir);
8207 } else {
8208 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8209 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8210 }
8211 chdir(&#39;/&#39;);
8212 } else {
8213 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8214 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8215 }
8216 }
8217
8218 sub fetch_dell_fw {
8219 my $path = shift;
8220 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
8221 download($url);
8222 }
8223
8224 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8225 # firmware packages to download from Dell. Only work for Linux
8226 # machines and 11th generation Dell servers.
8227 sub fetch_dell_fw_list {
8228 my $filename = shift;
8229
8230 my $product = `dmidecode -s system-product-name`;
8231 chomp $product;
8232 my ($mybrand, $mymodel) = split(/\s+/, $product);
8233
8234 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
8235
8236 my $xml = XMLin($filename);
8237 my @paths;
8238 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
8239 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
8240 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
8241 my $oscode;
8242 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
8243 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
8244 } else {
8245 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
8246 }
8247 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
8248 {
8249 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
8250 }
8251 }
8252 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
8253 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
8254
8255 # Drop application packages, only firmware and BIOS
8256 next if &#39;APAC&#39; eq $componenttype;
8257
8258 my $cpath = $component-&gt;{path};
8259 for my $path (@paths) {
8260 if ($cpath =~ m%/$path$%) {
8261 push(@paths, $cpath);
8262 }
8263 }
8264 }
8265 return @paths;
8266 }
8267 &lt;/pre&gt;
8268
8269 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
8270 it could work on other platforms with some tweaking. Anyone know a
8271 index like Catalog.xml is available from HP for HP servers? At the
8272 moment I maintain a similar list manually and it is quickly getting
8273 outdated.&lt;/p&gt;
8274 </description>
8275 </item>
8276
8277 <item>
8278 <title>How is booting into runlevel 1 different from single user boots?</title>
8279 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
8280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
8281 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
8282 <description>&lt;p&gt;Wouter Verhelst have some
8283 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
8284 comments and opinions&lt;/a&gt; on my blog post on
8285 &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
8286 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
8287 &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
8288 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
8289 small piece of his comment now, and though it best to address the
8290 misunderstanding he bring forward:&lt;/p&gt;
8291
8292 &lt;p&gt;&lt;blockquote&gt;
8293 Currently, a system admin has four options: [...] boot to a
8294 single-user system (by adding &#39;single&#39; to the kernel command line;
8295 this runs rcS and rc1 scripts)
8296 &lt;/blockquote&gt;&lt;/p&gt;
8297
8298 &lt;p&gt;This make me believe Wouter believe booting into single user mode
8299 and booting into runlevel 1 is the same. I am not surprised he
8300 believe this, because it would make sense and is a quite sensible
8301 thing to believe. But because the boot in Debian is slightly broken,
8302 runlevel 1 do not work properly and it isn&#39;t the same as single user
8303 mode. I&#39;ll try to explain what is actually happing, but it is a bit
8304 hard to explain.&lt;/p&gt;
8305
8306 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
8307 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
8308 executed in single user mode is sulogin. Single user mode is a boot
8309 state &quot;between&quot; the runlevels, and when booting into single user mode,
8310 only the scripts in /etc/rcS.d/ are executed before the init process
8311 enters the single user state. When switching to runlevel 1, the state
8312 is in fact not ending in runlevel 1, but it passes through runlevel 1
8313 and end up in the single user mode (see /etc/rc1.d/S03single, which
8314 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
8315 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
8316 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8317 mode).&lt;/p&gt;
8318
8319 &lt;p&gt;This summary might make it clearer. When booting for the first
8320 time into single user mode, the following commands are executed:
8321 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
8322 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
8323 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
8324 trying to continue after visiting single user mode. Not all services
8325 are started again as they should, causing the machine to end up in an
8326 unpredicatble state. This is why Debian admins recommend rebooting
8327 after visiting single user mode.&lt;/p&gt;
8328
8329 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
8330 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
8331 to runlevel 1, the services started from /etc/rcS.d/ are not properly
8332 stopped when passing through the scripts in /etc/rc1.d/, and not
8333 started again when switching away from runlevel 1 to the runlevels
8334 2-5. I believe the problem is best fixed by moving all the scripts
8335 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
8336 functioning single user mode during boot.&lt;/p&gt;
8337
8338 &lt;p&gt;I have spent several years investigating the Debian boot system,
8339 and discovered this problem a few years ago. I suspect it originates
8340 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
8341 </description>
8342 </item>
8343
8344 <item>
8345 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
8346 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
8347 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
8348 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
8349 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
8350 are started from /etc/rcS.d/. In fact, there is a bite more of them
8351 than make sense, and this causes a few problems. What kind of
8352 problems, you might ask. There are at least two problems. The first
8353 is that it is not possible to recover a machine after switching to
8354 runlevel 1. One need to actually reboot to get the machine back to
8355 the expected state. The other is that single user boot will sometimes
8356 run into problems because some of the subsystems are activated before
8357 the root login is presented, causing problems when trying to recover a
8358 machine from a problem in that subsystem. A minor additional point is
8359 that moving more scripts out of rcS.d/ and into the other rc#.d/
8360 directories will increase the amount of scripts that can run in
8361 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
8362
8363 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
8364 scripts that _have_ to execute before the root login prompt is
8365 presented during a single user boot should go there. Everything else
8366 should go into the numeric runlevels. This means things like
8367 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8368 the numeric runlevels. Today in Debian, there are around 115 init.d
8369 scripts that are started from rcS.d/, and most of them should be moved
8370 out. Do your package have one of them? Please help us make single
8371 user and runlevel 1 better by moving it.&lt;/p&gt;
8372
8373 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
8374 etc. should still be started from rcS.d/, but there is for example no
8375 need to have the network enabled before the single user login prompt
8376 is presented.&lt;/p&gt;
8377
8378 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
8379 Debian systems working while scripts migrate and during upgrades, the
8380 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8381 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8382 and the next ones can only be moved when their dependencies have been
8383 moved first. This migration must be done sequentially while we ensure
8384 that the package system upgrade packages in the right order to keep
8385 the system state correct. This will require some coordination when it
8386 comes to network related packages, but most of the packages with
8387 scripts that should migrate do not have anything in rcS.d/ depending
8388 on them. Some packages have already been updated, like the sudo
8389 package, while others are still left to do. I wish I had time to work
8390 on this myself, but real live constrains make it unlikely that I will
8391 find time to push this forward.&lt;/p&gt;
8392 </description>
8393 </item>
8394
8395 <item>
8396 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
8397 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
8398 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
8399 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
8400 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
8401 mentioned the issues I believe should be improved in Debian for its
8402 desktop to be useful for more people. The use case for this is my
8403 parents, which are currently running Kubuntu which solve the
8404 issues.&lt;/p&gt;
8405
8406 &lt;p&gt;I suspect these four missing features are not very hard to
8407 implement. After all, they are present in Ubuntu, so if we wanted to
8408 do this in Debian we would have a source.&lt;/p&gt;
8409
8410 &lt;ol&gt;
8411
8412 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
8413 are new packages available for upgrades, a icon in the KDE status bar
8414 indicate this, and clicking on it will activate the simple upgrade
8415 tool to handle it. I have no problem guiding both of my parents
8416 through the process over the phone. If a kernel reboot is required,
8417 this too is indicated by the status bars and the upgrade tool. Last
8418 time I checked, nothing with the same features was working in KDE in
8419 Debian.&lt;/li&gt;
8420
8421 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
8422 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
8423 currently have a handler for, it will ask the user if the system
8424 should search for a package that would add support for this MIME type,
8425 and if the user say yes, the APT sources will be searched for packages
8426 advertising the MIME type in their control file (visible in the
8427 Packages file in the APT archive). If one or more packages are found,
8428 it is a simple click of the mouse to add support for the missing mime
8429 type. If the package require the user to accept some non-free
8430 license, this is explained to the user. The entire process make it
8431 more clear to the user why something do not work in the browser, and
8432 make the chances higher for the user to blame the web page authors and
8433 not the browser for any missing features.&lt;/li&gt;
8434
8435 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
8436 handlers.&lt;/strong&gt; When the media players encounter a format or codec
8437 it is not supporting, a dialog pop up asking the user if the system
8438 should search for a package that would add support for it. This
8439 happen with things like MP3, Windows Media or H.264. The selection
8440 and installation procedure is very similar to the Firefox browser
8441 plugin handling. This is as far as I know implemented using a
8442 gstreamer hook. The end result is that the user easily get access to
8443 the codecs that are present from the APT archives available, while
8444 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
8445
8446 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
8447 displaying a text/plain file in my Debian browser, it will propose to
8448 start emacs to show it. If I remember correctly, when doing the same
8449 in Kunbutu it show the file as a text file in the browser. At least I
8450 know Opera will show text files within the browser. I much prefer the
8451 latter behaviour.&lt;/li&gt;
8452
8453 &lt;/ol&gt;
8454
8455 &lt;p&gt;There are other nice features as well, like the simplified suite
8456 upgrader, but given that I am the one mostly doing the dist-upgrade,
8457 it do not matter much.&lt;/p&gt;
8458
8459 &lt;p&gt;I really hope we could get these features in place for the next
8460 Debian release. It would require the coordinated effort of several
8461 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
8462 </description>
8463 </item>
8464
8465 <item>
8466 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
8467 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
8468 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
8469 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
8470 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
8471 site is build on Debian/Squeeze, and this platform was chosen because
8472 I am most familiar with Debian (being a Debian Developer for around 10
8473 years) because it is the latest stable Debian release which should get
8474 security support for a few years.&lt;/p&gt;
8475
8476 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
8477 that are missing in Debian at the moment. It would be great if these
8478 modules were added to the Debian archive, allowing anyone to set up
8479 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
8480 in their own country using only Debian packages. The list of modules
8481 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
8482 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
8483 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8484 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8485 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8486 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8487 easier in the future.&lt;/p&gt;
8488
8489 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
8490 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
8491 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
8492 with the responsibility of tracking security problems, which I really
8493 do not have time for.&lt;/p&gt;
8494 </description>
8495 </item>
8496
8497 <item>
8498 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
8499 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
8500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
8501 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
8502 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
8503 posts have been in Norwegian the last few weeks, so here is a short
8504 update in English.&lt;/p&gt;
8505
8506 &lt;p&gt;The kids still keep me too busy to get much free software work
8507 done, but I did manage to organise a project to get a Norwegian port
8508 of the British service
8509 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8510 and it has been running for a month now. The entire project has been
8511 organised by me and two others. Around Christmas we gathered sponsors
8512 to fund the development work. In January I drafted a contract with
8513 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8514 and in February the development took place. Most of it involved
8515 converting the source to use GPS coordinates instead of British
8516 easting/northing, and the resulting code should be a lot easier to get
8517 running in any country by now. The Norwegian
8518 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8519 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8520 source and the source for administrative borders in Norway, and
8521 support for this had to be added/fixed.&lt;/p&gt;
8522
8523 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8524 polishing the system before we announced it March 7th. The system is
8525 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8526 problem reports in a few weeks. Soon we hope to announce the Android
8527 and iPhone versions making it even easier to report problems with the
8528 public infrastructure.&lt;/p&gt;
8529
8530 &lt;p&gt;Perhaps something to consider for those of you in countries without
8531 such service?&lt;/p&gt;
8532 </description>
8533 </item>
8534
8535 <item>
8536 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8537 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8539 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8540 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8541 issues here at my work with the University of Oslo. My idea is that
8542 it should be possible to use the information about security issues
8543 available on the Internet, and check our locally
8544 maintained/distributed software against this information. It should
8545 allow us to verify that no known security issues are forgotten. The
8546 CVE database listing vulnerabilities seem like a great central point,
8547 and by using the package lists from Debian mapped to CVEs provided by
8548 the testing security team, I believed it should be possible to figure
8549 out which security holes were present in our free software
8550 collection.&lt;/p&gt;
8551
8552 &lt;p&gt;After reading up on the topic, it became obvious that the first
8553 building block is to be able to name software packages in a unique and
8554 consistent way across data sources. I considered several ways to do
8555 this, for example coming up with my own naming scheme like using URLs
8556 to project home pages or URLs to the Freshmeat entries, or using some
8557 existing naming scheme. And it seem like I am not the first one to
8558 come across this problem, as MITRE already proposed and implemented a
8559 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8560 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8561 software, hardware and other platform components. The CPE ids are
8562 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8563 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8564 issues for any CPE name. With this in place, all I need to do is to
8565 locate the CPE id for the software packages we use at the university.
8566 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8567 NVD entry if a CVE for the package exist).&lt;/p&gt;
8568
8569 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8570 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8571 check out, one could look up
8572 &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
8573 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8574 The most recent one is
8575 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8576 and at the bottom of the NVD page for this vulnerability the complete
8577 list of affected versions is provided.&lt;/p&gt;
8578
8579 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8580 for offline processing of issues. Using this dump, I&#39;ve written a
8581 small script taking a list of CPEs as input and list all CVEs
8582 affecting the packages represented by these CPEs. One give it CPEs
8583 with version numbers as specified above and get a list of open
8584 security issues out.&lt;/p&gt;
8585
8586 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8587 information need to be high. For that to happen, I believe as many as
8588 possible need to use and contribute to the NVD database. I notice
8589 RHEL is providing
8590 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8591 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8592 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8593
8594 &lt;p&gt;To get an idea about the quality for free software, I spent some
8595 time making it possible to compare the CVE database from Debian with
8596 the CVE database in NVD. The result look fairly good, but there are
8597 some inconsistencies in NVD (same software package having several
8598 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8599 Debian believe are affected by a CVE). Hope to find time to improve
8600 the quality of NVD, but that require being able to get in touch with
8601 someone maintaining it. So far my three emails with questions and
8602 corrections have not seen any reply, but I hope contact can be
8603 established soon.&lt;/p&gt;
8604
8605 &lt;p&gt;An interesting application for CPEs is cross platform package
8606 mapping. It would be useful to know which packages in for example
8607 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8608 this would be trivial if all linux distributions provided CPE entries
8609 for their packages.&lt;/p&gt;
8610 </description>
8611 </item>
8612
8613 <item>
8614 <title>Which module is loaded for a given PCI and USB device?</title>
8615 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8617 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8618 <description>&lt;p&gt;In the
8619 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8620 package in Debian, there is a script to report useful information
8621 about the running hardware for use when people report missing
8622 information. One part of this script that I find very useful when
8623 debugging hardware problems, is the part mapping loaded kernel module
8624 to the PCI device it claims. It allow me to quickly see if the kernel
8625 module I expect is driving the hardware I am struggling with. To see
8626 the output, make sure discover-data is installed and run
8627 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8628 one of my machines like this:&lt;/p&gt;
8629
8630 &lt;pre&gt;
8631 loaded modules:
8632 10de:03eb i2c_nforce2
8633 10de:03f1 ohci_hcd
8634 10de:03f2 ehci_hcd
8635 10de:03f0 snd_hda_intel
8636 10de:03ec pata_amd
8637 10de:03f6 sata_nv
8638 1022:1103 k8temp
8639 109e:036e bttv
8640 109e:0878 snd_bt87x
8641 11ab:4364 sky2
8642 &lt;/pre&gt;
8643
8644 &lt;p&gt;The code in question look like this, slightly modified for
8645 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8646
8647 &lt;pre&gt;
8648 if [ -d /sys/bus/pci/devices/ ] ; then
8649 echo loaded pci modules:
8650 (
8651 cd /sys/bus/pci/devices/
8652 for address in * ; do
8653 if [ -d &quot;$address/driver/module&quot; ] ; then
8654 module=`cd $address/driver/module ; pwd -P | xargs basename`
8655 if grep -q &quot;^$module &quot; /proc/modules ; then
8656 address=$(echo $address |sed s/0000://)
8657 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8658 echo &quot;$id $module&quot;
8659 fi
8660 fi
8661 done
8662 )
8663 echo
8664 fi
8665 &lt;/pre&gt;
8666
8667 &lt;p&gt;Similar code could be used to extract USB device module
8668 mappings:&lt;/p&gt;
8669
8670 &lt;pre&gt;
8671 if [ -d /sys/bus/usb/devices/ ] ; then
8672 echo loaded usb modules:
8673 (
8674 cd /sys/bus/usb/devices/
8675 for address in * ; do
8676 if [ -d &quot;$address/driver/module&quot; ] ; then
8677 module=`cd $address/driver/module ; pwd -P | xargs basename`
8678 if grep -q &quot;^$module &quot; /proc/modules ; then
8679 address=$(echo $address |sed s/0000://)
8680 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8681 if [ &quot;$id&quot; ] ; then
8682 echo &quot;$id $module&quot;
8683 fi
8684 fi
8685 fi
8686 done
8687 )
8688 echo
8689 fi
8690 &lt;/pre&gt;
8691
8692 &lt;p&gt;This might perhaps be something to include in other tools as
8693 well.&lt;/p&gt;
8694 </description>
8695 </item>
8696
8697 <item>
8698 <title>How to test if a laptop is working with Linux</title>
8699 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8701 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8702 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8703 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8704 batch of computers will work with Linux. Every year for the last few
8705 years the university have organised shared bid of a few thousand
8706 computers, and this year HP won the bid. Two different desktops and
8707 five different laptops are on the list this year. We in the UNIX
8708 group want to know which one of these computers work well with RHEL
8709 and Ubuntu, the two Linux distributions we currently handle at the
8710 university.&lt;/p&gt;
8711
8712 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8713 perhaps inspire others to test hardware as well. To test, I PXE
8714 install the OS version of choice, and log in as my normal user and run
8715 a few applications and plug in selected pieces of hardware. When
8716 something fail, I make a note about this in the test matrix and move
8717 on. If I have some spare time I try to report the bug to the OS
8718 vendor, but as I only have the machines for a short time, I rarely
8719 have the time to do this for all the problems I find.&lt;/p&gt;
8720
8721 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8722 I perform on a new model.&lt;/p&gt;
8723
8724 &lt;ul&gt;
8725
8726 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8727 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8728 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8729
8730 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8731 installation, X.org is working.&lt;/li&gt;
8732
8733 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8734 package mesa-utils on Ubuntu) and writing down the frames per second
8735 reported by the program.&lt;/li&gt;
8736
8737 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8738 logging in, and if I can hear this the test is successful. If there
8739 are several audio exits on the machine, I try them all and check if
8740 the Gnome/KDE audio mixer can control where to send the sound. I
8741 normally test this by playing
8742 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8743 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8744
8745 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8746 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8747
8748 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8749 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8750
8751 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8752 picture from the v4l device show up.&lt;/li&gt;
8753
8754 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8755 any bluetooth devices are discovered. In my office, I normally see a
8756 few.&lt;/li&gt;
8757
8758 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8759 memory modules lying around, and stick them in and see if Gnome/KDE
8760 notice this.&lt;/li&gt;
8761
8762 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8763 special button work, and if the laptop continue to work after
8764 resume.&lt;/li&gt;
8765
8766 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8767 adjusting background light, switching on/off external video output,
8768 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8769 laptop to laptop, so I just write down which are working and which are
8770 not.&lt;/li&gt;
8771
8772 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8773 acceleration sensors etc. I rarely test these, as I do not know how
8774 to quickly test if they are working or not, so I only document their
8775 existence.&lt;/li&gt;
8776
8777 &lt;/ul&gt;
8778
8779 &lt;p&gt;By now I suspect you are really curious what the test results are
8780 for the HP machines I am testing. I&#39;m not done yet, so I will report
8781 the test results later. For now I can report that HP 8100 Elite work
8782 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8783 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8784 can see, I have most machines left to test. One interesting
8785 observation is that Ubuntu Lucid has almost twice the frame rate than
8786 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8787 </description>
8788 </item>
8789
8790 <item>
8791 <title>Some thoughts on BitCoins</title>
8792 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8793 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8794 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8795 <description>&lt;p&gt;As I continue to explore
8796 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8797 what properties the system have, and how it will be affected by laws
8798 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8799
8800 &lt;p&gt;One interesting thing to note is that since the transactions are
8801 verified using a peer to peer network, all details about a transaction
8802 is known to everyone. This means that if a BitCoin address has been
8803 published like I did with mine in my initial post about BitCoin, it is
8804 possible for everyone to see how many BitCoins have been transfered to
8805 that address. There is even a web service to look at the details for
8806 all transactions. There I can see that my address
8807 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8808 have received 16.06 Bitcoin, the
8809 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8810 address of Simon Phipps have received 181.97 BitCoin and the address
8811 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8812 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8813 every one of you that donated bitcoins to support my activity. The
8814 fact that anyone can see how much money was transfered to a given
8815 address make it more obvious why the BitCoin community recommend to
8816 generate and hand out a new address for each transaction. I&#39;m told
8817 there is no way to track which addresses belong to a given person or
8818 organisation without the person or organisation revealing it
8819 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8820
8821 &lt;p&gt;In Norway, and in most other countries, there are laws and
8822 regulations limiting how much money one can transfer across the border
8823 without declaring it. There are money laundering, tax and accounting
8824 laws and regulations I would expect to apply to the use of BitCoin.
8825 If the Skolelinux foundation
8826 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8827 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8828 normal bank transfers like EFF is doing, how should this be accounted?
8829 Given that it is impossible to know if money can cross the border or
8830 not, should everything or nothing be declared? What exchange rate
8831 should be used when calculating taxes? Would receivers have to pay
8832 income tax if the foundation were to pay Skolelinux contributors in
8833 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8834
8835 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8836 accepted by a lot of users. It must be possible to get easy access to
8837 the currency (as a wage or using currency exchanges), and it must be
8838 easy to spend it. At the moment BitCoin seem fairly easy to get
8839 access to, but there are very few places to spend it. I am not really
8840 a regular user of any of the vendor types currently accepting BitCoin,
8841 so I wonder when my kind of shop would start accepting BitCoins. I
8842 would like to buy electronics, travels and subway tickets, not herbs
8843 and books. :) The currency is young, and this will improve over time
8844 if it become popular, but I suspect regular banks will start to lobby
8845 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8846 will claim it is helping fund terrorism and money laundering (which
8847 probably would be true, as is any currency in existence), but I
8848 believe the problems should be solved elsewhere and not by blaming
8849 currencies.&lt;/p&gt;
8850
8851 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8852 CPU intensive process that depend on a bit of luck as well (as one is
8853 competing against all the other miners currently spending CPU cycles
8854 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8855 BitCoin when this happen. Yesterday I came across the obvious way to
8856 join forces to increase ones changes of getting at least some coins,
8857 by coordinating the work on mining BitCoins across several machines
8858 and people, and sharing the result if one is lucky and get the 50
8859 BitCoins. Check out
8860 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8861 if this sounds interesting. I have not had time to try to set up a
8862 machine to participate there yet, but have seen that running on ones
8863 own for a few days have not yield any BitCoins througth mining
8864 yet.&lt;/p&gt;
8865
8866 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8867 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8868 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8869 it was interesting to read. The arguments presented seem to be
8870 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8871 </description>
8872 </item>
8873
8874 <item>
8875 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8876 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8877 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8878 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8879 <description>&lt;p&gt;With this weeks lawless
8880 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8881 attacks&lt;/a&gt; on Wikileak and
8882 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8883 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8884 not be trusted to handle money transactions.
8885 A blog post from
8886 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8887 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8888 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8889 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8890 some help from my friend to get it all running, and he even handed me
8891 some bitcoins to get started. I even donated a few bitcoins to Simon
8892 for helping me remember BitCoin.&lt;/p&gt;
8893
8894 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8895 crypto-currency, decentralised and handled using peer-to-peer
8896 networks. It allows anonymous transactions and prohibits central
8897 control over the transactions, making it impossible for governments
8898 and companies alike to block donations and other transactions. The
8899 source is free software, and while the key dependency wxWidgets 2.9
8900 for the graphical user interface is missing in Debian, the command
8901 line client builds just fine. Hopefully Jonas
8902 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8903 Debian&lt;/a&gt; soon.&lt;/p&gt;
8904
8905 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8906 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8907 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8908 currency &quot;stock&quot; markets where the exchange rate is decided. There
8909 are not many users so far, but the concept seems promising. If you
8910 want to get started and lack a friend with any bitcoins to spare,
8911 you can even get
8912 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8913 bitcoin at the time of writing). Use
8914 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8915 on the current exchange rates.&lt;/p&gt;
8916
8917 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8918 machines. If you want to support my activity, please send Bitcoin
8919 donations to the address
8920 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8921 </description>
8922 </item>
8923
8924 <item>
8925 <title>Why isn&#39;t Debian Edu using VLC?</title>
8926 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8928 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8929 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8930 presented, and the winner among the multimedia player were VLC.
8931 Personally, I like VLC, and it is my player of choice when I first try
8932 to play a video file or stream. Only if VLC fail will I drag out
8933 gmplayer to see if it can do better. The reason is mostly the failure
8934 model and trust. When VLC fail, it normally pop up a error message
8935 reporting the problem. When mplayer fail, it normally segfault or
8936 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8937
8938 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8939 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8940 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8941 plugin to play web videos seamlessly, and the VLC browser plugin is
8942 not very good. For example, it lack in-line control buttons, so there
8943 is no way for the user to pause the video. Also, when I
8944 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8945 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8946 failed on several video pages where mplayer based plugins worked. If
8947 the browser plugin for VLC was as good as the gecko-mediaplayer
8948 package (which uses mplayer), we would switch.&lt;/P&gt;
8949
8950 &lt;p&gt;While VLC is a good player, its user interface is slightly
8951 annoying. The most annoying feature is its inconsistent use of
8952 keyboard shortcuts. When the player is in full screen mode, its
8953 shortcuts are different from when it is playing the video in a window.
8954 For example, space only work as pause when in full screen mode. I
8955 wish it had consisten shortcuts and that space also would work when in
8956 window mode. Another nice shortcut in gmplayer is [enter] to restart
8957 the current video. It is very nice when playing short videos from the
8958 web and want to restart it when new people arrive to have a look at
8959 what is going on.&lt;/p&gt;
8960 </description>
8961 </item>
8962
8963 <item>
8964 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8965 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8966 <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>
8967 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8968 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8969 upgrade testing of the
8970 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8971 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8972 This seem like a very good idea, so I adjusted by test scripts and
8973 can now present the updated result from today:&lt;/p&gt;
8974
8975 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8976
8977 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8978
8979 &lt;blockquote&gt;&lt;p&gt;
8980 apache2.2-bin
8981 aptdaemon
8982 baobab
8983 binfmt-support
8984 browser-plugin-gnash
8985 cheese-common
8986 cli-common
8987 cups-pk-helper
8988 dmz-cursor-theme
8989 empathy
8990 empathy-common
8991 freedesktop-sound-theme
8992 freeglut3
8993 gconf-defaults-service
8994 gdm-themes
8995 gedit-plugins
8996 geoclue
8997 geoclue-hostip
8998 geoclue-localnet
8999 geoclue-manual
9000 geoclue-yahoo
9001 gnash
9002 gnash-common
9003 gnome
9004 gnome-backgrounds
9005 gnome-cards-data
9006 gnome-codec-install
9007 gnome-core
9008 gnome-desktop-environment
9009 gnome-disk-utility
9010 gnome-screenshot
9011 gnome-search-tool
9012 gnome-session-canberra
9013 gnome-system-log
9014 gnome-themes-extras
9015 gnome-themes-more
9016 gnome-user-share
9017 gstreamer0.10-fluendo-mp3
9018 gstreamer0.10-tools
9019 gtk2-engines
9020 gtk2-engines-pixbuf
9021 gtk2-engines-smooth
9022 hamster-applet
9023 libapache2-mod-dnssd
9024 libapr1
9025 libaprutil1
9026 libaprutil1-dbd-sqlite3
9027 libaprutil1-ldap
9028 libart2.0-cil
9029 libboost-date-time1.42.0
9030 libboost-python1.42.0
9031 libboost-thread1.42.0
9032 libchamplain-0.4-0
9033 libchamplain-gtk-0.4-0
9034 libcheese-gtk18
9035 libclutter-gtk-0.10-0
9036 libcryptui0
9037 libdiscid0
9038 libelf1
9039 libepc-1.0-2
9040 libepc-common
9041 libepc-ui-1.0-2
9042 libfreerdp-plugins-standard
9043 libfreerdp0
9044 libgconf2.0-cil
9045 libgdata-common
9046 libgdata7
9047 libgdu-gtk0
9048 libgee2
9049 libgeoclue0
9050 libgexiv2-0
9051 libgif4
9052 libglade2.0-cil
9053 libglib2.0-cil
9054 libgmime2.4-cil
9055 libgnome-vfs2.0-cil
9056 libgnome2.24-cil
9057 libgnomepanel2.24-cil
9058 libgpod-common
9059 libgpod4
9060 libgtk2.0-cil
9061 libgtkglext1
9062 libgtksourceview2.0-common
9063 libmono-addins-gui0.2-cil
9064 libmono-addins0.2-cil
9065 libmono-cairo2.0-cil
9066 libmono-corlib2.0-cil
9067 libmono-i18n-west2.0-cil
9068 libmono-posix2.0-cil
9069 libmono-security2.0-cil
9070 libmono-sharpzip2.84-cil
9071 libmono-system2.0-cil
9072 libmtp8
9073 libmusicbrainz3-6
9074 libndesk-dbus-glib1.0-cil
9075 libndesk-dbus1.0-cil
9076 libopal3.6.8
9077 libpolkit-gtk-1-0
9078 libpt2.6.7
9079 libpython2.6
9080 librpm1
9081 librpmio1
9082 libsdl1.2debian
9083 libsrtp0
9084 libssh-4
9085 libtelepathy-farsight0
9086 libtelepathy-glib0
9087 libtidy-0.99-0
9088 media-player-info
9089 mesa-utils
9090 mono-2.0-gac
9091 mono-gac
9092 mono-runtime
9093 nautilus-sendto
9094 nautilus-sendto-empathy
9095 p7zip-full
9096 pkg-config
9097 python-aptdaemon
9098 python-aptdaemon-gtk
9099 python-axiom
9100 python-beautifulsoup
9101 python-bugbuddy
9102 python-clientform
9103 python-coherence
9104 python-configobj
9105 python-crypto
9106 python-cupshelpers
9107 python-elementtree
9108 python-epsilon
9109 python-evolution
9110 python-feedparser
9111 python-gdata
9112 python-gdbm
9113 python-gst0.10
9114 python-gtkglext1
9115 python-gtksourceview2
9116 python-httplib2
9117 python-louie
9118 python-mako
9119 python-markupsafe
9120 python-mechanize
9121 python-nevow
9122 python-notify
9123 python-opengl
9124 python-openssl
9125 python-pam
9126 python-pkg-resources
9127 python-pyasn1
9128 python-pysqlite2
9129 python-rdflib
9130 python-serial
9131 python-tagpy
9132 python-twisted-bin
9133 python-twisted-conch
9134 python-twisted-core
9135 python-twisted-web
9136 python-utidylib
9137 python-webkit
9138 python-xdg
9139 python-zope.interface
9140 remmina
9141 remmina-plugin-data
9142 remmina-plugin-rdp
9143 remmina-plugin-vnc
9144 rhythmbox-plugin-cdrecorder
9145 rhythmbox-plugins
9146 rpm-common
9147 rpm2cpio
9148 seahorse-plugins
9149 shotwell
9150 software-center
9151 system-config-printer-udev
9152 telepathy-gabble
9153 telepathy-mission-control-5
9154 telepathy-salut
9155 tomboy
9156 totem
9157 totem-coherence
9158 totem-mozilla
9159 totem-plugins
9160 transmission-common
9161 xdg-user-dirs
9162 xdg-user-dirs-gtk
9163 xserver-xephyr
9164 &lt;/p&gt;&lt;/blockquote&gt;
9165
9166 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9167
9168 &lt;blockquote&gt;&lt;p&gt;
9169 cheese
9170 ekiga
9171 eog
9172 epiphany-extensions
9173 evolution-exchange
9174 fast-user-switch-applet
9175 file-roller
9176 gcalctool
9177 gconf-editor
9178 gdm
9179 gedit
9180 gedit-common
9181 gnome-games
9182 gnome-games-data
9183 gnome-nettool
9184 gnome-system-tools
9185 gnome-themes
9186 gnuchess
9187 gucharmap
9188 guile-1.8-libs
9189 libavahi-ui0
9190 libdmx1
9191 libgalago3
9192 libgtk-vnc-1.0-0
9193 libgtksourceview2.0-0
9194 liblircclient0
9195 libsdl1.2debian-alsa
9196 libspeexdsp1
9197 libsvga1
9198 rhythmbox
9199 seahorse
9200 sound-juicer
9201 system-config-printer
9202 totem-common
9203 transmission-gtk
9204 vinagre
9205 vino
9206 &lt;/p&gt;&lt;/blockquote&gt;
9207
9208 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9209
9210 &lt;blockquote&gt;&lt;p&gt;
9211 gstreamer0.10-gnomevfs
9212 &lt;/p&gt;&lt;/blockquote&gt;
9213
9214 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9215
9216 &lt;blockquote&gt;&lt;p&gt;
9217 [nothing]
9218 &lt;/p&gt;&lt;/blockquote&gt;
9219
9220 &lt;p&gt;This is for KDE:&lt;/p&gt;
9221
9222 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9223
9224 &lt;blockquote&gt;&lt;p&gt;
9225 ksmserver
9226 &lt;/p&gt;&lt;/blockquote&gt;
9227
9228 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9229
9230 &lt;blockquote&gt;&lt;p&gt;
9231 kwin
9232 network-manager-kde
9233 &lt;/p&gt;&lt;/blockquote&gt;
9234
9235 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9236
9237 &lt;blockquote&gt;&lt;p&gt;
9238 arts
9239 dolphin
9240 freespacenotifier
9241 google-gadgets-gst
9242 google-gadgets-xul
9243 kappfinder
9244 kcalc
9245 kcharselect
9246 kde-core
9247 kde-plasma-desktop
9248 kde-standard
9249 kde-window-manager
9250 kdeartwork
9251 kdeartwork-emoticons
9252 kdeartwork-style
9253 kdeartwork-theme-icon
9254 kdebase
9255 kdebase-apps
9256 kdebase-workspace
9257 kdebase-workspace-bin
9258 kdebase-workspace-data
9259 kdeeject
9260 kdelibs
9261 kdeplasma-addons
9262 kdeutils
9263 kdewallpapers
9264 kdf
9265 kfloppy
9266 kgpg
9267 khelpcenter4
9268 kinfocenter
9269 konq-plugins-l10n
9270 konqueror-nsplugins
9271 kscreensaver
9272 kscreensaver-xsavers
9273 ktimer
9274 kwrite
9275 libgle3
9276 libkde4-ruby1.8
9277 libkonq5
9278 libkonq5-templates
9279 libnetpbm10
9280 libplasma-ruby
9281 libplasma-ruby1.8
9282 libqt4-ruby1.8
9283 marble-data
9284 marble-plugins
9285 netpbm
9286 nuvola-icon-theme
9287 plasma-dataengines-workspace
9288 plasma-desktop
9289 plasma-desktopthemes-artwork
9290 plasma-runners-addons
9291 plasma-scriptengine-googlegadgets
9292 plasma-scriptengine-python
9293 plasma-scriptengine-qedje
9294 plasma-scriptengine-ruby
9295 plasma-scriptengine-webkit
9296 plasma-scriptengines
9297 plasma-wallpapers-addons
9298 plasma-widget-folderview
9299 plasma-widget-networkmanagement
9300 ruby
9301 sweeper
9302 update-notifier-kde
9303 xscreensaver-data-extra
9304 xscreensaver-gl
9305 xscreensaver-gl-extra
9306 xscreensaver-screensaver-bsod
9307 &lt;/p&gt;&lt;/blockquote&gt;
9308
9309 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9310
9311 &lt;blockquote&gt;&lt;p&gt;
9312 ark
9313 google-gadgets-common
9314 google-gadgets-qt
9315 htdig
9316 kate
9317 kdebase-bin
9318 kdebase-data
9319 kdepasswd
9320 kfind
9321 klipper
9322 konq-plugins
9323 konqueror
9324 ksysguard
9325 ksysguardd
9326 libarchive1
9327 libcln6
9328 libeet1
9329 libeina-svn-06
9330 libggadget-1.0-0b
9331 libggadget-qt-1.0-0b
9332 libgps19
9333 libkdecorations4
9334 libkephal4
9335 libkonq4
9336 libkonqsidebarplugin4a
9337 libkscreensaver5
9338 libksgrd4
9339 libksignalplotter4
9340 libkunitconversion4
9341 libkwineffects1a
9342 libmarblewidget4
9343 libntrack-qt4-1
9344 libntrack0
9345 libplasma-geolocation-interface4
9346 libplasmaclock4a
9347 libplasmagenericshell4
9348 libprocesscore4a
9349 libprocessui4a
9350 libqalculate5
9351 libqedje0a
9352 libqtruby4shared2
9353 libqzion0a
9354 libruby1.8
9355 libscim8c2a
9356 libsmokekdecore4-3
9357 libsmokekdeui4-3
9358 libsmokekfile3
9359 libsmokekhtml3
9360 libsmokekio3
9361 libsmokeknewstuff2-3
9362 libsmokeknewstuff3-3
9363 libsmokekparts3
9364 libsmokektexteditor3
9365 libsmokekutils3
9366 libsmokenepomuk3
9367 libsmokephonon3
9368 libsmokeplasma3
9369 libsmokeqtcore4-3
9370 libsmokeqtdbus4-3
9371 libsmokeqtgui4-3
9372 libsmokeqtnetwork4-3
9373 libsmokeqtopengl4-3
9374 libsmokeqtscript4-3
9375 libsmokeqtsql4-3
9376 libsmokeqtsvg4-3
9377 libsmokeqttest4-3
9378 libsmokeqtuitools4-3
9379 libsmokeqtwebkit4-3
9380 libsmokeqtxml4-3
9381 libsmokesolid3
9382 libsmokesoprano3
9383 libtaskmanager4a
9384 libtidy-0.99-0
9385 libweather-ion4a
9386 libxklavier16
9387 libxxf86misc1
9388 okteta
9389 oxygencursors
9390 plasma-dataengines-addons
9391 plasma-scriptengine-superkaramba
9392 plasma-widget-lancelot
9393 plasma-widgets-addons
9394 plasma-widgets-workspace
9395 polkit-kde-1
9396 ruby1.8
9397 systemsettings
9398 update-notifier-common
9399 &lt;/p&gt;&lt;/blockquote&gt;
9400
9401 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
9402 aptitude a bit more similar, but there are still quite a lott of
9403 differences. I have no idea what packages should be installed after
9404 the upgrade, but hope those that do can have a look.&lt;/p&gt;
9405 </description>
9406 </item>
9407
9408 <item>
9409 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
9410 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
9411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
9412 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
9413 <description>&lt;p&gt;Most of the computers in use by the
9414 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
9415 are virtual machines. And they have been Xen machines running on a
9416 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
9417 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
9418 bit harder that it could have been, because we set up the Xen virtual
9419 machines to get the virtual partitions from LVM, which as far as I
9420 know is not supported by KVM. So to migrate, we had to convert
9421 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
9422
9423 &lt;p&gt;I found
9424 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
9425 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
9426 migration. It uses qemu-img from the qemu package to make the disk
9427 image, parted to partition it, losetup and kpartx to present the disk
9428 image partions as devices, and dd to copy the data. I NFS mounted the
9429 new servers storage area on the old server to do the migration.&lt;/p&gt;
9430
9431 &lt;pre&gt;
9432 #!/bin/sh
9433
9434 # Based on
9435 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9436
9437 set -e
9438 set -x
9439
9440 if [ -z &quot;$1&quot; ] ; then
9441 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
9442 exit 1
9443 else
9444 host=&quot;$1&quot;
9445 fi
9446
9447 if [ ! -e /dev/vg_data/$host-disk ] ; then
9448 echo &quot;error: unable to find LVM volume for $host&quot;
9449 exit 1
9450 fi
9451
9452 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9453 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9454 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9455 totalsize=$(( ( $disksize + $swapsize ) ))
9456
9457 img=$host.img
9458 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
9459 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9460
9461 parted $img mklabel msdos
9462 parted $img mkpart primary linux-swap 0 $disksize
9463 parted $img mkpart primary ext2 $disksize $totalsize
9464 parted $img set 1 boot on
9465
9466 modprobe dm-mod
9467 losetup /dev/loop0 $img
9468 kpartx -a /dev/loop0
9469
9470 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
9471 fsck.ext3 -f /dev/mapper/loop0p1 || true
9472 mkswap /dev/mapper/loop0p2
9473
9474 kpartx -d /dev/loop0
9475 losetup -d /dev/loop0
9476 &lt;/pre&gt;
9477
9478 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
9479 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
9480
9481 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
9482 the new disk image attached, installed grub-pc and linux-image-686 and
9483 set up grub to boot from the disk image. After this, the KVM machines
9484 seem to work just fine.&lt;/p&gt;
9485 </description>
9486 </item>
9487
9488 <item>
9489 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
9490 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
9491 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
9492 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
9493 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
9494 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9495 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
9496 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
9497
9498 &lt;p&gt;I still do not know what a correct migration should look like, so I
9499 report any differences between apt and aptitude and hope someone else
9500 can see if anything should be changed.&lt;/p&gt;
9501
9502 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9503
9504 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9505
9506 &lt;blockquote&gt;&lt;p&gt;
9507 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9508 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9509 dmz-cursor-theme empathy empathy-common finger
9510 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9511 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9512 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9513 gnome-cards-data gnome-codec-install gnome-core
9514 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9515 gnome-search-tool gnome-session-canberra gnome-spell
9516 gnome-system-log gnome-themes-extras gnome-themes-more
9517 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9518 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9519 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9520 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9521 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9522 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9523 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9524 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9525 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9526 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9527 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9528 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9529 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9530 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9531 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9532 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9533 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9534 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9535 libmono-security2.0-cil libmono-sharpzip2.84-cil
9536 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9537 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9538 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9539 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9540 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9541 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9542 libxalan2-java libxerces2-java media-player-info mesa-utils
9543 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9544 nautilus-sendto-empathy openoffice.org-writer2latex
9545 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9546 python-aptdaemon python-aptdaemon-gtk python-axiom
9547 python-beautifulsoup python-bugbuddy python-clientform
9548 python-coherence python-configobj python-crypto python-cupshelpers
9549 python-cupsutils python-eggtrayicon python-elementtree
9550 python-epsilon python-evolution python-feedparser python-gdata
9551 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9552 python-gtksourceview2 python-httplib2 python-louie python-mako
9553 python-markupsafe python-mechanize python-nevow python-notify
9554 python-opengl python-openssl python-pam python-pkg-resources
9555 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9556 python-tagpy python-twisted-bin python-twisted-conch
9557 python-twisted-core python-twisted-web python-utidylib python-webkit
9558 python-xdg python-zope.interface remmina remmina-plugin-data
9559 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9560 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9561 software-center svgalibg1 system-config-printer-udev
9562 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9563 totem totem-coherence totem-mozilla totem-plugins
9564 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9565 zip
9566 &lt;/p&gt;&lt;/blockquote&gt;
9567
9568 Installed using apt-get, removed with aptitude
9569
9570 &lt;blockquote&gt;&lt;p&gt;
9571 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9572 epiphany-extensions epiphany-gecko evolution-exchange
9573 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9574 gedit-common gnome-app-install gnome-games gnome-games-data
9575 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9576 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9577 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9578 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9579 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9580 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9581 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9582 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9583 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9584 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9585 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9586 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9587 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9588 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9589 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9590 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9591 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9592 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9593 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9594 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9595 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9596 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9597 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9598 sound-juicer swfdec-gnome system-config-printer totem-common
9599 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9600 &lt;/p&gt;&lt;/blockquote&gt;
9601
9602 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9603
9604 &lt;blockquote&gt;&lt;p&gt;
9605 gstreamer0.10-gnomevfs
9606 &lt;/p&gt;&lt;/blockquote&gt;
9607
9608 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9609
9610 &lt;blockquote&gt;&lt;p&gt;
9611 [nothing]
9612 &lt;/p&gt;&lt;/blockquote&gt;
9613
9614 &lt;p&gt;This is for KDE:&lt;/p&gt;
9615
9616 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9617
9618 &lt;blockquote&gt;&lt;p&gt;
9619 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9620 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9621 ghostscript-x git gnome-audio gnugo granatier gs-common
9622 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9623 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9624 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9625 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9626 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9627 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9628 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9629 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9630 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9631 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9632 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9633 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9634 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9635 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9636 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9637 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9638 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9639 libkrossui4 libmailtools-perl libmime-tools-perl
9640 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9641 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9642 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9643 lirc luatex marble networkstatus noatun-plugins
9644 openoffice.org-writer2latex palapeli palapeli-data parley
9645 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9646 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9647 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9648 ttf-sazanami-gothic
9649 &lt;/p&gt;&lt;/blockquote&gt;
9650
9651 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9652
9653 &lt;blockquote&gt;&lt;p&gt;
9654 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9655 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9656 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9657 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9658 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9659 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9660 kitchensync kiten kjumpingcube klatin klettres klickety klines
9661 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9662 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9663 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9664 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9665 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9666 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9667 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9668 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9669 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9670 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9671 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9672 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9673 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9674 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9675 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9676 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9677 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9678 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9679 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9680 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9681 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9682 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9683 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9684 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9685 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9686 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9687 &lt;/p&gt;&lt;/blockquote&gt;
9688
9689 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9690
9691 &lt;blockquote&gt;&lt;p&gt;
9692 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9693 kdeartwork kdebase kdebase-apps kdebase-workspace
9694 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9695 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9696 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9697 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9698 xscreensaver-screensaver-bsod
9699 &lt;/p&gt;&lt;/blockquote&gt;
9700
9701 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9702
9703 &lt;blockquote&gt;&lt;p&gt;
9704 kdebase-bin konq-plugins konqueror
9705 &lt;/p&gt;&lt;/blockquote&gt;
9706 </description>
9707 </item>
9708
9709 <item>
9710 <title>Gnash buildbot slave and Debian kfreebsd</title>
9711 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9713 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9714 <description>&lt;p&gt;Answering
9715 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9716 call from the Gnash project&lt;/a&gt; for
9717 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9718 current source, I have set up a virtual KVM machine on the Debian
9719 Edu/Skolelinux virtualization host to test the git source on
9720 Debian/Squeeze. I hope this can help the developers in getting new
9721 releases out more often.&lt;/p&gt;
9722
9723 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9724 I have considered setting up a &lt;a
9725 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9726 machine as well. I have also considered using the kfreebsd
9727 architecture in Debian as a file server in NUUG to get access to the 5
9728 TB zfs volume we currently use to store DV video. Because of this, I
9729 finally got around to do a test installation of Debian/Squeeze with
9730 kfreebsd. Installation went fairly smooth, thought I noticed some
9731 visual glitches in the cdebconf dialogs (black cursor left on the
9732 screen at random locations). Have not gotten very far with the
9733 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9734 fatal problem. Have to spend some more time on it to see if it is
9735 useful as a file server for NUUG. Will try to find time to set up a
9736 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9737 </description>
9738 </item>
9739
9740 <item>
9741 <title>Debian in 3D</title>
9742 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9744 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9745 <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;
9746
9747 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9748 3D linked in from
9749 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9750 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9751 </description>
9752 </item>
9753
9754 <item>
9755 <title>Software updates 2010-10-24</title>
9756 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9758 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9759 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9760
9761 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9762 raise money for the project is going well. The lower limit of 10
9763 signers was reached in 24 hours, and so far 13 people have signed it.
9764 More signers and more funding is most welcome, and I am really curious
9765 how far we can get before the time limit of December 24 is reached.
9766 :)&lt;/p&gt;
9767
9768 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9769 about what appear to be a great code coverage tool capable of
9770 generating code coverage stats without any changes to the source code.
9771 It is called
9772 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9773 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9774 It is missing in Debian, but the git source built just fine in Squeeze
9775 after I installed libelf-dev, libdwarf-dev, pkg-config and
9776 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9777 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9778
9779 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9780 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9781 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9782 alpha test release of the Squeeze based Debian Edu /
9783 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9784 release. Give it a try if you need a complete linux solution for your
9785 school, including central infrastructure server, workstations, thin
9786 client servers and diskless workstations. A nice touch added
9787 yesterday is RDP support on the thin client servers, for windows
9788 clients to get a Linux desktop on request.&lt;/p&gt;
9789 </description>
9790 </item>
9791
9792 <item>
9793 <title>Some notes on Flash in Debian and Debian Edu</title>
9794 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9795 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9796 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9797 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9798 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9799 second most popular used package that is missing in Debian. The sixth
9800 most popular is flashplayer-mozilla. This is a clear indication that
9801 working flash is important for Debian users. Around 10 percent of the
9802 users submitting data to popcon.debian.org have this package
9803 installed.&lt;/p&gt;
9804
9805 &lt;p&gt;In the report written by Lars Risan in August 2008
9806&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
9807 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9808 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9809 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9810 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9811 web sites require Flash to work, and lacking working Flash support in
9812 the web browser and the problems with installing it was perceived as a
9813 good reason to stay with Windows.&lt;/p&gt;
9814
9815 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9816 said to be the retarded cousin that did not really understand
9817 everything you told him but could work fairly well. This was a
9818 comment regarding the problems Linux have with proprietary formats and
9819 non-standard web pages, and is sad because it exposes a fairly common
9820 understanding of whose fault it is if web pages that only work in for
9821 example Internet Explorer 6 fail to work on Firefox, and funny because
9822 it explain very well how annoying it is for users when Linux
9823 distributions do not work with the documents they receive or the web
9824 pages they want to visit.&lt;/p&gt;
9825
9826 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9827 and Debian Edu to have a well working Flash implementation in the
9828 distribution, to get at least popular sites as Youtube and Google
9829 Video to working out of the box. For Squeeze, Debian have the chance
9830 to include the latest version of Gnash that will make this happen, as
9831 the new release 0.8.8 was published a few weeks ago and is resting in
9832 unstable. The new version work with more sites that version 0.8.7.
9833 The Gnash maintainers have asked for a freeze exception, but the
9834 release team have not had time to reply to it yet. I hope they agree
9835 with me that Flash is important for the Debian desktop users, and thus
9836 accept the new package into Squeeze.&lt;/p&gt;
9837 </description>
9838 </item>
9839
9840 <item>
9841 <title>Circular package dependencies harms apt recovery</title>
9842 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9843 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9844 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9845 <description>&lt;p&gt;I discovered this while doing
9846 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9847 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9848 in Debian still got circular dependencies, and it is often claimed
9849 that apt and aptitude should be able to handle this just fine, but
9850 some times these dependency loops causes apt to fail.&lt;/p&gt;
9851
9852 &lt;p&gt;An example is from todays
9853 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9854 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9855 causes perl-modules to fail to upgrade. The cause is simple. If a
9856 package fail to unpack, then only part of packages with the circular
9857 dependency might end up being unpacked when unpacking aborts, and the
9858 ones already unpacked will fail to configure in the recovery phase
9859 because its dependencies are unavailable.&lt;/p&gt;
9860
9861 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9862
9863 &lt;blockquote&gt;&lt;pre&gt;
9864 dpkg: dependency problems prevent configuration of perl-modules:
9865 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9866 Version of perl on system is 5.10.0-19lenny2.
9867 dpkg: error processing perl-modules (--configure):
9868 dependency problems - leaving unconfigured
9869 &lt;/pre&gt;&lt;/blockquote&gt;
9870
9871 &lt;p&gt;The perl/perl-modules circular dependency is already
9872 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9873 hopefully be solved as soon as possible, but it is not the only one,
9874 and each one of these loops in the dependency tree can cause similar
9875 failures. Of course, they only occur when there are bugs in other
9876 packages causing the unpacking to fail, but it is rather nasty when
9877 the failure of one package causes the problem to become worse because
9878 of dependency loops.&lt;/p&gt;
9879
9880 &lt;p&gt;Thanks to
9881 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9882 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9883 dependencies
9884 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9885 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9886
9887 &lt;p&gt;Todays testing also exposed a bug in
9888 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9889 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9890 apt-get and aptitude, the latter possibly caused by some circular
9891 dependency. Reported both to BTS to try to get someone to look at
9892 it.&lt;/p&gt;
9893 </description>
9894 </item>
9895
9896 <item>
9897 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9898 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9900 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9901 <description>&lt;p&gt;This is a
9902 &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;
9903 on my
9904 &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
9905 work&lt;/a&gt; on
9906 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9907 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9908
9909 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9910 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9911 and dhcp3-server-ldap in Debian use the LDAP server. The two
9912 implementations are quite different in how they use LDAP.&lt;/p&gt;
9913
9914 To get this information, I started slapd with debugging enabled and
9915 dumped the debug output to a file to get the LDAP searches performed
9916 on a Debian Edu main-server. Here is a summary.
9917
9918 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9919
9920 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9921 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9922 the web.
9923
9924 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9925 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9926 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9927 reverse entries are in two different subtrees in LDAP with a structure
9928 based on the DNS names, as in tjener.intern and
9929 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9930
9931 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9932 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9933 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9934 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9935 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9936 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9937 forward entries, it is looking for attributes named dnsttl, arecord,
9938 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9939 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9940 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9941 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9942 spfrecord and modifytimestamp. For reverse entries it is looking for
9943 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9944 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9945 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9946 ldapsearch commands could look like this:&lt;/p&gt;
9947
9948 &lt;blockquote&gt;&lt;pre&gt;
9949 ldapsearch -h ldap \
9950 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9951 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9952 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9953 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9954 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9955 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9956
9957 ldapsearch -h ldap \
9958 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9959 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9960 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9961 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9962 srvrecord naptrrecord modifytimestamp
9963 &lt;/pre&gt;&lt;/blockquote&gt;
9964
9965 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9966 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9967 example LDAP objects used there. In addition to these objects, the
9968 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9969 also exist.&lt;/p&gt;
9970
9971 &lt;blockquote&gt;&lt;pre&gt;
9972 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9973 objectclass: top
9974 objectclass: dnsdomain
9975 objectclass: domainrelatedobject
9976 dc: tjener
9977 arecord: 10.0.2.2
9978 associateddomain: tjener.intern
9979
9980 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9981 objectclass: top
9982 objectclass: dnsdomain2
9983 objectclass: domainrelatedobject
9984 dc: 2
9985 ptrrecord: tjener.intern
9986 associateddomain: 2.2.0.10.in-addr.arpa
9987 &lt;/pre&gt;&lt;/blockquote&gt;
9988
9989 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9990 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9991 same base as in the tree mode for a object with filter
9992 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9993 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9994 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9995 naptrrecord and modifytimestamp. For reverse entires it also do a
9996 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9997 and the requested attributes are associateddomain, dnsttl and
9998 modifytimestamp. In short, in strict mode the objects with ptrrecord
9999 go away, and the arecord attribute in the forward object is used
10000 instead.&lt;/p&gt;
10001
10002 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
10003 like this:&lt;/p&gt;
10004
10005 &lt;blockquote&gt;&lt;pre&gt;
10006 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10007 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10008 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10009 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10010 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10011 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10012
10013 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10014 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
10015 &lt;/pre&gt;&lt;/blockquote&gt;
10016
10017 &lt;p&gt;In addition to the forward and reverse searches , there is also a
10018 search for SOA records, which behave similar to the forward and
10019 reverse lookups.&lt;/p&gt;
10020
10021 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
10022 specify any objectclass names, and instead look for the attributes it
10023 need to generate a DNS reply. This make it able to work with any
10024 objectclass that provide the needed attributes.&lt;/p&gt;
10025
10026 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
10027 dnsdomain2 schemas. The latter is used for reverse entries like
10028 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
10029
10030 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
10031 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
10032 attributes) and domainrelatedobject (for associatedDomain). The use
10033 of structural object classes make it impossible to combine these
10034 classes with the object classes used by DHCP.&lt;/p&gt;
10035
10036 &lt;p&gt;There are other schemas that could be used too, for example the
10037 dnszone structural object class used by Gosa and bind-sdb for the DNS
10038 attributes combined with the domainrelatedobject object class, but in
10039 this case some unused attributes would have to be included as well
10040 (zonename and relativedomainname).&lt;/p&gt;
10041
10042 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
10043 mode and not use any of the existing objectclasses (dnsdomain,
10044 dnsdomain2 and dnszone) when one want to combine the DNS information
10045 with DHCP information, and instead create a auxiliary object class
10046 defined something like this (using the attributes defined for
10047 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
10048
10049 &lt;blockquote&gt;&lt;pre&gt;
10050 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
10051 SUP top
10052 AUXILIARY
10053 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
10054 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
10055 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
10056 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
10057 A6Record $ DNAMERecord
10058 ))
10059 &lt;/pre&gt;&lt;/blockquote&gt;
10060
10061 &lt;p&gt;This will allow any object to become a DNS entry when combined with
10062 the domainrelatedobject object class, and allow any entity to include
10063 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
10064 developers asking for their view on this schema and if they are
10065 interested in providing such schema with PowerDNS, and I hope my
10066 message will be accepted into their mailing list soon.&lt;/p&gt;
10067
10068 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
10069
10070 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
10071 the object attributes, and then uses the attributes it want. This
10072 make it harder to figure out exactly what attributes are used, but
10073 thanks to the working example in Debian Edu I can at least get an idea
10074 what is needed without having to read the source code.&lt;/p&gt;
10075
10076 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
10077 search filter to use to locate the correct dhcpServer entity is
10078 stored. These are the relevant entries from
10079 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
10080
10081 &lt;blockquote&gt;&lt;pre&gt;
10082 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
10083 ldap-dhcp-server-cn &quot;dhcp&quot;;
10084 &lt;/pre&gt;&lt;/blockquote&gt;
10085
10086 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
10087 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
10088 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
10089 search result is this entry:&lt;/p&gt;
10090
10091 &lt;blockquote&gt;&lt;pre&gt;
10092 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10093 cn: dhcp
10094 objectClass: top
10095 objectClass: dhcpServer
10096 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10097 &lt;/pre&gt;&lt;/blockquote&gt;
10098
10099 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
10100 subtree with DHCP configuration. The DHCP configuration subtree base
10101 is located using a base scope search with base &quot;cn=DHCP
10102 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
10103 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
10104 The search result is this entry:&lt;/p&gt;
10105
10106 &lt;blockquote&gt;&lt;pre&gt;
10107 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10108 cn: DHCP Config
10109 objectClass: top
10110 objectClass: dhcpService
10111 objectClass: dhcpOptions
10112 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
10113 dhcpStatements: ddns-update-style none
10114 dhcpStatements: authoritative
10115 dhcpOption: smtp-server code 69 = array of ip-address
10116 dhcpOption: www-server code 72 = array of ip-address
10117 dhcpOption: wpad-url code 252 = text
10118 &lt;/pre&gt;&lt;/blockquote&gt;
10119
10120 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
10121 all the DHCP configuration is loaded, it is ready to receive requests.
10122 The subtree in Debian Edu contain objects with object classes
10123 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
10124 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
10125 and information about netmasks, dynamic range etc. Leaving out the
10126 details here because it is not relevant for the focus of my
10127 investigation, which is to see if it is possible to merge dns and dhcp
10128 related computer objects.&lt;/p&gt;
10129
10130 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
10131 of the client (00:00:00:00:00:00 in this example), using a subtree
10132 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
10133 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
10134 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
10135 like:&lt;/p&gt;
10136
10137 &lt;blockquote&gt;&lt;pre&gt;
10138 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10139 cn: hostname
10140 objectClass: top
10141 objectClass: dhcpHost
10142 dhcpHWAddress: ethernet 00:00:00:00:00:00
10143 dhcpStatements: fixed-address hostname
10144 &lt;/pre&gt;&lt;/blockquote&gt;
10145
10146 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
10147 The object classes need to have fixed names, and the configuration
10148 need to be stored in a fairly specific LDAP structure. On the
10149 positive side, the invidiual dhcpHost entires can be anywhere without
10150 the DN pointed to by the dhcpServer entries. The latter should make
10151 it possible to group all host entries in a subtree next to the
10152 configuration entries, and this subtree can also be shared with the
10153 DNS server if the schema proposed above is combined with the dhcpHost
10154 structural object class.
10155
10156 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
10157
10158 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
10159 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
10160 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
10161 allowing DNS objects to be stored anywhere under the base cn specified
10162 in the configuration.&lt;/p&gt;
10163
10164 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
10165 regarding which LDAP schemas to use and which LDAP structure to use.
10166 I guess one could implement ones own schema, as long as the
10167 objectclasses and attributes have the names used, but this do not
10168 really help when the DHCP subtree need to have a fairly fixed
10169 structure.&lt;/p&gt;
10170
10171 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
10172 this might work for Debian Edu:&lt;/p&gt;
10173
10174 &lt;blockquote&gt;&lt;pre&gt;
10175 ou=services
10176 cn=machine-info (dhcpService) - dhcpServiceDN points here
10177 cn=dhcp (dhcpServer)
10178 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10179 cn=10.0.2.0 (dhcpSubnet)
10180 cn=group1 (dhcpGroup/dhcpOptions)
10181 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10182 cn=192.168.0.0 (dhcpSubnet)
10183 cn=group1 (dhcpGroup/dhcpOptions)
10184 ou=machines - PowerDNS base points here
10185 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10186 &lt;/pre&gt;&lt;/blockquote&gt;
10187
10188 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
10189 entries to be in the dhcpGroup subtrees, the entries can be stored
10190 there instead of a common machines subtree, and the PowerDNS base
10191 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
10192
10193 &lt;p&gt;The combined object under the machines subtree would look something
10194 like this:&lt;/p&gt;
10195
10196 &lt;blockquote&gt;&lt;pre&gt;
10197 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10198 dc: hostname
10199 objectClass: top
10200 objectClass: dhcpHost
10201 objectclass: domainrelatedobject
10202 objectclass: dnsDomainAux
10203 associateddomain: hostname.intern
10204 arecord: 10.11.12.13
10205 dhcpHWAddress: ethernet 00:00:00:00:00:00
10206 dhcpStatements: fixed-address hostname.intern
10207 &lt;/pre&gt;&lt;/blockquote&gt;
10208
10209 &lt;/p&gt;One could even add the LTSP configuration associated with a given
10210 machine, as long as the required attributes are available in a
10211 auxiliary object class.&lt;/p&gt;
10212 </description>
10213 </item>
10214
10215 <item>
10216 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
10217 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
10218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
10219 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
10220 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
10221 DHCP services in Debian Edu to use the same LDAP objects for a given
10222 computer, to avoid the possibility of having a inconsistent state for
10223 a computer in LDAP (as in DHCP but no DNS entry or the other way
10224 around) and make it easier to add computers to LDAP.&lt;/p&gt;
10225
10226 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
10227 information finally found a solution that seem to work.&lt;/p&gt;
10228
10229 &lt;p&gt;The old setup required three LDAP objects for a given computer.
10230 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10231 we switch powerdns to use its strict LDAP method (ldap-method=strict
10232 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10233 merged into one while making it impossible to transfer the reverse map
10234 to a slave DNS server.&lt;/p&gt;
10235
10236 &lt;p&gt;If we also replace the object class used to get the DNS related
10237 attributes to one allowing these attributes to be combined with the
10238 dhcphost object class, we can merge the DNS and DHCP entries into one.
10239 I&#39;ve written such object class in the dnsdomainaux.schema file (need
10240 proper OIDs, but that is a minor issue), and tested the setup. It
10241 seem to work.&lt;/p&gt;
10242
10243 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
10244 for both DNS and DHCP, and even the LTSP configuration I suggested in
10245 an earlier email. The combined LDAP object will look something like
10246 this:&lt;/p&gt;
10247
10248 &lt;blockquote&gt;&lt;pre&gt;
10249 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10250 cn: hostname
10251 objectClass: dhcphost
10252 objectclass: domainrelatedobject
10253 objectclass: dnsdomainaux
10254 associateddomain: hostname.intern
10255 arecord: 10.11.12.13
10256 dhcphwaddress: ethernet 00:00:00:00:00:00
10257 dhcpstatements: fixed-address hostname
10258 ldapconfigsound: Y
10259 &lt;/pre&gt;&lt;/blockquote&gt;
10260
10261 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
10262 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10263 before asking DNS to resolve the fixed-adddress. LTSP will use
10264 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
10265
10266 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
10267 dhcphost in a different location, to allow us to put the objects
10268 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
10269 that. If I can&#39;t figure out a way to do that, we can still get rid of
10270 the hosts subtree and move all its content into the DHCP Config tree
10271 (which probably should be renamed to be more related to the new
10272 content. I suspect cn=dnsdhcp,ou=services or something like that
10273 might be a good place to put it.&lt;/p&gt;
10274
10275 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10276 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10277 </description>
10278 </item>
10279
10280 <item>
10281 <title>Idea for storing LTSP configuration in LDAP</title>
10282 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
10283 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
10284 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
10285 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
10286 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10287 clients, and that this can be used to fetch configuration from LDAP if
10288 Debian Edu choose to store configuration there.&lt;/p&gt;
10289
10290 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
10291 to get configuration from LDAP. The idea is to look up the MAC
10292 address of the client in LDAP, and look for attributes on the form
10293 ltspconfigsetting=value, and use this to export SETTING=value to the
10294 LTSP clients.&lt;/p&gt;
10295
10296 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
10297 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
10298 allowing us to store all information about a computer in one place.&lt;/p&gt;
10299
10300 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
10301 this approach. A real LDAP schema for the ltspClientAux objectclass
10302 need to be written. Comments, suggestions, etc?&lt;/p&gt;
10303
10304 &lt;blockquote&gt;&lt;pre&gt;
10305 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10306 #
10307 # Fetch LTSP client settings from LDAP based on MAC address
10308 #
10309 # Uses ethernet address as stored in the dhcpHost objectclass using
10310 # the dhcpHWAddress attribute or ethernet address stored in the
10311 # ieee802Device objectclass with the macAddress attribute.
10312 #
10313 # This module is written to be schema agnostic, and only depend on the
10314 # existence of attribute names.
10315 #
10316 # The LTSP configuration variables are saved directly using a
10317 # ltspConfig prefix and uppercasing the rest of the attribute name.
10318 # To set the SERVER variable, set the ltspConfigServer attribute.
10319 #
10320 # Some LDAP schema should be created with all the relevant
10321 # configuration settings. Something like this should work:
10322 #
10323 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
10324 # SUP top
10325 # AUXILIARY
10326 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10327
10328 LDAPSERVER=$(debian-edu-ldapserver)
10329 if [ &quot;$LDAPSERVER&quot; ] ; then
10330 LDAPBASE=$(debian-edu-ldapserver -b)
10331 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
10332 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
10333 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
10334 grep &#39;^ltspConfig&#39; | while read attr value ; do
10335 # Remove prefix and convert to upper case
10336 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
10337 # bass value on to clients
10338 eval &quot;$attr=$value; export $attr&quot;
10339 done
10340 done
10341 fi
10342 &lt;/pre&gt;&lt;/blockquote&gt;
10343
10344 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
10345 the while block might end up in a subshell causing the variables set
10346 there to not show up in ltsp-config, but if that is the case I am sure
10347 the code can be restructured to make sure the variables are passed on.
10348 I expect that can be solved with some testing. :)&lt;/p&gt;
10349
10350 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10351 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10352
10353 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
10354 configuration in LDAP that was created around year 2000 by
10355 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
10356 Xperience, Inc., 2000&lt;/a&gt;. I found its
10357 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
10358 personal home page over at redhat.com.&lt;/p&gt;
10359 </description>
10360 </item>
10361
10362 <item>
10363 <title>jXplorer, a very nice LDAP GUI</title>
10364 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
10365 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
10366 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
10367 <description>&lt;p&gt;Since
10368 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
10369 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
10370 LDAP GUI that is even better than luma. The java application
10371 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
10372 moving LDAP objects and subtrees using drag-and-drop, and can
10373 authenticate using Kerberos. I have only tested the Kerberos
10374 authentication, but do not have a LDAP setup allowing me to rewrite
10375 LDAP with my test user yet. It is
10376 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
10377 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
10378 have with it is how it handle errors. If something go wrong, its
10379 non-intuitive behaviour require me to go through some query work list
10380 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
10381 </description>
10382 </item>
10383
10384 <item>
10385 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
10386 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
10387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
10388 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
10389 <description>&lt;p&gt;Here is a short update on my &lt;a
10390 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
10391 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
10392 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
10393 not reporting the status for KDE, because the upgrade crashes when
10394 aptitude try because of missing conflicts
10395 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
10396 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
10397
10398 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
10399 complete list of the installed packages. Based on this I see these
10400 differences when I did a test run today. As usual, I do not really
10401 know what the correct set of packages would be, but thought it best to
10402 publish the difference.&lt;/p&gt;
10403
10404 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10405
10406 &lt;blockquote&gt;&lt;p&gt;
10407 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
10408 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
10409 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10410 libgtksourceview-common libpt-1.10.10-plugins-alsa
10411 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10412 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10413 python-4suite-xml python-eggtrayicon python-gtkhtml2
10414 python-gtkmozembed svgalibg1 xserver-xephyr zip
10415 &lt;/p&gt;&lt;/blockquote&gt;
10416
10417 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10418
10419 &lt;blockquote&gt;&lt;p&gt;
10420 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10421 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10422 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
10423 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
10424 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
10425 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
10426 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10427 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10428 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10429 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
10430 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
10431 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
10432 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10433 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
10434 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10435 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
10436 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
10437 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10438 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10439 mysql-common swfdec-gnome totem-gstreamer wodim
10440 &lt;/p&gt;&lt;/blockquote&gt;
10441
10442 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10443
10444 &lt;blockquote&gt;&lt;p&gt;
10445 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10446 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10447 xserver-xorg-input-all xserver-xorg-input-evdev
10448 xserver-xorg-input-kbd xserver-xorg-input-mouse
10449 xserver-xorg-input-synaptics xserver-xorg-video-all
10450 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10451 xserver-xorg-video-chips xserver-xorg-video-cirrus
10452 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10453 xserver-xorg-video-glint xserver-xorg-video-i128
10454 xserver-xorg-video-i740 xserver-xorg-video-mach64
10455 xserver-xorg-video-mga xserver-xorg-video-neomagic
10456 xserver-xorg-video-nouveau xserver-xorg-video-nv
10457 xserver-xorg-video-r128 xserver-xorg-video-radeon
10458 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10459 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10460 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10461 xserver-xorg-video-sis xserver-xorg-video-sisusb
10462 xserver-xorg-video-tdfx xserver-xorg-video-tga
10463 xserver-xorg-video-trident xserver-xorg-video-tseng
10464 xserver-xorg-video-vesa xserver-xorg-video-vmware
10465 xserver-xorg-video-voodoo
10466 &lt;/p&gt;&lt;/blockquote&gt;
10467
10468 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10469
10470 &lt;blockquote&gt;&lt;p&gt;
10471 deskbar-applet xserver-xorg xserver-xorg-core
10472 xserver-xorg-input-wacom xserver-xorg-video-intel
10473 xserver-xorg-video-openchrome
10474 &lt;/p&gt;&lt;/blockquote&gt;
10475
10476 &lt;p&gt;I was told on IRC that the xorg-xserver package was
10477 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
10478 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
10479 No idea when it hits Squeeze, but when it does I hope it will reduce
10480 the difference somewhat.
10481 </description>
10482 </item>
10483
10484 <item>
10485 <title>LUMA, a very nice LDAP GUI</title>
10486 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
10487 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
10488 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
10489 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
10490 directory in Debian Edu, and in the process I started to miss a GUI
10491 tool to browse the LDAP tree. The only one I was able to find in
10492 Debian/Squeeze and Lenny is
10493 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
10494 be a great tool to get a overview of the current LDAP directory
10495 populated by default in Skolelinux. Thanks to it, I have been able to
10496 find empty and obsolete subtrees, misplaced objects and duplicate
10497 objects. It will be installed by default in Debian/Squeeze. If you
10498 are working with LDAP, give it a go. :)&lt;/p&gt;
10499
10500 &lt;p&gt;I did notice one problem with it I have not had time to report to
10501 the BTS yet. There is no .desktop file in the package, so the tool do
10502 not show up in the Gnome and KDE menus, but only deep down in in the
10503 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10504 released.&lt;/p&gt;
10505
10506 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10507 like to move objects and remove subtrees directly in the GUI, but have
10508 not found a way to do that with LUMA yet. So in the mean time, I use
10509 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10510
10511 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10512 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10513
10514 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10515 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10516 useful GUI alternative. It seem like a good tool, but is unmaintained
10517 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10518 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10519 </description>
10520 </item>
10521
10522 <item>
10523 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10524 <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>
10525 <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>
10526 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10527 <description>&lt;p&gt;A while back, I
10528 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10529 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10530 for storing DNS and DHCP information in LDAP to combine the two sets
10531 of information into one LDAP object representing a computer.&lt;/p&gt;
10532
10533 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10534 the dhcpHost object class auxiliary, to allow it to be combined with
10535 the dNSDomain object class, and thus forming one object for one
10536 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10537
10538 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10539 without also changing the assigned number for the object class, and I
10540 do not know enough about LDAP schema design to do that properly for
10541 Debian Edu.&lt;/p&gt;
10542
10543 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10544 the
10545 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10546 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10547 available today from IETF.&lt;/p&gt;
10548
10549 &lt;pre&gt;
10550 --- dhcp.schema (revision 65192)
10551 +++ dhcp.schema (working copy)
10552 @@ -376,7 +376,7 @@
10553 objectclass ( 2.16.840.1.113719.1.203.6.6
10554 NAME &#39;dhcpHost&#39;
10555 DESC &#39;This represents information about a particular client&#39;
10556 - SUP top
10557 + SUP top AUXILIARY
10558 MUST cn
10559 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10560 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10561 &lt;/pre&gt;
10562
10563 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10564 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10565 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10566
10567 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10568 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10569 </description>
10570 </item>
10571
10572 <item>
10573 <title>Calling tasksel like the installer, while still getting useful output</title>
10574 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10575 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10576 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10577 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10578 installs packages during the normal debian-installer run. Until now,
10579 I have ended up letting tasksel do the work, with the annoying problem
10580 of not getting any feedback at all when something fails (like a
10581 conffile question from dpkg or a download that fails), using code like
10582 this:
10583
10584 &lt;blockquote&gt;&lt;pre&gt;
10585 export DEBIAN_FRONTEND=noninteractive
10586 tasksel --new-install
10587 &lt;/pre&gt;&lt;/blockquote&gt;
10588
10589 This would invoke tasksel, let its automatic task selection pick the
10590 tasks to install, and continue to install the requested tasks without
10591 any output what so ever.
10592
10593 Recently I revisited this problem while working on the automatic
10594 package upgrade testing, because tasksel would some times hang without
10595 any useful feedback, and I want to see what is going on when it
10596 happen. Then it occured to me, I can parse the output from tasksel
10597 when asked to run in test mode, and use that aptitude command line
10598 printed by tasksel then to simulate the tasksel run. I ended up using
10599 code like this:
10600
10601 &lt;blockquote&gt;&lt;pre&gt;
10602 export DEBIAN_FRONTEND=noninteractive
10603 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10604 $cmd
10605 &lt;/pre&gt;&lt;/blockquote&gt;
10606
10607 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10608 --without-recommends -o APT::Install-Recommends=no -y install
10609 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10610 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10611 laptop task and all packages with priority standard , required and
10612 important, just like tasksel would have done it during
10613 installation.&lt;/p&gt;
10614
10615 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10616 install packages without using debconf-apt-progress, for use cases
10617 like this.&lt;/p&gt;
10618 </description>
10619 </item>
10620
10621 <item>
10622 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10623 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10624 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10625 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10626 <description>&lt;p&gt;My
10627 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10628 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10629 finally made the upgrade logs available from
10630 &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;.
10631 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10632 apt and aptitude, and found their differences interesting. This time
10633 I will only focus on their removal plans.&lt;/p&gt;
10634
10635 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10636 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10637 surprising part is that it want to remove xorg and all
10638 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10639 sure why. When asking aptitude to do the same, it want to remove 129
10640 packages, but most of them are library packages I suspect are no
10641 longer needed. Both of them want to remove bluetooth packages, which
10642 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10643
10644 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10645 which seem like a bad idea and xorg the same way as with Gnome. Asking
10646 aptitude for the same, it wants to remove 192 packages, none which are
10647 too surprising.&lt;/p&gt;
10648
10649 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10650 and avoided, and perhaps others as well. Here are the complete list
10651 of planned removals. The complete logs is available from the URL
10652 above. Note if you want to repeat these tests, that the upgrade test
10653 for kde+apt-get hung in the tasksel setup because of dpkg asking
10654 conffile questions. No idea why. I worked around it by using
10655 &#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
10656 continue.&lt;/p&gt;
10657
10658 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10659 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10660 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10661 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10662 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10663 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10664 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10665 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10666 xserver-xorg-input-kbd xserver-xorg-input-mouse
10667 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10668 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10669 xserver-xorg-video-ati xserver-xorg-video-chips
10670 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10671 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10672 xserver-xorg-video-glint xserver-xorg-video-i128
10673 xserver-xorg-video-i740 xserver-xorg-video-imstt
10674 xserver-xorg-video-intel xserver-xorg-video-mach64
10675 xserver-xorg-video-mga xserver-xorg-video-neomagic
10676 xserver-xorg-video-nsc xserver-xorg-video-nv
10677 xserver-xorg-video-openchrome xserver-xorg-video-r128
10678 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10679 xserver-xorg-video-rendition xserver-xorg-video-s3
10680 xserver-xorg-video-s3virge xserver-xorg-video-savage
10681 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10682 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10683 xserver-xorg-video-tga xserver-xorg-video-trident
10684 xserver-xorg-video-tseng xserver-xorg-video-v4l
10685 xserver-xorg-video-vesa xserver-xorg-video-vga
10686 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10687 xulrunner-1.9-gnome-support&lt;/p&gt;
10688
10689 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10690
10691 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10692 djvulibre-desktop finger gnome-app-install gnome-mount
10693 gnome-network-admin gnome-spell gnome-vfs-obexftp
10694 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10695 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10696 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10697 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10698 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10699 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10700 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10701 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10702 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10703 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10704 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10705 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10706 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10707 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10708 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10709 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10710 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10711 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10712 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10713 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10714 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10715 openoffice.org-writer2latex openssl-blacklist p7zip
10716 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10717 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10718 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10719 swfdec-mozilla totem-gstreamer update-manager wodim
10720 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10721 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10722 zip&lt;/p&gt;
10723
10724 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10725
10726 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10727 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10728 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10729 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10730 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10731 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10732 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10733 xserver-xorg-input-kbd xserver-xorg-input-mouse
10734 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10735 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10736 xserver-xorg-video-ati xserver-xorg-video-chips
10737 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10738 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10739 xserver-xorg-video-glint xserver-xorg-video-i128
10740 xserver-xorg-video-i740 xserver-xorg-video-imstt
10741 xserver-xorg-video-intel xserver-xorg-video-mach64
10742 xserver-xorg-video-mga xserver-xorg-video-neomagic
10743 xserver-xorg-video-nsc xserver-xorg-video-nv
10744 xserver-xorg-video-openchrome xserver-xorg-video-r128
10745 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10746 xserver-xorg-video-rendition xserver-xorg-video-s3
10747 xserver-xorg-video-s3virge xserver-xorg-video-savage
10748 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10749 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10750 xserver-xorg-video-tga xserver-xorg-video-trident
10751 xserver-xorg-video-tseng xserver-xorg-video-v4l
10752 xserver-xorg-video-vesa xserver-xorg-video-vga
10753 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10754
10755 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10756 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10757 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10758 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10759 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10760 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10761 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10762 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10763 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10764 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10765 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10766 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10767 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10768 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10769 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10770 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10771 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10772 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10773 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10774 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10775 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10776 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10777 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10778 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10779 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10780 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10781 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10782 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10783 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10784 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10785 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10786 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10787 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10788 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10789 texlive-common texlive-doc-base texlive-fonts-recommended
10790 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10791 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10792 xulrunner-1.9&lt;/p&gt;
10793
10794 </description>
10795 </item>
10796
10797 <item>
10798 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10799 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10801 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10802 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10803 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10804 have been discovered and reported in the process
10805 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10806 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10807 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10808 kdebase-workspace-data), and to get a more regular testing going on, I
10809 am working on a script to automate the test.&lt;/p&gt;
10810
10811 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10812 Gnome or KDE desktop installation inside the chroot before upgrading
10813 it. To ensure no services are started in the chroot, a policy-rc.d
10814 script is inserted. To make sure tasksel believe it is to install a
10815 desktop on a laptop, the tasksel tests are replaced in the chroot
10816 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10817
10818 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10819 currently always fail because udev refuses to upgrade with the kernel
10820 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10821 is created. The bug report
10822 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10823 this problem do not trigger in a chroot, but I touch the file anyway
10824 to make sure the upgrade go well. Testing on virtual and real
10825 hardware have failed me because of udev so far, and creating this file
10826 do the trick in such settings anyway. This is a
10827 &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
10828 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10829 maintainer because he lack the resources to rewrite udev to keep
10830 working with old kernels or something like that. I really wish the
10831 udev upstream would keep udev backwards compatible, to avoid such
10832 upgrade problem, but given that they fail to do so, I guess
10833 documenting the way out of this mess is the best option we got for
10834 Debian Squeeze.&lt;/p&gt;
10835
10836 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10837 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10838 trick:&lt;/p&gt;
10839
10840 &lt;blockquote&gt;&lt;pre&gt;
10841 #!/bin/sh
10842 set -ex
10843
10844 if [ &quot;$1&quot; ] ; then
10845 desktop=$1
10846 else
10847 desktop=gnome
10848 fi
10849
10850 from=lenny
10851 to=squeeze
10852
10853 exec &amp;lt; /dev/null
10854 unset LANG
10855 mirror=http://ftp.skolelinux.org/debian
10856 tmpdir=chroot-$from-upgrade-$to-$desktop
10857 fuser -mv .
10858 debootstrap $from $tmpdir $mirror
10859 chroot $tmpdir aptitude update
10860 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10861 #!/bin/sh
10862 exit 101
10863 EOF
10864 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10865 exit_cleanup() {
10866 umount $tmpdir/proc
10867 }
10868 mount -t proc proc $tmpdir/proc
10869 # Make sure proc is unmounted also on failure
10870 trap exit_cleanup EXIT INT
10871
10872 chroot $tmpdir aptitude -y install debconf-utils
10873
10874 # Make sure tasksel autoselection trigger. It need the test scripts
10875 # to return the correct answers.
10876 echo tasksel tasksel/desktop multiselect $desktop | \
10877 chroot $tmpdir debconf-set-selections
10878
10879 # Include the desktop and laptop task
10880 for test in desktop laptop ; do
10881 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10882 #!/bin/sh
10883 exit 2
10884 EOF
10885 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10886 done
10887
10888 DEBIAN_FRONTEND=noninteractive
10889 DEBIAN_PRIORITY=critical
10890 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10891 chroot $tmpdir tasksel --new-install
10892
10893 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10894 chroot $tmpdir aptitude update
10895 touch $tmpdir/etc/udev/kernel-upgrade
10896 chroot $tmpdir aptitude -y dist-upgrade
10897 fuser -mv
10898 &lt;/pre&gt;&lt;/blockquote&gt;
10899
10900 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10901 with aptitude, but I have not had time to look at how they behave
10902 differently so far. I hope to get a cron job running to do the test
10903 regularly and post the result on the web. The Gnome upgrade currently
10904 work, while the KDE upgrade fail because of the bug in
10905 kdebase-workspace-data&lt;/p&gt;
10906
10907 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10908 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10909 post, so I will refrain from trying. I can report that for Gnome,
10910 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10911 remove and 1 not upgraded and 1024MB need to be downloaded while for
10912 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10913 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10914
10915 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10916 is able to migrate to dependency based boot sequencing and parallel
10917 booting without a hitch. Was unsure if there were still bugs with
10918 packages failing to clean up their obsolete init.d script during
10919 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10920 packages.&lt;/p&gt;
10921 </description>
10922 </item>
10923
10924 <item>
10925 <title>Upstart or sysvinit - as init.d scripts see it</title>
10926 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10928 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10929 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10930 scripts to migrate (some of) their operations to upstart job while
10931 keeping the init.d for hurd and kfreebsd. The packages with such
10932 needs will need a way to get their init.d scripts to behave
10933 differently when used with sysvinit and with upstart. Because of
10934 this, I had a look at the environment variables set when a init.d
10935 script is running under upstart, and when it is not.&lt;/p&gt;
10936
10937 &lt;p&gt;With upstart, I notice these environment variables are set when a
10938 script is started from rcS.d/ (ignoring some irrelevant ones like
10939 COLUMNS):&lt;/p&gt;
10940
10941 &lt;blockquote&gt;&lt;pre&gt;
10942 DEFAULT_RUNLEVEL=2
10943 previous=N
10944 PREVLEVEL=
10945 RUNLEVEL=
10946 runlevel=S
10947 UPSTART_EVENTS=startup
10948 UPSTART_INSTANCE=
10949 UPSTART_JOB=rc-sysinit
10950 &lt;/pre&gt;&lt;/blockquote&gt;
10951
10952 &lt;p&gt;With sysvinit, these environment variables are set for the same
10953 script.&lt;/p&gt;
10954
10955 &lt;blockquote&gt;&lt;pre&gt;
10956 INIT_VERSION=sysvinit-2.88
10957 previous=N
10958 PREVLEVEL=N
10959 RUNLEVEL=S
10960 runlevel=S
10961 &lt;/pre&gt;&lt;/blockquote&gt;
10962
10963 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10964 sysvinit are not set by upstart. Not sure if it is intentional or not
10965 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10966
10967 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10968 looking for the UPSTART_JOB environment variable seem to be a good
10969 choice.&lt;/p&gt;
10970 </description>
10971 </item>
10972
10973 <item>
10974 <title>A manual for standards wars...</title>
10975 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10976 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10977 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10978 <description>&lt;p&gt;Via the
10979 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10980 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10981 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10982 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10983 following the standards wars of today.&lt;/p&gt;
10984 </description>
10985 </item>
10986
10987 <item>
10988 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10989 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10991 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10992 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10993 to get a list of the machine types in use thanks to the DMI
10994 information extracted from each machine. The script to do so is
10995 included in the sitesummary package, and here is example output from
10996 the Skolelinux build servers:&lt;/p&gt;
10997
10998 &lt;blockquote&gt;&lt;pre&gt;
10999 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11000 vendor count
11001 Dell Computer Corporation 1
11002 PowerEdge 1750 1
11003 IBM 1
11004 eserver xSeries 345 -[8670M1X]- 1
11005 Intel 2
11006 [no-dmi-info] 3
11007 maintainer:~#
11008 &lt;/pre&gt;&lt;/blockquote&gt;
11009
11010 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
11011 provided in each machine. Here there are Intel machines without model
11012 information listed with Intel as vendor and no model, and virtual Xen
11013 machines listed as [no-dmi-info]. One can add -l as a command line
11014 option to list the individual machines.&lt;/p&gt;
11015
11016 &lt;p&gt;A larger list is
11017 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
11018 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
11019 provide the basic sitesummary report publicly. In their report there
11020 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
11021 their machines, and as sitesummary is available in both distributions,
11022 it is trivial to get all of them to report to the same central
11023 collector.&lt;/p&gt;
11024 </description>
11025 </item>
11026
11027 <item>
11028 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
11029 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
11030 <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>
11031 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
11032 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
11033 start at boot when an NVidia video card is used is handled. The
11034 problem seem to be that the nvidia X.org driver uses a long time to
11035 initialize, and this duration is longer than kdm is configured to
11036 wait.&lt;/p&gt;
11037
11038 &lt;p&gt;I came across two bugs related to this issue,
11039 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
11040 against initscripts and passed on to nvidia-glx when it became obvious
11041 that the nvidia drivers were involved, and
11042 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
11043 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
11044
11045 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
11046 problem nvidia video card owners experience and make sure the Debian
11047 distribution work out of the box for these users. The nvidia driver
11048 maintainers expect kdm to be set up to wait longer, while kdm expect
11049 the nvidia driver maintainers to fix the driver to start faster, and
11050 while they wait for each other I guess the users end up switching to a
11051 distribution that work for them. I have no idea what the solution is,
11052 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
11053
11054 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
11055 </description>
11056 </item>
11057
11058 <item>
11059 <title>Parallellized boot seem to hold up well in Debian/testing</title>
11060 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
11061 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
11062 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
11063 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
11064 The feature seem to hold up pretty well, but three fairly serious
11065 issues are known and should be solved:
11066
11067 &lt;p&gt;&lt;ul&gt;
11068
11069 &lt;li&gt;The wicd package seen to
11070 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
11071 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
11072 parallel booting is enabled. No idea why, but the wicd maintainer
11073 seem to be on the case.&lt;/li&gt;
11074
11075 &lt;li&gt;The nvidia X driver seem to
11076 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
11077 triggered more easily when parallel booting is in effect. The
11078 maintainer is on the case.&lt;/li&gt;
11079
11080 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
11081 sequencing (the shutdown is broken) when old file-rc users
11082 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
11083 sysv-rc. One way to solve it would be for file-rc to create
11084 /etc/init.d/.legacy-bootordering, and another is to try to make
11085 sysv-rc more robust. Will investigate some more and probably upload a
11086 workaround in sysv-rc to help those trying to move from file-rc to
11087 sysv-rc get a working shutdown.&lt;/li&gt;
11088
11089 &lt;/ul&gt;&lt;/p&gt;
11090
11091 &lt;p&gt;All in all not many surprising issues, and all of them seem
11092 solvable before Squeeze is released. In addition to these there are
11093 some packages with bugs in their dependencies and run level settings,
11094 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
11095
11096 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11097 the BTS, please usertag the report to get it to show up at
11098 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11099 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11100
11101 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
11102 </description>
11103 </item>
11104
11105 <item>
11106 <title>More flexible firmware handling in debian-installer</title>
11107 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
11108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
11109 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
11110 <description>&lt;p&gt;After a long break from debian-installer development, I finally
11111 found time today to return to the project. Having to spend less time
11112 working dependency based boot in debian, as it is almost complete now,
11113 definitely helped freeing some time.&lt;/p&gt;
11114
11115 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
11116 include some firmware packages on the Debian Edu CDs, those needed to
11117 get disk and network controllers working. Without having these
11118 firmware packages available during installation, it is impossible to
11119 install Debian Edu on the given machine, and because our target group
11120 are non-technical people, asking them to provide firmware packages on
11121 an external medium is a support pain. Initially, I expected it to be
11122 enough to include the firmware packages on the CD to get
11123 debian-installer to find and use them. This proved to be wrong.
11124 Next, I hoped it was enough to symlink the relevant firmware packages
11125 to some useful location on the CD (tried /cdrom/ and
11126 /cdrom/firmware/). This also proved to not work, and at this point I
11127 found time to look at the debian-installer code to figure out what was
11128 going to work.&lt;/p&gt;
11129
11130 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
11131 look revealed that it would only look for firmware packages outside
11132 the installation media, so the CD was never checked for firmware
11133 packages. It would only check USB sticks, floppies and other
11134 &quot;external&quot; media devices. Today I changed it to also look in the
11135 /cdrom/firmware/ directory on the mounted CD or DVD, which should
11136 solve the problem I ran into with Debian edu. I also changed it to
11137 look in /firmware/, to make sure the installer also find firmware
11138 provided in the initrd when booting the installer via PXE, to allow us
11139 to provide the same feature in the PXE setup included in Debian
11140 Edu.&lt;/p&gt;
11141
11142 &lt;p&gt;To make sure firmware deb packages with a license questions are not
11143 activated without asking if the license is accepted, I extended
11144 hw-detect to look for preinst scripts in the firmware packages, and
11145 run these before activating the firmware during installation. The
11146 license question is asked using debconf in the preinst, so this should
11147 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
11148
11149 &lt;p&gt;If you want to discuss the details of these features, please
11150 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
11151 </description>
11152 </item>
11153
11154 <item>
11155 <title>Parallellized boot is now the default in Debian/unstable</title>
11156 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
11157 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
11158 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
11159 <description>&lt;p&gt;Since this evening, parallel booting is the default in
11160 Debian/unstable for machines using dependency based boot sequencing.
11161 Apparently the testing of concurrent booting has been wider than
11162 expected, if I am to believe the
11163 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11164 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
11165 with the feature this weekend, to give us some time to detect any
11166 remaining problems before Squeeze is frozen. If serious problems are
11167 detected, it is simple to change the default back to sequential boot.
11168 The upload of the new sysvinit package also activate a new upstream
11169 version.&lt;/p&gt;
11170
11171 More information about
11172 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11173 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
11174 currently possible to disable parallel booting when one run into
11175 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
11176
11177 &lt;blockquote&gt;&lt;pre&gt;
11178 CONCURRENCY=none
11179 &lt;/pre&gt;&lt;/blockquote&gt;
11180
11181 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11182 the BTS, please usertag the report to get it to show up at
11183 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11184 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11185 </description>
11186 </item>
11187
11188 <item>
11189 <title>Sitesummary tip: Listing MAC address of all clients</title>
11190 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
11191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
11192 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
11193 <description>&lt;p&gt;In the recent Debian Edu versions, the
11194 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
11195 system&lt;/a&gt; is used to keep track of the machines in the school
11196 network. Each machine will automatically report its status to the
11197 central server after boot and once per night. The network setup is
11198 also reported, and using this information it is possible to get the
11199 MAC address of all network interfaces in the machines. This is useful
11200 to update the DHCP configuration.&lt;/p&gt;
11201
11202 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
11203 ist all MAC addresses of all machines reporting to sitesummary. Run
11204 this on the collector host:&lt;/p&gt;
11205
11206 &lt;blockquote&gt;&lt;pre&gt;
11207 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
11208 &lt;/pre&gt;&lt;/blockquote&gt;
11209
11210 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
11211 line per machine and with space between the MAC addresses.&lt;/p&gt;
11212
11213 &lt;p&gt;To allow system administrators easier job at adding static DHCP
11214 addresses for hosts, it would be possible to extend this to fetch
11215 machine information from sitesummary and update the DHCP and DNS
11216 tables in LDAP using this information. Such tool is unfortunately not
11217 written yet.&lt;/p&gt;
11218 </description>
11219 </item>
11220
11221 <item>
11222 <title>systemd, an interesting alternative to upstart</title>
11223 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
11224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
11225 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
11226 <description>&lt;p&gt;The last few days a new boot system called
11227 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
11228 has been
11229 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
11230
11231 to the free software world. I have not yet had time to play around
11232 with it, but it seem to be a very interesting alternative to
11233 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
11234 a good alternative for Debian when we are able to switch to an event
11235 based boot system. Tollef is
11236 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
11237 systemd into Debian, and I look forward to seeing how well it work. I
11238 like the fact that systemd handles init.d scripts with dependency
11239 information natively, allowing them to run in parallel where upstart
11240 at the moment do not.&lt;/p&gt;
11241
11242 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
11243 platform support. It only work on recent Linux kernels, and also need
11244 some new kernel features enabled to function properly. This means
11245 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11246 system. Not sure how that will be handled if systemd proves to be the
11247 way forward.&lt;/p&gt;
11248
11249 &lt;p&gt;In the mean time, based on the
11250 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11251 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
11252 decided to enable full parallel booting as the default in Debian as
11253 soon as possible (probably this weekend or early next week), to see if
11254 there are any remaining serious bugs in the init.d dependencies. A
11255 new version of the sysvinit package implementing this change is
11256 already in experimental. If all go well, Squeeze will be released
11257 with parallel booting enabled by default.&lt;/p&gt;
11258 </description>
11259 </item>
11260
11261 <item>
11262 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
11263 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
11264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
11265 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
11266 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
11267 complete, so complete that it is actually possible to run all the
11268 init.d scripts in parallell based on these dependencies. If you want
11269 to test your Squeeze system, make sure
11270 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11271 based boot sequencing&lt;/a&gt; is enabled, and add this line to
11272 /etc/default/rcS:&lt;/p&gt;
11273
11274 &lt;blockquote&gt;&lt;pre&gt;
11275 CONCURRENCY=makefile
11276 &lt;/pre&gt;&lt;/blockquote&gt;
11277
11278 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
11279 scripts in parallel using the dependency information stored in
11280 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11281 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11282 to try to start the kdm and gdm scripts as early as possible, and will
11283 start the facilities required by kdm or gdm as early as possible to
11284 make this happen.&lt;/p&gt;
11285
11286 &lt;p&gt;Give it a try, and see if you like the result. If some services
11287 fail to start properly, it is most likely because they have incomplete
11288 init.d script dependencies in their startup script (or some of their
11289 dependent scripts have incomplete dependencies). Report bugs and get
11290 the package maintainers to fix it. :)&lt;/p&gt;
11291
11292 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
11293 manage to get the init.d script dependencies complete and correct. I
11294 expect we will get there in Squeeze+1, if we get manage to test and
11295 fix the remaining issues.&lt;/p&gt;
11296
11297 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11298 the BTS, please usertag the report to get it to show up at
11299 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11300 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11301 </description>
11302 </item>
11303
11304 <item>
11305 <title>Debian has switched to dependency based boot sequencing</title>
11306 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
11307 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
11308 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
11309 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
11310 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
11311 have been migrated to using dependency based boot sequencing. This
11312 conclude work me and others have been doing for the last three days.
11313 It feels great to see this finally part of the default Debian
11314 installation. Now we just need to weed out the last few problems that
11315 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
11316
11317 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
11318 fixing the more fundamental problem of handing the event based
11319 non-predictable kernel in the early boot.&lt;/p&gt;
11320 </description>
11321 </item>
11322
11323 <item>
11324 <title>Taking over sysvinit development</title>
11325 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
11326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
11327 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
11328 <description>&lt;p&gt;After several years of frustration with the lack of activity from
11329 the existing sysvinit upstream developer, I decided a few weeks ago to
11330 take over the package and become the new upstream. The number of
11331 patches to track for the Debian package was becoming a burden, and the
11332 lack of synchronization between the distribution made it hard to keep
11333 the package up to date.&lt;/p&gt;
11334
11335 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11336 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
11337 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
11338 and Fedora), based on the patches currently in use in these
11339 distributions. We Debian maintainers plan to move to this tarball as
11340 the new upstream as soon as we find time to do the merge. Since the
11341 new tarball was created, we agreed with Werner at SuSe to make a new
11342 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
11343 development there. The project is registered and currently waiting
11344 for approval by the Savannah administrators, and as soon as it is
11345 approved, we will import the old versions from svn and continue
11346 working on the future release.&lt;/p&gt;
11347
11348 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
11349 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
11350 </description>
11351 </item>
11352
11353 <item>
11354 <title>Debian boots quicker and quicker</title>
11355 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
11356 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
11357 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
11358 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
11359 people involved in the boot system on Debian and Ubuntu, to see if we
11360 could find more ways to speed up the boot system. This was an Ubuntu
11361 funded
11362 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
11363 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
11364 of boot systems, and ways to handle the increasing number of boot
11365 issues introduced by the Linux kernel becoming more and more
11366 asynchronous and event base. The Ubuntu approach using udev and
11367 upstart might be a good way forward. Time will show.&lt;/p&gt;
11368
11369 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
11370 process in Debian. All of these should be applied to get a quick
11371 boot:&lt;/p&gt;
11372
11373 &lt;ul&gt;
11374
11375 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
11376
11377 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
11378 clock is in UTC.&lt;/li&gt;
11379
11380 &lt;li&gt;Install and activate the insserv package to enable
11381 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11382 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
11383
11384 &lt;/ul&gt;
11385
11386 These points are based on the Google summer of code work done by
11387 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
11388 Villegas&lt;/a&gt;.
11389
11390 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
11391 unstable yesterday. When we tested it, we were able to cut 6 seconds
11392 from the boot sequence. It depend on very correct dependency
11393 declaration in all init.d scripts, so I expect us to find edge cases
11394 where the dependences in some scripts are slightly wrong when we start
11395 using this.&lt;/p&gt;
11396
11397 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11398 introduced by Raphael Geissert today, one that could affect the
11399 startup speed as well. Instead of starting some scripts concurrently
11400 from rcS.d/ and another set of scripts from rc2.d/, it would be
11401 possible to run a of them in the same process. A quick way to test
11402 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
11403 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
11404 </description>
11405 </item>
11406
11407 <item>
11408 <title>BSAs påstander om piratkopiering møter motstand</title>
11409 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
11410 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
11411 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
11412 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
11413 programvareselskapene som Microsoft og Apple, publisert en rapport der
11414 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11415 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11416 dager siden kom
11417 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
11418 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
11419 dagene. Et spesielt interessant kommentar fra Sverige,
11420 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
11421 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
11422
11423 &lt;blockquote&gt;
11424 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
11425 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11426 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
11427 exakta&quot;, säger BSAs Sverigechef John Hugosson.
11428 &lt;/blockquote&gt;
11429
11430 &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
11431 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
11432 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
11433 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
11434 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
11435
11436 &lt;p&gt;Fant lenkene via &lt;a
11437 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
11438 på Slashdot&lt;/a&gt;.&lt;/p&gt;
11439 </description>
11440 </item>
11441
11442 <item>
11443 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
11444 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
11445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
11446 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
11447 <description>&lt;p&gt;Kom over
11448 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
11449 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11450 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11451 jobber til daglig. En rask opptelling forteller meg at vi har 490
11452 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
11453 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
11454 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
11455 </description>
11456 </item>
11457
11458 <item>
11459 <title>Kryptert harddisk - naturligvis</title>
11460 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
11461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
11462 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
11463 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
11464 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
11465 når en tar tap av arbeidstid, fortrolige dokumenter,
11466 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11467 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11468 til at jeg har kryptert harddisken på både kontormaskinen og min
11469 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11470 komme på avveie, den første informasjon relatert til jobben min ved
11471 Universitetet i Oslo, og den andre relatert til blant annet
11472 foreningsarbeide. Kryptering av diskene gjør at det er lite
11473 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11474 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11475 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11476 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11477 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11478 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11479 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11480 det er gjort slik jeg gjør det er minimale, og gevinstene er
11481 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11482 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
11483
11484 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11485 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11486 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11487 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11488 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11489 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11490 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11491 betydelige.&lt;/p&gt;
11492 </description>
11493 </item>
11494
11495 <item>
11496 <title>Two projects that have improved the quality of free software a lot</title>
11497 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
11498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
11499 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
11500 <description>&lt;p&gt;There are two software projects that have had huge influence on the
11501 quality of free software, and I wanted to mention both in case someone
11502 do not yet know them.&lt;/p&gt;
11503
11504 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11505 tool to detect and expose errors in the memory handling of programs.
11506 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11507 and it will report any problems on stdout. It is even better if the
11508 program include debug information. With debug information, it is able
11509 to report the source file name and line number where the problem
11510 occurs. It can report things like &#39;reading past memory block in file
11511 X line N, the memory block was allocated in file Y, line M&#39;, and
11512 &#39;using uninitialised value in control logic&#39;. This tool has made it
11513 trivial to investigate reproducible crash bugs in programs, and have
11514 reduced the number of this kind of bugs in free software a lot.
11515
11516 &lt;p&gt;The second one is
11517 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11518 a source code checker. It is able to process the source of a program
11519 and find problems in the logic without running the program. It
11520 started out as the Stanford Checker and became well known when it was
11521 used to find bugs in the Linux kernel. It is now a commercial tool
11522 and the company behind it is running
11523 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11524 free software community, where a lot of free software projects get
11525 their source checked for free. Several thousand defects have been
11526 found and fixed so far. It can find errors like &#39;lock L taken in file
11527 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11528 Y lines O to P can never be executed&#39;. The projects included in the
11529 community service project have managed to get rid of a lot of
11530 reliability problems thanks to Coverity.&lt;/p&gt;
11531
11532 &lt;p&gt;I believe tools like this, that are able to automatically find
11533 errors in the source, are vital to improve the quality of software and
11534 make sure we can get rid of the crashing and failing software we are
11535 surrounded by today.&lt;/p&gt;
11536 </description>
11537 </item>
11538
11539 <item>
11540 <title>No patch is not better than a useless patch</title>
11541 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11542 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11543 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11544 <description>&lt;p&gt;Julien Blache
11545 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11546 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11547 patch allow one to discuss a concrete and proposed solution, and also
11548 prove that the issue at hand is important enough for someone to spent
11549 time on fixing it. No patch do not provide any of these positive
11550 properties.&lt;/p&gt;
11551 </description>
11552 </item>
11553
11554 <item>
11555 <title>Standardize on protocols and formats, not vendors and applications</title>
11556 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11558 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11559 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11560 very good one to form a long lived computer infrastructure. It is the
11561 simple one, lost by many in todays computer industry: Standardize on
11562 open network protocols and open exchange/storage formats, not applications.
11563 Applications come and go, while protocols and files tend to stay, and
11564 thus one want to make it easy to change application and vendor, while
11565 avoiding conversion costs and locking users to a specific platform or
11566 application.&lt;/p&gt;
11567
11568 &lt;p&gt;This approach make it possible to replace the client applications
11569 independently of the server applications. One can even allow users to
11570 use several different applications as long as they handle the selected
11571 protocol and format. In the normal case, only one client application
11572 is recommended and users only get help if they choose to use this
11573 application, but those that want to deviate from the easy path are not
11574 blocked from doing so.&lt;/p&gt;
11575
11576 &lt;p&gt;It also allow us to replace the server side without forcing the
11577 users to replace their applications, and thus allow us to select the
11578 best server implementation at any moment, when scale and resouce
11579 requirements change.&lt;/p&gt;
11580
11581 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11582 open formats, but I would never recommend standardizing on a single
11583 application that do not use open network protocol or open formats.&lt;/p&gt;
11584 </description>
11585 </item>
11586
11587 <item>
11588 <title>Returning from Skolelinux developer gathering</title>
11589 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11590 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11591 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11592 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11593 Edu/Skolelinux development gathering. I got a bit done tuning the
11594 desktop, and looked into the dynamic service location protocol
11595 implementation avahi. It look like it could be useful for us. Almost
11596 30 people participated, and I believe it was a great environment to
11597 get to know the Skolelinux system. Walter Bender, involved in the
11598 development of the Sugar educational platform, presented his stuff and
11599 also helped me improve my OLPC installation. He also showed me that
11600 his Turtle Art application can be used in standalone mode, and we
11601 agreed that I would help getting it packaged for Debian. As a
11602 standalone application it would be great for Debian Edu. We also
11603 tried to get the video conferencing working with two OLPCs, but that
11604 proved to be too hard for us. The application seem to need more work
11605 before it is ready for me. I look forward to getting home and relax
11606 now. :)&lt;/p&gt;
11607 </description>
11608 </item>
11609
11610 <item>
11611 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11612 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11614 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11615 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11616 optimal. There is RFC 2307 documenting one way to store NIS maps in
11617 LDAP, and a modified version of this normally called RFC 2307bis, with
11618 some modifications to be compatible with Active Directory. The RFC
11619 specification handle the content of a lot of system databases, but do
11620 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11621
11622 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11623 we would like to store information about users, SMB clients/hosts,
11624 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11625 and LTSP configuration in LDAP. These objects have a lot in common,
11626 but with the current LDAP schemas it is not possible to have one
11627 object per entity. For example, one need to have at least three LDAP
11628 objects for a given computer, one with the SMB related stuff, one with
11629 DNS information and another with DHCP information. The schemas
11630 provided for DNS and DHCP are impossible to combine into one LDAP
11631 object. In addition, it is impossible to implement quick queries for
11632 netgroup membership, because of the way NIS triples are implemented.
11633 It just do not scale. I believe it is time for a few RFC
11634 specifications to cleam up this mess.&lt;/p&gt;
11635
11636 &lt;p&gt;I would like to have one LDAP object representing each computer in
11637 the network, and this object can then keep the SMB (ie host key), DHCP
11638 (mac address/name) and DNS (name/IP address) settings in one place.
11639 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11640
11641 &lt;p&gt;I would also like to have a quick way to map from a user or
11642 computer and to the net group this user or computer is a member.&lt;/p&gt;
11643
11644 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11645 in this regard, and the unix side need to catch up. Time to start a
11646 new IETF work group?&lt;/p&gt;
11647 </description>
11648 </item>
11649
11650 <item>
11651 <title>Endelig er Debian Lenny gitt ut</title>
11652 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11654 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11655 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11656 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11657 Et langt steg videre for Debian-prosjektet, og en rekke nye
11658 programpakker blir nå tilgjengelig for de av oss som bruker den
11659 stabile utgaven av Debian. Neste steg er nå å få
11660 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11661 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11662 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11663 slippes løs på skolene. Takk til alle debian-utviklerne som har
11664 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11665 bootsekvens tilgjengelig i stabil utgave, vha pakken
11666 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11667 </description>
11668 </item>
11669
11670 <item>
11671 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11672 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11673 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11674 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11675 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11676 Oslo. Most of Saturday was used for the general assemly for the
11677 member organization, but the rest of the weekend I used to tune the
11678 LTSP installation. LTSP now work out of the box on the 10-network.
11679 Acer Aspire One proved to be a very nice thin client, with both
11680 screen, mouse and keybard in a small box. Was working on getting the
11681 diskless workstation setup configured out of the box, but did not
11682 finish it before the weekend was up.&lt;/p&gt;
11683
11684 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11685 the Brazilian group, so that will have to wait for the next
11686 development gathering. Would love to have the Debian Edu installer
11687 automatically detect and configure a multiseat setup when it find one
11688 of these cards.&lt;/p&gt;
11689 </description>
11690 </item>
11691
11692 <item>
11693 <title>The sorry state of multimedia browser plugins in Debian</title>
11694 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11696 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11697 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11698 plugins available in Debian Lenny, to see which one we should use by
11699 default in Debian Edu. We need an embedded video playing plugin with
11700 control buttons to pause or stop the video, and capable of streaming
11701 all the multimedia content available on the web. The test results and
11702 notes are available on
11703 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11704 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11705 fill this need. My personal video player favorite, VLC, has a really
11706 bad plugin which fail on a lot of the test pages. A lot of the MIME
11707 types I would expect to work with any free software player (like
11708 video/ogg), just do not work. And simple formats like the
11709 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11710 totem and vlc plugins. I hope the situation will improve soon. No
11711 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11712
11713 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11714 be the only one fitting our needs. :/&lt;/p&gt;
11715 </description>
11716 </item>
11717
11718 </channel>
11719 </rss>