]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
60a856a2c12fd96208538849f34785fd80e18a10
[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>Jami/Ring, finally functioning peer to peer communication client</title>
11 <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
13 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
14 <description>&lt;p&gt;Some years ago, in 2016, I
15 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
16 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
17 It would provide messaging without any central server coordinating the
18 system and without requiring all users to register a phone number or
19 own a mobile phone. Back then, I could not get it to work, and put it
20 aside until it had seen more development. A few days ago I decided to
21 give it another try, and am happy to report that this time I am able
22 to not only send and receive messages, but also place audio and video
23 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
24
25 &lt;p&gt;The Ring system changed name earlier this year to
26 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
27 tried doing web search for &#39;ring&#39; when I discovered it for the first
28 time, and can only applaud this change as it is impossible to find
29 something called Ring among the noise of other uses of that word. Now
30 you can search for &#39;jami&#39; and this client and
31 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
32 least on duckduckgo.&lt;/p&gt;
33
34 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
35 calls, and try to send them directly between the communicating parties
36 if possible. If this proves impossible (for example if both ends are
37 behind NAT), it will use a central SIP TURN server maintained by the
38 Jami project. Jami can also be a normal SIP client. If the SIP
39 server is unencrypted, the audio and video calls will also be
40 unencrypted. This is as far as I know the only case where Jami will
41 do anything without encryption.&lt;/p&gt;
42
43 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
44 Android, iOS, and Android TV. It is included in Debian already. Jami
45 also work for those using F-Droid without any Google connections,
46 while Signal do not.
47 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
48 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
49 distributed hash table (DHT) system (similar to BitTorrent) running
50 over UDP. On one of the networks I use, I discovered Jami failed to
51 work. I tracked this down to the fact that incoming UDP packages
52 going to ports 1-49999 were blocked, and the DHT would pick a random
53 port and end up in the low range most of the time. After talking to
54 the developers, I solved this by enabling the dhtproxy in the
55 settings, thus using TCP to talk to a central DHT proxy instead of
56
57 peering directly with others. I&#39;ve been told the developers are
58 working on allowing DHT to use TCP to avoid this problem. I also ran
59 into a problem when trying to talk to the version of Ring included in
60 Debian Stable (Stretch). Apparently the protocol changed between
61 beta2 and the current version, making these clients incompatible.
62 Hopefully the protocol will not be made incompatible in the
63 future.&lt;/p&gt;
64
65 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
66 came across another communication platform I have not tested yet. The
67 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
68 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
69 become the topic of a future blog post.&lt;/p&gt;
70
71 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
72 activities, please send Bitcoin donations to my address
73 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
74 </description>
75 </item>
76
77 <item>
78 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
79 <link>http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
80 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
81 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
82 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
83 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
84 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
85 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
86 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
87 nye versjonen kom på nyåret, og ble
88 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
89 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
90 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
91 måtte justeres, men ikke noe alvorlig. Har oppdatert
92 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
93 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
94
95 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
96 å spille for oss som liker slikt. :)&lt;/p&gt;
97
98 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
99 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
100 til min adresse
101 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
102 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
103 </description>
104 </item>
105
106 <item>
107 <title>Debian now got everything you need to program Micro:bit</title>
108 <link>http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
110 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
111 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
112 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
113 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
114 thanks to the hard work of Nick Morrott and the Debian python
115 packaging team. The micro:bit project recommend the mu-editor to
116 program the microcomputer, as this editor will take care of all the
117 machinery required to injekt/flash micropython alongside the program
118 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
119
120 &lt;p&gt;There are three main pieces involved. The first to enter Debian
121 was
122 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
123 which was accepted into the archive 2019-01-12. The next one was
124 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
125 showed up 2019-01-13. The final and hardest part to to into the
126 archive was
127 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
128 which needed to get its build system and dependencies into Debian
129 before it was accepted 2019-01-20. The last one is already in Debian
130 Unstable and should enter Debian Testing / Buster in three days. This
131 all allow any user of the micro:bit to get going by simply running
132 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
133 Buster is released as stable, all the users of Debian stable will be
134 catered for.&lt;/p&gt;
135
136 &lt;p&gt;As a minor final touch, I added rules to
137 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
138 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
139 package. This make sure any user of the isenkram desktop daemon will
140 get a popup suggesting to install mu-editor then the USB cable from
141 the micro:bit is inserted for the first time.&lt;/p&gt;
142
143 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
144
145 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
146 activities, please send Bitcoin donations to my address
147 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
148 </description>
149 </item>
150
151 <item>
152 <title>Learn to program with Minetest on Debian</title>
153 <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
155 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
156 <description>&lt;p&gt;A fun way to learn how to program
157 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
158 instructions in the book
159 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
160 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
161 who like to play with Minecraft. The book uses a Python library to
162 talk to a TCP/IP socket with an API accepting build instructions and
163 providing information about the current players in a Minecraft world.
164 The TCP/IP API was first created for the Minecraft implementation for
165 Raspberry Pi, and has since been ported to some server versions of
166 Minecraft. The book contain recipes for those using Windows, MacOSX
167 and Raspian. But a little known fact is that you can follow the same
168 recipes using the free software construction game
169 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
170
171 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
172 Minetest module implementing the same API&lt;/a&gt;, making it possible to
173 use the Python programs coded to talk to Minecraft with Minetest too.
174 I
175 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
176 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
177 FTP masters NEW queue, learning to program Python with Minetest on
178 Debian will be a simple &#39;apt install&#39; away. The Debian package is
179 maintained as part of the Debian Games team, and
180 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
181 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
182 Salsa.&lt;/p&gt;
183
184 &lt;p&gt;You will most likely need to install several of the Minetest
185 modules in Debian for the examples included with the library to work
186 well, as there are several blocks used by the example scripts that are
187 provided via modules in Minetest. Without the required blocks, a
188 simple stone block is used instead. My initial testing with a analog
189 clock did not get gold arms as instructed in the python library, but
190 instead used stone arms.&lt;/p&gt;
191
192 &lt;p&gt;I tried to find a way to add the API to the desktop version of
193 Minecraft, but were unable to find any working recipes. The
194 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
195 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
196 working with a standalone Minecraft server setup. Are there any
197 options to use with the normal desktop version?&lt;/p&gt;
198
199 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
200 activities, please send Bitcoin donations to my address
201 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
202 </description>
203 </item>
204
205 <item>
206 <title>Time for an official MIME type for patches?</title>
207 <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
209 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
210 <description>&lt;p&gt;As part of my involvement in
211 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
212 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
213 emails into a test instance of the archive to see how well this would
214 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
215 notmuch email database&lt;/a&gt;, all public emails sent to me via
216 @lists.debian.org, giving me a set of around 216 000 emails to import.
217 In the process, I had a look at the various attachments included in
218 these emails, to figure out what to do with attachments, and noticed
219 that one of the most common attachment formats do not have
220 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
221 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
222 diff, ie the input for patch, is on the top 10 list of formats
223 included in these emails. At the moment people seem to use either
224 text/x-patch or text/x-diff, but neither is officially registered. It
225 would be better if one official MIME type were registered and used
226 everywhere.&lt;/p&gt;
227
228 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
229 up the topic on
230 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
231 media-types mailing list&lt;/a&gt;. If you are interested in discussion
232 which MIME type to use as the official for patch files, or involved in
233 making software using a MIME type for patches, perhaps you would like
234 to join the discussion?&lt;/p&gt;
235
236 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
237 activities, please send Bitcoin donations to my address
238 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
239 </description>
240 </item>
241
242 <item>
243 <title>Automatic Google Drive sync using grive in Debian</title>
244 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
246 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
247 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
248 rescue the remains, I helped set up automatic sync with Google Drive.
249 I did not find any sensible Debian package handling this
250 automatically, so I rebuild the grive2 source from
251 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
252 task and added a autostart desktop entry and a small shell script to
253 run in the background while the user is logged in to do the sync.
254 Here is a sketch of the setup for future reference.&lt;/p&gt;
255
256 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
257 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
258 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
259 to start the sync when the user log in:&lt;/p&gt;
260
261 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
262 [Desktop Entry]
263 Name=Google drive autosync
264 Type=Application
265 Exec=/home/user/bin/grive-sync
266 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
267
268 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
269 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
270
271 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
272 #!/bin/sh
273 set -e
274 cd ~/
275 cleanup() {
276 if [ &quot;$syncpid&quot; ] ; then
277 kill $syncpid
278 fi
279 }
280 trap cleanup EXIT INT QUIT
281 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
282 syncpdi=$!
283 while true; do
284 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
285 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
286 exit 1
287 fi
288 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
289 /usr/lib/grive/grive-sync.sh sync googledrive
290 fi
291 sleep 300
292 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
293 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
294
295 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
296 GNU GPL v2 licensed (or any later version, at your leisure), but I
297 doubt this code is possible to claim copyright on.&lt;/p&gt;
298
299 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
300 activities, please send Bitcoin donations to my address
301 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
302 </description>
303 </item>
304
305 <item>
306 <title>Using the Kodi API to play Youtube videos</title>
307 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
308 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
309 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
310 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
311 tell it to play a youtube URL I received in a chat, without having to
312 insert search terms using the on-screen keyboard. After searching the
313 web for API access to the Youtube plugin and testing a bit, I managed
314 to find a recipe that worked. If you got a kodi instance with its API
315 available from http://kodihost/jsonrpc, you can try the following to
316 have check out a nice cover band.&lt;/p&gt;
317
318 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
319 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
320 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
321 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
322 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
323
324 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
325 first argument. It can now handle direct video links, youtube links
326 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
327 Chromecast. :)&lt;/p&gt;
328
329 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
330 activities, please send Bitcoin donations to my address
331 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
332 </description>
333 </item>
334
335 <item>
336 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
337 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
339 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
340 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
341 with my family using a self hosted solution, as it is unacceptable to
342 place images from my personal life under the control of strangers
343 working for data hoarders like Google or Dropbox. The last few days I
344 have drafted an approach that might work out, and I would like to
345 share it with you. I would like to publish images on a server under
346 my control, and point some Internet connected display units using some
347 free and open standard to the images I published. As my primary
348 language is not limited to ASCII, I need to store metadata using
349 UTF-8. Many years ago, I hoped to find a digital photo frame capable
350 of reading a RSS feed with image references (aka using the
351 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
352 of such frames. In the end I gave up that approach.&lt;/p&gt;
353
354 &lt;p&gt;Some months ago, I discovered that
355 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
356 read images from a RSS feed, and used it to set up a screen saver on
357 my home info screen, showing images from the Daily images feed from
358 NASA. This proved to work well. More recently I discovered that
359 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
360 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
361 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
362 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
363 screen saver capable of reading a RSS feed with images and news. For
364 fun, I used it this summer to test Kodi on my parents TV by hooking up
365 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
366 screen saver showing selected pictures from my selection.&lt;/p&gt;
367
368 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
369 a RSS feed for the Kodi instance. I adjusted my &lt;a
370 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
371 /var/www/html/privatepictures/, wrote a small Perl script to extract
372 title and description metadata from the photo files and generate the
373 RSS file. I ended up using Perl instead of python, as the
374 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
375 tags I ended up using, while python3-exif did not. The relevant EXIF
376 tags only support ASCII, so I had to find better alternatives. XMP
377 seem to have the support I need.&lt;/p&gt;
378
379 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
380 use tags that can be easily added/updated using normal free software
381 photo managing software. I ended up using the tags set using this
382 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
383
384 &lt;blockquote&gt;&lt;pre&gt;
385 exiftool -headline=&#39;The RSS image title&#39; \
386 -description=&#39;The RSS image description.&#39; \
387 -subject+=for-family photo.jpeg
388 &lt;/pre&gt;&lt;/blockquote&gt;
389
390 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
391 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
392 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
393 shared with my family. Images with this keyword set are located and
394 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
395
396 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
397 suggestions.&lt;/p&gt;
398
399 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
400 activities, please send Bitcoin donations to my address
401 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
402 </description>
403 </item>
404
405 <item>
406 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
407 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
409 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
410 <description>&lt;p&gt;Last night, I wrote
411 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
412 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
413 During the day I received valuable feedback, and thanks to the
414 suggestions I have been able to rewrite the recipe into a much simpler
415 approach requiring no setup at all. It is a single script that take
416 care of it all.&lt;/p&gt;
417
418 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
419 desktop and stream it to Kodi. This fixed the video quality issue I
420 saw initially. It further removes the need to add a m3u file on the
421 Kodi machine, as it instead connects to
422 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
423 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
424 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
425 the script below, run it with the DNS name or IP address of the kodi
426 server to stream to as the only argument, and watch your screen show
427 up on the Kodi screen. Note, it depend on multicast on the local
428 network, so if you need to stream outside the local network, the
429 script must be modified. Also note, I have no idea if audio work, as
430 I only care about the picture part.&lt;/p&gt;
431
432 &lt;blockquote&gt;&lt;pre&gt;
433 #!/bin/sh
434 #
435 # Stream the Linux desktop view to Kodi. See
436 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
437 # for backgorund information.
438
439 # Make sure the stream is stopped in Kodi and the gstreamer process is
440 # killed if something go wrong (for example if curl is unable to find the
441 # kodi server). Do the same when interrupting this script.
442 kodicmd() {
443 host=&quot;$1&quot;
444 cmd=&quot;$2&quot;
445 params=&quot;$3&quot;
446 curl --silent --header &#39;Content-Type: application/json&#39; \
447 --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; \
448 &quot;http://$host/jsonrpc&quot;
449 }
450 cleanup() {
451 if [ -n &quot;$kodihost&quot; ] ; then
452 # Stop the playing when we end
453 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
454 jq .result[].playerid)
455 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
456 fi
457 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
458 kill &quot;$gstpid&quot;
459 fi
460 }
461 trap cleanup EXIT INT
462
463 if [ -n &quot;$1&quot; ]; then
464 kodihost=$1
465 shift
466 else
467 kodihost=kodi.local
468 fi
469
470 mcast=239.255.0.1
471 mcastport=1234
472 mcastttl=1
473
474 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
475 cut -d&quot; &quot; -f2|head -1)
476 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
477 videoconvert ! queue2 ! \
478 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
479 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
480 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
481 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
482 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
483 &gt; /dev/null 2&gt;&amp;1 &amp;
484 gstpid=$!
485
486 # Give stream a second to get going
487 sleep 1
488
489 # Ask kodi to start streaming using its JSON-RPC API
490 kodicmd &quot;$kodihost&quot; Player.Open \
491 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
492
493 # wait for gst to end
494 wait &quot;$gstpid&quot;
495 &lt;/pre&gt;&lt;/blockquote&gt;
496
497 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
498
499 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
500 activities, please send Bitcoin donations to my address
501 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
502 </description>
503 </item>
504
505 <item>
506 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
507 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
509 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
510 <description>&lt;p&gt;PS: See
511 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
512 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
513
514 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
515 my projector connected to Kodi. I sadly had to admit that I had no
516 idea, as it was a task I never had tried. Since then, I have been
517 looking for a way to do so, preferable without much extra software to
518 install on either side. Today I found a way that seem to kind of
519 work. Not great, but it is a start.&lt;/p&gt;
520
521 &lt;p&gt;I had a look at several approaches, for example
522 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
523 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
524 local storage enough to store the stream locally. This is not going
525 to work well for me, lacking enough free space, and it would
526 impossible for my friend to get working.&lt;/p&gt;
527
528 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
529 video stream that Kodi could play. Preferably using
530 broadcast/multicast, to avoid having to change any setup on the Kodi
531 side when starting such stream. Unfortunately, the only recipe I
532 could find using multicast used the rtp protocol, and this protocol
533 seem to not be supported by Kodi.&lt;/p&gt;
534
535 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
536 have to specify the IP address of the streaming machine in both the
537 sending command and the file on the Kodi server. But it is showing my
538 desktop, and thus allow us to have a shared look on the big screen at
539 the programs I work on.&lt;/p&gt;
540
541 &lt;p&gt;I did not spend much time investigating codeces. I combined the
542 rtp and rtsp recipes from
543 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
544 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
545 this working on the desktop/streaming end.&lt;/p&gt;
546
547 &lt;blockquote&gt;&lt;pre&gt;
548 vlc screen:// --sout \
549 &#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;
550 &lt;/pre&gt;&lt;/blockquote&gt;
551
552 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
553 same IP address:&lt;/p&gt;
554
555 &lt;blockquote&gt;&lt;pre&gt;
556 echo rtsp://192.168.11.4:8080/test.sdp \
557 &gt; /storage/videos/screenstream.m3u
558 &lt;/pre&gt;&lt;/blockquote&gt;
559
560 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
561 as I can tell the IP must be hardcoded for this to work. In other
562 words, if someone elses machine is going to do the steaming, you have
563 to update screenstream.m3u on the Kodi machine and adjust the vlc
564 recipe. To get started, locate the file in Kodi and select the m3u
565 file while the VLC stream is running. The desktop then show up in my
566 big screen. :)&lt;/p&gt;
567
568 &lt;p&gt;When using the same technique to stream a video file with audio,
569 the audio quality is really bad. No idea if the problem is package
570 loss or bad parameters for the transcode. I do not know VLC nor Kodi
571 enough to tell.&lt;/p&gt;
572
573 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
574 succestions and reminded me about an important step. The &quot;screen:&quot;
575 input source is only available once the vlc-plugin-access-extra
576 package is installed on Debian. Without it, you will see this error
577 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
578 for details.&quot; He further found that it is possible to drop some parts
579 of the VLC command line to reduce the amount of hardcoded information.
580 It is also useful to consider using cvlc to avoid having the VLC
581 window in the desktop view. In sum, this give us this command line on
582 the source end
583
584 &lt;blockquote&gt;&lt;pre&gt;
585 cvlc screen:// --sout \
586 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
587 &lt;/pre&gt;&lt;/blockquote&gt;
588
589 &lt;p&gt;and this on the Kodi end&lt;p&gt;
590
591 &lt;blockquote&gt;&lt;pre&gt;
592 echo rtsp://192.168.11.4:8080/ \
593 &gt; /storage/videos/screenstream.m3u
594 &lt;/pre&gt;&lt;/blockquote&gt;
595
596 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
597 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
598 audio quality, so I guess the issue is in the input or transcoding
599 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
600 parameters to use more bandwidth, but it did not make a
601 difference.&lt;/p&gt;
602
603 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
604 gstreamer instead of VLC, and this proved to work great! He also
605 provided me with the trick to get Kodi to use a multicast stream as
606 its source. By using this monstrous oneliner, I can stream my desktop
607 with good video quality in reasonable framerate to the 239.255.0.1
608 multicast address on port 1234:
609
610 &lt;blockquote&gt;&lt;pre&gt;
611 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
612 videoconvert ! queue2 ! \
613 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
614 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
615 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
616 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
617 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
618 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
619 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
620 &lt;/pre&gt;&lt;/blockquote&gt;
621
622 &lt;p&gt;and this on the Kodi end&lt;p&gt;
623
624 &lt;blockquote&gt;&lt;pre&gt;
625 echo udp://@239.255.0.1:1234 \
626 &gt; /storage/videos/screenstream.m3u
627 &lt;/pre&gt;&lt;/blockquote&gt;
628
629 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
630 pick the one you need. This approach will of course lead to trouble
631 if more than one source uses the same multicast port and address.
632 Note the ttl-mc=1 setting, which limit the multicast packages to the
633 local network. If the value is increased, your screen will be
634 broadcasted further, one network &quot;hop&quot; for each increase (read up on
635 multicast to learn more. :)!&lt;/p&gt;
636
637 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
638 could use this VLC command to stream to the same multicast address.
639 The image quality is way better than the rtsp approach, but gstreamer
640 seem to be doing a better job.&lt;/p&gt;
641
642 &lt;blockquote&gt;&lt;pre&gt;
643 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;
644 &lt;/pre&gt;&lt;/blockquote&gt;
645
646 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
647 activities, please send Bitcoin donations to my address
648 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
649 </description>
650 </item>
651
652 <item>
653 <title>What is the most supported MIME type in Debian in 2018?</title>
654 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
656 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
657 <description>&lt;p&gt;Five years ago,
658 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
659 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
660 analysing the desktop files in all packages in the archive. Since
661 then, the DEP-11 AppStream system has been put into production, making
662 the task a lot easier. This made me want to repeat the measurement,
663 to see how much things changed. Here are the new numbers, for
664 unstable only this time:
665
666 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
667
668 &lt;pre&gt;
669 count MIME type
670 ----- -----------------------
671 56 image/jpeg
672 55 image/png
673 49 image/tiff
674 48 image/gif
675 39 image/bmp
676 38 text/plain
677 37 audio/mpeg
678 34 application/ogg
679 33 audio/x-flac
680 32 audio/x-mp3
681 30 audio/x-wav
682 30 audio/x-vorbis+ogg
683 29 image/x-portable-pixmap
684 27 inode/directory
685 27 image/x-portable-bitmap
686 27 audio/x-mpeg
687 26 application/x-ogg
688 25 audio/x-mpegurl
689 25 audio/ogg
690 24 text/html
691 &lt;/pre&gt;
692
693 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
694 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
695 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
696
697 &lt;p&gt;It is interesting to see how image formats have passed text/plain
698 as the most announced supported MIME type. These days, thanks to the
699 AppStream system, if you run into a file format you do not know, and
700 want to figure out which packages support the format, you can find the
701 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
702 look up all packages announcing support for this format in their
703 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
704 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
705 me, want to know which packages support inode/directory, you can get a
706 list like this:&lt;/p&gt;
707
708 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
709 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
710 Package: anjuta
711 Package: audacious
712 Package: baobab
713 Package: cervisia
714 Package: chirp
715 Package: dolphin
716 Package: doublecmd-common
717 Package: easytag
718 Package: enlightenment
719 Package: ephoto
720 Package: filelight
721 Package: gwenview
722 Package: k4dirstat
723 Package: kaffeine
724 Package: kdesvn
725 Package: kid3
726 Package: kid3-qt
727 Package: nautilus
728 Package: nemo
729 Package: pcmanfm
730 Package: pcmanfm-qt
731 Package: qweborf
732 Package: ranger
733 Package: sirikali
734 Package: spacefm
735 Package: spacefm
736 Package: vifm
737 %
738 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
739
740 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
741 format is not yet supported by any package in Debian:&lt;/p&gt;
742
743 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
744 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
745 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
746 %
747 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
748
749 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
750 format:&lt;/p&gt;
751
752 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
753 % appstreamcli what-provides mimetype application/sla|grep Package
754 Package: cura
755 Package: meshlab
756 Package: printrun
757 %
758 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
759
760 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
761
762 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
763 activities, please send Bitcoin donations to my address
764 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
765 </description>
766 </item>
767
768 <item>
769 <title>Debian APT upgrade without enough free space on the disk...</title>
770 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
772 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
773 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
774 for a while, and when I need to update it there is not enough free
775 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
776 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
777 upgrade only some of the packages in one batch, until the amount of
778 packages to download fall below the amount of free space available.
779 Today, I had about 500 packages to upgrade, and after a while I got
780 tired of trying to install chunks of packages manually. I concluded
781 that I did not have the spare hours required to complete the task, and
782 decided to see if I could automate it. I came up with this small
783 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
784
785 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
786 #!/bin/sh
787 #
788 # Upgrade packages when the disk is too full to upgrade every
789 # upgradable package in one lump. Fetching packages to upgrade using
790 # apt, and then installing using dpkg, to avoid changing the package
791 # flag for manual/automatic.
792
793 set -e
794
795 ignore() {
796 if [ &quot;$1&quot; ]; then
797 grep -v &quot;$1&quot;
798 else
799 cat
800 fi
801 }
802
803 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
804 echo &quot;Upgrading $p&quot;
805 apt clean
806 apt install --download-only -y $p
807 for f in /var/cache/apt/archives/*.deb; do
808 if [ -e &quot;$f&quot; ]; then
809 dpkg -i /var/cache/apt/archives/*.deb
810 break
811 fi
812 done
813 done
814 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
815
816 &lt;p&gt;The script will extract the list of packages to upgrade, try to
817 download the packages needed to upgrade one package, install the
818 downloaded packages using dpkg. The idea is to upgrade packages
819 without changing the APT mark for the package (ie the one recording of
820 the package was manually requested or pulled in as a dependency). To
821 use it, simply run it as root from the command line. If it fail, try
822 &#39;apt install -f&#39; to clean up the mess and run the script again. This
823 might happen if the new packages conflict with one of the old
824 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
825
826 &lt;p&gt;It take one option, a package to ignore in the list of packages to
827 upgrade. The option to ignore a package is there to be able to skip
828 the packages that are simply too large to unpack. Today this was
829 &#39;ghc&#39;, but I have run into other large packages causing similar
830 problems earlier (like TeX).&lt;/p&gt;
831
832 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
833 alternative ways to handle this. The &quot;unattended-upgrades
834 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
835 each package to upgrade, and then upgrade them in order, smallest set
836 first. It might be a better option than my above mentioned script.
837 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
838 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
839
840 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
841 activities, please send Bitcoin donations to my address
842 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
843 </description>
844 </item>
845
846 <item>
847 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
848 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
849 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
850 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
851 <description>&lt;p&gt;A new version of the
852 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
853 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
854 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
855 useful. It was uploaded the last few days, and the last update will
856 enter testing tomorrow. See the
857 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
858 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
859 was announced 6 days ago. We will try to get it into Debian as
860 well.&lt;/p&gt;
861
862 &lt;p&gt;More information related to 3D printing is available on the
863 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
864 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
865 in Debian.&lt;/p&gt;
866
867 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
868 activities, please send Bitcoin donations to my address
869 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
870 </description>
871 </item>
872
873 <item>
874 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
875 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
877 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
878 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
879 that the nice and user friendly 3D printer slicer software Cura just
880 entered Debian Unstable. It consist of five packages,
881 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
882 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
883 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
884 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
885 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
886 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
887 two, uranium and cura, entered Unstable yesterday. This should make
888 it easier for Debian users to print on at least the Ultimaker class of
889 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
890 make life easier for at least me. :)&lt;/p&gt;
891
892 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
893 happy to assist him in sponsoring the packages. With the introduction
894 of Cura, Debian is up to three 3D printer slicers at your service,
895 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
896 printer, give it a go. :)&lt;/p&gt;
897
898 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
899 team, flocking together on the
900 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
901 mailing list and the
902 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
903 IRC channel.&lt;/p&gt;
904
905 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
906 version 3.0.3 and then update the entire set of packages to version
907 3.1.0 which showed up the last few days.&lt;/p&gt;
908 </description>
909 </item>
910
911 <item>
912 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
913 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
914 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
915 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
916 <description>&lt;p&gt;At my nearby maker space,
917 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
918 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
919 on Windows and MacOS X than Linux, because the software involved had
920 to be manually compiled and set up on Linux while premade packages
921 worked out of the box on Windows and MacOS X. I found this annoying,
922 as the software involved,
923 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
924 and should be trivial to get up and running on Linux if someone took
925 the time to package it for the relevant distributions. I even found
926 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
927 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
928 never resulted in the software showing up in Debian. So a few days
929 ago I offered my help to try to improve the situation.&lt;/p&gt;
930
931 &lt;p&gt;Now I am very happy to see that all the packages required by a
932 working Cura in Debian are uploaded into Debian and waiting in the NEW
933 queue for the ftpmasters to have a look. You can track the progress
934 on
935 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
936 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
937
938 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
939 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
940 queue&lt;/a&gt; while we work up updating the packages to the latest
941 upstream version.&lt;/p&gt;
942
943 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
944 to use and was unable to configure correctly for Ultimaker 2+ in the
945 short time I spent on it, are already in Debian. If you are looking
946 for 3D printer &quot;slicers&quot; and want something already available in
947 Debian, check out
948 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
949 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
950 The latter is a fork of the former.&lt;/p&gt;
951
952 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
953 activities, please send Bitcoin donations to my address
954 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
955 </description>
956 </item>
957
958 <item>
959 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
960 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
961 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
962 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
963 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
964 mobile cell towers. And this radio chatter is available for anyone
965 with a radio receiver capable of receiving them. Details about the
966 mobile phones with very good accuracy is of course collected by the
967 phone companies, but this is not the topic of this blog post. The
968 mobile phone radio chatter make it possible to figure out when a cell
969 phone is nearby, as it include the SIM card ID (IMSI). By paying
970 attention over time, one can see when a phone arrive and when it leave
971 an area. I believe it would be nice to make this information more
972 available to the general public, to make more people aware of how
973 their phones are announcing their whereabouts to anyone that care to
974 listen.&lt;/p&gt;
975
976 &lt;p&gt;I am very happy to report that we managed to get something
977 visualizing this information up and running for
978 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
979 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
980 library. The solution is based on the
981 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
982 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
983 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
984 Sone from the Computer Science department of the University of
985 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
986 IMSIs) as dots in a web browser graph, with lines to the dot
987 representing mobile base station it is talking to. It was working in
988 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
989
990 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
991 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
992 connected and visualize the visible cell phone towers using an
993 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
994 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
995 grgsm_livemon_headless processes from
996 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
997 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
998
999 &lt;p&gt;The frequencies to listen to, are identified using a slightly
1000 patched scan-and-livemon (to set the --args values for each receiver),
1001 and the Hopglass data is generated using the
1002 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
1003 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
1004 more than four SDRs working. There is also a geographical map trying
1005 to show the location of the base stations, but I believe their
1006 coordinates are hardcoded to some random location in Germany, I
1007 believe. The code should be replaced with code to look up location in
1008 a text file, a sqlite database or one of the online databases
1009 mentioned in
1010 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
1011 issue for the topic&lt;/a&gt;.
1012
1013 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
1014 </description>
1015 </item>
1016
1017 <item>
1018 <title>Easier recipe to observe the cell phones around you</title>
1019 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
1020 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
1021 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
1022 <description>&lt;p&gt;A little more than a month ago I wrote
1023 &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
1024 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1025 to nearby mobile phone base stations using Debian GNU/Linux and a
1026 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
1027 the location of people and equipment (like cars and trains) with an
1028 accuracy of a few kilometer. Since then we have worked to make the
1029 procedure even simpler, and it is now possible to do this without any
1030 manual frequency tuning and without building your own packages.&lt;/p&gt;
1031
1032 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
1033 package is now included in Debian testing and unstable, and the
1034 IMSI-catcher code no longer require root access to fetch and decode
1035 the GSM data collected using gr-gsm.&lt;/p&gt;
1036
1037 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
1038 clone of two python scripts:&lt;/p&gt;
1039
1040 &lt;ol&gt;
1041
1042 &lt;li&gt;Start with a Debian machine running the Buster version (aka
1043 testing).&lt;/li&gt;
1044
1045 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
1046 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
1047
1048 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
1049 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
1050
1051 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
1052
1053 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1054 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
1055 stations and start listening for GSM packages on one of them.&lt;/li&gt;
1056
1057 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1058 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
1059
1060 &lt;/ol&gt;
1061
1062 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
1063 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
1064 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
1065 work with RTL 8232 and other similar USB radio receivers you can get
1066 very cheaply
1067 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
1068 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
1069 and only use HackRF for fetching GSM data.&lt;/p&gt;
1070
1071 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
1072 frequencies at the time, so if you are going to track and count every
1073 cell phone around you, you need to listen to all the frequencies used.
1074 To listen to several frequencies, use the --numrecv argument to
1075 scan-and-livemon to use several receivers. Further, I am not sure if
1076 phones using 3G or 4G will show as talking GSM to base stations, so
1077 this approach might not see all phones around you. I typically see
1078 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
1079
1080 &lt;p&gt;I&#39;ve tried to run the scanner on a
1081 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
1082 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
1083 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
1084 stdout, I am told there it is caused by a buffer overflow between the
1085 radio and GNU Radio, caused by the program being unable to read the
1086 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
1087 where you started scan-and-livemon, you need a give the process more
1088 CPU power. Perhaps someone are able to optimize the code to a point
1089 where it become possible to set up RPi3 based GSM sniffers? I tried
1090 using Raspbian instead of Debian, but there seem to be something wrong
1091 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
1092 </description>
1093 </item>
1094
1095 <item>
1096 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
1097 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
1098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
1099 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
1100 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
1101 web based ICT news magazine digi.no on
1102 &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
1103 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
1104 DVB-T software defined radios. The article refered to instructions
1105 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
1106 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;
1107
1108 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
1109 bypass apt), use pip to install pybombs (to bypass both apt and pip),
1110 and the ask pybombs to fetch and build everything you need from
1111 scratch. I wanted to see if I could do the same on the most recent
1112 Debian packages, but this did not work because pybombs tried to build
1113 stuff that no longer build with the most recent openssl library or
1114 some other version skew problem. While trying to get this recipe
1115 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
1116 and the only piece of software dependency missing in Debian was the
1117 gr-gsm package. I also found out that the lead upstream developer of
1118 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
1119 Debian packages provided in an Ubuntu PPA repository. All I needed to
1120 do was to dget the Debian source package and built it.&lt;/p&gt;
1121
1122 &lt;p&gt;The IMSI collector is a python script listening for packages on the
1123 loopback network device and printing to the terminal some specific GSM
1124 packages with IMSI numbers in them. The code is fairly short and easy
1125 to understand. The reason this work is because gr-gsm include a tool
1126 to read GSM data from a software defined radio like a DVB-T USB stick
1127 and other software defined radios, decode them and inject them into a
1128 network device on your Linux machine (using the loopback device by
1129 default). This proved to work just fine, and I&#39;ve been testing the
1130 collector for a few days now.&lt;/p&gt;
1131
1132 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
1133
1134 &lt;ol&gt;
1135
1136 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
1137
1138 &lt;li&gt;build and install the gr-gsm package available from
1139 &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;
1140
1141 &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;
1142
1143 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
1144 where it was started is filled with a stream of text (meaning you
1145 found a GSM station).&lt;/li&gt;
1146
1147 &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;
1148
1149 &lt;/ol&gt;
1150
1151 &lt;p&gt;To make it even easier in the future to get this sniffer up and
1152 running, I decided to package
1153 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
1154 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
1155 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
1156 Luckily the gnuradio maintainer has promised to help me, as I do not
1157 know much about gnuradio stuff yet.&lt;/p&gt;
1158
1159 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
1160 commercial tools like
1161 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
1162 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
1163 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
1164 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
1165 more people realise how their whereabouts when carrying a cell phone
1166 is easily tracked. Seeing the data flow on the screen, realizing that
1167 I live close to a police station and knowing that the police is also
1168 wearing cell phones, I wonder how hard it would be for criminals to
1169 track the position of the police officers to discover when there are
1170 police near by, or for foreign military forces to track the location
1171 of the Norwegian military forces, or for anyone to track the location
1172 of government officials...&lt;/p&gt;
1173
1174 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
1175 script mentioned above is only a fraction of the data broadcasted on
1176 the GSM network. It will only collect one frequency at the time,
1177 while a typical phone will be using several frequencies, and not all
1178 phones will be using the frequencies tracked by the grgsm_livemod
1179 program. Also, there is a lot of radio chatter being ignored by the
1180 simple_IMSI-catcher script, which would be collected by extending the
1181 parser code. I wonder if gr-gsm can be set up to listen to more than
1182 one frequency?&lt;/p&gt;
1183 </description>
1184 </item>
1185
1186 <item>
1187 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
1188 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
1189 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
1190 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
1191 <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;
1192
1193 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
1194 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1195 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
1196 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
1197 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
1198 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
1199 price. The book is also available for download in electronic form as
1200 PDF, EPUB and Mobipocket, as can be
1201 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
1202 as a web page&lt;/a&gt;.&lt;/p&gt;
1203
1204 &lt;p&gt;This is the second book I publish (the first was the book
1205 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
1206 in
1207 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
1208 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
1209 and
1210 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
1211 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
1212 project. I hope
1213 &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
1214 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
1215 </description>
1216 </item>
1217
1218 <item>
1219 <title>Når nynorskoversettelsen svikter til eksamen...</title>
1220 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
1221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
1222 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
1223 <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
1224 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
1225 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
1226 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
1227 på om den fri oversetterløsningen
1228 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
1229 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
1230
1231 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
1232
1233 &lt;blockquote&gt;
1234 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1235 rolle og muligheter til å håndtere internasjonale utfordringer, som
1236 for eksempel flykningekrisen.&lt;/p&gt;
1237
1238 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1239 på temaet:&lt;/p&gt;
1240 &lt;ol&gt;
1241 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
1242 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
1243 &lt;/ol&gt;
1244
1245 &lt;/blockquote&gt;
1246
1247 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
1248
1249 &lt;blockquote&gt;
1250 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1251 andre aktørar og høve til å handtera internasjonale utfordringar, som
1252 til dømes *flykningekrisen.&lt;/p&gt;
1253
1254 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
1255 temaet:&lt;/p&gt;
1256
1257 &lt;ol&gt;
1258 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
1259 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
1260 &lt;/ol&gt;
1261
1262 &lt;/blockquote&gt;
1263
1264 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
1265 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1266 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1267 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
1268 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
1269 det er kanskje flisespikking. Det understreker vel bare at det alltid
1270 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
1271 </description>
1272 </item>
1273
1274 <item>
1275 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
1276 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
1277 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
1278 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
1279 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
1280 computers at the time, I often needed a way to detect if the machine
1281 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
1282 file or directory affected by the hang, the process (and possibly the
1283 shell) will hang too. So you want to be able to detect this without
1284 risking the detection process getting stuck too. It has not been
1285 obvious how to do this. When the hang has lasted a while, it is
1286 possible to find messages like these in dmesg:&lt;/p&gt;
1287
1288 &lt;p&gt;&lt;blockquote&gt;
1289 nfs: server nfsserver not responding, still trying
1290 &lt;br&gt;nfs: server nfsserver OK
1291 &lt;/blockquote&gt;&lt;/p&gt;
1292
1293 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
1294 be sure looking in dmesg is going to work. If there are lots of other
1295 messages in dmesg the lines might have rotated out of site before they
1296 are noticed.&lt;/p&gt;
1297
1298 &lt;p&gt;While reading through the nfs client implementation in linux kernel
1299 code, I came across some statistics that seem to give a way to detect
1300 it. The om_timeouts sunrpc value in the kernel will increase every
1301 time the above log entry is inserted into dmesg. And after digging a
1302 bit further, I discovered that this value show up in
1303 /proc/self/mountstats on Linux.&lt;/p&gt;
1304
1305 &lt;p&gt;The mountstats content seem to be shared between files using the
1306 same file system context, so it is enough to check one of the
1307 mountstats files to get the state of the mount point for the machine.
1308 I assume this will not show lazy umounted NFS points, nor NFS mount
1309 points in a different process context (ie with a different filesystem
1310 view), but that does not worry me.&lt;/p&gt;
1311
1312 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
1313
1314 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1315 [...]
1316 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1317 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
1318 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
1319 age: 7863311
1320 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
1321 sec: flavor=1,pseudoflavor=1
1322 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
1323 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1324 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
1325 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1326 per-op statistics
1327 NULL: 0 0 0 0 0 0 0 0
1328 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1329 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
1330 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1331 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1332 READLINK: 125 125 0 20472 18620 0 1112 1118
1333 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1334 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1335 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
1336 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
1337 SYMLINK: 903 903 0 233428 245488 6 5865 5917
1338 MKNOD: 80 80 0 20148 21760 0 299 304
1339 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
1340 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
1341 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
1342 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
1343 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1344 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1345 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
1346 FSINFO: 2 2 0 232 328 0 1 1
1347 PATHCONF: 1 1 0 116 140 0 0 0
1348 COMMIT: 0 0 0 0 0 0 0 0
1349
1350 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1351 [...]
1352 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1353
1354 &lt;p&gt;The key number to look at is the third number in the per-op list.
1355 It is the number of NFS timeouts experiences per file system
1356 operation. Here 22 write timeouts and 5 access timeouts. If these
1357 numbers are increasing, I believe the machine is experiencing NFS
1358 hang. Unfortunately the timeout value do not start to increase right
1359 away. The NFS operations need to time out first, and this can take a
1360 while. The exact timeout value depend on the setup. For example the
1361 defaults for TCP and UDP mount points are quite different, and the
1362 timeout value is affected by the soft, hard, timeo and retrans NFS
1363 mount options.&lt;/p&gt;
1364
1365 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
1366 Enterprise Linux for getting the timeout count is to peek in /proc/.
1367 But according to
1368 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
1369 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
1370 command can be used to get these timeout values. But this do not work
1371 on Linux, as far as I can tell. I
1372 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
1373 but have not seen any replies yet.&lt;/p&gt;
1374
1375 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
1376 experiencing NFS hangs? Is there a way to detect which processes are
1377 affected? Is there a way to get the NFS mount going quickly once the
1378 network problem causing the NFS hang has been cleared? I would very
1379 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
1380 </description>
1381 </item>
1382
1383 <item>
1384 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
1385 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
1386 <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>
1387 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
1388 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
1389 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1390 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
1391 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1392 we are working on the proof reading to ensure consistent language and
1393 use of correct computer science terms. The plan is to make the book
1394 available on paper, as well as in electronic form. For that to
1395 happen, the proof reading must be completed and all the figures need
1396 to be translated. If you want to help out, get in touch.&lt;/p&gt;
1397
1398 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
1399
1400 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
1401 pages) of the book created every morning is available for
1402 proofreading. If you find any errors, please
1403 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
1404 Weblate and correct the error&lt;/a&gt;. The
1405 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
1406 of the translation including figures&lt;/a&gt; is a useful source for those
1407 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
1408 </description>
1409 </item>
1410
1411 <item>
1412 <title>Unlimited randomness with the ChaosKey?</title>
1413 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
1414 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
1415 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
1416 <description>&lt;p&gt;A few days ago I ordered a small batch of
1417 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
1418 USB dongle for generating entropy created by Bdale Garbee and Keith
1419 Packard. Yesterday it arrived, and I am very happy to report that it
1420 work great! According to its designers, to get it to work out of the
1421 box, you need the Linux kernel version 4.1 or later. I tested on a
1422 Debian Stretch machine (kernel version 4.9), and there it worked just
1423 fine, increasing the available entropy very quickly. I wrote a small
1424 test oneliner to test. It first print the current entropy level,
1425 drain /dev/random, and then print the entropy level for five seconds.
1426 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
1427
1428 &lt;blockquote&gt;&lt;pre&gt;
1429 % cat /proc/sys/kernel/random/entropy_avail; \
1430 dd bs=1M if=/dev/random of=/dev/null count=1; \
1431 for n in $(seq 1 5); do \
1432 cat /proc/sys/kernel/random/entropy_avail; \
1433 sleep 1; \
1434 done
1435 300
1436 0+1 oppføringer inn
1437 0+1 oppføringer ut
1438 28 byte kopiert, 0,000264565 s, 106 kB/s
1439 4
1440 8
1441 12
1442 17
1443 21
1444 %
1445 &lt;/pre&gt;&lt;/blockquote&gt;
1446
1447 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
1448 application requiring random bits (like a HTTPS enabled web server)
1449 will halt and wait for more entrpy. And here is the situation with
1450 the ChaosKey inserted:&lt;/p&gt;
1451
1452 &lt;blockquote&gt;&lt;pre&gt;
1453 % cat /proc/sys/kernel/random/entropy_avail; \
1454 dd bs=1M if=/dev/random of=/dev/null count=1; \
1455 for n in $(seq 1 5); do \
1456 cat /proc/sys/kernel/random/entropy_avail; \
1457 sleep 1; \
1458 done
1459 1079
1460 0+1 oppføringer inn
1461 0+1 oppføringer ut
1462 104 byte kopiert, 0,000487647 s, 213 kB/s
1463 433
1464 1028
1465 1031
1466 1035
1467 1038
1468 %
1469 &lt;/pre&gt;&lt;/blockquote&gt;
1470
1471 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
1472 someone want to buy one here in Norway. :)&lt;/p&gt;
1473
1474 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
1475 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
1476 recording illuminating&lt;/a&gt;. It explains exactly what the source of
1477 randomness is, if you are unable to spot it from the schema drawing
1478 available from the ChaosKey web site linked at the start of this blog
1479 post.&lt;/p&gt;
1480 </description>
1481 </item>
1482
1483 <item>
1484 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
1485 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
1486 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
1487 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
1488 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
1489 web servers, and who own the network equipment it is flowing through?
1490 It is possible to get a glimpse of this from using traceroute, but it
1491 is hard to find all the details. Many years ago, I wrote a system to
1492 map the Norwegian Internet (trying to figure out if our plans for a
1493 network game service would get low enough latency, and who we needed
1494 to talk to about setting up game servers close to the users. Back
1495 then I used traceroute output from many locations (I asked my friends
1496 to run a script and send me their traceroute output) to create the
1497 graph and the map. The output from traceroute typically look like
1498 this:
1499
1500 &lt;p&gt;&lt;pre&gt;
1501 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
1502 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
1503 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
1504 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
1505 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
1506 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
1507 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
1508 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
1509 8 * * *
1510 9 * * *
1511 [...]
1512 &lt;/pre&gt;&lt;/p&gt;
1513
1514 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
1515 network equipment involved in getting the data traffic from me to the
1516 www.stortinget.no server, and how long it took in milliseconds for a
1517 package to reach the equipment and return to me. Three packages are
1518 sent, and some times the packages do not follow the same path. This
1519 is shown for hop 5, where three different IP addresses replied to the
1520 traceroute request.&lt;/p&gt;
1521
1522 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
1523 implementations I use are traceroute (using ICMP packages) mtr (can do
1524 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1525 traceroute and a lot of other capabilities). All of them are easily
1526 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
1527
1528 &lt;p&gt;This time around, I wanted to know the geographic location of
1529 different route points, to visualize how visiting a web page spread
1530 information about the visit to a lot of servers around the globe. The
1531 background is that a web site today often will ask the browser to get
1532 from many servers the parts (for example HTML, JSON, fonts,
1533 JavaScript, CSS, video) required to display the content. This will
1534 leak information about the visit to those controlling these servers
1535 and anyone able to peek at the data traffic passing by (like your ISP,
1536 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
1537
1538 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
1539 www.stortinget.no. It is read daily by all members of parliament and
1540 their staff, as well as political journalists, activits and many other
1541 citizens of Norway. A visit to the www.stortinget.no web site will
1542 ask your browser to contact 8 other servers: ajax.googleapis.com,
1543 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1544 stats.g.doubleclick.net, www.google-analytics.com,
1545 www.googletagmanager.com and www.netigate.se. I extracted this by
1546 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
1547 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1548 render the page (in HAR format using
1549 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
1550 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
1551 to do this). My goal is to visualize network traces to all IP
1552 addresses behind these DNS names, do show where visitors personal
1553 information is spread when visiting the page.&lt;/p&gt;
1554
1555 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
1556 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;
1557
1558 &lt;p&gt;When I had a look around for options, I could not find any good
1559 free software tools to do this, and decided I needed my own traceroute
1560 wrapper outputting KML based on locations looked up using GeoIP. KML
1561 is easy to work with and easy to generate, and understood by several
1562 of the GIS tools I have available. I got good help from by NUUG
1563 colleague Anders Einar with this, and the result can be seen in
1564 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
1565 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
1566 free GeoIP databases I could find (and the for-pay databases my
1567 friends had access to) is not up to the task. The IP addresses of
1568 central Internet infrastructure would typically be placed near the
1569 controlling companies main office, and not where the router is really
1570 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
1571 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
1572
1573 &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
1574 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;
1575
1576 &lt;p&gt;I also had a look at the visual traceroute graph created by
1577 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1578 showing IP network ownership (aka AS owner) for the IP address in
1579 question.
1580 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1581 graph display a lot of useful information about the traceroute in SVG
1582 format&lt;/a&gt;, and give a good indication on who control the network
1583 equipment involved, but it do not include geolocation. This graph
1584 make it possible to see the information is made available at least for
1585 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1586 3 Communications and NetDNA.&lt;/p&gt;
1587
1588 &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
1589 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;
1590
1591 &lt;p&gt;In the process, I came across the
1592 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1593 Salim Gasmi. Its methology of combining guesses based on DNS names,
1594 various location databases and finally use latecy times to rule out
1595 candidate locations seemed to do a very good job of guessing correct
1596 geolocation. But it could only do one trace at the time, did not have
1597 a sensor in Norway and did not make the geolocations easily available
1598 for postprocessing. So I contacted the developer and asked if he
1599 would be willing to share the code (he refused until he had time to
1600 clean it up), but he was interested in providing the geolocations in a
1601 machine readable format, and willing to set up a sensor in Norway. So
1602 since yesterday, it is possible to run traces from Norway in this
1603 service thanks to a sensor node set up by
1604 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1605 trace in KML format for further processing.&lt;/p&gt;
1606
1607 &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
1608 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;
1609
1610 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1611 Denmark, Germany, Holland and Ireland. Plenty of places where the
1612 Snowden confirmations verified the traffic is read by various actors
1613 without your best interest as their top priority.&lt;/p&gt;
1614
1615 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1616 over all the hosts behind the urls imported by www.stortinget.no and
1617 ask for the KML file from GeoTraceroute, and create a combined KML
1618 file with all the traces (unfortunately only one of the IP addresses
1619 behind the DNS name is traced this time. To get them all, one would
1620 have to request traces using IP number instead of DNS names from
1621 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1622
1623 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1624 the IP traffic moves and who control the boxes involved in moving it.
1625 And every time the link crosses for example the Swedish border, we can
1626 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1627 Britain and NSA in USA and cables around the globe. (Hm, what should
1628 we tell them? :) Keep that in mind if you ever send anything
1629 unencrypted over the Internet.&lt;/p&gt;
1630
1631 &lt;p&gt;PS: KML files are drawn using
1632 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1633 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1634 Marble. There are heaps of other options too.&lt;/p&gt;
1635
1636 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1637 activities, please send Bitcoin donations to my address
1638 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1639 </description>
1640 </item>
1641
1642 <item>
1643 <title>Appstream just learned how to map hardware to packages too!</title>
1644 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1646 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1647 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1648 readers probably know, I have been working on the
1649 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1650 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1651 it easier for users to figure out what to install to get a given piece
1652 of hardware to work in Debian, and a key part of this system is a way
1653 to map hardware to packages. Isenkram have its own mapping database,
1654 and also uses data provided by each package using the AppStream
1655 metadata format. And today,
1656 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1657 Debian learned to look up hardware the same way Isenkram is doing it,
1658 ie using fnmatch():&lt;/p&gt;
1659
1660 &lt;p&gt;&lt;pre&gt;
1661 % appstreamcli what-provides modalias \
1662 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1663 Identifier: pymissile [generic]
1664 Name: pymissile
1665 Summary: Control original Striker USB Missile Launcher
1666 Package: pymissile
1667 % appstreamcli what-provides modalias usb:v0694p0002d0000
1668 Identifier: libnxt [generic]
1669 Name: libnxt
1670 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1671 Package: libnxt
1672 ---
1673 Identifier: t2n [generic]
1674 Name: t2n
1675 Summary: Simple command-line tool for Lego NXT
1676 Package: t2n
1677 ---
1678 Identifier: python-nxt [generic]
1679 Name: python-nxt
1680 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1681 Package: python-nxt
1682 ---
1683 Identifier: nbc [generic]
1684 Name: nbc
1685 Summary: C compiler for LEGO Mindstorms NXT bricks
1686 Package: nbc
1687 %
1688 &lt;/pre&gt;&lt;/p&gt;
1689
1690 &lt;p&gt;A similar query can be done using the combined AppStream and
1691 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1692
1693 &lt;p&gt;&lt;pre&gt;
1694 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1695 pymissile
1696 % isenkram-lookup usb:v0694p0002d0000
1697 libnxt
1698 nbc
1699 python-nxt
1700 t2n
1701 %
1702 &lt;/pre&gt;&lt;/p&gt;
1703
1704 &lt;p&gt;You can find modalias values relevant for your machine using
1705 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1706
1707 &lt;p&gt;If you want to make this system a success and help Debian users
1708 make the most of the hardware they have, please
1709 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1710 AppStream metadata for your package following the guidelines&lt;/a&gt;
1711 documented in the wiki. So far only 11 packages provide such
1712 information, among the several hundred hardware specific packages in
1713 Debian. The Isenkram database on the other hand contain 101 packages,
1714 mostly related to USB dongles. Most of the packages with hardware
1715 mapping in AppStream are LEGO Mindstorms related, because I have, as
1716 part of my involvement in
1717 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1718 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1719 complete set of packages in Debian for that particular hardware. The
1720 team also got a nice Christmas present today. The
1721 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1722 package&lt;/a&gt; made it into Debian. With this package in place, it is
1723 now possible to use the LEGO Mindstorms NXT unit with only free
1724 software, as the nxt-firmware package contain the source and firmware
1725 binaries for the NXT brick.&lt;/p&gt;
1726
1727 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1728 activities, please send Bitcoin donations to my address
1729 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1730 </description>
1731 </item>
1732
1733 <item>
1734 <title>Isenkram updated with a lot more hardware-package mappings</title>
1735 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1736 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1737 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1738 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1739 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1740 and install packages to get your hardware dongles to work, is still
1741 going strong. It is a system to look up the hardware present on or
1742 connected to the current system, and map the hardware to Debian
1743 packages. It can either be done using the tools in isenkram-cli or
1744 using the user space daemon in the isenkram package. The latter will
1745 notify you, when inserting new hardware, about what packages to
1746 install to get the dongle working. It will even provide a button to
1747 click on to ask packagekit to install the packages.&lt;/p&gt;
1748
1749 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1750
1751 &lt;p&gt;&lt;pre&gt;
1752 % isenkram-lookup
1753 bluez
1754 cheese
1755 ethtool
1756 fprintd
1757 fprintd-demo
1758 gkrellm-thinkbat
1759 hdapsd
1760 libpam-fprintd
1761 pidgin-blinklight
1762 thinkfan
1763 tlp
1764 tp-smapi-dkms
1765 tp-smapi-source
1766 tpb
1767 %
1768 &lt;/pre&gt;&lt;/p&gt;
1769
1770 &lt;p&gt;It can also list the firware package providing firmware requested
1771 by the load kernel modules, which in my case is an empty list because
1772 I have all the firmware my machine need:
1773
1774 &lt;p&gt;&lt;pre&gt;
1775 % /usr/sbin/isenkram-autoinstall-firmware -l
1776 info: did not find any firmware files requested by loaded kernel modules. exiting
1777 %
1778 &lt;/pre&gt;&lt;/p&gt;
1779
1780 &lt;p&gt;The last few days I had a look at several of the around 250
1781 packages in Debian with udev rules. These seem like good candidates
1782 to install when a given hardware dongle is inserted, and I found
1783 several that should be proposed by isenkram. I have not had time to
1784 check all of them, but am happy to report that now there are 97
1785 packages packages mapped to hardware by Isenkram. 11 of these
1786 packages provide hardware mapping using AppStream, while the rest are
1787 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1788
1789 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1790 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1791 support using AppStream, for everyone to use:&lt;/p&gt;
1792
1793 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1794 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1795 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1796 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1797 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1798 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1799 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1800 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1801 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1802 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1803 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1804 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1805 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1806 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1807 pcscd, pidgin-blinklight, printer-driver-splix,
1808 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1809 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1810 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1811 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1812 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1813 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1814 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1815 xserver-xorg-video-vmware, yubikey-personalization and
1816 zd1211-firmware&lt;/p&gt;
1817
1818 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1819 bug report against the isenkram-cli package, and ask the package
1820 maintainer to
1821 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1822 metadata according to the guidelines&lt;/a&gt; to provide the information
1823 for everyone. In time, I hope to get rid of the isenkram specific
1824 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1825
1826 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1827 much hardware, and suggest that the package with with any ethernet
1828 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1829 the details. I hope the maintainer find time to address it soon. In
1830 the mean time I provide an override in isenkram.&lt;/p&gt;
1831 </description>
1832 </item>
1833
1834 <item>
1835 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1836 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1838 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1839 <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;
1840
1841 &lt;p&gt;In my early years, I played
1842 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1843 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1844 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1845 original Elite game was available on Commodore 64 and the IBM PC
1846 edition I played had a 64 KB executable. I am still impressed today
1847 that the authors managed to squeeze both a 3D engine and details about
1848 more than 2000 planet systems across 7 galaxies into a binary so
1849 small.&lt;/p&gt;
1850
1851 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1852 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1853 really have time to test it properly until a few days ago. It was
1854 great to discover that my old knowledge about trading routes were
1855 still valid. But my fighting and flying abilities were gone, so I had
1856 to retrain to be able to dock on a space station. And I am still not
1857 able to make much resistance when I am attacked by pirates, so I
1858 bougth and mounted the most powerful laser in the rear to be able to
1859 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1860
1861 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1862 everything on my own, and I had long lists of prices seen on different
1863 planets to be able to decide where to trade what. This time I had the
1864 advantages of the
1865 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1866 where information about each planet is easily available with common
1867 price ranges and suggested trading routes. This improved my ability
1868 to earn money and I have been able to earn enough to buy a lot of
1869 useful equipent in a few days. I believe I originally played for
1870 months before I could get a docking computer, while now I could get it
1871 after less then a week.&lt;/p&gt;
1872
1873 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1874 space, you should try out Oolite. It is available for Linux, MacOSX
1875 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1876
1877 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1878 activities, please send Bitcoin donations to my address
1879 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1880 </description>
1881 </item>
1882
1883 <item>
1884 <title>Quicker Debian installations using eatmydata</title>
1885 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1887 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1888 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1889 installation system, observing how using
1890 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1891 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1892 speedup around 20-40 percent for Debian Edu, where we install around
1893 1000 packages from within the installer. The eatmydata package
1894 provide a way to disable/delay file system flushing. This is a bit
1895 risky in the general case, as files that should be stored on disk will
1896 stay only in memory a bit longer than expected, causing problems if a
1897 machine crashes at an inconvenient time. But for an installation, if
1898 the machine crashes during installation the process is normally
1899 restarted, and avoiding disk operations as much as possible to speed
1900 up the process make perfect sense.
1901
1902 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1903 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1904 but did not have time to push it any further. But a few months ago I
1905 picked it up again and worked with the libeatmydata package maintainer
1906 Mattia Rizzolo to make it easier for everyone to get this installation
1907 speedup in Debian. Thanks to our cooperation There is now an
1908 eatmydata-udeb package in Debian testing and unstable, and simply
1909 enabling/installing it in debian-installer (d-i) is enough to get the
1910 quicker installations. It can be enabled using preseeding. The
1911 following untested kernel argument should do the trick:&lt;/p&gt;
1912
1913 &lt;blockquote&gt;&lt;pre&gt;
1914 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1915 &lt;/pre&gt;&lt;/blockquote&gt;
1916
1917 &lt;p&gt;This should ask d-i to install the package inside the d-i
1918 environment early in the installation sequence. Having it installed
1919 in d-i in turn will make sure the relevant scripts are called just
1920 after debootstrap filled /target/ with the freshly installed Debian
1921 system to configure apt to run dpkg with eatmydata. This is enough to
1922 speed up the installation process. There is a proposal to
1923 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1924 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1925 tested its impact.&lt;/p&gt;
1926
1927 </description>
1928 </item>
1929
1930 <item>
1931 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1932 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1933 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1934 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1935 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1936 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1937 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1938 elever over det ganske land skal levere inn hvert år. Det mange ikke
1939 vet er at selv om de kommersielle alternativene
1940 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1941 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1942 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1943 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1944 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1945 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1946 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1947 nynorsk, og få den automatoversatt til det andre skriftspråket.
1948 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1949 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1950 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1951 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1952 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1953 teksten din i webskjemaet der.
1954
1955 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1956 teknologien kan du enten installere pakken
1957 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1958 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1959 api.apertium.org. Se
1960 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1961 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1962 denne teksten som ble skrevet på bokmål over maskinoversatt til
1963 nynorsk.&lt;/p&gt;
1964
1965 &lt;hr/&gt;
1966
1967 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1968 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1969 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1970 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1971 veit er at sjølv om dei kommersielle alternativa
1972 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1973 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1974 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1975 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1976 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1977 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1978 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1979 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1980 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1981 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1982 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1983 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1984 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1985 teksta di i *webskjemaet der.
1986
1987 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1988 teknologien kan du anten installera pakken
1989 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1990 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1991 *api.*apertium.org. Sjå
1992 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1993 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1994 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1995 nynorsk.&lt;/p&gt;
1996 </description>
1997 </item>
1998
1999 <item>
2000 <title>Coz profiler for multi-threaded software is now in Debian</title>
2001 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
2002 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
2003 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
2004 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
2005 profiler able to run benchmarking experiments on the instrumented
2006 multi-threaded program, finally
2007 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
2008 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
2009 months since
2010 &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
2011 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
2012 it suitable for Debian. There are still issues with clang
2013 compatibility, inline assembly only working x86 and minimized
2014 JavaScript libraries.&lt;/p&gt;
2015
2016 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
2017
2018 &lt;p&gt;&lt;blockquote&gt;
2019 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
2020 &lt;/blockquote&gt;&lt;/p&gt;
2021
2022 &lt;p&gt;This will produce a profile.coz file in the current working
2023 directory with the profiling information. This is then given to a
2024 JavaScript application provided in the package and available from
2025 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
2026 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
2027
2028 &lt;p&gt;&lt;blockquote&gt;
2029 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
2030 &lt;/blockquote&gt;&lt;/p&gt;
2031
2032 &lt;p&gt;See the project home page and the
2033 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
2034 ;login: article on Coz&lt;/a&gt; for more information on how it is
2035 working.&lt;/p&gt;
2036 </description>
2037 </item>
2038
2039 <item>
2040 <title>My own self balancing Lego Segway</title>
2041 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
2042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
2043 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
2044 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
2045 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
2046 present. It had been on my wishlist for a while, because I wanted to
2047 build a Segway like balancing lego robot. I had already built
2048 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
2049 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
2050 NXT kit as the balance sensor, but it was not working very well. It
2051 could balance for a while, but was very sensitive to the light
2052 condition in the room and the reflective properties of the surface and
2053 would fall over after a short while. I wanted something more robust,
2054 and had
2055 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
2056 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
2057 wishlist for some years before it suddenly showed up as a gift from my
2058 loved ones. :)&lt;/p&gt;
2059
2060 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
2061 since then. But that changed some days ago, when I was searching for
2062 lego segway information and came across a recipe from HiTechnic for
2063 building
2064 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
2065 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
2066 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
2067 code&lt;/a&gt; was included, so it was just a question of putting it all
2068 together. And thanks to the great work of many Debian developers, the
2069 compiler needed to build the source for the NXT is already included in
2070 Debian, so I was read to go in less than an hour. The resulting robot
2071 do not look very impressive in its simplicity:&lt;/p&gt;
2072
2073 &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;
2074
2075 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
2076 design from HiTechnic, I had to comment out the last task
2077 (taskControl). I simply placed /* and */ around it get the program
2078 working without that sensor present. Now it balances just fine until
2079 the battery status run low:&lt;/p&gt;
2080
2081 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
2082 &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;
2083 &lt;/video&gt;&lt;/p&gt;
2084
2085 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
2086 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
2087
2088 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
2089 they need to work with LEGO in Debian and all our derivative
2090 distributions like Ubuntu, check out
2091 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
2092 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
2093 RCX and NXT controller (no EV3), and would like to make sure the
2094 Debian tools needed to program the systems I own work as they
2095 should.&lt;/p&gt;
2096 </description>
2097 </item>
2098
2099 <item>
2100 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
2101 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
2102 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
2103 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
2104 <description>&lt;p&gt;In July
2105 &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
2106 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
2107 the ability to receive SMS messages (aka without a cell phone). It is
2108 time to share some experiences and provide an updated setup.&lt;/p&gt;
2109
2110 &lt;p&gt;The Signal app have worked fine for several months now, and I use
2111 it regularly to chat with my loved ones. I had a major snag at the
2112 end of my summer vacation, when the the app completely forgot my
2113 setup, identity and keys. The reason behind this major mess was
2114 running out of disk space. To avoid that ever happening again I have
2115 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
2116 roll back to an earlier version if the files are wiped by mistake. I
2117 had to use it once after introducing the git backup. When rolling
2118 back to an earlier version, one need to use the &#39;reset session&#39; option
2119 in Signal to get going, and notify the people you talk with about the
2120 problem. I assume there is some sequence number tracking in the
2121 protocol to detect rollback attacks. The git repository is rather big
2122 (674 MiB so far), but I have not tried to figure out if some of the
2123 content can be added to a .gitignore file due to lack of spare
2124 time.&lt;/p&gt;
2125
2126 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
2127 make it impossible to send messages using Signal. I could still
2128 receive them, but had to patch the code with a new timestamp to send.
2129 I believe the timeout is added by the developers to force people to
2130 upgrade to the latest version of the app, even when there is no
2131 protocol changes, to reduce the version skew among the user base and
2132 thus try to keep the number of support requests down.&lt;/p&gt;
2133
2134 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
2135 making the old patch fail to apply cleanly. Below is an updated
2136 patch, including the shell wrapper I use to start Signal. The
2137 original version required a new user to locate the JavaScript console
2138 and call a function from there. I got help from a friend with more
2139 JavaScript knowledge than me to modify the code to provide a GUI
2140 button instead. This mean that to get started you just need to run
2141 the wrapper and click the &#39;Register without mobile phone&#39; to get going
2142 now. I&#39;ve also modified the timeout code to always set it to 90 days
2143 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
2144
2145 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
2146
2147 &lt;ol&gt;
2148
2149 &lt;li&gt;First, install required packages to get the source code and the
2150 browser you need. Signal only work with Chrome/Chromium, as far as I
2151 know, so you need to install it.
2152
2153 &lt;pre&gt;
2154 apt install git tor chromium
2155 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2156 &lt;/pre&gt;&lt;/li&gt;
2157
2158 &lt;li&gt;Modify the source code using command listed in the the patch
2159 block below.&lt;/li&gt;
2160
2161 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
2162 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
2163
2164 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
2165 number you can receive calls to the next minute, receive the
2166 verification code and enter it into the form field and press
2167 &#39;Register&#39;. Note, the phone number you use will be user Signal
2168 username, ie the way others can find you on Signal.&lt;/li&gt;
2169
2170 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
2171 not show up in the contact list until you restart Signal, and there is
2172 no way to assign names to Contacts. There is also no way to create or
2173 update chat groups. I suspect this is because the web app do not have
2174 a associated contact database.&lt;/li&gt;
2175
2176 &lt;/ol&gt;
2177
2178 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
2179 main author moxie0 reject federation and accept dependencies to major
2180 corporations like Google (part of the code is fetched from Google) and
2181 Amazon (the central coordination point is owned by Amazon). See for
2182 example
2183 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
2184 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
2185 view on these issues. But the network effect is strong in this case,
2186 and several of the people I want to communicate with already use
2187 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
2188 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
2189 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
2190 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
2191 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
2192 working on Debian Stable.&lt;/p&gt;
2193
2194 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
2195 working. It switch to the production servers, disable to timeout,
2196 make registration easier and add the shell wrapper:&lt;/p&gt;
2197
2198 &lt;pre&gt;
2199 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
2200 diff --git a/js/background.js b/js/background.js
2201 index 24b4c1d..579345f 100644
2202 --- a/js/background.js
2203 +++ b/js/background.js
2204 @@ -33,9 +33,9 @@
2205 });
2206 });
2207
2208 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2209 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
2210 var SERVER_PORTS = [80, 4433, 8443];
2211 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2212 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2213 var messageReceiver;
2214 window.getSocketStatus = function() {
2215 if (messageReceiver) {
2216 diff --git a/js/expire.js b/js/expire.js
2217 index 639aeae..beb91c3 100644
2218 --- a/js/expire.js
2219 +++ b/js/expire.js
2220 @@ -1,6 +1,6 @@
2221 ;(function() {
2222 &#39;use strict&#39;;
2223 - var BUILD_EXPIRATION = 0;
2224 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
2225
2226 window.extension = window.extension || {};
2227
2228 diff --git a/js/views/install_view.js b/js/views/install_view.js
2229 index 7816f4f..1d6233b 100644
2230 --- a/js/views/install_view.js
2231 +++ b/js/views/install_view.js
2232 @@ -38,7 +38,8 @@
2233 return {
2234 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
2235 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
2236 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
2237 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
2238 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
2239 };
2240 },
2241 clearQR: function() {
2242 diff --git a/options.html b/options.html
2243 index dc0f28e..8d709f6 100644
2244 --- a/options.html
2245 +++ b/options.html
2246 @@ -14,7 +14,10 @@
2247 &amp;lt;div class=&#39;nav&#39;&gt;
2248 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
2249 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
2250 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
2251 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
2252 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
2253 +
2254 + &amp;lt;/div&gt;
2255 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
2256 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
2257 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
2258 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
2259 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
2260 @@ -0,0 +1,12 @@
2261 +#!/bin/sh
2262 +set -e
2263 +cd $(dirname $0)
2264 +mkdir -p userdata
2265 +userdata=&quot;`pwd`/userdata&quot;
2266 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
2267 + (cd $userdata &amp;&amp; git init)
2268 +fi
2269 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
2270 +exec chromium \
2271 + --proxy-server=&quot;socks://localhost:9050&quot; \
2272 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2273 EOF
2274 chmod a+rx run-signal-app
2275 &lt;/pre&gt;
2276
2277 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2278 activities, please send Bitcoin donations to my address
2279 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2280 </description>
2281 </item>
2282
2283 <item>
2284 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
2285 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
2286 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
2287 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
2288 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2289 system&lt;/a&gt; provide a practical and easy way to figure out which
2290 packages support the hardware in a given machine. The command line
2291 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
2292 convenient way to list and install packages relevant for the current
2293 hardware during system installation, both user space packages and
2294 firmware packages. The GUI background daemon on the other hand provide
2295 a pop-up proposing to install packages when a new dongle is inserted
2296 while using the computer. For example, if you plug in a smart card
2297 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
2298 that package isn&#39;t already installed, and if you plug in a USB video
2299 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
2300 cheese is currently missing. This already work just fine.&lt;/p&gt;
2301
2302 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
2303 package names. When I started no such database existed in Debian, so
2304 I made my own data set and included it with the isenkram package and
2305 made isenkram fetch the latest version of this database from git using
2306 http. This way the isenkram users would get updated package proposals
2307 as soon as I learned more about hardware related packages.&lt;/p&gt;
2308
2309 &lt;p&gt;The hardware is identified using modalias strings. The modalias
2310 design is from the Linux kernel where most hardware descriptors are
2311 made available as a strings that can be matched using filename style
2312 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2313 identifiers.&lt;/p&gt;
2314
2315 &lt;p&gt;The downside to the Isenkram specific database is that there is no
2316 information about relevant distribution / Debian version, making
2317 isenkram propose obsolete packages too. But along came AppStream, a
2318 cross distribution mechanism to store and collect metadata about
2319 software packages. When I heard about the proposal, I contacted the
2320 people involved and suggested to add a hardware matching rule using
2321 modalias strings in the specification, to be able to use AppStream for
2322 mapping hardware to packages. This idea was accepted and AppStream is
2323 now a great way for a package to announce the hardware it support in a
2324 distribution neutral way. I wrote
2325 &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
2326 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
2327 December. If you have a hardware related package in Debian, please
2328 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
2329
2330 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
2331 RCX or NXT unit, announce this support using AppStream. The effect is
2332 that when you insert such LEGO robot controller into your Debian
2333 machine, Isenkram will propose to install the packages needed to get
2334 it working. The intention is that this should allow the local user to
2335 start programming his robot controller right away without having to
2336 guess what packages to use or which permissions to fix.&lt;/p&gt;
2337
2338 &lt;p&gt;But when I sat down with my son the other day to program our NXT
2339 unit using his Debian Stretch computer, I discovered something
2340 annoying. The local console user (ie my son) did not get access to
2341 the USB device for programming the unit. This used to work, but no
2342 longer in Jessie and Stretch. After some investigation and asking
2343 around on #debian-devel, I discovered that this was because udev had
2344 changed the mechanism used to grant access to local devices. The
2345 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
2346 no longer applied, because LDAP users no longer was added to the
2347 plugdev group during login. Michael Biebl told me that this method
2348 was obsolete and the new method used ACLs instead. This was good
2349 news, as the plugdev mechanism is a mess when using a remote user
2350 directory like LDAP. Using ACLs would make sure a user lost device
2351 access when she logged out, even if the user left behind a background
2352 process which would retain the plugdev membership with the ConsoleKit
2353 setup. Armed with this knowledge I moved on to fix the access problem
2354 for the LEGO Mindstorms related packages.&lt;/p&gt;
2355
2356 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
2357 applied directly for a device, or is applied in
2358 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
2359 LEGO Mindstorms udev rules did not have a class, I decided to add the
2360 tag directly in the udev rules files included in the packages. Here
2361 is one example. For the nqc C compiler for the RCX, the
2362 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
2363
2364 &lt;p&gt;&lt;pre&gt;
2365 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
2366 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
2367 &lt;/pre&gt;&lt;/p&gt;
2368
2369 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
2370 packages using plugdev in their /lib/udev/rules.d/ files should be
2371 changed to use this tag (either directly or indirectly via
2372 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
2373 to detect this?&lt;/p&gt;
2374
2375 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
2376 It is unclear to me if the uaccess tag is an internal implementation
2377 detail like the udev-acl tag used by
2378 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
2379 indirect method is the preferred way. Michael
2380 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
2381 documentation from the systemd project&lt;/a&gt; and I hope it will make
2382 this clearer. For now I use the generic classes when they exist and
2383 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
2384 directly if no such class exist.&lt;/p&gt;
2385
2386 &lt;p&gt;To learn more about the isenkram system, please check out
2387 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2388 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2389
2390 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
2391 please join us on our IRC channel
2392 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
2393 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
2394 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
2395 list is not yet created, but we are working on it. :)&lt;/p&gt;
2396
2397 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2398 activities, please send Bitcoin donations to my address
2399 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2400 </description>
2401 </item>
2402
2403 <item>
2404 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
2405 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
2406 <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>
2407 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
2408 <description>&lt;p&gt;In April we
2409 &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
2410 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
2411 how to set up and administrate a Debian system. Today I am happy to
2412 report that the first draft is now publicly available. You can find
2413 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
2414 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
2415 eight chapters have a first draft translation, and we are working on
2416 proofreading the content. If you want to help out, please start
2417 contributing using
2418 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2419 hosted weblate project page&lt;/a&gt;, and get in touch using
2420 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2421 translators mailing list&lt;/a&gt;. Please also check out
2422 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2423 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
2424 and update weblate if you find errors.&lt;/p&gt;
2425
2426 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
2427 electronic form.&lt;/p&gt;
2428 </description>
2429 </item>
2430
2431 <item>
2432 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
2433 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
2434 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
2435 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
2436 <description>&lt;p&gt;This summer, I read a great article
2437 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
2438 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
2439 how to profile multi-threaded programs. It presented a system for
2440 profiling software by running experiences in the running program,
2441 testing how run time performance is affected by &quot;speeding up&quot; parts of
2442 the code to various degrees compared to a normal run. It does this by
2443 slowing down parallel threads while the &quot;faster up&quot; code is running
2444 and measure how this affect processing time. The processing time is
2445 measured using probes inserted into the code, either using progress
2446 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2447 can also measure unmodified code by measuring complete the program
2448 runtime and running the program several times instead.&lt;/p&gt;
2449
2450 &lt;p&gt;The project and presentation was so inspiring that I would like to
2451 get the system into Debian. I
2452 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
2453 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
2454 system ready for Debian by sending patches. The build process need to
2455 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
2456 to include the JavaScript web page used to visualize the collected
2457 profiling information included in the source package.
2458 But I expect that should work out fairly soon.&lt;/p&gt;
2459
2460 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
2461 on a binary with debug symbols available, start the program like this:
2462
2463 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2464 coz run --- program-to-run
2465 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2466
2467 &lt;p&gt;This will create a text file profile.coz with the instrumentation
2468 information. To show what part of the code affect the performance
2469 most, use a web browser and either point it to
2470 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
2471 or use the copy from git (in the gh-pages branch). Check out this web
2472 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
2473 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
2474 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2475 code, rebuild and run the profiler. This allow coz to do more
2476 targeted experiments.&lt;/p&gt;
2477
2478 &lt;p&gt;A video published by ACM
2479 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
2480 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
2481 from the 25th Symposium on Operating Systems Principles available
2482 titled
2483 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
2484 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
2485
2486 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
2487 for Coz is available from github. It will only build with clang
2488 because it uses a
2489 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
2490 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
2491 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
2492 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
2493
2494 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
2495 of software in Debian. I would very much like some help with the
2496 packaging effort, as I lack the in depth knowledge on how to package
2497 C++ libraries.&lt;/p&gt;
2498 </description>
2499 </item>
2500
2501 <item>
2502 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
2503 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
2504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
2505 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
2506 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2507 to be a slight challenge. Here is the recipe if I ever need to do it
2508 again. It all started by me wanting to try the recipe to set up
2509 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
2510 hardened Android installation&lt;/a&gt; from the Tor project blog on a
2511 device I had access to. It is a old mobile phone with a broken
2512 microphone The initial idea had been to just
2513 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
2514 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
2515 until a few days ago.&lt;/p&gt;
2516
2517 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
2518 loader (press volume down and power at the same time), (2) select
2519 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
2520 machine, (4) request the device identifier token by running &#39;fastboot
2521 oem get_identifier_token&#39;, (5) request the device unlocking key using
2522 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
2523 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
2524
2525 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
2526 or newer, and the device I was working on had 2.00.0027. This
2527 apparently can be easily fixed by downloading a Windows program and
2528 running it on your Windows machine, if you accept the terms Microsoft
2529 require you to accept to use Windows - which I do not. So I had to
2530 come up with a different approach. I got a lot of help from AndyCap
2531 on #nuug, and would not have been able to get this working without
2532 him.&lt;/p&gt;
2533
2534 &lt;p&gt;First I needed to extract the hboot firmware from
2535 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
2536 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
2537 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
2538 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
2539 recognise the file format, but unruu worked and extracted rom.zip,
2540 containing the new hboot firmware and a text file describing which
2541 devices it would work for.&lt;/p&gt;
2542
2543 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
2544 followed some instructions
2545 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
2546 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
2547 machine with Debian testing:&lt;/p&gt;
2548
2549 &lt;p&gt;&lt;pre&gt;
2550 adb reboot-bootloader
2551 fastboot oem rebootRUU
2552 fastboot flash zip rom.zip
2553 fastboot flash zip rom.zip
2554 fastboot reboot
2555 &lt;/pre&gt;&lt;/p&gt;
2556
2557 &lt;p&gt;The flash command apparently need to be done twice to take effect,
2558 as the first is just preparations and the second one do the flashing.
2559 The adb command is just to get to the boot loader menu, so turning the
2560 device on while holding volume down and the power button should work
2561 too.&lt;/p&gt;
2562
2563 &lt;p&gt;With the new hboot version in place I could start following the
2564 instructions on the HTC developer web site. I got the device token
2565 like this:&lt;/p&gt;
2566
2567 &lt;p&gt;&lt;pre&gt;
2568 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
2569 &lt;/pre&gt;
2570
2571 &lt;p&gt;And once I got the unlock code via email, I could use it like
2572 this:&lt;/p&gt;
2573
2574 &lt;p&gt;&lt;pre&gt;
2575 fastboot flash unlocktoken Unlock_code.bin
2576 &lt;/pre&gt;&lt;/p&gt;
2577
2578 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2579 could start stuffing the software of my own choosing into the device.
2580 So far I only inserted a replacement recovery image to wipe the phone
2581 before I start. We will see what happen next. Perhaps I should
2582 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2583 </description>
2584 </item>
2585
2586 <item>
2587 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2588 <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>
2589 <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>
2590 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2591 <description>&lt;p&gt;For a while now, I have wanted to test
2592 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2593 said to provide end to end encrypted communication and several of my
2594 friends and family are already using it. As I by choice do not own a
2595 mobile phone, this proved to be harder than expected. And I wanted to
2596 have the source of the client and know that it was the code used on my
2597 machine. But yesterday I managed to get it working. I used the
2598 Github source, compared it to the source in
2599 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2600 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2601 patches to use the production Signal servers, started the app and
2602 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2603 the recipe how I did it.&lt;/p&gt;
2604
2605 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2606
2607 &lt;pre&gt;
2608 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2609 &lt;/pre&gt;
2610
2611 &lt;p&gt;Next, I patched the source to use the production servers, to be
2612 able to talk to other Signal users:&lt;/p&gt;
2613
2614 &lt;pre&gt;
2615 cat &amp;lt;&amp;lt;EOF | patch -p0
2616 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2617 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2618 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2619 @@ -47,8 +47,8 @@
2620 });
2621 });
2622
2623 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2624 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2625 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2626 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2627 var messageReceiver;
2628 window.getSocketStatus = function() {
2629 if (messageReceiver) {
2630 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2631 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2632 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2633 @@ -1,6 +1,6 @@
2634 ;(function() {
2635 &#39;use strict&#39;;
2636 - var BUILD_EXPIRATION = 0;
2637 + var BUILD_EXPIRATION = 1474492690000;
2638
2639 window.extension = window.extension || {};
2640
2641 EOF
2642 &lt;/pre&gt;
2643
2644 &lt;p&gt;The first part is changing the servers, and the second is updating
2645 an expiration timestamp. This timestamp need to be updated regularly.
2646 It is set 90 days in the future by the build process (Gruntfile.js).
2647 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2648
2649 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2650 script to launch Signal in Chromium.&lt;/p&gt;
2651
2652 &lt;pre&gt;
2653 #!/bin/sh
2654 cd $(dirname $0)
2655 mkdir -p userdata
2656 exec chromium \
2657 --proxy-server=&quot;socks://localhost:9050&quot; \
2658 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2659 &lt;/pre&gt;
2660
2661 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2662 SOCKS5 proxy to make sure those controlling the Signal servers (today
2663 Amazon and Whisper Systems) as well as those listening on the lines
2664 will have a harder time location my laptop based on the Signal
2665 connections if they use source IP address.&lt;/p&gt;
2666
2667 &lt;p&gt;When the script starts, one need to follow the instructions under
2668 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2669 repository. I right clicked on the Signal window to get up the
2670 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2671 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2672 registration form. Then I entered by land line phone number and
2673 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2674 repeated the verification code three times. After entering the number
2675 into the verification code field in the form, I could start using
2676 Signal from my laptop.
2677
2678 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2679 whom and thus who know who to those controlling the central server,
2680 but such leakage is hard to avoid with a centrally controlled server
2681 setup. It is something to keep in mind when using Signal - the
2682 content of your chats are harder to intercept, but the meta data
2683 exposing your contact network is available to people you do not know.
2684 So better than many options, but not great. And sadly the usage is
2685 connected to my land line, thus allowing those controlling the server
2686 to associate it to my home and person. I would prefer it if only
2687 those I knew could tell who I was on Signal. There are options
2688 avoiding such information leakage, but most of my friends are not
2689 using them, so I am stuck with Signal for now.&lt;/p&gt;
2690
2691 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2692 on this topic in
2693 &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
2694 and updated recipe for using the Signal app without a mobile
2695 phone&lt;/a&gt;.&lt;/p&gt;
2696 </description>
2697 </item>
2698
2699 <item>
2700 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2701 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2702 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2703 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2704 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2705 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2706 multimedia player in Debian claimed to support most file formats /
2707 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2708 the various players claimed support for. The range was from 55 to 130
2709 MIME types. I suspect most media formats are supported by all
2710 players, but this is not really reflected in the MimeTypes values in
2711 their desktop files. There are probably also some bogus MIME types
2712 listed, but it is hard to identify which one this is.&lt;/p&gt;
2713
2714 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2715 the players suggesting to add more MIME types to their desktop files,
2716 and decided to spend some time myself improving the situation for my
2717 favorite media player VLC. The fixes for VLC entered Debian unstable
2718 yesterday. The complete list of MIME types can be seen on the
2719 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2720 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2721
2722 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2723 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2724 kmplayer. I am sure some of the other players desktop files support
2725 several of the formats currently listed as working only with vlc,
2726 toten and parole.&lt;/p&gt;
2727
2728 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2729 supported by all the tested multimedia players in Debian in their
2730 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2731 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2732 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2733 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2734 it sad that video/ogg and video/webm is not supported by all the media
2735 players in Debian. As far as I can tell, all of them can handle both
2736 formats.&lt;/p&gt;
2737 </description>
2738 </item>
2739
2740 <item>
2741 <title>A program should be able to open its own files on Linux</title>
2742 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2744 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2745 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2746 decided to test its presentation tool when making the slides for a
2747 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2748 wrote the first draft of the slides, saved the result and went to bed
2749 the day before I would give the talk. The next day I took a plane to
2750 the location where the meeting should take place, and on the plane I
2751 started up koffice again to polish the talk a bit, only to discover
2752 that kpresenter refused to load its own data file. I cursed a bit and
2753 started making the slides again from memory, to have something to
2754 present when I arrived. I tested that the saved files could be
2755 loaded, and the day seemed to be rescued. I continued to polish the
2756 slides until I suddenly discovered that the saved file could no longer
2757 be loaded into kpresenter. In the end I had to rewrite the slides
2758 three times, condensing the content until the talk became shorter and
2759 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2760 kpresenter wrote inline images in a way itself could not understand.
2761 Eventually that bug was fixed and kpresenter ended up being a great
2762 program to make slides. The point I&#39;m trying to make is that we
2763 expect a program to be able to load its own data files, and it is
2764 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2765
2766 &lt;p&gt;Did you ever experience a program failing to load its own data
2767 files from the desktop file browser? It is not a uncommon problem. A
2768 while back I discovered that the screencast recorder
2769 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2770 browser would refuse to open. No video player claimed to understand
2771 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2772 returning the application/ogg MIME type, which no video player I had
2773 installed listed as a MIME type they would understand. I asked for
2774 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2775 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2776 several video players to add video/ogg to their desktop files, to give
2777 the file browser an idea what to do about Ogg Theora files. After a
2778 while, the desktop file browsers in Debian started to handle the
2779 output from gtk-recordmydesktop properly.&lt;/p&gt;
2780
2781 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2782 system Rosegarden again, and I discovered that the KDE and xfce file
2783 browsers did not know what to do with the Rosegarden project files
2784 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2785 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2786 included in the next upload. To increase the chance of me remembering
2787 how to fix the problem next time some program fail to load its files
2788 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2789
2790 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2791 There are two sources for the MIME type of a given file. The output from
2792 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2793 shared MIME type registry (under /usr/share/mime/). The file MIME
2794 type is mapped to programs supporting the MIME type, and this
2795 information is collected from
2796 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2797 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2798 one desktop file claiming support for the MIME type of the file, it is
2799 activated when asking to open a given file. If there are more, one
2800 can normally select which one to use by right-clicking on the file and
2801 selecting the wanted one using &#39;Open with&#39; or similar. In general
2802 this work well. But it depend on each program picking a good MIME
2803 type (preferably
2804 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2805 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2806 registry recognizing the file and the desktop file to list the MIME
2807 type in its list of supported MIME types.&lt;/p&gt;
2808
2809 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2810 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2811 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2812
2813 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2814 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2815 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2816 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2817 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2818 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2819 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2820 &amp;lt;/mime-type&amp;gt;
2821 &amp;lt;/mime-info&amp;gt;
2822 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2823
2824 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2825 (it is a gzipped XML file). Note, it is much better to use an
2826 official MIME type registered with IANA than it is to make up ones own
2827 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2828
2829 &lt;p&gt;The desktop file of the rosegarden program failed to list
2830 audio/x-rosegarden in its list of supported MIME types, causing the
2831 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2832
2833 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2834 % grep Mime /usr/share/applications/rosegarden.desktop
2835 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2836 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2837 %
2838 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2839
2840 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2841 MimeType= line.&lt;/p&gt;
2842
2843 &lt;p&gt;If you run into a file which fail to open the correct program when
2844 selected from the file browser, please check out the output from
2845 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2846 MIME type is registered somewhere under /usr/share/mime/ and check
2847 that some desktop file under /usr/share/applications/ is claiming
2848 support for this MIME type. If not, please report a bug to have it
2849 fixed. :)&lt;/p&gt;
2850 </description>
2851 </item>
2852
2853 <item>
2854 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2855 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2857 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2858 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2859 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2860 related packages. The idea is to have a database of mappings between
2861 hardware and packages, and pop up a dialog suggesting for the user to
2862 install the packages to use a given hardware dongle. Some use cases
2863 are when you insert a Yubikey, it proposes to install the software
2864 needed to control it; when you insert a braille reader list it
2865 proposes to install the packages needed to send text to the reader;
2866 and when you insert a ColorHug screen calibrator it suggests to
2867 install the driver for it. The system work well, and even have a few
2868 command line tools to install firmware packages and packages for the
2869 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2870
2871 &lt;p&gt;The system was initially written using aptdaemon, because I found
2872 good documentation and example code on how to use it. But aptdaemon
2873 is going away and is generally being replaced by
2874 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2875 so Isenkram needed a rewrite. And today, thanks to the great patch
2876 from my college Sunil Mohan Adapa in the FreedomBox project, the
2877 rewrite finally took place. I&#39;ve just uploaded a new version of
2878 Isenkram into Debian Unstable with the patch included, and the default
2879 for the background daemon is now to use PackageKit. To check it out,
2880 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2881 and see if it is recognised.&lt;/p&gt;
2882
2883 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2884 the machine it is running on, you can check out the isenkram-lookup
2885 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2886
2887 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2888 % isenkram-lookup
2889 bluez
2890 cheese
2891 fprintd
2892 fprintd-demo
2893 gkrellm-thinkbat
2894 hdapsd
2895 libpam-fprintd
2896 pidgin-blinklight
2897 thinkfan
2898 tleds
2899 tp-smapi-dkms
2900 tp-smapi-source
2901 tpb
2902 %p
2903 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2904
2905 &lt;p&gt;The hardware mappings come from several places. The preferred way
2906 is for packages to announce their hardware support using
2907 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2908 cross distribution appstream system&lt;/a&gt;.
2909 See
2910 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2911 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2912 </description>
2913 </item>
2914
2915 <item>
2916 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2917 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2918 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2919 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2920 <description>&lt;p&gt;Yesterday I updated the
2921 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2922 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2923 enterprising users. There were some nice user and visible changes.
2924 First of all, both desktop menu entries now work. A design flaw in
2925 one of the script made the history graph fail to show up (its PNG was
2926 dumped in ~/.xsession-errors) if no controlling TTY was available.
2927 The script worked when called from the command line, but not when
2928 called from the desktop menu. I changed this to look for a DISPLAY
2929 variable or a TTY before deciding where to draw the graph, and now the
2930 graph window pop up as expected.&lt;/p&gt;
2931
2932 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2933 graphs (the one showing the last few hours). New is also the user of
2934 colours showing charging in blue and discharge in red. The percentages
2935 of this graph is relative to last full charge, not battery design
2936 capacity.&lt;/p&gt;
2937
2938 &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;
2939
2940 &lt;p&gt;The other graph show the entire history of the collected battery
2941 statistics, comparing it to the design capacity of the battery to
2942 visualise how the battery life time get shorter over time. The red
2943 line in this graph is what the previous graph considers 100 percent:
2944
2945 &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;
2946
2947 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2948 percent of last full capacity, and how the capacity of the battery is
2949 shrinking. :(&lt;/p&gt;
2950
2951 &lt;p&gt;The last new feature is in the collector, which now will handle
2952 more hardware models. On some hardware, Linux power supply
2953 information is stored in /sys/class/power_supply/ACAD/, while the
2954 collector previously only looked in /sys/class/power_supply/AC/. Now
2955 both are checked to figure if there is power connected to the
2956 machine.&lt;/p&gt;
2957
2958 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2959 check out the
2960 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2961 in Debian unstable, or rebuild it on Jessie to get it working on
2962 Debian stable. :) The upstream source is available from &lt;a
2963 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2964 Patches are very welcome.&lt;/p&gt;
2965
2966 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2967 activities, please send Bitcoin donations to my address
2968 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2969 </description>
2970 </item>
2971
2972 <item>
2973 <title>Debian now with ZFS on Linux included</title>
2974 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2975 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2976 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2977 <description>&lt;p&gt;Today, after many years of hard work from many people,
2978 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2979 Debian. The package status can be seen on
2980 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2981 for zfs-linux&lt;/a&gt;. and
2982 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2983 team status page&lt;/a&gt;. If you want to help out, please join us.
2984 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2985 source code&lt;/a&gt; is available via git on Alioth. It would also be
2986 great if you could help out with
2987 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2988 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2989 </description>
2990 </item>
2991
2992 <item>
2993 <title>What is the best multimedia player in Debian?</title>
2994 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2996 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2997 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2998 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2999
3000 &lt;p&gt;A few years ago, I had a look at the media support for Browser
3001 plugins in Debian, to get an idea which plugins to include in Debian
3002 Edu. I created a script to extract the set of supported MIME types
3003 for each plugin, and used this to find out which multimedia browser
3004 plugin supported most file formats / media types.
3005 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
3006 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
3007 not been updated for a while. But browser plugins are less relevant
3008 these days, so I thought it was time to look at standalone
3009 players.&lt;/p&gt;
3010
3011 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
3012 player when I wanted to play videos from the Norwegian National
3013 Broadcasting Company, and decided to investigate why. The cause is a
3014 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
3015 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
3016 of MIME types announced in the desktop file and the browser plugin,
3017 only to discover that there is quite a large difference between the
3018 two for VLC. This discovery made me dig up the script I used to
3019 compare browser plugins, and adjust it to compare desktop files
3020 instead, to try to figure out which multimedia player in Debian
3021 support most file formats.&lt;/p&gt;
3022
3023 &lt;p&gt;The result can be seen on the Debian Wiki, as
3024 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
3025 table listing all MIME types supported by one of the packages included
3026 in the table&lt;/a&gt;, with the package supporting most MIME types being
3027 listed first in the table.&lt;/p&gt;
3028
3029 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
3030 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3031 kmplayer. Time for the other players to update their announced MIME
3032 support?&lt;/p&gt;
3033 </description>
3034 </item>
3035
3036 <item>
3037 <title>The Pyra - handheld computer with Debian preinstalled</title>
3038 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
3039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
3040 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
3041 <description>A friend of mine made me aware of
3042 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
3043 handheld computer which will be delivered with Debian preinstalled. I
3044 would love to get one of those for my birthday. :)&lt;/p&gt;
3045
3046 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3047 plugs and many others connectors, and include a full keyboard and a 5&quot;
3048 LCD touch screen. The 6000mAh battery is claimed to provide a whole
3049 day of battery life time, but I have not seen any independent tests
3050 confirming this. The vendor is still collecting preorders, and the
3051 last I heard last night was that 22 more orders were needed before
3052 production started.&lt;/p&gt;
3053
3054 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
3055 Debian. Please let me know if you know of any others. Is it the
3056 first computer being sold with Debian preinstalled?&lt;/p&gt;
3057 </description>
3058 </item>
3059
3060 <item>
3061 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
3062 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
3063 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
3064 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
3065 <description>&lt;p&gt;During this weekends
3066 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
3067 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
3068 to make sure there are good books about Debian available in Norwegian
3069 Bokmål, and got in touch with the people behind the
3070 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
3071 project&lt;/a&gt; to get started. If you want to help out, please start
3072 contributing using
3073 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3074 hosted weblate project page&lt;/a&gt;, and get in touch using
3075 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3076 translators mailing list&lt;/a&gt;. Please also check out
3077 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3078 contributors&lt;/a&gt;.&lt;/p&gt;
3079
3080 &lt;p&gt;The book is already available on paper in English, French and
3081 Japanese, and our goal is to get it available on paper in Norwegian
3082 Bokmål too. In addition to the paper edition, there are also EPUB and
3083 Mobi versions available. And there are incomplete translations
3084 available for many more languages.&lt;/p&gt;
3085 </description>
3086 </item>
3087
3088 <item>
3089 <title>One in two hundred Debian users using ZFS on Linux?</title>
3090 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
3091 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
3092 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
3093 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
3094 packages in Debian, and was quite surprised with what I found. I use
3095 ZFS myself at home, but did not really expect many others to do so.
3096 But I might be wrong.&lt;/p&gt;
3097
3098 &lt;p&gt;According to
3099 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
3100 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
3101 0.53% of the population, with the package installed. As far as I know
3102 the only use of the spl-linux package is as a support library for ZFS
3103 on Linux, so I use it here as proxy for measuring the number of ZFS
3104 installation on Linux in Debian. In the kFreeBSD variant of Debian
3105 the ZFS feature is already available, and there
3106 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
3107 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
3108 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
3109
3110 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
3111 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
3112 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
3113 cleared, the package is still not in Debian. The package is again in
3114 the NEW queue. Several uploads have been rejected so far because the
3115 debian/copyright file was incomplete or wrong, but there is no reason
3116 to give up. The current status can be seen on
3117 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3118 team status page&lt;/a&gt;, and
3119 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
3120 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
3121
3122 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
3123 my home server can function in the future using only official Debian
3124 packages, and the current blocker is to get the debian/copyright file
3125 accepted by the FTP masters in Debian, I decided a while back to try
3126 to help out the team. This was the background for my blog post about
3127 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
3128 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
3129 used the techniques I explored there to try to find any errors in the
3130 copyright file. It is not very easy to check every one of the around
3131 2000 files in the source package, but I hope we this time got it
3132 right. If you want to help out, check out the git source and try to
3133 find missing entries in the debian/copyright file.&lt;/p&gt;
3134 </description>
3135 </item>
3136
3137 <item>
3138 <title>Full battery stats collector is now available in Debian</title>
3139 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
3140 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
3141 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
3142 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
3143 extended collector that will collect the complete battery history for
3144 later processing and graphing. The original collector store the
3145 battery level as percentage of last full level, while the new
3146 collector also record battery vendor, model, serial number, design
3147 full level, last full level and current battery level. This make it
3148 possible to predict the lifetime of the battery as well as visualise
3149 the energy flow when the battery is charging or discharging.&lt;/p&gt;
3150
3151 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
3152 in the version 0.5.1 package in unstable. Get the new battery level graph
3153 and lifetime prediction by running:
3154
3155 &lt;p&gt;&lt;pre&gt;
3156 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3157 &lt;/pre&gt;&lt;/p&gt;
3158
3159 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
3160
3161 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
3162 entry yet):&lt;/p&gt;
3163
3164 &lt;p&gt;&lt;pre&gt;
3165 /usr/share/battery-stats/battery-stats-graph-flow
3166 &lt;/pre&gt;&lt;/p&gt;
3167
3168 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
3169 when there are few data points. The graphs look a bit better with a
3170 few years of data.&lt;/p&gt;
3171
3172 &lt;p&gt;A while back one important feature I use in the battery stats
3173 collector broke in Debian. The scripts in
3174 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
3175 suspect it happened when Jessie started using systemd, but I do not
3176 know. The issue is reported as
3177 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
3178 pm-utils. I managed to work around it by adding an udev rule to call
3179 the collector script every time the power connector is connected and
3180 disconnected. With this fix in place it was finally time to make a
3181 new release of the package, and get it into Debian.&lt;/p&gt;
3182
3183 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3184 check out the
3185 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3186 in Debian unstable, or rebuild it on Jessie to get it working on
3187 Debian stable. :) The upstream source is available from
3188 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3189 As always, patches are very welcome.&lt;/p&gt;
3190 </description>
3191 </item>
3192
3193 <item>
3194 <title>Making battery measurements a little easier in Debian</title>
3195 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
3196 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
3197 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
3198 <description>&lt;p&gt;Back in September, I blogged about
3199 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
3200 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
3201 how it showed the decay and death of this battery (now replaced). I
3202 created a simple deb package to handle the collection and graphing,
3203 but did not want to upload it to Debian as there were already
3204 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
3205 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
3206 a point of uploading a competing package when battery-stats could be
3207 fixed instead. I reported a few bugs about its non-function, and
3208 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
3209
3210 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
3211 hands. The end result is that I am now the new upstream developer of
3212 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
3213 battery-stats in Debian, and the package in Debian unstable is finally
3214 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
3215 information provided by the Linux kernel. If you install the
3216 battery-stats package from unstable now, you will be able to get a
3217 graph of the current battery fill level, to get some idea about the
3218 status of the battery. The source package build and work just fine in
3219 Debian testing and stable (and probably oldstable too, but I have not
3220 tested). The default graph you get for that system look like this:&lt;/p&gt;
3221
3222 &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;
3223
3224 &lt;p&gt;My plans for the future is to merge my old scripts into the
3225 battery-stats package, as my old scripts collected a lot more details
3226 about the battery. The scripts are merged into the upstream
3227 battery-stats git repository already, but I am not convinced they work
3228 yet, as I changed a lot of paths along the way. Will have to test a
3229 bit more before I make a new release.&lt;/p&gt;
3230
3231 &lt;p&gt;I will also consider changing the file format slightly, as I
3232 suspect the way I combine several values into one field might make it
3233 impossible to know the type of the value when using it for processing
3234 and graphing.&lt;/p&gt;
3235
3236 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
3237 battery, check out the battery-stats package in
3238 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
3239 on
3240 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3241 I would love some help to improve the system further.&lt;/p&gt;
3242 </description>
3243 </item>
3244
3245 <item>
3246 <title>Creating, updating and checking debian/copyright semi-automatically</title>
3247 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
3248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
3249 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
3250 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
3251 details. And one of the details is the content of the
3252 debian/copyright file, which should list all relevant licenses used by
3253 the code in the package in question, preferably in
3254 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
3255 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
3256
3257 &lt;p&gt;For large packages with lots of contributors it is hard to write
3258 and update this file manually, and if you get some detail wrong, the
3259 package is normally rejected by the ftpmasters. So getting it right
3260 the first time around get the package into Debian faster, and save
3261 both you and the ftpmasters some work.. Today, while trying to figure
3262 out what was wrong with
3263 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
3264 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
3265 figuring out the options for doing this job automatically, or at least
3266 semi-automatically.&lt;/p&gt;
3267
3268 &lt;p&gt;Lucikly, there are at least two tools available for generating the
3269 file based on the code in the source package,
3270 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
3271 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
3272 not sure which one of them came first, but both seem to be able to
3273 create a sensible draft file. As far as I can tell, none of them can
3274 be trusted to get the result just right, so the content need to be
3275 polished a bit before the file is OK to upload. I found the debmake
3276 option in
3277 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
3278 blog posts from 2014&lt;/a&gt;.
3279
3280 &lt;p&gt;To generate using debmake, use the -cc option:
3281
3282 &lt;p&gt;&lt;pre&gt;
3283 debmake -cc &gt; debian/copyright
3284 &lt;/pre&gt;&lt;/p&gt;
3285
3286 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
3287 this might not be the best option.&lt;/p&gt;
3288
3289 &lt;p&gt;The cme option is based on a config parsing library, and I found
3290 this approach in
3291 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
3292 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
3293 dpkg-copyright&#39; option:
3294
3295 &lt;p&gt;&lt;pre&gt;
3296 cme update dpkg-copyright
3297 &lt;/pre&gt;&lt;/p&gt;
3298
3299 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
3300 handle UTF-8 names better than debmake.&lt;/p&gt;
3301
3302 &lt;p&gt;When the copyright file is created, I would also like some help to
3303 check if the file is correct. For this I found two good options,
3304 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
3305 to focus on license types and file matching, and is able to detect
3306 ineffective blocks in the copyright file. The latter reports missing
3307 copyright holders and years, but was confused by inconsistent license
3308 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
3309 fix all issues reported by them before uploading. But I do not know
3310 if the tools and the ftpmasters agree on what is important to fix in a
3311 copyright file, so the package might still be rejected.&lt;/p&gt;
3312
3313 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
3314 will read through the source and try to find all copyright statements.
3315 It is not comparing the result to the content of debian/copyright, but
3316 can be useful when verifying the content of the copyright file.&lt;/p&gt;
3317
3318 &lt;p&gt;Are you aware of better tools in Debian to create and update
3319 debian/copyright file. Please let me know, or blog about it on
3320 planet.debian.org.&lt;/p&gt;
3321
3322 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3323 activities, please send Bitcoin donations to my address
3324 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3325
3326 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
3327 on how to use licensecheck and cdbs to create a draft copyright file
3328
3329 &lt;p&gt;&lt;pre&gt;
3330 licensecheck --copyright -r `find * -type f` | \
3331 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
3332 &lt;/pre&gt;&lt;/p&gt;
3333
3334 &lt;p&gt;He mentioned that he normally check the generated file into the
3335 version control system to make it easier to discover license and
3336 copyright changes in the upstream source. I will try to do the same
3337 with my packages in the future.&lt;/p&gt;
3338
3339 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
3340 against using -quiet for new users, so I removed it from the proposed
3341 command line.&lt;/p&gt;
3342 </description>
3343 </item>
3344
3345 <item>
3346 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
3347 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
3348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
3349 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
3350 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
3351 is taking shape in Debian, and one provided feature is a very
3352 convenient way to tell you which package to install to make a given
3353 firmware file available when the kernel is looking for it. This can
3354 be done using apt-file too, but that is for someone else to blog
3355 about. :)&lt;/p&gt;
3356
3357 &lt;p&gt;Here is a small recipe to find the package with a given firmware
3358 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
3359 picked from the set of firmware announced using appstream in Debian
3360 unstable. In general you would be looking for the firmware requested
3361 by the kernel during kernel module loading. To find the package
3362 providing the example file, do like this:&lt;/p&gt;
3363
3364 &lt;blockquote&gt;&lt;pre&gt;
3365 % apt install appstream
3366 [...]
3367 % apt update
3368 [...]
3369 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
3370 awk &#39;/Package:/ {print $2}&#39;
3371 firmware-qlogic
3372 %
3373 &lt;/pre&gt;&lt;/blockquote&gt;
3374
3375 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
3376 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
3377 a way appstream can use.&lt;/p&gt;
3378
3379 &lt;p&gt;This same approach can be used to find any package supporting a
3380 given MIME type. This is very useful when you get a file you do not
3381 know how to handle. First find the mime type using &lt;tt&gt;file
3382 --mime-type&lt;/tt&gt;, and next look up the package providing support for
3383 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3384 and you can find all packages handling this type like this:&lt;/p&gt;
3385
3386 &lt;blockquote&gt;&lt;pre&gt;
3387 % apt install appstream
3388 [...]
3389 % apt update
3390 [...]
3391 % appstreamcli what-provides mimetype image/svg+xml | \
3392 awk &#39;/Package:/ {print $2}&#39;
3393 bkchem
3394 phototonic
3395 inkscape
3396 shutter
3397 tetzle
3398 geeqie
3399 xia
3400 pinta
3401 gthumb
3402 karbon
3403 comix
3404 mirage
3405 viewnior
3406 postr
3407 ristretto
3408 kolourpaint4
3409 eog
3410 eom
3411 gimagereader
3412 midori
3413 %
3414 &lt;/pre&gt;&lt;/blockquote&gt;
3415
3416 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
3417 packages providing appstream metadata.&lt;/p&gt;
3418 </description>
3419 </item>
3420
3421 <item>
3422 <title>Creepy, visualise geotagged social media information - nice free software</title>
3423 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
3424 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
3425 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
3426 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
3427 with the computerised radio beacon known as a mobile phone their
3428 position is tracked by the phone company and often stored for a long
3429 time (like every time a SMS is received or sent). And if their
3430 computerised radio beacon is capable of running programs (often called
3431 mobile apps) downloaded from the Internet, these programs are often
3432 also capable of tracking their location (if the app requested access
3433 during installation). And when these programs send out information to
3434 central collection points, the location is often included, unless
3435 extra care is taken to not send the location. The provided
3436 information is used by several entities, for good and bad (what is
3437 good and bad, depend on your point of view). What is certain, is that
3438 the private sphere and the right to free movement is challenged and
3439 perhaps even eradicated for those announcing their location this way,
3440 when they share their whereabouts with private and public
3441 entities.&lt;/p&gt;
3442
3443 &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;
3444
3445 &lt;p&gt;The phone company logs provide a register of locations to check out
3446 when one want to figure out what the tracked person was doing. It is
3447 unavailable for most of us, but provided to selected government
3448 officials, company staff, those illegally buying information from
3449 unfaithful servants and crackers stealing the information. But the
3450 public information can be collected and analysed, and a free software
3451 tool to do so is called
3452 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
3453 discovered it when I read
3454 &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
3455 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
3456 November 2014, and decided to check if it was available in Debian.
3457 The python program was in Debian, but
3458 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
3459 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
3460 uploaded a new version which did not work quite right, but did not
3461 have time to fix it then. This Christmas I decided to finally try to
3462 get Creepy operational in Debian. Now a fixed version is available in
3463 Debian unstable and testing, and almost all Debian specific patches
3464 are now included
3465 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
3466
3467 &lt;p&gt;The Creepy program visualises geolocation information fetched from
3468 Twitter, Instagram, Flickr and Google+, and allow one to get a
3469 complete picture of every social media message posted recently in a
3470 given area, or track the movement of a given individual across all
3471 these services. Earlier it was possible to use the search API of at
3472 least some of these services without identifying oneself, but these
3473 days it is impossible. This mean that to use Creepy, you need to
3474 configure it to log in as yourself on these services, and provide
3475 information to them about your search interests. This should be taken
3476 into account when using Creepy, as it will also share information
3477 about yourself with the services.&lt;/p&gt;
3478
3479 &lt;p&gt;The picture above show the twitter messages sent from (or at least
3480 geotagged with a position from) the city centre of Oslo, the capital
3481 of Norway. One useful way to use Creepy is to first look at
3482 information tagged with an area of interest, and next look at all the
3483 information provided by one or more individuals who was in the area.
3484 I tested it by checking out which celebrity provide their location in
3485 twitter messages by checkout out who sent twitter messages near a
3486 Norwegian TV station, and next could track their position over time,
3487 making it possible to locate their home and work place, among other
3488 things. A similar technique have been
3489 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
3490 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
3491 tool to discover lying governments, and a useful tool to help people
3492 understand the value of the private information they provide to the
3493 public.&lt;/p&gt;
3494
3495 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
3496 it depend on several python modules currently missing in Jessie (at
3497 least python-instagram, python-flickrapi and
3498 python-requests-toolbelt).&lt;/p&gt;
3499
3500 &lt;p&gt;(I have uploaded
3501 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
3502 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
3503 Creepy program in Debian.)&lt;/p&gt;
3504 </description>
3505 </item>
3506
3507 <item>
3508 <title>Always download Debian packages using Tor - the simple recipe</title>
3509 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
3510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
3511 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
3512 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
3513 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
3514 that those listening on the Internet lines would have good reason to
3515 believe a computer have a given security hole&lt;/a&gt; if it download a
3516 security fix from a Debian mirror. This is a good reason to always
3517 use encrypted connections to the Debian mirror, to make sure those
3518 listening do not know which IP address to attack. In August, Richard
3519 Hartmann observed that encryption was not enough, when it was possible
3520 to interfere download size to security patches or the fact that
3521 download took place shortly after a security fix was released, and
3522 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
3523 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
3524 was not the first to propose this, as the
3525 &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;
3526 package by Tim Retout already existed to make it easy to convince apt
3527 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
3528 aware of that package when I read the blog post from Richard.&lt;/p&gt;
3529
3530 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
3531 sysadmins, and he set up a Tor hidden service on one of the central
3532 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3533 it possible to download packages directly between two tor nodes,
3534 making sure the network traffic always were encrypted.&lt;/p&gt;
3535
3536 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
3537 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
3538 urls with tor+http and tor+https, and using the hidden service instead
3539 of the official Debian mirror site. I recommend installing
3540 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
3541 done in /etc/.&lt;/p&gt;
3542
3543 &lt;blockquote&gt;&lt;pre&gt;
3544 apt install apt-transport-tor
3545 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
3546 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
3547 &lt;/pre&gt;&lt;/blockquote&gt;
3548
3549 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
3550 the sed commands for these too. The sed command is assuming your are
3551 using the ftp.debian.org Debian mirror. Adjust the command (or just
3552 edit the file manually) to match your mirror.&lt;/p&gt;
3553
3554 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
3555 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
3556 system, and do not work with these tor+http URLs. For
3557 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
3558 which need a recent apt version currently only in unstable. So if you
3559 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
3560
3561 &lt;p&gt;Another advantage from this change is that your machine will start
3562 using Tor regularly and at fairly random intervals (every time you
3563 update the package lists or upgrade or install a new package), thus
3564 masking other Tor traffic done from the same machine. Using Tor will
3565 become normal for the machine in question.&lt;/p&gt;
3566
3567 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
3568 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
3569 enabled. It would be great if it was the default on any Debian
3570 system.&lt;/p&gt;
3571 </description>
3572 </item>
3573
3574 <item>
3575 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3576 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3577 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3578 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3579 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3580 call the car license plate numbers in those days. I would write the
3581 numbers down in my little book and compare notes with the other kids
3582 to see how many region codes we had seen and if we had seen some
3583 exotic or special region codes and numbers. It was a fun game to pass
3584 time, as we kids have plenty of it.&lt;/p&gt;
3585
3586 &lt;p&gt;A few days I came across
3587 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3588 project&lt;/a&gt;, a free software project to automatically discover and
3589 report license plates in images and video streams, and provide the
3590 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3591 such system for a while now, because I believe it is a bad idea that the
3592 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3593 number plate recognition&lt;/a&gt; tool only is available in the hands of
3594 the powerful, and want it to be available also for the powerless to
3595 even the score when it comes to surveillance and sousveillance. I
3596 discovered the developer
3597 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3598 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3599 help him get it into shape to get the package uploaded into the Debian
3600 archive.&lt;/p&gt;
3601
3602 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3603 it into Debian, where it currently
3604 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3605 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3606
3607 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3608 for the common folks, ie those not running a large government
3609 surveillance system? Well, I plan to put it in a computer on my bike
3610 and in my car, tracking the cars nearby and allowing me to be notified
3611 when number plates on my watch list are discovered. Another use case
3612 was suggested by a friend of mine, who wanted to set it up at his home
3613 to open the car port automatically when it discovered the plate on his
3614 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3615 capable of placing his license plate number of a piece of cardboard to
3616 open his car port, men replied that it was always unlocked anyway. I
3617 guess for such use case it make sense. I am sure there are other use
3618 cases too, for those with imagination and a vision.&lt;/p&gt;
3619
3620 &lt;p&gt;If you want to build your own version of the Debian package, check
3621 out the upstream git source and symlink ./distros/debian to ./debian/
3622 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3623 package show up in unstable.&lt;/p&gt;
3624 </description>
3625 </item>
3626
3627 <item>
3628 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3629 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3631 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3632 <description>&lt;p&gt;Around three years ago, I created
3633 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3634 system&lt;/a&gt; to get a more practical solution in Debian for handing
3635 hardware related packages. A GUI system in the isenkram package will
3636 present a pop-up dialog when some hardware dongle supported by
3637 relevant packages in Debian is inserted into the machine. The same
3638 lookup mechanism to detect packages is available as command line
3639 tools in the isenkram-cli package. In addition to mapping hardware,
3640 it will also map kernel firmware files to packages and make it easy to
3641 install needed firmware packages automatically. The key for this
3642 system to work is a good way to map hardware to packages, in other
3643 words, allow packages to announce what hardware they will work
3644 with.&lt;/p&gt;
3645
3646 &lt;p&gt;I started by providing data files in the isenkram source, and
3647 adding code to download the latest version of these data files at run
3648 time, to ensure every user had the most up to date mapping available.
3649 I also added support for storing the mapping in the Packages file in
3650 the apt repositories, but did not push this approach because while I
3651 was trying to figure out how to best store hardware/package mappings,
3652 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3653 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3654 add the hardware mapping into that data set to be able to use
3655 appstream as a data source, and this was accepted at least for the
3656 Debian version of appstream.&lt;/p&gt;
3657
3658 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3659 and today I uploaded a new version 0.20 of isenkram adding support for
3660 appstream as a data source for mapping hardware to packages. The only
3661 package so far using appstream to announce its hardware support is my
3662 pymissile package. I got help from Matthias Klumpp with figuring out
3663 how do add the required
3664 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3665 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3666 this content:&lt;/p&gt;
3667
3668 &lt;blockquote&gt;&lt;pre&gt;
3669 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3670 &amp;lt;component&amp;gt;
3671 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3672 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3673 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3674 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3675 &amp;lt;description&amp;gt;
3676 &amp;lt;p&amp;gt;
3677 Pymissile provides a curses interface to control an original
3678 Marks and Spencer / Striker USB Missile Launcher, as well as a
3679 motion control script to allow a webcamera to control the
3680 launcher.
3681 &amp;lt;/p&amp;gt;
3682 &amp;lt;/description&amp;gt;
3683 &amp;lt;provides&amp;gt;
3684 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3685 &amp;lt;/provides&amp;gt;
3686 &amp;lt;/component&amp;gt;
3687 &lt;/pre&gt;&lt;/blockquote&gt;
3688
3689 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3690 which is a glob style match rule for hardware specific strings
3691 (modalias strings) provided by the Linux kernel. In this case, it
3692 will map to all USB devices with vendor code 1130 and product code
3693 0202.&lt;/p&gt;
3694
3695 &lt;p&gt;Note, it is important that the license of all the metadata files
3696 are compatible to have permissions to aggregate them into archive wide
3697 appstream files. Matthias suggested to use MIT or BSD licenses for
3698 these files. A challenge is figuring out a good id for the data, as
3699 it is supposed to be globally unique and shared across distributions
3700 (in other words, best to coordinate with upstream what to use). But
3701 it can be changed later or, so we went with the package name as
3702 upstream for this project is dormant.&lt;/p&gt;
3703
3704 &lt;p&gt;To get the metadata file installed in the correct location for the
3705 mirror update scripts to pick it up and include its content the
3706 appstream data source, the file must be installed in the binary
3707 package under /usr/share/appdata/. I did this by adding the following
3708 line to debian/pymissile.install:&lt;/p&gt;
3709
3710 &lt;blockquote&gt;&lt;pre&gt;
3711 debian/pymissile.metainfo.xml usr/share/appdata
3712 &lt;/pre&gt;&lt;/blockquote&gt;
3713
3714 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3715 all packages useful on the current computer automatically, and the GUI
3716 pop-up handler will propose to install the package not already
3717 installed if a hardware dongle is inserted into the machine in
3718 question.&lt;/p&gt;
3719
3720 &lt;p&gt;Details of the modalias field in appstream is available from the
3721 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3722
3723 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3724 try running this command on the command line:&lt;/p&gt;
3725
3726 &lt;blockquote&gt;&lt;pre&gt;
3727 cat $(find /sys/devices/|grep modalias)
3728 &lt;/pre&gt;&lt;/blockquote&gt;
3729
3730 &lt;p&gt;To learn more about the isenkram system, please check out
3731 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3732 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3733 </description>
3734 </item>
3735
3736 <item>
3737 <title>The GNU General Public License is not magic pixie dust</title>
3738 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3739 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3740 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3741 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3742 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3743 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3744 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3745 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3746
3747 &lt;blockquote&gt;
3748
3749 &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;
3750
3751 &lt;blockquote&gt;
3752 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3753
3754 The first step is to choose a
3755 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3756 code.&lt;br/&gt;
3757
3758 The next step is, when someone fails to follow that copyleft license,
3759 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3760
3761 and its a simple fact of our modern society that such type of
3762 work&lt;br/&gt;
3763
3764 is incredibly expensive to do and incredibly difficult to do.
3765 &lt;/blockquote&gt;
3766
3767 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3768 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3769 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3770 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3771
3772 &lt;p&gt;As the Debian Website
3773 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3774 &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;
3775 imply, public domain and permissively licensed software can lead to
3776 the production of more proprietary software as people discover useful
3777 software, extend it and or incorporate it into their hardware or
3778 software products. Copyleft licenses such as the GNU GPL were created
3779 to close off this avenue to the production of proprietary software but
3780 such licenses are not enough. With the ongoing adoption of Free
3781 Software by individuals and groups, inevitably the community&#39;s
3782 expectations of license compliance are violated, usually out of
3783 ignorance of the way Free Software works, but not always. As Karen
3784 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3785 Freedom&quot;&gt;FaiF&lt;/a&gt;
3786 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3787 copyleft is nothing if no-one is willing and able to stand up in court
3788 to protect it. The reality of today&#39;s world is that legal
3789 representation is expensive, difficult and time consuming. With
3790 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3791 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3792 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3793 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3794 of the Linux project, Debian and other groups against GPL violations.
3795 In March the SFC supported a
3796 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3797 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3798 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3799 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3800 kernel. Since then two of their sponsors pulled corporate funding and
3801 conferences
3802 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3803 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3804 less on corporate funding and more on the broad community of
3805 individuals who support Free Software and copyleft. So the SFC has
3806 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3807 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3808 a community of folks who stand up for copyleft and the GPL by
3809 supporting their work on promoting and supporting copyleft and Free
3810 Software.&lt;/p&gt;
3811
3812 &lt;p&gt;If you support Free Software,
3813 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3814 what the SFC do, agree with their
3815 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3816 principles&lt;/a&gt;, are happy about their
3817 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3818 work on a project that is an SFC
3819 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3820 just want to stand up for copyleft, please join
3821 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3822 Allan Webber&lt;/a&gt;,
3823 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3824 Smith&lt;/a&gt;,
3825 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3826 Bacon&lt;/a&gt;, myself and
3827 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3828 becoming a
3829 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3830 next week your donation will be
3831 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3832 by an anonymous donor. Please also consider asking your employer to
3833 match your donation or become a sponsor of SFC. Don&#39;t forget to
3834 spread the word about your support for SFC via email, your blog and or
3835 social media accounts.&lt;/p&gt;
3836
3837 &lt;/blockquote&gt;
3838
3839 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3840 of Software Freedom Conservancy myself. Perhaps you should be a
3841 supporter too?&lt;/p&gt;
3842 </description>
3843 </item>
3844
3845 <item>
3846 <title>PGP key transition statement for key EE4E02F9</title>
3847 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3848 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3849 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3850 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3851 set it up properly. I wanted to generate it offline and have it
3852 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3853 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3854 time to sit down with an offline machine almost took forever. But
3855 finally I&#39;ve been able to complete the process, and have now moved
3856 from my old GPG key to a new GPG key. See
3857 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3858 full transition statement, signed with both my old and new key&lt;/a&gt; for
3859 the details. This is my new key:&lt;/p&gt;
3860
3861 &lt;pre&gt;
3862 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]
3863 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3864 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3865 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3866 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3867 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3868 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3869 &lt;/pre&gt;
3870
3871 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3872 my old key.&lt;/p&gt;
3873
3874 &lt;p&gt;If you signed my old key
3875 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3876 I&#39;d very much appreciate a signature on my new key, details and
3877 instructions in the transition statement. I m happy to reciprocate if
3878 you have a similarly signed transition statement to present.&lt;/p&gt;
3879 </description>
3880 </item>
3881
3882 <item>
3883 <title>The life and death of a laptop battery</title>
3884 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3886 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3887 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3888 But this do not last. The last few laptops gave me a feeling that
3889 within a year, the life time is just a fraction of what it used to be,
3890 and it slowly become painful to use the laptop without power connected
3891 all the time. Because of this, when I got a new Thinkpad X230 laptop
3892 about two years ago, I decided to monitor its battery state to have
3893 more hard facts when the battery started to fail.&lt;/p&gt;
3894
3895 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3896
3897 &lt;p&gt;First I tried to find a sensible Debian package to record the
3898 battery status, assuming that this must be a problem already handled
3899 by someone else. I found
3900 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3901 which collects statistics from the battery, but it was completely
3902 broken. I sent a few suggestions to the maintainer, but decided to
3903 write my own collector as a shell script while I waited for feedback
3904 from him. Via
3905 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3906 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3907 discovered
3908 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3909 available in Debian.&lt;/p&gt;
3910
3911 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3912 battery stats ever since. Now my
3913 /var/log/hjemmenett-battery-status.log file contain around 115,000
3914 measurements, from the time the battery was working great until now,
3915 when it is unable to charge above 7% of original capacity. My
3916 collector shell script is quite simple and look like this:&lt;/p&gt;
3917
3918 &lt;pre&gt;
3919 #!/bin/sh
3920 # Inspired by
3921 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3922 # See also
3923 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3924 logfile=/var/log/hjemmenett-battery-status.log
3925
3926 files=&quot;manufacturer model_name technology serial_number \
3927 energy_full energy_full_design energy_now cycle_count status&quot;
3928
3929 if [ ! -e &quot;$logfile&quot; ] ; then
3930 (
3931 printf &quot;timestamp,&quot;
3932 for f in $files; do
3933 printf &quot;%s,&quot; $f
3934 done
3935 echo
3936 ) &gt; &quot;$logfile&quot;
3937 fi
3938
3939 log_battery() {
3940 # Print complete message in one echo call, to avoid race condition
3941 # when several log processes run in parallel.
3942 msg=$(printf &quot;%s,&quot; $(date +%s); \
3943 for f in $files; do \
3944 printf &quot;%s,&quot; $(cat $f); \
3945 done)
3946 echo &quot;$msg&quot;
3947 }
3948
3949 cd /sys/class/power_supply
3950
3951 for bat in BAT*; do
3952 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3953 done
3954 &lt;/pre&gt;
3955
3956 &lt;p&gt;The script is called when the power management system detect a
3957 change in the power status (power plug in or out), and when going into
3958 and out of hibernation and suspend. In addition, it collect a value
3959 every 10 minutes. This make it possible for me know when the battery
3960 is discharging, charging and how the maximum charge change over time.
3961 The code for the Debian package
3962 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3963 available on github&lt;/a&gt;.&lt;/p&gt;
3964
3965 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3966
3967 &lt;pre&gt;
3968 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3969 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3970 [...]
3971 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3972 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3973 &lt;/pre&gt;
3974
3975 &lt;p&gt;I wrote a small script to create a graph of the charge development
3976 over time. This graph depicted above show the slow death of my laptop
3977 battery.&lt;/p&gt;
3978
3979 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3980 dying in a year or two, while the batteries of space probes and
3981 satellites keep working year after year. If we are to believe
3982 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3983 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3984 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3985 all the time, but to stay below 90% of full charge most of the time.
3986 I&#39;ve been told that the Tesla electric cars
3987 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3988 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3989 100% when preparing for a longer trip (not that I would want a car
3990 like Tesla where rights to privacy is abandoned, but that is another
3991 story), which I guess is the option we should have for laptops on
3992 Linux too.&lt;/p&gt;
3993
3994 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3995 stop charging at 80%, unless requested to charge to 100% once in
3996 preparation for a longer trip? I found
3997 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3998 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3999 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
4000 load).&lt;/p&gt;
4001
4002 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
4003 at the start. I also wonder why the &quot;full capacity&quot; increases some
4004 times, and if it is possible to repeat the process to get the battery
4005 back to design capacity. And I wonder if the discharge and charge
4006 speed change over time, or if this stay the same. I did not yet try
4007 to write a tool to calculate the derivative values of the battery
4008 level, but suspect some interesting insights might be learned from
4009 those.&lt;/p&gt;
4010
4011 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
4012 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4013 packages instead of the tp-smapi-dkms package I had tried to use
4014 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
4015 and stop. I&#39;ve done so now, but expect my existing battery is toast
4016 and need to be replaced. The proposal is unfortunately Thinkpad
4017 specific.&lt;/p&gt;
4018 </description>
4019 </item>
4020
4021 <item>
4022 <title>New laptop - some more clues and ideas based on feedback</title>
4023 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
4024 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
4025 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
4026 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
4027 need for a new laptop, and provided very useful feedback. I wish to
4028 thank every one of these. Several pointed me to the possibility of
4029 fixing my X230, and I am already in the process of getting Lenovo to
4030 do so thanks to the on site, next day support contract covering the
4031 machine. But the battery is almost useless (I expect to replace it
4032 with a non-official battery) and I do not expect the machine to live
4033 for many more years, so it is time to plan its replacement. If I did
4034 not have a support contract, it was suggested to find replacement parts
4035 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
4036 might present a language barrier as I do not understand French.&lt;/p&gt;
4037
4038 &lt;p&gt;One tip I got was to use the
4039 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
4040 compare laptop models. It seem to have more models available than
4041 prisjakt.no. Another tip I got from someone I know have similar
4042 keyboard preferences was that the HP EliteBook 840 keyboard is not
4043 very good, and this matches my experience with earlier EliteBook
4044 keyboards I tested. Because of this, I will not consider it any further.
4045
4046 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
4047 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4048 (which is missing from the X240), and is working fairly well with
4049 Debian Sid/Unstable according to
4050 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
4051 got on the keyboard quality are not consistent. Some say the keyboard
4052 is good, others say it is ok, while others say it is not very good.
4053 Those with experience from X41 and and X60 agree that the X250
4054 keyboard is not as good as those trusty old laptops, and suggest I
4055 keep and fix my X230 instead of upgrading, or get a used X230 to
4056 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
4057 activity and battery status, which is very convenient on my X230. I&#39;m
4058 also told that the CPU fan is running very often, making it a bit
4059 noisy. In any case, the X250 do not work out of the box with Debian
4060 Stable/Jessie, one of my requirements.&lt;/p&gt;
4061
4062 &lt;p&gt;I have also gotten a few vendor proposals, one was
4063 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
4064 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
4065 The latter look very attractive to me.&lt;/p&gt;
4066
4067 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
4068 as I keep looking for a replacement.&lt;/p&gt;
4069
4070 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
4071 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
4072 different
4073 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
4074 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
4075 </description>
4076 </item>
4077
4078 <item>
4079 <title>Time to find a new laptop, as the old one is broken after only two years</title>
4080 <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>
4081 <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>
4082 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
4083 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
4084 replacement soon. The left 5 cm of the screen on my Thinkpad X230
4085 started flickering yesterday, and I suspect the cause is a broken
4086 cable, as changing the angle of the screen some times get rid of the
4087 flickering.&lt;/p&gt;
4088
4089 &lt;p&gt;My requirements have not really changed since I bought it, and is
4090 still as
4091 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
4092 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
4093 good help from
4094 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
4095 where I could select at least a few of the requirements (mouse pin,
4096 wifi, weight) and go through the rest manually. Three button mouse
4097 and a good keyboard is not available as an option, and all the three
4098 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
4099 G2) lack three mouse buttons). It is also unclear to me how good the
4100 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
4101 the keyboard, even if the quality and robustness in the X series have
4102 deteriorated since X41.&lt;/p&gt;
4103
4104 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
4105 seem sensible to me? Are there better services around to search the
4106 set of available laptops for features? Please send me an email if you
4107 have suggestions.&lt;/p&gt;
4108
4109 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
4110 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
4111 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
4112 </description>
4113 </item>
4114
4115 <item>
4116 <title>How to stay with sysvinit in Debian Jessie</title>
4117 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
4118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
4119 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
4120 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
4121 sysvinit as its boot system by default. But how can one keep using
4122 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
4123 courtesy of
4124 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
4125 Schubert&lt;/a&gt; and
4126 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
4127 McVittie&lt;/a&gt;.
4128
4129 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
4130 keep sysvinit as your boot system, create a file
4131 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
4132 you upgrade:&lt;/p&gt;
4133
4134 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4135 Package: systemd-sysv
4136 Pin: release o=Debian
4137 Pin-Priority: -1
4138 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4139
4140 &lt;p&gt;This file content will tell apt and aptitude to not consider
4141 installing systemd-sysv as part of any installation and upgrade
4142 solution when resolving dependencies, and thus tell it to avoid
4143 systemd as a default boot system. The end result should be that the
4144 upgraded system keep using sysvinit.&lt;/p&gt;
4145
4146 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
4147 get sysvinit installed by default (debootstrap used by
4148 debian-installer have no option for this), but one can tell the
4149 installer to switch to sysvinit before the first boot. Either by
4150 using a kernel argument to the installer, or by adding a line to the
4151 preseed file used. First, the kernel command line argument:
4152
4153 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4154 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
4155 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4156
4157 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
4158
4159 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4160 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4161 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4162
4163 &lt;p&gt;One can of course also do this after the first boot by installing
4164 the sysvinit-core package.&lt;/p&gt;
4165
4166 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
4167 sysvinit boot sequence in Debian have several hardware specific bugs
4168 on Linux caused by the fact that it is unpredictable when hardware
4169 devices show up during boot. But on the other hand, the new default
4170 boot system still have a few rough edges I hope will be fixed before
4171 Jessie is released.&lt;/p&gt;
4172
4173 &lt;p&gt;Update 2014-11-26: Inspired by
4174 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
4175 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
4176 line.&lt;/p&gt;
4177 </description>
4178 </item>
4179
4180 <item>
4181 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
4182 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
4183 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
4184 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
4185 <description>&lt;p&gt;The right to communicate with your friends and family in private,
4186 without anyone snooping, is a right every citicen have in a liberal
4187 democracy. But this right is under serious attack these days.&lt;/p&gt;
4188
4189 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
4190 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
4191 the whisleblower Snowden) more expensive for Internet email,
4192 is to deliver all email using SMTP via Tor. Such SMTP option would be
4193 a nice addition to the FreedomBox project if we could send email
4194 between FreedomBox machines without leaking metadata about the emails
4195 to the people peeking on the wire. I
4196 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
4197 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
4198 lot of useful feedback and suggestions. It also became obvious to me
4199 that this was not a novel idea, as the same idea was tested and
4200 documented by Johannes Berg as early as 2006, and both
4201 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
4202 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
4203 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
4204
4205 &lt;p&gt;To implement such system one need to set up a Tor hidden service
4206 providing the SMTP protocol on port 25, and use email addresses
4207 looking like username@hidden-service-name.onion. With such addresses
4208 the connections to port 25 on hidden-service-name.onion using Tor will
4209 go to the correct SMTP server. To do this, one need to configure the
4210 Tor daemon to provide the hidden service and the mail server to accept
4211 emails for this .onion domain. To learn more about Exim configuration
4212 in Debian and test the design provided by Johannes Berg in his FAQ, I
4213 set out yesterday to create a Debian package for making it trivial to
4214 set up such SMTP over Tor service based on Debian. Getting it to work
4215 were fairly easy, and
4216 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
4217 source code for the Debian package&lt;/a&gt; is available from github. I
4218 plan to move it into Debian if further testing prove this to be a
4219 useful approach.&lt;/p&gt;
4220
4221 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
4222 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
4223 get rid of exim4). Install tor, clone the git repository mentioned
4224 above, build the deb and install it on the machine. Next, run
4225 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
4226 the instructions to get the service up and running. Restart tor and
4227 exim when it is done, and test mail delivery using swaks like
4228 this:&lt;/p&gt;
4229
4230 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4231 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
4232 --to fbx@dutlqrrmjhtfa3vp.onion
4233 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4234
4235 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
4236 address with your own address to test your server. :)&lt;/p&gt;
4237
4238 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
4239 easier and more automatic. Especially the tor setup need more work.
4240 Also, the package include a tor-smtp tool written in C, but its task
4241 should probably be rewritten in some script language to make the deb
4242 architecture independent. It would probably also make the code easier
4243 to review. The tor-smtp tool currently need to listen on a socket for
4244 exim to talk to it and is started using xinetd. It would be better if
4245 no daemon and no socket is needed. I suspect it is possible to get
4246 exim to run a command line tool for delivery instead of talking to a
4247 socket, and hope to figure out how in a future version of this
4248 system.&lt;/p&gt;
4249
4250 &lt;p&gt;Until I wipe my test machine, I can be reached using the
4251 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
4252 SMTorP. :)&lt;/p&gt;
4253 </description>
4254 </item>
4255
4256 <item>
4257 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
4258 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
4259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
4260 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
4261 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
4262 alioth.debian.org, you know the web interface is fairly slow to
4263 operate. First you visit one web page, enter the moderation password
4264 and get a new page shown with a list of all the messages to moderate
4265 and various options for each email address. This take a while for
4266 every list you moderate, and you need to do it regularly to do a good
4267 job as a list moderator. But there is a quick alternative,
4268 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
4269 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
4270 to moderate in a fraction of a second. Here is a test run on two
4271 lists I recently took over:&lt;/p&gt;
4272
4273 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4274 % time listadmin xiph
4275 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4276 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4277
4278 real 0m1.709s
4279 user 0m0.232s
4280 sys 0m0.012s
4281 %
4282 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4283
4284 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
4285 there are no message in the moderation queue. Every morning I
4286 currently moderate 68 mailman lists, and it normally take around two
4287 minutes. When I took over the two pkg-xiph lists above a few days
4288 ago, there were 400 emails waiting in the moderator queue. It took me
4289 less than 15 minutes to process them all using the listadmin
4290 program.&lt;/p&gt;
4291
4292 &lt;p&gt;If you install
4293 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
4294 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
4295 with content like this, the moderation task is a breeze:&lt;/p&gt;
4296
4297 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4298 username username@example.org
4299 spamlevel 23
4300 default discard
4301 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
4302
4303 password secret
4304 adminurl https://{domain}/mailman/admindb/{list}
4305 mailman-list@lists.example.com
4306
4307 password hidden
4308 other-list@otherserver.example.org
4309 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4310
4311 &lt;p&gt;There are other options to set as well. Check the manual page to
4312 learn the details.&lt;/p&gt;
4313
4314 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
4315 the SSL certificate is self signed or not properly signed by a
4316 generally accepted signing authority, you can set a environment
4317 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
4318
4319 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4320 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
4321 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4322
4323 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
4324 can provide an argument to the listadmin script like I do in the
4325 initial screen dump (the xiph argument). Using an argument, only
4326 lists matching the argument string will be processed. This make it
4327 quick to accept messages if you notice the moderation request in your
4328 email.&lt;/p&gt;
4329
4330 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
4331 mailing lists, as I simply do not have time to spend on that if the
4332 process was any slower. The listadmin program have saved me hours of
4333 time I could spend elsewhere over the years. It truly is nice free
4334 software.&lt;/p&gt;
4335
4336 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4337 activities, please send Bitcoin donations to my address
4338 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4339
4340 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
4341 configuration example. Also, I&#39;ve been told that the
4342 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
4343 sure why.&lt;/p&gt;
4344 </description>
4345 </item>
4346
4347 <item>
4348 <title>Debian Jessie, PXE and automatic firmware installation</title>
4349 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
4350 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
4351 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
4352 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
4353 problem that the WiFi card require some firmware to work properly.
4354 And it has been a pain to fix this using preseeding in Debian.
4355 Normally something more is needed. But thanks to
4356 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
4357 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
4358 to do this using simple preseeding.&lt;/p&gt;
4359
4360 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
4361 firmware for the hardware found in the machine (actually, requested by
4362 the kernel modules for the hardware). (It can also install user space
4363 programs supporting the hardware detected, but that is not the focus
4364 of this story.)&lt;/p&gt;
4365
4366 &lt;p&gt;To get this working in the default installation, two preeseding
4367 values are needed. First, the isenkram-cli package must be installed
4368 into the target chroot (aka the hard drive) before tasksel is executed
4369 in the pkgsel step of the debian-installer system. This is done by
4370 preseeding the base-installer/includes debconf value to include the
4371 isenkram-cli package. The package name is next passed to debootstrap
4372 for installation. With the isenkram-cli package in place, tasksel
4373 will automatically use the isenkram tasks to detect hardware specific
4374 packages for the machine being installed and install them, because
4375 isenkram-cli contain tasksel tasks.&lt;/p&gt;
4376
4377 &lt;p&gt;Second, one need to enable the non-free APT repository, because
4378 most firmware unfortunately is non-free. This is done by preseeding
4379 the apt-mirror-setup step. This is unfortunate, but for a lot of
4380 hardware it is the only option in Debian.&lt;/p&gt;
4381
4382 &lt;p&gt;The end result is two lines needed in your preseeding file to get
4383 firmware installed automatically by the installer:&lt;/p&gt;
4384
4385 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4386 base-installer base-installer/includes string isenkram-cli
4387 apt-mirror-setup apt-setup/non-free boolean true
4388 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4389
4390 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
4391 both firmware and user space packages when using this method. It also
4392 do not work well, so use version 0.15 or later. Installing both
4393 firmware and user space packages might give you a bit more than you
4394 want, so I decided to split the tasksel task in two, one for firmware
4395 and one for user space programs. The firmware task is enabled by
4396 default, while the one for user space programs is not. This split is
4397 implemented in the package currently in unstable.&lt;/p&gt;
4398
4399 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
4400 this recipe work for you. :)&lt;/p&gt;
4401
4402 &lt;p&gt;So, I bet you are wondering, how can this work. First and
4403 foremost, it work because tasksel is modular, and driven by whatever
4404 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4405 isenkram-cli package place two files for tasksel to find. First there
4406 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
4407
4408 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4409 Task: isenkram-packages
4410 Section: hardware
4411 Description: Hardware specific packages (autodetected by isenkram)
4412 Based on the detected hardware various hardware specific packages are
4413 proposed.
4414 Test-new-install: show show
4415 Relevance: 8
4416 Packages: for-current-hardware
4417
4418 Task: isenkram-firmware
4419 Section: hardware
4420 Description: Hardware specific firmware packages (autodetected by isenkram)
4421 Based on the detected hardware various hardware specific firmware
4422 packages are proposed.
4423 Test-new-install: mark show
4424 Relevance: 8
4425 Packages: for-current-hardware-firmware
4426 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4427
4428 &lt;p&gt;The key parts are Test-new-install which indicate how the task
4429 should be handled and the Packages line referencing to a script in
4430 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4431 list of packages to install. The for-current-hardware-firmware script
4432 look like this to list relevant firmware for the machine:
4433
4434 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4435 #!/bin/sh
4436 #
4437 PATH=/usr/sbin:$PATH
4438 export PATH
4439 isenkram-autoinstall-firmware -l
4440 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4441
4442 &lt;p&gt;With those two pieces in place, the firmware is installed by
4443 tasksel during the normal d-i run. :)&lt;/p&gt;
4444
4445 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
4446 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
4447 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
4448 install.&lt;/p&gt;
4449
4450 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
4451 pilots in testing this feature, as isenkram is used there now to
4452 install firmware, replacing the earlier scripts.&lt;/p&gt;
4453 </description>
4454 </item>
4455
4456 <item>
4457 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
4458 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
4459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
4460 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
4461 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
4462 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4463 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
4464 on a screen normally showing the bread types and prizes:&lt;/p&gt;
4465
4466 &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;
4467
4468 &lt;p&gt;If it had booted as it was supposed to, I would never had known
4469 about this hidden Linux installation. It is interesting what
4470 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
4471 </description>
4472 </item>
4473
4474 <item>
4475 <title>New lsdvd release version 0.17 is ready</title>
4476 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
4477 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
4478 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
4479 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
4480 got a new set of developers a few weeks ago, after the original
4481 developer decided to step down and pass the project to fresh blood.
4482 This project is now maintained by Petter Reinholdtsen and Steve
4483 Dibb.&lt;/p&gt;
4484
4485 &lt;p&gt;I just wrapped up
4486 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
4487 new lsdvd release&lt;/a&gt;, available in git or from
4488 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
4489 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
4490 0.17.&lt;/p&gt;
4491
4492 &lt;ul&gt;
4493
4494 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
4495 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
4496 non-existant, to work around additional copy protection&lt;/li&gt;
4497 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
4498 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
4499 &lt;li&gt;Fix include orders&lt;/li&gt;
4500 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
4501 &lt;li&gt;Fix the chapter count&lt;/li&gt;
4502 &lt;li&gt;Make sure the array size and the array limit used when initialising
4503 the palette size is the same.&lt;/li&gt;
4504 &lt;li&gt;Fix array printing.&lt;/li&gt;
4505 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
4506 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
4507 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
4508 with more GCC compiler warnings.&lt;/li&gt;
4509
4510 &lt;/ul&gt;
4511
4512 &lt;p&gt;This change bring together patches for lsdvd in use in various
4513 Linux and Unix distributions, as well as patches submitted to the
4514 project the last nine years. Please check it out. :)&lt;/p&gt;
4515 </description>
4516 </item>
4517
4518 <item>
4519 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
4520 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
4521 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
4522 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
4523 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4524 project&lt;/a&gt; provide a Linux solution for schools, including a
4525 powerful desktop with education software, a central server providing
4526 web pages, user database, user home directories, central login and PXE
4527 boot of both clients without disk and the installation to install Debian
4528 Edu on machines with disk (and a few other services perhaps to small
4529 to mention here). We in the Debian Edu team are currently working on
4530 the Jessie based version, trying to get everything in shape before the
4531 freeze, to avoid having to maintain our own package repository in the
4532 future. The
4533 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
4534 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
4535 work left. Some fatal problems block testing, breaking the installer,
4536 but it is possible to work around these to get anyway. Here is a
4537 recipe on how to get the installation limping along.&lt;/p&gt;
4538
4539 &lt;p&gt;First, download the test ISO via
4540 &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;,
4541 &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;
4542 or rsync (use
4543 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
4544 The ISO build was broken on Tuesday, so we do not get a new ISO every
4545 12 hours or so, but thankfully the ISO we already got we are able to
4546 install with some tweaking.&lt;/p&gt;
4547
4548 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
4549 (use Alt-Ctrl-F2), run&lt;/p&gt;
4550
4551 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4552 nano /usr/bin/edu-eatmydata-install
4553 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4554
4555 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
4556 optimization. Return to the installation, select the profile you want
4557 and continue. Without this change, exim4-config will fail to install
4558 due to a known bug in eatmydata.&lt;/p&gt;
4559
4560 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
4561 this do not work, figure out what your correct value would be. All my
4562 test machines need /dev/sda, so I have no advice if it do not fit
4563 your need.&lt;/p&gt;
4564
4565 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
4566 root after the initial boot from hard drive, and install the
4567 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4568 or mate. If you want several desktop options, install more than one
4569 metapackage. Once this is done, reboot and you should have a working
4570 graphical login screen. This workaround should no longer be needed
4571 once the education-tasks package version 1.801 enter testing in two
4572 days.&lt;/p&gt;
4573
4574 &lt;p&gt;I believe the ISO build will start working on two days when the new
4575 tasksel package enter testing and Steve McIntyre get a chance to
4576 update the debian-cd git repository. The eatmydata, grub and desktop
4577 issues are already fixed in unstable and testing, and should show up
4578 on the ISO as soon as the ISO build start working again. Well the
4579 eatmydata optimization is really just disabled. The proper fix
4580 require an upload by the eatmydata maintainer applying the patch
4581 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4582 The rest have proper fixes in unstable.&lt;/p&gt;
4583
4584 &lt;p&gt;I hope this get you going with the installation testing, as we are
4585 quickly running out of time trying to get our Jessie based
4586 installation ready before the distribution freeze in a month.&lt;/p&gt;
4587 </description>
4588 </item>
4589
4590 <item>
4591 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4592 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4593 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4594 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4595 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4596 to handle my fairly large DVD collection. It is a nice command line
4597 tool to get details about a DVD, like title, tracks, track length,
4598 etc, in XML, Perl or human readable format. But lsdvd have not seen
4599 any new development since 2006 and had a few irritating bugs affecting
4600 its use with some DVDs. Upstream seemed to be dead, and in January I
4601 sent a small probe asking for a version control repository for the
4602 project, without any reply. But I use it regularly and would like to
4603 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4604 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4605 the project admin, and after getting a reply from him explaining that
4606 he was no longer interested in the project, I asked if I could take
4607 over. And yesterday, I became project admin.&lt;/p&gt;
4608
4609 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4610 maintainer interested in joining forces to maintain the upstream
4611 project, and I hope we can get a new release out fairly quickly,
4612 collecting the patches spread around on the internet into on place.
4613 I&#39;ve added the relevant Debian patches to the freshly created git
4614 repository, and expect the Gentoo patches to make it too. If you got
4615 a DVD collection and care about command line tools, check out
4616 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4617 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4618 list&lt;/a&gt;. :)&lt;/p&gt;
4619 </description>
4620 </item>
4621
4622 <item>
4623 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4624 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4625 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4626 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4627 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4628 a lot quicker. When we install more than 2000 packages in
4629 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4630 tasksel in the installer, unpacking the binary packages take forever.
4631 A part of the slow I/O issue was discussed in
4632 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4633 much file system sync-ing done by dpkg, which is the package
4634 responsible for unpacking the binary packages. Other parts (like code
4635 executed by postinst scripts) might also sync to disk during
4636 installation. All this sync-ing to disk do not really make sense to
4637 me. If the machine crash half-way through, I start over, I do not try
4638 to salvage the half installed system. So the failure sync-ing is
4639 supposed to protect against, hardware or system crash, is not really
4640 relevant while the installer is running.&lt;/p&gt;
4641
4642 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4643 system sync()-ing in a fairly non-intrusive way, without the need to
4644 change the code in several packages. The idea is not new, but I have
4645 not heard anyone propose the approach using dpkg-divert before. It
4646 depend on the small and clever package
4647 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4648 uses LD_PRELOAD to replace the system functions for syncing data to
4649 disk with functions doing nothing, thus allowing programs to live
4650 dangerous while speeding up disk I/O significantly. Instead of
4651 modifying the implementation of dpkg, apt and tasksel (which are the
4652 packages responsible for selecting, fetching and installing packages),
4653 it occurred to me that we could just divert the programs away, replace
4654 them with a simple shell wrapper calling
4655 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4656 Two days ago I decided to test the idea, and wrapped up a simple
4657 implementation for the Debian Edu udeb.&lt;/p&gt;
4658
4659 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4660 time of the pkgsel step (installing tasks) from 64 to less than 44
4661 minutes (20 minutes shaved off the installation) on an old Dell
4662 Latitude D505 machine. I am not quite sure what the optimised time
4663 would have been, as I messed up the testing a bit, causing the debconf
4664 priority to get low enough for two questions to pop up during
4665 installation. As soon as I saw the questions I moved the installation
4666 along, but do not know how long the question were holding up the
4667 installation. I did some more measurements using Debian Edu Jessie,
4668 and got these results. The time measured is the time stamp in
4669 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4670 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4671 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4672 timing thus do not depend on how quickly the user handle the tasksel
4673 dialog.&lt;/p&gt;
4674
4675 &lt;p&gt;&lt;table&gt;
4676
4677 &lt;tr&gt;
4678 &lt;th&gt;Machine/setup&lt;/th&gt;
4679 &lt;th&gt;Original tasksel&lt;/th&gt;
4680 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4681 &lt;th&gt;Reduction&lt;/th&gt;
4682 &lt;/tr&gt;
4683
4684 &lt;tr&gt;
4685 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4686 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4687 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4688 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4689 &lt;/tr&gt;
4690
4691 &lt;tr&gt;
4692 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4693 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4694 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4695 &lt;td&gt;23 min 40%&lt;/td&gt;
4696 &lt;/tr&gt;
4697
4698 &lt;tr&gt;
4699 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4700 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4701 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4702 &lt;td&gt;11 min 50%&lt;/td&gt;
4703 &lt;/tr&gt;
4704
4705 &lt;tr&gt;
4706 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4707 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4708 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4709 &lt;td&gt;2 min 33%&lt;/td&gt;
4710 &lt;/tr&gt;
4711
4712 &lt;tr&gt;
4713 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4714 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4715 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4716 &lt;td&gt;4 min 21%&lt;/td&gt;
4717 &lt;/tr&gt;
4718
4719 &lt;/table&gt;&lt;/p&gt;
4720
4721 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4722 time is spent downloading packages. The connection to the Internet
4723 was 100Mbit/s during testing, so downloading should not be a
4724 significant factor in the measurement. Download typically took a few
4725 seconds to a few minutes, depending on the amount of packages being
4726 installed.&lt;/p&gt;
4727
4728 &lt;p&gt;The speedup is implemented by using two hooks in
4729 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4730 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4731 finish-install.d hook to remove the divert at the end of the
4732 installation. I picked the pre-pkgsel.d hook instead of the
4733 post-base-installer.d hook because I test using an ISO without the
4734 eatmydata package included, and the post-base-installer.d hook in
4735 Debian Edu can only operate on packages included in the ISO. The
4736 negative effect of this is that I am unable to activate this
4737 optimization for the kernel installation step in d-i. If the code is
4738 moved to the post-base-installer.d hook, the speedup would be larger
4739 for the entire installation.&lt;/p&gt;
4740
4741 &lt;p&gt;I&#39;ve implemented this in the
4742 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4743 git repository, and plan to provide the optimization as part of the
4744 Debian Edu installation. If you want to test this yourself, you can
4745 create two files in the installer (or in an udeb). One shell script
4746 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4747
4748 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4749 #!/bin/sh
4750 set -e
4751 . /usr/share/debconf/confmodule
4752 info() {
4753 logger -t my-pkgsel &quot;info: $*&quot;
4754 }
4755 error() {
4756 logger -t my-pkgsel &quot;error: $*&quot;
4757 }
4758 override_install() {
4759 apt-install eatmydata || true
4760 if [ -x /target/usr/bin/eatmydata ] ; then
4761 for bin in dpkg apt-get aptitude tasksel ; do
4762 file=/usr/bin/$bin
4763 # Test that the file exist and have not been diverted already.
4764 if [ -f /target$file ] ; then
4765 info &quot;diverting $file using eatmydata&quot;
4766 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4767 &gt; /target$file.edu
4768 chmod 755 /target$file.edu
4769 in-target dpkg-divert --package debian-edu-config \
4770 --rename --quiet --add $file
4771 ln -sf ./$bin.edu /target$file
4772 else
4773 error &quot;unable to divert $file, as it is missing.&quot;
4774 fi
4775 done
4776 else
4777 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4778 fi
4779 }
4780
4781 override_install
4782 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4783
4784 &lt;p&gt;To clean up, another shell script should go into
4785 /usr/lib/finish-install.d/ with code like this:
4786
4787 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4788 #! /bin/sh -e
4789 . /usr/share/debconf/confmodule
4790 error() {
4791 logger -t my-finish-install &quot;error: $@&quot;
4792 }
4793 remove_install_override() {
4794 for bin in dpkg apt-get aptitude tasksel ; do
4795 file=/usr/bin/$bin
4796 if [ -x /target$file.edu ] ; then
4797 rm /target$file
4798 in-target dpkg-divert --package debian-edu-config \
4799 --rename --quiet --remove $file
4800 rm /target$file.edu
4801 else
4802 error &quot;Missing divert for $file.&quot;
4803 fi
4804 done
4805 sync # Flush file buffers before continuing
4806 }
4807
4808 remove_install_override
4809 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4810
4811 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4812 edu-eatmydata-install and call it from the pre-pkgsel.d and
4813 finish-install.d scripts.&lt;/p&gt;
4814
4815 &lt;p&gt;By now you might ask if this change should get into the normal
4816 Debian installer too? I suspect it should, but am not sure the
4817 current debian-installer coordinators find it useful enough. It also
4818 depend on the side effects of the change. I&#39;m not aware of any, but I
4819 guess we will see if the change is safe after some more testing.
4820 Perhaps there is some package in Debian depending on sync() and
4821 fsync() having effect? Perhaps it should go into its own udeb, to
4822 allow those of us wanting to enable it to do so without affecting
4823 everyone.&lt;/p&gt;
4824
4825 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4826 will break installation of all programs using gnutls because of
4827 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4828 eatmydata package in Debian will solve it.&lt;/p&gt;
4829
4830 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4831 the optimization work again. And I have discovered that the
4832 dpkg-divert trick is not really needed and implemented a slightly
4833 simpler approach as part of the debian-edu-install package. See
4834 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4835
4836 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4837 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4838 triggering on i386 made it into testing, and broke this installation
4839 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4840 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4841 </description>
4842 </item>
4843
4844 <item>
4845 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4846 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4847 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4848 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4849 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4850 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4851 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4852 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4853 learn that there is a large set of publicly available key servers to
4854 use when looking for peoples public key. So far I have used
4855 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4856 were misbehaving, but those days are ended. The servers I have used
4857 up until yesterday have been slow and some times unavailable. I hope
4858 those problems are gone now.&lt;/p&gt;
4859
4860 &lt;p&gt;Behind the round robin DNS entry of the
4861 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4862 there is a pool of more than 100 keyservers which are checked every
4863 day to ensure they are well connected and up to date. It must be
4864 better than what I have used so far. :)&lt;/p&gt;
4865
4866 &lt;p&gt;Yesterdays speaker told me that the service is the default
4867 keyserver provided by the default configuration in GnuPG, but this do
4868 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4869
4870 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4871 line:&lt;/p&gt;
4872
4873 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4874 keyserver pool.sks-keyservers.net
4875 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4876
4877 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4878 entries in DNS. Just for fun, I did just that at work, so now every
4879 user of GnuPG at the University of Oslo should find a OpenGPG
4880 keyserver automatically should their need it:&lt;/p&gt;
4881
4882 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4883 % host -t srv _pgpkey-http._tcp.uio.no
4884 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4885 %
4886 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4887
4888 &lt;p&gt;Now if only
4889 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4890 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4891 very happy. It can look up a given key or search for a user ID, but I
4892 normally do not want that, but to find a trust path from my key to
4893 another key. Given a user ID or key ID, I would like to find (and
4894 download) the keys representing a signature path from my key to the
4895 key in question, to be able to get a trust path between the two keys.
4896 This is as far as I can tell not possible today. Perhaps something
4897 for a future version of the protocol?&lt;/p&gt;
4898 </description>
4899 </item>
4900
4901 <item>
4902 <title>From English wiki to translated PDF and epub via Docbook</title>
4903 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4905 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4906 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4907 project&lt;/a&gt; provide an instruction manual for teachers, system
4908 administrators and other users that contain useful tips for setting up
4909 and maintaining a Debian Edu installation. This text is about how the
4910 text processing of this manual is handled in the project.&lt;/p&gt;
4911
4912 &lt;p&gt;One goal of the project is to provide information in the native
4913 language of its users, and for this we need to handle translations.
4914 But we also want to make sure each language contain the same
4915 information, so for this we need a good way to keep the translations
4916 in sync. And we want it to be easy for our users to improve the
4917 documentation, avoiding the need to learn special formats or tools to
4918 contribute, and the obvious way to do this is to make it possible to
4919 edit the documentation using a web browser. We also want it to be
4920 easy for translators to keep the translation up to date, and give them
4921 help in figuring out what need to be translated. Here is the list of
4922 tools and the process we have found trying to reach all these
4923 goals.&lt;/p&gt;
4924
4925 &lt;p&gt;We maintain the authoritative source of our manual in the
4926 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4927 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4928 front page with references to the different chapters, several pages
4929 for each chapter, and finally one &quot;collection page&quot; gluing all the
4930 chapters together into one large web page (aka
4931 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4932 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4933 processing and translations. Thanks to the fact that the
4934 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4935 wiki.debian.org support exporting pages in
4936 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4937 the list of pages to export using the raw version of the AllInOne
4938 page, loop over each of them to generate a Docbook XML version of the
4939 manual. This process also download images and transform image
4940 references to use the locally downloaded images. The generated
4941 Docbook XML files are slightly broken, so some post-processing is done
4942 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4943 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4944 a handfull of images. The XML file can now be used to generate PDF, HTML
4945 and epub versions of the English manual. This is the basic step of
4946 our process, making PDF (using dblatex), HTML (using xsltproc) and
4947 epub (using dbtoepub) version from Docbook XML, and the resulting files
4948 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4949
4950 &lt;p&gt;But English documentation is not enough for us. We want translated
4951 documentation too, and we want to make it easy for translators to
4952 track the English original. For this we use the
4953 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4954 which allow us to transform the English Docbook XML file into a
4955 translation file (a .pot file), usable with the normal gettext based
4956 translation tools used by those translating free software. The pot
4957 file is used to create and maintain translation files (several .po
4958 files), which the translations update with the native language
4959 translations of all titles, paragraphs and blocks of text in the
4960 original. The next step is combining the original English Docbook XML
4961 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4962 create a translated Docbook XML file (in this case
4963 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4964 translated, if the translation is not complete) Docbook XML file can
4965 then be used like the original to create a PDF, HTML and epub version
4966 of the documentation.&lt;/p&gt;
4967
4968 &lt;p&gt;The translators use different tools to edit the .po files. We
4969 recommend using
4970 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4971 while some use emacs and vi, others can use web based editors like
4972 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4973 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4974 is where the .po file end up, in our git repository. Updated
4975 translations can either be committed directly to git, or submitted as
4976 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4977 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4978
4979 &lt;p&gt;One challenge is images, which both might need to be translated (if
4980 they show translated user applications), and are needed in different
4981 formats when creating PDF and HTML versions (epub is a HTML version in
4982 this regard). For this we transform the original PNG images to the
4983 needed density and format during build, and have a way to provide
4984 translated images by storing translated versions in
4985 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4986 package maintainers know more.&lt;/p&gt;
4987
4988 &lt;p&gt;If you wonder what the result look like, we provide
4989 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4990 of the documentation packages on the web&lt;/a&gt;. See for example the
4991 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4992 PDF version&lt;/a&gt; or the
4993 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4994 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4995 but perhaps it will be done in the future.&lt;/p&gt;
4996
4997 &lt;p&gt;To learn more, check out
4998 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4999 debian-edu-doc package&lt;/a&gt;,
5000 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
5001 manual on the wiki&lt;/a&gt; and
5002 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
5003 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
5004 </description>
5005 </item>
5006
5007 <item>
5008 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
5009 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
5010 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
5011 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
5012 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
5013 related packages relevant for the computer installed automatically.
5014 So I implemented one, using
5015 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
5016 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
5017 run tasksel as user root. You should be presented with a new option,
5018 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
5019 select it, tasksel will install the packages isenkram claim is fit for
5020 the current hardware, hot pluggable or not.&lt;p&gt;
5021
5022 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
5023 description, and the other is the script used to extract the list of
5024 packages to install. The first part is in
5025 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
5026 this:&lt;/p&gt;
5027
5028 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5029 Task: isenkram
5030 Section: hardware
5031 Description: Hardware specific packages (autodetected by isenkram)
5032 Based on the detected hardware various hardware specific packages are
5033 proposed.
5034 Test-new-install: mark show
5035 Relevance: 8
5036 Packages: for-current-hardware
5037 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5038
5039 &lt;p&gt;The second part is in
5040 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
5041 this:&lt;/p&gt;
5042
5043 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5044 #!/bin/sh
5045 #
5046 (
5047 isenkram-lookup
5048 isenkram-autoinstall-firmware -l
5049 ) | sort -u
5050 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5051
5052 &lt;p&gt;All in all, a very short and simple implementation making it
5053 trivial to install the hardware dependent package we all may want to
5054 have installed on our machines. I&#39;ve not been able to find a way to
5055 get tasksel to tell you exactly which packages it plan to install
5056 before doing the installation. So if you are curious or careful,
5057 check the output from the isenkram-* command line tools first.&lt;/p&gt;
5058
5059 &lt;p&gt;The information about which packages are handling which hardware is
5060 fetched either from the isenkram package itself in
5061 /usr/share/isenkram/, from git.debian.org or from the APT package
5062 database (using the Modaliases header). The APT package database
5063 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5064 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
5065 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
5066 the python-apt code (bug
5067 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
5068 workaround I was able to get rid of the file descriptor leak and
5069 reduce the memory leak from ~30 MiB per hardware detection down to
5070 around 2 MiB per hardware detection. It should make the desktop
5071 daemon a lot more useful. The fix is in version 0.7 uploaded to
5072 unstable today.&lt;/p&gt;
5073
5074 &lt;p&gt;I believe the current way of mapping hardware to packages in
5075 Isenkram is is a good draft, but in the future I expect isenkram to
5076 use the AppStream data source for this. A proposal for getting proper
5077 AppStream support into Debian is floating around as
5078 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
5079 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
5080 project&lt;/a&gt; will take place this summer to improve the situation. I
5081 look forward to seeing the result, and welcome patches for isenkram to
5082 start using the information when it is ready.&lt;/p&gt;
5083
5084 &lt;p&gt;If you want your package to map to some specific hardware, either
5085 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
5086 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
5087 package&lt;/a&gt; or submit a bug report with the details to the isenkram
5088 package. See also
5089 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
5090 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
5091 the information will be migrated to AppStream eventually, but for the
5092 moment I got no better place to store it.&lt;/p&gt;
5093 </description>
5094 </item>
5095
5096 <item>
5097 <title>FreedomBox milestone - all packages now in Debian Sid</title>
5098 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
5099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
5100 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
5101 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5102 project&lt;/a&gt; is working on providing the software and hardware to make
5103 it easy for non-technical people to host their data and communication
5104 at home, and being able to communicate with their friends and family
5105 encrypted and away from prying eyes. It is still going strong, and
5106 today a major mile stone was reached.&lt;/p&gt;
5107
5108 &lt;p&gt;Today, the last of the packages currently used by the project to
5109 created the system images were accepted into Debian Unstable. It was
5110 the freedombox-setup package, which is used to configure the images
5111 during build and on the first boot. Now all one need to get going is
5112 the build code from the freedom-maker git repository and packages from
5113 Debian. And once the freedombox-setup package enter testing, we can
5114 build everything directly from Debian. :)&lt;/p&gt;
5115
5116 &lt;p&gt;Some key packages used by Freedombox are
5117 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
5118 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
5119 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
5120 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
5121 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
5122 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
5123 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
5124 are plans to integrate more packages into the setup. User
5125 documentation is maintained on the Debian wiki. Please
5126 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
5127 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
5128
5129 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
5130 setup, run this on a Debian machine using a user with sudo rights to
5131 become root:&lt;/p&gt;
5132
5133 &lt;p&gt;&lt;pre&gt;
5134 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5135 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5136 u-boot-tools
5137 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5138 freedom-maker
5139 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5140 &lt;/pre&gt;&lt;/p&gt;
5141
5142 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5143 devices. See the README in the freedom-maker git repo for more
5144 details on the build. If you do not want all three images, trim the
5145 make line. Note that the virtualbox-image target is not really
5146 virtualbox specific. It create a x86 image usable in kvm, qemu,
5147 vmware and any other x86 virtual machine environment. You might need
5148 the version of vmdebootstrap in Jessie to get the build working, as it
5149 include fixes for a race condition with kpartx.&lt;/p&gt;
5150
5151 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5152 method, boot a Debian Wheezy ISO and use this boot argument to load
5153 the preseed values:&lt;/p&gt;
5154
5155 &lt;p&gt;&lt;pre&gt;
5156 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;
5157 &lt;/pre&gt;&lt;/p&gt;
5158
5159 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
5160 it still work.&lt;/p&gt;
5161
5162 &lt;p&gt;If you wonder how to help, one task you could look at is using
5163 systemd as the boot system. It will become the default for Linux in
5164 Jessie, so we need to make sure it is usable on the Freedombox. I did
5165 a simple test a few weeks ago, and noticed dnsmasq failed to start
5166 during boot when using systemd. I suspect there are other problems
5167 too. :) To detect problems, there is a test suite included, which can
5168 be run from the plinth web interface.&lt;/p&gt;
5169
5170 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5171 us get the new release published. :) Please join us on
5172 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5173 irc.debian.org)&lt;/a&gt; and
5174 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5175 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5176 </description>
5177 </item>
5178
5179 <item>
5180 <title>S3QL, a locally mounted cloud file system - nice free software</title>
5181 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
5182 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
5183 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
5184 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
5185 solution for use at home. My requirements are simple, it must be
5186 cheap and locally encrypted (in other words, I keep the encryption
5187 keys, the storage provider do not have access to my private files).
5188 One idea me and my friends had many years ago, before the cloud
5189 storage providers showed up, was to use Google mail as storage,
5190 writing a Linux block device storing blocks as emails in the mail
5191 service provided by Google, and thus get heaps of free space. On top
5192 of this one can add encryption, RAID and volume management to have
5193 lots of (fairly slow, I admit that) cheap and encrypted storage. But
5194 I never found time to implement such system. But the last few weeks I
5195 have looked at a system called
5196 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
5197 mounted network backed file system with the features I need.&lt;/p&gt;
5198
5199 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
5200 handling several different storage providers, any with Amazon S3,
5201 Google Drive or OpenStack API. There are heaps of such storage
5202 providers. S3QL can also use a local directory as storage, which
5203 combined with sshfs allow for file storage on any ssh server. S3QL
5204 include support for encryption, compression, de-duplication, snapshots
5205 and immutable file systems, allowing me to mount the remote storage as
5206 a local mount point, look at and use the files as if they were local,
5207 while the content is stored in the cloud as well. This allow me to
5208 have a backup that should survive fire. The file system can not be
5209 shared between several machines at the same time, as only one can
5210 mount it at the time, but any machine with the encryption key and
5211 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
5212
5213 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
5214 package is included already. So to get started, run &lt;tt&gt;apt-get
5215 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
5216 Greenqloud, after reading their nice recipe on
5217 &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
5218 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
5219 in Iceland more than those in USA when it come to keeping my personal
5220 data safe and private, and thus would rather spend money on a company
5221 in Iceland. Another nice recipe is available from the article
5222 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
5223 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
5224 Admin magazine. When the provider is picked, figure out how to get
5225 the API key needed to connect to the storage API. With Greencloud,
5226 the key did not show up until I had added payment details to my
5227 account.&lt;/p&gt;
5228
5229 &lt;p&gt;Armed with the API access details, it is time to create the file
5230 system. First, create a new bucket in the cloud. This bucket is the
5231 file system storage area. I picked a bucket name reflecting the
5232 machine that was going to store data there, but any name will do.
5233 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
5234 the API login and password, and a locally created password. Store it
5235 all in ~root/.s3ql/authinfo2 like this:
5236
5237 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5238 [s3c]
5239 storage-url: s3c://s.greenqloud.com:443/bucket-name
5240 backend-login: API-login
5241 backend-password: API-password
5242 fs-passphrase: local-password
5243 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5244
5245 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
5246 but any sensible way to create a fairly random password should do it.
5247 Armed with these details, it is now time to run mkfs, entering the API
5248 details and password to create it:&lt;/p&gt;
5249
5250 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5251 # mkdir -m 700 /var/lib/s3ql-cache
5252 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5253 --ssl s3c://s.greenqloud.com:443/bucket-name
5254 Enter backend login:
5255 Enter backend password:
5256 Before using S3QL, make sure to read the user&#39;s guide, especially
5257 the &#39;Important Rules to Avoid Loosing Data&#39; section.
5258 Enter encryption password:
5259 Confirm encryption password:
5260 Generating random encryption key...
5261 Creating metadata tables...
5262 Dumping metadata...
5263 ..objects..
5264 ..blocks..
5265 ..inodes..
5266 ..inode_blocks..
5267 ..symlink_targets..
5268 ..names..
5269 ..contents..
5270 ..ext_attributes..
5271 Compressing and uploading metadata...
5272 Wrote 0.00 MB of compressed metadata.
5273 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5274
5275 &lt;p&gt;The next step is mounting the file system to make the storage available.
5276
5277 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5278 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5279 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5280 Using 4 upload threads.
5281 Downloading and decompressing metadata...
5282 Reading metadata...
5283 ..objects..
5284 ..blocks..
5285 ..inodes..
5286 ..inode_blocks..
5287 ..symlink_targets..
5288 ..names..
5289 ..contents..
5290 ..ext_attributes..
5291 Mounting filesystem...
5292 # df -h /s3ql
5293 Filesystem Size Used Avail Use% Mounted on
5294 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
5295 #
5296 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5297
5298 &lt;p&gt;The file system is now ready for use. I use rsync to store my
5299 backups in it, and as the metadata used by rsync is downloaded at
5300 mount time, no network traffic (and storage cost) is triggered by
5301 running rsync. To unmount, one should not use the normal umount
5302 command, as this will not flush the cache to the cloud storage, but
5303 instead running the umount.s3ql command like this:
5304
5305 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5306 # umount.s3ql /s3ql
5307 #
5308 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5309
5310 &lt;p&gt;There is a fsck command available to check the file system and
5311 correct any problems detected. This can be used if the local server
5312 crashes while the file system is mounted, to reset the &quot;already
5313 mounted&quot; flag. This is what it look like when processing a working
5314 file system:&lt;/p&gt;
5315
5316 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5317 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
5318 Using cached metadata.
5319 File system seems clean, checking anyway.
5320 Checking DB integrity...
5321 Creating temporary extra indices...
5322 Checking lost+found...
5323 Checking cached objects...
5324 Checking names (refcounts)...
5325 Checking contents (names)...
5326 Checking contents (inodes)...
5327 Checking contents (parent inodes)...
5328 Checking objects (reference counts)...
5329 Checking objects (backend)...
5330 ..processed 5000 objects so far..
5331 ..processed 10000 objects so far..
5332 ..processed 15000 objects so far..
5333 Checking objects (sizes)...
5334 Checking blocks (referenced objects)...
5335 Checking blocks (refcounts)...
5336 Checking inode-block mapping (blocks)...
5337 Checking inode-block mapping (inodes)...
5338 Checking inodes (refcounts)...
5339 Checking inodes (sizes)...
5340 Checking extended attributes (names)...
5341 Checking extended attributes (inodes)...
5342 Checking symlinks (inodes)...
5343 Checking directory reachability...
5344 Checking unix conventions...
5345 Checking referential integrity...
5346 Dropping temporary indices...
5347 Backing up old metadata...
5348 Dumping metadata...
5349 ..objects..
5350 ..blocks..
5351 ..inodes..
5352 ..inode_blocks..
5353 ..symlink_targets..
5354 ..names..
5355 ..contents..
5356 ..ext_attributes..
5357 Compressing and uploading metadata...
5358 Wrote 0.89 MB of compressed metadata.
5359 #
5360 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5361
5362 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
5363 quick, about the same speed as local file access. Uploading large
5364 amount of data is to me limited by the bandwidth out of and into my
5365 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
5366 which is very close to my upload speed, and downloading the same
5367 Debian installation ISO gave me 610 kiB/s, close to my download speed.
5368 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
5369 network, not the file system code. I do not know what a good cache
5370 size would be, but suspect that the cache should e larger than your
5371 working set.&lt;/p&gt;
5372
5373 &lt;p&gt;I mentioned that only one machine can mount the file system at the
5374 time. If another machine try, it is told that the file system is
5375 busy:&lt;/p&gt;
5376
5377 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5378 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5379 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5380 Using 8 upload threads.
5381 Backend reports that fs is still mounted elsewhere, aborting.
5382 #
5383 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5384
5385 &lt;p&gt;The file content is uploaded when the cache is full, while the
5386 metadata is uploaded once every 24 hour by default. To ensure the
5387 file system content is flushed to the cloud, one can either umount the
5388 file system, or ask S3QL to flush the cache and metadata using
5389 s3qlctrl:
5390
5391 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5392 # s3qlctrl upload-meta /s3ql
5393 # s3qlctrl flushcache /s3ql
5394 #
5395 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5396
5397 &lt;p&gt;If you are curious about how much space your data uses in the
5398 cloud, and how much compression and deduplication cut down on the
5399 storage usage, you can use s3qlstat on the mounted file system to get
5400 a report:&lt;/p&gt;
5401
5402 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5403 # s3qlstat /s3ql
5404 Directory entries: 9141
5405 Inodes: 9143
5406 Data blocks: 8851
5407 Total data size: 22049.38 MB
5408 After de-duplication: 21955.46 MB (99.57% of total)
5409 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
5410 Database size: 2.39 MB (uncompressed)
5411 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5412 #
5413 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5414
5415 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
5416 storage. I did not try to locate them all, but am aware of at least
5417 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
5418 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
5419 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
5420 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
5421 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
5422 accept payment in Bitcoin. Pick one that suit your need. Some of
5423 them provide several GiB of free storage, but the prize models are
5424 quite different and you will have to figure out what suits you
5425 best.&lt;/p&gt;
5426
5427 &lt;p&gt;While researching this blog post, I had a look at research papers
5428 and posters discussing the S3QL file system. There are several, which
5429 told me that the file system is getting a critical check by the
5430 science community and increased my confidence in using it. One nice
5431 poster is titled
5432 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
5433 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5434 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
5435 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5436 and Pamela Smith. Please have a look.&lt;/p&gt;
5437
5438 &lt;p&gt;Given my problems with different file systems earlier, I decided to
5439 check out the mounted S3QL file system to see if it would be usable as
5440 a home directory (in other word, that it provided POSIX semantics when
5441 it come to locking and umask handling etc). Running
5442 &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
5443 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
5444 no error was found. So the file system can be used for home
5445 directories, if one chooses to do so.&lt;/p&gt;
5446
5447 &lt;p&gt;If you do not want a locally file system, and want something that
5448 work without the Linux fuse file system, I would like to mention the
5449 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
5450 provide locally encrypted backup using a command line client. It have
5451 a nicer access control system, where one can split out read and write
5452 access, allowing some systems to write to the backup and others to
5453 only read from it.&lt;/p&gt;
5454
5455 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5456 activities, please send Bitcoin donations to my address
5457 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5458 </description>
5459 </item>
5460
5461 <item>
5462 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
5463 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
5464 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
5465 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
5466 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5467 project&lt;/a&gt; is working on providing the software and hardware for
5468 making it easy for non-technical people to host their data and
5469 communication at home, and being able to communicate with their
5470 friends and family encrypted and away from prying eyes. It has been
5471 going on for a while, and is slowly progressing towards a new test
5472 release (0.2).&lt;/p&gt;
5473
5474 &lt;p&gt;And what day could be better than the Pi day to announce that the
5475 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
5476 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5477 system), and can also be installed using a Debian installer preseed
5478 file. The Debian based Freedombox is now based on Debian Jessie,
5479 where most of the needed packages used are already present. Only one,
5480 the freedombox-setup package, is missing. To try to build your own
5481 boot image to test the current status, fetch the freedom-maker scripts
5482 and build using
5483 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
5484 with a user with sudo access to become root:
5485
5486 &lt;pre&gt;
5487 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5488 freedom-maker
5489 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5490 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5491 u-boot-tools
5492 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5493 &lt;/pre&gt;
5494
5495 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5496 devices. See the README for more details on the build. If you do not
5497 want all three images, trim the make line. But note that thanks to &lt;a
5498 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
5499 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
5500 kpartx call.&lt;/p&gt;
5501
5502 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5503 method, boot a Debian Wheezy ISO and use this boot argument to load
5504 the preseed values:&lt;/p&gt;
5505
5506 &lt;pre&gt;
5507 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;
5508 &lt;/pre&gt;
5509
5510 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
5511 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
5512 currently hang while setting up APT sources. Killing the
5513 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
5514 installation will get the installation going. This affect all
5515 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
5516
5517 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5518 us get the new release published. :) Please join us on
5519 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5520 irc.debian.org)&lt;/a&gt; and
5521 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5522 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5523 </description>
5524 </item>
5525
5526 <item>
5527 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
5528 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
5529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
5530 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
5531 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
5532 innetgr tools, because I needed them in
5533 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
5534 ng-utils, and it has served me well. I placed the project under the
5535 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
5536 repository. But many years ago, the CVS repository was dropped (lost,
5537 not migrated to new hardware, not sure), and the project have lacked a
5538 proper home since then.&lt;/p&gt;
5539
5540 &lt;p&gt;Last summer, I had a look at the package and made a new release
5541 fixing a irritating crash bug, but was unable to store the changes in
5542 a proper source control system. I applied for a project on
5543 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
5544 to follow up on it. Until today. :)&lt;/p&gt;
5545
5546 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
5547 now have a new home, and a git repository with the highlight of the
5548 history of the project. I published all release tarballs and imported
5549 them into the git repository. As the project is really stable and not
5550 expected to gain new features any time soon, I decided to make a new
5551 release and call it 1.0. Visit the new project home on
5552 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
5553 if you want to check it out. The new version is also uploaded into
5554 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
5555 </description>
5556 </item>
5557
5558 <item>
5559 <title>Testing sysvinit from experimental in Debian Hurd</title>
5560 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
5561 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
5562 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
5563 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
5564 their changes into sysvinit, to allow them to use the normal sysvinit
5565 boot system instead of their old one. This follow up on the
5566 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
5567 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
5568 get Debian on Hurd working more like Debian on Linux. To get started,
5569 I downloaded a prebuilt hard disk image from
5570 &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;,
5571 and started it using virt-manager.&lt;/p&gt;
5572
5573 &lt;p&gt;The first think I had to do after logging in (root without any
5574 password) was to get the network operational. I followed
5575 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5576 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5577 commands as root to get the machine to accept a IP address from the
5578 kvm internal DHCP server:&lt;/p&gt;
5579
5580 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5581 settrans -fgap /dev/netdde /hurd/netdde
5582 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5583 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5584 dhclient /dev/eth0
5585 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5586
5587 &lt;p&gt;After this, the machine had internet connectivity, and I could
5588 upgrade it and install the sysvinit packages from experimental and
5589 enable it as the default boot system in Hurd.&lt;/p&gt;
5590
5591 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5592 running on the machine it for ssh login to work a password need to be
5593 set. Also, note that a bug somewhere in openssh on Hurd block
5594 compression from working. Remember to turn that off on the client
5595 side.&lt;/p&gt;
5596
5597 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5598 stuff:&lt;/p&gt;
5599
5600 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5601 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5602 deb http://http.debian.net/debian/ experimental main
5603 EOF
5604 apt-get update
5605 apt-get dist-upgrade
5606 apt-get install -t experimental initscripts sysv-rc sysvinit \
5607 sysvinit-core sysvinit-utils
5608 update-alternatives --config runsystem
5609 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5610
5611 &lt;p&gt;To reboot after switching boot system, you have to use
5612 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5613 yet a sysvinit process able to receive the signals from the normal
5614 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5615 upgrading every package and rebooting, the network come up with DHCP
5616 after boot as it should, and the settrans/pkill hack mentioned at the
5617 start is no longer needed. But for some strange reason, there are no
5618 longer any login prompt in the virtual console, so I logged in using
5619 ssh instead.
5620
5621 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5622 fail some times. No idea what the cause is, but hope the Hurd porters
5623 figure it out. At least Justus said on IRC (#debian-hurd on
5624 irc.debian.org) that they are aware of the problem. A way to reduce
5625 the impact is to upgrade to the Hurd packages built by Justus by
5626 adding this repository to the machine:&lt;/p&gt;
5627
5628 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5629 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5630 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5631 EOF
5632 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5633
5634 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5635 http://ftp.debian-ports.org/debian, because some of the packages in
5636 unstable do not yet include the required patches that are lingering in
5637 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5638
5639 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5640 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5641 i emacs - GNU Emacs editor (metapackage)
5642 i gdb - GNU Debugger
5643 i hurd-recommended - Miscellaneous translators
5644 i isc-dhcp-client - ISC DHCP client
5645 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5646 i libc-bin - Embedded GNU C Library: Binaries
5647 i libc-dev-bin - Embedded GNU C Library: Development binaries
5648 i libc0.3 - Embedded GNU C Library: Shared libraries
5649 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5650 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5651 i multiarch-support - Transitional package to ensure multiarch compatibilit
5652 i A x11-common - X Window System (X.Org) infrastructure
5653 i xorg - X.Org X Window System
5654 i A xserver-xorg - X.Org X server
5655 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5656 #
5657 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5658
5659 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5660 X.org did not work out of the box and I never took the time to follow
5661 the porters instructions to fix it. This time I was interested in the
5662 command line stuff.&lt;p&gt;
5663 </description>
5664 </item>
5665
5666 <item>
5667 <title>New chrpath release 0.16</title>
5668 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5669 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5670 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5671 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5672 find problems in C, C++ and Java code using static source code
5673 analysis. It can detect a lot of different problems, and is very
5674 useful to find memory and locking bugs in the error handling part of
5675 the source. The company behind it provide
5676 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5677 a community service&lt;/a&gt;, and many hundred free software projects are
5678 already checked. A few days ago I decided to have a closer look at
5679 the Coverity system, and discovered that the
5680 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5681 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5682 projects I am involved with was already registered. But these are
5683 fairly big, and I would also like to have a small and easy project to
5684 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5685 checking of the chrpath project&lt;/a&gt;. It was
5686 added to the checker and discovered seven potential defects. Six of
5687 these were real, mostly resource &quot;leak&quot; when the program detected an
5688 error. Nothing serious, as the resources would be released a fraction
5689 of a second later when the program exited because of the error, but it
5690 is nice to do it right in case the source of the program some time in
5691 the future end up in a library. Having fixed all defects and added
5692 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5693 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5694 publish a new release. These are the release notes:&lt;/p&gt;
5695
5696 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5697
5698 &lt;ul&gt;
5699
5700 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5701 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5702 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5703
5704 &lt;/ul&gt;
5705
5706 &lt;p&gt;You can
5707 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5708 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5709 project if something is wrong with the new release. The test suite
5710 did not discover any old errors, so if you find a new one, please also
5711 include a test suite check.&lt;/p&gt;
5712 </description>
5713 </item>
5714
5715 <item>
5716 <title>New chrpath release 0.15</title>
5717 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5719 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5720 <description>&lt;p&gt;After many years break from the package and a vain hope that
5721 development would be continued by someone else, I finally pulled my
5722 acts together this morning and wrapped up a new release of chrpath,
5723 the command line tool to modify the rpath and runpath of already
5724 compiled ELF programs. The update was triggered by the persistence of
5725 Isha Vishnoi at IBM, which needed a new config.guess file to get
5726 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5727 is working on. I checked the
5728 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5729 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5730 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5731 packages for interesting patches (failed to find the source from
5732 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5733 These are the release notes:&lt;/p&gt;
5734
5735 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5736
5737 &lt;ul&gt;
5738
5739 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5740 with newer architectures. Thanks to isha vishnoi for the heads
5741 up.&lt;/li&gt;
5742
5743 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5744
5745 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5746 Matthias Klose.&lt;/li&gt;
5747
5748 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5749 Petr Machata found in Fedora.&lt;/li&gt;
5750
5751 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5752 .dynamic is a NULL terminated string. Based on patch found in
5753 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5754
5755 &lt;/ul&gt;
5756
5757 &lt;p&gt;You can
5758 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5759 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5760 project if something is wrong with the new release. The test suite
5761 did not discover any old errors, so if you find a new one, please also
5762 include a testsuite check.&lt;/p&gt;
5763 </description>
5764 </item>
5765
5766 <item>
5767 <title>Debian init.d boot script example for rsyslog</title>
5768 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5770 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5771 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5772 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5773 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5774 init.d scripts at all. Here is an example init.d script, ie a rewrite
5775 of /etc/init.d/rsyslog:&lt;/p&gt;
5776
5777 &lt;p&gt;&lt;pre&gt;
5778 #!/lib/init/init-d-script
5779 ### BEGIN INIT INFO
5780 # Provides: rsyslog
5781 # Required-Start: $remote_fs $time
5782 # Required-Stop: umountnfs $time
5783 # X-Stop-After: sendsigs
5784 # Default-Start: 2 3 4 5
5785 # Default-Stop: 0 1 6
5786 # Short-Description: enhanced syslogd
5787 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5788 # It is quite compatible to stock sysklogd and can be
5789 # used as a drop-in replacement.
5790 ### END INIT INFO
5791 DESC=&quot;enhanced syslogd&quot;
5792 DAEMON=/usr/sbin/rsyslogd
5793 &lt;/pre&gt;&lt;/p&gt;
5794
5795 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5796 script was 137 lines, and the above is just 15 lines, most of it meta
5797 info/comments.&lt;/p&gt;
5798
5799 &lt;p&gt;How to do this, you ask? Well, one create a new script
5800 /lib/init/init-d-script looking something like this:
5801
5802 &lt;p&gt;&lt;pre&gt;
5803 #!/bin/sh
5804
5805 # Define LSB log_* functions.
5806 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5807 # and status_of_proc is working.
5808 . /lib/lsb/init-functions
5809
5810 #
5811 # Function that starts the daemon/service
5812
5813 #
5814 do_start()
5815 {
5816 # Return
5817 # 0 if daemon has been started
5818 # 1 if daemon was already running
5819 # 2 if daemon could not be started
5820 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5821 || return 1
5822 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5823 $DAEMON_ARGS \
5824 || return 2
5825 # Add code here, if necessary, that waits for the process to be ready
5826 # to handle requests from services started subsequently which depend
5827 # on this one. As a last resort, sleep for some time.
5828 }
5829
5830 #
5831 # Function that stops the daemon/service
5832 #
5833 do_stop()
5834 {
5835 # Return
5836 # 0 if daemon has been stopped
5837 # 1 if daemon was already stopped
5838 # 2 if daemon could not be stopped
5839 # other if a failure occurred
5840 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5841 RETVAL=&quot;$?&quot;
5842 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5843 # Wait for children to finish too if this is a daemon that forks
5844 # and if the daemon is only ever run from this initscript.
5845 # If the above conditions are not satisfied then add some other code
5846 # that waits for the process to drop all resources that could be
5847 # needed by services started subsequently. A last resort is to
5848 # sleep for some time.
5849 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5850 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5851 # Many daemons don&#39;t delete their pidfiles when they exit.
5852 rm -f $PIDFILE
5853 return &quot;$RETVAL&quot;
5854 }
5855
5856 #
5857 # Function that sends a SIGHUP to the daemon/service
5858 #
5859 do_reload() {
5860 #
5861 # If the daemon can reload its configuration without
5862 # restarting (for example, when it is sent a SIGHUP),
5863 # then implement that here.
5864 #
5865 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5866 return 0
5867 }
5868
5869 SCRIPTNAME=$1
5870 scriptbasename=&quot;$(basename $1)&quot;
5871 echo &quot;SN: $scriptbasename&quot;
5872 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5873 script=&quot;$1&quot;
5874 shift
5875 . $script
5876 else
5877 exit 0
5878 fi
5879
5880 NAME=$(basename $DAEMON)
5881 PIDFILE=/var/run/$NAME.pid
5882
5883 # Exit if the package is not installed
5884 #[ -x &quot;$DAEMON&quot; ] || exit 0
5885
5886 # Read configuration variable file if it is present
5887 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5888
5889 # Load the VERBOSE setting and other rcS variables
5890 . /lib/init/vars.sh
5891
5892 case &quot;$1&quot; in
5893 start)
5894 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5895 do_start
5896 case &quot;$?&quot; in
5897 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5898 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5899 esac
5900 ;;
5901 stop)
5902 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5903 do_stop
5904 case &quot;$?&quot; in
5905 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5906 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5907 esac
5908 ;;
5909 status)
5910 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5911 ;;
5912 #reload|force-reload)
5913 #
5914 # If do_reload() is not implemented then leave this commented out
5915 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5916 #
5917 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5918 #do_reload
5919 #log_end_msg $?
5920 #;;
5921 restart|force-reload)
5922 #
5923 # If the &quot;reload&quot; option is implemented then remove the
5924 # &#39;force-reload&#39; alias
5925 #
5926 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5927 do_stop
5928 case &quot;$?&quot; in
5929 0|1)
5930 do_start
5931 case &quot;$?&quot; in
5932 0) log_end_msg 0 ;;
5933 1) log_end_msg 1 ;; # Old process is still running
5934 *) log_end_msg 1 ;; # Failed to start
5935 esac
5936 ;;
5937 *)
5938 # Failed to stop
5939 log_end_msg 1
5940 ;;
5941 esac
5942 ;;
5943 *)
5944 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5945 exit 3
5946 ;;
5947 esac
5948
5949 :
5950 &lt;/pre&gt;&lt;/p&gt;
5951
5952 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5953 lot. I did not really polish the approach, so it might not always
5954 work out of the box, but you get the idea. I did not try very hard to
5955 optimize it nor make it more robust either.&lt;/p&gt;
5956
5957 &lt;p&gt;A better argument for switching init system in Debian than reducing
5958 the size of init scripts (which is a good thing to do anyway), is to
5959 get boot system that is able to handle the kernel events sensibly and
5960 robustly, and do not depend on the boot to run sequentially. The boot
5961 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5962 </description>
5963 </item>
5964
5965 <item>
5966 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5967 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5969 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5970 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5971 remote display access is the preferred solution with oVirt and RedHat
5972 Enterprise Virtualization, and I was sad to discover the other day
5973 that the browser plugin needed to use these systems seamlessly was
5974 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5975 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5976 2013-04-01, so I decided to wrap up a package based on the great work
5977 from Cajus Pollmeier and put it in a collab-maint maintained git
5978 repository to get a package I could use. I would very much like
5979 others to help me maintain the package (or just take over, I do not
5980 mind), but as no-one had volunteered so far, I just uploaded it to
5981 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5982
5983 &lt;p&gt;The source is now available from
5984 &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;
5985 </description>
5986 </item>
5987
5988 <item>
5989 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5990 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5992 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5993 <description>&lt;p&gt;The
5994 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5995 program is a a very nice system to create virtual machine images. It
5996 create a image file, add a partition table, mount it and run
5997 debootstrap in the mounted directory to create a Debian system on a
5998 stick. Yesterday, I decided to try to teach it how to make images for
5999 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
6000 of a plan to simplify the build system for
6001 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
6002 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
6003 the virtualbox images, but its current build system made multistrap
6004 based system for Dreamplug images, and it is lacking support for
6005 Raspberry Pi.&lt;/p&gt;
6006
6007 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
6008 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6009 code and adjusted it to be able to build armel images on my amd64
6010 Debian laptop. I ended up giving vmdebootstrap five new options,
6011 allowing me to replicate the image creation process I use to make
6012 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
6013 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
6014 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
6015 call debootstrap with --foreign and to copy the handler into the
6016 generated chroot before running the second stage. This allow
6017 vmdebootstrap to create armel images on an amd64 host. Next I added
6018 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
6019 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
6020 given file system type, allowing me to create an image with a vfat
6021 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
6022 variant&lt;/tt&gt; option to allow me to create smaller images without the
6023 Debian base system packages installed. Finally, I added an option
6024 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
6025 as a boot loader. It is not needed on the Raspberry Pi and probably
6026 most other non-x86 architectures. The changes were accepted by the
6027 upstream author of vmdebootstrap yesterday and today, and is now
6028 available from
6029 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
6030 upstream project page&lt;/a&gt;.&lt;/p&gt;
6031
6032 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
6033 create a small script (the customize script) to add the non-free
6034 binary blob needed to boot the Raspberry Pi and the APT source
6035 list:&lt;/p&gt;
6036
6037 &lt;p&gt;&lt;pre&gt;
6038 #!/bin/sh
6039 set -e # Exit on first error
6040 rootdir=&quot;$1&quot;
6041 cd &quot;$rootdir&quot;
6042 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
6043 deb http://http.debian.net/debian/ jessie main contrib non-free
6044 EOF
6045 # Install non-free binary blob needed to boot Raspberry Pi. This
6046 # install a kernel somewhere too.
6047 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6048 -O $rootdir/usr/bin/rpi-update
6049 chmod a+x $rootdir/usr/bin/rpi-update
6050 mkdir -p $rootdir/lib/modules
6051 touch $rootdir/boot/start.elf
6052 chroot $rootdir rpi-update
6053 &lt;/pre&gt;&lt;/p&gt;
6054
6055 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
6056 to build the image:&lt;/p&gt;
6057
6058 &lt;pre&gt;
6059 sudo ./vmdebootstrap \
6060 --variant minbase \
6061 --arch armel \
6062 --distribution jessie \
6063 --mirror http://http.debian.net/debian \
6064 --image test.img \
6065 --size 600M \
6066 --bootsize 64M \
6067 --boottype vfat \
6068 --log-level debug \
6069 --verbose \
6070 --no-kernel \
6071 --no-extlinux \
6072 --root-password raspberry \
6073 --hostname raspberrypi \
6074 --foreign /usr/bin/qemu-arm-static \
6075 --customize `pwd`/customize \
6076 --package netbase \
6077 --package git-core \
6078 --package binutils \
6079 --package ca-certificates \
6080 --package wget \
6081 --package kmod
6082 &lt;/pre&gt;&lt;/p&gt;
6083
6084 &lt;p&gt;The list of packages being installed are the ones needed by
6085 rpi-update to make the image bootable on the Raspberry Pi, with the
6086 exception of netbase, which is needed by debootstrap to find
6087 /etc/hosts with the minbase variant. I really wish there was a way to
6088 set up an Raspberry Pi using only packages in the Debian archive, but
6089 that is not possible as far as I know, because it boots from the GPU
6090 using a non-free binary blob.&lt;/p&gt;
6091
6092 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
6093 probably a few others installed. I have not checked the complete
6094 build dependency list.&lt;/p&gt;
6095
6096 &lt;p&gt;The resulting image will not use the hardware floating point unit
6097 on the Raspberry PI, because the armel architecture in Debian is not
6098 optimized for that use. So the images created will be a bit slower
6099 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
6100 </description>
6101 </item>
6102
6103 <item>
6104 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
6105 <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>
6106 <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>
6107 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
6108 <description>&lt;p&gt;The last few days I came across a few good causes that should get
6109 wider attention. I recommend signing and donating to each one of
6110 these. :)&lt;/p&gt;
6111
6112 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
6113 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
6114 Women program which is a Google Summer of Code like initiative to get
6115 more women involved in free software. One debian sponsor has offered
6116 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
6117 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
6118 hope you will to. :)&lt;/p&gt;
6119
6120 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
6121 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
6122 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
6123 take place these days, and their need to fund the work. I&#39;ve already
6124 donated. Are you next?&lt;/p&gt;
6125
6126 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
6127 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
6128 statement under the heading
6129 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
6130 Access&lt;/a&gt; for those of us asking for more focus on open access in the
6131 Norwegian government. So far 499 signatures. I hope you will sign it
6132 too.&lt;/p&gt;
6133 </description>
6134 </item>
6135
6136 <item>
6137 <title>Videos about the Freedombox project - for inspiration and learning</title>
6138 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
6139 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
6140 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
6141 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
6142 project&lt;/a&gt; have been going on for a while, and have presented the
6143 vision, ideas and solution several places. Here is a little
6144 collection of videos of talks and presentation of the project.&lt;/p&gt;
6145
6146 &lt;ul&gt;
6147
6148 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
6149 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
6150
6151 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
6152 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6153
6154 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
6155 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6156 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
6157 (Youtube)&lt;/li&gt;
6158
6159 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
6160 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
6161
6162 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
6163 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6164
6165 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
6166 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6167 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
6168
6169 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
6170 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
6171 (Youtube)&lt;/li&gt;
6172
6173 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
6174 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
6175
6176 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
6177 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
6178
6179 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
6180 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
6181 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
6182
6183 &lt;/ul&gt;
6184
6185 &lt;p&gt;A larger list is available from
6186 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
6187 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
6188
6189 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
6190 Jessie is coming along quite well, and soon both Owncloud and using
6191 Tor should be available for testers of the Freedombox solution. :) In
6192 a few weeks I hope everything needed to test it is included in Debian.
6193 The withsqlite package is already in Debian, and the plinth package is
6194 pending in NEW. The third and vital part of that puzzle is the
6195 metapackage/setup framework, which is still pending an upload. Join
6196 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
6197 (#freedombox on irc.debian.org)&lt;/a&gt; and
6198 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6199 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6200 </description>
6201 </item>
6202
6203 <item>
6204 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
6205 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
6206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
6207 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
6208 <description>&lt;p&gt;I was introduced to the
6209 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
6210 in 2010, when Eben Moglen presented his vision about serving the need
6211 of non-technical people to keep their personal information private and
6212 within the legal protection of their own homes. The idea is to give
6213 people back the power over their network and machines, and return
6214 Internet back to its intended peer-to-peer architecture. Instead of
6215 depending on a central service, the Freedombox will give everyone
6216 control over their own basic infrastructure.&lt;/p&gt;
6217
6218 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
6219 taken priority. But this summers nasty news about the misuse of trust
6220 and privilege exercised by the &quot;western&quot; intelligence gathering
6221 communities increased my eagerness to contribute to a point where I
6222 actually started working on the project a while back.&lt;/p&gt;
6223
6224 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
6225 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
6226 create a simple and cheap Debian based appliance that anyone can hook
6227 up in their home and get access to secure and private services and
6228 communication. The initial deployment platform have been the
6229 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
6230 which is a piece of hardware I do not own. So to be able to test what
6231 the current Freedombox setup look like, I had to come up with a way to install
6232 it on some hardware I do have access to. I have rewritten the
6233 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
6234 image build framework to use .deb packages instead of only copying
6235 setup into the boot images, and thanks to this rewrite I am able to
6236 set up any machine supported by Debian Wheezy as a Freedombox, using
6237 the previously mentioned deb (and a few support debs for packages
6238 missing in Debian).&lt;/p&gt;
6239
6240 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
6241 scripts
6242 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
6243 and a administrative web interface
6244 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
6245 withsqlite), as well as a privacy enhancing proxy based on
6246 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
6247 (freedombox-privoxy). There is also a web/javascript based XMPP
6248 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
6249 trying (unsuccessfully so far) to talk to the XMPP server
6250 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
6251 web interface is pluggable, and the goal is to use it to enable OpenID
6252 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6253 this is really working yet, see
6254 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
6255 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
6256 on github at the moment. The HTTP proxy is operational out of the
6257 box, and the admin web interface can be used to add/remove plinth
6258 users. I&#39;ve not been able to do anything else with it so far, but
6259 know there are several branches spread around github and other places
6260 with lots of half baked features.&lt;/p&gt;
6261
6262 &lt;p&gt;Anyway, if you want to have a look at the current state, the
6263 following recipes should work to give you a test machine to poke
6264 at.&lt;/p&gt;
6265
6266 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
6267
6268 &lt;ol&gt;
6269
6270 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
6271 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
6272 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
6273 to the Debian installer:&lt;p&gt;
6274 &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;
6275
6276 &lt;li&gt;Answer the few language/region/password questions and pick disk to
6277 install on.&lt;/li&gt;
6278
6279 &lt;li&gt;When the installation is finished and the machine have rebooted a
6280 few times, your Freedombox is ready for testing.&lt;/li&gt;
6281
6282 &lt;/ol&gt;
6283
6284 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
6285
6286 &lt;ol&gt;
6287
6288 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
6289 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
6290 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
6291 &lt;pre&gt;
6292 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
6293 &lt;/pre&gt;&lt;/li&gt;
6294 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
6295 &lt;pre&gt;
6296 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6297 apt-key add -
6298 apt-get update
6299 apt-get install freedombox-setup
6300 /usr/lib/freedombox/setup
6301 &lt;/pre&gt;&lt;/li&gt;
6302 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
6303
6304 &lt;/ol&gt;
6305
6306 &lt;p&gt;You can test it on other architectures too, but because the
6307 freedombox-privoxy package is binary, it will only work as intended on
6308 the architectures where I have had time to build the binary and put it
6309 in my APT repository. But do not let this stop you. It is only a
6310 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
6311
6312 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
6313 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
6314 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
6315 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
6316
6317 &lt;p&gt;Please let me know if this works for you, or if you have any
6318 problems. We gather on the IRC channel
6319 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
6320 irc.debian.org and the
6321 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
6322 mailing list&lt;/a&gt;.&lt;/p&gt;
6323
6324 &lt;p&gt;Once you get your freedombox operational, you can visit
6325 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
6326 welcome screen (dead end - do not be surprised if you are unable to
6327 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
6328 to look at the rest of plinth. The default user is &#39;admin&#39; and the
6329 default password is &#39;secret&#39;.&lt;/p&gt;
6330 </description>
6331 </item>
6332
6333 <item>
6334 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
6335 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
6336 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
6337 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
6338 <description>&lt;p&gt;Earlier, I reported about
6339 &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
6340 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
6341 told by IBM that the original disk should be thrown away. And as
6342 there no longer was a problem if I bricked the firmware, I decided
6343 today to try to install Intel firmware to replace the Lenovo firmware
6344 currently on the disk.&lt;/p&gt;
6345
6346 &lt;p&gt;I searched the Intel site for firmware, and found
6347 &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;
6348 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6349 according to the site should contain the latest firmware for SSD
6350 disks. I inserted the broken disk in one of my spare laptops and
6351 booted the ISO from a USB stick. The disk was recognized, but the
6352 program claimed the newest firmware already were installed and refused
6353 to insert any Intel firmware. So no change, and the disk is still
6354 unable to handle write load. :( I guess the only way to get them
6355 working would be if Lenovo releases new firmware. No idea how likely
6356 that is. Anyway, just blogging about this test for completeness. I
6357 got a working Samsung disk, and see no point in spending more time on
6358 the broken disks.&lt;/p&gt;
6359 </description>
6360 </item>
6361
6362 <item>
6363 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
6364 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
6365 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
6366 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
6367 <description>&lt;p&gt;Today I switched to
6368 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
6369 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
6370 my new Thinkpad X230, which was delivered with an
6371 &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
6372 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
6373 sustained writes. My hardware supplier have been very forthcoming in
6374 trying to find a solution, and after first trying with another
6375 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
6376 disk instead to fix it once and for all. The Samsung disk survived
6377 the installation of Debian with encrypted disks (filling the disk with
6378 random data during installation killed the first two), and I thus
6379 decided to trust it with my data. I have installed it as a Debian Edu
6380 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6381 server at home using Kerberos and LDAP, and will use it as my work
6382 station from now on.&lt;/p&gt;
6383
6384 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
6385 Debian Wheezy default installation need to be tuned a bit to increase
6386 performance and increase life time of the disk. The Linux kernel and
6387 user space applications do not yet adjust automatically to such
6388 environment. To make it easier for my self, I created a draft Debian
6389 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
6390 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
6391 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
6392 is set up to adjust the setup of the machine by just installing the
6393 package. If there is any non-SSD disk in the machine, the package
6394 will refuse to install, as I did not try to write any logic to sort
6395 file systems in SSD and non-SSD file systems.&lt;/p&gt;
6396
6397 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
6398 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6399 where I set up the machine with one large encrypted partition (in
6400 addition to /boot), put LVM on top of this and set up partitions on
6401 top of this again. See the README file in the package source for the
6402 references I used to pick the settings. At the moment these
6403 parameters are tuned:&lt;/p&gt;
6404
6405 &lt;ul&gt;
6406
6407 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
6408 (adding discard to /etc/crypttab)&lt;/li&gt;
6409
6410 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
6411 this case a cryptsetup partition) by changing issue_discards from
6412 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
6413
6414 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
6415 systems.&lt;/li&gt;
6416
6417 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
6418 /etc/fstab.&lt;/li&gt;
6419
6420 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
6421
6422 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
6423 cron.daily).&lt;/li&gt;
6424
6425 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
6426 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
6427
6428 &lt;/ul&gt;
6429
6430 &lt;p&gt;During installation, I cancelled the part where the installer fill
6431 the disk with random data, as this would kill the SSD performance for
6432 little gain. My goal with the encrypted file system is to ensure
6433 those stealing my laptop end up with a brick and not a working
6434 computer. I have no hope in keeping the really resourceful people
6435 from getting the data on the disk (see
6436 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
6437 Thus I concluded that adding the discard option to crypttab is the
6438 right thing to do.&lt;/p&gt;
6439
6440 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
6441 it for SSD, but others recommended deadline and a benchmark I found
6442 indicated that deadline might be better for interactive use.&lt;/p&gt;
6443
6444 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
6445 and ext4, but read that it would give a performance hit ever time a
6446 file is removed, and thought it best to that that slowdown once a day
6447 instead of during my work.&lt;/p&gt;
6448
6449 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6450 this is already done by Debian Edu.&lt;/p&gt;
6451
6452 &lt;p&gt;I have not yet started on the user space tuning. I expect
6453 iceweasel need some tuning, and perhaps other applications too, but
6454 have not yet had time to investigate those parts.&lt;/p&gt;
6455
6456 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
6457 there.&lt;/p&gt;
6458
6459 &lt;p&gt;As for the answer to the question in the title of this blog post,
6460 as far as I know, the only solution I know about is to replace the
6461 disk. It might be possible to flash it with Intel firmware instead of
6462 the Lenovo firmware. But I have not tried and did not want to do so
6463 without approval from Lenovo as I wanted to keep the warranty on the
6464 disk until a solution was found and they wanted the broken disks
6465 back.&lt;/p&gt;
6466 </description>
6467 </item>
6468
6469 <item>
6470 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
6471 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
6472 <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>
6473 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
6474 <description>&lt;p&gt;A few days ago, I wrote about
6475 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
6476 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
6477 was dying during installation because it is unable to cope with
6478 sustained write. My supplier is in contact with
6479 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
6480 replacement disk to try to fix the problem. They decided to send an
6481 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
6482
6483 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
6484 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6485 same firmware version as the original. This time my hope raised
6486 slightly as the installation progressed, as the original disk used to
6487 die after 4-7% of the disk was written to, while this time it kept
6488 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
6489 died again and I was back on square one. I still do not have a new
6490 laptop with a disk I can trust. I can not live with a disk that might
6491 lock up when I download a new
6492 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
6493 other large files. I look forward to hearing from my supplier with
6494 the next proposal from Lenovo.&lt;/p&gt;
6495
6496 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
6497 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6498 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6499 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
6500 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6501 P/N 45N8295, P0C38732.&lt;/p&gt;
6502
6503 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
6504 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
6505 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6506 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
6507 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6508 P/N 45N8295, P0C38732.&lt;/p&gt;
6509
6510 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
6511 SA, date and WNPP values. Mentioning all the details here in case
6512 someone is able to use the information to find a way to identify the
6513 failing disk among working ones (if any such working disk actually
6514 exist).&lt;/p&gt;
6515 </description>
6516 </item>
6517
6518 <item>
6519 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
6520 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
6521 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
6522 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
6523 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
6524 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6525 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
6526 member assosiation NUUG&lt;/a&gt; and
6527 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
6528 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
6529 Bitraf&lt;/a&gt;.&lt;/p&gt;
6530
6531 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
6532 welcome, and there is no fee to participate. There is on the other
6533 hand limited space, and only room for 30 people. Please put your name
6534 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
6535 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
6536 </description>
6537 </item>
6538
6539 <item>
6540 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
6541 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
6542 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
6543 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
6544 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
6545 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
6546 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
6547 time to spend on it, and it took a while to find a model I believe
6548 will do the job, but two days ago the replacement finally arrived. I
6549 ended up picking a
6550 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
6551 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6552 a roaming workstation, and it seemed to work flawlessly. But my
6553 second installation with encrypted disk was not as successful. More
6554 on that below.&lt;/p&gt;
6555
6556 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6557 important requirements (robust and with a good keyboard) are never
6558 listed in the feature list. But I did get good help from the search
6559 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6560 allowed me to limit the list of interesting laptops based on my other
6561 requirements. A bit surprising that SSD disk are not disks according
6562 to that search interface, so I had to drop specifying the number of
6563 disks from my search parameters. I also asked around among friends to
6564 get their impression on keyboards and robustness.&lt;/p&gt;
6565
6566 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
6567 X41. I am not quite convinced about the keyboard, as it is
6568 significantly wider than my old keyboard, and I have to stretch my
6569 hand a lot more to reach the edges. But the key response is fairly
6570 good and the individual key shape is fairly easy to handle, so I hope
6571 I will get used to it. My old X40 was starting to fail, and I really
6572 needed a new laptop now. :)&lt;/p&gt;
6573
6574 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6575 visit to the BIOS during boot it disable it.&lt;/p&gt;
6576
6577 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6578 lock up during load. And this happen when installing Debian Wheezy
6579 with encrypted disk, while the disk is being filled with random data.
6580 I also tested to install Ubuntu Raring, and it happen there too if I
6581 reenable the code to fill the disk with random data (it is disabled by
6582 default in Ubuntu). And the bug with is already known. It was
6583 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6584 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6585 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6586 kernel developers as
6587 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6588 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6589 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6590 Lenovo forums, both for
6591 &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
6592 2012-11-10&lt;/a&gt; and for
6593 &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
6594 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6595 reports state that the disk lock up during use if many writes are done
6596 on the disk, so it is much no use to work around the installation
6597 problem and end up with a computer that can lock up at any moment.
6598 There is even a
6599 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6600 available&lt;/a&gt; that will lock up the hard drive after running a few
6601 minutes by writing to a file.&lt;/p&gt;
6602
6603 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6604 contacting PCHELP Norway (request 01D1FDP) which handle support
6605 requests for Lenovo, his first suggestion was to upgrade the disk
6606 firmware. Unfortunately there is no newer firmware available from
6607 Lenovo, as my disk already have the most recent one (version LF1i). I
6608 hope to hear more from him today and hope the problem can be
6609 fixed. :)&lt;/p&gt;
6610 </description>
6611 </item>
6612
6613 <item>
6614 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6615 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6616 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6617 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6618 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6619 trusty old Thinkpad X41. Unfortunately I did not have much time to
6620 spend on it, but today the replacement finally arrived. I ended up
6621 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6622 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6623 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6624 this, it is installing what I hope will be a more final installation,
6625 with a encrypted hard drive to ensure any dope head stealing it end up
6626 with an expencive door stop.&lt;/p&gt;
6627
6628 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6629 important requirements (robust and with a good keyboard) are never
6630 listed in the feature list. But I did get good help from the search
6631 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6632 allowed me to limit the list of interesting laptops based on my other
6633 requirements. A bit surprising that SSD disk are not disks, so I had
6634 to drop number of disks from my search parameters.&lt;/p&gt;
6635
6636 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6637 wider than my old keyboard, and I have to stretch my hand a lot more
6638 to reach the edges. But the key response is fairly good and the
6639 individual key shape is fairly easy to handle, so I hope I will get
6640 used to it. My old X40 was starting to fail, and I really needed a
6641 new laptop now. :)&lt;/p&gt;
6642
6643 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6644 </description>
6645 </item>
6646
6647 <item>
6648 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6649 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6650 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6651 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6652 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6653 perfectly capable of, and I have to do it manually to get things
6654 working. One such task is to find out what firmware packages are
6655 needed to get the hardware on my computer working. Most often this
6656 affect the wifi card, but some times it even affect the RAID
6657 controller or the ethernet card. Today I pushed version 0.4 of the
6658 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6659 including a new script isenkram-autoinstall-firmware handling the
6660 process of asking all the loaded kernel modules what firmware files
6661 they want, find debian packages providing these files and install the
6662 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6663
6664 &lt;p&gt;&lt;pre&gt;
6665 # isenkram-autoinstall-firmware
6666 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6667 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6668 info: locating packages with the requested firmware files
6669 info: Updating APT sources after adding non-free APT source
6670 info: trying to install firmware-ipw2x00
6671 firmware-ipw2x00
6672 firmware-ipw2x00
6673 Preconfiguring packages ...
6674 Selecting previously deselected package firmware-ipw2x00.
6675 (Reading database ... 259727 files and directories currently installed.)
6676 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6677 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6678 #
6679 &lt;/pre&gt;&lt;/p&gt;
6680
6681 &lt;p&gt;When all the requested firmware is present, a simple message is
6682 printed instead:&lt;/p&gt;
6683
6684 &lt;p&gt;&lt;pre&gt;
6685 # isenkram-autoinstall-firmware
6686 info: did not find any firmware files requested by loaded kernel modules. exiting
6687 #
6688 &lt;/pre&gt;&lt;/p&gt;
6689
6690 &lt;p&gt;It could use some polish, but it is already working well and saving
6691 me some time when setting up new machines. :)&lt;/p&gt;
6692
6693 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6694 kernel modules, and look up each one of them using modinfo, to find
6695 the firmware files listed in the module meta-information. Next, it
6696 download the Contents file from a nearby APT mirror, and search for
6697 the firmware files in this file to locate the package with the
6698 requested firmware file. If the package is in the non-free section, a
6699 non-free APT source is added and the package is installed using
6700 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6701 machine.&lt;/p&gt;
6702
6703 &lt;p&gt;I hope someone find time to implement a more polished version of
6704 this script as part of the hw-detect debian-installer module, to
6705 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6706 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6707 firmware during a PXE install when the packages already are available
6708 from the nearby Debian mirror.&lt;/p&gt;
6709 </description>
6710 </item>
6711
6712 <item>
6713 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6714 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6715 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6716 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6717 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6718 the screen just turn black when Linux boot, either during installation
6719 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6720 last few years, but only recently understood the cause. I&#39;ve seen it
6721 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6722 The reason seem to be in the wiring of some laptops. The system to
6723 control the screen background light is inverted, so when Linux try to
6724 turn the brightness fully on, it end up turning it off instead. I do
6725 not know which Linux drivers are affected, but this post is about the
6726 i915 driver used by the
6727 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6728 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6729
6730 &lt;p&gt;The problem can be worked around two ways. Either by adding
6731 i915.invert_brightness=1 as a kernel option, or by adding a file in
6732 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6733 option when it load the i915 kernel module. On Debian and Ubuntu, it
6734 can be done by running these commands as root:&lt;/p&gt;
6735
6736 &lt;pre&gt;
6737 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6738 update-initramfs -u -k all
6739 &lt;/pre&gt;
6740
6741 &lt;p&gt;Since March 2012 there is
6742 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6743 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6744 hardware have this problem, and get the driver to invert the
6745 brightness setting automatically. To use it, one need to add a row in
6746 &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
6747 intel_quirks array&lt;/a&gt; in the driver source
6748 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6749 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6750 number (vendor number 8086 is assumed) and subdevice vendor and device
6751 number.&lt;/p&gt;
6752
6753 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6754 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6755
6756 &lt;p&gt;&lt;pre&gt;
6757 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6758 3rd Gen Core processor Graphics Controller [8086:0156] \
6759 (rev 09) (prog-if 00 [VGA controller])
6760 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6761 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6762 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6763 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6764 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6765 Latency: 0
6766 Interrupt: pin A routed to IRQ 42
6767 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6768 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6769 Region 4: I/O ports at 4000 [size=64]
6770 Expansion ROM at &lt;unassigned&gt; [disabled]
6771 Capabilities: &lt;access denied&gt;
6772 Kernel driver in use: i915
6773 &lt;/pre&gt;&lt;/p&gt;
6774
6775 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6776
6777 &lt;p&gt;&lt;pre&gt;
6778 struct intel_quirk intel_quirks[] = {
6779 ...
6780 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6781 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6782 ...
6783 }
6784 &lt;/pre&gt;&lt;/p&gt;
6785
6786 &lt;p&gt;According to the kernel module instructions (as seen using
6787 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6788 invert_brightness flag should be sent to the
6789 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6790 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6791 developers. But my email about the laptop sent 2013-06-03 have not
6792 yet shown up in
6793 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6794 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6795 emails from non-subscribers. Because of this, I sent my patch also to
6796 the Debian bug tracking system instead as
6797 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6798 sure the patch is not lost.&lt;/p&gt;
6799
6800 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6801 with this problem working properly with Linux. If you use Gnome, your
6802 worries should be over at this point. But if you use KDE, there is
6803 something in KDE ignoring the invert_brightness setting and turning on
6804 the screen during login. I&#39;ve reported it to Debian as
6805 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6806 have no idea yet how to figure out exactly what subsystem is doing
6807 this. Perhaps you can help? Perhaps you know what the Gnome
6808 developers did to handle this, and this can give a clue to the KDE
6809 developers? Or you know where in KDE the screen brightness is changed
6810 during login? If so, please update the BTS report (or get in touch if
6811 you do not know how to update BTS).&lt;/p&gt;
6812
6813 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6814 acpi_backlight=vendor, to disable ACPI backlight support completely,
6815 as the ACPI information on the machine is trash and it is better to
6816 leave it to the intel video driver to control the screen
6817 backlight.&lt;/p&gt;
6818 </description>
6819 </item>
6820
6821 <item>
6822 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6823 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6824 <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>
6825 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6826 <description>&lt;p&gt;Two days ago, I asked
6827 &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
6828 I could install Linux on a Packard Bell EasyNote LV computer
6829 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6830 with the obstacles put in the way of Linux users on a laptop with UEFI
6831 and Windows 8.&lt;/p&gt;
6832
6833 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6834 secure booting or fast boot. I suspect fast boot was the problem,
6835 causing the firmware to boot directly from HD without considering any
6836 key presses and alternative devices, but do not know UEFI settings
6837 enough to tell.&lt;/p&gt;
6838
6839 &lt;p&gt;There is no way to install Linux on the machine in question without
6840 opening the box and disconnecting the hard drive! This is as far as I
6841 can tell, the only way to get access to the firmware setup menu
6842 without accepting the Windows 8 license agreement. I am told (and
6843 found description on how to) that it is possible to configure the
6844 firmware setup once booted into Windows 8. But as I believe the terms
6845 of that agreement are completely unacceptable, accepting the license
6846 was never an alternative. I do not enter agreements I do not intend
6847 to follow.&lt;/p&gt;
6848
6849 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6850 waste many hours on this, but luckily there was a way to get it to
6851 work. But I would not recommend it to anyone planning to run Linux on
6852 it, and I have become sceptical to Windows 8 certified laptops. Is
6853 this the way Linux will be forced out of the market place, by making
6854 it close to impossible for &quot;normal&quot; users to install Linux without
6855 accepting the Microsoft Windows license terms? Or at least not
6856 without risking to loose the warranty?&lt;/p&gt;
6857
6858 &lt;p&gt;I&#39;ve updated the
6859 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6860 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6861 do not have to struggle as much as I did to get Linux into the
6862 machine.&lt;/p&gt;
6863
6864 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6865 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6866 </description>
6867 </item>
6868
6869 <item>
6870 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6871 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6872 <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>
6873 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6874 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6875 new laptops for my parents and a few others. I bought Packard Bell
6876 Easynote LV to run Kubuntu on and use as their home computer. But I
6877 am completely unable to figure out how to install Linux on it. The
6878 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6879 instead of a BIOS to boot.&lt;/p&gt;
6880
6881 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6882 to get it to boot the Linux installer from my USB stick. I have yet
6883 to try the DVD install, and still hope it will work. when I turn on
6884 the computer, there is no information on what buttons to press to get
6885 the normal boot menu. I expect to get some boot menu to select PXE or
6886 USB stick booting. When booting, it first ask for the language to
6887 use, then for some regional settings, and finally if I will accept the
6888 Windows 8 terms of use. As these terms are completely unacceptable to
6889 me, I have no other choice but to turn off the computer and try again
6890 to get it to boot the Linux installer.&lt;/p&gt;
6891
6892 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6893 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6894 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6895 installed on this machine, please get in touch or update that wiki
6896 page. If I can&#39;t find a way to install Linux, I will have to return
6897 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6898
6899 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6900 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6901 on new Laptops?&lt;/p&gt;
6902 </description>
6903 </item>
6904
6905 <item>
6906 <title>How to transform a Debian based system to a Debian Edu installation</title>
6907 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6908 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6909 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6910 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6911 an operating system based on Debian intended for use in schools. It
6912 contain a turn-key solution for the computer network provided to
6913 pupils in the primary schools. It provide both the central server,
6914 network boot servers and desktop environments with heaps of
6915 educational software. The project was founded almost 12 years ago,
6916 2001-07-02. If you want to support the project, which is in need for
6917 cash to fund developer gatherings and other project related activity,
6918 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6919 donate some money&lt;/a&gt;.
6920
6921 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6922 lists and elsewhere, is the question on how to transform a Debian or
6923 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6924 hard, and last week I wrote a script to replicate the steps done by
6925 the Debian Edu installer.&lt;/p&gt;
6926
6927 &lt;p&gt;The script,
6928 &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;
6929 in the debian-edu-config package, will go through these six steps and
6930 transform an existing Debian Wheezy or Ubuntu (untested) installation
6931 into a Debian Edu Workstation:&lt;/p&gt;
6932
6933 &lt;ol&gt;
6934
6935 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6936 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6937 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6938 our configuration.&lt;/li&gt;
6939 &lt;li&gt;Preseed debconf database with profile setup in
6940 /etc/debian-edu/config, and run tasksel to install packages
6941 according to the profile specified in the config above,
6942 overriding some of the Debian automation machinery.&lt;/li&gt;
6943 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6944 that could not be done using preseeding.&lt;/li&gt;
6945 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6946
6947 &lt;/ol&gt;
6948
6949 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6950 replicated like this. Disk partitioning and LVM setup, for example.
6951 So this script just assume there is enough disk space to install all
6952 the needed packages.&lt;/p&gt;
6953
6954 &lt;p&gt;The script was created to help a Debian Edu student working on
6955 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6956 Debian Edu client, and using it he can take the existing
6957 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6958 transform it into a fully functioning Debian Edu Workstation (or
6959 Roaming Workstation, or whatever :).&lt;/p&gt;
6960
6961 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6962 If a LXDE based Roaming workstation is wanted instead, modify the
6963 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6964
6965 &lt;p&gt;&lt;pre&gt;
6966 PROFILE=&quot;Roaming-Workstation&quot;
6967 DESKTOP=&quot;lxde&quot;
6968 &lt;/pre&gt;&lt;/p&gt;
6969
6970 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6971 the cloud, by starting with a virtual Debian installation at some
6972 virtual hosting service and setting up all the services on first
6973 boot.&lt;/p&gt;
6974 </description>
6975 </item>
6976
6977 <item>
6978 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6979 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6980 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6981 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6982 <description>&lt;P&gt;In January,
6983 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6984 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6985 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6986 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6987 marvellous construction system from Denmark. We also created
6988 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6989 a place to take notes and write down our plans and hopes. And several
6990 people showed up to help. I was very happy to see the effect of my
6991 call. Since the small start, we have a debtags tag
6992 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6993 tag for LEGO related packages, and now count 10 packages related to
6994 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6995
6996 &lt;p&gt;&lt;table&gt;
6997 &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;
6998 &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;
6999 &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;
7000 &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;
7001 &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;
7002 &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;
7003 &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;
7004 &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;
7005 &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;
7006 &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;
7007 &lt;/table&gt;&lt;/p&gt;
7008
7009 &lt;p&gt;Some of these are available in Wheezy, and all but one are
7010 currently available in Jessie/testing. leocad is so far only
7011 available in experimental.&lt;/p&gt;
7012
7013 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
7014 adding the rest of the great free software tools available on Linux
7015 for LEGO designers.&lt;/p&gt;
7016 </description>
7017 </item>
7018
7019 <item>
7020 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
7021 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
7022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
7023 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
7024 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
7025 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
7026 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
7027 Debian release, and I expect to move my machines at home over to it fairly
7028 soon.&lt;/p&gt;
7029
7030 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
7031 in particular make me very happy to see included. The
7032 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
7033 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
7034 included for the first time. Alongside similar programs like
7035 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
7036 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
7037 it allow for visual programming where syntax errors can not happen,
7038 and a friendly programming environment for learning to control the
7039 computer. Scratch will also be included in the next release of Debian
7040 Edu.&lt;/a&gt;
7041
7042 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
7043 Edu/Skolelinux release too. The
7044 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
7045 alpha release&lt;/a&gt; went out last week, and the next should soon
7046 follow.&lt;p&gt;
7047 </description>
7048 </item>
7049
7050 <item>
7051 <title>Isenkram 0.2 finally in the Debian archive</title>
7052 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
7053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
7054 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
7055 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
7056 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
7057 for many months. I uploaded it to the Debian experimental suite
7058 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
7059
7060 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
7061 install to work with a pluggable hardware device. The suggestion pop
7062 up when the device is plugged in. For example if a Lego Mindstorm NXT
7063 is inserted, it will suggest to install the program needed to program
7064 the NXT controller. Give it a go, and report bugs and suggestions to
7065 BTS. :)&lt;/p&gt;
7066 </description>
7067 </item>
7068
7069 <item>
7070 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
7071 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
7072 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
7073 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
7074 <description>&lt;p&gt;My
7075 &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
7076 bitcoin related blog post&lt;/a&gt; mentioned that the new
7077 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
7078 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7079 2013-01-19, and have been available in unstable since then. It was
7080 automatically copied to Ubuntu, and is available in their Raring
7081 version too.&lt;/p&gt;
7082
7083 &lt;p&gt;But there is a strange problem with the build that block this new
7084 version from being available on the i386 and kfreebsd-i386
7085 architectures. For some strange reason, the autobuilders in Debian
7086 for these architectures fail to run the test suite on these
7087 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
7088 We are so far unable to reproduce it when building it manually, and
7089 no-one have been able to propose a fix. If you got an idea what is
7090 failing, please let us know via the BTS.&lt;/p&gt;
7091
7092 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
7093 I often run low on disk space, is the fact that the client will exit
7094 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
7095 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
7096 it. :)&lt;/p&gt;
7097
7098 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7099 activities, please send Bitcoin donations to my address
7100 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7101 </description>
7102 </item>
7103
7104 <item>
7105 <title>Welcome to the world, Isenkram!</title>
7106 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
7107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
7108 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
7109 <description>&lt;p&gt;Yesterday, I
7110 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
7111 for testers&lt;/a&gt; for my prototype for making Debian better at handling
7112 pluggable hardware devices, which I
7113 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
7114 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
7115 up, and caused me to really want to to open up the development to more
7116 people. But before I did this, I want to come up with a sensible name
7117 for this project. Today I finally decided on a new name, and I have
7118 renamed the project from hw-support-handler to this new name. In the
7119 process, I moved the source to git and made it available as a
7120 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
7121 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
7122 To fetch and build the latest version of the source, use&lt;/p&gt;
7123
7124 &lt;pre&gt;
7125 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
7126 cd isenkram &amp;&amp; git-buildpackage -us -uc
7127 &lt;/pre&gt;
7128
7129 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
7130 want to hack on the source or improve the package, please go ahead.
7131 But please talk to me first on IRC or via email before you do major
7132 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
7133
7134 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
7135 stuff, typically meaning tools, nails, screws, etc. Typical hardware
7136 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
7137 the German word eisenkram, for those that are familiar with that
7138 word.&lt;/p&gt;
7139
7140 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
7141 instructions, to avoid confusing people with an error from the signing
7142 process.&lt;/p&gt;
7143
7144 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
7145 clone argument to avoid the need for authentication.&lt;/p&gt;
7146 </description>
7147 </item>
7148
7149 <item>
7150 <title>First prototype ready making hardware easier to use in Debian</title>
7151 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
7152 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
7153 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
7154 <description>&lt;p&gt;Early this month I set out to try to
7155 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
7156 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
7157 prototype is working, and it is ready for a larger audience. To test
7158 it, fetch the
7159 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
7160 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
7161 package. You might have to log out and in again activate the
7162 autostart script.&lt;/p&gt;
7163
7164 &lt;p&gt;The design is simple:&lt;/p&gt;
7165
7166 &lt;ul&gt;
7167
7168 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
7169 hw-support-handlerd to start when the user log in.&lt;/li&gt;
7170
7171 &lt;li&gt;This program listen for kernel events about new hardware (directly
7172 from the kernel like udev does), not using HAL dbus events as I
7173 initially did.&lt;/li&gt;
7174
7175 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
7176 the APT database, a database
7177 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
7178 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
7179
7180 &lt;li&gt;If a package is mapped to the hardware in question, the package
7181 isn&#39;t installed yet and this is the first time the hardware was
7182 plugged in, show a desktop notification suggesting to install the
7183 package or packages.&lt;/li&gt;
7184
7185 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
7186 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
7187
7188 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
7189 package while showing progress information in a window.&lt;/li&gt;
7190
7191 &lt;/ul&gt;
7192
7193 &lt;p&gt;I still need to come up with a better name for the system. Here
7194 are some screen shots showing the prototype in action. First the
7195 notification, then the password request, and finally the request to
7196 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
7197
7198 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
7199 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
7200 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
7201 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
7202 &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;
7203
7204 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
7205 is already useful. The database of hardware to package mappings also
7206 need more work. It is currently compatible with the Ubuntu way of
7207 storing such information in the package control file, but could be
7208 changed to use other formats instead or in addition to the current
7209 method. I&#39;ve dropped the use of discover for this mapping, as the
7210 modalias approach is more flexible and easier to use on Linux as long
7211 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
7212
7213 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
7214 here is the command required to check out and build the source: Use
7215 &#39;&lt;tt&gt;svn checkout
7216 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
7217 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
7218 devscripts package.&lt;/p&gt;
7219
7220 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
7221 renamed to Isenkram and the source moved from the Debian Edu
7222 subversion repository to a Debian collab-maint git repository. See
7223 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
7224 instructions&lt;/a&gt; for details.&lt;/p&gt;
7225 </description>
7226 </item>
7227
7228 <item>
7229 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
7230 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
7231 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
7232 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
7233 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
7234 suddenly in bed. With a quiet whimper, it went completely quiet and
7235 black. The power button was no longer able to turn it on. It was a
7236 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7237 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7238 Compaq I had before that. Now I need to find a replacement. To keep
7239 going during Christmas, I moved the one year old SSD disk to my old
7240 X40 where it fitted (only one I had left that could use it), but it is
7241 not a durable solution.
7242
7243 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
7244 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
7245
7246 &lt;ul&gt;
7247
7248 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
7249 than A4).&lt;/li&gt;
7250 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
7251 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
7252 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
7253 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
7254 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
7255 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
7256 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
7257 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
7258 size).&lt;/li&gt;
7259 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
7260 X.org packages.&lt;/li&gt;
7261 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
7262 the time).
7263
7264 &lt;/ul&gt;
7265
7266 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
7267 list. The reason is simply that the specifications on laptops the
7268 last 10-15 years have been sufficient for my needs, and I have to look
7269 at other features to choose my laptop. But are there still made as
7270 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7271 robust, and Thinkpads seem to be heading in the wrong direction since
7272 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
7273 still be useful.&lt;/p&gt;
7274
7275 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
7276 external keyboard? I&#39;ll have to check the
7277 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
7278 well-supported laptops, or perhaps just buy one preinstalled from one
7279 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
7280 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
7281 </description>
7282 </item>
7283
7284 <item>
7285 <title>How to find a browser plugin supporting a given MIME type</title>
7286 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
7287 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
7288 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
7289 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
7290 install to get support for a given MIME type. Thanks to
7291 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
7292 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
7293 Unfortunately, not very many packages provide the needed meta
7294 information, Anyway, here is a small script to look up all browser
7295 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
7296
7297 &lt;pre&gt;
7298 #!/usr/bin/python
7299 import sys
7300 import apt
7301 def pkgs_handling_mimetype(mimetype):
7302 cache = apt.Cache()
7303 cache.open(None)
7304 thepkgs = []
7305 for pkg in cache:
7306 version = pkg.candidate
7307 if version is None:
7308 version = pkg.installed
7309 if version is None:
7310 continue
7311 record = version.record
7312 if not record.has_key(&#39;Npp-MimeType&#39;):
7313 continue
7314 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
7315 for t in mime_types:
7316 t = t.rstrip().strip()
7317 if t == mimetype:
7318 thepkgs.append(pkg.name)
7319 return thepkgs
7320 mimetype = &quot;audio/ogg&quot;
7321 if 1 &lt; len(sys.argv):
7322 mimetype = sys.argv[1]
7323 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
7324 for pkg in pkgs_handling_mimetype(mimetype):
7325 print &quot; %s&quot; %pkg
7326 &lt;/pre&gt;
7327
7328 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
7329
7330 &lt;pre&gt;
7331 % ./apt-find-browserplug-for-mimetype
7332 Browser plugin packages supporting audio/ogg:
7333 gecko-mediaplayer
7334 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7335 Browser plugin packages supporting application/x-shockwave-flash:
7336 browser-plugin-gnash
7337 %
7338 &lt;/pre&gt;
7339
7340 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
7341 itself to query for plugins and propose to install the needed
7342 packages. It would be great if Debian supported such feature too. Is
7343 anyone working on adding it?&lt;/p&gt;
7344
7345 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
7346 request for icweasel support for this feature is
7347 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
7348 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
7349 of manpower and wish for a different design is the reason thus feature
7350 is not yet in iceweasel from Debian.&lt;/p&gt;
7351 </description>
7352 </item>
7353
7354 <item>
7355 <title>What is the most supported MIME type in Debian?</title>
7356 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
7357 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
7358 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
7359 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
7360 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
7361 proposal to make it possible for a Desktop application to propose to
7362 the user some package to install to gain support for a given MIME
7363 type, font, library etc. that is currently missing. With such
7364 mechanism in place, it would be possible for the desktop to
7365 automatically propose and install leocad if some LDraw file is
7366 downloaded by the browser.&lt;/p&gt;
7367
7368 &lt;p&gt;To get some idea about the current content of the archive, I decided
7369 to write a simple program to extract all .desktop files from the
7370 Debian archive and look up the claimed MIME support there. The result
7371 can be found on the
7372 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
7373 site&lt;/a&gt;. Using the collected information, it become possible to
7374 answer the question in the title. Here are the 20 most supported MIME
7375 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7376 The complete list is available from the link above.&lt;/p&gt;
7377
7378 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
7379
7380 &lt;pre&gt;
7381 count MIME type
7382 ----- -----------------------
7383 32 text/plain
7384 30 audio/mpeg
7385 29 image/png
7386 28 image/jpeg
7387 27 application/ogg
7388 26 audio/x-mp3
7389 25 image/tiff
7390 25 image/gif
7391 22 image/bmp
7392 22 audio/x-wav
7393 20 audio/x-flac
7394 19 audio/x-mpegurl
7395 18 video/x-ms-asf
7396 18 audio/x-musepack
7397 18 audio/x-mpeg
7398 18 application/x-ogg
7399 17 video/mpeg
7400 17 audio/x-scpls
7401 17 audio/ogg
7402 16 video/x-ms-wmv
7403 &lt;/pre&gt;
7404
7405 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
7406
7407 &lt;pre&gt;
7408 count MIME type
7409 ----- -----------------------
7410 33 text/plain
7411 32 image/png
7412 32 image/jpeg
7413 29 audio/mpeg
7414 27 image/gif
7415 26 image/tiff
7416 26 application/ogg
7417 25 audio/x-mp3
7418 22 image/bmp
7419 21 audio/x-wav
7420 19 audio/x-mpegurl
7421 19 audio/x-mpeg
7422 18 video/mpeg
7423 18 audio/x-scpls
7424 18 audio/x-flac
7425 18 application/x-ogg
7426 17 video/x-ms-asf
7427 17 text/html
7428 17 audio/x-musepack
7429 16 image/x-xbitmap
7430 &lt;/pre&gt;
7431
7432 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
7433
7434 &lt;pre&gt;
7435 count MIME type
7436 ----- -----------------------
7437 31 text/plain
7438 31 image/png
7439 31 image/jpeg
7440 29 audio/mpeg
7441 28 application/ogg
7442 27 image/gif
7443 26 image/tiff
7444 26 audio/x-mp3
7445 23 audio/x-wav
7446 22 image/bmp
7447 21 audio/x-flac
7448 20 audio/x-mpegurl
7449 19 audio/x-mpeg
7450 18 video/x-ms-asf
7451 18 video/mpeg
7452 18 audio/x-scpls
7453 18 application/x-ogg
7454 17 audio/x-musepack
7455 16 video/x-ms-wmv
7456 16 video/x-msvideo
7457 &lt;/pre&gt;
7458
7459 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
7460 information mentioned in DEP-11. I have not yet had time to look at
7461 it, but hope the PackageKit people in Debian are on top of these
7462 issues.&lt;/p&gt;
7463
7464 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
7465 discovering a typo in my script.&lt;/p&gt;
7466 </description>
7467 </item>
7468
7469 <item>
7470 <title>Using modalias info to find packages handling my hardware</title>
7471 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
7472 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
7473 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
7474 <description>&lt;p&gt;Yesterday, I wrote about the
7475 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
7476 values provided by the Linux kernel&lt;/a&gt; following my hope for
7477 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
7478 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
7479 modalias values attached to package names can be used to map packages
7480 to hardware. This allow the system to look up and suggest relevant
7481 packages when I plug in some new hardware into my machine, and replace
7482 discover and discover-data as the database used to map hardware to
7483 packages.&lt;/p&gt;
7484
7485 &lt;p&gt;I create a modaliases file with entries like the following,
7486 containing package name, kernel module name (if relevant, otherwise
7487 the package name) and globs matching the relevant hardware
7488 modalias.&lt;/p&gt;
7489
7490 &lt;p&gt;&lt;blockquote&gt;
7491 Package: package-name
7492 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
7493 &lt;/blockquote&gt;&lt;/p&gt;
7494
7495 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
7496 for a given modalias value using this file.&lt;/p&gt;
7497
7498 &lt;p&gt;An entry like this would suggest the video and picture application
7499 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
7500
7501 &lt;p&gt;&lt;blockquote&gt;
7502 Package: cheese
7503 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
7504 &lt;/blockquote&gt;&lt;/p&gt;
7505
7506 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
7507 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
7508
7509 &lt;p&gt;&lt;blockquote&gt;
7510 Package: pcmciautils
7511 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7512 &lt;/blockquote&gt;&lt;/p&gt;
7513
7514 &lt;p&gt;An entry like this would suggest the package colorhug-client when
7515 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
7516
7517 &lt;p&gt;&lt;blockquote&gt;
7518 Package: colorhug-client
7519 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
7520 &lt;/blockquote&gt;&lt;/p&gt;
7521
7522 &lt;p&gt;I believe the format is compatible with the format of the Packages
7523 file in the Debian archive. Ubuntu already uses their Packages file
7524 to store their mappings from packages to hardware.&lt;/p&gt;
7525
7526 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
7527 announce the hardware it support in a way my prototype understand.
7528 This allow those publishing packages in an APT source outside the
7529 Debian archive as well as those backporting packages to make sure the
7530 hardware mapping are included in the package meta information. I&#39;ve
7531 tested such header in the pymissile package, and its modalias mapping
7532 is working as it should with my prototype. It even made it to Ubuntu
7533 Raring.&lt;/p&gt;
7534
7535 &lt;p&gt;To test if it was possible to look up supported hardware using only
7536 the shell tools available in the Debian installer, I wrote a shell
7537 implementation of the lookup code. The idea is to create files for
7538 each modalias and let the shell do the matching. Please check out and
7539 try the
7540 &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;
7541 shell script. It run without any extra dependencies and fetch the
7542 hardware mappings from the Debian archive and the subversion
7543 repository where I currently work on my prototype.&lt;/p&gt;
7544
7545 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
7546 install yubikey-personalization:&lt;/p&gt;
7547
7548 &lt;p&gt;&lt;blockquote&gt;
7549 % ./hw-support-lookup
7550 &lt;br&gt;yubikey-personalization
7551 &lt;br&gt;%
7552 &lt;/blockquote&gt;&lt;/p&gt;
7553
7554 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7555 propose to install the pcmciautils package:&lt;/p&gt;
7556
7557 &lt;p&gt;&lt;blockquote&gt;
7558 % ./hw-support-lookup
7559 &lt;br&gt;pcmciautils
7560 &lt;br&gt;%
7561 &lt;/blockquote&gt;&lt;/p&gt;
7562
7563 &lt;p&gt;If you know of any hardware-package mapping that should be added to
7564 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
7565 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
7566
7567 &lt;p&gt;It could be possible to generate several of the mappings between
7568 packages and hardware. One source would be to look at packages with
7569 kernel modules, ie packages with *.ko files in /lib/modules/, and
7570 extract their modalias information. Another would be to look at
7571 packages with udev rules, ie packages with files in
7572 /lib/udev/rules.d/, and extract their vendor/model information to
7573 generate a modalias matching rule. I have not tested any of these to
7574 see if it work.&lt;/p&gt;
7575
7576 &lt;p&gt;If you want to help implementing a system to let us propose what
7577 packages to install when new hardware is plugged into a Debian
7578 machine, please send me an email or talk to me on
7579 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7580 </description>
7581 </item>
7582
7583 <item>
7584 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7585 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7586 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7587 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7588 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7589 information, to find the packages that support a given piece of
7590 hardware, I refreshed my memory regarding modalias values, and decided
7591 to document the details. Here are my findings so far, also available
7592 in
7593 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7594 Debian Edu subversion repository&lt;/a&gt;:
7595
7596 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7597
7598 &lt;p&gt;This document try to explain what the different types of modalias
7599 values stands for. It is in part based on information from
7600 &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;,
7601 &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;,
7602 &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
7603 &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;.
7604
7605 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7606 this shell script:&lt;/p&gt;
7607
7608 &lt;pre&gt;
7609 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7610 &lt;/pre&gt;
7611
7612 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7613 using modinfo:&lt;/p&gt;
7614
7615 &lt;pre&gt;
7616 % /sbin/modinfo psmouse | grep alias:
7617 alias: serio:ty05pr*id*ex*
7618 alias: serio:ty01pr*id*ex*
7619 %
7620 &lt;/pre&gt;
7621
7622 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7623
7624 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7625 Bridge memory controller:&lt;/p&gt;
7626
7627 &lt;p&gt;&lt;blockquote&gt;
7628 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7629 &lt;/blockquote&gt;&lt;/p&gt;
7630
7631 &lt;p&gt;This represent these values:&lt;/p&gt;
7632
7633 &lt;pre&gt;
7634 v 00008086 (vendor)
7635 d 00002770 (device)
7636 sv 00001028 (subvendor)
7637 sd 000001AD (subdevice)
7638 bc 06 (bus class)
7639 sc 00 (bus subclass)
7640 i 00 (interface)
7641 &lt;/pre&gt;
7642
7643 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7644 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7645 0600. The 0600 class is a host bridge. Other useful bus values are
7646 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7647
7648 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7649 means.&lt;/p&gt;
7650
7651 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7652
7653 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7654 USB hub in a laptop:&lt;/p&gt;
7655
7656 &lt;p&gt;&lt;blockquote&gt;
7657 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7658 &lt;/blockquote&gt;&lt;/p&gt;
7659
7660 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7661
7662 &lt;pre&gt;
7663 v 1D6B (device vendor)
7664 p 0001 (device product)
7665 d 0206 (bcddevice)
7666 dc 09 (device class)
7667 dsc 00 (device subclass)
7668 dp 00 (device protocol)
7669 ic 09 (interface class)
7670 isc 00 (interface subclass)
7671 ip 00 (interface protocol)
7672 &lt;/pre&gt;
7673
7674 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7675 class is in the interface class section. For a simple USB web camera,
7676 these alias entries show up:&lt;/p&gt;
7677
7678 &lt;p&gt;&lt;blockquote&gt;
7679 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7680 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7681 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7682 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7683 &lt;/blockquote&gt;&lt;/p&gt;
7684
7685 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7686 camera), 0101 is audio control device and 0102 is audio streaming (aka
7687 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7688
7689 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7690
7691 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7692 receiver in a Thinkpad X40:&lt;/p&gt;
7693
7694 &lt;p&gt;&lt;blockquote&gt;
7695 acpi:IBM0071:PNP0511:
7696 &lt;/blockquote&gt;&lt;/p&gt;
7697
7698 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7699
7700 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7701
7702 &lt;p&gt;The DMI table contain lots of information about the computer case
7703 and model. This is an entry for a IBM Thinkpad X40, fetched from
7704 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7705
7706 &lt;p&gt;&lt;blockquote&gt;
7707 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7708 &lt;/blockquote&gt;&lt;/p&gt;
7709
7710 &lt;p&gt;The values present are&lt;/p&gt;
7711
7712 &lt;pre&gt;
7713 bvn IBM (BIOS vendor)
7714 bvr 1UETB6WW(1.66) (BIOS version)
7715 bd 06/15/2005 (BIOS date)
7716 svn IBM (system vendor)
7717 pn 2371H4G (product name)
7718 pvr ThinkPadX40 (product version)
7719 rvn IBM (board vendor)
7720 rn 2371H4G (board name)
7721 rvr NotAvailable (board version)
7722 cvn IBM (chassis vendor)
7723 ct 10 (chassis type)
7724 cvr NotAvailable (chassis version)
7725 &lt;/pre&gt;
7726
7727 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7728 found in the dmidecode source:&lt;/p&gt;
7729
7730 &lt;pre&gt;
7731 3 Desktop
7732 4 Low Profile Desktop
7733 5 Pizza Box
7734 6 Mini Tower
7735 7 Tower
7736 8 Portable
7737 9 Laptop
7738 10 Notebook
7739 11 Hand Held
7740 12 Docking Station
7741 13 All In One
7742 14 Sub Notebook
7743 15 Space-saving
7744 16 Lunch Box
7745 17 Main Server Chassis
7746 18 Expansion Chassis
7747 19 Sub Chassis
7748 20 Bus Expansion Chassis
7749 21 Peripheral Chassis
7750 22 RAID Chassis
7751 23 Rack Mount Chassis
7752 24 Sealed-case PC
7753 25 Multi-system
7754 26 CompactPCI
7755 27 AdvancedTCA
7756 28 Blade
7757 29 Blade Enclosing
7758 &lt;/pre&gt;
7759
7760 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7761 table. For example my home server is a tower, but the DMI modalias
7762 claim it is a desktop.&lt;/p&gt;
7763
7764 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7765
7766 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7767 test machine:&lt;/p&gt;
7768
7769 &lt;p&gt;&lt;blockquote&gt;
7770 serio:ty01pr00id00ex00
7771 &lt;/blockquote&gt;&lt;/p&gt;
7772
7773 &lt;p&gt;The values present are&lt;/p&gt;
7774
7775 &lt;pre&gt;
7776 ty 01 (type)
7777 pr 00 (prototype)
7778 id 00 (id)
7779 ex 00 (extra)
7780 &lt;/pre&gt;
7781
7782 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7783 the valid values are.&lt;/p&gt;
7784
7785 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7786
7787 &lt;p&gt;There are heaps of other modalias subtypes according to
7788 file2alias.c. There is the rest of the list from that source: amba,
7789 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7790 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7791 vmbus, x86cpu and zorro. I did not spend time documenting all of
7792 these, as they do not seem relevant for my intended use with mapping
7793 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7794
7795 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7796
7797 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7798 one can use the following shell script:&lt;/p&gt;
7799
7800 &lt;pre&gt;
7801 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7802 echo &quot;$id&quot; ; \
7803 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7804 done
7805 &lt;/pre&gt;
7806
7807 &lt;p&gt;The output can look like this (only the first few entries as the
7808 list is very long on my test machine):&lt;/p&gt;
7809
7810 &lt;pre&gt;
7811 acpi:ACPI0003:
7812 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7813 acpi:device:
7814 FATAL: Module acpi:device: not found.
7815 acpi:IBM0068:
7816 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7817 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7818 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7819 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7820 acpi:IBM0071:PNP0511:
7821 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7822 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7823 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7824 [...]
7825 &lt;/pre&gt;
7826
7827 &lt;p&gt;If you want to help implementing a system to let us propose what
7828 packages to install when new hardware is plugged into a Debian
7829 machine, please send me an email or talk to me on
7830 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7831
7832 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7833 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7834 in /sys/ with space in them.&lt;/p&gt;
7835 </description>
7836 </item>
7837
7838 <item>
7839 <title>Moved the pymissile Debian packaging to collab-maint</title>
7840 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7842 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7843 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7844 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7845 Launcher and updated the Debian package
7846 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7847 sure udev will fix the device permissions when it is plugged in. I
7848 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7849 hopefully make the package be proposed by jockey in Ubuntu when a user
7850 plug in his rocket launcher. In the process I moved the source to a
7851 git repository under collab-maint, to make it easier for any DD to
7852 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7853 is not very active, but the software still work for me even after five
7854 years of relative silence. The new git repository is not listed in
7855 the uploaded package yet, because I want to test the other changes a
7856 bit more before I upload the new version. If you want to check out
7857 the new version with a .desktop file included, visit the
7858 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7859 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7860 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7861 </description>
7862 </item>
7863
7864 <item>
7865 <title>Lets make hardware dongles easier to use in Debian</title>
7866 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7867 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7868 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7869 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7870 general, is that there is a great package management system with the
7871 ability to automatically install software packages by downloading them
7872 from the distribution mirrors, but no way to get it to automatically
7873 install the packages I need to use the hardware I plug into my
7874 machine. Even if the package to use it is easily available from the
7875 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7876 suggest to automatically install the python-nxt, nbc and t2n packages
7877 I need to talk to it. When I plug in a Yubikey, it could propose the
7878 yubikey-personalization package. The information required to do this
7879 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7880
7881 &lt;p&gt;Some years ago, I proposed to
7882 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7883 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7884 simple:
7885
7886 &lt;ul&gt;
7887
7888 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7889 starting when a user log in.&lt;/li&gt;
7890
7891 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7892 hardware is inserted into the computer.&lt;/li&gt;
7893
7894 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7895 database mapping to packages, and take note of any non-installed
7896 packages.&lt;/li&gt;
7897
7898 &lt;li&gt;Show a message to the user proposing to install the discovered
7899 package, and make it easy to install it.&lt;/li&gt;
7900
7901 &lt;/ul&gt;
7902
7903 &lt;p&gt;I am not sure what the best way to implement this is, but my
7904 initial idea was to use dbus events to discover new hardware, the
7905 discover database to find packages and
7906 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7907 packages.&lt;/p&gt;
7908
7909 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7910 draft package is now checked into
7911 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7912 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7913 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7914 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7915 the relevant packages in Debian, and uploaded a new version
7916 2.2013.01.09 to unstable. I also discovered that the current
7917 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7918 package in Debian no longer discovered any USB devices, because
7919 /proc/bus/usb/devices is no longer present. I ported it to use
7920 libusb as a fall back option to get it working. The fixed package
7921 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7922 because of the freeze).&lt;/p&gt;
7923
7924 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7925 desktop notification to show up (only once, the first time it is
7926 inserted):&lt;/p&gt;
7927
7928 &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;
7929
7930 &lt;p&gt;For this prototype to be really useful, some way to automatically
7931 install the proposed packages by pressing the &quot;Please install
7932 program(s)&quot; button should to be implemented.&lt;/p&gt;
7933
7934 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7935 happen, please help me update the discover-data database with mappings
7936 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7937 list the package you would like to have installed when a given
7938 hardware device is inserted into your computer, and report bugs using
7939 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7940 such mapping, please let me know.&lt;/p&gt;
7941
7942 &lt;p&gt;This prototype need more work, and there are several questions that
7943 should be considered before it is ready for production use. Is dbus
7944 the correct way to detect new hardware? At the moment I look for HAL
7945 dbus events on the system bus, because that is the events I could see
7946 on my Debian Squeeze KDE desktop. Are there better events to use?
7947 How should the user be notified? Is the desktop notification
7948 mechanism the best option, or should the background daemon raise a
7949 popup instead? How should packages be installed? When should they
7950 not be installed?&lt;/p&gt;
7951
7952 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7953 please send me an email. :)&lt;/p&gt;
7954 </description>
7955 </item>
7956
7957 <item>
7958 <title>New IRC channel for LEGO designers using Debian</title>
7959 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7961 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7962 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7963 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7964 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7965 discovered I had to build all the tools myself because none were
7966 already in Debian Squeeze. If Debian support for LEGO is something
7967 you care about, please join me on the IRC channel
7968 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7969 irc.debian.org). There is a lot that could be done to improve the
7970 Debian support for LEGO designers. For example both CAD software
7971 and Mindstorm compilers are missing. :)&lt;/p&gt;
7972
7973 &lt;p&gt;Update 2012-01-03: A
7974 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7975 including links to Lego related packages is now available.&lt;/p&gt;
7976 </description>
7977 </item>
7978
7979 <item>
7980 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7981 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7983 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7984 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7985 year! I hope next year will prove to be a good year.&lt;/p&gt;
7986
7987 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7988 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7989 between each other with minimal overhead, is a very interesting
7990 experiment. And as I wrote a few days ago, the bitcoin situation in
7991 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7992 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7993 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7994 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7995 for one of the ftpmasters to approve the new bitcoin-qt package
7996 name.&lt;/p&gt;
7997
7998 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7999 team in Debian, you can easily test the package in Debian Squeeze
8000 using the following steps to get a set of working packages:&lt;/p&gt;
8001
8002 &lt;blockquote&gt;&lt;pre&gt;
8003 git clone git://git.debian.org/git/collab-maint/bitcoin
8004 cd bitcoin
8005 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8006 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8007 &lt;/pre&gt;&lt;/blockquote&gt;
8008
8009 &lt;p&gt;You might have to install some build dependencies as well. The
8010 list of commands should give you two packages, bitcoind and
8011 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8012 client will download the complete set of bitcoin &quot;blocks&quot;, which need
8013 around 5.6 GiB of data on my machine at the moment. Make sure your
8014 ~/.bitcoin/ directory have lots of spare room if you want to download
8015 all the blocks. The client will warn if the disk is getting full, so
8016 there is not really a problem if you got too little room, but you will
8017 not be able to get all the features out of the client.&lt;/p&gt;
8018
8019 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8020 activities, please send Bitcoin donations to my address
8021 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8022 </description>
8023 </item>
8024
8025 <item>
8026 <title>A word on bitcoin support in Debian</title>
8027 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
8028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
8029 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
8030 <description>&lt;p&gt;It has been a while since I wrote about
8031 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
8032 peer-to-peer based crypto-currency, and the reason is simply that I
8033 have been busy elsewhere. But two days ago, I started looking at the
8034 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
8035 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
8036 is now maintained by a
8037 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
8038 people&lt;/a&gt;, and the grunt work had already been done by this team. We
8039 owe a huge thank you to all these team members. :)
8040 But I was sad to discover that the bitcoin client is missing in
8041 Wheezy. It is only available in Sid (and an outdated client from
8042 backports). The client had several RC bugs registered in BTS blocking
8043 it from entering testing. To try to help the team and improve the
8044 situation, I spent some time providing patches and triaging the bug
8045 reports. I also had a look at the bitcoin package available from Matt
8046 Corallo in a
8047 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
8048 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
8049 Debian package.&lt;/p&gt;
8050
8051 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
8052 IRC, I pushed several patches into the collab-maint git repository to
8053 improve the package. It now contains fixes for the RC issues (not from
8054 me, but fixed by Scott Howard), build rules for a Qt GUI client
8055 package, konqueror support for the bitcoin: URI and bash completion
8056 setup. As I work on Debian Squeeze, I also created
8057 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
8058 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
8059 it and try to integrate it into the git repository before uploading a
8060 new version to unstable.
8061
8062 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
8063 centralized control currently exercised in the monetary system. I
8064 find it completely unacceptable that the USA government is collecting
8065 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8066 that the major credit card companies can block legal money
8067 transactions to Wikileaks. But for bitcoin to succeed, more people
8068 need to use bitcoins, and more people need to accept bitcoins when
8069 they sell products and services. Improving the bitcoin support in
8070 Debian is a small step in the right direction, but not enough.
8071 Unfortunately the user experience when browsing the web and wanting to
8072 pay with bitcoin is still not very good. The bitcoin: URI is a step
8073 in the right direction, but need to work in most or every browser in
8074 use. Also the bitcoin-qt client is too heavy to fire up to do a
8075 quick transaction. I believe there are other clients available, but
8076 have not tested them.&lt;/p&gt;
8077
8078 &lt;p&gt;My
8079 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
8080 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
8081 I received 20.15 BTC so far on the address I provided in my blog two
8082 years ago, as can be
8083 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
8084 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
8085 donation. The blockexplorer service demonstrates quite well that
8086 bitcoin is not quite anonymous and untracked. :) I wonder if the
8087 number of users have gone up since then. If you use bitcoin and want
8088 to show your support of my activity, please send Bitcoin donations to
8089 the same address as last time,
8090 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8091 </description>
8092 </item>
8093
8094 <item>
8095 <title>Git repository for song book for Computer Scientists</title>
8096 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
8097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
8098 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
8099 <description>&lt;p&gt;As I
8100 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
8101 this summer&lt;/a&gt;, I have created a Computer Science song book a few
8102 years ago, and today I finally found time to create a public
8103 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
8104 repository for the project&lt;/a&gt;.&lt;/p&gt;
8105
8106 &lt;p&gt;If you want to help out, please clone the source and submit patches
8107 to the HTML version. To generate the PDF and PostScript version,
8108 please use prince XML, or let me know about a useful free software
8109 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
8110
8111 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
8112 PostScript formats at
8113 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
8114 Science Songbook&lt;/a&gt;.&lt;/p&gt;
8115 </description>
8116 </item>
8117
8118 <item>
8119 <title>Gratulerer med 19-årsdagen, Debian!</title>
8120 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
8121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
8122 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
8123 <description>&lt;p&gt;I dag fyller
8124 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
8125 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
8126 si gratulerer med dagen, Debian!&lt;/p&gt;
8127 </description>
8128 </item>
8129
8130 <item>
8131 <title>Song book for Computer Scientists</title>
8132 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
8133 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
8134 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
8135 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
8136 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
8137 collecting computer related songs for use at parties. The original
8138 version was written in LaTeX, but a few years ago I got help from
8139 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
8140 while keeping the ability to create a nice book in PDF format. I have
8141 not had time to maintain the book for a while now, and guess I should
8142 put it up on some public version control repository where others can
8143 help me extend and update the book. If anyone is volunteering to help
8144 me with this, send me an email. Also let me know if there are songs
8145 missing in my book.&lt;/p&gt;
8146
8147 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
8148 me today that I really should let all my readers share the joys of
8149 singing out load about programming, computers and computer networks.
8150 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
8151 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
8152 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
8153 Computer Science Songbook&lt;/a&gt;.
8154 </description>
8155 </item>
8156
8157 <item>
8158 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
8159 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
8160 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
8161 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
8162 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
8163 around 1000 at the moment. To be able to get help from the vendors
8164 when something go wrong, we want to keep the firmware on the servers
8165 up to date. If the firmware isn&#39;t the latest and greatest, the
8166 vendors typically refuse to start debugging any problems until the
8167 firmware is upgraded. So before every reboot, we want to upgrade the
8168 firmware, and we would really like everyone handling servers at the
8169 university to do this themselves when they plan to reboot a machine.
8170 For that to happen we at the unix server admin group need to provide
8171 the tools to do so.&lt;/p&gt;
8172
8173 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
8174 fetch and install the latest firmware for the servers we got. Most of
8175 our hardware are from Dell and HP, so I have focused on these servers
8176 so far. This blog post is about the Dell part.&lt;/P&gt;
8177
8178 &lt;p&gt;On the Dell FTP site I was lucky enough to find
8179 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
8180 with firmware information for all 11th generation servers, listing
8181 which firmware should be used on a given model and where on the FTP
8182 site I can find it. Using a simple perl XML parser I can then
8183 download the shell scripts Dell provides to do firmware upgrades from
8184 within Linux and reboot when all the firmware is primed and ready to
8185 be activated on the first reboot.&lt;/p&gt;
8186
8187 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
8188 Are there anyone working on similar tools for firmware upgrading all
8189 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
8190
8191 &lt;p&gt;&lt;pre&gt;
8192 #!/usr/bin/perl
8193 use strict;
8194 use warnings;
8195 use File::Temp qw(tempdir);
8196 BEGIN {
8197 # Install needed RHEL packages if missing
8198 my %rhelmodules = (
8199 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
8200 );
8201 for my $module (keys %rhelmodules) {
8202 eval &quot;use $module;&quot;;
8203 if ($@) {
8204 my $pkg = $rhelmodules{$module};
8205 system(&quot;yum install -y $pkg&quot;);
8206 eval &quot;use $module;&quot;;
8207 }
8208 }
8209 }
8210 my $errorsto = &#39;pere@hungry.com&#39;;
8211
8212 upgrade_dell();
8213
8214 exit 0;
8215
8216 sub run_firmware_script {
8217 my ($opts, $script) = @_;
8218 unless ($script) {
8219 print STDERR &quot;fail: missing script name\n&quot;;
8220 exit 1
8221 }
8222 print STDERR &quot;Running $script\n\n&quot;;
8223
8224 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
8225 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
8226 } else {
8227 print STDERR &quot;fail: firmware script returned error\n&quot;;
8228 }
8229 }
8230
8231 sub run_firmware_scripts {
8232 my ($opts, @dirs) = @_;
8233 # Run firmware packages
8234 for my $dir (@dirs) {
8235 print STDERR &quot;info: Running scripts in $dir\n&quot;;
8236 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
8237 while (my $s = readdir $dh) {
8238 next if $s =~ m/^\.\.?/;
8239 run_firmware_script($opts, &quot;$dir/$s&quot;);
8240 }
8241 closedir $dh;
8242 }
8243 }
8244
8245 sub download {
8246 my $url = shift;
8247 print STDERR &quot;info: Downloading $url\n&quot;;
8248 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
8249 }
8250
8251 sub upgrade_dell {
8252 my @dirs;
8253 my $product = `dmidecode -s system-product-name`;
8254 chomp $product;
8255
8256 if ($product =~ m/PowerEdge/) {
8257
8258 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8259 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
8260
8261 my $tmpdir = tempdir(
8262 CLEANUP =&gt; 1
8263 );
8264 chdir($tmpdir);
8265 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
8266 system(&#39;gunzip Catalog.xml.gz&#39;);
8267 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
8268 # -q is quiet, disabling interactivity and reducing console output
8269 my $fwopts = &quot;-q&quot;;
8270 if (@paths) {
8271 for my $url (@paths) {
8272 fetch_dell_fw($url);
8273 }
8274 run_firmware_scripts($fwopts, $tmpdir);
8275 } else {
8276 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8277 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8278 }
8279 chdir(&#39;/&#39;);
8280 } else {
8281 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8282 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8283 }
8284 }
8285
8286 sub fetch_dell_fw {
8287 my $path = shift;
8288 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
8289 download($url);
8290 }
8291
8292 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8293 # firmware packages to download from Dell. Only work for Linux
8294 # machines and 11th generation Dell servers.
8295 sub fetch_dell_fw_list {
8296 my $filename = shift;
8297
8298 my $product = `dmidecode -s system-product-name`;
8299 chomp $product;
8300 my ($mybrand, $mymodel) = split(/\s+/, $product);
8301
8302 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
8303
8304 my $xml = XMLin($filename);
8305 my @paths;
8306 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
8307 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
8308 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
8309 my $oscode;
8310 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
8311 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
8312 } else {
8313 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
8314 }
8315 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
8316 {
8317 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
8318 }
8319 }
8320 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
8321 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
8322
8323 # Drop application packages, only firmware and BIOS
8324 next if &#39;APAC&#39; eq $componenttype;
8325
8326 my $cpath = $component-&gt;{path};
8327 for my $path (@paths) {
8328 if ($cpath =~ m%/$path$%) {
8329 push(@paths, $cpath);
8330 }
8331 }
8332 }
8333 return @paths;
8334 }
8335 &lt;/pre&gt;
8336
8337 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
8338 it could work on other platforms with some tweaking. Anyone know a
8339 index like Catalog.xml is available from HP for HP servers? At the
8340 moment I maintain a similar list manually and it is quickly getting
8341 outdated.&lt;/p&gt;
8342 </description>
8343 </item>
8344
8345 <item>
8346 <title>How is booting into runlevel 1 different from single user boots?</title>
8347 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
8348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
8349 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
8350 <description>&lt;p&gt;Wouter Verhelst have some
8351 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
8352 comments and opinions&lt;/a&gt; on my blog post on
8353 &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
8354 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
8355 &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
8356 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
8357 small piece of his comment now, and though it best to address the
8358 misunderstanding he bring forward:&lt;/p&gt;
8359
8360 &lt;p&gt;&lt;blockquote&gt;
8361 Currently, a system admin has four options: [...] boot to a
8362 single-user system (by adding &#39;single&#39; to the kernel command line;
8363 this runs rcS and rc1 scripts)
8364 &lt;/blockquote&gt;&lt;/p&gt;
8365
8366 &lt;p&gt;This make me believe Wouter believe booting into single user mode
8367 and booting into runlevel 1 is the same. I am not surprised he
8368 believe this, because it would make sense and is a quite sensible
8369 thing to believe. But because the boot in Debian is slightly broken,
8370 runlevel 1 do not work properly and it isn&#39;t the same as single user
8371 mode. I&#39;ll try to explain what is actually happing, but it is a bit
8372 hard to explain.&lt;/p&gt;
8373
8374 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
8375 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
8376 executed in single user mode is sulogin. Single user mode is a boot
8377 state &quot;between&quot; the runlevels, and when booting into single user mode,
8378 only the scripts in /etc/rcS.d/ are executed before the init process
8379 enters the single user state. When switching to runlevel 1, the state
8380 is in fact not ending in runlevel 1, but it passes through runlevel 1
8381 and end up in the single user mode (see /etc/rc1.d/S03single, which
8382 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
8383 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
8384 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8385 mode).&lt;/p&gt;
8386
8387 &lt;p&gt;This summary might make it clearer. When booting for the first
8388 time into single user mode, the following commands are executed:
8389 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
8390 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
8391 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
8392 trying to continue after visiting single user mode. Not all services
8393 are started again as they should, causing the machine to end up in an
8394 unpredicatble state. This is why Debian admins recommend rebooting
8395 after visiting single user mode.&lt;/p&gt;
8396
8397 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
8398 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
8399 to runlevel 1, the services started from /etc/rcS.d/ are not properly
8400 stopped when passing through the scripts in /etc/rc1.d/, and not
8401 started again when switching away from runlevel 1 to the runlevels
8402 2-5. I believe the problem is best fixed by moving all the scripts
8403 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
8404 functioning single user mode during boot.&lt;/p&gt;
8405
8406 &lt;p&gt;I have spent several years investigating the Debian boot system,
8407 and discovered this problem a few years ago. I suspect it originates
8408 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
8409 </description>
8410 </item>
8411
8412 <item>
8413 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
8414 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
8415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
8416 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
8417 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
8418 are started from /etc/rcS.d/. In fact, there is a bite more of them
8419 than make sense, and this causes a few problems. What kind of
8420 problems, you might ask. There are at least two problems. The first
8421 is that it is not possible to recover a machine after switching to
8422 runlevel 1. One need to actually reboot to get the machine back to
8423 the expected state. The other is that single user boot will sometimes
8424 run into problems because some of the subsystems are activated before
8425 the root login is presented, causing problems when trying to recover a
8426 machine from a problem in that subsystem. A minor additional point is
8427 that moving more scripts out of rcS.d/ and into the other rc#.d/
8428 directories will increase the amount of scripts that can run in
8429 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
8430
8431 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
8432 scripts that _have_ to execute before the root login prompt is
8433 presented during a single user boot should go there. Everything else
8434 should go into the numeric runlevels. This means things like
8435 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8436 the numeric runlevels. Today in Debian, there are around 115 init.d
8437 scripts that are started from rcS.d/, and most of them should be moved
8438 out. Do your package have one of them? Please help us make single
8439 user and runlevel 1 better by moving it.&lt;/p&gt;
8440
8441 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
8442 etc. should still be started from rcS.d/, but there is for example no
8443 need to have the network enabled before the single user login prompt
8444 is presented.&lt;/p&gt;
8445
8446 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
8447 Debian systems working while scripts migrate and during upgrades, the
8448 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8449 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8450 and the next ones can only be moved when their dependencies have been
8451 moved first. This migration must be done sequentially while we ensure
8452 that the package system upgrade packages in the right order to keep
8453 the system state correct. This will require some coordination when it
8454 comes to network related packages, but most of the packages with
8455 scripts that should migrate do not have anything in rcS.d/ depending
8456 on them. Some packages have already been updated, like the sudo
8457 package, while others are still left to do. I wish I had time to work
8458 on this myself, but real live constrains make it unlikely that I will
8459 find time to push this forward.&lt;/p&gt;
8460 </description>
8461 </item>
8462
8463 <item>
8464 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
8465 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
8466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
8467 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
8468 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
8469 mentioned the issues I believe should be improved in Debian for its
8470 desktop to be useful for more people. The use case for this is my
8471 parents, which are currently running Kubuntu which solve the
8472 issues.&lt;/p&gt;
8473
8474 &lt;p&gt;I suspect these four missing features are not very hard to
8475 implement. After all, they are present in Ubuntu, so if we wanted to
8476 do this in Debian we would have a source.&lt;/p&gt;
8477
8478 &lt;ol&gt;
8479
8480 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
8481 are new packages available for upgrades, a icon in the KDE status bar
8482 indicate this, and clicking on it will activate the simple upgrade
8483 tool to handle it. I have no problem guiding both of my parents
8484 through the process over the phone. If a kernel reboot is required,
8485 this too is indicated by the status bars and the upgrade tool. Last
8486 time I checked, nothing with the same features was working in KDE in
8487 Debian.&lt;/li&gt;
8488
8489 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
8490 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
8491 currently have a handler for, it will ask the user if the system
8492 should search for a package that would add support for this MIME type,
8493 and if the user say yes, the APT sources will be searched for packages
8494 advertising the MIME type in their control file (visible in the
8495 Packages file in the APT archive). If one or more packages are found,
8496 it is a simple click of the mouse to add support for the missing mime
8497 type. If the package require the user to accept some non-free
8498 license, this is explained to the user. The entire process make it
8499 more clear to the user why something do not work in the browser, and
8500 make the chances higher for the user to blame the web page authors and
8501 not the browser for any missing features.&lt;/li&gt;
8502
8503 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
8504 handlers.&lt;/strong&gt; When the media players encounter a format or codec
8505 it is not supporting, a dialog pop up asking the user if the system
8506 should search for a package that would add support for it. This
8507 happen with things like MP3, Windows Media or H.264. The selection
8508 and installation procedure is very similar to the Firefox browser
8509 plugin handling. This is as far as I know implemented using a
8510 gstreamer hook. The end result is that the user easily get access to
8511 the codecs that are present from the APT archives available, while
8512 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
8513
8514 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
8515 displaying a text/plain file in my Debian browser, it will propose to
8516 start emacs to show it. If I remember correctly, when doing the same
8517 in Kunbutu it show the file as a text file in the browser. At least I
8518 know Opera will show text files within the browser. I much prefer the
8519 latter behaviour.&lt;/li&gt;
8520
8521 &lt;/ol&gt;
8522
8523 &lt;p&gt;There are other nice features as well, like the simplified suite
8524 upgrader, but given that I am the one mostly doing the dist-upgrade,
8525 it do not matter much.&lt;/p&gt;
8526
8527 &lt;p&gt;I really hope we could get these features in place for the next
8528 Debian release. It would require the coordinated effort of several
8529 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
8530 </description>
8531 </item>
8532
8533 <item>
8534 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
8535 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
8536 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
8537 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
8538 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
8539 site is build on Debian/Squeeze, and this platform was chosen because
8540 I am most familiar with Debian (being a Debian Developer for around 10
8541 years) because it is the latest stable Debian release which should get
8542 security support for a few years.&lt;/p&gt;
8543
8544 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
8545 that are missing in Debian at the moment. It would be great if these
8546 modules were added to the Debian archive, allowing anyone to set up
8547 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
8548 in their own country using only Debian packages. The list of modules
8549 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
8550 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
8551 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8552 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8553 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8554 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8555 easier in the future.&lt;/p&gt;
8556
8557 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
8558 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
8559 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
8560 with the responsibility of tracking security problems, which I really
8561 do not have time for.&lt;/p&gt;
8562 </description>
8563 </item>
8564
8565 <item>
8566 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
8567 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
8568 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
8569 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
8570 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
8571 posts have been in Norwegian the last few weeks, so here is a short
8572 update in English.&lt;/p&gt;
8573
8574 &lt;p&gt;The kids still keep me too busy to get much free software work
8575 done, but I did manage to organise a project to get a Norwegian port
8576 of the British service
8577 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8578 and it has been running for a month now. The entire project has been
8579 organised by me and two others. Around Christmas we gathered sponsors
8580 to fund the development work. In January I drafted a contract with
8581 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8582 and in February the development took place. Most of it involved
8583 converting the source to use GPS coordinates instead of British
8584 easting/northing, and the resulting code should be a lot easier to get
8585 running in any country by now. The Norwegian
8586 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8587 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8588 source and the source for administrative borders in Norway, and
8589 support for this had to be added/fixed.&lt;/p&gt;
8590
8591 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8592 polishing the system before we announced it March 7th. The system is
8593 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8594 problem reports in a few weeks. Soon we hope to announce the Android
8595 and iPhone versions making it even easier to report problems with the
8596 public infrastructure.&lt;/p&gt;
8597
8598 &lt;p&gt;Perhaps something to consider for those of you in countries without
8599 such service?&lt;/p&gt;
8600 </description>
8601 </item>
8602
8603 <item>
8604 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8605 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8607 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8608 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8609 issues here at my work with the University of Oslo. My idea is that
8610 it should be possible to use the information about security issues
8611 available on the Internet, and check our locally
8612 maintained/distributed software against this information. It should
8613 allow us to verify that no known security issues are forgotten. The
8614 CVE database listing vulnerabilities seem like a great central point,
8615 and by using the package lists from Debian mapped to CVEs provided by
8616 the testing security team, I believed it should be possible to figure
8617 out which security holes were present in our free software
8618 collection.&lt;/p&gt;
8619
8620 &lt;p&gt;After reading up on the topic, it became obvious that the first
8621 building block is to be able to name software packages in a unique and
8622 consistent way across data sources. I considered several ways to do
8623 this, for example coming up with my own naming scheme like using URLs
8624 to project home pages or URLs to the Freshmeat entries, or using some
8625 existing naming scheme. And it seem like I am not the first one to
8626 come across this problem, as MITRE already proposed and implemented a
8627 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8628 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8629 software, hardware and other platform components. The CPE ids are
8630 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8631 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8632 issues for any CPE name. With this in place, all I need to do is to
8633 locate the CPE id for the software packages we use at the university.
8634 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8635 NVD entry if a CVE for the package exist).&lt;/p&gt;
8636
8637 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8638 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8639 check out, one could look up
8640 &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
8641 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8642 The most recent one is
8643 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8644 and at the bottom of the NVD page for this vulnerability the complete
8645 list of affected versions is provided.&lt;/p&gt;
8646
8647 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8648 for offline processing of issues. Using this dump, I&#39;ve written a
8649 small script taking a list of CPEs as input and list all CVEs
8650 affecting the packages represented by these CPEs. One give it CPEs
8651 with version numbers as specified above and get a list of open
8652 security issues out.&lt;/p&gt;
8653
8654 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8655 information need to be high. For that to happen, I believe as many as
8656 possible need to use and contribute to the NVD database. I notice
8657 RHEL is providing
8658 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8659 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8660 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8661
8662 &lt;p&gt;To get an idea about the quality for free software, I spent some
8663 time making it possible to compare the CVE database from Debian with
8664 the CVE database in NVD. The result look fairly good, but there are
8665 some inconsistencies in NVD (same software package having several
8666 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8667 Debian believe are affected by a CVE). Hope to find time to improve
8668 the quality of NVD, but that require being able to get in touch with
8669 someone maintaining it. So far my three emails with questions and
8670 corrections have not seen any reply, but I hope contact can be
8671 established soon.&lt;/p&gt;
8672
8673 &lt;p&gt;An interesting application for CPEs is cross platform package
8674 mapping. It would be useful to know which packages in for example
8675 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8676 this would be trivial if all linux distributions provided CPE entries
8677 for their packages.&lt;/p&gt;
8678 </description>
8679 </item>
8680
8681 <item>
8682 <title>Which module is loaded for a given PCI and USB device?</title>
8683 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8685 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8686 <description>&lt;p&gt;In the
8687 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8688 package in Debian, there is a script to report useful information
8689 about the running hardware for use when people report missing
8690 information. One part of this script that I find very useful when
8691 debugging hardware problems, is the part mapping loaded kernel module
8692 to the PCI device it claims. It allow me to quickly see if the kernel
8693 module I expect is driving the hardware I am struggling with. To see
8694 the output, make sure discover-data is installed and run
8695 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8696 one of my machines like this:&lt;/p&gt;
8697
8698 &lt;pre&gt;
8699 loaded modules:
8700 10de:03eb i2c_nforce2
8701 10de:03f1 ohci_hcd
8702 10de:03f2 ehci_hcd
8703 10de:03f0 snd_hda_intel
8704 10de:03ec pata_amd
8705 10de:03f6 sata_nv
8706 1022:1103 k8temp
8707 109e:036e bttv
8708 109e:0878 snd_bt87x
8709 11ab:4364 sky2
8710 &lt;/pre&gt;
8711
8712 &lt;p&gt;The code in question look like this, slightly modified for
8713 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8714
8715 &lt;pre&gt;
8716 if [ -d /sys/bus/pci/devices/ ] ; then
8717 echo loaded pci modules:
8718 (
8719 cd /sys/bus/pci/devices/
8720 for address in * ; do
8721 if [ -d &quot;$address/driver/module&quot; ] ; then
8722 module=`cd $address/driver/module ; pwd -P | xargs basename`
8723 if grep -q &quot;^$module &quot; /proc/modules ; then
8724 address=$(echo $address |sed s/0000://)
8725 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8726 echo &quot;$id $module&quot;
8727 fi
8728 fi
8729 done
8730 )
8731 echo
8732 fi
8733 &lt;/pre&gt;
8734
8735 &lt;p&gt;Similar code could be used to extract USB device module
8736 mappings:&lt;/p&gt;
8737
8738 &lt;pre&gt;
8739 if [ -d /sys/bus/usb/devices/ ] ; then
8740 echo loaded usb modules:
8741 (
8742 cd /sys/bus/usb/devices/
8743 for address in * ; do
8744 if [ -d &quot;$address/driver/module&quot; ] ; then
8745 module=`cd $address/driver/module ; pwd -P | xargs basename`
8746 if grep -q &quot;^$module &quot; /proc/modules ; then
8747 address=$(echo $address |sed s/0000://)
8748 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8749 if [ &quot;$id&quot; ] ; then
8750 echo &quot;$id $module&quot;
8751 fi
8752 fi
8753 fi
8754 done
8755 )
8756 echo
8757 fi
8758 &lt;/pre&gt;
8759
8760 &lt;p&gt;This might perhaps be something to include in other tools as
8761 well.&lt;/p&gt;
8762 </description>
8763 </item>
8764
8765 <item>
8766 <title>How to test if a laptop is working with Linux</title>
8767 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8768 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8769 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8770 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8771 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8772 batch of computers will work with Linux. Every year for the last few
8773 years the university have organised shared bid of a few thousand
8774 computers, and this year HP won the bid. Two different desktops and
8775 five different laptops are on the list this year. We in the UNIX
8776 group want to know which one of these computers work well with RHEL
8777 and Ubuntu, the two Linux distributions we currently handle at the
8778 university.&lt;/p&gt;
8779
8780 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8781 perhaps inspire others to test hardware as well. To test, I PXE
8782 install the OS version of choice, and log in as my normal user and run
8783 a few applications and plug in selected pieces of hardware. When
8784 something fail, I make a note about this in the test matrix and move
8785 on. If I have some spare time I try to report the bug to the OS
8786 vendor, but as I only have the machines for a short time, I rarely
8787 have the time to do this for all the problems I find.&lt;/p&gt;
8788
8789 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8790 I perform on a new model.&lt;/p&gt;
8791
8792 &lt;ul&gt;
8793
8794 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8795 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8796 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8797
8798 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8799 installation, X.org is working.&lt;/li&gt;
8800
8801 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8802 package mesa-utils on Ubuntu) and writing down the frames per second
8803 reported by the program.&lt;/li&gt;
8804
8805 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8806 logging in, and if I can hear this the test is successful. If there
8807 are several audio exits on the machine, I try them all and check if
8808 the Gnome/KDE audio mixer can control where to send the sound. I
8809 normally test this by playing
8810 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8811 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8812
8813 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8814 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8815
8816 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8817 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8818
8819 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8820 picture from the v4l device show up.&lt;/li&gt;
8821
8822 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8823 any bluetooth devices are discovered. In my office, I normally see a
8824 few.&lt;/li&gt;
8825
8826 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8827 memory modules lying around, and stick them in and see if Gnome/KDE
8828 notice this.&lt;/li&gt;
8829
8830 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8831 special button work, and if the laptop continue to work after
8832 resume.&lt;/li&gt;
8833
8834 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8835 adjusting background light, switching on/off external video output,
8836 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8837 laptop to laptop, so I just write down which are working and which are
8838 not.&lt;/li&gt;
8839
8840 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8841 acceleration sensors etc. I rarely test these, as I do not know how
8842 to quickly test if they are working or not, so I only document their
8843 existence.&lt;/li&gt;
8844
8845 &lt;/ul&gt;
8846
8847 &lt;p&gt;By now I suspect you are really curious what the test results are
8848 for the HP machines I am testing. I&#39;m not done yet, so I will report
8849 the test results later. For now I can report that HP 8100 Elite work
8850 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8851 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8852 can see, I have most machines left to test. One interesting
8853 observation is that Ubuntu Lucid has almost twice the frame rate than
8854 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8855 </description>
8856 </item>
8857
8858 <item>
8859 <title>Some thoughts on BitCoins</title>
8860 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8861 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8862 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8863 <description>&lt;p&gt;As I continue to explore
8864 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8865 what properties the system have, and how it will be affected by laws
8866 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8867
8868 &lt;p&gt;One interesting thing to note is that since the transactions are
8869 verified using a peer to peer network, all details about a transaction
8870 is known to everyone. This means that if a BitCoin address has been
8871 published like I did with mine in my initial post about BitCoin, it is
8872 possible for everyone to see how many BitCoins have been transfered to
8873 that address. There is even a web service to look at the details for
8874 all transactions. There I can see that my address
8875 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8876 have received 16.06 Bitcoin, the
8877 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8878 address of Simon Phipps have received 181.97 BitCoin and the address
8879 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8880 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8881 every one of you that donated bitcoins to support my activity. The
8882 fact that anyone can see how much money was transfered to a given
8883 address make it more obvious why the BitCoin community recommend to
8884 generate and hand out a new address for each transaction. I&#39;m told
8885 there is no way to track which addresses belong to a given person or
8886 organisation without the person or organisation revealing it
8887 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8888
8889 &lt;p&gt;In Norway, and in most other countries, there are laws and
8890 regulations limiting how much money one can transfer across the border
8891 without declaring it. There are money laundering, tax and accounting
8892 laws and regulations I would expect to apply to the use of BitCoin.
8893 If the Skolelinux foundation
8894 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8895 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8896 normal bank transfers like EFF is doing, how should this be accounted?
8897 Given that it is impossible to know if money can cross the border or
8898 not, should everything or nothing be declared? What exchange rate
8899 should be used when calculating taxes? Would receivers have to pay
8900 income tax if the foundation were to pay Skolelinux contributors in
8901 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8902
8903 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8904 accepted by a lot of users. It must be possible to get easy access to
8905 the currency (as a wage or using currency exchanges), and it must be
8906 easy to spend it. At the moment BitCoin seem fairly easy to get
8907 access to, but there are very few places to spend it. I am not really
8908 a regular user of any of the vendor types currently accepting BitCoin,
8909 so I wonder when my kind of shop would start accepting BitCoins. I
8910 would like to buy electronics, travels and subway tickets, not herbs
8911 and books. :) The currency is young, and this will improve over time
8912 if it become popular, but I suspect regular banks will start to lobby
8913 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8914 will claim it is helping fund terrorism and money laundering (which
8915 probably would be true, as is any currency in existence), but I
8916 believe the problems should be solved elsewhere and not by blaming
8917 currencies.&lt;/p&gt;
8918
8919 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8920 CPU intensive process that depend on a bit of luck as well (as one is
8921 competing against all the other miners currently spending CPU cycles
8922 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8923 BitCoin when this happen. Yesterday I came across the obvious way to
8924 join forces to increase ones changes of getting at least some coins,
8925 by coordinating the work on mining BitCoins across several machines
8926 and people, and sharing the result if one is lucky and get the 50
8927 BitCoins. Check out
8928 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8929 if this sounds interesting. I have not had time to try to set up a
8930 machine to participate there yet, but have seen that running on ones
8931 own for a few days have not yield any BitCoins througth mining
8932 yet.&lt;/p&gt;
8933
8934 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8935 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8936 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8937 it was interesting to read. The arguments presented seem to be
8938 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8939 </description>
8940 </item>
8941
8942 <item>
8943 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8944 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8946 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8947 <description>&lt;p&gt;With this weeks lawless
8948 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8949 attacks&lt;/a&gt; on Wikileak and
8950 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8951 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8952 not be trusted to handle money transactions.
8953 A blog post from
8954 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8955 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8956 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8957 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8958 some help from my friend to get it all running, and he even handed me
8959 some bitcoins to get started. I even donated a few bitcoins to Simon
8960 for helping me remember BitCoin.&lt;/p&gt;
8961
8962 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8963 crypto-currency, decentralised and handled using peer-to-peer
8964 networks. It allows anonymous transactions and prohibits central
8965 control over the transactions, making it impossible for governments
8966 and companies alike to block donations and other transactions. The
8967 source is free software, and while the key dependency wxWidgets 2.9
8968 for the graphical user interface is missing in Debian, the command
8969 line client builds just fine. Hopefully Jonas
8970 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8971 Debian&lt;/a&gt; soon.&lt;/p&gt;
8972
8973 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8974 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8975 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8976 currency &quot;stock&quot; markets where the exchange rate is decided. There
8977 are not many users so far, but the concept seems promising. If you
8978 want to get started and lack a friend with any bitcoins to spare,
8979 you can even get
8980 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8981 bitcoin at the time of writing). Use
8982 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8983 on the current exchange rates.&lt;/p&gt;
8984
8985 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8986 machines. If you want to support my activity, please send Bitcoin
8987 donations to the address
8988 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8989 </description>
8990 </item>
8991
8992 <item>
8993 <title>Why isn&#39;t Debian Edu using VLC?</title>
8994 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8996 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8997 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8998 presented, and the winner among the multimedia player were VLC.
8999 Personally, I like VLC, and it is my player of choice when I first try
9000 to play a video file or stream. Only if VLC fail will I drag out
9001 gmplayer to see if it can do better. The reason is mostly the failure
9002 model and trust. When VLC fail, it normally pop up a error message
9003 reporting the problem. When mplayer fail, it normally segfault or
9004 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
9005
9006 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
9007 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9008 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
9009 plugin to play web videos seamlessly, and the VLC browser plugin is
9010 not very good. For example, it lack in-line control buttons, so there
9011 is no way for the user to pause the video. Also, when I
9012 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
9013 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
9014 failed on several video pages where mplayer based plugins worked. If
9015 the browser plugin for VLC was as good as the gecko-mediaplayer
9016 package (which uses mplayer), we would switch.&lt;/P&gt;
9017
9018 &lt;p&gt;While VLC is a good player, its user interface is slightly
9019 annoying. The most annoying feature is its inconsistent use of
9020 keyboard shortcuts. When the player is in full screen mode, its
9021 shortcuts are different from when it is playing the video in a window.
9022 For example, space only work as pause when in full screen mode. I
9023 wish it had consisten shortcuts and that space also would work when in
9024 window mode. Another nice shortcut in gmplayer is [enter] to restart
9025 the current video. It is very nice when playing short videos from the
9026 web and want to restart it when new people arrive to have a look at
9027 what is going on.&lt;/p&gt;
9028 </description>
9029 </item>
9030
9031 <item>
9032 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
9033 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
9034 <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>
9035 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
9036 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
9037 upgrade testing of the
9038 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9039 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
9040 This seem like a very good idea, so I adjusted by test scripts and
9041 can now present the updated result from today:&lt;/p&gt;
9042
9043 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9044
9045 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9046
9047 &lt;blockquote&gt;&lt;p&gt;
9048 apache2.2-bin
9049 aptdaemon
9050 baobab
9051 binfmt-support
9052 browser-plugin-gnash
9053 cheese-common
9054 cli-common
9055 cups-pk-helper
9056 dmz-cursor-theme
9057 empathy
9058 empathy-common
9059 freedesktop-sound-theme
9060 freeglut3
9061 gconf-defaults-service
9062 gdm-themes
9063 gedit-plugins
9064 geoclue
9065 geoclue-hostip
9066 geoclue-localnet
9067 geoclue-manual
9068 geoclue-yahoo
9069 gnash
9070 gnash-common
9071 gnome
9072 gnome-backgrounds
9073 gnome-cards-data
9074 gnome-codec-install
9075 gnome-core
9076 gnome-desktop-environment
9077 gnome-disk-utility
9078 gnome-screenshot
9079 gnome-search-tool
9080 gnome-session-canberra
9081 gnome-system-log
9082 gnome-themes-extras
9083 gnome-themes-more
9084 gnome-user-share
9085 gstreamer0.10-fluendo-mp3
9086 gstreamer0.10-tools
9087 gtk2-engines
9088 gtk2-engines-pixbuf
9089 gtk2-engines-smooth
9090 hamster-applet
9091 libapache2-mod-dnssd
9092 libapr1
9093 libaprutil1
9094 libaprutil1-dbd-sqlite3
9095 libaprutil1-ldap
9096 libart2.0-cil
9097 libboost-date-time1.42.0
9098 libboost-python1.42.0
9099 libboost-thread1.42.0
9100 libchamplain-0.4-0
9101 libchamplain-gtk-0.4-0
9102 libcheese-gtk18
9103 libclutter-gtk-0.10-0
9104 libcryptui0
9105 libdiscid0
9106 libelf1
9107 libepc-1.0-2
9108 libepc-common
9109 libepc-ui-1.0-2
9110 libfreerdp-plugins-standard
9111 libfreerdp0
9112 libgconf2.0-cil
9113 libgdata-common
9114 libgdata7
9115 libgdu-gtk0
9116 libgee2
9117 libgeoclue0
9118 libgexiv2-0
9119 libgif4
9120 libglade2.0-cil
9121 libglib2.0-cil
9122 libgmime2.4-cil
9123 libgnome-vfs2.0-cil
9124 libgnome2.24-cil
9125 libgnomepanel2.24-cil
9126 libgpod-common
9127 libgpod4
9128 libgtk2.0-cil
9129 libgtkglext1
9130 libgtksourceview2.0-common
9131 libmono-addins-gui0.2-cil
9132 libmono-addins0.2-cil
9133 libmono-cairo2.0-cil
9134 libmono-corlib2.0-cil
9135 libmono-i18n-west2.0-cil
9136 libmono-posix2.0-cil
9137 libmono-security2.0-cil
9138 libmono-sharpzip2.84-cil
9139 libmono-system2.0-cil
9140 libmtp8
9141 libmusicbrainz3-6
9142 libndesk-dbus-glib1.0-cil
9143 libndesk-dbus1.0-cil
9144 libopal3.6.8
9145 libpolkit-gtk-1-0
9146 libpt2.6.7
9147 libpython2.6
9148 librpm1
9149 librpmio1
9150 libsdl1.2debian
9151 libsrtp0
9152 libssh-4
9153 libtelepathy-farsight0
9154 libtelepathy-glib0
9155 libtidy-0.99-0
9156 media-player-info
9157 mesa-utils
9158 mono-2.0-gac
9159 mono-gac
9160 mono-runtime
9161 nautilus-sendto
9162 nautilus-sendto-empathy
9163 p7zip-full
9164 pkg-config
9165 python-aptdaemon
9166 python-aptdaemon-gtk
9167 python-axiom
9168 python-beautifulsoup
9169 python-bugbuddy
9170 python-clientform
9171 python-coherence
9172 python-configobj
9173 python-crypto
9174 python-cupshelpers
9175 python-elementtree
9176 python-epsilon
9177 python-evolution
9178 python-feedparser
9179 python-gdata
9180 python-gdbm
9181 python-gst0.10
9182 python-gtkglext1
9183 python-gtksourceview2
9184 python-httplib2
9185 python-louie
9186 python-mako
9187 python-markupsafe
9188 python-mechanize
9189 python-nevow
9190 python-notify
9191 python-opengl
9192 python-openssl
9193 python-pam
9194 python-pkg-resources
9195 python-pyasn1
9196 python-pysqlite2
9197 python-rdflib
9198 python-serial
9199 python-tagpy
9200 python-twisted-bin
9201 python-twisted-conch
9202 python-twisted-core
9203 python-twisted-web
9204 python-utidylib
9205 python-webkit
9206 python-xdg
9207 python-zope.interface
9208 remmina
9209 remmina-plugin-data
9210 remmina-plugin-rdp
9211 remmina-plugin-vnc
9212 rhythmbox-plugin-cdrecorder
9213 rhythmbox-plugins
9214 rpm-common
9215 rpm2cpio
9216 seahorse-plugins
9217 shotwell
9218 software-center
9219 system-config-printer-udev
9220 telepathy-gabble
9221 telepathy-mission-control-5
9222 telepathy-salut
9223 tomboy
9224 totem
9225 totem-coherence
9226 totem-mozilla
9227 totem-plugins
9228 transmission-common
9229 xdg-user-dirs
9230 xdg-user-dirs-gtk
9231 xserver-xephyr
9232 &lt;/p&gt;&lt;/blockquote&gt;
9233
9234 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9235
9236 &lt;blockquote&gt;&lt;p&gt;
9237 cheese
9238 ekiga
9239 eog
9240 epiphany-extensions
9241 evolution-exchange
9242 fast-user-switch-applet
9243 file-roller
9244 gcalctool
9245 gconf-editor
9246 gdm
9247 gedit
9248 gedit-common
9249 gnome-games
9250 gnome-games-data
9251 gnome-nettool
9252 gnome-system-tools
9253 gnome-themes
9254 gnuchess
9255 gucharmap
9256 guile-1.8-libs
9257 libavahi-ui0
9258 libdmx1
9259 libgalago3
9260 libgtk-vnc-1.0-0
9261 libgtksourceview2.0-0
9262 liblircclient0
9263 libsdl1.2debian-alsa
9264 libspeexdsp1
9265 libsvga1
9266 rhythmbox
9267 seahorse
9268 sound-juicer
9269 system-config-printer
9270 totem-common
9271 transmission-gtk
9272 vinagre
9273 vino
9274 &lt;/p&gt;&lt;/blockquote&gt;
9275
9276 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9277
9278 &lt;blockquote&gt;&lt;p&gt;
9279 gstreamer0.10-gnomevfs
9280 &lt;/p&gt;&lt;/blockquote&gt;
9281
9282 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9283
9284 &lt;blockquote&gt;&lt;p&gt;
9285 [nothing]
9286 &lt;/p&gt;&lt;/blockquote&gt;
9287
9288 &lt;p&gt;This is for KDE:&lt;/p&gt;
9289
9290 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9291
9292 &lt;blockquote&gt;&lt;p&gt;
9293 ksmserver
9294 &lt;/p&gt;&lt;/blockquote&gt;
9295
9296 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9297
9298 &lt;blockquote&gt;&lt;p&gt;
9299 kwin
9300 network-manager-kde
9301 &lt;/p&gt;&lt;/blockquote&gt;
9302
9303 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9304
9305 &lt;blockquote&gt;&lt;p&gt;
9306 arts
9307 dolphin
9308 freespacenotifier
9309 google-gadgets-gst
9310 google-gadgets-xul
9311 kappfinder
9312 kcalc
9313 kcharselect
9314 kde-core
9315 kde-plasma-desktop
9316 kde-standard
9317 kde-window-manager
9318 kdeartwork
9319 kdeartwork-emoticons
9320 kdeartwork-style
9321 kdeartwork-theme-icon
9322 kdebase
9323 kdebase-apps
9324 kdebase-workspace
9325 kdebase-workspace-bin
9326 kdebase-workspace-data
9327 kdeeject
9328 kdelibs
9329 kdeplasma-addons
9330 kdeutils
9331 kdewallpapers
9332 kdf
9333 kfloppy
9334 kgpg
9335 khelpcenter4
9336 kinfocenter
9337 konq-plugins-l10n
9338 konqueror-nsplugins
9339 kscreensaver
9340 kscreensaver-xsavers
9341 ktimer
9342 kwrite
9343 libgle3
9344 libkde4-ruby1.8
9345 libkonq5
9346 libkonq5-templates
9347 libnetpbm10
9348 libplasma-ruby
9349 libplasma-ruby1.8
9350 libqt4-ruby1.8
9351 marble-data
9352 marble-plugins
9353 netpbm
9354 nuvola-icon-theme
9355 plasma-dataengines-workspace
9356 plasma-desktop
9357 plasma-desktopthemes-artwork
9358 plasma-runners-addons
9359 plasma-scriptengine-googlegadgets
9360 plasma-scriptengine-python
9361 plasma-scriptengine-qedje
9362 plasma-scriptengine-ruby
9363 plasma-scriptengine-webkit
9364 plasma-scriptengines
9365 plasma-wallpapers-addons
9366 plasma-widget-folderview
9367 plasma-widget-networkmanagement
9368 ruby
9369 sweeper
9370 update-notifier-kde
9371 xscreensaver-data-extra
9372 xscreensaver-gl
9373 xscreensaver-gl-extra
9374 xscreensaver-screensaver-bsod
9375 &lt;/p&gt;&lt;/blockquote&gt;
9376
9377 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9378
9379 &lt;blockquote&gt;&lt;p&gt;
9380 ark
9381 google-gadgets-common
9382 google-gadgets-qt
9383 htdig
9384 kate
9385 kdebase-bin
9386 kdebase-data
9387 kdepasswd
9388 kfind
9389 klipper
9390 konq-plugins
9391 konqueror
9392 ksysguard
9393 ksysguardd
9394 libarchive1
9395 libcln6
9396 libeet1
9397 libeina-svn-06
9398 libggadget-1.0-0b
9399 libggadget-qt-1.0-0b
9400 libgps19
9401 libkdecorations4
9402 libkephal4
9403 libkonq4
9404 libkonqsidebarplugin4a
9405 libkscreensaver5
9406 libksgrd4
9407 libksignalplotter4
9408 libkunitconversion4
9409 libkwineffects1a
9410 libmarblewidget4
9411 libntrack-qt4-1
9412 libntrack0
9413 libplasma-geolocation-interface4
9414 libplasmaclock4a
9415 libplasmagenericshell4
9416 libprocesscore4a
9417 libprocessui4a
9418 libqalculate5
9419 libqedje0a
9420 libqtruby4shared2
9421 libqzion0a
9422 libruby1.8
9423 libscim8c2a
9424 libsmokekdecore4-3
9425 libsmokekdeui4-3
9426 libsmokekfile3
9427 libsmokekhtml3
9428 libsmokekio3
9429 libsmokeknewstuff2-3
9430 libsmokeknewstuff3-3
9431 libsmokekparts3
9432 libsmokektexteditor3
9433 libsmokekutils3
9434 libsmokenepomuk3
9435 libsmokephonon3
9436 libsmokeplasma3
9437 libsmokeqtcore4-3
9438 libsmokeqtdbus4-3
9439 libsmokeqtgui4-3
9440 libsmokeqtnetwork4-3
9441 libsmokeqtopengl4-3
9442 libsmokeqtscript4-3
9443 libsmokeqtsql4-3
9444 libsmokeqtsvg4-3
9445 libsmokeqttest4-3
9446 libsmokeqtuitools4-3
9447 libsmokeqtwebkit4-3
9448 libsmokeqtxml4-3
9449 libsmokesolid3
9450 libsmokesoprano3
9451 libtaskmanager4a
9452 libtidy-0.99-0
9453 libweather-ion4a
9454 libxklavier16
9455 libxxf86misc1
9456 okteta
9457 oxygencursors
9458 plasma-dataengines-addons
9459 plasma-scriptengine-superkaramba
9460 plasma-widget-lancelot
9461 plasma-widgets-addons
9462 plasma-widgets-workspace
9463 polkit-kde-1
9464 ruby1.8
9465 systemsettings
9466 update-notifier-common
9467 &lt;/p&gt;&lt;/blockquote&gt;
9468
9469 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
9470 aptitude a bit more similar, but there are still quite a lott of
9471 differences. I have no idea what packages should be installed after
9472 the upgrade, but hope those that do can have a look.&lt;/p&gt;
9473 </description>
9474 </item>
9475
9476 <item>
9477 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
9478 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
9479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
9480 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
9481 <description>&lt;p&gt;Most of the computers in use by the
9482 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
9483 are virtual machines. And they have been Xen machines running on a
9484 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
9485 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
9486 bit harder that it could have been, because we set up the Xen virtual
9487 machines to get the virtual partitions from LVM, which as far as I
9488 know is not supported by KVM. So to migrate, we had to convert
9489 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
9490
9491 &lt;p&gt;I found
9492 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
9493 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
9494 migration. It uses qemu-img from the qemu package to make the disk
9495 image, parted to partition it, losetup and kpartx to present the disk
9496 image partions as devices, and dd to copy the data. I NFS mounted the
9497 new servers storage area on the old server to do the migration.&lt;/p&gt;
9498
9499 &lt;pre&gt;
9500 #!/bin/sh
9501
9502 # Based on
9503 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9504
9505 set -e
9506 set -x
9507
9508 if [ -z &quot;$1&quot; ] ; then
9509 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
9510 exit 1
9511 else
9512 host=&quot;$1&quot;
9513 fi
9514
9515 if [ ! -e /dev/vg_data/$host-disk ] ; then
9516 echo &quot;error: unable to find LVM volume for $host&quot;
9517 exit 1
9518 fi
9519
9520 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9521 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9522 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9523 totalsize=$(( ( $disksize + $swapsize ) ))
9524
9525 img=$host.img
9526 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
9527 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9528
9529 parted $img mklabel msdos
9530 parted $img mkpart primary linux-swap 0 $disksize
9531 parted $img mkpart primary ext2 $disksize $totalsize
9532 parted $img set 1 boot on
9533
9534 modprobe dm-mod
9535 losetup /dev/loop0 $img
9536 kpartx -a /dev/loop0
9537
9538 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
9539 fsck.ext3 -f /dev/mapper/loop0p1 || true
9540 mkswap /dev/mapper/loop0p2
9541
9542 kpartx -d /dev/loop0
9543 losetup -d /dev/loop0
9544 &lt;/pre&gt;
9545
9546 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
9547 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
9548
9549 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
9550 the new disk image attached, installed grub-pc and linux-image-686 and
9551 set up grub to boot from the disk image. After this, the KVM machines
9552 seem to work just fine.&lt;/p&gt;
9553 </description>
9554 </item>
9555
9556 <item>
9557 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
9558 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
9559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
9560 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
9561 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
9562 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9563 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
9564 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
9565
9566 &lt;p&gt;I still do not know what a correct migration should look like, so I
9567 report any differences between apt and aptitude and hope someone else
9568 can see if anything should be changed.&lt;/p&gt;
9569
9570 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9571
9572 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9573
9574 &lt;blockquote&gt;&lt;p&gt;
9575 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9576 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9577 dmz-cursor-theme empathy empathy-common finger
9578 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9579 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9580 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9581 gnome-cards-data gnome-codec-install gnome-core
9582 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9583 gnome-search-tool gnome-session-canberra gnome-spell
9584 gnome-system-log gnome-themes-extras gnome-themes-more
9585 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9586 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9587 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9588 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9589 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9590 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9591 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9592 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9593 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9594 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9595 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9596 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9597 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9598 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9599 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9600 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9601 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9602 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9603 libmono-security2.0-cil libmono-sharpzip2.84-cil
9604 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9605 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9606 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9607 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9608 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9609 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9610 libxalan2-java libxerces2-java media-player-info mesa-utils
9611 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9612 nautilus-sendto-empathy openoffice.org-writer2latex
9613 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9614 python-aptdaemon python-aptdaemon-gtk python-axiom
9615 python-beautifulsoup python-bugbuddy python-clientform
9616 python-coherence python-configobj python-crypto python-cupshelpers
9617 python-cupsutils python-eggtrayicon python-elementtree
9618 python-epsilon python-evolution python-feedparser python-gdata
9619 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9620 python-gtksourceview2 python-httplib2 python-louie python-mako
9621 python-markupsafe python-mechanize python-nevow python-notify
9622 python-opengl python-openssl python-pam python-pkg-resources
9623 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9624 python-tagpy python-twisted-bin python-twisted-conch
9625 python-twisted-core python-twisted-web python-utidylib python-webkit
9626 python-xdg python-zope.interface remmina remmina-plugin-data
9627 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9628 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9629 software-center svgalibg1 system-config-printer-udev
9630 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9631 totem totem-coherence totem-mozilla totem-plugins
9632 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9633 zip
9634 &lt;/p&gt;&lt;/blockquote&gt;
9635
9636 Installed using apt-get, removed with aptitude
9637
9638 &lt;blockquote&gt;&lt;p&gt;
9639 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9640 epiphany-extensions epiphany-gecko evolution-exchange
9641 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9642 gedit-common gnome-app-install gnome-games gnome-games-data
9643 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9644 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9645 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9646 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9647 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9648 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9649 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9650 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9651 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9652 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9653 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9654 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9655 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9656 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9657 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9658 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9659 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9660 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9661 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9662 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9663 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9664 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9665 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9666 sound-juicer swfdec-gnome system-config-printer totem-common
9667 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9668 &lt;/p&gt;&lt;/blockquote&gt;
9669
9670 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9671
9672 &lt;blockquote&gt;&lt;p&gt;
9673 gstreamer0.10-gnomevfs
9674 &lt;/p&gt;&lt;/blockquote&gt;
9675
9676 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9677
9678 &lt;blockquote&gt;&lt;p&gt;
9679 [nothing]
9680 &lt;/p&gt;&lt;/blockquote&gt;
9681
9682 &lt;p&gt;This is for KDE:&lt;/p&gt;
9683
9684 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9685
9686 &lt;blockquote&gt;&lt;p&gt;
9687 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9688 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9689 ghostscript-x git gnome-audio gnugo granatier gs-common
9690 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9691 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9692 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9693 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9694 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9695 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9696 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9697 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9698 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9699 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9700 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9701 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9702 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9703 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9704 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9705 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9706 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9707 libkrossui4 libmailtools-perl libmime-tools-perl
9708 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9709 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9710 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9711 lirc luatex marble networkstatus noatun-plugins
9712 openoffice.org-writer2latex palapeli palapeli-data parley
9713 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9714 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9715 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9716 ttf-sazanami-gothic
9717 &lt;/p&gt;&lt;/blockquote&gt;
9718
9719 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9720
9721 &lt;blockquote&gt;&lt;p&gt;
9722 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9723 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9724 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9725 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9726 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9727 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9728 kitchensync kiten kjumpingcube klatin klettres klickety klines
9729 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9730 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9731 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9732 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9733 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9734 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9735 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9736 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9737 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9738 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9739 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9740 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9741 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9742 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9743 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9744 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9745 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9746 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9747 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9748 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9749 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9750 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9751 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9752 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9753 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9754 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9755 &lt;/p&gt;&lt;/blockquote&gt;
9756
9757 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9758
9759 &lt;blockquote&gt;&lt;p&gt;
9760 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9761 kdeartwork kdebase kdebase-apps kdebase-workspace
9762 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9763 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9764 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9765 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9766 xscreensaver-screensaver-bsod
9767 &lt;/p&gt;&lt;/blockquote&gt;
9768
9769 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9770
9771 &lt;blockquote&gt;&lt;p&gt;
9772 kdebase-bin konq-plugins konqueror
9773 &lt;/p&gt;&lt;/blockquote&gt;
9774 </description>
9775 </item>
9776
9777 <item>
9778 <title>Gnash buildbot slave and Debian kfreebsd</title>
9779 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9780 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9781 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9782 <description>&lt;p&gt;Answering
9783 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9784 call from the Gnash project&lt;/a&gt; for
9785 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9786 current source, I have set up a virtual KVM machine on the Debian
9787 Edu/Skolelinux virtualization host to test the git source on
9788 Debian/Squeeze. I hope this can help the developers in getting new
9789 releases out more often.&lt;/p&gt;
9790
9791 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9792 I have considered setting up a &lt;a
9793 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9794 machine as well. I have also considered using the kfreebsd
9795 architecture in Debian as a file server in NUUG to get access to the 5
9796 TB zfs volume we currently use to store DV video. Because of this, I
9797 finally got around to do a test installation of Debian/Squeeze with
9798 kfreebsd. Installation went fairly smooth, thought I noticed some
9799 visual glitches in the cdebconf dialogs (black cursor left on the
9800 screen at random locations). Have not gotten very far with the
9801 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9802 fatal problem. Have to spend some more time on it to see if it is
9803 useful as a file server for NUUG. Will try to find time to set up a
9804 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9805 </description>
9806 </item>
9807
9808 <item>
9809 <title>Debian in 3D</title>
9810 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9812 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9813 <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;
9814
9815 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9816 3D linked in from
9817 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9818 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9819 </description>
9820 </item>
9821
9822 <item>
9823 <title>Software updates 2010-10-24</title>
9824 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9826 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9827 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9828
9829 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9830 raise money for the project is going well. The lower limit of 10
9831 signers was reached in 24 hours, and so far 13 people have signed it.
9832 More signers and more funding is most welcome, and I am really curious
9833 how far we can get before the time limit of December 24 is reached.
9834 :)&lt;/p&gt;
9835
9836 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9837 about what appear to be a great code coverage tool capable of
9838 generating code coverage stats without any changes to the source code.
9839 It is called
9840 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9841 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9842 It is missing in Debian, but the git source built just fine in Squeeze
9843 after I installed libelf-dev, libdwarf-dev, pkg-config and
9844 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9845 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9846
9847 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9848 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9849 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9850 alpha test release of the Squeeze based Debian Edu /
9851 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9852 release. Give it a try if you need a complete linux solution for your
9853 school, including central infrastructure server, workstations, thin
9854 client servers and diskless workstations. A nice touch added
9855 yesterday is RDP support on the thin client servers, for windows
9856 clients to get a Linux desktop on request.&lt;/p&gt;
9857 </description>
9858 </item>
9859
9860 <item>
9861 <title>Some notes on Flash in Debian and Debian Edu</title>
9862 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9863 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9864 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9865 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9866 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9867 second most popular used package that is missing in Debian. The sixth
9868 most popular is flashplayer-mozilla. This is a clear indication that
9869 working flash is important for Debian users. Around 10 percent of the
9870 users submitting data to popcon.debian.org have this package
9871 installed.&lt;/p&gt;
9872
9873 &lt;p&gt;In the report written by Lars Risan in August 2008
9874&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
9875 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9876 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9877 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9878 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9879 web sites require Flash to work, and lacking working Flash support in
9880 the web browser and the problems with installing it was perceived as a
9881 good reason to stay with Windows.&lt;/p&gt;
9882
9883 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9884 said to be the retarded cousin that did not really understand
9885 everything you told him but could work fairly well. This was a
9886 comment regarding the problems Linux have with proprietary formats and
9887 non-standard web pages, and is sad because it exposes a fairly common
9888 understanding of whose fault it is if web pages that only work in for
9889 example Internet Explorer 6 fail to work on Firefox, and funny because
9890 it explain very well how annoying it is for users when Linux
9891 distributions do not work with the documents they receive or the web
9892 pages they want to visit.&lt;/p&gt;
9893
9894 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9895 and Debian Edu to have a well working Flash implementation in the
9896 distribution, to get at least popular sites as Youtube and Google
9897 Video to working out of the box. For Squeeze, Debian have the chance
9898 to include the latest version of Gnash that will make this happen, as
9899 the new release 0.8.8 was published a few weeks ago and is resting in
9900 unstable. The new version work with more sites that version 0.8.7.
9901 The Gnash maintainers have asked for a freeze exception, but the
9902 release team have not had time to reply to it yet. I hope they agree
9903 with me that Flash is important for the Debian desktop users, and thus
9904 accept the new package into Squeeze.&lt;/p&gt;
9905 </description>
9906 </item>
9907
9908 <item>
9909 <title>Circular package dependencies harms apt recovery</title>
9910 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9911 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9912 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9913 <description>&lt;p&gt;I discovered this while doing
9914 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9915 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9916 in Debian still got circular dependencies, and it is often claimed
9917 that apt and aptitude should be able to handle this just fine, but
9918 some times these dependency loops causes apt to fail.&lt;/p&gt;
9919
9920 &lt;p&gt;An example is from todays
9921 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9922 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9923 causes perl-modules to fail to upgrade. The cause is simple. If a
9924 package fail to unpack, then only part of packages with the circular
9925 dependency might end up being unpacked when unpacking aborts, and the
9926 ones already unpacked will fail to configure in the recovery phase
9927 because its dependencies are unavailable.&lt;/p&gt;
9928
9929 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9930
9931 &lt;blockquote&gt;&lt;pre&gt;
9932 dpkg: dependency problems prevent configuration of perl-modules:
9933 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9934 Version of perl on system is 5.10.0-19lenny2.
9935 dpkg: error processing perl-modules (--configure):
9936 dependency problems - leaving unconfigured
9937 &lt;/pre&gt;&lt;/blockquote&gt;
9938
9939 &lt;p&gt;The perl/perl-modules circular dependency is already
9940 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9941 hopefully be solved as soon as possible, but it is not the only one,
9942 and each one of these loops in the dependency tree can cause similar
9943 failures. Of course, they only occur when there are bugs in other
9944 packages causing the unpacking to fail, but it is rather nasty when
9945 the failure of one package causes the problem to become worse because
9946 of dependency loops.&lt;/p&gt;
9947
9948 &lt;p&gt;Thanks to
9949 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9950 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9951 dependencies
9952 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9953 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9954
9955 &lt;p&gt;Todays testing also exposed a bug in
9956 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9957 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9958 apt-get and aptitude, the latter possibly caused by some circular
9959 dependency. Reported both to BTS to try to get someone to look at
9960 it.&lt;/p&gt;
9961 </description>
9962 </item>
9963
9964 <item>
9965 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9966 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9967 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9968 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9969 <description>&lt;p&gt;This is a
9970 &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;
9971 on my
9972 &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
9973 work&lt;/a&gt; on
9974 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9975 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9976
9977 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9978 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9979 and dhcp3-server-ldap in Debian use the LDAP server. The two
9980 implementations are quite different in how they use LDAP.&lt;/p&gt;
9981
9982 To get this information, I started slapd with debugging enabled and
9983 dumped the debug output to a file to get the LDAP searches performed
9984 on a Debian Edu main-server. Here is a summary.
9985
9986 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9987
9988 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9989 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9990 the web.
9991
9992 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9993 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9994 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9995 reverse entries are in two different subtrees in LDAP with a structure
9996 based on the DNS names, as in tjener.intern and
9997 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9998
9999 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
10000 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
10001 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
10002 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
10003 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
10004 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
10005 forward entries, it is looking for attributes named dnsttl, arecord,
10006 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10007 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10008 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10009 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10010 spfrecord and modifytimestamp. For reverse entries it is looking for
10011 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10012 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10013 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10014 ldapsearch commands could look like this:&lt;/p&gt;
10015
10016 &lt;blockquote&gt;&lt;pre&gt;
10017 ldapsearch -h ldap \
10018 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10019 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10020 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10021 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10022 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10023 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10024
10025 ldapsearch -h ldap \
10026 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10027 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
10028 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10029 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10030 srvrecord naptrrecord modifytimestamp
10031 &lt;/pre&gt;&lt;/blockquote&gt;
10032
10033 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
10034 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10035 example LDAP objects used there. In addition to these objects, the
10036 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10037 also exist.&lt;/p&gt;
10038
10039 &lt;blockquote&gt;&lt;pre&gt;
10040 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10041 objectclass: top
10042 objectclass: dnsdomain
10043 objectclass: domainrelatedobject
10044 dc: tjener
10045 arecord: 10.0.2.2
10046 associateddomain: tjener.intern
10047
10048 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10049 objectclass: top
10050 objectclass: dnsdomain2
10051 objectclass: domainrelatedobject
10052 dc: 2
10053 ptrrecord: tjener.intern
10054 associateddomain: 2.2.0.10.in-addr.arpa
10055 &lt;/pre&gt;&lt;/blockquote&gt;
10056
10057 &lt;p&gt;In strict mode, the server behaves differently. When looking for
10058 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
10059 same base as in the tree mode for a object with filter
10060 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
10061 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10062 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10063 naptrrecord and modifytimestamp. For reverse entires it also do a
10064 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
10065 and the requested attributes are associateddomain, dnsttl and
10066 modifytimestamp. In short, in strict mode the objects with ptrrecord
10067 go away, and the arecord attribute in the forward object is used
10068 instead.&lt;/p&gt;
10069
10070 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
10071 like this:&lt;/p&gt;
10072
10073 &lt;blockquote&gt;&lt;pre&gt;
10074 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10075 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10076 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10077 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10078 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10079 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10080
10081 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10082 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
10083 &lt;/pre&gt;&lt;/blockquote&gt;
10084
10085 &lt;p&gt;In addition to the forward and reverse searches , there is also a
10086 search for SOA records, which behave similar to the forward and
10087 reverse lookups.&lt;/p&gt;
10088
10089 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
10090 specify any objectclass names, and instead look for the attributes it
10091 need to generate a DNS reply. This make it able to work with any
10092 objectclass that provide the needed attributes.&lt;/p&gt;
10093
10094 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
10095 dnsdomain2 schemas. The latter is used for reverse entries like
10096 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
10097
10098 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
10099 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
10100 attributes) and domainrelatedobject (for associatedDomain). The use
10101 of structural object classes make it impossible to combine these
10102 classes with the object classes used by DHCP.&lt;/p&gt;
10103
10104 &lt;p&gt;There are other schemas that could be used too, for example the
10105 dnszone structural object class used by Gosa and bind-sdb for the DNS
10106 attributes combined with the domainrelatedobject object class, but in
10107 this case some unused attributes would have to be included as well
10108 (zonename and relativedomainname).&lt;/p&gt;
10109
10110 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
10111 mode and not use any of the existing objectclasses (dnsdomain,
10112 dnsdomain2 and dnszone) when one want to combine the DNS information
10113 with DHCP information, and instead create a auxiliary object class
10114 defined something like this (using the attributes defined for
10115 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
10116
10117 &lt;blockquote&gt;&lt;pre&gt;
10118 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
10119 SUP top
10120 AUXILIARY
10121 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
10122 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
10123 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
10124 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
10125 A6Record $ DNAMERecord
10126 ))
10127 &lt;/pre&gt;&lt;/blockquote&gt;
10128
10129 &lt;p&gt;This will allow any object to become a DNS entry when combined with
10130 the domainrelatedobject object class, and allow any entity to include
10131 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
10132 developers asking for their view on this schema and if they are
10133 interested in providing such schema with PowerDNS, and I hope my
10134 message will be accepted into their mailing list soon.&lt;/p&gt;
10135
10136 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
10137
10138 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
10139 the object attributes, and then uses the attributes it want. This
10140 make it harder to figure out exactly what attributes are used, but
10141 thanks to the working example in Debian Edu I can at least get an idea
10142 what is needed without having to read the source code.&lt;/p&gt;
10143
10144 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
10145 search filter to use to locate the correct dhcpServer entity is
10146 stored. These are the relevant entries from
10147 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
10148
10149 &lt;blockquote&gt;&lt;pre&gt;
10150 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
10151 ldap-dhcp-server-cn &quot;dhcp&quot;;
10152 &lt;/pre&gt;&lt;/blockquote&gt;
10153
10154 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
10155 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
10156 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
10157 search result is this entry:&lt;/p&gt;
10158
10159 &lt;blockquote&gt;&lt;pre&gt;
10160 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10161 cn: dhcp
10162 objectClass: top
10163 objectClass: dhcpServer
10164 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10165 &lt;/pre&gt;&lt;/blockquote&gt;
10166
10167 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
10168 subtree with DHCP configuration. The DHCP configuration subtree base
10169 is located using a base scope search with base &quot;cn=DHCP
10170 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
10171 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
10172 The search result is this entry:&lt;/p&gt;
10173
10174 &lt;blockquote&gt;&lt;pre&gt;
10175 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10176 cn: DHCP Config
10177 objectClass: top
10178 objectClass: dhcpService
10179 objectClass: dhcpOptions
10180 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
10181 dhcpStatements: ddns-update-style none
10182 dhcpStatements: authoritative
10183 dhcpOption: smtp-server code 69 = array of ip-address
10184 dhcpOption: www-server code 72 = array of ip-address
10185 dhcpOption: wpad-url code 252 = text
10186 &lt;/pre&gt;&lt;/blockquote&gt;
10187
10188 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
10189 all the DHCP configuration is loaded, it is ready to receive requests.
10190 The subtree in Debian Edu contain objects with object classes
10191 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
10192 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
10193 and information about netmasks, dynamic range etc. Leaving out the
10194 details here because it is not relevant for the focus of my
10195 investigation, which is to see if it is possible to merge dns and dhcp
10196 related computer objects.&lt;/p&gt;
10197
10198 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
10199 of the client (00:00:00:00:00:00 in this example), using a subtree
10200 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
10201 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
10202 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
10203 like:&lt;/p&gt;
10204
10205 &lt;blockquote&gt;&lt;pre&gt;
10206 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10207 cn: hostname
10208 objectClass: top
10209 objectClass: dhcpHost
10210 dhcpHWAddress: ethernet 00:00:00:00:00:00
10211 dhcpStatements: fixed-address hostname
10212 &lt;/pre&gt;&lt;/blockquote&gt;
10213
10214 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
10215 The object classes need to have fixed names, and the configuration
10216 need to be stored in a fairly specific LDAP structure. On the
10217 positive side, the invidiual dhcpHost entires can be anywhere without
10218 the DN pointed to by the dhcpServer entries. The latter should make
10219 it possible to group all host entries in a subtree next to the
10220 configuration entries, and this subtree can also be shared with the
10221 DNS server if the schema proposed above is combined with the dhcpHost
10222 structural object class.
10223
10224 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
10225
10226 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
10227 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
10228 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
10229 allowing DNS objects to be stored anywhere under the base cn specified
10230 in the configuration.&lt;/p&gt;
10231
10232 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
10233 regarding which LDAP schemas to use and which LDAP structure to use.
10234 I guess one could implement ones own schema, as long as the
10235 objectclasses and attributes have the names used, but this do not
10236 really help when the DHCP subtree need to have a fairly fixed
10237 structure.&lt;/p&gt;
10238
10239 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
10240 this might work for Debian Edu:&lt;/p&gt;
10241
10242 &lt;blockquote&gt;&lt;pre&gt;
10243 ou=services
10244 cn=machine-info (dhcpService) - dhcpServiceDN points here
10245 cn=dhcp (dhcpServer)
10246 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10247 cn=10.0.2.0 (dhcpSubnet)
10248 cn=group1 (dhcpGroup/dhcpOptions)
10249 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10250 cn=192.168.0.0 (dhcpSubnet)
10251 cn=group1 (dhcpGroup/dhcpOptions)
10252 ou=machines - PowerDNS base points here
10253 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10254 &lt;/pre&gt;&lt;/blockquote&gt;
10255
10256 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
10257 entries to be in the dhcpGroup subtrees, the entries can be stored
10258 there instead of a common machines subtree, and the PowerDNS base
10259 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
10260
10261 &lt;p&gt;The combined object under the machines subtree would look something
10262 like this:&lt;/p&gt;
10263
10264 &lt;blockquote&gt;&lt;pre&gt;
10265 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10266 dc: hostname
10267 objectClass: top
10268 objectClass: dhcpHost
10269 objectclass: domainrelatedobject
10270 objectclass: dnsDomainAux
10271 associateddomain: hostname.intern
10272 arecord: 10.11.12.13
10273 dhcpHWAddress: ethernet 00:00:00:00:00:00
10274 dhcpStatements: fixed-address hostname.intern
10275 &lt;/pre&gt;&lt;/blockquote&gt;
10276
10277 &lt;/p&gt;One could even add the LTSP configuration associated with a given
10278 machine, as long as the required attributes are available in a
10279 auxiliary object class.&lt;/p&gt;
10280 </description>
10281 </item>
10282
10283 <item>
10284 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
10285 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
10286 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
10287 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
10288 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
10289 DHCP services in Debian Edu to use the same LDAP objects for a given
10290 computer, to avoid the possibility of having a inconsistent state for
10291 a computer in LDAP (as in DHCP but no DNS entry or the other way
10292 around) and make it easier to add computers to LDAP.&lt;/p&gt;
10293
10294 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
10295 information finally found a solution that seem to work.&lt;/p&gt;
10296
10297 &lt;p&gt;The old setup required three LDAP objects for a given computer.
10298 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10299 we switch powerdns to use its strict LDAP method (ldap-method=strict
10300 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10301 merged into one while making it impossible to transfer the reverse map
10302 to a slave DNS server.&lt;/p&gt;
10303
10304 &lt;p&gt;If we also replace the object class used to get the DNS related
10305 attributes to one allowing these attributes to be combined with the
10306 dhcphost object class, we can merge the DNS and DHCP entries into one.
10307 I&#39;ve written such object class in the dnsdomainaux.schema file (need
10308 proper OIDs, but that is a minor issue), and tested the setup. It
10309 seem to work.&lt;/p&gt;
10310
10311 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
10312 for both DNS and DHCP, and even the LTSP configuration I suggested in
10313 an earlier email. The combined LDAP object will look something like
10314 this:&lt;/p&gt;
10315
10316 &lt;blockquote&gt;&lt;pre&gt;
10317 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10318 cn: hostname
10319 objectClass: dhcphost
10320 objectclass: domainrelatedobject
10321 objectclass: dnsdomainaux
10322 associateddomain: hostname.intern
10323 arecord: 10.11.12.13
10324 dhcphwaddress: ethernet 00:00:00:00:00:00
10325 dhcpstatements: fixed-address hostname
10326 ldapconfigsound: Y
10327 &lt;/pre&gt;&lt;/blockquote&gt;
10328
10329 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
10330 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10331 before asking DNS to resolve the fixed-adddress. LTSP will use
10332 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
10333
10334 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
10335 dhcphost in a different location, to allow us to put the objects
10336 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
10337 that. If I can&#39;t figure out a way to do that, we can still get rid of
10338 the hosts subtree and move all its content into the DHCP Config tree
10339 (which probably should be renamed to be more related to the new
10340 content. I suspect cn=dnsdhcp,ou=services or something like that
10341 might be a good place to put it.&lt;/p&gt;
10342
10343 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10344 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10345 </description>
10346 </item>
10347
10348 <item>
10349 <title>Idea for storing LTSP configuration in LDAP</title>
10350 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
10351 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
10352 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
10353 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
10354 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10355 clients, and that this can be used to fetch configuration from LDAP if
10356 Debian Edu choose to store configuration there.&lt;/p&gt;
10357
10358 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
10359 to get configuration from LDAP. The idea is to look up the MAC
10360 address of the client in LDAP, and look for attributes on the form
10361 ltspconfigsetting=value, and use this to export SETTING=value to the
10362 LTSP clients.&lt;/p&gt;
10363
10364 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
10365 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
10366 allowing us to store all information about a computer in one place.&lt;/p&gt;
10367
10368 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
10369 this approach. A real LDAP schema for the ltspClientAux objectclass
10370 need to be written. Comments, suggestions, etc?&lt;/p&gt;
10371
10372 &lt;blockquote&gt;&lt;pre&gt;
10373 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10374 #
10375 # Fetch LTSP client settings from LDAP based on MAC address
10376 #
10377 # Uses ethernet address as stored in the dhcpHost objectclass using
10378 # the dhcpHWAddress attribute or ethernet address stored in the
10379 # ieee802Device objectclass with the macAddress attribute.
10380 #
10381 # This module is written to be schema agnostic, and only depend on the
10382 # existence of attribute names.
10383 #
10384 # The LTSP configuration variables are saved directly using a
10385 # ltspConfig prefix and uppercasing the rest of the attribute name.
10386 # To set the SERVER variable, set the ltspConfigServer attribute.
10387 #
10388 # Some LDAP schema should be created with all the relevant
10389 # configuration settings. Something like this should work:
10390 #
10391 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
10392 # SUP top
10393 # AUXILIARY
10394 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10395
10396 LDAPSERVER=$(debian-edu-ldapserver)
10397 if [ &quot;$LDAPSERVER&quot; ] ; then
10398 LDAPBASE=$(debian-edu-ldapserver -b)
10399 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
10400 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
10401 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
10402 grep &#39;^ltspConfig&#39; | while read attr value ; do
10403 # Remove prefix and convert to upper case
10404 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
10405 # bass value on to clients
10406 eval &quot;$attr=$value; export $attr&quot;
10407 done
10408 done
10409 fi
10410 &lt;/pre&gt;&lt;/blockquote&gt;
10411
10412 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
10413 the while block might end up in a subshell causing the variables set
10414 there to not show up in ltsp-config, but if that is the case I am sure
10415 the code can be restructured to make sure the variables are passed on.
10416 I expect that can be solved with some testing. :)&lt;/p&gt;
10417
10418 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10419 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10420
10421 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
10422 configuration in LDAP that was created around year 2000 by
10423 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
10424 Xperience, Inc., 2000&lt;/a&gt;. I found its
10425 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
10426 personal home page over at redhat.com.&lt;/p&gt;
10427 </description>
10428 </item>
10429
10430 <item>
10431 <title>jXplorer, a very nice LDAP GUI</title>
10432 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
10433 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
10434 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
10435 <description>&lt;p&gt;Since
10436 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
10437 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
10438 LDAP GUI that is even better than luma. The java application
10439 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
10440 moving LDAP objects and subtrees using drag-and-drop, and can
10441 authenticate using Kerberos. I have only tested the Kerberos
10442 authentication, but do not have a LDAP setup allowing me to rewrite
10443 LDAP with my test user yet. It is
10444 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
10445 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
10446 have with it is how it handle errors. If something go wrong, its
10447 non-intuitive behaviour require me to go through some query work list
10448 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
10449 </description>
10450 </item>
10451
10452 <item>
10453 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
10454 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
10455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
10456 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
10457 <description>&lt;p&gt;Here is a short update on my &lt;a
10458 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
10459 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
10460 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
10461 not reporting the status for KDE, because the upgrade crashes when
10462 aptitude try because of missing conflicts
10463 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
10464 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
10465
10466 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
10467 complete list of the installed packages. Based on this I see these
10468 differences when I did a test run today. As usual, I do not really
10469 know what the correct set of packages would be, but thought it best to
10470 publish the difference.&lt;/p&gt;
10471
10472 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10473
10474 &lt;blockquote&gt;&lt;p&gt;
10475 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
10476 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
10477 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10478 libgtksourceview-common libpt-1.10.10-plugins-alsa
10479 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10480 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10481 python-4suite-xml python-eggtrayicon python-gtkhtml2
10482 python-gtkmozembed svgalibg1 xserver-xephyr zip
10483 &lt;/p&gt;&lt;/blockquote&gt;
10484
10485 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10486
10487 &lt;blockquote&gt;&lt;p&gt;
10488 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10489 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10490 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
10491 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
10492 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
10493 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
10494 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10495 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10496 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10497 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
10498 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
10499 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
10500 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10501 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
10502 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10503 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
10504 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
10505 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10506 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10507 mysql-common swfdec-gnome totem-gstreamer wodim
10508 &lt;/p&gt;&lt;/blockquote&gt;
10509
10510 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10511
10512 &lt;blockquote&gt;&lt;p&gt;
10513 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10514 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10515 xserver-xorg-input-all xserver-xorg-input-evdev
10516 xserver-xorg-input-kbd xserver-xorg-input-mouse
10517 xserver-xorg-input-synaptics xserver-xorg-video-all
10518 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10519 xserver-xorg-video-chips xserver-xorg-video-cirrus
10520 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10521 xserver-xorg-video-glint xserver-xorg-video-i128
10522 xserver-xorg-video-i740 xserver-xorg-video-mach64
10523 xserver-xorg-video-mga xserver-xorg-video-neomagic
10524 xserver-xorg-video-nouveau xserver-xorg-video-nv
10525 xserver-xorg-video-r128 xserver-xorg-video-radeon
10526 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10527 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10528 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10529 xserver-xorg-video-sis xserver-xorg-video-sisusb
10530 xserver-xorg-video-tdfx xserver-xorg-video-tga
10531 xserver-xorg-video-trident xserver-xorg-video-tseng
10532 xserver-xorg-video-vesa xserver-xorg-video-vmware
10533 xserver-xorg-video-voodoo
10534 &lt;/p&gt;&lt;/blockquote&gt;
10535
10536 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10537
10538 &lt;blockquote&gt;&lt;p&gt;
10539 deskbar-applet xserver-xorg xserver-xorg-core
10540 xserver-xorg-input-wacom xserver-xorg-video-intel
10541 xserver-xorg-video-openchrome
10542 &lt;/p&gt;&lt;/blockquote&gt;
10543
10544 &lt;p&gt;I was told on IRC that the xorg-xserver package was
10545 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
10546 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
10547 No idea when it hits Squeeze, but when it does I hope it will reduce
10548 the difference somewhat.
10549 </description>
10550 </item>
10551
10552 <item>
10553 <title>LUMA, a very nice LDAP GUI</title>
10554 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
10555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
10556 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
10557 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
10558 directory in Debian Edu, and in the process I started to miss a GUI
10559 tool to browse the LDAP tree. The only one I was able to find in
10560 Debian/Squeeze and Lenny is
10561 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
10562 be a great tool to get a overview of the current LDAP directory
10563 populated by default in Skolelinux. Thanks to it, I have been able to
10564 find empty and obsolete subtrees, misplaced objects and duplicate
10565 objects. It will be installed by default in Debian/Squeeze. If you
10566 are working with LDAP, give it a go. :)&lt;/p&gt;
10567
10568 &lt;p&gt;I did notice one problem with it I have not had time to report to
10569 the BTS yet. There is no .desktop file in the package, so the tool do
10570 not show up in the Gnome and KDE menus, but only deep down in in the
10571 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10572 released.&lt;/p&gt;
10573
10574 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10575 like to move objects and remove subtrees directly in the GUI, but have
10576 not found a way to do that with LUMA yet. So in the mean time, I use
10577 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10578
10579 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10580 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10581
10582 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10583 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10584 useful GUI alternative. It seem like a good tool, but is unmaintained
10585 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10586 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10587 </description>
10588 </item>
10589
10590 <item>
10591 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10592 <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>
10593 <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>
10594 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10595 <description>&lt;p&gt;A while back, I
10596 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10597 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10598 for storing DNS and DHCP information in LDAP to combine the two sets
10599 of information into one LDAP object representing a computer.&lt;/p&gt;
10600
10601 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10602 the dhcpHost object class auxiliary, to allow it to be combined with
10603 the dNSDomain object class, and thus forming one object for one
10604 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10605
10606 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10607 without also changing the assigned number for the object class, and I
10608 do not know enough about LDAP schema design to do that properly for
10609 Debian Edu.&lt;/p&gt;
10610
10611 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10612 the
10613 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10614 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10615 available today from IETF.&lt;/p&gt;
10616
10617 &lt;pre&gt;
10618 --- dhcp.schema (revision 65192)
10619 +++ dhcp.schema (working copy)
10620 @@ -376,7 +376,7 @@
10621 objectclass ( 2.16.840.1.113719.1.203.6.6
10622 NAME &#39;dhcpHost&#39;
10623 DESC &#39;This represents information about a particular client&#39;
10624 - SUP top
10625 + SUP top AUXILIARY
10626 MUST cn
10627 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10628 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10629 &lt;/pre&gt;
10630
10631 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10632 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10633 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10634
10635 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10636 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10637 </description>
10638 </item>
10639
10640 <item>
10641 <title>Calling tasksel like the installer, while still getting useful output</title>
10642 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10643 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10644 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10645 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10646 installs packages during the normal debian-installer run. Until now,
10647 I have ended up letting tasksel do the work, with the annoying problem
10648 of not getting any feedback at all when something fails (like a
10649 conffile question from dpkg or a download that fails), using code like
10650 this:
10651
10652 &lt;blockquote&gt;&lt;pre&gt;
10653 export DEBIAN_FRONTEND=noninteractive
10654 tasksel --new-install
10655 &lt;/pre&gt;&lt;/blockquote&gt;
10656
10657 This would invoke tasksel, let its automatic task selection pick the
10658 tasks to install, and continue to install the requested tasks without
10659 any output what so ever.
10660
10661 Recently I revisited this problem while working on the automatic
10662 package upgrade testing, because tasksel would some times hang without
10663 any useful feedback, and I want to see what is going on when it
10664 happen. Then it occured to me, I can parse the output from tasksel
10665 when asked to run in test mode, and use that aptitude command line
10666 printed by tasksel then to simulate the tasksel run. I ended up using
10667 code like this:
10668
10669 &lt;blockquote&gt;&lt;pre&gt;
10670 export DEBIAN_FRONTEND=noninteractive
10671 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10672 $cmd
10673 &lt;/pre&gt;&lt;/blockquote&gt;
10674
10675 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10676 --without-recommends -o APT::Install-Recommends=no -y install
10677 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10678 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10679 laptop task and all packages with priority standard , required and
10680 important, just like tasksel would have done it during
10681 installation.&lt;/p&gt;
10682
10683 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10684 install packages without using debconf-apt-progress, for use cases
10685 like this.&lt;/p&gt;
10686 </description>
10687 </item>
10688
10689 <item>
10690 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10691 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10693 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10694 <description>&lt;p&gt;My
10695 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10696 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10697 finally made the upgrade logs available from
10698 &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;.
10699 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10700 apt and aptitude, and found their differences interesting. This time
10701 I will only focus on their removal plans.&lt;/p&gt;
10702
10703 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10704 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10705 surprising part is that it want to remove xorg and all
10706 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10707 sure why. When asking aptitude to do the same, it want to remove 129
10708 packages, but most of them are library packages I suspect are no
10709 longer needed. Both of them want to remove bluetooth packages, which
10710 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10711
10712 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10713 which seem like a bad idea and xorg the same way as with Gnome. Asking
10714 aptitude for the same, it wants to remove 192 packages, none which are
10715 too surprising.&lt;/p&gt;
10716
10717 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10718 and avoided, and perhaps others as well. Here are the complete list
10719 of planned removals. The complete logs is available from the URL
10720 above. Note if you want to repeat these tests, that the upgrade test
10721 for kde+apt-get hung in the tasksel setup because of dpkg asking
10722 conffile questions. No idea why. I worked around it by using
10723 &#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
10724 continue.&lt;/p&gt;
10725
10726 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10727 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10728 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10729 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10730 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10731 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10732 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10733 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10734 xserver-xorg-input-kbd xserver-xorg-input-mouse
10735 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10736 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10737 xserver-xorg-video-ati xserver-xorg-video-chips
10738 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10739 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10740 xserver-xorg-video-glint xserver-xorg-video-i128
10741 xserver-xorg-video-i740 xserver-xorg-video-imstt
10742 xserver-xorg-video-intel xserver-xorg-video-mach64
10743 xserver-xorg-video-mga xserver-xorg-video-neomagic
10744 xserver-xorg-video-nsc xserver-xorg-video-nv
10745 xserver-xorg-video-openchrome xserver-xorg-video-r128
10746 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10747 xserver-xorg-video-rendition xserver-xorg-video-s3
10748 xserver-xorg-video-s3virge xserver-xorg-video-savage
10749 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10750 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10751 xserver-xorg-video-tga xserver-xorg-video-trident
10752 xserver-xorg-video-tseng xserver-xorg-video-v4l
10753 xserver-xorg-video-vesa xserver-xorg-video-vga
10754 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10755 xulrunner-1.9-gnome-support&lt;/p&gt;
10756
10757 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10758
10759 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10760 djvulibre-desktop finger gnome-app-install gnome-mount
10761 gnome-network-admin gnome-spell gnome-vfs-obexftp
10762 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10763 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10764 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10765 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10766 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10767 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10768 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10769 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10770 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10771 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10772 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10773 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10774 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10775 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10776 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10777 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10778 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10779 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10780 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10781 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10782 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10783 openoffice.org-writer2latex openssl-blacklist p7zip
10784 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10785 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10786 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10787 swfdec-mozilla totem-gstreamer update-manager wodim
10788 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10789 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10790 zip&lt;/p&gt;
10791
10792 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10793
10794 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10795 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10796 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10797 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10798 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10799 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10800 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10801 xserver-xorg-input-kbd xserver-xorg-input-mouse
10802 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10803 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10804 xserver-xorg-video-ati xserver-xorg-video-chips
10805 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10806 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10807 xserver-xorg-video-glint xserver-xorg-video-i128
10808 xserver-xorg-video-i740 xserver-xorg-video-imstt
10809 xserver-xorg-video-intel xserver-xorg-video-mach64
10810 xserver-xorg-video-mga xserver-xorg-video-neomagic
10811 xserver-xorg-video-nsc xserver-xorg-video-nv
10812 xserver-xorg-video-openchrome xserver-xorg-video-r128
10813 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10814 xserver-xorg-video-rendition xserver-xorg-video-s3
10815 xserver-xorg-video-s3virge xserver-xorg-video-savage
10816 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10817 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10818 xserver-xorg-video-tga xserver-xorg-video-trident
10819 xserver-xorg-video-tseng xserver-xorg-video-v4l
10820 xserver-xorg-video-vesa xserver-xorg-video-vga
10821 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10822
10823 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10824 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10825 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10826 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10827 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10828 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10829 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10830 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10831 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10832 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10833 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10834 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10835 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10836 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10837 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10838 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10839 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10840 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10841 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10842 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10843 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10844 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10845 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10846 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10847 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10848 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10849 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10850 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10851 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10852 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10853 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10854 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10855 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10856 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10857 texlive-common texlive-doc-base texlive-fonts-recommended
10858 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10859 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10860 xulrunner-1.9&lt;/p&gt;
10861
10862 </description>
10863 </item>
10864
10865 <item>
10866 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10867 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10869 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10870 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10871 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10872 have been discovered and reported in the process
10873 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10874 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10875 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10876 kdebase-workspace-data), and to get a more regular testing going on, I
10877 am working on a script to automate the test.&lt;/p&gt;
10878
10879 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10880 Gnome or KDE desktop installation inside the chroot before upgrading
10881 it. To ensure no services are started in the chroot, a policy-rc.d
10882 script is inserted. To make sure tasksel believe it is to install a
10883 desktop on a laptop, the tasksel tests are replaced in the chroot
10884 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10885
10886 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10887 currently always fail because udev refuses to upgrade with the kernel
10888 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10889 is created. The bug report
10890 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10891 this problem do not trigger in a chroot, but I touch the file anyway
10892 to make sure the upgrade go well. Testing on virtual and real
10893 hardware have failed me because of udev so far, and creating this file
10894 do the trick in such settings anyway. This is a
10895 &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
10896 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10897 maintainer because he lack the resources to rewrite udev to keep
10898 working with old kernels or something like that. I really wish the
10899 udev upstream would keep udev backwards compatible, to avoid such
10900 upgrade problem, but given that they fail to do so, I guess
10901 documenting the way out of this mess is the best option we got for
10902 Debian Squeeze.&lt;/p&gt;
10903
10904 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10905 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10906 trick:&lt;/p&gt;
10907
10908 &lt;blockquote&gt;&lt;pre&gt;
10909 #!/bin/sh
10910 set -ex
10911
10912 if [ &quot;$1&quot; ] ; then
10913 desktop=$1
10914 else
10915 desktop=gnome
10916 fi
10917
10918 from=lenny
10919 to=squeeze
10920
10921 exec &amp;lt; /dev/null
10922 unset LANG
10923 mirror=http://ftp.skolelinux.org/debian
10924 tmpdir=chroot-$from-upgrade-$to-$desktop
10925 fuser -mv .
10926 debootstrap $from $tmpdir $mirror
10927 chroot $tmpdir aptitude update
10928 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10929 #!/bin/sh
10930 exit 101
10931 EOF
10932 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10933 exit_cleanup() {
10934 umount $tmpdir/proc
10935 }
10936 mount -t proc proc $tmpdir/proc
10937 # Make sure proc is unmounted also on failure
10938 trap exit_cleanup EXIT INT
10939
10940 chroot $tmpdir aptitude -y install debconf-utils
10941
10942 # Make sure tasksel autoselection trigger. It need the test scripts
10943 # to return the correct answers.
10944 echo tasksel tasksel/desktop multiselect $desktop | \
10945 chroot $tmpdir debconf-set-selections
10946
10947 # Include the desktop and laptop task
10948 for test in desktop laptop ; do
10949 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10950 #!/bin/sh
10951 exit 2
10952 EOF
10953 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10954 done
10955
10956 DEBIAN_FRONTEND=noninteractive
10957 DEBIAN_PRIORITY=critical
10958 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10959 chroot $tmpdir tasksel --new-install
10960
10961 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10962 chroot $tmpdir aptitude update
10963 touch $tmpdir/etc/udev/kernel-upgrade
10964 chroot $tmpdir aptitude -y dist-upgrade
10965 fuser -mv
10966 &lt;/pre&gt;&lt;/blockquote&gt;
10967
10968 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10969 with aptitude, but I have not had time to look at how they behave
10970 differently so far. I hope to get a cron job running to do the test
10971 regularly and post the result on the web. The Gnome upgrade currently
10972 work, while the KDE upgrade fail because of the bug in
10973 kdebase-workspace-data&lt;/p&gt;
10974
10975 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10976 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10977 post, so I will refrain from trying. I can report that for Gnome,
10978 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10979 remove and 1 not upgraded and 1024MB need to be downloaded while for
10980 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10981 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10982
10983 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10984 is able to migrate to dependency based boot sequencing and parallel
10985 booting without a hitch. Was unsure if there were still bugs with
10986 packages failing to clean up their obsolete init.d script during
10987 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10988 packages.&lt;/p&gt;
10989 </description>
10990 </item>
10991
10992 <item>
10993 <title>Upstart or sysvinit - as init.d scripts see it</title>
10994 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10996 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10997 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10998 scripts to migrate (some of) their operations to upstart job while
10999 keeping the init.d for hurd and kfreebsd. The packages with such
11000 needs will need a way to get their init.d scripts to behave
11001 differently when used with sysvinit and with upstart. Because of
11002 this, I had a look at the environment variables set when a init.d
11003 script is running under upstart, and when it is not.&lt;/p&gt;
11004
11005 &lt;p&gt;With upstart, I notice these environment variables are set when a
11006 script is started from rcS.d/ (ignoring some irrelevant ones like
11007 COLUMNS):&lt;/p&gt;
11008
11009 &lt;blockquote&gt;&lt;pre&gt;
11010 DEFAULT_RUNLEVEL=2
11011 previous=N
11012 PREVLEVEL=
11013 RUNLEVEL=
11014 runlevel=S
11015 UPSTART_EVENTS=startup
11016 UPSTART_INSTANCE=
11017 UPSTART_JOB=rc-sysinit
11018 &lt;/pre&gt;&lt;/blockquote&gt;
11019
11020 &lt;p&gt;With sysvinit, these environment variables are set for the same
11021 script.&lt;/p&gt;
11022
11023 &lt;blockquote&gt;&lt;pre&gt;
11024 INIT_VERSION=sysvinit-2.88
11025 previous=N
11026 PREVLEVEL=N
11027 RUNLEVEL=S
11028 runlevel=S
11029 &lt;/pre&gt;&lt;/blockquote&gt;
11030
11031 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
11032 sysvinit are not set by upstart. Not sure if it is intentional or not
11033 to not be compatible with sysvinit in this regard.&lt;/p&gt;
11034
11035 &lt;p&gt;For scripts needing to behave differently when upstart is used,
11036 looking for the UPSTART_JOB environment variable seem to be a good
11037 choice.&lt;/p&gt;
11038 </description>
11039 </item>
11040
11041 <item>
11042 <title>A manual for standards wars...</title>
11043 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
11044 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
11045 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
11046 <description>&lt;p&gt;Via the
11047 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
11048 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
11049 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
11050 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
11051 following the standards wars of today.&lt;/p&gt;
11052 </description>
11053 </item>
11054
11055 <item>
11056 <title>Sitesummary tip: Listing computer hardware models used at site</title>
11057 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
11058 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
11059 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
11060 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
11061 to get a list of the machine types in use thanks to the DMI
11062 information extracted from each machine. The script to do so is
11063 included in the sitesummary package, and here is example output from
11064 the Skolelinux build servers:&lt;/p&gt;
11065
11066 &lt;blockquote&gt;&lt;pre&gt;
11067 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11068 vendor count
11069 Dell Computer Corporation 1
11070 PowerEdge 1750 1
11071 IBM 1
11072 eserver xSeries 345 -[8670M1X]- 1
11073 Intel 2
11074 [no-dmi-info] 3
11075 maintainer:~#
11076 &lt;/pre&gt;&lt;/blockquote&gt;
11077
11078 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
11079 provided in each machine. Here there are Intel machines without model
11080 information listed with Intel as vendor and no model, and virtual Xen
11081 machines listed as [no-dmi-info]. One can add -l as a command line
11082 option to list the individual machines.&lt;/p&gt;
11083
11084 &lt;p&gt;A larger list is
11085 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
11086 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
11087 provide the basic sitesummary report publicly. In their report there
11088 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
11089 their machines, and as sitesummary is available in both distributions,
11090 it is trivial to get all of them to report to the same central
11091 collector.&lt;/p&gt;
11092 </description>
11093 </item>
11094
11095 <item>
11096 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
11097 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
11098 <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>
11099 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
11100 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
11101 start at boot when an NVidia video card is used is handled. The
11102 problem seem to be that the nvidia X.org driver uses a long time to
11103 initialize, and this duration is longer than kdm is configured to
11104 wait.&lt;/p&gt;
11105
11106 &lt;p&gt;I came across two bugs related to this issue,
11107 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
11108 against initscripts and passed on to nvidia-glx when it became obvious
11109 that the nvidia drivers were involved, and
11110 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
11111 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
11112
11113 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
11114 problem nvidia video card owners experience and make sure the Debian
11115 distribution work out of the box for these users. The nvidia driver
11116 maintainers expect kdm to be set up to wait longer, while kdm expect
11117 the nvidia driver maintainers to fix the driver to start faster, and
11118 while they wait for each other I guess the users end up switching to a
11119 distribution that work for them. I have no idea what the solution is,
11120 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
11121
11122 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
11123 </description>
11124 </item>
11125
11126 <item>
11127 <title>Parallellized boot seem to hold up well in Debian/testing</title>
11128 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
11129 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
11130 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
11131 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
11132 The feature seem to hold up pretty well, but three fairly serious
11133 issues are known and should be solved:
11134
11135 &lt;p&gt;&lt;ul&gt;
11136
11137 &lt;li&gt;The wicd package seen to
11138 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
11139 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
11140 parallel booting is enabled. No idea why, but the wicd maintainer
11141 seem to be on the case.&lt;/li&gt;
11142
11143 &lt;li&gt;The nvidia X driver seem to
11144 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
11145 triggered more easily when parallel booting is in effect. The
11146 maintainer is on the case.&lt;/li&gt;
11147
11148 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
11149 sequencing (the shutdown is broken) when old file-rc users
11150 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
11151 sysv-rc. One way to solve it would be for file-rc to create
11152 /etc/init.d/.legacy-bootordering, and another is to try to make
11153 sysv-rc more robust. Will investigate some more and probably upload a
11154 workaround in sysv-rc to help those trying to move from file-rc to
11155 sysv-rc get a working shutdown.&lt;/li&gt;
11156
11157 &lt;/ul&gt;&lt;/p&gt;
11158
11159 &lt;p&gt;All in all not many surprising issues, and all of them seem
11160 solvable before Squeeze is released. In addition to these there are
11161 some packages with bugs in their dependencies and run level settings,
11162 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
11163
11164 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11165 the BTS, please usertag the report to get it to show up at
11166 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11167 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11168
11169 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
11170 </description>
11171 </item>
11172
11173 <item>
11174 <title>More flexible firmware handling in debian-installer</title>
11175 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
11176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
11177 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
11178 <description>&lt;p&gt;After a long break from debian-installer development, I finally
11179 found time today to return to the project. Having to spend less time
11180 working dependency based boot in debian, as it is almost complete now,
11181 definitely helped freeing some time.&lt;/p&gt;
11182
11183 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
11184 include some firmware packages on the Debian Edu CDs, those needed to
11185 get disk and network controllers working. Without having these
11186 firmware packages available during installation, it is impossible to
11187 install Debian Edu on the given machine, and because our target group
11188 are non-technical people, asking them to provide firmware packages on
11189 an external medium is a support pain. Initially, I expected it to be
11190 enough to include the firmware packages on the CD to get
11191 debian-installer to find and use them. This proved to be wrong.
11192 Next, I hoped it was enough to symlink the relevant firmware packages
11193 to some useful location on the CD (tried /cdrom/ and
11194 /cdrom/firmware/). This also proved to not work, and at this point I
11195 found time to look at the debian-installer code to figure out what was
11196 going to work.&lt;/p&gt;
11197
11198 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
11199 look revealed that it would only look for firmware packages outside
11200 the installation media, so the CD was never checked for firmware
11201 packages. It would only check USB sticks, floppies and other
11202 &quot;external&quot; media devices. Today I changed it to also look in the
11203 /cdrom/firmware/ directory on the mounted CD or DVD, which should
11204 solve the problem I ran into with Debian edu. I also changed it to
11205 look in /firmware/, to make sure the installer also find firmware
11206 provided in the initrd when booting the installer via PXE, to allow us
11207 to provide the same feature in the PXE setup included in Debian
11208 Edu.&lt;/p&gt;
11209
11210 &lt;p&gt;To make sure firmware deb packages with a license questions are not
11211 activated without asking if the license is accepted, I extended
11212 hw-detect to look for preinst scripts in the firmware packages, and
11213 run these before activating the firmware during installation. The
11214 license question is asked using debconf in the preinst, so this should
11215 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
11216
11217 &lt;p&gt;If you want to discuss the details of these features, please
11218 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
11219 </description>
11220 </item>
11221
11222 <item>
11223 <title>Parallellized boot is now the default in Debian/unstable</title>
11224 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
11225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
11226 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
11227 <description>&lt;p&gt;Since this evening, parallel booting is the default in
11228 Debian/unstable for machines using dependency based boot sequencing.
11229 Apparently the testing of concurrent booting has been wider than
11230 expected, if I am to believe the
11231 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11232 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
11233 with the feature this weekend, to give us some time to detect any
11234 remaining problems before Squeeze is frozen. If serious problems are
11235 detected, it is simple to change the default back to sequential boot.
11236 The upload of the new sysvinit package also activate a new upstream
11237 version.&lt;/p&gt;
11238
11239 More information about
11240 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11241 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
11242 currently possible to disable parallel booting when one run into
11243 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
11244
11245 &lt;blockquote&gt;&lt;pre&gt;
11246 CONCURRENCY=none
11247 &lt;/pre&gt;&lt;/blockquote&gt;
11248
11249 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11250 the BTS, please usertag the report to get it to show up at
11251 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11252 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11253 </description>
11254 </item>
11255
11256 <item>
11257 <title>Sitesummary tip: Listing MAC address of all clients</title>
11258 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
11259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
11260 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
11261 <description>&lt;p&gt;In the recent Debian Edu versions, the
11262 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
11263 system&lt;/a&gt; is used to keep track of the machines in the school
11264 network. Each machine will automatically report its status to the
11265 central server after boot and once per night. The network setup is
11266 also reported, and using this information it is possible to get the
11267 MAC address of all network interfaces in the machines. This is useful
11268 to update the DHCP configuration.&lt;/p&gt;
11269
11270 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
11271 ist all MAC addresses of all machines reporting to sitesummary. Run
11272 this on the collector host:&lt;/p&gt;
11273
11274 &lt;blockquote&gt;&lt;pre&gt;
11275 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
11276 &lt;/pre&gt;&lt;/blockquote&gt;
11277
11278 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
11279 line per machine and with space between the MAC addresses.&lt;/p&gt;
11280
11281 &lt;p&gt;To allow system administrators easier job at adding static DHCP
11282 addresses for hosts, it would be possible to extend this to fetch
11283 machine information from sitesummary and update the DHCP and DNS
11284 tables in LDAP using this information. Such tool is unfortunately not
11285 written yet.&lt;/p&gt;
11286 </description>
11287 </item>
11288
11289 <item>
11290 <title>systemd, an interesting alternative to upstart</title>
11291 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
11292 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
11293 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
11294 <description>&lt;p&gt;The last few days a new boot system called
11295 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
11296 has been
11297 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
11298
11299 to the free software world. I have not yet had time to play around
11300 with it, but it seem to be a very interesting alternative to
11301 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
11302 a good alternative for Debian when we are able to switch to an event
11303 based boot system. Tollef is
11304 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
11305 systemd into Debian, and I look forward to seeing how well it work. I
11306 like the fact that systemd handles init.d scripts with dependency
11307 information natively, allowing them to run in parallel where upstart
11308 at the moment do not.&lt;/p&gt;
11309
11310 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
11311 platform support. It only work on recent Linux kernels, and also need
11312 some new kernel features enabled to function properly. This means
11313 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11314 system. Not sure how that will be handled if systemd proves to be the
11315 way forward.&lt;/p&gt;
11316
11317 &lt;p&gt;In the mean time, based on the
11318 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11319 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
11320 decided to enable full parallel booting as the default in Debian as
11321 soon as possible (probably this weekend or early next week), to see if
11322 there are any remaining serious bugs in the init.d dependencies. A
11323 new version of the sysvinit package implementing this change is
11324 already in experimental. If all go well, Squeeze will be released
11325 with parallel booting enabled by default.&lt;/p&gt;
11326 </description>
11327 </item>
11328
11329 <item>
11330 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
11331 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
11332 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
11333 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
11334 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
11335 complete, so complete that it is actually possible to run all the
11336 init.d scripts in parallell based on these dependencies. If you want
11337 to test your Squeeze system, make sure
11338 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11339 based boot sequencing&lt;/a&gt; is enabled, and add this line to
11340 /etc/default/rcS:&lt;/p&gt;
11341
11342 &lt;blockquote&gt;&lt;pre&gt;
11343 CONCURRENCY=makefile
11344 &lt;/pre&gt;&lt;/blockquote&gt;
11345
11346 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
11347 scripts in parallel using the dependency information stored in
11348 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11349 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11350 to try to start the kdm and gdm scripts as early as possible, and will
11351 start the facilities required by kdm or gdm as early as possible to
11352 make this happen.&lt;/p&gt;
11353
11354 &lt;p&gt;Give it a try, and see if you like the result. If some services
11355 fail to start properly, it is most likely because they have incomplete
11356 init.d script dependencies in their startup script (or some of their
11357 dependent scripts have incomplete dependencies). Report bugs and get
11358 the package maintainers to fix it. :)&lt;/p&gt;
11359
11360 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
11361 manage to get the init.d script dependencies complete and correct. I
11362 expect we will get there in Squeeze+1, if we get manage to test and
11363 fix the remaining issues.&lt;/p&gt;
11364
11365 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11366 the BTS, please usertag the report to get it to show up at
11367 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11368 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11369 </description>
11370 </item>
11371
11372 <item>
11373 <title>Debian has switched to dependency based boot sequencing</title>
11374 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
11375 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
11376 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
11377 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
11378 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
11379 have been migrated to using dependency based boot sequencing. This
11380 conclude work me and others have been doing for the last three days.
11381 It feels great to see this finally part of the default Debian
11382 installation. Now we just need to weed out the last few problems that
11383 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
11384
11385 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
11386 fixing the more fundamental problem of handing the event based
11387 non-predictable kernel in the early boot.&lt;/p&gt;
11388 </description>
11389 </item>
11390
11391 <item>
11392 <title>Taking over sysvinit development</title>
11393 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
11394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
11395 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
11396 <description>&lt;p&gt;After several years of frustration with the lack of activity from
11397 the existing sysvinit upstream developer, I decided a few weeks ago to
11398 take over the package and become the new upstream. The number of
11399 patches to track for the Debian package was becoming a burden, and the
11400 lack of synchronization between the distribution made it hard to keep
11401 the package up to date.&lt;/p&gt;
11402
11403 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11404 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
11405 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
11406 and Fedora), based on the patches currently in use in these
11407 distributions. We Debian maintainers plan to move to this tarball as
11408 the new upstream as soon as we find time to do the merge. Since the
11409 new tarball was created, we agreed with Werner at SuSe to make a new
11410 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
11411 development there. The project is registered and currently waiting
11412 for approval by the Savannah administrators, and as soon as it is
11413 approved, we will import the old versions from svn and continue
11414 working on the future release.&lt;/p&gt;
11415
11416 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
11417 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
11418 </description>
11419 </item>
11420
11421 <item>
11422 <title>Debian boots quicker and quicker</title>
11423 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
11424 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
11425 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
11426 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
11427 people involved in the boot system on Debian and Ubuntu, to see if we
11428 could find more ways to speed up the boot system. This was an Ubuntu
11429 funded
11430 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
11431 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
11432 of boot systems, and ways to handle the increasing number of boot
11433 issues introduced by the Linux kernel becoming more and more
11434 asynchronous and event base. The Ubuntu approach using udev and
11435 upstart might be a good way forward. Time will show.&lt;/p&gt;
11436
11437 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
11438 process in Debian. All of these should be applied to get a quick
11439 boot:&lt;/p&gt;
11440
11441 &lt;ul&gt;
11442
11443 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
11444
11445 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
11446 clock is in UTC.&lt;/li&gt;
11447
11448 &lt;li&gt;Install and activate the insserv package to enable
11449 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11450 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
11451
11452 &lt;/ul&gt;
11453
11454 These points are based on the Google summer of code work done by
11455 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
11456 Villegas&lt;/a&gt;.
11457
11458 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
11459 unstable yesterday. When we tested it, we were able to cut 6 seconds
11460 from the boot sequence. It depend on very correct dependency
11461 declaration in all init.d scripts, so I expect us to find edge cases
11462 where the dependences in some scripts are slightly wrong when we start
11463 using this.&lt;/p&gt;
11464
11465 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11466 introduced by Raphael Geissert today, one that could affect the
11467 startup speed as well. Instead of starting some scripts concurrently
11468 from rcS.d/ and another set of scripts from rc2.d/, it would be
11469 possible to run a of them in the same process. A quick way to test
11470 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
11471 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
11472 </description>
11473 </item>
11474
11475 <item>
11476 <title>BSAs påstander om piratkopiering møter motstand</title>
11477 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
11478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
11479 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
11480 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
11481 programvareselskapene som Microsoft og Apple, publisert en rapport der
11482 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11483 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11484 dager siden kom
11485 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
11486 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
11487 dagene. Et spesielt interessant kommentar fra Sverige,
11488 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
11489 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
11490
11491 &lt;blockquote&gt;
11492 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
11493 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11494 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
11495 exakta&quot;, säger BSAs Sverigechef John Hugosson.
11496 &lt;/blockquote&gt;
11497
11498 &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
11499 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
11500 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
11501 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
11502 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
11503
11504 &lt;p&gt;Fant lenkene via &lt;a
11505 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
11506 på Slashdot&lt;/a&gt;.&lt;/p&gt;
11507 </description>
11508 </item>
11509
11510 <item>
11511 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
11512 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
11513 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
11514 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
11515 <description>&lt;p&gt;Kom over
11516 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
11517 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11518 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11519 jobber til daglig. En rask opptelling forteller meg at vi har 490
11520 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
11521 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
11522 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
11523 </description>
11524 </item>
11525
11526 <item>
11527 <title>Kryptert harddisk - naturligvis</title>
11528 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
11529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
11530 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
11531 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
11532 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
11533 når en tar tap av arbeidstid, fortrolige dokumenter,
11534 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11535 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11536 til at jeg har kryptert harddisken på både kontormaskinen og min
11537 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11538 komme på avveie, den første informasjon relatert til jobben min ved
11539 Universitetet i Oslo, og den andre relatert til blant annet
11540 foreningsarbeide. Kryptering av diskene gjør at det er lite
11541 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11542 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11543 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11544 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11545 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11546 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11547 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11548 det er gjort slik jeg gjør det er minimale, og gevinstene er
11549 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11550 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
11551
11552 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11553 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11554 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11555 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11556 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11557 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11558 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11559 betydelige.&lt;/p&gt;
11560 </description>
11561 </item>
11562
11563 <item>
11564 <title>Two projects that have improved the quality of free software a lot</title>
11565 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
11566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
11567 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
11568 <description>&lt;p&gt;There are two software projects that have had huge influence on the
11569 quality of free software, and I wanted to mention both in case someone
11570 do not yet know them.&lt;/p&gt;
11571
11572 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11573 tool to detect and expose errors in the memory handling of programs.
11574 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11575 and it will report any problems on stdout. It is even better if the
11576 program include debug information. With debug information, it is able
11577 to report the source file name and line number where the problem
11578 occurs. It can report things like &#39;reading past memory block in file
11579 X line N, the memory block was allocated in file Y, line M&#39;, and
11580 &#39;using uninitialised value in control logic&#39;. This tool has made it
11581 trivial to investigate reproducible crash bugs in programs, and have
11582 reduced the number of this kind of bugs in free software a lot.
11583
11584 &lt;p&gt;The second one is
11585 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11586 a source code checker. It is able to process the source of a program
11587 and find problems in the logic without running the program. It
11588 started out as the Stanford Checker and became well known when it was
11589 used to find bugs in the Linux kernel. It is now a commercial tool
11590 and the company behind it is running
11591 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11592 free software community, where a lot of free software projects get
11593 their source checked for free. Several thousand defects have been
11594 found and fixed so far. It can find errors like &#39;lock L taken in file
11595 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11596 Y lines O to P can never be executed&#39;. The projects included in the
11597 community service project have managed to get rid of a lot of
11598 reliability problems thanks to Coverity.&lt;/p&gt;
11599
11600 &lt;p&gt;I believe tools like this, that are able to automatically find
11601 errors in the source, are vital to improve the quality of software and
11602 make sure we can get rid of the crashing and failing software we are
11603 surrounded by today.&lt;/p&gt;
11604 </description>
11605 </item>
11606
11607 <item>
11608 <title>No patch is not better than a useless patch</title>
11609 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11611 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11612 <description>&lt;p&gt;Julien Blache
11613 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11614 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11615 patch allow one to discuss a concrete and proposed solution, and also
11616 prove that the issue at hand is important enough for someone to spent
11617 time on fixing it. No patch do not provide any of these positive
11618 properties.&lt;/p&gt;
11619 </description>
11620 </item>
11621
11622 <item>
11623 <title>Standardize on protocols and formats, not vendors and applications</title>
11624 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11625 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11626 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11627 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11628 very good one to form a long lived computer infrastructure. It is the
11629 simple one, lost by many in todays computer industry: Standardize on
11630 open network protocols and open exchange/storage formats, not applications.
11631 Applications come and go, while protocols and files tend to stay, and
11632 thus one want to make it easy to change application and vendor, while
11633 avoiding conversion costs and locking users to a specific platform or
11634 application.&lt;/p&gt;
11635
11636 &lt;p&gt;This approach make it possible to replace the client applications
11637 independently of the server applications. One can even allow users to
11638 use several different applications as long as they handle the selected
11639 protocol and format. In the normal case, only one client application
11640 is recommended and users only get help if they choose to use this
11641 application, but those that want to deviate from the easy path are not
11642 blocked from doing so.&lt;/p&gt;
11643
11644 &lt;p&gt;It also allow us to replace the server side without forcing the
11645 users to replace their applications, and thus allow us to select the
11646 best server implementation at any moment, when scale and resouce
11647 requirements change.&lt;/p&gt;
11648
11649 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11650 open formats, but I would never recommend standardizing on a single
11651 application that do not use open network protocol or open formats.&lt;/p&gt;
11652 </description>
11653 </item>
11654
11655 <item>
11656 <title>Returning from Skolelinux developer gathering</title>
11657 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11658 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11659 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11660 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11661 Edu/Skolelinux development gathering. I got a bit done tuning the
11662 desktop, and looked into the dynamic service location protocol
11663 implementation avahi. It look like it could be useful for us. Almost
11664 30 people participated, and I believe it was a great environment to
11665 get to know the Skolelinux system. Walter Bender, involved in the
11666 development of the Sugar educational platform, presented his stuff and
11667 also helped me improve my OLPC installation. He also showed me that
11668 his Turtle Art application can be used in standalone mode, and we
11669 agreed that I would help getting it packaged for Debian. As a
11670 standalone application it would be great for Debian Edu. We also
11671 tried to get the video conferencing working with two OLPCs, but that
11672 proved to be too hard for us. The application seem to need more work
11673 before it is ready for me. I look forward to getting home and relax
11674 now. :)&lt;/p&gt;
11675 </description>
11676 </item>
11677
11678 <item>
11679 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11680 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11681 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11682 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11683 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11684 optimal. There is RFC 2307 documenting one way to store NIS maps in
11685 LDAP, and a modified version of this normally called RFC 2307bis, with
11686 some modifications to be compatible with Active Directory. The RFC
11687 specification handle the content of a lot of system databases, but do
11688 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11689
11690 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11691 we would like to store information about users, SMB clients/hosts,
11692 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11693 and LTSP configuration in LDAP. These objects have a lot in common,
11694 but with the current LDAP schemas it is not possible to have one
11695 object per entity. For example, one need to have at least three LDAP
11696 objects for a given computer, one with the SMB related stuff, one with
11697 DNS information and another with DHCP information. The schemas
11698 provided for DNS and DHCP are impossible to combine into one LDAP
11699 object. In addition, it is impossible to implement quick queries for
11700 netgroup membership, because of the way NIS triples are implemented.
11701 It just do not scale. I believe it is time for a few RFC
11702 specifications to cleam up this mess.&lt;/p&gt;
11703
11704 &lt;p&gt;I would like to have one LDAP object representing each computer in
11705 the network, and this object can then keep the SMB (ie host key), DHCP
11706 (mac address/name) and DNS (name/IP address) settings in one place.
11707 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11708
11709 &lt;p&gt;I would also like to have a quick way to map from a user or
11710 computer and to the net group this user or computer is a member.&lt;/p&gt;
11711
11712 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11713 in this regard, and the unix side need to catch up. Time to start a
11714 new IETF work group?&lt;/p&gt;
11715 </description>
11716 </item>
11717
11718 <item>
11719 <title>Endelig er Debian Lenny gitt ut</title>
11720 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11721 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11722 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11723 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11724 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11725 Et langt steg videre for Debian-prosjektet, og en rekke nye
11726 programpakker blir nå tilgjengelig for de av oss som bruker den
11727 stabile utgaven av Debian. Neste steg er nå å få
11728 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11729 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11730 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11731 slippes løs på skolene. Takk til alle debian-utviklerne som har
11732 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11733 bootsekvens tilgjengelig i stabil utgave, vha pakken
11734 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11735 </description>
11736 </item>
11737
11738 <item>
11739 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11740 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11742 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11743 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11744 Oslo. Most of Saturday was used for the general assemly for the
11745 member organization, but the rest of the weekend I used to tune the
11746 LTSP installation. LTSP now work out of the box on the 10-network.
11747 Acer Aspire One proved to be a very nice thin client, with both
11748 screen, mouse and keybard in a small box. Was working on getting the
11749 diskless workstation setup configured out of the box, but did not
11750 finish it before the weekend was up.&lt;/p&gt;
11751
11752 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11753 the Brazilian group, so that will have to wait for the next
11754 development gathering. Would love to have the Debian Edu installer
11755 automatically detect and configure a multiseat setup when it find one
11756 of these cards.&lt;/p&gt;
11757 </description>
11758 </item>
11759
11760 <item>
11761 <title>The sorry state of multimedia browser plugins in Debian</title>
11762 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11764 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11765 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11766 plugins available in Debian Lenny, to see which one we should use by
11767 default in Debian Edu. We need an embedded video playing plugin with
11768 control buttons to pause or stop the video, and capable of streaming
11769 all the multimedia content available on the web. The test results and
11770 notes are available on
11771 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11772 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11773 fill this need. My personal video player favorite, VLC, has a really
11774 bad plugin which fail on a lot of the test pages. A lot of the MIME
11775 types I would expect to work with any free software player (like
11776 video/ogg), just do not work. And simple formats like the
11777 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11778 totem and vlc plugins. I hope the situation will improve soon. No
11779 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11780
11781 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11782 be the only one fitting our needs. :/&lt;/p&gt;
11783 </description>
11784 </item>
11785
11786 </channel>
11787 </rss>