]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
3c99860c1941e81bcd7cd2b54119fab66d12cdcb
[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>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
11 <link>http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
13 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
14 <description>&lt;p&gt;The curiosity got the better of me when
15 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
16 reported&lt;/a&gt; that New Jersey was desperately looking for
17 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
18 and a few days later it was reported that
19 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
20 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
21
22 &lt;p&gt;I thus decided to have a look at free software alternatives to
23 learn COBOL, and had the pleasure to find
24 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
25 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
26 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
27 transforming COBOL code to C or C++ before giving it to GCC or Visual
28 Studio to build binaries.&lt;/p&gt;
29
30 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
31 quick response, and also was happy to see a new Debian maintainer
32 taking over when the original one recently asked to be replaced. A
33 new Debian upload was done as recently as yesterday.&lt;/p&gt;
34
35 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
36 introduction and make and run simple COBOL programs. It was fun to
37 learn a new programming language. If you want to test for yourself,
38 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
39 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
40
41 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
42 standard compliant it is, but it claim to pass most tests from COBOL
43 test suite, which sound good to me. It is nice to know it is possible
44 to learn COBOL using software without any usage restrictions, and I am
45 very happy such nice free software project as this is available. If
46 you as me is curious about COBOL, check it out.&lt;/p&gt;
47
48 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
49 activities, please send Bitcoin donations to my address
50 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
51 </description>
52 </item>
53
54 <item>
55 <title>Jami/Ring, finally functioning peer to peer communication client</title>
56 <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
57 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
58 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
59 <description>&lt;p&gt;Some years ago, in 2016, I
60 &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
61 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
62 It would provide messaging without any central server coordinating the
63 system and without requiring all users to register a phone number or
64 own a mobile phone. Back then, I could not get it to work, and put it
65 aside until it had seen more development. A few days ago I decided to
66 give it another try, and am happy to report that this time I am able
67 to not only send and receive messages, but also place audio and video
68 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
69
70 &lt;p&gt;The Ring system changed name earlier this year to
71 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
72 tried doing web search for &#39;ring&#39; when I discovered it for the first
73 time, and can only applaud this change as it is impossible to find
74 something called Ring among the noise of other uses of that word. Now
75 you can search for &#39;jami&#39; and this client and
76 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
77 least on duckduckgo.&lt;/p&gt;
78
79 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
80 calls, and try to send them directly between the communicating parties
81 if possible. If this proves impossible (for example if both ends are
82 behind NAT), it will use a central SIP TURN server maintained by the
83 Jami project. Jami can also be a normal SIP client. If the SIP
84 server is unencrypted, the audio and video calls will also be
85 unencrypted. This is as far as I know the only case where Jami will
86 do anything without encryption.&lt;/p&gt;
87
88 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
89 Android, iOS, and Android TV. It is included in Debian already. Jami
90 also work for those using F-Droid without any Google connections,
91 while Signal do not.
92 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
93 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
94 distributed hash table (DHT) system (similar to BitTorrent) running
95 over UDP. On one of the networks I use, I discovered Jami failed to
96 work. I tracked this down to the fact that incoming UDP packages
97 going to ports 1-49999 were blocked, and the DHT would pick a random
98 port and end up in the low range most of the time. After talking to
99 the developers, I solved this by enabling the dhtproxy in the
100 settings, thus using TCP to talk to a central DHT proxy instead of
101
102 peering directly with others. I&#39;ve been told the developers are
103 working on allowing DHT to use TCP to avoid this problem. I also ran
104 into a problem when trying to talk to the version of Ring included in
105 Debian Stable (Stretch). Apparently the protocol changed between
106 beta2 and the current version, making these clients incompatible.
107 Hopefully the protocol will not be made incompatible in the
108 future.&lt;/p&gt;
109
110 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
111 came across another communication platform I have not tested yet. The
112 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
113 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
114 become the topic of a future blog post.&lt;/p&gt;
115
116 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
117 activities, please send Bitcoin donations to my address
118 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
119 </description>
120 </item>
121
122 <item>
123 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
124 <link>http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
126 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
127 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
128 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
129 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
130 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
131 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
132 nye versjonen kom på nyåret, og ble
133 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
134 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
135 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
136 måtte justeres, men ikke noe alvorlig. Har oppdatert
137 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
138 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
139
140 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
141 å spille for oss som liker slikt. :)&lt;/p&gt;
142
143 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
144 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
145 til min adresse
146 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
147 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
148 </description>
149 </item>
150
151 <item>
152 <title>Debian now got everything you need to program Micro:bit</title>
153 <link>http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
155 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
156 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
157 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
158 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
159 thanks to the hard work of Nick Morrott and the Debian python
160 packaging team. The micro:bit project recommend the mu-editor to
161 program the microcomputer, as this editor will take care of all the
162 machinery required to injekt/flash micropython alongside the program
163 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
164
165 &lt;p&gt;There are three main pieces involved. The first to enter Debian
166 was
167 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
168 which was accepted into the archive 2019-01-12. The next one was
169 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
170 showed up 2019-01-13. The final and hardest part to to into the
171 archive was
172 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
173 which needed to get its build system and dependencies into Debian
174 before it was accepted 2019-01-20. The last one is already in Debian
175 Unstable and should enter Debian Testing / Buster in three days. This
176 all allow any user of the micro:bit to get going by simply running
177 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
178 Buster is released as stable, all the users of Debian stable will be
179 catered for.&lt;/p&gt;
180
181 &lt;p&gt;As a minor final touch, I added rules to
182 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
183 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
184 package. This make sure any user of the isenkram desktop daemon will
185 get a popup suggesting to install mu-editor then the USB cable from
186 the micro:bit is inserted for the first time.&lt;/p&gt;
187
188 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
189
190 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
191 activities, please send Bitcoin donations to my address
192 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
193 </description>
194 </item>
195
196 <item>
197 <title>Learn to program with Minetest on Debian</title>
198 <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
199 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
200 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
201 <description>&lt;p&gt;A fun way to learn how to program
202 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
203 instructions in the book
204 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
205 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
206 who like to play with Minecraft. The book uses a Python library to
207 talk to a TCP/IP socket with an API accepting build instructions and
208 providing information about the current players in a Minecraft world.
209 The TCP/IP API was first created for the Minecraft implementation for
210 Raspberry Pi, and has since been ported to some server versions of
211 Minecraft. The book contain recipes for those using Windows, MacOSX
212 and Raspian. But a little known fact is that you can follow the same
213 recipes using the free software construction game
214 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
215
216 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
217 Minetest module implementing the same API&lt;/a&gt;, making it possible to
218 use the Python programs coded to talk to Minecraft with Minetest too.
219 I
220 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
221 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
222 FTP masters NEW queue, learning to program Python with Minetest on
223 Debian will be a simple &#39;apt install&#39; away. The Debian package is
224 maintained as part of the Debian Games team, and
225 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
226 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
227 Salsa.&lt;/p&gt;
228
229 &lt;p&gt;You will most likely need to install several of the Minetest
230 modules in Debian for the examples included with the library to work
231 well, as there are several blocks used by the example scripts that are
232 provided via modules in Minetest. Without the required blocks, a
233 simple stone block is used instead. My initial testing with a analog
234 clock did not get gold arms as instructed in the python library, but
235 instead used stone arms.&lt;/p&gt;
236
237 &lt;p&gt;I tried to find a way to add the API to the desktop version of
238 Minecraft, but were unable to find any working recipes. The
239 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
240 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
241 working with a standalone Minecraft server setup. Are there any
242 options to use with the normal desktop version?&lt;/p&gt;
243
244 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
245 activities, please send Bitcoin donations to my address
246 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
247 </description>
248 </item>
249
250 <item>
251 <title>Time for an official MIME type for patches?</title>
252 <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
253 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
254 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
255 <description>&lt;p&gt;As part of my involvement in
256 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
257 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
258 emails into a test instance of the archive to see how well this would
259 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
260 notmuch email database&lt;/a&gt;, all public emails sent to me via
261 @lists.debian.org, giving me a set of around 216 000 emails to import.
262 In the process, I had a look at the various attachments included in
263 these emails, to figure out what to do with attachments, and noticed
264 that one of the most common attachment formats do not have
265 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
266 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
267 diff, ie the input for patch, is on the top 10 list of formats
268 included in these emails. At the moment people seem to use either
269 text/x-patch or text/x-diff, but neither is officially registered. It
270 would be better if one official MIME type were registered and used
271 everywhere.&lt;/p&gt;
272
273 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
274 up the topic on
275 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
276 media-types mailing list&lt;/a&gt;. If you are interested in discussion
277 which MIME type to use as the official for patch files, or involved in
278 making software using a MIME type for patches, perhaps you would like
279 to join the discussion?&lt;/p&gt;
280
281 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
282 activities, please send Bitcoin donations to my address
283 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
284 </description>
285 </item>
286
287 <item>
288 <title>Automatic Google Drive sync using grive in Debian</title>
289 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
291 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
292 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
293 rescue the remains, I helped set up automatic sync with Google Drive.
294 I did not find any sensible Debian package handling this
295 automatically, so I rebuild the grive2 source from
296 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
297 task and added a autostart desktop entry and a small shell script to
298 run in the background while the user is logged in to do the sync.
299 Here is a sketch of the setup for future reference.&lt;/p&gt;
300
301 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
302 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
303 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
304 to start the sync when the user log in:&lt;/p&gt;
305
306 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
307 [Desktop Entry]
308 Name=Google drive autosync
309 Type=Application
310 Exec=/home/user/bin/grive-sync
311 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
312
313 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
314 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
315
316 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
317 #!/bin/sh
318 set -e
319 cd ~/
320 cleanup() {
321 if [ &quot;$syncpid&quot; ] ; then
322 kill $syncpid
323 fi
324 }
325 trap cleanup EXIT INT QUIT
326 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
327 syncpdi=$!
328 while true; do
329 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
330 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
331 exit 1
332 fi
333 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
334 /usr/lib/grive/grive-sync.sh sync googledrive
335 fi
336 sleep 300
337 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
338 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
339
340 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
341 GNU GPL v2 licensed (or any later version, at your leisure), but I
342 doubt this code is possible to claim copyright on.&lt;/p&gt;
343
344 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
345 activities, please send Bitcoin donations to my address
346 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
347 </description>
348 </item>
349
350 <item>
351 <title>Using the Kodi API to play Youtube videos</title>
352 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
354 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
355 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
356 tell it to play a youtube URL I received in a chat, without having to
357 insert search terms using the on-screen keyboard. After searching the
358 web for API access to the Youtube plugin and testing a bit, I managed
359 to find a recipe that worked. If you got a kodi instance with its API
360 available from http://kodihost/jsonrpc, you can try the following to
361 have check out a nice cover band.&lt;/p&gt;
362
363 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
364 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
365 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
366 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
367 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
368
369 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
370 first argument. It can now handle direct video links, youtube links
371 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
372 Chromecast. :)&lt;/p&gt;
373
374 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
375 activities, please send Bitcoin donations to my address
376 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
377 </description>
378 </item>
379
380 <item>
381 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
382 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
383 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
384 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
385 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
386 with my family using a self hosted solution, as it is unacceptable to
387 place images from my personal life under the control of strangers
388 working for data hoarders like Google or Dropbox. The last few days I
389 have drafted an approach that might work out, and I would like to
390 share it with you. I would like to publish images on a server under
391 my control, and point some Internet connected display units using some
392 free and open standard to the images I published. As my primary
393 language is not limited to ASCII, I need to store metadata using
394 UTF-8. Many years ago, I hoped to find a digital photo frame capable
395 of reading a RSS feed with image references (aka using the
396 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
397 of such frames. In the end I gave up that approach.&lt;/p&gt;
398
399 &lt;p&gt;Some months ago, I discovered that
400 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
401 read images from a RSS feed, and used it to set up a screen saver on
402 my home info screen, showing images from the Daily images feed from
403 NASA. This proved to work well. More recently I discovered that
404 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
405 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
406 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
407 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
408 screen saver capable of reading a RSS feed with images and news. For
409 fun, I used it this summer to test Kodi on my parents TV by hooking up
410 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
411 screen saver showing selected pictures from my selection.&lt;/p&gt;
412
413 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
414 a RSS feed for the Kodi instance. I adjusted my &lt;a
415 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
416 /var/www/html/privatepictures/, wrote a small Perl script to extract
417 title and description metadata from the photo files and generate the
418 RSS file. I ended up using Perl instead of python, as the
419 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
420 tags I ended up using, while python3-exif did not. The relevant EXIF
421 tags only support ASCII, so I had to find better alternatives. XMP
422 seem to have the support I need.&lt;/p&gt;
423
424 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
425 use tags that can be easily added/updated using normal free software
426 photo managing software. I ended up using the tags set using this
427 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
428
429 &lt;blockquote&gt;&lt;pre&gt;
430 exiftool -headline=&#39;The RSS image title&#39; \
431 -description=&#39;The RSS image description.&#39; \
432 -subject+=for-family photo.jpeg
433 &lt;/pre&gt;&lt;/blockquote&gt;
434
435 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
436 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
437 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
438 shared with my family. Images with this keyword set are located and
439 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
440
441 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
442 suggestions.&lt;/p&gt;
443
444 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
445 activities, please send Bitcoin donations to my address
446 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
447 </description>
448 </item>
449
450 <item>
451 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
452 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
454 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
455 <description>&lt;p&gt;Last night, I wrote
456 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
457 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
458 During the day I received valuable feedback, and thanks to the
459 suggestions I have been able to rewrite the recipe into a much simpler
460 approach requiring no setup at all. It is a single script that take
461 care of it all.&lt;/p&gt;
462
463 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
464 desktop and stream it to Kodi. This fixed the video quality issue I
465 saw initially. It further removes the need to add a m3u file on the
466 Kodi machine, as it instead connects to
467 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
468 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
469 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
470 the script below, run it with the DNS name or IP address of the kodi
471 server to stream to as the only argument, and watch your screen show
472 up on the Kodi screen. Note, it depend on multicast on the local
473 network, so if you need to stream outside the local network, the
474 script must be modified. Also note, I have no idea if audio work, as
475 I only care about the picture part.&lt;/p&gt;
476
477 &lt;blockquote&gt;&lt;pre&gt;
478 #!/bin/sh
479 #
480 # Stream the Linux desktop view to Kodi. See
481 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
482 # for backgorund information.
483
484 # Make sure the stream is stopped in Kodi and the gstreamer process is
485 # killed if something go wrong (for example if curl is unable to find the
486 # kodi server). Do the same when interrupting this script.
487 kodicmd() {
488 host=&quot;$1&quot;
489 cmd=&quot;$2&quot;
490 params=&quot;$3&quot;
491 curl --silent --header &#39;Content-Type: application/json&#39; \
492 --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; \
493 &quot;http://$host/jsonrpc&quot;
494 }
495 cleanup() {
496 if [ -n &quot;$kodihost&quot; ] ; then
497 # Stop the playing when we end
498 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
499 jq .result[].playerid)
500 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
501 fi
502 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
503 kill &quot;$gstpid&quot;
504 fi
505 }
506 trap cleanup EXIT INT
507
508 if [ -n &quot;$1&quot; ]; then
509 kodihost=$1
510 shift
511 else
512 kodihost=kodi.local
513 fi
514
515 mcast=239.255.0.1
516 mcastport=1234
517 mcastttl=1
518
519 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
520 cut -d&quot; &quot; -f2|head -1)
521 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
522 videoconvert ! queue2 ! \
523 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
524 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
525 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
526 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
527 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
528 &gt; /dev/null 2&gt;&amp;1 &amp;
529 gstpid=$!
530
531 # Give stream a second to get going
532 sleep 1
533
534 # Ask kodi to start streaming using its JSON-RPC API
535 kodicmd &quot;$kodihost&quot; Player.Open \
536 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
537
538 # wait for gst to end
539 wait &quot;$gstpid&quot;
540 &lt;/pre&gt;&lt;/blockquote&gt;
541
542 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
543
544 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
545 activities, please send Bitcoin donations to my address
546 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
547 </description>
548 </item>
549
550 <item>
551 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
552 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
553 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
554 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
555 <description>&lt;p&gt;PS: See
556 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
557 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
558
559 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
560 my projector connected to Kodi. I sadly had to admit that I had no
561 idea, as it was a task I never had tried. Since then, I have been
562 looking for a way to do so, preferable without much extra software to
563 install on either side. Today I found a way that seem to kind of
564 work. Not great, but it is a start.&lt;/p&gt;
565
566 &lt;p&gt;I had a look at several approaches, for example
567 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
568 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
569 local storage enough to store the stream locally. This is not going
570 to work well for me, lacking enough free space, and it would
571 impossible for my friend to get working.&lt;/p&gt;
572
573 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
574 video stream that Kodi could play. Preferably using
575 broadcast/multicast, to avoid having to change any setup on the Kodi
576 side when starting such stream. Unfortunately, the only recipe I
577 could find using multicast used the rtp protocol, and this protocol
578 seem to not be supported by Kodi.&lt;/p&gt;
579
580 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
581 have to specify the IP address of the streaming machine in both the
582 sending command and the file on the Kodi server. But it is showing my
583 desktop, and thus allow us to have a shared look on the big screen at
584 the programs I work on.&lt;/p&gt;
585
586 &lt;p&gt;I did not spend much time investigating codeces. I combined the
587 rtp and rtsp recipes from
588 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
589 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
590 this working on the desktop/streaming end.&lt;/p&gt;
591
592 &lt;blockquote&gt;&lt;pre&gt;
593 vlc screen:// --sout \
594 &#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;
595 &lt;/pre&gt;&lt;/blockquote&gt;
596
597 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
598 same IP address:&lt;/p&gt;
599
600 &lt;blockquote&gt;&lt;pre&gt;
601 echo rtsp://192.168.11.4:8080/test.sdp \
602 &gt; /storage/videos/screenstream.m3u
603 &lt;/pre&gt;&lt;/blockquote&gt;
604
605 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
606 as I can tell the IP must be hardcoded for this to work. In other
607 words, if someone elses machine is going to do the steaming, you have
608 to update screenstream.m3u on the Kodi machine and adjust the vlc
609 recipe. To get started, locate the file in Kodi and select the m3u
610 file while the VLC stream is running. The desktop then show up in my
611 big screen. :)&lt;/p&gt;
612
613 &lt;p&gt;When using the same technique to stream a video file with audio,
614 the audio quality is really bad. No idea if the problem is package
615 loss or bad parameters for the transcode. I do not know VLC nor Kodi
616 enough to tell.&lt;/p&gt;
617
618 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
619 succestions and reminded me about an important step. The &quot;screen:&quot;
620 input source is only available once the vlc-plugin-access-extra
621 package is installed on Debian. Without it, you will see this error
622 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
623 for details.&quot; He further found that it is possible to drop some parts
624 of the VLC command line to reduce the amount of hardcoded information.
625 It is also useful to consider using cvlc to avoid having the VLC
626 window in the desktop view. In sum, this give us this command line on
627 the source end
628
629 &lt;blockquote&gt;&lt;pre&gt;
630 cvlc screen:// --sout \
631 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
632 &lt;/pre&gt;&lt;/blockquote&gt;
633
634 &lt;p&gt;and this on the Kodi end&lt;p&gt;
635
636 &lt;blockquote&gt;&lt;pre&gt;
637 echo rtsp://192.168.11.4:8080/ \
638 &gt; /storage/videos/screenstream.m3u
639 &lt;/pre&gt;&lt;/blockquote&gt;
640
641 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
642 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
643 audio quality, so I guess the issue is in the input or transcoding
644 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
645 parameters to use more bandwidth, but it did not make a
646 difference.&lt;/p&gt;
647
648 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
649 gstreamer instead of VLC, and this proved to work great! He also
650 provided me with the trick to get Kodi to use a multicast stream as
651 its source. By using this monstrous oneliner, I can stream my desktop
652 with good video quality in reasonable framerate to the 239.255.0.1
653 multicast address on port 1234:
654
655 &lt;blockquote&gt;&lt;pre&gt;
656 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
657 videoconvert ! queue2 ! \
658 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
659 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
660 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
661 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
662 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
663 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
664 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
665 &lt;/pre&gt;&lt;/blockquote&gt;
666
667 &lt;p&gt;and this on the Kodi end&lt;p&gt;
668
669 &lt;blockquote&gt;&lt;pre&gt;
670 echo udp://@239.255.0.1:1234 \
671 &gt; /storage/videos/screenstream.m3u
672 &lt;/pre&gt;&lt;/blockquote&gt;
673
674 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
675 pick the one you need. This approach will of course lead to trouble
676 if more than one source uses the same multicast port and address.
677 Note the ttl-mc=1 setting, which limit the multicast packages to the
678 local network. If the value is increased, your screen will be
679 broadcasted further, one network &quot;hop&quot; for each increase (read up on
680 multicast to learn more. :)!&lt;/p&gt;
681
682 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
683 could use this VLC command to stream to the same multicast address.
684 The image quality is way better than the rtsp approach, but gstreamer
685 seem to be doing a better job.&lt;/p&gt;
686
687 &lt;blockquote&gt;&lt;pre&gt;
688 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;
689 &lt;/pre&gt;&lt;/blockquote&gt;
690
691 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
692 activities, please send Bitcoin donations to my address
693 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
694 </description>
695 </item>
696
697 <item>
698 <title>What is the most supported MIME type in Debian in 2018?</title>
699 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
701 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
702 <description>&lt;p&gt;Five years ago,
703 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
704 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
705 analysing the desktop files in all packages in the archive. Since
706 then, the DEP-11 AppStream system has been put into production, making
707 the task a lot easier. This made me want to repeat the measurement,
708 to see how much things changed. Here are the new numbers, for
709 unstable only this time:
710
711 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
712
713 &lt;pre&gt;
714 count MIME type
715 ----- -----------------------
716 56 image/jpeg
717 55 image/png
718 49 image/tiff
719 48 image/gif
720 39 image/bmp
721 38 text/plain
722 37 audio/mpeg
723 34 application/ogg
724 33 audio/x-flac
725 32 audio/x-mp3
726 30 audio/x-wav
727 30 audio/x-vorbis+ogg
728 29 image/x-portable-pixmap
729 27 inode/directory
730 27 image/x-portable-bitmap
731 27 audio/x-mpeg
732 26 application/x-ogg
733 25 audio/x-mpegurl
734 25 audio/ogg
735 24 text/html
736 &lt;/pre&gt;
737
738 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
739 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
740 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
741
742 &lt;p&gt;It is interesting to see how image formats have passed text/plain
743 as the most announced supported MIME type. These days, thanks to the
744 AppStream system, if you run into a file format you do not know, and
745 want to figure out which packages support the format, you can find the
746 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
747 look up all packages announcing support for this format in their
748 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
749 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
750 me, want to know which packages support inode/directory, you can get a
751 list like this:&lt;/p&gt;
752
753 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
754 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
755 Package: anjuta
756 Package: audacious
757 Package: baobab
758 Package: cervisia
759 Package: chirp
760 Package: dolphin
761 Package: doublecmd-common
762 Package: easytag
763 Package: enlightenment
764 Package: ephoto
765 Package: filelight
766 Package: gwenview
767 Package: k4dirstat
768 Package: kaffeine
769 Package: kdesvn
770 Package: kid3
771 Package: kid3-qt
772 Package: nautilus
773 Package: nemo
774 Package: pcmanfm
775 Package: pcmanfm-qt
776 Package: qweborf
777 Package: ranger
778 Package: sirikali
779 Package: spacefm
780 Package: spacefm
781 Package: vifm
782 %
783 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
784
785 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
786 format is not yet supported by any package in Debian:&lt;/p&gt;
787
788 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
789 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
790 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
791 %
792 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
793
794 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
795 format:&lt;/p&gt;
796
797 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
798 % appstreamcli what-provides mimetype application/sla|grep Package
799 Package: cura
800 Package: meshlab
801 Package: printrun
802 %
803 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
804
805 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
806
807 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
808 activities, please send Bitcoin donations to my address
809 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
810 </description>
811 </item>
812
813 <item>
814 <title>Debian APT upgrade without enough free space on the disk...</title>
815 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
817 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
818 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
819 for a while, and when I need to update it there is not enough free
820 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
821 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
822 upgrade only some of the packages in one batch, until the amount of
823 packages to download fall below the amount of free space available.
824 Today, I had about 500 packages to upgrade, and after a while I got
825 tired of trying to install chunks of packages manually. I concluded
826 that I did not have the spare hours required to complete the task, and
827 decided to see if I could automate it. I came up with this small
828 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
829
830 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
831 #!/bin/sh
832 #
833 # Upgrade packages when the disk is too full to upgrade every
834 # upgradable package in one lump. Fetching packages to upgrade using
835 # apt, and then installing using dpkg, to avoid changing the package
836 # flag for manual/automatic.
837
838 set -e
839
840 ignore() {
841 if [ &quot;$1&quot; ]; then
842 grep -v &quot;$1&quot;
843 else
844 cat
845 fi
846 }
847
848 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
849 echo &quot;Upgrading $p&quot;
850 apt clean
851 apt install --download-only -y $p
852 for f in /var/cache/apt/archives/*.deb; do
853 if [ -e &quot;$f&quot; ]; then
854 dpkg -i /var/cache/apt/archives/*.deb
855 break
856 fi
857 done
858 done
859 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
860
861 &lt;p&gt;The script will extract the list of packages to upgrade, try to
862 download the packages needed to upgrade one package, install the
863 downloaded packages using dpkg. The idea is to upgrade packages
864 without changing the APT mark for the package (ie the one recording of
865 the package was manually requested or pulled in as a dependency). To
866 use it, simply run it as root from the command line. If it fail, try
867 &#39;apt install -f&#39; to clean up the mess and run the script again. This
868 might happen if the new packages conflict with one of the old
869 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
870
871 &lt;p&gt;It take one option, a package to ignore in the list of packages to
872 upgrade. The option to ignore a package is there to be able to skip
873 the packages that are simply too large to unpack. Today this was
874 &#39;ghc&#39;, but I have run into other large packages causing similar
875 problems earlier (like TeX).&lt;/p&gt;
876
877 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
878 alternative ways to handle this. The &quot;unattended-upgrades
879 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
880 each package to upgrade, and then upgrade them in order, smallest set
881 first. It might be a better option than my above mentioned script.
882 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
883 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
884
885 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
886 activities, please send Bitcoin donations to my address
887 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
888 </description>
889 </item>
890
891 <item>
892 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
893 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
895 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
896 <description>&lt;p&gt;A new version of the
897 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
898 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
899 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
900 useful. It was uploaded the last few days, and the last update will
901 enter testing tomorrow. See the
902 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
903 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
904 was announced 6 days ago. We will try to get it into Debian as
905 well.&lt;/p&gt;
906
907 &lt;p&gt;More information related to 3D printing is available on the
908 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
909 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
910 in Debian.&lt;/p&gt;
911
912 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
913 activities, please send Bitcoin donations to my address
914 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
915 </description>
916 </item>
917
918 <item>
919 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
920 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
921 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
922 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
923 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
924 that the nice and user friendly 3D printer slicer software Cura just
925 entered Debian Unstable. It consist of five packages,
926 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
927 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
928 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
929 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
930 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
931 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
932 two, uranium and cura, entered Unstable yesterday. This should make
933 it easier for Debian users to print on at least the Ultimaker class of
934 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
935 make life easier for at least me. :)&lt;/p&gt;
936
937 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
938 happy to assist him in sponsoring the packages. With the introduction
939 of Cura, Debian is up to three 3D printer slicers at your service,
940 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
941 printer, give it a go. :)&lt;/p&gt;
942
943 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
944 team, flocking together on the
945 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
946 mailing list and the
947 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
948 IRC channel.&lt;/p&gt;
949
950 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
951 version 3.0.3 and then update the entire set of packages to version
952 3.1.0 which showed up the last few days.&lt;/p&gt;
953 </description>
954 </item>
955
956 <item>
957 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
958 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
960 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
961 <description>&lt;p&gt;At my nearby maker space,
962 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
963 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
964 on Windows and MacOS X than Linux, because the software involved had
965 to be manually compiled and set up on Linux while premade packages
966 worked out of the box on Windows and MacOS X. I found this annoying,
967 as the software involved,
968 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
969 and should be trivial to get up and running on Linux if someone took
970 the time to package it for the relevant distributions. I even found
971 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
972 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
973 never resulted in the software showing up in Debian. So a few days
974 ago I offered my help to try to improve the situation.&lt;/p&gt;
975
976 &lt;p&gt;Now I am very happy to see that all the packages required by a
977 working Cura in Debian are uploaded into Debian and waiting in the NEW
978 queue for the ftpmasters to have a look. You can track the progress
979 on
980 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
981 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
982
983 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
984 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
985 queue&lt;/a&gt; while we work up updating the packages to the latest
986 upstream version.&lt;/p&gt;
987
988 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
989 to use and was unable to configure correctly for Ultimaker 2+ in the
990 short time I spent on it, are already in Debian. If you are looking
991 for 3D printer &quot;slicers&quot; and want something already available in
992 Debian, check out
993 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
994 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
995 The latter is a fork of the former.&lt;/p&gt;
996
997 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
998 activities, please send Bitcoin donations to my address
999 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1000 </description>
1001 </item>
1002
1003 <item>
1004 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
1005 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
1006 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
1007 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
1008 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
1009 mobile cell towers. And this radio chatter is available for anyone
1010 with a radio receiver capable of receiving them. Details about the
1011 mobile phones with very good accuracy is of course collected by the
1012 phone companies, but this is not the topic of this blog post. The
1013 mobile phone radio chatter make it possible to figure out when a cell
1014 phone is nearby, as it include the SIM card ID (IMSI). By paying
1015 attention over time, one can see when a phone arrive and when it leave
1016 an area. I believe it would be nice to make this information more
1017 available to the general public, to make more people aware of how
1018 their phones are announcing their whereabouts to anyone that care to
1019 listen.&lt;/p&gt;
1020
1021 &lt;p&gt;I am very happy to report that we managed to get something
1022 visualizing this information up and running for
1023 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
1024 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
1025 library. The solution is based on the
1026 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
1027 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
1028 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
1029 Sone from the Computer Science department of the University of
1030 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
1031 IMSIs) as dots in a web browser graph, with lines to the dot
1032 representing mobile base station it is talking to. It was working in
1033 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
1034
1035 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
1036 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
1037 connected and visualize the visible cell phone towers using an
1038 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
1039 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
1040 grgsm_livemon_headless processes from
1041 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
1042 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
1043
1044 &lt;p&gt;The frequencies to listen to, are identified using a slightly
1045 patched scan-and-livemon (to set the --args values for each receiver),
1046 and the Hopglass data is generated using the
1047 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
1048 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
1049 more than four SDRs working. There is also a geographical map trying
1050 to show the location of the base stations, but I believe their
1051 coordinates are hardcoded to some random location in Germany, I
1052 believe. The code should be replaced with code to look up location in
1053 a text file, a sqlite database or one of the online databases
1054 mentioned in
1055 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
1056 issue for the topic&lt;/a&gt;.
1057
1058 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
1059 </description>
1060 </item>
1061
1062 <item>
1063 <title>Easier recipe to observe the cell phones around you</title>
1064 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
1065 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
1066 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
1067 <description>&lt;p&gt;A little more than a month ago I wrote
1068 &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
1069 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1070 to nearby mobile phone base stations using Debian GNU/Linux and a
1071 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
1072 the location of people and equipment (like cars and trains) with an
1073 accuracy of a few kilometer. Since then we have worked to make the
1074 procedure even simpler, and it is now possible to do this without any
1075 manual frequency tuning and without building your own packages.&lt;/p&gt;
1076
1077 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
1078 package is now included in Debian testing and unstable, and the
1079 IMSI-catcher code no longer require root access to fetch and decode
1080 the GSM data collected using gr-gsm.&lt;/p&gt;
1081
1082 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
1083 clone of two python scripts:&lt;/p&gt;
1084
1085 &lt;ol&gt;
1086
1087 &lt;li&gt;Start with a Debian machine running the Buster version (aka
1088 testing).&lt;/li&gt;
1089
1090 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
1091 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
1092
1093 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
1094 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
1095
1096 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
1097
1098 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1099 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
1100 stations and start listening for GSM packages on one of them.&lt;/li&gt;
1101
1102 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1103 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
1104
1105 &lt;/ol&gt;
1106
1107 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
1108 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
1109 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
1110 work with RTL 8232 and other similar USB radio receivers you can get
1111 very cheaply
1112 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
1113 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
1114 and only use HackRF for fetching GSM data.&lt;/p&gt;
1115
1116 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
1117 frequencies at the time, so if you are going to track and count every
1118 cell phone around you, you need to listen to all the frequencies used.
1119 To listen to several frequencies, use the --numrecv argument to
1120 scan-and-livemon to use several receivers. Further, I am not sure if
1121 phones using 3G or 4G will show as talking GSM to base stations, so
1122 this approach might not see all phones around you. I typically see
1123 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
1124
1125 &lt;p&gt;I&#39;ve tried to run the scanner on a
1126 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
1127 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
1128 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
1129 stdout, I am told there it is caused by a buffer overflow between the
1130 radio and GNU Radio, caused by the program being unable to read the
1131 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
1132 where you started scan-and-livemon, you need a give the process more
1133 CPU power. Perhaps someone are able to optimize the code to a point
1134 where it become possible to set up RPi3 based GSM sniffers? I tried
1135 using Raspbian instead of Debian, but there seem to be something wrong
1136 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
1137 </description>
1138 </item>
1139
1140 <item>
1141 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
1142 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
1143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
1144 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
1145 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
1146 web based ICT news magazine digi.no on
1147 &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
1148 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
1149 DVB-T software defined radios. The article refered to instructions
1150 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
1151 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;
1152
1153 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
1154 bypass apt), use pip to install pybombs (to bypass both apt and pip),
1155 and the ask pybombs to fetch and build everything you need from
1156 scratch. I wanted to see if I could do the same on the most recent
1157 Debian packages, but this did not work because pybombs tried to build
1158 stuff that no longer build with the most recent openssl library or
1159 some other version skew problem. While trying to get this recipe
1160 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
1161 and the only piece of software dependency missing in Debian was the
1162 gr-gsm package. I also found out that the lead upstream developer of
1163 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
1164 Debian packages provided in an Ubuntu PPA repository. All I needed to
1165 do was to dget the Debian source package and built it.&lt;/p&gt;
1166
1167 &lt;p&gt;The IMSI collector is a python script listening for packages on the
1168 loopback network device and printing to the terminal some specific GSM
1169 packages with IMSI numbers in them. The code is fairly short and easy
1170 to understand. The reason this work is because gr-gsm include a tool
1171 to read GSM data from a software defined radio like a DVB-T USB stick
1172 and other software defined radios, decode them and inject them into a
1173 network device on your Linux machine (using the loopback device by
1174 default). This proved to work just fine, and I&#39;ve been testing the
1175 collector for a few days now.&lt;/p&gt;
1176
1177 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
1178
1179 &lt;ol&gt;
1180
1181 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
1182
1183 &lt;li&gt;build and install the gr-gsm package available from
1184 &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;
1185
1186 &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;
1187
1188 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
1189 where it was started is filled with a stream of text (meaning you
1190 found a GSM station).&lt;/li&gt;
1191
1192 &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;
1193
1194 &lt;/ol&gt;
1195
1196 &lt;p&gt;To make it even easier in the future to get this sniffer up and
1197 running, I decided to package
1198 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
1199 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
1200 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
1201 Luckily the gnuradio maintainer has promised to help me, as I do not
1202 know much about gnuradio stuff yet.&lt;/p&gt;
1203
1204 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
1205 commercial tools like
1206 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
1207 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
1208 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
1209 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
1210 more people realise how their whereabouts when carrying a cell phone
1211 is easily tracked. Seeing the data flow on the screen, realizing that
1212 I live close to a police station and knowing that the police is also
1213 wearing cell phones, I wonder how hard it would be for criminals to
1214 track the position of the police officers to discover when there are
1215 police near by, or for foreign military forces to track the location
1216 of the Norwegian military forces, or for anyone to track the location
1217 of government officials...&lt;/p&gt;
1218
1219 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
1220 script mentioned above is only a fraction of the data broadcasted on
1221 the GSM network. It will only collect one frequency at the time,
1222 while a typical phone will be using several frequencies, and not all
1223 phones will be using the frequencies tracked by the grgsm_livemod
1224 program. Also, there is a lot of radio chatter being ignored by the
1225 simple_IMSI-catcher script, which would be collected by extending the
1226 parser code. I wonder if gr-gsm can be set up to listen to more than
1227 one frequency?&lt;/p&gt;
1228 </description>
1229 </item>
1230
1231 <item>
1232 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
1233 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
1234 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
1235 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
1236 <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;
1237
1238 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
1239 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1240 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
1241 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
1242 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
1243 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
1244 price. The book is also available for download in electronic form as
1245 PDF, EPUB and Mobipocket, as can be
1246 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
1247 as a web page&lt;/a&gt;.&lt;/p&gt;
1248
1249 &lt;p&gt;This is the second book I publish (the first was the book
1250 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
1251 in
1252 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
1253 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
1254 and
1255 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
1256 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
1257 project. I hope
1258 &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
1259 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
1260 </description>
1261 </item>
1262
1263 <item>
1264 <title>Når nynorskoversettelsen svikter til eksamen...</title>
1265 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
1266 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
1267 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
1268 <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
1269 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
1270 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
1271 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
1272 på om den fri oversetterløsningen
1273 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
1274 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
1275
1276 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
1277
1278 &lt;blockquote&gt;
1279 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1280 rolle og muligheter til å håndtere internasjonale utfordringer, som
1281 for eksempel flykningekrisen.&lt;/p&gt;
1282
1283 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1284 på temaet:&lt;/p&gt;
1285 &lt;ol&gt;
1286 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
1287 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
1288 &lt;/ol&gt;
1289
1290 &lt;/blockquote&gt;
1291
1292 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
1293
1294 &lt;blockquote&gt;
1295 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1296 andre aktørar og høve til å handtera internasjonale utfordringar, som
1297 til dømes *flykningekrisen.&lt;/p&gt;
1298
1299 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
1300 temaet:&lt;/p&gt;
1301
1302 &lt;ol&gt;
1303 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
1304 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
1305 &lt;/ol&gt;
1306
1307 &lt;/blockquote&gt;
1308
1309 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
1310 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1311 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1312 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
1313 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
1314 det er kanskje flisespikking. Det understreker vel bare at det alltid
1315 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
1316 </description>
1317 </item>
1318
1319 <item>
1320 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
1321 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
1322 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
1323 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
1324 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
1325 computers at the time, I often needed a way to detect if the machine
1326 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
1327 file or directory affected by the hang, the process (and possibly the
1328 shell) will hang too. So you want to be able to detect this without
1329 risking the detection process getting stuck too. It has not been
1330 obvious how to do this. When the hang has lasted a while, it is
1331 possible to find messages like these in dmesg:&lt;/p&gt;
1332
1333 &lt;p&gt;&lt;blockquote&gt;
1334 nfs: server nfsserver not responding, still trying
1335 &lt;br&gt;nfs: server nfsserver OK
1336 &lt;/blockquote&gt;&lt;/p&gt;
1337
1338 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
1339 be sure looking in dmesg is going to work. If there are lots of other
1340 messages in dmesg the lines might have rotated out of site before they
1341 are noticed.&lt;/p&gt;
1342
1343 &lt;p&gt;While reading through the nfs client implementation in linux kernel
1344 code, I came across some statistics that seem to give a way to detect
1345 it. The om_timeouts sunrpc value in the kernel will increase every
1346 time the above log entry is inserted into dmesg. And after digging a
1347 bit further, I discovered that this value show up in
1348 /proc/self/mountstats on Linux.&lt;/p&gt;
1349
1350 &lt;p&gt;The mountstats content seem to be shared between files using the
1351 same file system context, so it is enough to check one of the
1352 mountstats files to get the state of the mount point for the machine.
1353 I assume this will not show lazy umounted NFS points, nor NFS mount
1354 points in a different process context (ie with a different filesystem
1355 view), but that does not worry me.&lt;/p&gt;
1356
1357 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
1358
1359 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1360 [...]
1361 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1362 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
1363 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
1364 age: 7863311
1365 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
1366 sec: flavor=1,pseudoflavor=1
1367 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
1368 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1369 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
1370 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1371 per-op statistics
1372 NULL: 0 0 0 0 0 0 0 0
1373 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1374 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
1375 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1376 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1377 READLINK: 125 125 0 20472 18620 0 1112 1118
1378 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1379 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1380 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
1381 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
1382 SYMLINK: 903 903 0 233428 245488 6 5865 5917
1383 MKNOD: 80 80 0 20148 21760 0 299 304
1384 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
1385 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
1386 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
1387 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
1388 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1389 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1390 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
1391 FSINFO: 2 2 0 232 328 0 1 1
1392 PATHCONF: 1 1 0 116 140 0 0 0
1393 COMMIT: 0 0 0 0 0 0 0 0
1394
1395 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1396 [...]
1397 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1398
1399 &lt;p&gt;The key number to look at is the third number in the per-op list.
1400 It is the number of NFS timeouts experiences per file system
1401 operation. Here 22 write timeouts and 5 access timeouts. If these
1402 numbers are increasing, I believe the machine is experiencing NFS
1403 hang. Unfortunately the timeout value do not start to increase right
1404 away. The NFS operations need to time out first, and this can take a
1405 while. The exact timeout value depend on the setup. For example the
1406 defaults for TCP and UDP mount points are quite different, and the
1407 timeout value is affected by the soft, hard, timeo and retrans NFS
1408 mount options.&lt;/p&gt;
1409
1410 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
1411 Enterprise Linux for getting the timeout count is to peek in /proc/.
1412 But according to
1413 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
1414 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
1415 command can be used to get these timeout values. But this do not work
1416 on Linux, as far as I can tell. I
1417 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
1418 but have not seen any replies yet.&lt;/p&gt;
1419
1420 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
1421 experiencing NFS hangs? Is there a way to detect which processes are
1422 affected? Is there a way to get the NFS mount going quickly once the
1423 network problem causing the NFS hang has been cleared? I would very
1424 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
1425 </description>
1426 </item>
1427
1428 <item>
1429 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
1430 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
1431 <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>
1432 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
1433 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
1434 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1435 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
1436 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1437 we are working on the proof reading to ensure consistent language and
1438 use of correct computer science terms. The plan is to make the book
1439 available on paper, as well as in electronic form. For that to
1440 happen, the proof reading must be completed and all the figures need
1441 to be translated. If you want to help out, get in touch.&lt;/p&gt;
1442
1443 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
1444
1445 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
1446 pages) of the book created every morning is available for
1447 proofreading. If you find any errors, please
1448 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
1449 Weblate and correct the error&lt;/a&gt;. The
1450 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
1451 of the translation including figures&lt;/a&gt; is a useful source for those
1452 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
1453 </description>
1454 </item>
1455
1456 <item>
1457 <title>Unlimited randomness with the ChaosKey?</title>
1458 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
1459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
1460 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
1461 <description>&lt;p&gt;A few days ago I ordered a small batch of
1462 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
1463 USB dongle for generating entropy created by Bdale Garbee and Keith
1464 Packard. Yesterday it arrived, and I am very happy to report that it
1465 work great! According to its designers, to get it to work out of the
1466 box, you need the Linux kernel version 4.1 or later. I tested on a
1467 Debian Stretch machine (kernel version 4.9), and there it worked just
1468 fine, increasing the available entropy very quickly. I wrote a small
1469 test oneliner to test. It first print the current entropy level,
1470 drain /dev/random, and then print the entropy level for five seconds.
1471 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
1472
1473 &lt;blockquote&gt;&lt;pre&gt;
1474 % cat /proc/sys/kernel/random/entropy_avail; \
1475 dd bs=1M if=/dev/random of=/dev/null count=1; \
1476 for n in $(seq 1 5); do \
1477 cat /proc/sys/kernel/random/entropy_avail; \
1478 sleep 1; \
1479 done
1480 300
1481 0+1 oppføringer inn
1482 0+1 oppføringer ut
1483 28 byte kopiert, 0,000264565 s, 106 kB/s
1484 4
1485 8
1486 12
1487 17
1488 21
1489 %
1490 &lt;/pre&gt;&lt;/blockquote&gt;
1491
1492 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
1493 application requiring random bits (like a HTTPS enabled web server)
1494 will halt and wait for more entrpy. And here is the situation with
1495 the ChaosKey inserted:&lt;/p&gt;
1496
1497 &lt;blockquote&gt;&lt;pre&gt;
1498 % cat /proc/sys/kernel/random/entropy_avail; \
1499 dd bs=1M if=/dev/random of=/dev/null count=1; \
1500 for n in $(seq 1 5); do \
1501 cat /proc/sys/kernel/random/entropy_avail; \
1502 sleep 1; \
1503 done
1504 1079
1505 0+1 oppføringer inn
1506 0+1 oppføringer ut
1507 104 byte kopiert, 0,000487647 s, 213 kB/s
1508 433
1509 1028
1510 1031
1511 1035
1512 1038
1513 %
1514 &lt;/pre&gt;&lt;/blockquote&gt;
1515
1516 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
1517 someone want to buy one here in Norway. :)&lt;/p&gt;
1518
1519 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
1520 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
1521 recording illuminating&lt;/a&gt;. It explains exactly what the source of
1522 randomness is, if you are unable to spot it from the schema drawing
1523 available from the ChaosKey web site linked at the start of this blog
1524 post.&lt;/p&gt;
1525 </description>
1526 </item>
1527
1528 <item>
1529 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
1530 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
1531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
1532 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
1533 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
1534 web servers, and who own the network equipment it is flowing through?
1535 It is possible to get a glimpse of this from using traceroute, but it
1536 is hard to find all the details. Many years ago, I wrote a system to
1537 map the Norwegian Internet (trying to figure out if our plans for a
1538 network game service would get low enough latency, and who we needed
1539 to talk to about setting up game servers close to the users. Back
1540 then I used traceroute output from many locations (I asked my friends
1541 to run a script and send me their traceroute output) to create the
1542 graph and the map. The output from traceroute typically look like
1543 this:
1544
1545 &lt;p&gt;&lt;pre&gt;
1546 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
1547 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
1548 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
1549 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
1550 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
1551 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
1552 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
1553 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
1554 8 * * *
1555 9 * * *
1556 [...]
1557 &lt;/pre&gt;&lt;/p&gt;
1558
1559 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
1560 network equipment involved in getting the data traffic from me to the
1561 www.stortinget.no server, and how long it took in milliseconds for a
1562 package to reach the equipment and return to me. Three packages are
1563 sent, and some times the packages do not follow the same path. This
1564 is shown for hop 5, where three different IP addresses replied to the
1565 traceroute request.&lt;/p&gt;
1566
1567 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
1568 implementations I use are traceroute (using ICMP packages) mtr (can do
1569 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1570 traceroute and a lot of other capabilities). All of them are easily
1571 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
1572
1573 &lt;p&gt;This time around, I wanted to know the geographic location of
1574 different route points, to visualize how visiting a web page spread
1575 information about the visit to a lot of servers around the globe. The
1576 background is that a web site today often will ask the browser to get
1577 from many servers the parts (for example HTML, JSON, fonts,
1578 JavaScript, CSS, video) required to display the content. This will
1579 leak information about the visit to those controlling these servers
1580 and anyone able to peek at the data traffic passing by (like your ISP,
1581 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
1582
1583 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
1584 www.stortinget.no. It is read daily by all members of parliament and
1585 their staff, as well as political journalists, activits and many other
1586 citizens of Norway. A visit to the www.stortinget.no web site will
1587 ask your browser to contact 8 other servers: ajax.googleapis.com,
1588 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1589 stats.g.doubleclick.net, www.google-analytics.com,
1590 www.googletagmanager.com and www.netigate.se. I extracted this by
1591 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
1592 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1593 render the page (in HAR format using
1594 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
1595 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
1596 to do this). My goal is to visualize network traces to all IP
1597 addresses behind these DNS names, do show where visitors personal
1598 information is spread when visiting the page.&lt;/p&gt;
1599
1600 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
1601 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;
1602
1603 &lt;p&gt;When I had a look around for options, I could not find any good
1604 free software tools to do this, and decided I needed my own traceroute
1605 wrapper outputting KML based on locations looked up using GeoIP. KML
1606 is easy to work with and easy to generate, and understood by several
1607 of the GIS tools I have available. I got good help from by NUUG
1608 colleague Anders Einar with this, and the result can be seen in
1609 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
1610 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
1611 free GeoIP databases I could find (and the for-pay databases my
1612 friends had access to) is not up to the task. The IP addresses of
1613 central Internet infrastructure would typically be placed near the
1614 controlling companies main office, and not where the router is really
1615 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
1616 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
1617
1618 &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
1619 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;
1620
1621 &lt;p&gt;I also had a look at the visual traceroute graph created by
1622 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
1623 showing IP network ownership (aka AS owner) for the IP address in
1624 question.
1625 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
1626 graph display a lot of useful information about the traceroute in SVG
1627 format&lt;/a&gt;, and give a good indication on who control the network
1628 equipment involved, but it do not include geolocation. This graph
1629 make it possible to see the information is made available at least for
1630 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1631 3 Communications and NetDNA.&lt;/p&gt;
1632
1633 &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
1634 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;
1635
1636 &lt;p&gt;In the process, I came across the
1637 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
1638 Salim Gasmi. Its methology of combining guesses based on DNS names,
1639 various location databases and finally use latecy times to rule out
1640 candidate locations seemed to do a very good job of guessing correct
1641 geolocation. But it could only do one trace at the time, did not have
1642 a sensor in Norway and did not make the geolocations easily available
1643 for postprocessing. So I contacted the developer and asked if he
1644 would be willing to share the code (he refused until he had time to
1645 clean it up), but he was interested in providing the geolocations in a
1646 machine readable format, and willing to set up a sensor in Norway. So
1647 since yesterday, it is possible to run traces from Norway in this
1648 service thanks to a sensor node set up by
1649 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
1650 trace in KML format for further processing.&lt;/p&gt;
1651
1652 &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
1653 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;
1654
1655 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
1656 Denmark, Germany, Holland and Ireland. Plenty of places where the
1657 Snowden confirmations verified the traffic is read by various actors
1658 without your best interest as their top priority.&lt;/p&gt;
1659
1660 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
1661 over all the hosts behind the urls imported by www.stortinget.no and
1662 ask for the KML file from GeoTraceroute, and create a combined KML
1663 file with all the traces (unfortunately only one of the IP addresses
1664 behind the DNS name is traced this time. To get them all, one would
1665 have to request traces using IP number instead of DNS names from
1666 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
1667
1668 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
1669 the IP traffic moves and who control the boxes involved in moving it.
1670 And every time the link crosses for example the Swedish border, we can
1671 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1672 Britain and NSA in USA and cables around the globe. (Hm, what should
1673 we tell them? :) Keep that in mind if you ever send anything
1674 unencrypted over the Internet.&lt;/p&gt;
1675
1676 &lt;p&gt;PS: KML files are drawn using
1677 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
1678 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
1679 Marble. There are heaps of other options too.&lt;/p&gt;
1680
1681 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1682 activities, please send Bitcoin donations to my address
1683 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1684 </description>
1685 </item>
1686
1687 <item>
1688 <title>Appstream just learned how to map hardware to packages too!</title>
1689 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
1690 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
1691 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
1692 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
1693 readers probably know, I have been working on the
1694 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
1695 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
1696 it easier for users to figure out what to install to get a given piece
1697 of hardware to work in Debian, and a key part of this system is a way
1698 to map hardware to packages. Isenkram have its own mapping database,
1699 and also uses data provided by each package using the AppStream
1700 metadata format. And today,
1701 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
1702 Debian learned to look up hardware the same way Isenkram is doing it,
1703 ie using fnmatch():&lt;/p&gt;
1704
1705 &lt;p&gt;&lt;pre&gt;
1706 % appstreamcli what-provides modalias \
1707 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1708 Identifier: pymissile [generic]
1709 Name: pymissile
1710 Summary: Control original Striker USB Missile Launcher
1711 Package: pymissile
1712 % appstreamcli what-provides modalias usb:v0694p0002d0000
1713 Identifier: libnxt [generic]
1714 Name: libnxt
1715 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1716 Package: libnxt
1717 ---
1718 Identifier: t2n [generic]
1719 Name: t2n
1720 Summary: Simple command-line tool for Lego NXT
1721 Package: t2n
1722 ---
1723 Identifier: python-nxt [generic]
1724 Name: python-nxt
1725 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1726 Package: python-nxt
1727 ---
1728 Identifier: nbc [generic]
1729 Name: nbc
1730 Summary: C compiler for LEGO Mindstorms NXT bricks
1731 Package: nbc
1732 %
1733 &lt;/pre&gt;&lt;/p&gt;
1734
1735 &lt;p&gt;A similar query can be done using the combined AppStream and
1736 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
1737
1738 &lt;p&gt;&lt;pre&gt;
1739 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1740 pymissile
1741 % isenkram-lookup usb:v0694p0002d0000
1742 libnxt
1743 nbc
1744 python-nxt
1745 t2n
1746 %
1747 &lt;/pre&gt;&lt;/p&gt;
1748
1749 &lt;p&gt;You can find modalias values relevant for your machine using
1750 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
1751
1752 &lt;p&gt;If you want to make this system a success and help Debian users
1753 make the most of the hardware they have, please
1754 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
1755 AppStream metadata for your package following the guidelines&lt;/a&gt;
1756 documented in the wiki. So far only 11 packages provide such
1757 information, among the several hundred hardware specific packages in
1758 Debian. The Isenkram database on the other hand contain 101 packages,
1759 mostly related to USB dongles. Most of the packages with hardware
1760 mapping in AppStream are LEGO Mindstorms related, because I have, as
1761 part of my involvement in
1762 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
1763 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
1764 complete set of packages in Debian for that particular hardware. The
1765 team also got a nice Christmas present today. The
1766 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
1767 package&lt;/a&gt; made it into Debian. With this package in place, it is
1768 now possible to use the LEGO Mindstorms NXT unit with only free
1769 software, as the nxt-firmware package contain the source and firmware
1770 binaries for the NXT brick.&lt;/p&gt;
1771
1772 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1773 activities, please send Bitcoin donations to my address
1774 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1775 </description>
1776 </item>
1777
1778 <item>
1779 <title>Isenkram updated with a lot more hardware-package mappings</title>
1780 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
1781 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
1782 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
1783 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1784 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
1785 and install packages to get your hardware dongles to work, is still
1786 going strong. It is a system to look up the hardware present on or
1787 connected to the current system, and map the hardware to Debian
1788 packages. It can either be done using the tools in isenkram-cli or
1789 using the user space daemon in the isenkram package. The latter will
1790 notify you, when inserting new hardware, about what packages to
1791 install to get the dongle working. It will even provide a button to
1792 click on to ask packagekit to install the packages.&lt;/p&gt;
1793
1794 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
1795
1796 &lt;p&gt;&lt;pre&gt;
1797 % isenkram-lookup
1798 bluez
1799 cheese
1800 ethtool
1801 fprintd
1802 fprintd-demo
1803 gkrellm-thinkbat
1804 hdapsd
1805 libpam-fprintd
1806 pidgin-blinklight
1807 thinkfan
1808 tlp
1809 tp-smapi-dkms
1810 tp-smapi-source
1811 tpb
1812 %
1813 &lt;/pre&gt;&lt;/p&gt;
1814
1815 &lt;p&gt;It can also list the firware package providing firmware requested
1816 by the load kernel modules, which in my case is an empty list because
1817 I have all the firmware my machine need:
1818
1819 &lt;p&gt;&lt;pre&gt;
1820 % /usr/sbin/isenkram-autoinstall-firmware -l
1821 info: did not find any firmware files requested by loaded kernel modules. exiting
1822 %
1823 &lt;/pre&gt;&lt;/p&gt;
1824
1825 &lt;p&gt;The last few days I had a look at several of the around 250
1826 packages in Debian with udev rules. These seem like good candidates
1827 to install when a given hardware dongle is inserted, and I found
1828 several that should be proposed by isenkram. I have not had time to
1829 check all of them, but am happy to report that now there are 97
1830 packages packages mapped to hardware by Isenkram. 11 of these
1831 packages provide hardware mapping using AppStream, while the rest are
1832 listed in the modaliases file provided in isenkram.&lt;/p&gt;
1833
1834 &lt;p&gt;These are the packages with hardware mappings at the moment. The
1835 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
1836 support using AppStream, for everyone to use:&lt;/p&gt;
1837
1838 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
1839 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
1840 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
1841 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
1842 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
1843 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1844 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
1845 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1846 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1847 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1848 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
1849 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1850 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
1851 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1852 pcscd, pidgin-blinklight, printer-driver-splix,
1853 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
1854 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1855 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1856 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1857 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1858 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1859 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1860 xserver-xorg-video-vmware, yubikey-personalization and
1861 zd1211-firmware&lt;/p&gt;
1862
1863 &lt;p&gt;If you know of other packages, please let me know with a wishlist
1864 bug report against the isenkram-cli package, and ask the package
1865 maintainer to
1866 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
1867 metadata according to the guidelines&lt;/a&gt; to provide the information
1868 for everyone. In time, I hope to get rid of the isenkram specific
1869 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
1870
1871 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
1872 much hardware, and suggest that the package with with any ethernet
1873 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
1874 the details. I hope the maintainer find time to address it soon. In
1875 the mean time I provide an override in isenkram.&lt;/p&gt;
1876 </description>
1877 </item>
1878
1879 <item>
1880 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
1881 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1882 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1883 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1884 <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;
1885
1886 &lt;p&gt;In my early years, I played
1887 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1888 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1889 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1890 original Elite game was available on Commodore 64 and the IBM PC
1891 edition I played had a 64 KB executable. I am still impressed today
1892 that the authors managed to squeeze both a 3D engine and details about
1893 more than 2000 planet systems across 7 galaxies into a binary so
1894 small.&lt;/p&gt;
1895
1896 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1897 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1898 really have time to test it properly until a few days ago. It was
1899 great to discover that my old knowledge about trading routes were
1900 still valid. But my fighting and flying abilities were gone, so I had
1901 to retrain to be able to dock on a space station. And I am still not
1902 able to make much resistance when I am attacked by pirates, so I
1903 bougth and mounted the most powerful laser in the rear to be able to
1904 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1905
1906 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1907 everything on my own, and I had long lists of prices seen on different
1908 planets to be able to decide where to trade what. This time I had the
1909 advantages of the
1910 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1911 where information about each planet is easily available with common
1912 price ranges and suggested trading routes. This improved my ability
1913 to earn money and I have been able to earn enough to buy a lot of
1914 useful equipent in a few days. I believe I originally played for
1915 months before I could get a docking computer, while now I could get it
1916 after less then a week.&lt;/p&gt;
1917
1918 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1919 space, you should try out Oolite. It is available for Linux, MacOSX
1920 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1921
1922 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1923 activities, please send Bitcoin donations to my address
1924 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1925 </description>
1926 </item>
1927
1928 <item>
1929 <title>Quicker Debian installations using eatmydata</title>
1930 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1932 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1933 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1934 installation system, observing how using
1935 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1936 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1937 speedup around 20-40 percent for Debian Edu, where we install around
1938 1000 packages from within the installer. The eatmydata package
1939 provide a way to disable/delay file system flushing. This is a bit
1940 risky in the general case, as files that should be stored on disk will
1941 stay only in memory a bit longer than expected, causing problems if a
1942 machine crashes at an inconvenient time. But for an installation, if
1943 the machine crashes during installation the process is normally
1944 restarted, and avoiding disk operations as much as possible to speed
1945 up the process make perfect sense.
1946
1947 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1948 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1949 but did not have time to push it any further. But a few months ago I
1950 picked it up again and worked with the libeatmydata package maintainer
1951 Mattia Rizzolo to make it easier for everyone to get this installation
1952 speedup in Debian. Thanks to our cooperation There is now an
1953 eatmydata-udeb package in Debian testing and unstable, and simply
1954 enabling/installing it in debian-installer (d-i) is enough to get the
1955 quicker installations. It can be enabled using preseeding. The
1956 following untested kernel argument should do the trick:&lt;/p&gt;
1957
1958 &lt;blockquote&gt;&lt;pre&gt;
1959 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1960 &lt;/pre&gt;&lt;/blockquote&gt;
1961
1962 &lt;p&gt;This should ask d-i to install the package inside the d-i
1963 environment early in the installation sequence. Having it installed
1964 in d-i in turn will make sure the relevant scripts are called just
1965 after debootstrap filled /target/ with the freshly installed Debian
1966 system to configure apt to run dpkg with eatmydata. This is enough to
1967 speed up the installation process. There is a proposal to
1968 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1969 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1970 tested its impact.&lt;/p&gt;
1971
1972 </description>
1973 </item>
1974
1975 <item>
1976 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1977 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1978 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1979 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1980 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1981 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1982 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1983 elever over det ganske land skal levere inn hvert år. Det mange ikke
1984 vet er at selv om de kommersielle alternativene
1985 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1986 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1987 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1988 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1989 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1990 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1991 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1992 nynorsk, og få den automatoversatt til det andre skriftspråket.
1993 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1994 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1995 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1996 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1997 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1998 teksten din i webskjemaet der.
1999
2000 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
2001 teknologien kan du enten installere pakken
2002 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
2003 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
2004 api.apertium.org. Se
2005 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
2006 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
2007 denne teksten som ble skrevet på bokmål over maskinoversatt til
2008 nynorsk.&lt;/p&gt;
2009
2010 &lt;hr/&gt;
2011
2012 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
2013 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
2014 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
2015 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
2016 veit er at sjølv om dei kommersielle alternativa
2017 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
2018 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
2019 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
2020 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
2021 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
2022 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
2023 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
2024 nynorsk, og få den *automatoversatt til det andre skriftspråket.
2025 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
2026 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
2027 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
2028 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
2029 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
2030 teksta di i *webskjemaet der.
2031
2032 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
2033 teknologien kan du anten installera pakken
2034 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
2035 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
2036 *api.*apertium.org. Sjå
2037 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
2038 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
2039 for denne teksta som vart skreva på bokmål over *maskinoversatt til
2040 nynorsk.&lt;/p&gt;
2041 </description>
2042 </item>
2043
2044 <item>
2045 <title>Coz profiler for multi-threaded software is now in Debian</title>
2046 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
2047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
2048 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
2049 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
2050 profiler able to run benchmarking experiments on the instrumented
2051 multi-threaded program, finally
2052 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
2053 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
2054 months since
2055 &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
2056 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
2057 it suitable for Debian. There are still issues with clang
2058 compatibility, inline assembly only working x86 and minimized
2059 JavaScript libraries.&lt;/p&gt;
2060
2061 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
2062
2063 &lt;p&gt;&lt;blockquote&gt;
2064 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
2065 &lt;/blockquote&gt;&lt;/p&gt;
2066
2067 &lt;p&gt;This will produce a profile.coz file in the current working
2068 directory with the profiling information. This is then given to a
2069 JavaScript application provided in the package and available from
2070 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
2071 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
2072
2073 &lt;p&gt;&lt;blockquote&gt;
2074 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
2075 &lt;/blockquote&gt;&lt;/p&gt;
2076
2077 &lt;p&gt;See the project home page and the
2078 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
2079 ;login: article on Coz&lt;/a&gt; for more information on how it is
2080 working.&lt;/p&gt;
2081 </description>
2082 </item>
2083
2084 <item>
2085 <title>My own self balancing Lego Segway</title>
2086 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
2087 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
2088 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
2089 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
2090 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
2091 present. It had been on my wishlist for a while, because I wanted to
2092 build a Segway like balancing lego robot. I had already built
2093 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
2094 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
2095 NXT kit as the balance sensor, but it was not working very well. It
2096 could balance for a while, but was very sensitive to the light
2097 condition in the room and the reflective properties of the surface and
2098 would fall over after a short while. I wanted something more robust,
2099 and had
2100 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
2101 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
2102 wishlist for some years before it suddenly showed up as a gift from my
2103 loved ones. :)&lt;/p&gt;
2104
2105 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
2106 since then. But that changed some days ago, when I was searching for
2107 lego segway information and came across a recipe from HiTechnic for
2108 building
2109 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
2110 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
2111 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
2112 code&lt;/a&gt; was included, so it was just a question of putting it all
2113 together. And thanks to the great work of many Debian developers, the
2114 compiler needed to build the source for the NXT is already included in
2115 Debian, so I was read to go in less than an hour. The resulting robot
2116 do not look very impressive in its simplicity:&lt;/p&gt;
2117
2118 &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;
2119
2120 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
2121 design from HiTechnic, I had to comment out the last task
2122 (taskControl). I simply placed /* and */ around it get the program
2123 working without that sensor present. Now it balances just fine until
2124 the battery status run low:&lt;/p&gt;
2125
2126 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
2127 &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;
2128 &lt;/video&gt;&lt;/p&gt;
2129
2130 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
2131 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
2132
2133 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
2134 they need to work with LEGO in Debian and all our derivative
2135 distributions like Ubuntu, check out
2136 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
2137 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
2138 RCX and NXT controller (no EV3), and would like to make sure the
2139 Debian tools needed to program the systems I own work as they
2140 should.&lt;/p&gt;
2141 </description>
2142 </item>
2143
2144 <item>
2145 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
2146 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
2147 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
2148 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
2149 <description>&lt;p&gt;In July
2150 &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
2151 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
2152 the ability to receive SMS messages (aka without a cell phone). It is
2153 time to share some experiences and provide an updated setup.&lt;/p&gt;
2154
2155 &lt;p&gt;The Signal app have worked fine for several months now, and I use
2156 it regularly to chat with my loved ones. I had a major snag at the
2157 end of my summer vacation, when the the app completely forgot my
2158 setup, identity and keys. The reason behind this major mess was
2159 running out of disk space. To avoid that ever happening again I have
2160 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
2161 roll back to an earlier version if the files are wiped by mistake. I
2162 had to use it once after introducing the git backup. When rolling
2163 back to an earlier version, one need to use the &#39;reset session&#39; option
2164 in Signal to get going, and notify the people you talk with about the
2165 problem. I assume there is some sequence number tracking in the
2166 protocol to detect rollback attacks. The git repository is rather big
2167 (674 MiB so far), but I have not tried to figure out if some of the
2168 content can be added to a .gitignore file due to lack of spare
2169 time.&lt;/p&gt;
2170
2171 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
2172 make it impossible to send messages using Signal. I could still
2173 receive them, but had to patch the code with a new timestamp to send.
2174 I believe the timeout is added by the developers to force people to
2175 upgrade to the latest version of the app, even when there is no
2176 protocol changes, to reduce the version skew among the user base and
2177 thus try to keep the number of support requests down.&lt;/p&gt;
2178
2179 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
2180 making the old patch fail to apply cleanly. Below is an updated
2181 patch, including the shell wrapper I use to start Signal. The
2182 original version required a new user to locate the JavaScript console
2183 and call a function from there. I got help from a friend with more
2184 JavaScript knowledge than me to modify the code to provide a GUI
2185 button instead. This mean that to get started you just need to run
2186 the wrapper and click the &#39;Register without mobile phone&#39; to get going
2187 now. I&#39;ve also modified the timeout code to always set it to 90 days
2188 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
2189
2190 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
2191
2192 &lt;ol&gt;
2193
2194 &lt;li&gt;First, install required packages to get the source code and the
2195 browser you need. Signal only work with Chrome/Chromium, as far as I
2196 know, so you need to install it.
2197
2198 &lt;pre&gt;
2199 apt install git tor chromium
2200 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2201 &lt;/pre&gt;&lt;/li&gt;
2202
2203 &lt;li&gt;Modify the source code using command listed in the the patch
2204 block below.&lt;/li&gt;
2205
2206 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
2207 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
2208
2209 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
2210 number you can receive calls to the next minute, receive the
2211 verification code and enter it into the form field and press
2212 &#39;Register&#39;. Note, the phone number you use will be user Signal
2213 username, ie the way others can find you on Signal.&lt;/li&gt;
2214
2215 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
2216 not show up in the contact list until you restart Signal, and there is
2217 no way to assign names to Contacts. There is also no way to create or
2218 update chat groups. I suspect this is because the web app do not have
2219 a associated contact database.&lt;/li&gt;
2220
2221 &lt;/ol&gt;
2222
2223 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
2224 main author moxie0 reject federation and accept dependencies to major
2225 corporations like Google (part of the code is fetched from Google) and
2226 Amazon (the central coordination point is owned by Amazon). See for
2227 example
2228 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
2229 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
2230 view on these issues. But the network effect is strong in this case,
2231 and several of the people I want to communicate with already use
2232 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
2233 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
2234 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
2235 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
2236 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
2237 working on Debian Stable.&lt;/p&gt;
2238
2239 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
2240 working. It switch to the production servers, disable to timeout,
2241 make registration easier and add the shell wrapper:&lt;/p&gt;
2242
2243 &lt;pre&gt;
2244 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
2245 diff --git a/js/background.js b/js/background.js
2246 index 24b4c1d..579345f 100644
2247 --- a/js/background.js
2248 +++ b/js/background.js
2249 @@ -33,9 +33,9 @@
2250 });
2251 });
2252
2253 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2254 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
2255 var SERVER_PORTS = [80, 4433, 8443];
2256 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2257 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2258 var messageReceiver;
2259 window.getSocketStatus = function() {
2260 if (messageReceiver) {
2261 diff --git a/js/expire.js b/js/expire.js
2262 index 639aeae..beb91c3 100644
2263 --- a/js/expire.js
2264 +++ b/js/expire.js
2265 @@ -1,6 +1,6 @@
2266 ;(function() {
2267 &#39;use strict&#39;;
2268 - var BUILD_EXPIRATION = 0;
2269 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
2270
2271 window.extension = window.extension || {};
2272
2273 diff --git a/js/views/install_view.js b/js/views/install_view.js
2274 index 7816f4f..1d6233b 100644
2275 --- a/js/views/install_view.js
2276 +++ b/js/views/install_view.js
2277 @@ -38,7 +38,8 @@
2278 return {
2279 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
2280 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
2281 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
2282 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
2283 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
2284 };
2285 },
2286 clearQR: function() {
2287 diff --git a/options.html b/options.html
2288 index dc0f28e..8d709f6 100644
2289 --- a/options.html
2290 +++ b/options.html
2291 @@ -14,7 +14,10 @@
2292 &amp;lt;div class=&#39;nav&#39;&gt;
2293 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
2294 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
2295 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
2296 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
2297 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
2298 +
2299 + &amp;lt;/div&gt;
2300 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
2301 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
2302 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
2303 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
2304 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
2305 @@ -0,0 +1,12 @@
2306 +#!/bin/sh
2307 +set -e
2308 +cd $(dirname $0)
2309 +mkdir -p userdata
2310 +userdata=&quot;`pwd`/userdata&quot;
2311 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
2312 + (cd $userdata &amp;&amp; git init)
2313 +fi
2314 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
2315 +exec chromium \
2316 + --proxy-server=&quot;socks://localhost:9050&quot; \
2317 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2318 EOF
2319 chmod a+rx run-signal-app
2320 &lt;/pre&gt;
2321
2322 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2323 activities, please send Bitcoin donations to my address
2324 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2325 </description>
2326 </item>
2327
2328 <item>
2329 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
2330 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
2331 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
2332 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
2333 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2334 system&lt;/a&gt; provide a practical and easy way to figure out which
2335 packages support the hardware in a given machine. The command line
2336 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
2337 convenient way to list and install packages relevant for the current
2338 hardware during system installation, both user space packages and
2339 firmware packages. The GUI background daemon on the other hand provide
2340 a pop-up proposing to install packages when a new dongle is inserted
2341 while using the computer. For example, if you plug in a smart card
2342 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
2343 that package isn&#39;t already installed, and if you plug in a USB video
2344 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
2345 cheese is currently missing. This already work just fine.&lt;/p&gt;
2346
2347 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
2348 package names. When I started no such database existed in Debian, so
2349 I made my own data set and included it with the isenkram package and
2350 made isenkram fetch the latest version of this database from git using
2351 http. This way the isenkram users would get updated package proposals
2352 as soon as I learned more about hardware related packages.&lt;/p&gt;
2353
2354 &lt;p&gt;The hardware is identified using modalias strings. The modalias
2355 design is from the Linux kernel where most hardware descriptors are
2356 made available as a strings that can be matched using filename style
2357 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2358 identifiers.&lt;/p&gt;
2359
2360 &lt;p&gt;The downside to the Isenkram specific database is that there is no
2361 information about relevant distribution / Debian version, making
2362 isenkram propose obsolete packages too. But along came AppStream, a
2363 cross distribution mechanism to store and collect metadata about
2364 software packages. When I heard about the proposal, I contacted the
2365 people involved and suggested to add a hardware matching rule using
2366 modalias strings in the specification, to be able to use AppStream for
2367 mapping hardware to packages. This idea was accepted and AppStream is
2368 now a great way for a package to announce the hardware it support in a
2369 distribution neutral way. I wrote
2370 &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
2371 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
2372 December. If you have a hardware related package in Debian, please
2373 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
2374
2375 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
2376 RCX or NXT unit, announce this support using AppStream. The effect is
2377 that when you insert such LEGO robot controller into your Debian
2378 machine, Isenkram will propose to install the packages needed to get
2379 it working. The intention is that this should allow the local user to
2380 start programming his robot controller right away without having to
2381 guess what packages to use or which permissions to fix.&lt;/p&gt;
2382
2383 &lt;p&gt;But when I sat down with my son the other day to program our NXT
2384 unit using his Debian Stretch computer, I discovered something
2385 annoying. The local console user (ie my son) did not get access to
2386 the USB device for programming the unit. This used to work, but no
2387 longer in Jessie and Stretch. After some investigation and asking
2388 around on #debian-devel, I discovered that this was because udev had
2389 changed the mechanism used to grant access to local devices. The
2390 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
2391 no longer applied, because LDAP users no longer was added to the
2392 plugdev group during login. Michael Biebl told me that this method
2393 was obsolete and the new method used ACLs instead. This was good
2394 news, as the plugdev mechanism is a mess when using a remote user
2395 directory like LDAP. Using ACLs would make sure a user lost device
2396 access when she logged out, even if the user left behind a background
2397 process which would retain the plugdev membership with the ConsoleKit
2398 setup. Armed with this knowledge I moved on to fix the access problem
2399 for the LEGO Mindstorms related packages.&lt;/p&gt;
2400
2401 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
2402 applied directly for a device, or is applied in
2403 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
2404 LEGO Mindstorms udev rules did not have a class, I decided to add the
2405 tag directly in the udev rules files included in the packages. Here
2406 is one example. For the nqc C compiler for the RCX, the
2407 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
2408
2409 &lt;p&gt;&lt;pre&gt;
2410 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
2411 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
2412 &lt;/pre&gt;&lt;/p&gt;
2413
2414 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
2415 packages using plugdev in their /lib/udev/rules.d/ files should be
2416 changed to use this tag (either directly or indirectly via
2417 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
2418 to detect this?&lt;/p&gt;
2419
2420 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
2421 It is unclear to me if the uaccess tag is an internal implementation
2422 detail like the udev-acl tag used by
2423 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
2424 indirect method is the preferred way. Michael
2425 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
2426 documentation from the systemd project&lt;/a&gt; and I hope it will make
2427 this clearer. For now I use the generic classes when they exist and
2428 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
2429 directly if no such class exist.&lt;/p&gt;
2430
2431 &lt;p&gt;To learn more about the isenkram system, please check out
2432 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2433 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2434
2435 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
2436 please join us on our IRC channel
2437 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
2438 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
2439 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
2440 list is not yet created, but we are working on it. :)&lt;/p&gt;
2441
2442 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2443 activities, please send Bitcoin donations to my address
2444 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2445 </description>
2446 </item>
2447
2448 <item>
2449 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
2450 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
2451 <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>
2452 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
2453 <description>&lt;p&gt;In April we
2454 &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
2455 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
2456 how to set up and administrate a Debian system. Today I am happy to
2457 report that the first draft is now publicly available. You can find
2458 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
2459 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
2460 eight chapters have a first draft translation, and we are working on
2461 proofreading the content. If you want to help out, please start
2462 contributing using
2463 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2464 hosted weblate project page&lt;/a&gt;, and get in touch using
2465 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2466 translators mailing list&lt;/a&gt;. Please also check out
2467 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2468 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
2469 and update weblate if you find errors.&lt;/p&gt;
2470
2471 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
2472 electronic form.&lt;/p&gt;
2473 </description>
2474 </item>
2475
2476 <item>
2477 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
2478 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
2479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
2480 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
2481 <description>&lt;p&gt;This summer, I read a great article
2482 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
2483 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
2484 how to profile multi-threaded programs. It presented a system for
2485 profiling software by running experiences in the running program,
2486 testing how run time performance is affected by &quot;speeding up&quot; parts of
2487 the code to various degrees compared to a normal run. It does this by
2488 slowing down parallel threads while the &quot;faster up&quot; code is running
2489 and measure how this affect processing time. The processing time is
2490 measured using probes inserted into the code, either using progress
2491 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2492 can also measure unmodified code by measuring complete the program
2493 runtime and running the program several times instead.&lt;/p&gt;
2494
2495 &lt;p&gt;The project and presentation was so inspiring that I would like to
2496 get the system into Debian. I
2497 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
2498 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
2499 system ready for Debian by sending patches. The build process need to
2500 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
2501 to include the JavaScript web page used to visualize the collected
2502 profiling information included in the source package.
2503 But I expect that should work out fairly soon.&lt;/p&gt;
2504
2505 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
2506 on a binary with debug symbols available, start the program like this:
2507
2508 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2509 coz run --- program-to-run
2510 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2511
2512 &lt;p&gt;This will create a text file profile.coz with the instrumentation
2513 information. To show what part of the code affect the performance
2514 most, use a web browser and either point it to
2515 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
2516 or use the copy from git (in the gh-pages branch). Check out this web
2517 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
2518 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
2519 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2520 code, rebuild and run the profiler. This allow coz to do more
2521 targeted experiments.&lt;/p&gt;
2522
2523 &lt;p&gt;A video published by ACM
2524 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
2525 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
2526 from the 25th Symposium on Operating Systems Principles available
2527 titled
2528 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
2529 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
2530
2531 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
2532 for Coz is available from github. It will only build with clang
2533 because it uses a
2534 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
2535 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
2536 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
2537 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
2538
2539 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
2540 of software in Debian. I would very much like some help with the
2541 packaging effort, as I lack the in depth knowledge on how to package
2542 C++ libraries.&lt;/p&gt;
2543 </description>
2544 </item>
2545
2546 <item>
2547 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
2548 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
2549 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
2550 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
2551 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2552 to be a slight challenge. Here is the recipe if I ever need to do it
2553 again. It all started by me wanting to try the recipe to set up
2554 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
2555 hardened Android installation&lt;/a&gt; from the Tor project blog on a
2556 device I had access to. It is a old mobile phone with a broken
2557 microphone The initial idea had been to just
2558 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
2559 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
2560 until a few days ago.&lt;/p&gt;
2561
2562 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
2563 loader (press volume down and power at the same time), (2) select
2564 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
2565 machine, (4) request the device identifier token by running &#39;fastboot
2566 oem get_identifier_token&#39;, (5) request the device unlocking key using
2567 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
2568 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
2569
2570 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
2571 or newer, and the device I was working on had 2.00.0027. This
2572 apparently can be easily fixed by downloading a Windows program and
2573 running it on your Windows machine, if you accept the terms Microsoft
2574 require you to accept to use Windows - which I do not. So I had to
2575 come up with a different approach. I got a lot of help from AndyCap
2576 on #nuug, and would not have been able to get this working without
2577 him.&lt;/p&gt;
2578
2579 &lt;p&gt;First I needed to extract the hboot firmware from
2580 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
2581 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
2582 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
2583 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
2584 recognise the file format, but unruu worked and extracted rom.zip,
2585 containing the new hboot firmware and a text file describing which
2586 devices it would work for.&lt;/p&gt;
2587
2588 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
2589 followed some instructions
2590 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
2591 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
2592 machine with Debian testing:&lt;/p&gt;
2593
2594 &lt;p&gt;&lt;pre&gt;
2595 adb reboot-bootloader
2596 fastboot oem rebootRUU
2597 fastboot flash zip rom.zip
2598 fastboot flash zip rom.zip
2599 fastboot reboot
2600 &lt;/pre&gt;&lt;/p&gt;
2601
2602 &lt;p&gt;The flash command apparently need to be done twice to take effect,
2603 as the first is just preparations and the second one do the flashing.
2604 The adb command is just to get to the boot loader menu, so turning the
2605 device on while holding volume down and the power button should work
2606 too.&lt;/p&gt;
2607
2608 &lt;p&gt;With the new hboot version in place I could start following the
2609 instructions on the HTC developer web site. I got the device token
2610 like this:&lt;/p&gt;
2611
2612 &lt;p&gt;&lt;pre&gt;
2613 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
2614 &lt;/pre&gt;
2615
2616 &lt;p&gt;And once I got the unlock code via email, I could use it like
2617 this:&lt;/p&gt;
2618
2619 &lt;p&gt;&lt;pre&gt;
2620 fastboot flash unlocktoken Unlock_code.bin
2621 &lt;/pre&gt;&lt;/p&gt;
2622
2623 &lt;p&gt;And with that final step in place, the phone was unlocked and I
2624 could start stuffing the software of my own choosing into the device.
2625 So far I only inserted a replacement recovery image to wipe the phone
2626 before I start. We will see what happen next. Perhaps I should
2627 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
2628 </description>
2629 </item>
2630
2631 <item>
2632 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
2633 <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>
2634 <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>
2635 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
2636 <description>&lt;p&gt;For a while now, I have wanted to test
2637 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
2638 said to provide end to end encrypted communication and several of my
2639 friends and family are already using it. As I by choice do not own a
2640 mobile phone, this proved to be harder than expected. And I wanted to
2641 have the source of the client and know that it was the code used on my
2642 machine. But yesterday I managed to get it working. I used the
2643 Github source, compared it to the source in
2644 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
2645 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
2646 patches to use the production Signal servers, started the app and
2647 asked for the hidden &quot;register without a smart phone&quot; form. Here is
2648 the recipe how I did it.&lt;/p&gt;
2649
2650 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
2651
2652 &lt;pre&gt;
2653 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2654 &lt;/pre&gt;
2655
2656 &lt;p&gt;Next, I patched the source to use the production servers, to be
2657 able to talk to other Signal users:&lt;/p&gt;
2658
2659 &lt;pre&gt;
2660 cat &amp;lt;&amp;lt;EOF | patch -p0
2661 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
2662 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
2663 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
2664 @@ -47,8 +47,8 @@
2665 });
2666 });
2667
2668 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
2669 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
2670 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
2671 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
2672 var messageReceiver;
2673 window.getSocketStatus = function() {
2674 if (messageReceiver) {
2675 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
2676 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
2677 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
2678 @@ -1,6 +1,6 @@
2679 ;(function() {
2680 &#39;use strict&#39;;
2681 - var BUILD_EXPIRATION = 0;
2682 + var BUILD_EXPIRATION = 1474492690000;
2683
2684 window.extension = window.extension || {};
2685
2686 EOF
2687 &lt;/pre&gt;
2688
2689 &lt;p&gt;The first part is changing the servers, and the second is updating
2690 an expiration timestamp. This timestamp need to be updated regularly.
2691 It is set 90 days in the future by the build process (Gruntfile.js).
2692 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
2693
2694 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
2695 script to launch Signal in Chromium.&lt;/p&gt;
2696
2697 &lt;pre&gt;
2698 #!/bin/sh
2699 cd $(dirname $0)
2700 mkdir -p userdata
2701 exec chromium \
2702 --proxy-server=&quot;socks://localhost:9050&quot; \
2703 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2704 &lt;/pre&gt;
2705
2706 &lt;p&gt; The script start the app and configure Chromium to use the Tor
2707 SOCKS5 proxy to make sure those controlling the Signal servers (today
2708 Amazon and Whisper Systems) as well as those listening on the lines
2709 will have a harder time location my laptop based on the Signal
2710 connections if they use source IP address.&lt;/p&gt;
2711
2712 &lt;p&gt;When the script starts, one need to follow the instructions under
2713 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
2714 repository. I right clicked on the Signal window to get up the
2715 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
2716 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
2717 registration form. Then I entered by land line phone number and
2718 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
2719 repeated the verification code three times. After entering the number
2720 into the verification code field in the form, I could start using
2721 Signal from my laptop.
2722
2723 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
2724 whom and thus who know who to those controlling the central server,
2725 but such leakage is hard to avoid with a centrally controlled server
2726 setup. It is something to keep in mind when using Signal - the
2727 content of your chats are harder to intercept, but the meta data
2728 exposing your contact network is available to people you do not know.
2729 So better than many options, but not great. And sadly the usage is
2730 connected to my land line, thus allowing those controlling the server
2731 to associate it to my home and person. I would prefer it if only
2732 those I knew could tell who I was on Signal. There are options
2733 avoiding such information leakage, but most of my friends are not
2734 using them, so I am stuck with Signal for now.&lt;/p&gt;
2735
2736 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
2737 on this topic in
2738 &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
2739 and updated recipe for using the Signal app without a mobile
2740 phone&lt;/a&gt;.&lt;/p&gt;
2741 </description>
2742 </item>
2743
2744 <item>
2745 <title>The new &quot;best&quot; multimedia player in Debian?</title>
2746 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
2747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
2748 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
2749 <description>&lt;p&gt;When I set out a few weeks ago to figure out
2750 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
2751 multimedia player in Debian claimed to support most file formats /
2752 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
2753 the various players claimed support for. The range was from 55 to 130
2754 MIME types. I suspect most media formats are supported by all
2755 players, but this is not really reflected in the MimeTypes values in
2756 their desktop files. There are probably also some bogus MIME types
2757 listed, but it is hard to identify which one this is.&lt;/p&gt;
2758
2759 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
2760 the players suggesting to add more MIME types to their desktop files,
2761 and decided to spend some time myself improving the situation for my
2762 favorite media player VLC. The fixes for VLC entered Debian unstable
2763 yesterday. The complete list of MIME types can be seen on the
2764 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
2765 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
2766
2767 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
2768 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2769 kmplayer. I am sure some of the other players desktop files support
2770 several of the formats currently listed as working only with vlc,
2771 toten and parole.&lt;/p&gt;
2772
2773 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
2774 supported by all the tested multimedia players in Debian in their
2775 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2776 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2777 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2778 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2779 it sad that video/ogg and video/webm is not supported by all the media
2780 players in Debian. As far as I can tell, all of them can handle both
2781 formats.&lt;/p&gt;
2782 </description>
2783 </item>
2784
2785 <item>
2786 <title>A program should be able to open its own files on Linux</title>
2787 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
2788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
2789 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
2790 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
2791 decided to test its presentation tool when making the slides for a
2792 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2793 wrote the first draft of the slides, saved the result and went to bed
2794 the day before I would give the talk. The next day I took a plane to
2795 the location where the meeting should take place, and on the plane I
2796 started up koffice again to polish the talk a bit, only to discover
2797 that kpresenter refused to load its own data file. I cursed a bit and
2798 started making the slides again from memory, to have something to
2799 present when I arrived. I tested that the saved files could be
2800 loaded, and the day seemed to be rescued. I continued to polish the
2801 slides until I suddenly discovered that the saved file could no longer
2802 be loaded into kpresenter. In the end I had to rewrite the slides
2803 three times, condensing the content until the talk became shorter and
2804 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
2805 kpresenter wrote inline images in a way itself could not understand.
2806 Eventually that bug was fixed and kpresenter ended up being a great
2807 program to make slides. The point I&#39;m trying to make is that we
2808 expect a program to be able to load its own data files, and it is
2809 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
2810
2811 &lt;p&gt;Did you ever experience a program failing to load its own data
2812 files from the desktop file browser? It is not a uncommon problem. A
2813 while back I discovered that the screencast recorder
2814 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2815 browser would refuse to open. No video player claimed to understand
2816 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
2817 returning the application/ogg MIME type, which no video player I had
2818 installed listed as a MIME type they would understand. I asked for
2819 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
2820 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
2821 several video players to add video/ogg to their desktop files, to give
2822 the file browser an idea what to do about Ogg Theora files. After a
2823 while, the desktop file browsers in Debian started to handle the
2824 output from gtk-recordmydesktop properly.&lt;/p&gt;
2825
2826 &lt;p&gt;But history repeats itself. A few days ago I tested the music
2827 system Rosegarden again, and I discovered that the KDE and xfce file
2828 browsers did not know what to do with the Rosegarden project files
2829 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
2830 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
2831 included in the next upload. To increase the chance of me remembering
2832 how to fix the problem next time some program fail to load its files
2833 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
2834
2835 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
2836 There are two sources for the MIME type of a given file. The output from
2837 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
2838 shared MIME type registry (under /usr/share/mime/). The file MIME
2839 type is mapped to programs supporting the MIME type, and this
2840 information is collected from
2841 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
2842 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
2843 one desktop file claiming support for the MIME type of the file, it is
2844 activated when asking to open a given file. If there are more, one
2845 can normally select which one to use by right-clicking on the file and
2846 selecting the wanted one using &#39;Open with&#39; or similar. In general
2847 this work well. But it depend on each program picking a good MIME
2848 type (preferably
2849 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
2850 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
2851 registry recognizing the file and the desktop file to list the MIME
2852 type in its list of supported MIME types.&lt;/p&gt;
2853
2854 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
2855 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
2856 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
2857
2858 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2859 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2860 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
2861 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
2862 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
2863 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
2864 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
2865 &amp;lt;/mime-type&amp;gt;
2866 &amp;lt;/mime-info&amp;gt;
2867 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2868
2869 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
2870 (it is a gzipped XML file). Note, it is much better to use an
2871 official MIME type registered with IANA than it is to make up ones own
2872 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
2873
2874 &lt;p&gt;The desktop file of the rosegarden program failed to list
2875 audio/x-rosegarden in its list of supported MIME types, causing the
2876 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
2877
2878 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2879 % grep Mime /usr/share/applications/rosegarden.desktop
2880 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2881 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2882 %
2883 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2884
2885 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2886 MimeType= line.&lt;/p&gt;
2887
2888 &lt;p&gt;If you run into a file which fail to open the correct program when
2889 selected from the file browser, please check out the output from
2890 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2891 MIME type is registered somewhere under /usr/share/mime/ and check
2892 that some desktop file under /usr/share/applications/ is claiming
2893 support for this MIME type. If not, please report a bug to have it
2894 fixed. :)&lt;/p&gt;
2895 </description>
2896 </item>
2897
2898 <item>
2899 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2900 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2901 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2902 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2903 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2904 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2905 related packages. The idea is to have a database of mappings between
2906 hardware and packages, and pop up a dialog suggesting for the user to
2907 install the packages to use a given hardware dongle. Some use cases
2908 are when you insert a Yubikey, it proposes to install the software
2909 needed to control it; when you insert a braille reader list it
2910 proposes to install the packages needed to send text to the reader;
2911 and when you insert a ColorHug screen calibrator it suggests to
2912 install the driver for it. The system work well, and even have a few
2913 command line tools to install firmware packages and packages for the
2914 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2915
2916 &lt;p&gt;The system was initially written using aptdaemon, because I found
2917 good documentation and example code on how to use it. But aptdaemon
2918 is going away and is generally being replaced by
2919 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2920 so Isenkram needed a rewrite. And today, thanks to the great patch
2921 from my college Sunil Mohan Adapa in the FreedomBox project, the
2922 rewrite finally took place. I&#39;ve just uploaded a new version of
2923 Isenkram into Debian Unstable with the patch included, and the default
2924 for the background daemon is now to use PackageKit. To check it out,
2925 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2926 and see if it is recognised.&lt;/p&gt;
2927
2928 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2929 the machine it is running on, you can check out the isenkram-lookup
2930 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2931
2932 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2933 % isenkram-lookup
2934 bluez
2935 cheese
2936 fprintd
2937 fprintd-demo
2938 gkrellm-thinkbat
2939 hdapsd
2940 libpam-fprintd
2941 pidgin-blinklight
2942 thinkfan
2943 tleds
2944 tp-smapi-dkms
2945 tp-smapi-source
2946 tpb
2947 %p
2948 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2949
2950 &lt;p&gt;The hardware mappings come from several places. The preferred way
2951 is for packages to announce their hardware support using
2952 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2953 cross distribution appstream system&lt;/a&gt;.
2954 See
2955 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2956 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2957 </description>
2958 </item>
2959
2960 <item>
2961 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2962 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2964 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2965 <description>&lt;p&gt;Yesterday I updated the
2966 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2967 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2968 enterprising users. There were some nice user and visible changes.
2969 First of all, both desktop menu entries now work. A design flaw in
2970 one of the script made the history graph fail to show up (its PNG was
2971 dumped in ~/.xsession-errors) if no controlling TTY was available.
2972 The script worked when called from the command line, but not when
2973 called from the desktop menu. I changed this to look for a DISPLAY
2974 variable or a TTY before deciding where to draw the graph, and now the
2975 graph window pop up as expected.&lt;/p&gt;
2976
2977 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2978 graphs (the one showing the last few hours). New is also the user of
2979 colours showing charging in blue and discharge in red. The percentages
2980 of this graph is relative to last full charge, not battery design
2981 capacity.&lt;/p&gt;
2982
2983 &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;
2984
2985 &lt;p&gt;The other graph show the entire history of the collected battery
2986 statistics, comparing it to the design capacity of the battery to
2987 visualise how the battery life time get shorter over time. The red
2988 line in this graph is what the previous graph considers 100 percent:
2989
2990 &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;
2991
2992 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2993 percent of last full capacity, and how the capacity of the battery is
2994 shrinking. :(&lt;/p&gt;
2995
2996 &lt;p&gt;The last new feature is in the collector, which now will handle
2997 more hardware models. On some hardware, Linux power supply
2998 information is stored in /sys/class/power_supply/ACAD/, while the
2999 collector previously only looked in /sys/class/power_supply/AC/. Now
3000 both are checked to figure if there is power connected to the
3001 machine.&lt;/p&gt;
3002
3003 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3004 check out the
3005 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3006 in Debian unstable, or rebuild it on Jessie to get it working on
3007 Debian stable. :) The upstream source is available from &lt;a
3008 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3009 Patches are very welcome.&lt;/p&gt;
3010
3011 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3012 activities, please send Bitcoin donations to my address
3013 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3014 </description>
3015 </item>
3016
3017 <item>
3018 <title>Debian now with ZFS on Linux included</title>
3019 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
3020 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
3021 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
3022 <description>&lt;p&gt;Today, after many years of hard work from many people,
3023 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
3024 Debian. The package status can be seen on
3025 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
3026 for zfs-linux&lt;/a&gt;. and
3027 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3028 team status page&lt;/a&gt;. If you want to help out, please join us.
3029 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
3030 source code&lt;/a&gt; is available via git on Alioth. It would also be
3031 great if you could help out with
3032 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
3033 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
3034 </description>
3035 </item>
3036
3037 <item>
3038 <title>What is the best multimedia player in Debian?</title>
3039 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
3040 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
3041 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
3042 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
3043 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
3044
3045 &lt;p&gt;A few years ago, I had a look at the media support for Browser
3046 plugins in Debian, to get an idea which plugins to include in Debian
3047 Edu. I created a script to extract the set of supported MIME types
3048 for each plugin, and used this to find out which multimedia browser
3049 plugin supported most file formats / media types.
3050 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
3051 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
3052 not been updated for a while. But browser plugins are less relevant
3053 these days, so I thought it was time to look at standalone
3054 players.&lt;/p&gt;
3055
3056 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
3057 player when I wanted to play videos from the Norwegian National
3058 Broadcasting Company, and decided to investigate why. The cause is a
3059 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
3060 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
3061 of MIME types announced in the desktop file and the browser plugin,
3062 only to discover that there is quite a large difference between the
3063 two for VLC. This discovery made me dig up the script I used to
3064 compare browser plugins, and adjust it to compare desktop files
3065 instead, to try to figure out which multimedia player in Debian
3066 support most file formats.&lt;/p&gt;
3067
3068 &lt;p&gt;The result can be seen on the Debian Wiki, as
3069 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
3070 table listing all MIME types supported by one of the packages included
3071 in the table&lt;/a&gt;, with the package supporting most MIME types being
3072 listed first in the table.&lt;/p&gt;
3073
3074 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
3075 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3076 kmplayer. Time for the other players to update their announced MIME
3077 support?&lt;/p&gt;
3078 </description>
3079 </item>
3080
3081 <item>
3082 <title>The Pyra - handheld computer with Debian preinstalled</title>
3083 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
3084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
3085 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
3086 <description>A friend of mine made me aware of
3087 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
3088 handheld computer which will be delivered with Debian preinstalled. I
3089 would love to get one of those for my birthday. :)&lt;/p&gt;
3090
3091 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3092 plugs and many others connectors, and include a full keyboard and a 5&quot;
3093 LCD touch screen. The 6000mAh battery is claimed to provide a whole
3094 day of battery life time, but I have not seen any independent tests
3095 confirming this. The vendor is still collecting preorders, and the
3096 last I heard last night was that 22 more orders were needed before
3097 production started.&lt;/p&gt;
3098
3099 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
3100 Debian. Please let me know if you know of any others. Is it the
3101 first computer being sold with Debian preinstalled?&lt;/p&gt;
3102 </description>
3103 </item>
3104
3105 <item>
3106 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
3107 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
3108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
3109 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
3110 <description>&lt;p&gt;During this weekends
3111 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
3112 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
3113 to make sure there are good books about Debian available in Norwegian
3114 Bokmål, and got in touch with the people behind the
3115 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
3116 project&lt;/a&gt; to get started. If you want to help out, please start
3117 contributing using
3118 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3119 hosted weblate project page&lt;/a&gt;, and get in touch using
3120 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3121 translators mailing list&lt;/a&gt;. Please also check out
3122 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3123 contributors&lt;/a&gt;.&lt;/p&gt;
3124
3125 &lt;p&gt;The book is already available on paper in English, French and
3126 Japanese, and our goal is to get it available on paper in Norwegian
3127 Bokmål too. In addition to the paper edition, there are also EPUB and
3128 Mobi versions available. And there are incomplete translations
3129 available for many more languages.&lt;/p&gt;
3130 </description>
3131 </item>
3132
3133 <item>
3134 <title>One in two hundred Debian users using ZFS on Linux?</title>
3135 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
3136 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
3137 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
3138 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
3139 packages in Debian, and was quite surprised with what I found. I use
3140 ZFS myself at home, but did not really expect many others to do so.
3141 But I might be wrong.&lt;/p&gt;
3142
3143 &lt;p&gt;According to
3144 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
3145 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
3146 0.53% of the population, with the package installed. As far as I know
3147 the only use of the spl-linux package is as a support library for ZFS
3148 on Linux, so I use it here as proxy for measuring the number of ZFS
3149 installation on Linux in Debian. In the kFreeBSD variant of Debian
3150 the ZFS feature is already available, and there
3151 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
3152 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
3153 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
3154
3155 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
3156 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
3157 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
3158 cleared, the package is still not in Debian. The package is again in
3159 the NEW queue. Several uploads have been rejected so far because the
3160 debian/copyright file was incomplete or wrong, but there is no reason
3161 to give up. The current status can be seen on
3162 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3163 team status page&lt;/a&gt;, and
3164 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
3165 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
3166
3167 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
3168 my home server can function in the future using only official Debian
3169 packages, and the current blocker is to get the debian/copyright file
3170 accepted by the FTP masters in Debian, I decided a while back to try
3171 to help out the team. This was the background for my blog post about
3172 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
3173 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
3174 used the techniques I explored there to try to find any errors in the
3175 copyright file. It is not very easy to check every one of the around
3176 2000 files in the source package, but I hope we this time got it
3177 right. If you want to help out, check out the git source and try to
3178 find missing entries in the debian/copyright file.&lt;/p&gt;
3179 </description>
3180 </item>
3181
3182 <item>
3183 <title>Full battery stats collector is now available in Debian</title>
3184 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
3185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
3186 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
3187 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
3188 extended collector that will collect the complete battery history for
3189 later processing and graphing. The original collector store the
3190 battery level as percentage of last full level, while the new
3191 collector also record battery vendor, model, serial number, design
3192 full level, last full level and current battery level. This make it
3193 possible to predict the lifetime of the battery as well as visualise
3194 the energy flow when the battery is charging or discharging.&lt;/p&gt;
3195
3196 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
3197 in the version 0.5.1 package in unstable. Get the new battery level graph
3198 and lifetime prediction by running:
3199
3200 &lt;p&gt;&lt;pre&gt;
3201 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3202 &lt;/pre&gt;&lt;/p&gt;
3203
3204 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
3205
3206 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
3207 entry yet):&lt;/p&gt;
3208
3209 &lt;p&gt;&lt;pre&gt;
3210 /usr/share/battery-stats/battery-stats-graph-flow
3211 &lt;/pre&gt;&lt;/p&gt;
3212
3213 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
3214 when there are few data points. The graphs look a bit better with a
3215 few years of data.&lt;/p&gt;
3216
3217 &lt;p&gt;A while back one important feature I use in the battery stats
3218 collector broke in Debian. The scripts in
3219 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
3220 suspect it happened when Jessie started using systemd, but I do not
3221 know. The issue is reported as
3222 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
3223 pm-utils. I managed to work around it by adding an udev rule to call
3224 the collector script every time the power connector is connected and
3225 disconnected. With this fix in place it was finally time to make a
3226 new release of the package, and get it into Debian.&lt;/p&gt;
3227
3228 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3229 check out the
3230 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3231 in Debian unstable, or rebuild it on Jessie to get it working on
3232 Debian stable. :) The upstream source is available from
3233 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3234 As always, patches are very welcome.&lt;/p&gt;
3235 </description>
3236 </item>
3237
3238 <item>
3239 <title>Making battery measurements a little easier in Debian</title>
3240 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
3241 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
3242 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
3243 <description>&lt;p&gt;Back in September, I blogged about
3244 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
3245 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
3246 how it showed the decay and death of this battery (now replaced). I
3247 created a simple deb package to handle the collection and graphing,
3248 but did not want to upload it to Debian as there were already
3249 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
3250 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
3251 a point of uploading a competing package when battery-stats could be
3252 fixed instead. I reported a few bugs about its non-function, and
3253 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
3254
3255 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
3256 hands. The end result is that I am now the new upstream developer of
3257 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
3258 battery-stats in Debian, and the package in Debian unstable is finally
3259 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
3260 information provided by the Linux kernel. If you install the
3261 battery-stats package from unstable now, you will be able to get a
3262 graph of the current battery fill level, to get some idea about the
3263 status of the battery. The source package build and work just fine in
3264 Debian testing and stable (and probably oldstable too, but I have not
3265 tested). The default graph you get for that system look like this:&lt;/p&gt;
3266
3267 &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;
3268
3269 &lt;p&gt;My plans for the future is to merge my old scripts into the
3270 battery-stats package, as my old scripts collected a lot more details
3271 about the battery. The scripts are merged into the upstream
3272 battery-stats git repository already, but I am not convinced they work
3273 yet, as I changed a lot of paths along the way. Will have to test a
3274 bit more before I make a new release.&lt;/p&gt;
3275
3276 &lt;p&gt;I will also consider changing the file format slightly, as I
3277 suspect the way I combine several values into one field might make it
3278 impossible to know the type of the value when using it for processing
3279 and graphing.&lt;/p&gt;
3280
3281 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
3282 battery, check out the battery-stats package in
3283 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
3284 on
3285 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3286 I would love some help to improve the system further.&lt;/p&gt;
3287 </description>
3288 </item>
3289
3290 <item>
3291 <title>Creating, updating and checking debian/copyright semi-automatically</title>
3292 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
3293 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
3294 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
3295 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
3296 details. And one of the details is the content of the
3297 debian/copyright file, which should list all relevant licenses used by
3298 the code in the package in question, preferably in
3299 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
3300 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
3301
3302 &lt;p&gt;For large packages with lots of contributors it is hard to write
3303 and update this file manually, and if you get some detail wrong, the
3304 package is normally rejected by the ftpmasters. So getting it right
3305 the first time around get the package into Debian faster, and save
3306 both you and the ftpmasters some work.. Today, while trying to figure
3307 out what was wrong with
3308 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
3309 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
3310 figuring out the options for doing this job automatically, or at least
3311 semi-automatically.&lt;/p&gt;
3312
3313 &lt;p&gt;Lucikly, there are at least two tools available for generating the
3314 file based on the code in the source package,
3315 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
3316 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
3317 not sure which one of them came first, but both seem to be able to
3318 create a sensible draft file. As far as I can tell, none of them can
3319 be trusted to get the result just right, so the content need to be
3320 polished a bit before the file is OK to upload. I found the debmake
3321 option in
3322 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
3323 blog posts from 2014&lt;/a&gt;.
3324
3325 &lt;p&gt;To generate using debmake, use the -cc option:
3326
3327 &lt;p&gt;&lt;pre&gt;
3328 debmake -cc &gt; debian/copyright
3329 &lt;/pre&gt;&lt;/p&gt;
3330
3331 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
3332 this might not be the best option.&lt;/p&gt;
3333
3334 &lt;p&gt;The cme option is based on a config parsing library, and I found
3335 this approach in
3336 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
3337 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
3338 dpkg-copyright&#39; option:
3339
3340 &lt;p&gt;&lt;pre&gt;
3341 cme update dpkg-copyright
3342 &lt;/pre&gt;&lt;/p&gt;
3343
3344 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
3345 handle UTF-8 names better than debmake.&lt;/p&gt;
3346
3347 &lt;p&gt;When the copyright file is created, I would also like some help to
3348 check if the file is correct. For this I found two good options,
3349 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
3350 to focus on license types and file matching, and is able to detect
3351 ineffective blocks in the copyright file. The latter reports missing
3352 copyright holders and years, but was confused by inconsistent license
3353 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
3354 fix all issues reported by them before uploading. But I do not know
3355 if the tools and the ftpmasters agree on what is important to fix in a
3356 copyright file, so the package might still be rejected.&lt;/p&gt;
3357
3358 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
3359 will read through the source and try to find all copyright statements.
3360 It is not comparing the result to the content of debian/copyright, but
3361 can be useful when verifying the content of the copyright file.&lt;/p&gt;
3362
3363 &lt;p&gt;Are you aware of better tools in Debian to create and update
3364 debian/copyright file. Please let me know, or blog about it on
3365 planet.debian.org.&lt;/p&gt;
3366
3367 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3368 activities, please send Bitcoin donations to my address
3369 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3370
3371 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
3372 on how to use licensecheck and cdbs to create a draft copyright file
3373
3374 &lt;p&gt;&lt;pre&gt;
3375 licensecheck --copyright -r `find * -type f` | \
3376 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
3377 &lt;/pre&gt;&lt;/p&gt;
3378
3379 &lt;p&gt;He mentioned that he normally check the generated file into the
3380 version control system to make it easier to discover license and
3381 copyright changes in the upstream source. I will try to do the same
3382 with my packages in the future.&lt;/p&gt;
3383
3384 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
3385 against using -quiet for new users, so I removed it from the proposed
3386 command line.&lt;/p&gt;
3387 </description>
3388 </item>
3389
3390 <item>
3391 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
3392 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
3393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
3394 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
3395 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
3396 is taking shape in Debian, and one provided feature is a very
3397 convenient way to tell you which package to install to make a given
3398 firmware file available when the kernel is looking for it. This can
3399 be done using apt-file too, but that is for someone else to blog
3400 about. :)&lt;/p&gt;
3401
3402 &lt;p&gt;Here is a small recipe to find the package with a given firmware
3403 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
3404 picked from the set of firmware announced using appstream in Debian
3405 unstable. In general you would be looking for the firmware requested
3406 by the kernel during kernel module loading. To find the package
3407 providing the example file, do like this:&lt;/p&gt;
3408
3409 &lt;blockquote&gt;&lt;pre&gt;
3410 % apt install appstream
3411 [...]
3412 % apt update
3413 [...]
3414 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
3415 awk &#39;/Package:/ {print $2}&#39;
3416 firmware-qlogic
3417 %
3418 &lt;/pre&gt;&lt;/blockquote&gt;
3419
3420 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
3421 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
3422 a way appstream can use.&lt;/p&gt;
3423
3424 &lt;p&gt;This same approach can be used to find any package supporting a
3425 given MIME type. This is very useful when you get a file you do not
3426 know how to handle. First find the mime type using &lt;tt&gt;file
3427 --mime-type&lt;/tt&gt;, and next look up the package providing support for
3428 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3429 and you can find all packages handling this type like this:&lt;/p&gt;
3430
3431 &lt;blockquote&gt;&lt;pre&gt;
3432 % apt install appstream
3433 [...]
3434 % apt update
3435 [...]
3436 % appstreamcli what-provides mimetype image/svg+xml | \
3437 awk &#39;/Package:/ {print $2}&#39;
3438 bkchem
3439 phototonic
3440 inkscape
3441 shutter
3442 tetzle
3443 geeqie
3444 xia
3445 pinta
3446 gthumb
3447 karbon
3448 comix
3449 mirage
3450 viewnior
3451 postr
3452 ristretto
3453 kolourpaint4
3454 eog
3455 eom
3456 gimagereader
3457 midori
3458 %
3459 &lt;/pre&gt;&lt;/blockquote&gt;
3460
3461 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
3462 packages providing appstream metadata.&lt;/p&gt;
3463 </description>
3464 </item>
3465
3466 <item>
3467 <title>Creepy, visualise geotagged social media information - nice free software</title>
3468 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
3469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
3470 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
3471 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
3472 with the computerised radio beacon known as a mobile phone their
3473 position is tracked by the phone company and often stored for a long
3474 time (like every time a SMS is received or sent). And if their
3475 computerised radio beacon is capable of running programs (often called
3476 mobile apps) downloaded from the Internet, these programs are often
3477 also capable of tracking their location (if the app requested access
3478 during installation). And when these programs send out information to
3479 central collection points, the location is often included, unless
3480 extra care is taken to not send the location. The provided
3481 information is used by several entities, for good and bad (what is
3482 good and bad, depend on your point of view). What is certain, is that
3483 the private sphere and the right to free movement is challenged and
3484 perhaps even eradicated for those announcing their location this way,
3485 when they share their whereabouts with private and public
3486 entities.&lt;/p&gt;
3487
3488 &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;
3489
3490 &lt;p&gt;The phone company logs provide a register of locations to check out
3491 when one want to figure out what the tracked person was doing. It is
3492 unavailable for most of us, but provided to selected government
3493 officials, company staff, those illegally buying information from
3494 unfaithful servants and crackers stealing the information. But the
3495 public information can be collected and analysed, and a free software
3496 tool to do so is called
3497 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
3498 discovered it when I read
3499 &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
3500 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
3501 November 2014, and decided to check if it was available in Debian.
3502 The python program was in Debian, but
3503 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
3504 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
3505 uploaded a new version which did not work quite right, but did not
3506 have time to fix it then. This Christmas I decided to finally try to
3507 get Creepy operational in Debian. Now a fixed version is available in
3508 Debian unstable and testing, and almost all Debian specific patches
3509 are now included
3510 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
3511
3512 &lt;p&gt;The Creepy program visualises geolocation information fetched from
3513 Twitter, Instagram, Flickr and Google+, and allow one to get a
3514 complete picture of every social media message posted recently in a
3515 given area, or track the movement of a given individual across all
3516 these services. Earlier it was possible to use the search API of at
3517 least some of these services without identifying oneself, but these
3518 days it is impossible. This mean that to use Creepy, you need to
3519 configure it to log in as yourself on these services, and provide
3520 information to them about your search interests. This should be taken
3521 into account when using Creepy, as it will also share information
3522 about yourself with the services.&lt;/p&gt;
3523
3524 &lt;p&gt;The picture above show the twitter messages sent from (or at least
3525 geotagged with a position from) the city centre of Oslo, the capital
3526 of Norway. One useful way to use Creepy is to first look at
3527 information tagged with an area of interest, and next look at all the
3528 information provided by one or more individuals who was in the area.
3529 I tested it by checking out which celebrity provide their location in
3530 twitter messages by checkout out who sent twitter messages near a
3531 Norwegian TV station, and next could track their position over time,
3532 making it possible to locate their home and work place, among other
3533 things. A similar technique have been
3534 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
3535 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
3536 tool to discover lying governments, and a useful tool to help people
3537 understand the value of the private information they provide to the
3538 public.&lt;/p&gt;
3539
3540 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
3541 it depend on several python modules currently missing in Jessie (at
3542 least python-instagram, python-flickrapi and
3543 python-requests-toolbelt).&lt;/p&gt;
3544
3545 &lt;p&gt;(I have uploaded
3546 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
3547 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
3548 Creepy program in Debian.)&lt;/p&gt;
3549 </description>
3550 </item>
3551
3552 <item>
3553 <title>Always download Debian packages using Tor - the simple recipe</title>
3554 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
3555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
3556 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
3557 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
3558 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
3559 that those listening on the Internet lines would have good reason to
3560 believe a computer have a given security hole&lt;/a&gt; if it download a
3561 security fix from a Debian mirror. This is a good reason to always
3562 use encrypted connections to the Debian mirror, to make sure those
3563 listening do not know which IP address to attack. In August, Richard
3564 Hartmann observed that encryption was not enough, when it was possible
3565 to interfere download size to security patches or the fact that
3566 download took place shortly after a security fix was released, and
3567 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
3568 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
3569 was not the first to propose this, as the
3570 &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;
3571 package by Tim Retout already existed to make it easy to convince apt
3572 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
3573 aware of that package when I read the blog post from Richard.&lt;/p&gt;
3574
3575 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
3576 sysadmins, and he set up a Tor hidden service on one of the central
3577 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3578 it possible to download packages directly between two tor nodes,
3579 making sure the network traffic always were encrypted.&lt;/p&gt;
3580
3581 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
3582 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
3583 urls with tor+http and tor+https, and using the hidden service instead
3584 of the official Debian mirror site. I recommend installing
3585 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
3586 done in /etc/.&lt;/p&gt;
3587
3588 &lt;blockquote&gt;&lt;pre&gt;
3589 apt install apt-transport-tor
3590 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
3591 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
3592 &lt;/pre&gt;&lt;/blockquote&gt;
3593
3594 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
3595 the sed commands for these too. The sed command is assuming your are
3596 using the ftp.debian.org Debian mirror. Adjust the command (or just
3597 edit the file manually) to match your mirror.&lt;/p&gt;
3598
3599 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
3600 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
3601 system, and do not work with these tor+http URLs. For
3602 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
3603 which need a recent apt version currently only in unstable. So if you
3604 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
3605
3606 &lt;p&gt;Another advantage from this change is that your machine will start
3607 using Tor regularly and at fairly random intervals (every time you
3608 update the package lists or upgrade or install a new package), thus
3609 masking other Tor traffic done from the same machine. Using Tor will
3610 become normal for the machine in question.&lt;/p&gt;
3611
3612 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
3613 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
3614 enabled. It would be great if it was the default on any Debian
3615 system.&lt;/p&gt;
3616 </description>
3617 </item>
3618
3619 <item>
3620 <title>OpenALPR, find car license plates in video streams - nice free software</title>
3621 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
3622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
3623 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
3624 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
3625 call the car license plate numbers in those days. I would write the
3626 numbers down in my little book and compare notes with the other kids
3627 to see how many region codes we had seen and if we had seen some
3628 exotic or special region codes and numbers. It was a fun game to pass
3629 time, as we kids have plenty of it.&lt;/p&gt;
3630
3631 &lt;p&gt;A few days I came across
3632 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
3633 project&lt;/a&gt;, a free software project to automatically discover and
3634 report license plates in images and video streams, and provide the
3635 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
3636 such system for a while now, because I believe it is a bad idea that the
3637 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
3638 number plate recognition&lt;/a&gt; tool only is available in the hands of
3639 the powerful, and want it to be available also for the powerless to
3640 even the score when it comes to surveillance and sousveillance. I
3641 discovered the developer
3642 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
3643 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
3644 help him get it into shape to get the package uploaded into the Debian
3645 archive.&lt;/p&gt;
3646
3647 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
3648 it into Debian, where it currently
3649 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
3650 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
3651
3652 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
3653 for the common folks, ie those not running a large government
3654 surveillance system? Well, I plan to put it in a computer on my bike
3655 and in my car, tracking the cars nearby and allowing me to be notified
3656 when number plates on my watch list are discovered. Another use case
3657 was suggested by a friend of mine, who wanted to set it up at his home
3658 to open the car port automatically when it discovered the plate on his
3659 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3660 capable of placing his license plate number of a piece of cardboard to
3661 open his car port, men replied that it was always unlocked anyway. I
3662 guess for such use case it make sense. I am sure there are other use
3663 cases too, for those with imagination and a vision.&lt;/p&gt;
3664
3665 &lt;p&gt;If you want to build your own version of the Debian package, check
3666 out the upstream git source and symlink ./distros/debian to ./debian/
3667 before running &quot;debuild&quot; to build the source. Or wait a bit until the
3668 package show up in unstable.&lt;/p&gt;
3669 </description>
3670 </item>
3671
3672 <item>
3673 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
3674 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
3675 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
3676 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
3677 <description>&lt;p&gt;Around three years ago, I created
3678 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
3679 system&lt;/a&gt; to get a more practical solution in Debian for handing
3680 hardware related packages. A GUI system in the isenkram package will
3681 present a pop-up dialog when some hardware dongle supported by
3682 relevant packages in Debian is inserted into the machine. The same
3683 lookup mechanism to detect packages is available as command line
3684 tools in the isenkram-cli package. In addition to mapping hardware,
3685 it will also map kernel firmware files to packages and make it easy to
3686 install needed firmware packages automatically. The key for this
3687 system to work is a good way to map hardware to packages, in other
3688 words, allow packages to announce what hardware they will work
3689 with.&lt;/p&gt;
3690
3691 &lt;p&gt;I started by providing data files in the isenkram source, and
3692 adding code to download the latest version of these data files at run
3693 time, to ensure every user had the most up to date mapping available.
3694 I also added support for storing the mapping in the Packages file in
3695 the apt repositories, but did not push this approach because while I
3696 was trying to figure out how to best store hardware/package mappings,
3697 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3698 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
3699 add the hardware mapping into that data set to be able to use
3700 appstream as a data source, and this was accepted at least for the
3701 Debian version of appstream.&lt;/p&gt;
3702
3703 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
3704 and today I uploaded a new version 0.20 of isenkram adding support for
3705 appstream as a data source for mapping hardware to packages. The only
3706 package so far using appstream to announce its hardware support is my
3707 pymissile package. I got help from Matthias Klumpp with figuring out
3708 how do add the required
3709 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
3710 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
3711 this content:&lt;/p&gt;
3712
3713 &lt;blockquote&gt;&lt;pre&gt;
3714 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3715 &amp;lt;component&amp;gt;
3716 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
3717 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
3718 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
3719 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
3720 &amp;lt;description&amp;gt;
3721 &amp;lt;p&amp;gt;
3722 Pymissile provides a curses interface to control an original
3723 Marks and Spencer / Striker USB Missile Launcher, as well as a
3724 motion control script to allow a webcamera to control the
3725 launcher.
3726 &amp;lt;/p&amp;gt;
3727 &amp;lt;/description&amp;gt;
3728 &amp;lt;provides&amp;gt;
3729 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
3730 &amp;lt;/provides&amp;gt;
3731 &amp;lt;/component&amp;gt;
3732 &lt;/pre&gt;&lt;/blockquote&gt;
3733
3734 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
3735 which is a glob style match rule for hardware specific strings
3736 (modalias strings) provided by the Linux kernel. In this case, it
3737 will map to all USB devices with vendor code 1130 and product code
3738 0202.&lt;/p&gt;
3739
3740 &lt;p&gt;Note, it is important that the license of all the metadata files
3741 are compatible to have permissions to aggregate them into archive wide
3742 appstream files. Matthias suggested to use MIT or BSD licenses for
3743 these files. A challenge is figuring out a good id for the data, as
3744 it is supposed to be globally unique and shared across distributions
3745 (in other words, best to coordinate with upstream what to use). But
3746 it can be changed later or, so we went with the package name as
3747 upstream for this project is dormant.&lt;/p&gt;
3748
3749 &lt;p&gt;To get the metadata file installed in the correct location for the
3750 mirror update scripts to pick it up and include its content the
3751 appstream data source, the file must be installed in the binary
3752 package under /usr/share/appdata/. I did this by adding the following
3753 line to debian/pymissile.install:&lt;/p&gt;
3754
3755 &lt;blockquote&gt;&lt;pre&gt;
3756 debian/pymissile.metainfo.xml usr/share/appdata
3757 &lt;/pre&gt;&lt;/blockquote&gt;
3758
3759 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
3760 all packages useful on the current computer automatically, and the GUI
3761 pop-up handler will propose to install the package not already
3762 installed if a hardware dongle is inserted into the machine in
3763 question.&lt;/p&gt;
3764
3765 &lt;p&gt;Details of the modalias field in appstream is available from the
3766 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
3767
3768 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
3769 try running this command on the command line:&lt;/p&gt;
3770
3771 &lt;blockquote&gt;&lt;pre&gt;
3772 cat $(find /sys/devices/|grep modalias)
3773 &lt;/pre&gt;&lt;/blockquote&gt;
3774
3775 &lt;p&gt;To learn more about the isenkram system, please check out
3776 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3777 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3778 </description>
3779 </item>
3780
3781 <item>
3782 <title>The GNU General Public License is not magic pixie dust</title>
3783 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
3784 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
3785 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
3786 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
3787 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
3788 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
3789 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
3790 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
3791
3792 &lt;blockquote&gt;
3793
3794 &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;
3795
3796 &lt;blockquote&gt;
3797 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
3798
3799 The first step is to choose a
3800 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
3801 code.&lt;br/&gt;
3802
3803 The next step is, when someone fails to follow that copyleft license,
3804 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
3805
3806 and its a simple fact of our modern society that such type of
3807 work&lt;br/&gt;
3808
3809 is incredibly expensive to do and incredibly difficult to do.
3810 &lt;/blockquote&gt;
3811
3812 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
3813 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
3814 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
3815 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
3816
3817 &lt;p&gt;As the Debian Website
3818 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
3819 &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;
3820 imply, public domain and permissively licensed software can lead to
3821 the production of more proprietary software as people discover useful
3822 software, extend it and or incorporate it into their hardware or
3823 software products. Copyleft licenses such as the GNU GPL were created
3824 to close off this avenue to the production of proprietary software but
3825 such licenses are not enough. With the ongoing adoption of Free
3826 Software by individuals and groups, inevitably the community&#39;s
3827 expectations of license compliance are violated, usually out of
3828 ignorance of the way Free Software works, but not always. As Karen
3829 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
3830 Freedom&quot;&gt;FaiF&lt;/a&gt;
3831 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
3832 copyleft is nothing if no-one is willing and able to stand up in court
3833 to protect it. The reality of today&#39;s world is that legal
3834 representation is expensive, difficult and time consuming. With
3835 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
3836 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
3837 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
3838 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
3839 of the Linux project, Debian and other groups against GPL violations.
3840 In March the SFC supported a
3841 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
3842 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
3843 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
3844 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
3845 kernel. Since then two of their sponsors pulled corporate funding and
3846 conferences
3847 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
3848 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
3849 less on corporate funding and more on the broad community of
3850 individuals who support Free Software and copyleft. So the SFC has
3851 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
3852 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
3853 a community of folks who stand up for copyleft and the GPL by
3854 supporting their work on promoting and supporting copyleft and Free
3855 Software.&lt;/p&gt;
3856
3857 &lt;p&gt;If you support Free Software,
3858 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
3859 what the SFC do, agree with their
3860 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
3861 principles&lt;/a&gt;, are happy about their
3862 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
3863 work on a project that is an SFC
3864 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
3865 just want to stand up for copyleft, please join
3866 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
3867 Allan Webber&lt;/a&gt;,
3868 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
3869 Smith&lt;/a&gt;,
3870 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
3871 Bacon&lt;/a&gt;, myself and
3872 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
3873 becoming a
3874 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
3875 next week your donation will be
3876 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
3877 by an anonymous donor. Please also consider asking your employer to
3878 match your donation or become a sponsor of SFC. Don&#39;t forget to
3879 spread the word about your support for SFC via email, your blog and or
3880 social media accounts.&lt;/p&gt;
3881
3882 &lt;/blockquote&gt;
3883
3884 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3885 of Software Freedom Conservancy myself. Perhaps you should be a
3886 supporter too?&lt;/p&gt;
3887 </description>
3888 </item>
3889
3890 <item>
3891 <title>PGP key transition statement for key EE4E02F9</title>
3892 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3893 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3894 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3895 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3896 set it up properly. I wanted to generate it offline and have it
3897 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3898 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3899 time to sit down with an offline machine almost took forever. But
3900 finally I&#39;ve been able to complete the process, and have now moved
3901 from my old GPG key to a new GPG key. See
3902 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3903 full transition statement, signed with both my old and new key&lt;/a&gt; for
3904 the details. This is my new key:&lt;/p&gt;
3905
3906 &lt;pre&gt;
3907 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]
3908 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3909 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3910 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3911 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3912 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3913 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3914 &lt;/pre&gt;
3915
3916 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3917 my old key.&lt;/p&gt;
3918
3919 &lt;p&gt;If you signed my old key
3920 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3921 I&#39;d very much appreciate a signature on my new key, details and
3922 instructions in the transition statement. I m happy to reciprocate if
3923 you have a similarly signed transition statement to present.&lt;/p&gt;
3924 </description>
3925 </item>
3926
3927 <item>
3928 <title>The life and death of a laptop battery</title>
3929 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3930 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3931 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3932 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3933 But this do not last. The last few laptops gave me a feeling that
3934 within a year, the life time is just a fraction of what it used to be,
3935 and it slowly become painful to use the laptop without power connected
3936 all the time. Because of this, when I got a new Thinkpad X230 laptop
3937 about two years ago, I decided to monitor its battery state to have
3938 more hard facts when the battery started to fail.&lt;/p&gt;
3939
3940 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3941
3942 &lt;p&gt;First I tried to find a sensible Debian package to record the
3943 battery status, assuming that this must be a problem already handled
3944 by someone else. I found
3945 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3946 which collects statistics from the battery, but it was completely
3947 broken. I sent a few suggestions to the maintainer, but decided to
3948 write my own collector as a shell script while I waited for feedback
3949 from him. Via
3950 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3951 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3952 discovered
3953 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3954 available in Debian.&lt;/p&gt;
3955
3956 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3957 battery stats ever since. Now my
3958 /var/log/hjemmenett-battery-status.log file contain around 115,000
3959 measurements, from the time the battery was working great until now,
3960 when it is unable to charge above 7% of original capacity. My
3961 collector shell script is quite simple and look like this:&lt;/p&gt;
3962
3963 &lt;pre&gt;
3964 #!/bin/sh
3965 # Inspired by
3966 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3967 # See also
3968 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3969 logfile=/var/log/hjemmenett-battery-status.log
3970
3971 files=&quot;manufacturer model_name technology serial_number \
3972 energy_full energy_full_design energy_now cycle_count status&quot;
3973
3974 if [ ! -e &quot;$logfile&quot; ] ; then
3975 (
3976 printf &quot;timestamp,&quot;
3977 for f in $files; do
3978 printf &quot;%s,&quot; $f
3979 done
3980 echo
3981 ) &gt; &quot;$logfile&quot;
3982 fi
3983
3984 log_battery() {
3985 # Print complete message in one echo call, to avoid race condition
3986 # when several log processes run in parallel.
3987 msg=$(printf &quot;%s,&quot; $(date +%s); \
3988 for f in $files; do \
3989 printf &quot;%s,&quot; $(cat $f); \
3990 done)
3991 echo &quot;$msg&quot;
3992 }
3993
3994 cd /sys/class/power_supply
3995
3996 for bat in BAT*; do
3997 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3998 done
3999 &lt;/pre&gt;
4000
4001 &lt;p&gt;The script is called when the power management system detect a
4002 change in the power status (power plug in or out), and when going into
4003 and out of hibernation and suspend. In addition, it collect a value
4004 every 10 minutes. This make it possible for me know when the battery
4005 is discharging, charging and how the maximum charge change over time.
4006 The code for the Debian package
4007 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
4008 available on github&lt;/a&gt;.&lt;/p&gt;
4009
4010 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
4011
4012 &lt;pre&gt;
4013 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
4014 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
4015 [...]
4016 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4017 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4018 &lt;/pre&gt;
4019
4020 &lt;p&gt;I wrote a small script to create a graph of the charge development
4021 over time. This graph depicted above show the slow death of my laptop
4022 battery.&lt;/p&gt;
4023
4024 &lt;p&gt;But why is this happening? Why are my laptop batteries always
4025 dying in a year or two, while the batteries of space probes and
4026 satellites keep working year after year. If we are to believe
4027 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
4028 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
4029 chance, and the fix is to not charge the Lithium-ion batteries to 100%
4030 all the time, but to stay below 90% of full charge most of the time.
4031 I&#39;ve been told that the Tesla electric cars
4032 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
4033 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
4034 100% when preparing for a longer trip (not that I would want a car
4035 like Tesla where rights to privacy is abandoned, but that is another
4036 story), which I guess is the option we should have for laptops on
4037 Linux too.&lt;/p&gt;
4038
4039 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
4040 stop charging at 80%, unless requested to charge to 100% once in
4041 preparation for a longer trip? I found
4042 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
4043 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
4044 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
4045 load).&lt;/p&gt;
4046
4047 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
4048 at the start. I also wonder why the &quot;full capacity&quot; increases some
4049 times, and if it is possible to repeat the process to get the battery
4050 back to design capacity. And I wonder if the discharge and charge
4051 speed change over time, or if this stay the same. I did not yet try
4052 to write a tool to calculate the derivative values of the battery
4053 level, but suspect some interesting insights might be learned from
4054 those.&lt;/p&gt;
4055
4056 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
4057 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4058 packages instead of the tp-smapi-dkms package I had tried to use
4059 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
4060 and stop. I&#39;ve done so now, but expect my existing battery is toast
4061 and need to be replaced. The proposal is unfortunately Thinkpad
4062 specific.&lt;/p&gt;
4063 </description>
4064 </item>
4065
4066 <item>
4067 <title>New laptop - some more clues and ideas based on feedback</title>
4068 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
4069 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
4070 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
4071 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
4072 need for a new laptop, and provided very useful feedback. I wish to
4073 thank every one of these. Several pointed me to the possibility of
4074 fixing my X230, and I am already in the process of getting Lenovo to
4075 do so thanks to the on site, next day support contract covering the
4076 machine. But the battery is almost useless (I expect to replace it
4077 with a non-official battery) and I do not expect the machine to live
4078 for many more years, so it is time to plan its replacement. If I did
4079 not have a support contract, it was suggested to find replacement parts
4080 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
4081 might present a language barrier as I do not understand French.&lt;/p&gt;
4082
4083 &lt;p&gt;One tip I got was to use the
4084 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
4085 compare laptop models. It seem to have more models available than
4086 prisjakt.no. Another tip I got from someone I know have similar
4087 keyboard preferences was that the HP EliteBook 840 keyboard is not
4088 very good, and this matches my experience with earlier EliteBook
4089 keyboards I tested. Because of this, I will not consider it any further.
4090
4091 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
4092 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4093 (which is missing from the X240), and is working fairly well with
4094 Debian Sid/Unstable according to
4095 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
4096 got on the keyboard quality are not consistent. Some say the keyboard
4097 is good, others say it is ok, while others say it is not very good.
4098 Those with experience from X41 and and X60 agree that the X250
4099 keyboard is not as good as those trusty old laptops, and suggest I
4100 keep and fix my X230 instead of upgrading, or get a used X230 to
4101 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
4102 activity and battery status, which is very convenient on my X230. I&#39;m
4103 also told that the CPU fan is running very often, making it a bit
4104 noisy. In any case, the X250 do not work out of the box with Debian
4105 Stable/Jessie, one of my requirements.&lt;/p&gt;
4106
4107 &lt;p&gt;I have also gotten a few vendor proposals, one was
4108 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
4109 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
4110 The latter look very attractive to me.&lt;/p&gt;
4111
4112 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
4113 as I keep looking for a replacement.&lt;/p&gt;
4114
4115 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
4116 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
4117 different
4118 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
4119 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
4120 </description>
4121 </item>
4122
4123 <item>
4124 <title>Time to find a new laptop, as the old one is broken after only two years</title>
4125 <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>
4126 <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>
4127 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
4128 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
4129 replacement soon. The left 5 cm of the screen on my Thinkpad X230
4130 started flickering yesterday, and I suspect the cause is a broken
4131 cable, as changing the angle of the screen some times get rid of the
4132 flickering.&lt;/p&gt;
4133
4134 &lt;p&gt;My requirements have not really changed since I bought it, and is
4135 still as
4136 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
4137 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
4138 good help from
4139 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
4140 where I could select at least a few of the requirements (mouse pin,
4141 wifi, weight) and go through the rest manually. Three button mouse
4142 and a good keyboard is not available as an option, and all the three
4143 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
4144 G2) lack three mouse buttons). It is also unclear to me how good the
4145 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
4146 the keyboard, even if the quality and robustness in the X series have
4147 deteriorated since X41.&lt;/p&gt;
4148
4149 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
4150 seem sensible to me? Are there better services around to search the
4151 set of available laptops for features? Please send me an email if you
4152 have suggestions.&lt;/p&gt;
4153
4154 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
4155 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
4156 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
4157 </description>
4158 </item>
4159
4160 <item>
4161 <title>How to stay with sysvinit in Debian Jessie</title>
4162 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
4163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
4164 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
4165 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
4166 sysvinit as its boot system by default. But how can one keep using
4167 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
4168 courtesy of
4169 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
4170 Schubert&lt;/a&gt; and
4171 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
4172 McVittie&lt;/a&gt;.
4173
4174 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
4175 keep sysvinit as your boot system, create a file
4176 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
4177 you upgrade:&lt;/p&gt;
4178
4179 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4180 Package: systemd-sysv
4181 Pin: release o=Debian
4182 Pin-Priority: -1
4183 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4184
4185 &lt;p&gt;This file content will tell apt and aptitude to not consider
4186 installing systemd-sysv as part of any installation and upgrade
4187 solution when resolving dependencies, and thus tell it to avoid
4188 systemd as a default boot system. The end result should be that the
4189 upgraded system keep using sysvinit.&lt;/p&gt;
4190
4191 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
4192 get sysvinit installed by default (debootstrap used by
4193 debian-installer have no option for this), but one can tell the
4194 installer to switch to sysvinit before the first boot. Either by
4195 using a kernel argument to the installer, or by adding a line to the
4196 preseed file used. First, the kernel command line argument:
4197
4198 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4199 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
4200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4201
4202 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
4203
4204 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4205 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4206 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4207
4208 &lt;p&gt;One can of course also do this after the first boot by installing
4209 the sysvinit-core package.&lt;/p&gt;
4210
4211 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
4212 sysvinit boot sequence in Debian have several hardware specific bugs
4213 on Linux caused by the fact that it is unpredictable when hardware
4214 devices show up during boot. But on the other hand, the new default
4215 boot system still have a few rough edges I hope will be fixed before
4216 Jessie is released.&lt;/p&gt;
4217
4218 &lt;p&gt;Update 2014-11-26: Inspired by
4219 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
4220 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
4221 line.&lt;/p&gt;
4222 </description>
4223 </item>
4224
4225 <item>
4226 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
4227 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
4228 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
4229 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
4230 <description>&lt;p&gt;The right to communicate with your friends and family in private,
4231 without anyone snooping, is a right every citicen have in a liberal
4232 democracy. But this right is under serious attack these days.&lt;/p&gt;
4233
4234 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
4235 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
4236 the whisleblower Snowden) more expensive for Internet email,
4237 is to deliver all email using SMTP via Tor. Such SMTP option would be
4238 a nice addition to the FreedomBox project if we could send email
4239 between FreedomBox machines without leaking metadata about the emails
4240 to the people peeking on the wire. I
4241 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
4242 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
4243 lot of useful feedback and suggestions. It also became obvious to me
4244 that this was not a novel idea, as the same idea was tested and
4245 documented by Johannes Berg as early as 2006, and both
4246 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
4247 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
4248 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
4249
4250 &lt;p&gt;To implement such system one need to set up a Tor hidden service
4251 providing the SMTP protocol on port 25, and use email addresses
4252 looking like username@hidden-service-name.onion. With such addresses
4253 the connections to port 25 on hidden-service-name.onion using Tor will
4254 go to the correct SMTP server. To do this, one need to configure the
4255 Tor daemon to provide the hidden service and the mail server to accept
4256 emails for this .onion domain. To learn more about Exim configuration
4257 in Debian and test the design provided by Johannes Berg in his FAQ, I
4258 set out yesterday to create a Debian package for making it trivial to
4259 set up such SMTP over Tor service based on Debian. Getting it to work
4260 were fairly easy, and
4261 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
4262 source code for the Debian package&lt;/a&gt; is available from github. I
4263 plan to move it into Debian if further testing prove this to be a
4264 useful approach.&lt;/p&gt;
4265
4266 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
4267 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
4268 get rid of exim4). Install tor, clone the git repository mentioned
4269 above, build the deb and install it on the machine. Next, run
4270 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
4271 the instructions to get the service up and running. Restart tor and
4272 exim when it is done, and test mail delivery using swaks like
4273 this:&lt;/p&gt;
4274
4275 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4276 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
4277 --to fbx@dutlqrrmjhtfa3vp.onion
4278 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4279
4280 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
4281 address with your own address to test your server. :)&lt;/p&gt;
4282
4283 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
4284 easier and more automatic. Especially the tor setup need more work.
4285 Also, the package include a tor-smtp tool written in C, but its task
4286 should probably be rewritten in some script language to make the deb
4287 architecture independent. It would probably also make the code easier
4288 to review. The tor-smtp tool currently need to listen on a socket for
4289 exim to talk to it and is started using xinetd. It would be better if
4290 no daemon and no socket is needed. I suspect it is possible to get
4291 exim to run a command line tool for delivery instead of talking to a
4292 socket, and hope to figure out how in a future version of this
4293 system.&lt;/p&gt;
4294
4295 &lt;p&gt;Until I wipe my test machine, I can be reached using the
4296 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
4297 SMTorP. :)&lt;/p&gt;
4298 </description>
4299 </item>
4300
4301 <item>
4302 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
4303 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
4304 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
4305 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
4306 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
4307 alioth.debian.org, you know the web interface is fairly slow to
4308 operate. First you visit one web page, enter the moderation password
4309 and get a new page shown with a list of all the messages to moderate
4310 and various options for each email address. This take a while for
4311 every list you moderate, and you need to do it regularly to do a good
4312 job as a list moderator. But there is a quick alternative,
4313 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
4314 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
4315 to moderate in a fraction of a second. Here is a test run on two
4316 lists I recently took over:&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4319 % time listadmin xiph
4320 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4321 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4322
4323 real 0m1.709s
4324 user 0m0.232s
4325 sys 0m0.012s
4326 %
4327 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4328
4329 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
4330 there are no message in the moderation queue. Every morning I
4331 currently moderate 68 mailman lists, and it normally take around two
4332 minutes. When I took over the two pkg-xiph lists above a few days
4333 ago, there were 400 emails waiting in the moderator queue. It took me
4334 less than 15 minutes to process them all using the listadmin
4335 program.&lt;/p&gt;
4336
4337 &lt;p&gt;If you install
4338 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
4339 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
4340 with content like this, the moderation task is a breeze:&lt;/p&gt;
4341
4342 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4343 username username@example.org
4344 spamlevel 23
4345 default discard
4346 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
4347
4348 password secret
4349 adminurl https://{domain}/mailman/admindb/{list}
4350 mailman-list@lists.example.com
4351
4352 password hidden
4353 other-list@otherserver.example.org
4354 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4355
4356 &lt;p&gt;There are other options to set as well. Check the manual page to
4357 learn the details.&lt;/p&gt;
4358
4359 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
4360 the SSL certificate is self signed or not properly signed by a
4361 generally accepted signing authority, you can set a environment
4362 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
4363
4364 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4365 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
4366 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4367
4368 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
4369 can provide an argument to the listadmin script like I do in the
4370 initial screen dump (the xiph argument). Using an argument, only
4371 lists matching the argument string will be processed. This make it
4372 quick to accept messages if you notice the moderation request in your
4373 email.&lt;/p&gt;
4374
4375 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
4376 mailing lists, as I simply do not have time to spend on that if the
4377 process was any slower. The listadmin program have saved me hours of
4378 time I could spend elsewhere over the years. It truly is nice free
4379 software.&lt;/p&gt;
4380
4381 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4382 activities, please send Bitcoin donations to my address
4383 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4384
4385 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
4386 configuration example. Also, I&#39;ve been told that the
4387 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
4388 sure why.&lt;/p&gt;
4389 </description>
4390 </item>
4391
4392 <item>
4393 <title>Debian Jessie, PXE and automatic firmware installation</title>
4394 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
4395 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
4396 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
4397 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
4398 problem that the WiFi card require some firmware to work properly.
4399 And it has been a pain to fix this using preseeding in Debian.
4400 Normally something more is needed. But thanks to
4401 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
4402 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
4403 to do this using simple preseeding.&lt;/p&gt;
4404
4405 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
4406 firmware for the hardware found in the machine (actually, requested by
4407 the kernel modules for the hardware). (It can also install user space
4408 programs supporting the hardware detected, but that is not the focus
4409 of this story.)&lt;/p&gt;
4410
4411 &lt;p&gt;To get this working in the default installation, two preeseding
4412 values are needed. First, the isenkram-cli package must be installed
4413 into the target chroot (aka the hard drive) before tasksel is executed
4414 in the pkgsel step of the debian-installer system. This is done by
4415 preseeding the base-installer/includes debconf value to include the
4416 isenkram-cli package. The package name is next passed to debootstrap
4417 for installation. With the isenkram-cli package in place, tasksel
4418 will automatically use the isenkram tasks to detect hardware specific
4419 packages for the machine being installed and install them, because
4420 isenkram-cli contain tasksel tasks.&lt;/p&gt;
4421
4422 &lt;p&gt;Second, one need to enable the non-free APT repository, because
4423 most firmware unfortunately is non-free. This is done by preseeding
4424 the apt-mirror-setup step. This is unfortunate, but for a lot of
4425 hardware it is the only option in Debian.&lt;/p&gt;
4426
4427 &lt;p&gt;The end result is two lines needed in your preseeding file to get
4428 firmware installed automatically by the installer:&lt;/p&gt;
4429
4430 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4431 base-installer base-installer/includes string isenkram-cli
4432 apt-mirror-setup apt-setup/non-free boolean true
4433 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4434
4435 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
4436 both firmware and user space packages when using this method. It also
4437 do not work well, so use version 0.15 or later. Installing both
4438 firmware and user space packages might give you a bit more than you
4439 want, so I decided to split the tasksel task in two, one for firmware
4440 and one for user space programs. The firmware task is enabled by
4441 default, while the one for user space programs is not. This split is
4442 implemented in the package currently in unstable.&lt;/p&gt;
4443
4444 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
4445 this recipe work for you. :)&lt;/p&gt;
4446
4447 &lt;p&gt;So, I bet you are wondering, how can this work. First and
4448 foremost, it work because tasksel is modular, and driven by whatever
4449 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4450 isenkram-cli package place two files for tasksel to find. First there
4451 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
4452
4453 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4454 Task: isenkram-packages
4455 Section: hardware
4456 Description: Hardware specific packages (autodetected by isenkram)
4457 Based on the detected hardware various hardware specific packages are
4458 proposed.
4459 Test-new-install: show show
4460 Relevance: 8
4461 Packages: for-current-hardware
4462
4463 Task: isenkram-firmware
4464 Section: hardware
4465 Description: Hardware specific firmware packages (autodetected by isenkram)
4466 Based on the detected hardware various hardware specific firmware
4467 packages are proposed.
4468 Test-new-install: mark show
4469 Relevance: 8
4470 Packages: for-current-hardware-firmware
4471 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4472
4473 &lt;p&gt;The key parts are Test-new-install which indicate how the task
4474 should be handled and the Packages line referencing to a script in
4475 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4476 list of packages to install. The for-current-hardware-firmware script
4477 look like this to list relevant firmware for the machine:
4478
4479 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4480 #!/bin/sh
4481 #
4482 PATH=/usr/sbin:$PATH
4483 export PATH
4484 isenkram-autoinstall-firmware -l
4485 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4486
4487 &lt;p&gt;With those two pieces in place, the firmware is installed by
4488 tasksel during the normal d-i run. :)&lt;/p&gt;
4489
4490 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
4491 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
4492 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
4493 install.&lt;/p&gt;
4494
4495 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
4496 pilots in testing this feature, as isenkram is used there now to
4497 install firmware, replacing the earlier scripts.&lt;/p&gt;
4498 </description>
4499 </item>
4500
4501 <item>
4502 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
4503 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
4504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
4505 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
4506 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
4507 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4508 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
4509 on a screen normally showing the bread types and prizes:&lt;/p&gt;
4510
4511 &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;
4512
4513 &lt;p&gt;If it had booted as it was supposed to, I would never had known
4514 about this hidden Linux installation. It is interesting what
4515 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
4516 </description>
4517 </item>
4518
4519 <item>
4520 <title>New lsdvd release version 0.17 is ready</title>
4521 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
4522 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
4523 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
4524 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
4525 got a new set of developers a few weeks ago, after the original
4526 developer decided to step down and pass the project to fresh blood.
4527 This project is now maintained by Petter Reinholdtsen and Steve
4528 Dibb.&lt;/p&gt;
4529
4530 &lt;p&gt;I just wrapped up
4531 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
4532 new lsdvd release&lt;/a&gt;, available in git or from
4533 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
4534 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
4535 0.17.&lt;/p&gt;
4536
4537 &lt;ul&gt;
4538
4539 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
4540 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
4541 non-existant, to work around additional copy protection&lt;/li&gt;
4542 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
4543 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
4544 &lt;li&gt;Fix include orders&lt;/li&gt;
4545 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
4546 &lt;li&gt;Fix the chapter count&lt;/li&gt;
4547 &lt;li&gt;Make sure the array size and the array limit used when initialising
4548 the palette size is the same.&lt;/li&gt;
4549 &lt;li&gt;Fix array printing.&lt;/li&gt;
4550 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
4551 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
4552 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
4553 with more GCC compiler warnings.&lt;/li&gt;
4554
4555 &lt;/ul&gt;
4556
4557 &lt;p&gt;This change bring together patches for lsdvd in use in various
4558 Linux and Unix distributions, as well as patches submitted to the
4559 project the last nine years. Please check it out. :)&lt;/p&gt;
4560 </description>
4561 </item>
4562
4563 <item>
4564 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
4565 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
4566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
4567 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
4568 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4569 project&lt;/a&gt; provide a Linux solution for schools, including a
4570 powerful desktop with education software, a central server providing
4571 web pages, user database, user home directories, central login and PXE
4572 boot of both clients without disk and the installation to install Debian
4573 Edu on machines with disk (and a few other services perhaps to small
4574 to mention here). We in the Debian Edu team are currently working on
4575 the Jessie based version, trying to get everything in shape before the
4576 freeze, to avoid having to maintain our own package repository in the
4577 future. The
4578 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
4579 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
4580 work left. Some fatal problems block testing, breaking the installer,
4581 but it is possible to work around these to get anyway. Here is a
4582 recipe on how to get the installation limping along.&lt;/p&gt;
4583
4584 &lt;p&gt;First, download the test ISO via
4585 &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;,
4586 &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;
4587 or rsync (use
4588 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
4589 The ISO build was broken on Tuesday, so we do not get a new ISO every
4590 12 hours or so, but thankfully the ISO we already got we are able to
4591 install with some tweaking.&lt;/p&gt;
4592
4593 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
4594 (use Alt-Ctrl-F2), run&lt;/p&gt;
4595
4596 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4597 nano /usr/bin/edu-eatmydata-install
4598 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4599
4600 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
4601 optimization. Return to the installation, select the profile you want
4602 and continue. Without this change, exim4-config will fail to install
4603 due to a known bug in eatmydata.&lt;/p&gt;
4604
4605 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
4606 this do not work, figure out what your correct value would be. All my
4607 test machines need /dev/sda, so I have no advice if it do not fit
4608 your need.&lt;/p&gt;
4609
4610 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
4611 root after the initial boot from hard drive, and install the
4612 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4613 or mate. If you want several desktop options, install more than one
4614 metapackage. Once this is done, reboot and you should have a working
4615 graphical login screen. This workaround should no longer be needed
4616 once the education-tasks package version 1.801 enter testing in two
4617 days.&lt;/p&gt;
4618
4619 &lt;p&gt;I believe the ISO build will start working on two days when the new
4620 tasksel package enter testing and Steve McIntyre get a chance to
4621 update the debian-cd git repository. The eatmydata, grub and desktop
4622 issues are already fixed in unstable and testing, and should show up
4623 on the ISO as soon as the ISO build start working again. Well the
4624 eatmydata optimization is really just disabled. The proper fix
4625 require an upload by the eatmydata maintainer applying the patch
4626 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
4627 The rest have proper fixes in unstable.&lt;/p&gt;
4628
4629 &lt;p&gt;I hope this get you going with the installation testing, as we are
4630 quickly running out of time trying to get our Jessie based
4631 installation ready before the distribution freeze in a month.&lt;/p&gt;
4632 </description>
4633 </item>
4634
4635 <item>
4636 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
4637 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
4638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
4639 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
4640 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
4641 to handle my fairly large DVD collection. It is a nice command line
4642 tool to get details about a DVD, like title, tracks, track length,
4643 etc, in XML, Perl or human readable format. But lsdvd have not seen
4644 any new development since 2006 and had a few irritating bugs affecting
4645 its use with some DVDs. Upstream seemed to be dead, and in January I
4646 sent a small probe asking for a version control repository for the
4647 project, without any reply. But I use it regularly and would like to
4648 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
4649 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
4650 the project admin, and after getting a reply from him explaining that
4651 he was no longer interested in the project, I asked if I could take
4652 over. And yesterday, I became project admin.&lt;/p&gt;
4653
4654 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
4655 maintainer interested in joining forces to maintain the upstream
4656 project, and I hope we can get a new release out fairly quickly,
4657 collecting the patches spread around on the internet into on place.
4658 I&#39;ve added the relevant Debian patches to the freshly created git
4659 repository, and expect the Gentoo patches to make it too. If you got
4660 a DVD collection and care about command line tools, check out
4661 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
4662 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
4663 list&lt;/a&gt;. :)&lt;/p&gt;
4664 </description>
4665 </item>
4666
4667 <item>
4668 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
4669 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
4670 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
4671 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
4672 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
4673 a lot quicker. When we install more than 2000 packages in
4674 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
4675 tasksel in the installer, unpacking the binary packages take forever.
4676 A part of the slow I/O issue was discussed in
4677 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
4678 much file system sync-ing done by dpkg, which is the package
4679 responsible for unpacking the binary packages. Other parts (like code
4680 executed by postinst scripts) might also sync to disk during
4681 installation. All this sync-ing to disk do not really make sense to
4682 me. If the machine crash half-way through, I start over, I do not try
4683 to salvage the half installed system. So the failure sync-ing is
4684 supposed to protect against, hardware or system crash, is not really
4685 relevant while the installer is running.&lt;/p&gt;
4686
4687 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
4688 system sync()-ing in a fairly non-intrusive way, without the need to
4689 change the code in several packages. The idea is not new, but I have
4690 not heard anyone propose the approach using dpkg-divert before. It
4691 depend on the small and clever package
4692 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
4693 uses LD_PRELOAD to replace the system functions for syncing data to
4694 disk with functions doing nothing, thus allowing programs to live
4695 dangerous while speeding up disk I/O significantly. Instead of
4696 modifying the implementation of dpkg, apt and tasksel (which are the
4697 packages responsible for selecting, fetching and installing packages),
4698 it occurred to me that we could just divert the programs away, replace
4699 them with a simple shell wrapper calling
4700 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
4701 Two days ago I decided to test the idea, and wrapped up a simple
4702 implementation for the Debian Edu udeb.&lt;/p&gt;
4703
4704 &lt;p&gt;The effect was stunning. In my first test it reduced the running
4705 time of the pkgsel step (installing tasks) from 64 to less than 44
4706 minutes (20 minutes shaved off the installation) on an old Dell
4707 Latitude D505 machine. I am not quite sure what the optimised time
4708 would have been, as I messed up the testing a bit, causing the debconf
4709 priority to get low enough for two questions to pop up during
4710 installation. As soon as I saw the questions I moved the installation
4711 along, but do not know how long the question were holding up the
4712 installation. I did some more measurements using Debian Edu Jessie,
4713 and got these results. The time measured is the time stamp in
4714 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
4715 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
4716 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4717 timing thus do not depend on how quickly the user handle the tasksel
4718 dialog.&lt;/p&gt;
4719
4720 &lt;p&gt;&lt;table&gt;
4721
4722 &lt;tr&gt;
4723 &lt;th&gt;Machine/setup&lt;/th&gt;
4724 &lt;th&gt;Original tasksel&lt;/th&gt;
4725 &lt;th&gt;Optimised tasksel&lt;/th&gt;
4726 &lt;th&gt;Reduction&lt;/th&gt;
4727 &lt;/tr&gt;
4728
4729 &lt;tr&gt;
4730 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
4731 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
4732 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
4733 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
4734 &lt;/tr&gt;
4735
4736 &lt;tr&gt;
4737 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
4738 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
4739 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
4740 &lt;td&gt;23 min 40%&lt;/td&gt;
4741 &lt;/tr&gt;
4742
4743 &lt;tr&gt;
4744 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
4745 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
4746 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
4747 &lt;td&gt;11 min 50%&lt;/td&gt;
4748 &lt;/tr&gt;
4749
4750 &lt;tr&gt;
4751 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
4752 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
4753 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
4754 &lt;td&gt;2 min 33%&lt;/td&gt;
4755 &lt;/tr&gt;
4756
4757 &lt;tr&gt;
4758 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
4759 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
4760 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
4761 &lt;td&gt;4 min 21%&lt;/td&gt;
4762 &lt;/tr&gt;
4763
4764 &lt;/table&gt;&lt;/p&gt;
4765
4766 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
4767 time is spent downloading packages. The connection to the Internet
4768 was 100Mbit/s during testing, so downloading should not be a
4769 significant factor in the measurement. Download typically took a few
4770 seconds to a few minutes, depending on the amount of packages being
4771 installed.&lt;/p&gt;
4772
4773 &lt;p&gt;The speedup is implemented by using two hooks in
4774 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
4775 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
4776 finish-install.d hook to remove the divert at the end of the
4777 installation. I picked the pre-pkgsel.d hook instead of the
4778 post-base-installer.d hook because I test using an ISO without the
4779 eatmydata package included, and the post-base-installer.d hook in
4780 Debian Edu can only operate on packages included in the ISO. The
4781 negative effect of this is that I am unable to activate this
4782 optimization for the kernel installation step in d-i. If the code is
4783 moved to the post-base-installer.d hook, the speedup would be larger
4784 for the entire installation.&lt;/p&gt;
4785
4786 &lt;p&gt;I&#39;ve implemented this in the
4787 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
4788 git repository, and plan to provide the optimization as part of the
4789 Debian Edu installation. If you want to test this yourself, you can
4790 create two files in the installer (or in an udeb). One shell script
4791 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
4792
4793 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4794 #!/bin/sh
4795 set -e
4796 . /usr/share/debconf/confmodule
4797 info() {
4798 logger -t my-pkgsel &quot;info: $*&quot;
4799 }
4800 error() {
4801 logger -t my-pkgsel &quot;error: $*&quot;
4802 }
4803 override_install() {
4804 apt-install eatmydata || true
4805 if [ -x /target/usr/bin/eatmydata ] ; then
4806 for bin in dpkg apt-get aptitude tasksel ; do
4807 file=/usr/bin/$bin
4808 # Test that the file exist and have not been diverted already.
4809 if [ -f /target$file ] ; then
4810 info &quot;diverting $file using eatmydata&quot;
4811 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
4812 &gt; /target$file.edu
4813 chmod 755 /target$file.edu
4814 in-target dpkg-divert --package debian-edu-config \
4815 --rename --quiet --add $file
4816 ln -sf ./$bin.edu /target$file
4817 else
4818 error &quot;unable to divert $file, as it is missing.&quot;
4819 fi
4820 done
4821 else
4822 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
4823 fi
4824 }
4825
4826 override_install
4827 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4828
4829 &lt;p&gt;To clean up, another shell script should go into
4830 /usr/lib/finish-install.d/ with code like this:
4831
4832 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4833 #! /bin/sh -e
4834 . /usr/share/debconf/confmodule
4835 error() {
4836 logger -t my-finish-install &quot;error: $@&quot;
4837 }
4838 remove_install_override() {
4839 for bin in dpkg apt-get aptitude tasksel ; do
4840 file=/usr/bin/$bin
4841 if [ -x /target$file.edu ] ; then
4842 rm /target$file
4843 in-target dpkg-divert --package debian-edu-config \
4844 --rename --quiet --remove $file
4845 rm /target$file.edu
4846 else
4847 error &quot;Missing divert for $file.&quot;
4848 fi
4849 done
4850 sync # Flush file buffers before continuing
4851 }
4852
4853 remove_install_override
4854 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4855
4856 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
4857 edu-eatmydata-install and call it from the pre-pkgsel.d and
4858 finish-install.d scripts.&lt;/p&gt;
4859
4860 &lt;p&gt;By now you might ask if this change should get into the normal
4861 Debian installer too? I suspect it should, but am not sure the
4862 current debian-installer coordinators find it useful enough. It also
4863 depend on the side effects of the change. I&#39;m not aware of any, but I
4864 guess we will see if the change is safe after some more testing.
4865 Perhaps there is some package in Debian depending on sync() and
4866 fsync() having effect? Perhaps it should go into its own udeb, to
4867 allow those of us wanting to enable it to do so without affecting
4868 everyone.&lt;/p&gt;
4869
4870 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
4871 will break installation of all programs using gnutls because of
4872 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
4873 eatmydata package in Debian will solve it.&lt;/p&gt;
4874
4875 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
4876 the optimization work again. And I have discovered that the
4877 dpkg-divert trick is not really needed and implemented a slightly
4878 simpler approach as part of the debian-edu-install package. See
4879 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
4880
4881 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4882 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4883 triggering on i386 made it into testing, and broke this installation
4884 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4885 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4886 </description>
4887 </item>
4888
4889 <item>
4890 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4891 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4892 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4893 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4894 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4895 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4896 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4897 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4898 learn that there is a large set of publicly available key servers to
4899 use when looking for peoples public key. So far I have used
4900 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4901 were misbehaving, but those days are ended. The servers I have used
4902 up until yesterday have been slow and some times unavailable. I hope
4903 those problems are gone now.&lt;/p&gt;
4904
4905 &lt;p&gt;Behind the round robin DNS entry of the
4906 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4907 there is a pool of more than 100 keyservers which are checked every
4908 day to ensure they are well connected and up to date. It must be
4909 better than what I have used so far. :)&lt;/p&gt;
4910
4911 &lt;p&gt;Yesterdays speaker told me that the service is the default
4912 keyserver provided by the default configuration in GnuPG, but this do
4913 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4914
4915 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4916 line:&lt;/p&gt;
4917
4918 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4919 keyserver pool.sks-keyservers.net
4920 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4921
4922 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4923 entries in DNS. Just for fun, I did just that at work, so now every
4924 user of GnuPG at the University of Oslo should find a OpenGPG
4925 keyserver automatically should their need it:&lt;/p&gt;
4926
4927 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4928 % host -t srv _pgpkey-http._tcp.uio.no
4929 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4930 %
4931 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4932
4933 &lt;p&gt;Now if only
4934 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4935 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4936 very happy. It can look up a given key or search for a user ID, but I
4937 normally do not want that, but to find a trust path from my key to
4938 another key. Given a user ID or key ID, I would like to find (and
4939 download) the keys representing a signature path from my key to the
4940 key in question, to be able to get a trust path between the two keys.
4941 This is as far as I can tell not possible today. Perhaps something
4942 for a future version of the protocol?&lt;/p&gt;
4943 </description>
4944 </item>
4945
4946 <item>
4947 <title>From English wiki to translated PDF and epub via Docbook</title>
4948 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4950 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4951 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4952 project&lt;/a&gt; provide an instruction manual for teachers, system
4953 administrators and other users that contain useful tips for setting up
4954 and maintaining a Debian Edu installation. This text is about how the
4955 text processing of this manual is handled in the project.&lt;/p&gt;
4956
4957 &lt;p&gt;One goal of the project is to provide information in the native
4958 language of its users, and for this we need to handle translations.
4959 But we also want to make sure each language contain the same
4960 information, so for this we need a good way to keep the translations
4961 in sync. And we want it to be easy for our users to improve the
4962 documentation, avoiding the need to learn special formats or tools to
4963 contribute, and the obvious way to do this is to make it possible to
4964 edit the documentation using a web browser. We also want it to be
4965 easy for translators to keep the translation up to date, and give them
4966 help in figuring out what need to be translated. Here is the list of
4967 tools and the process we have found trying to reach all these
4968 goals.&lt;/p&gt;
4969
4970 &lt;p&gt;We maintain the authoritative source of our manual in the
4971 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4972 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4973 front page with references to the different chapters, several pages
4974 for each chapter, and finally one &quot;collection page&quot; gluing all the
4975 chapters together into one large web page (aka
4976 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4977 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4978 processing and translations. Thanks to the fact that the
4979 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4980 wiki.debian.org support exporting pages in
4981 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4982 the list of pages to export using the raw version of the AllInOne
4983 page, loop over each of them to generate a Docbook XML version of the
4984 manual. This process also download images and transform image
4985 references to use the locally downloaded images. The generated
4986 Docbook XML files are slightly broken, so some post-processing is done
4987 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4988 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4989 a handfull of images. The XML file can now be used to generate PDF, HTML
4990 and epub versions of the English manual. This is the basic step of
4991 our process, making PDF (using dblatex), HTML (using xsltproc) and
4992 epub (using dbtoepub) version from Docbook XML, and the resulting files
4993 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4994
4995 &lt;p&gt;But English documentation is not enough for us. We want translated
4996 documentation too, and we want to make it easy for translators to
4997 track the English original. For this we use the
4998 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4999 which allow us to transform the English Docbook XML file into a
5000 translation file (a .pot file), usable with the normal gettext based
5001 translation tools used by those translating free software. The pot
5002 file is used to create and maintain translation files (several .po
5003 files), which the translations update with the native language
5004 translations of all titles, paragraphs and blocks of text in the
5005 original. The next step is combining the original English Docbook XML
5006 and the translation file (say debian-edu-wheezy-manual.nb.po), to
5007 create a translated Docbook XML file (in this case
5008 debian-edu-wheezy-manual.nb.xml). This translated (or partly
5009 translated, if the translation is not complete) Docbook XML file can
5010 then be used like the original to create a PDF, HTML and epub version
5011 of the documentation.&lt;/p&gt;
5012
5013 &lt;p&gt;The translators use different tools to edit the .po files. We
5014 recommend using
5015 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
5016 while some use emacs and vi, others can use web based editors like
5017 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
5018 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
5019 is where the .po file end up, in our git repository. Updated
5020 translations can either be committed directly to git, or submitted as
5021 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
5022 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
5023
5024 &lt;p&gt;One challenge is images, which both might need to be translated (if
5025 they show translated user applications), and are needed in different
5026 formats when creating PDF and HTML versions (epub is a HTML version in
5027 this regard). For this we transform the original PNG images to the
5028 needed density and format during build, and have a way to provide
5029 translated images by storing translated versions in
5030 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
5031 package maintainers know more.&lt;/p&gt;
5032
5033 &lt;p&gt;If you wonder what the result look like, we provide
5034 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
5035 of the documentation packages on the web&lt;/a&gt;. See for example the
5036 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
5037 PDF version&lt;/a&gt; or the
5038 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
5039 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
5040 but perhaps it will be done in the future.&lt;/p&gt;
5041
5042 &lt;p&gt;To learn more, check out
5043 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
5044 debian-edu-doc package&lt;/a&gt;,
5045 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
5046 manual on the wiki&lt;/a&gt; and
5047 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
5048 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
5049 </description>
5050 </item>
5051
5052 <item>
5053 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
5054 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
5055 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
5056 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
5057 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
5058 related packages relevant for the computer installed automatically.
5059 So I implemented one, using
5060 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
5061 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
5062 run tasksel as user root. You should be presented with a new option,
5063 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
5064 select it, tasksel will install the packages isenkram claim is fit for
5065 the current hardware, hot pluggable or not.&lt;p&gt;
5066
5067 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
5068 description, and the other is the script used to extract the list of
5069 packages to install. The first part is in
5070 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
5071 this:&lt;/p&gt;
5072
5073 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5074 Task: isenkram
5075 Section: hardware
5076 Description: Hardware specific packages (autodetected by isenkram)
5077 Based on the detected hardware various hardware specific packages are
5078 proposed.
5079 Test-new-install: mark show
5080 Relevance: 8
5081 Packages: for-current-hardware
5082 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5083
5084 &lt;p&gt;The second part is in
5085 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
5086 this:&lt;/p&gt;
5087
5088 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5089 #!/bin/sh
5090 #
5091 (
5092 isenkram-lookup
5093 isenkram-autoinstall-firmware -l
5094 ) | sort -u
5095 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5096
5097 &lt;p&gt;All in all, a very short and simple implementation making it
5098 trivial to install the hardware dependent package we all may want to
5099 have installed on our machines. I&#39;ve not been able to find a way to
5100 get tasksel to tell you exactly which packages it plan to install
5101 before doing the installation. So if you are curious or careful,
5102 check the output from the isenkram-* command line tools first.&lt;/p&gt;
5103
5104 &lt;p&gt;The information about which packages are handling which hardware is
5105 fetched either from the isenkram package itself in
5106 /usr/share/isenkram/, from git.debian.org or from the APT package
5107 database (using the Modaliases header). The APT package database
5108 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5109 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
5110 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
5111 the python-apt code (bug
5112 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
5113 workaround I was able to get rid of the file descriptor leak and
5114 reduce the memory leak from ~30 MiB per hardware detection down to
5115 around 2 MiB per hardware detection. It should make the desktop
5116 daemon a lot more useful. The fix is in version 0.7 uploaded to
5117 unstable today.&lt;/p&gt;
5118
5119 &lt;p&gt;I believe the current way of mapping hardware to packages in
5120 Isenkram is is a good draft, but in the future I expect isenkram to
5121 use the AppStream data source for this. A proposal for getting proper
5122 AppStream support into Debian is floating around as
5123 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
5124 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
5125 project&lt;/a&gt; will take place this summer to improve the situation. I
5126 look forward to seeing the result, and welcome patches for isenkram to
5127 start using the information when it is ready.&lt;/p&gt;
5128
5129 &lt;p&gt;If you want your package to map to some specific hardware, either
5130 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
5131 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
5132 package&lt;/a&gt; or submit a bug report with the details to the isenkram
5133 package. See also
5134 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
5135 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
5136 the information will be migrated to AppStream eventually, but for the
5137 moment I got no better place to store it.&lt;/p&gt;
5138 </description>
5139 </item>
5140
5141 <item>
5142 <title>FreedomBox milestone - all packages now in Debian Sid</title>
5143 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
5144 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
5145 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
5146 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5147 project&lt;/a&gt; is working on providing the software and hardware to make
5148 it easy for non-technical people to host their data and communication
5149 at home, and being able to communicate with their friends and family
5150 encrypted and away from prying eyes. It is still going strong, and
5151 today a major mile stone was reached.&lt;/p&gt;
5152
5153 &lt;p&gt;Today, the last of the packages currently used by the project to
5154 created the system images were accepted into Debian Unstable. It was
5155 the freedombox-setup package, which is used to configure the images
5156 during build and on the first boot. Now all one need to get going is
5157 the build code from the freedom-maker git repository and packages from
5158 Debian. And once the freedombox-setup package enter testing, we can
5159 build everything directly from Debian. :)&lt;/p&gt;
5160
5161 &lt;p&gt;Some key packages used by Freedombox are
5162 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
5163 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
5164 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
5165 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
5166 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
5167 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
5168 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
5169 are plans to integrate more packages into the setup. User
5170 documentation is maintained on the Debian wiki. Please
5171 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
5172 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
5173
5174 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
5175 setup, run this on a Debian machine using a user with sudo rights to
5176 become root:&lt;/p&gt;
5177
5178 &lt;p&gt;&lt;pre&gt;
5179 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5180 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5181 u-boot-tools
5182 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5183 freedom-maker
5184 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5185 &lt;/pre&gt;&lt;/p&gt;
5186
5187 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5188 devices. See the README in the freedom-maker git repo for more
5189 details on the build. If you do not want all three images, trim the
5190 make line. Note that the virtualbox-image target is not really
5191 virtualbox specific. It create a x86 image usable in kvm, qemu,
5192 vmware and any other x86 virtual machine environment. You might need
5193 the version of vmdebootstrap in Jessie to get the build working, as it
5194 include fixes for a race condition with kpartx.&lt;/p&gt;
5195
5196 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5197 method, boot a Debian Wheezy ISO and use this boot argument to load
5198 the preseed values:&lt;/p&gt;
5199
5200 &lt;p&gt;&lt;pre&gt;
5201 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;
5202 &lt;/pre&gt;&lt;/p&gt;
5203
5204 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
5205 it still work.&lt;/p&gt;
5206
5207 &lt;p&gt;If you wonder how to help, one task you could look at is using
5208 systemd as the boot system. It will become the default for Linux in
5209 Jessie, so we need to make sure it is usable on the Freedombox. I did
5210 a simple test a few weeks ago, and noticed dnsmasq failed to start
5211 during boot when using systemd. I suspect there are other problems
5212 too. :) To detect problems, there is a test suite included, which can
5213 be run from the plinth web interface.&lt;/p&gt;
5214
5215 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5216 us get the new release published. :) Please join us on
5217 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5218 irc.debian.org)&lt;/a&gt; and
5219 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5220 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5221 </description>
5222 </item>
5223
5224 <item>
5225 <title>S3QL, a locally mounted cloud file system - nice free software</title>
5226 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
5227 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
5228 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
5229 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
5230 solution for use at home. My requirements are simple, it must be
5231 cheap and locally encrypted (in other words, I keep the encryption
5232 keys, the storage provider do not have access to my private files).
5233 One idea me and my friends had many years ago, before the cloud
5234 storage providers showed up, was to use Google mail as storage,
5235 writing a Linux block device storing blocks as emails in the mail
5236 service provided by Google, and thus get heaps of free space. On top
5237 of this one can add encryption, RAID and volume management to have
5238 lots of (fairly slow, I admit that) cheap and encrypted storage. But
5239 I never found time to implement such system. But the last few weeks I
5240 have looked at a system called
5241 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
5242 mounted network backed file system with the features I need.&lt;/p&gt;
5243
5244 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
5245 handling several different storage providers, any with Amazon S3,
5246 Google Drive or OpenStack API. There are heaps of such storage
5247 providers. S3QL can also use a local directory as storage, which
5248 combined with sshfs allow for file storage on any ssh server. S3QL
5249 include support for encryption, compression, de-duplication, snapshots
5250 and immutable file systems, allowing me to mount the remote storage as
5251 a local mount point, look at and use the files as if they were local,
5252 while the content is stored in the cloud as well. This allow me to
5253 have a backup that should survive fire. The file system can not be
5254 shared between several machines at the same time, as only one can
5255 mount it at the time, but any machine with the encryption key and
5256 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
5257
5258 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
5259 package is included already. So to get started, run &lt;tt&gt;apt-get
5260 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
5261 Greenqloud, after reading their nice recipe on
5262 &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
5263 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
5264 in Iceland more than those in USA when it come to keeping my personal
5265 data safe and private, and thus would rather spend money on a company
5266 in Iceland. Another nice recipe is available from the article
5267 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
5268 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
5269 Admin magazine. When the provider is picked, figure out how to get
5270 the API key needed to connect to the storage API. With Greencloud,
5271 the key did not show up until I had added payment details to my
5272 account.&lt;/p&gt;
5273
5274 &lt;p&gt;Armed with the API access details, it is time to create the file
5275 system. First, create a new bucket in the cloud. This bucket is the
5276 file system storage area. I picked a bucket name reflecting the
5277 machine that was going to store data there, but any name will do.
5278 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
5279 the API login and password, and a locally created password. Store it
5280 all in ~root/.s3ql/authinfo2 like this:
5281
5282 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5283 [s3c]
5284 storage-url: s3c://s.greenqloud.com:443/bucket-name
5285 backend-login: API-login
5286 backend-password: API-password
5287 fs-passphrase: local-password
5288 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5289
5290 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
5291 but any sensible way to create a fairly random password should do it.
5292 Armed with these details, it is now time to run mkfs, entering the API
5293 details and password to create it:&lt;/p&gt;
5294
5295 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5296 # mkdir -m 700 /var/lib/s3ql-cache
5297 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5298 --ssl s3c://s.greenqloud.com:443/bucket-name
5299 Enter backend login:
5300 Enter backend password:
5301 Before using S3QL, make sure to read the user&#39;s guide, especially
5302 the &#39;Important Rules to Avoid Loosing Data&#39; section.
5303 Enter encryption password:
5304 Confirm encryption password:
5305 Generating random encryption key...
5306 Creating metadata tables...
5307 Dumping metadata...
5308 ..objects..
5309 ..blocks..
5310 ..inodes..
5311 ..inode_blocks..
5312 ..symlink_targets..
5313 ..names..
5314 ..contents..
5315 ..ext_attributes..
5316 Compressing and uploading metadata...
5317 Wrote 0.00 MB of compressed metadata.
5318 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5319
5320 &lt;p&gt;The next step is mounting the file system to make the storage available.
5321
5322 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5323 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5324 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5325 Using 4 upload threads.
5326 Downloading and decompressing metadata...
5327 Reading metadata...
5328 ..objects..
5329 ..blocks..
5330 ..inodes..
5331 ..inode_blocks..
5332 ..symlink_targets..
5333 ..names..
5334 ..contents..
5335 ..ext_attributes..
5336 Mounting filesystem...
5337 # df -h /s3ql
5338 Filesystem Size Used Avail Use% Mounted on
5339 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
5340 #
5341 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5342
5343 &lt;p&gt;The file system is now ready for use. I use rsync to store my
5344 backups in it, and as the metadata used by rsync is downloaded at
5345 mount time, no network traffic (and storage cost) is triggered by
5346 running rsync. To unmount, one should not use the normal umount
5347 command, as this will not flush the cache to the cloud storage, but
5348 instead running the umount.s3ql command like this:
5349
5350 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5351 # umount.s3ql /s3ql
5352 #
5353 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5354
5355 &lt;p&gt;There is a fsck command available to check the file system and
5356 correct any problems detected. This can be used if the local server
5357 crashes while the file system is mounted, to reset the &quot;already
5358 mounted&quot; flag. This is what it look like when processing a working
5359 file system:&lt;/p&gt;
5360
5361 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5362 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
5363 Using cached metadata.
5364 File system seems clean, checking anyway.
5365 Checking DB integrity...
5366 Creating temporary extra indices...
5367 Checking lost+found...
5368 Checking cached objects...
5369 Checking names (refcounts)...
5370 Checking contents (names)...
5371 Checking contents (inodes)...
5372 Checking contents (parent inodes)...
5373 Checking objects (reference counts)...
5374 Checking objects (backend)...
5375 ..processed 5000 objects so far..
5376 ..processed 10000 objects so far..
5377 ..processed 15000 objects so far..
5378 Checking objects (sizes)...
5379 Checking blocks (referenced objects)...
5380 Checking blocks (refcounts)...
5381 Checking inode-block mapping (blocks)...
5382 Checking inode-block mapping (inodes)...
5383 Checking inodes (refcounts)...
5384 Checking inodes (sizes)...
5385 Checking extended attributes (names)...
5386 Checking extended attributes (inodes)...
5387 Checking symlinks (inodes)...
5388 Checking directory reachability...
5389 Checking unix conventions...
5390 Checking referential integrity...
5391 Dropping temporary indices...
5392 Backing up old metadata...
5393 Dumping metadata...
5394 ..objects..
5395 ..blocks..
5396 ..inodes..
5397 ..inode_blocks..
5398 ..symlink_targets..
5399 ..names..
5400 ..contents..
5401 ..ext_attributes..
5402 Compressing and uploading metadata...
5403 Wrote 0.89 MB of compressed metadata.
5404 #
5405 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5406
5407 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
5408 quick, about the same speed as local file access. Uploading large
5409 amount of data is to me limited by the bandwidth out of and into my
5410 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
5411 which is very close to my upload speed, and downloading the same
5412 Debian installation ISO gave me 610 kiB/s, close to my download speed.
5413 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
5414 network, not the file system code. I do not know what a good cache
5415 size would be, but suspect that the cache should e larger than your
5416 working set.&lt;/p&gt;
5417
5418 &lt;p&gt;I mentioned that only one machine can mount the file system at the
5419 time. If another machine try, it is told that the file system is
5420 busy:&lt;/p&gt;
5421
5422 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5423 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5424 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
5425 Using 8 upload threads.
5426 Backend reports that fs is still mounted elsewhere, aborting.
5427 #
5428 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5429
5430 &lt;p&gt;The file content is uploaded when the cache is full, while the
5431 metadata is uploaded once every 24 hour by default. To ensure the
5432 file system content is flushed to the cloud, one can either umount the
5433 file system, or ask S3QL to flush the cache and metadata using
5434 s3qlctrl:
5435
5436 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5437 # s3qlctrl upload-meta /s3ql
5438 # s3qlctrl flushcache /s3ql
5439 #
5440 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5441
5442 &lt;p&gt;If you are curious about how much space your data uses in the
5443 cloud, and how much compression and deduplication cut down on the
5444 storage usage, you can use s3qlstat on the mounted file system to get
5445 a report:&lt;/p&gt;
5446
5447 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5448 # s3qlstat /s3ql
5449 Directory entries: 9141
5450 Inodes: 9143
5451 Data blocks: 8851
5452 Total data size: 22049.38 MB
5453 After de-duplication: 21955.46 MB (99.57% of total)
5454 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
5455 Database size: 2.39 MB (uncompressed)
5456 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5457 #
5458 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5459
5460 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
5461 storage. I did not try to locate them all, but am aware of at least
5462 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
5463 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
5464 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
5465 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
5466 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
5467 accept payment in Bitcoin. Pick one that suit your need. Some of
5468 them provide several GiB of free storage, but the prize models are
5469 quite different and you will have to figure out what suits you
5470 best.&lt;/p&gt;
5471
5472 &lt;p&gt;While researching this blog post, I had a look at research papers
5473 and posters discussing the S3QL file system. There are several, which
5474 told me that the file system is getting a critical check by the
5475 science community and increased my confidence in using it. One nice
5476 poster is titled
5477 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
5478 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5479 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
5480 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5481 and Pamela Smith. Please have a look.&lt;/p&gt;
5482
5483 &lt;p&gt;Given my problems with different file systems earlier, I decided to
5484 check out the mounted S3QL file system to see if it would be usable as
5485 a home directory (in other word, that it provided POSIX semantics when
5486 it come to locking and umask handling etc). Running
5487 &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
5488 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
5489 no error was found. So the file system can be used for home
5490 directories, if one chooses to do so.&lt;/p&gt;
5491
5492 &lt;p&gt;If you do not want a locally file system, and want something that
5493 work without the Linux fuse file system, I would like to mention the
5494 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
5495 provide locally encrypted backup using a command line client. It have
5496 a nicer access control system, where one can split out read and write
5497 access, allowing some systems to write to the backup and others to
5498 only read from it.&lt;/p&gt;
5499
5500 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5501 activities, please send Bitcoin donations to my address
5502 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5503 </description>
5504 </item>
5505
5506 <item>
5507 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
5508 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
5509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
5510 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
5511 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5512 project&lt;/a&gt; is working on providing the software and hardware for
5513 making it easy for non-technical people to host their data and
5514 communication at home, and being able to communicate with their
5515 friends and family encrypted and away from prying eyes. It has been
5516 going on for a while, and is slowly progressing towards a new test
5517 release (0.2).&lt;/p&gt;
5518
5519 &lt;p&gt;And what day could be better than the Pi day to announce that the
5520 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
5521 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5522 system), and can also be installed using a Debian installer preseed
5523 file. The Debian based Freedombox is now based on Debian Jessie,
5524 where most of the needed packages used are already present. Only one,
5525 the freedombox-setup package, is missing. To try to build your own
5526 boot image to test the current status, fetch the freedom-maker scripts
5527 and build using
5528 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
5529 with a user with sudo access to become root:
5530
5531 &lt;pre&gt;
5532 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5533 freedom-maker
5534 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5535 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5536 u-boot-tools
5537 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5538 &lt;/pre&gt;
5539
5540 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5541 devices. See the README for more details on the build. If you do not
5542 want all three images, trim the make line. But note that thanks to &lt;a
5543 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
5544 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
5545 kpartx call.&lt;/p&gt;
5546
5547 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5548 method, boot a Debian Wheezy ISO and use this boot argument to load
5549 the preseed values:&lt;/p&gt;
5550
5551 &lt;pre&gt;
5552 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;
5553 &lt;/pre&gt;
5554
5555 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
5556 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
5557 currently hang while setting up APT sources. Killing the
5558 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
5559 installation will get the installation going. This affect all
5560 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
5561
5562 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
5563 us get the new release published. :) Please join us on
5564 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
5565 irc.debian.org)&lt;/a&gt; and
5566 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5567 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5568 </description>
5569 </item>
5570
5571 <item>
5572 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
5573 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
5574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
5575 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
5576 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
5577 innetgr tools, because I needed them in
5578 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
5579 ng-utils, and it has served me well. I placed the project under the
5580 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
5581 repository. But many years ago, the CVS repository was dropped (lost,
5582 not migrated to new hardware, not sure), and the project have lacked a
5583 proper home since then.&lt;/p&gt;
5584
5585 &lt;p&gt;Last summer, I had a look at the package and made a new release
5586 fixing a irritating crash bug, but was unable to store the changes in
5587 a proper source control system. I applied for a project on
5588 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
5589 to follow up on it. Until today. :)&lt;/p&gt;
5590
5591 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
5592 now have a new home, and a git repository with the highlight of the
5593 history of the project. I published all release tarballs and imported
5594 them into the git repository. As the project is really stable and not
5595 expected to gain new features any time soon, I decided to make a new
5596 release and call it 1.0. Visit the new project home on
5597 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
5598 if you want to check it out. The new version is also uploaded into
5599 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
5600 </description>
5601 </item>
5602
5603 <item>
5604 <title>Testing sysvinit from experimental in Debian Hurd</title>
5605 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
5606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
5607 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
5608 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
5609 their changes into sysvinit, to allow them to use the normal sysvinit
5610 boot system instead of their old one. This follow up on the
5611 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
5612 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
5613 get Debian on Hurd working more like Debian on Linux. To get started,
5614 I downloaded a prebuilt hard disk image from
5615 &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;,
5616 and started it using virt-manager.&lt;/p&gt;
5617
5618 &lt;p&gt;The first think I had to do after logging in (root without any
5619 password) was to get the network operational. I followed
5620 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
5621 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
5622 commands as root to get the machine to accept a IP address from the
5623 kvm internal DHCP server:&lt;/p&gt;
5624
5625 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5626 settrans -fgap /dev/netdde /hurd/netdde
5627 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
5628 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
5629 dhclient /dev/eth0
5630 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5631
5632 &lt;p&gt;After this, the machine had internet connectivity, and I could
5633 upgrade it and install the sysvinit packages from experimental and
5634 enable it as the default boot system in Hurd.&lt;/p&gt;
5635
5636 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
5637 running on the machine it for ssh login to work a password need to be
5638 set. Also, note that a bug somewhere in openssh on Hurd block
5639 compression from working. Remember to turn that off on the client
5640 side.&lt;/p&gt;
5641
5642 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
5643 stuff:&lt;/p&gt;
5644
5645 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5646 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
5647 deb http://http.debian.net/debian/ experimental main
5648 EOF
5649 apt-get update
5650 apt-get dist-upgrade
5651 apt-get install -t experimental initscripts sysv-rc sysvinit \
5652 sysvinit-core sysvinit-utils
5653 update-alternatives --config runsystem
5654 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5655
5656 &lt;p&gt;To reboot after switching boot system, you have to use
5657 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
5658 yet a sysvinit process able to receive the signals from the normal
5659 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
5660 upgrading every package and rebooting, the network come up with DHCP
5661 after boot as it should, and the settrans/pkill hack mentioned at the
5662 start is no longer needed. But for some strange reason, there are no
5663 longer any login prompt in the virtual console, so I logged in using
5664 ssh instead.
5665
5666 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
5667 fail some times. No idea what the cause is, but hope the Hurd porters
5668 figure it out. At least Justus said on IRC (#debian-hurd on
5669 irc.debian.org) that they are aware of the problem. A way to reduce
5670 the impact is to upgrade to the Hurd packages built by Justus by
5671 adding this repository to the machine:&lt;/p&gt;
5672
5673 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5674 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
5675 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5676 EOF
5677 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5678
5679 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
5680 http://ftp.debian-ports.org/debian, because some of the packages in
5681 unstable do not yet include the required patches that are lingering in
5682 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
5683
5684 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5685 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
5686 i emacs - GNU Emacs editor (metapackage)
5687 i gdb - GNU Debugger
5688 i hurd-recommended - Miscellaneous translators
5689 i isc-dhcp-client - ISC DHCP client
5690 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5691 i libc-bin - Embedded GNU C Library: Binaries
5692 i libc-dev-bin - Embedded GNU C Library: Development binaries
5693 i libc0.3 - Embedded GNU C Library: Shared libraries
5694 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5695 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5696 i multiarch-support - Transitional package to ensure multiarch compatibilit
5697 i A x11-common - X Window System (X.Org) infrastructure
5698 i xorg - X.Org X Window System
5699 i A xserver-xorg - X.Org X server
5700 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5701 #
5702 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5703
5704 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
5705 X.org did not work out of the box and I never took the time to follow
5706 the porters instructions to fix it. This time I was interested in the
5707 command line stuff.&lt;p&gt;
5708 </description>
5709 </item>
5710
5711 <item>
5712 <title>New chrpath release 0.16</title>
5713 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
5714 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
5715 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
5716 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
5717 find problems in C, C++ and Java code using static source code
5718 analysis. It can detect a lot of different problems, and is very
5719 useful to find memory and locking bugs in the error handling part of
5720 the source. The company behind it provide
5721 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
5722 a community service&lt;/a&gt;, and many hundred free software projects are
5723 already checked. A few days ago I decided to have a closer look at
5724 the Coverity system, and discovered that the
5725 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
5726 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
5727 projects I am involved with was already registered. But these are
5728 fairly big, and I would also like to have a small and easy project to
5729 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
5730 checking of the chrpath project&lt;/a&gt;. It was
5731 added to the checker and discovered seven potential defects. Six of
5732 these were real, mostly resource &quot;leak&quot; when the program detected an
5733 error. Nothing serious, as the resources would be released a fraction
5734 of a second later when the program exited because of the error, but it
5735 is nice to do it right in case the source of the program some time in
5736 the future end up in a library. Having fixed all defects and added
5737 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
5738 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
5739 publish a new release. These are the release notes:&lt;/p&gt;
5740
5741 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
5742
5743 &lt;ul&gt;
5744
5745 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
5746 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
5747 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
5748
5749 &lt;/ul&gt;
5750
5751 &lt;p&gt;You can
5752 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5753 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
5754 project if something is wrong with the new release. The test suite
5755 did not discover any old errors, so if you find a new one, please also
5756 include a test suite check.&lt;/p&gt;
5757 </description>
5758 </item>
5759
5760 <item>
5761 <title>New chrpath release 0.15</title>
5762 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
5763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
5764 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
5765 <description>&lt;p&gt;After many years break from the package and a vain hope that
5766 development would be continued by someone else, I finally pulled my
5767 acts together this morning and wrapped up a new release of chrpath,
5768 the command line tool to modify the rpath and runpath of already
5769 compiled ELF programs. The update was triggered by the persistence of
5770 Isha Vishnoi at IBM, which needed a new config.guess file to get
5771 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
5772 is working on. I checked the
5773 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
5774 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
5775 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
5776 packages for interesting patches (failed to find the source from
5777 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5778 These are the release notes:&lt;/p&gt;
5779
5780 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
5781
5782 &lt;ul&gt;
5783
5784 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
5785 with newer architectures. Thanks to isha vishnoi for the heads
5786 up.&lt;/li&gt;
5787
5788 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
5789
5790 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5791 Matthias Klose.&lt;/li&gt;
5792
5793 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
5794 Petr Machata found in Fedora.&lt;/li&gt;
5795
5796 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
5797 .dynamic is a NULL terminated string. Based on patch found in
5798 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
5799
5800 &lt;/ul&gt;
5801
5802 &lt;p&gt;You can
5803 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
5804 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
5805 project if something is wrong with the new release. The test suite
5806 did not discover any old errors, so if you find a new one, please also
5807 include a testsuite check.&lt;/p&gt;
5808 </description>
5809 </item>
5810
5811 <item>
5812 <title>Debian init.d boot script example for rsyslog</title>
5813 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
5814 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
5815 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
5816 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
5817 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
5818 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
5819 init.d scripts at all. Here is an example init.d script, ie a rewrite
5820 of /etc/init.d/rsyslog:&lt;/p&gt;
5821
5822 &lt;p&gt;&lt;pre&gt;
5823 #!/lib/init/init-d-script
5824 ### BEGIN INIT INFO
5825 # Provides: rsyslog
5826 # Required-Start: $remote_fs $time
5827 # Required-Stop: umountnfs $time
5828 # X-Stop-After: sendsigs
5829 # Default-Start: 2 3 4 5
5830 # Default-Stop: 0 1 6
5831 # Short-Description: enhanced syslogd
5832 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5833 # It is quite compatible to stock sysklogd and can be
5834 # used as a drop-in replacement.
5835 ### END INIT INFO
5836 DESC=&quot;enhanced syslogd&quot;
5837 DAEMON=/usr/sbin/rsyslogd
5838 &lt;/pre&gt;&lt;/p&gt;
5839
5840 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
5841 script was 137 lines, and the above is just 15 lines, most of it meta
5842 info/comments.&lt;/p&gt;
5843
5844 &lt;p&gt;How to do this, you ask? Well, one create a new script
5845 /lib/init/init-d-script looking something like this:
5846
5847 &lt;p&gt;&lt;pre&gt;
5848 #!/bin/sh
5849
5850 # Define LSB log_* functions.
5851 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
5852 # and status_of_proc is working.
5853 . /lib/lsb/init-functions
5854
5855 #
5856 # Function that starts the daemon/service
5857
5858 #
5859 do_start()
5860 {
5861 # Return
5862 # 0 if daemon has been started
5863 # 1 if daemon was already running
5864 # 2 if daemon could not be started
5865 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
5866 || return 1
5867 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5868 $DAEMON_ARGS \
5869 || return 2
5870 # Add code here, if necessary, that waits for the process to be ready
5871 # to handle requests from services started subsequently which depend
5872 # on this one. As a last resort, sleep for some time.
5873 }
5874
5875 #
5876 # Function that stops the daemon/service
5877 #
5878 do_stop()
5879 {
5880 # Return
5881 # 0 if daemon has been stopped
5882 # 1 if daemon was already stopped
5883 # 2 if daemon could not be stopped
5884 # other if a failure occurred
5885 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5886 RETVAL=&quot;$?&quot;
5887 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5888 # Wait for children to finish too if this is a daemon that forks
5889 # and if the daemon is only ever run from this initscript.
5890 # If the above conditions are not satisfied then add some other code
5891 # that waits for the process to drop all resources that could be
5892 # needed by services started subsequently. A last resort is to
5893 # sleep for some time.
5894 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5895 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5896 # Many daemons don&#39;t delete their pidfiles when they exit.
5897 rm -f $PIDFILE
5898 return &quot;$RETVAL&quot;
5899 }
5900
5901 #
5902 # Function that sends a SIGHUP to the daemon/service
5903 #
5904 do_reload() {
5905 #
5906 # If the daemon can reload its configuration without
5907 # restarting (for example, when it is sent a SIGHUP),
5908 # then implement that here.
5909 #
5910 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5911 return 0
5912 }
5913
5914 SCRIPTNAME=$1
5915 scriptbasename=&quot;$(basename $1)&quot;
5916 echo &quot;SN: $scriptbasename&quot;
5917 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5918 script=&quot;$1&quot;
5919 shift
5920 . $script
5921 else
5922 exit 0
5923 fi
5924
5925 NAME=$(basename $DAEMON)
5926 PIDFILE=/var/run/$NAME.pid
5927
5928 # Exit if the package is not installed
5929 #[ -x &quot;$DAEMON&quot; ] || exit 0
5930
5931 # Read configuration variable file if it is present
5932 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5933
5934 # Load the VERBOSE setting and other rcS variables
5935 . /lib/init/vars.sh
5936
5937 case &quot;$1&quot; in
5938 start)
5939 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5940 do_start
5941 case &quot;$?&quot; in
5942 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5943 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5944 esac
5945 ;;
5946 stop)
5947 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5948 do_stop
5949 case &quot;$?&quot; in
5950 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5951 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5952 esac
5953 ;;
5954 status)
5955 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5956 ;;
5957 #reload|force-reload)
5958 #
5959 # If do_reload() is not implemented then leave this commented out
5960 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5961 #
5962 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5963 #do_reload
5964 #log_end_msg $?
5965 #;;
5966 restart|force-reload)
5967 #
5968 # If the &quot;reload&quot; option is implemented then remove the
5969 # &#39;force-reload&#39; alias
5970 #
5971 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5972 do_stop
5973 case &quot;$?&quot; in
5974 0|1)
5975 do_start
5976 case &quot;$?&quot; in
5977 0) log_end_msg 0 ;;
5978 1) log_end_msg 1 ;; # Old process is still running
5979 *) log_end_msg 1 ;; # Failed to start
5980 esac
5981 ;;
5982 *)
5983 # Failed to stop
5984 log_end_msg 1
5985 ;;
5986 esac
5987 ;;
5988 *)
5989 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5990 exit 3
5991 ;;
5992 esac
5993
5994 :
5995 &lt;/pre&gt;&lt;/p&gt;
5996
5997 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5998 lot. I did not really polish the approach, so it might not always
5999 work out of the box, but you get the idea. I did not try very hard to
6000 optimize it nor make it more robust either.&lt;/p&gt;
6001
6002 &lt;p&gt;A better argument for switching init system in Debian than reducing
6003 the size of init scripts (which is a good thing to do anyway), is to
6004 get boot system that is able to handle the kernel events sensibly and
6005 robustly, and do not depend on the boot to run sequentially. The boot
6006 and the kernel have not behaved sequentially in years.&lt;/p&gt;
6007 </description>
6008 </item>
6009
6010 <item>
6011 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
6012 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
6013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
6014 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
6015 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
6016 remote display access is the preferred solution with oVirt and RedHat
6017 Enterprise Virtualization, and I was sad to discover the other day
6018 that the browser plugin needed to use these systems seamlessly was
6019 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
6020 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
6021 2013-04-01, so I decided to wrap up a package based on the great work
6022 from Cajus Pollmeier and put it in a collab-maint maintained git
6023 repository to get a package I could use. I would very much like
6024 others to help me maintain the package (or just take over, I do not
6025 mind), but as no-one had volunteered so far, I just uploaded it to
6026 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
6027
6028 &lt;p&gt;The source is now available from
6029 &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;
6030 </description>
6031 </item>
6032
6033 <item>
6034 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
6035 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
6036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
6037 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
6038 <description>&lt;p&gt;The
6039 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
6040 program is a a very nice system to create virtual machine images. It
6041 create a image file, add a partition table, mount it and run
6042 debootstrap in the mounted directory to create a Debian system on a
6043 stick. Yesterday, I decided to try to teach it how to make images for
6044 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
6045 of a plan to simplify the build system for
6046 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
6047 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
6048 the virtualbox images, but its current build system made multistrap
6049 based system for Dreamplug images, and it is lacking support for
6050 Raspberry Pi.&lt;/p&gt;
6051
6052 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
6053 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6054 code and adjusted it to be able to build armel images on my amd64
6055 Debian laptop. I ended up giving vmdebootstrap five new options,
6056 allowing me to replicate the image creation process I use to make
6057 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
6058 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
6059 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
6060 call debootstrap with --foreign and to copy the handler into the
6061 generated chroot before running the second stage. This allow
6062 vmdebootstrap to create armel images on an amd64 host. Next I added
6063 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
6064 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
6065 given file system type, allowing me to create an image with a vfat
6066 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
6067 variant&lt;/tt&gt; option to allow me to create smaller images without the
6068 Debian base system packages installed. Finally, I added an option
6069 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
6070 as a boot loader. It is not needed on the Raspberry Pi and probably
6071 most other non-x86 architectures. The changes were accepted by the
6072 upstream author of vmdebootstrap yesterday and today, and is now
6073 available from
6074 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
6075 upstream project page&lt;/a&gt;.&lt;/p&gt;
6076
6077 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
6078 create a small script (the customize script) to add the non-free
6079 binary blob needed to boot the Raspberry Pi and the APT source
6080 list:&lt;/p&gt;
6081
6082 &lt;p&gt;&lt;pre&gt;
6083 #!/bin/sh
6084 set -e # Exit on first error
6085 rootdir=&quot;$1&quot;
6086 cd &quot;$rootdir&quot;
6087 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
6088 deb http://http.debian.net/debian/ jessie main contrib non-free
6089 EOF
6090 # Install non-free binary blob needed to boot Raspberry Pi. This
6091 # install a kernel somewhere too.
6092 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6093 -O $rootdir/usr/bin/rpi-update
6094 chmod a+x $rootdir/usr/bin/rpi-update
6095 mkdir -p $rootdir/lib/modules
6096 touch $rootdir/boot/start.elf
6097 chroot $rootdir rpi-update
6098 &lt;/pre&gt;&lt;/p&gt;
6099
6100 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
6101 to build the image:&lt;/p&gt;
6102
6103 &lt;pre&gt;
6104 sudo ./vmdebootstrap \
6105 --variant minbase \
6106 --arch armel \
6107 --distribution jessie \
6108 --mirror http://http.debian.net/debian \
6109 --image test.img \
6110 --size 600M \
6111 --bootsize 64M \
6112 --boottype vfat \
6113 --log-level debug \
6114 --verbose \
6115 --no-kernel \
6116 --no-extlinux \
6117 --root-password raspberry \
6118 --hostname raspberrypi \
6119 --foreign /usr/bin/qemu-arm-static \
6120 --customize `pwd`/customize \
6121 --package netbase \
6122 --package git-core \
6123 --package binutils \
6124 --package ca-certificates \
6125 --package wget \
6126 --package kmod
6127 &lt;/pre&gt;&lt;/p&gt;
6128
6129 &lt;p&gt;The list of packages being installed are the ones needed by
6130 rpi-update to make the image bootable on the Raspberry Pi, with the
6131 exception of netbase, which is needed by debootstrap to find
6132 /etc/hosts with the minbase variant. I really wish there was a way to
6133 set up an Raspberry Pi using only packages in the Debian archive, but
6134 that is not possible as far as I know, because it boots from the GPU
6135 using a non-free binary blob.&lt;/p&gt;
6136
6137 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
6138 probably a few others installed. I have not checked the complete
6139 build dependency list.&lt;/p&gt;
6140
6141 &lt;p&gt;The resulting image will not use the hardware floating point unit
6142 on the Raspberry PI, because the armel architecture in Debian is not
6143 optimized for that use. So the images created will be a bit slower
6144 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
6145 </description>
6146 </item>
6147
6148 <item>
6149 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
6150 <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>
6151 <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>
6152 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
6153 <description>&lt;p&gt;The last few days I came across a few good causes that should get
6154 wider attention. I recommend signing and donating to each one of
6155 these. :)&lt;/p&gt;
6156
6157 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
6158 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
6159 Women program which is a Google Summer of Code like initiative to get
6160 more women involved in free software. One debian sponsor has offered
6161 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
6162 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
6163 hope you will to. :)&lt;/p&gt;
6164
6165 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
6166 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
6167 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
6168 take place these days, and their need to fund the work. I&#39;ve already
6169 donated. Are you next?&lt;/p&gt;
6170
6171 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
6172 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
6173 statement under the heading
6174 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
6175 Access&lt;/a&gt; for those of us asking for more focus on open access in the
6176 Norwegian government. So far 499 signatures. I hope you will sign it
6177 too.&lt;/p&gt;
6178 </description>
6179 </item>
6180
6181 <item>
6182 <title>Videos about the Freedombox project - for inspiration and learning</title>
6183 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
6184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
6185 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
6186 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
6187 project&lt;/a&gt; have been going on for a while, and have presented the
6188 vision, ideas and solution several places. Here is a little
6189 collection of videos of talks and presentation of the project.&lt;/p&gt;
6190
6191 &lt;ul&gt;
6192
6193 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
6194 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
6195
6196 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
6197 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6198
6199 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
6200 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6201 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
6202 (Youtube)&lt;/li&gt;
6203
6204 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
6205 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
6206
6207 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
6208 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6209
6210 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
6211 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6212 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
6213
6214 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
6215 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
6216 (Youtube)&lt;/li&gt;
6217
6218 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
6219 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
6220
6221 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
6222 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
6223
6224 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
6225 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
6226 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
6227
6228 &lt;/ul&gt;
6229
6230 &lt;p&gt;A larger list is available from
6231 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
6232 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
6233
6234 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
6235 Jessie is coming along quite well, and soon both Owncloud and using
6236 Tor should be available for testers of the Freedombox solution. :) In
6237 a few weeks I hope everything needed to test it is included in Debian.
6238 The withsqlite package is already in Debian, and the plinth package is
6239 pending in NEW. The third and vital part of that puzzle is the
6240 metapackage/setup framework, which is still pending an upload. Join
6241 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
6242 (#freedombox on irc.debian.org)&lt;/a&gt; and
6243 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6244 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6245 </description>
6246 </item>
6247
6248 <item>
6249 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
6250 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
6251 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
6252 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
6253 <description>&lt;p&gt;I was introduced to the
6254 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
6255 in 2010, when Eben Moglen presented his vision about serving the need
6256 of non-technical people to keep their personal information private and
6257 within the legal protection of their own homes. The idea is to give
6258 people back the power over their network and machines, and return
6259 Internet back to its intended peer-to-peer architecture. Instead of
6260 depending on a central service, the Freedombox will give everyone
6261 control over their own basic infrastructure.&lt;/p&gt;
6262
6263 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
6264 taken priority. But this summers nasty news about the misuse of trust
6265 and privilege exercised by the &quot;western&quot; intelligence gathering
6266 communities increased my eagerness to contribute to a point where I
6267 actually started working on the project a while back.&lt;/p&gt;
6268
6269 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
6270 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
6271 create a simple and cheap Debian based appliance that anyone can hook
6272 up in their home and get access to secure and private services and
6273 communication. The initial deployment platform have been the
6274 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
6275 which is a piece of hardware I do not own. So to be able to test what
6276 the current Freedombox setup look like, I had to come up with a way to install
6277 it on some hardware I do have access to. I have rewritten the
6278 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
6279 image build framework to use .deb packages instead of only copying
6280 setup into the boot images, and thanks to this rewrite I am able to
6281 set up any machine supported by Debian Wheezy as a Freedombox, using
6282 the previously mentioned deb (and a few support debs for packages
6283 missing in Debian).&lt;/p&gt;
6284
6285 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
6286 scripts
6287 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
6288 and a administrative web interface
6289 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
6290 withsqlite), as well as a privacy enhancing proxy based on
6291 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
6292 (freedombox-privoxy). There is also a web/javascript based XMPP
6293 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
6294 trying (unsuccessfully so far) to talk to the XMPP server
6295 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
6296 web interface is pluggable, and the goal is to use it to enable OpenID
6297 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6298 this is really working yet, see
6299 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
6300 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
6301 on github at the moment. The HTTP proxy is operational out of the
6302 box, and the admin web interface can be used to add/remove plinth
6303 users. I&#39;ve not been able to do anything else with it so far, but
6304 know there are several branches spread around github and other places
6305 with lots of half baked features.&lt;/p&gt;
6306
6307 &lt;p&gt;Anyway, if you want to have a look at the current state, the
6308 following recipes should work to give you a test machine to poke
6309 at.&lt;/p&gt;
6310
6311 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
6312
6313 &lt;ol&gt;
6314
6315 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
6316 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
6317 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
6318 to the Debian installer:&lt;p&gt;
6319 &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;
6320
6321 &lt;li&gt;Answer the few language/region/password questions and pick disk to
6322 install on.&lt;/li&gt;
6323
6324 &lt;li&gt;When the installation is finished and the machine have rebooted a
6325 few times, your Freedombox is ready for testing.&lt;/li&gt;
6326
6327 &lt;/ol&gt;
6328
6329 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
6330
6331 &lt;ol&gt;
6332
6333 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
6334 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
6335 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
6336 &lt;pre&gt;
6337 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
6338 &lt;/pre&gt;&lt;/li&gt;
6339 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
6340 &lt;pre&gt;
6341 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6342 apt-key add -
6343 apt-get update
6344 apt-get install freedombox-setup
6345 /usr/lib/freedombox/setup
6346 &lt;/pre&gt;&lt;/li&gt;
6347 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
6348
6349 &lt;/ol&gt;
6350
6351 &lt;p&gt;You can test it on other architectures too, but because the
6352 freedombox-privoxy package is binary, it will only work as intended on
6353 the architectures where I have had time to build the binary and put it
6354 in my APT repository. But do not let this stop you. It is only a
6355 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
6356
6357 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
6358 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
6359 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
6360 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
6361
6362 &lt;p&gt;Please let me know if this works for you, or if you have any
6363 problems. We gather on the IRC channel
6364 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
6365 irc.debian.org and the
6366 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
6367 mailing list&lt;/a&gt;.&lt;/p&gt;
6368
6369 &lt;p&gt;Once you get your freedombox operational, you can visit
6370 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
6371 welcome screen (dead end - do not be surprised if you are unable to
6372 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
6373 to look at the rest of plinth. The default user is &#39;admin&#39; and the
6374 default password is &#39;secret&#39;.&lt;/p&gt;
6375 </description>
6376 </item>
6377
6378 <item>
6379 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
6380 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
6381 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
6382 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
6383 <description>&lt;p&gt;Earlier, I reported about
6384 &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
6385 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
6386 told by IBM that the original disk should be thrown away. And as
6387 there no longer was a problem if I bricked the firmware, I decided
6388 today to try to install Intel firmware to replace the Lenovo firmware
6389 currently on the disk.&lt;/p&gt;
6390
6391 &lt;p&gt;I searched the Intel site for firmware, and found
6392 &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;
6393 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6394 according to the site should contain the latest firmware for SSD
6395 disks. I inserted the broken disk in one of my spare laptops and
6396 booted the ISO from a USB stick. The disk was recognized, but the
6397 program claimed the newest firmware already were installed and refused
6398 to insert any Intel firmware. So no change, and the disk is still
6399 unable to handle write load. :( I guess the only way to get them
6400 working would be if Lenovo releases new firmware. No idea how likely
6401 that is. Anyway, just blogging about this test for completeness. I
6402 got a working Samsung disk, and see no point in spending more time on
6403 the broken disks.&lt;/p&gt;
6404 </description>
6405 </item>
6406
6407 <item>
6408 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
6409 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
6410 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
6411 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
6412 <description>&lt;p&gt;Today I switched to
6413 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
6414 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
6415 my new Thinkpad X230, which was delivered with an
6416 &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
6417 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
6418 sustained writes. My hardware supplier have been very forthcoming in
6419 trying to find a solution, and after first trying with another
6420 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
6421 disk instead to fix it once and for all. The Samsung disk survived
6422 the installation of Debian with encrypted disks (filling the disk with
6423 random data during installation killed the first two), and I thus
6424 decided to trust it with my data. I have installed it as a Debian Edu
6425 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6426 server at home using Kerberos and LDAP, and will use it as my work
6427 station from now on.&lt;/p&gt;
6428
6429 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
6430 Debian Wheezy default installation need to be tuned a bit to increase
6431 performance and increase life time of the disk. The Linux kernel and
6432 user space applications do not yet adjust automatically to such
6433 environment. To make it easier for my self, I created a draft Debian
6434 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
6435 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
6436 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
6437 is set up to adjust the setup of the machine by just installing the
6438 package. If there is any non-SSD disk in the machine, the package
6439 will refuse to install, as I did not try to write any logic to sort
6440 file systems in SSD and non-SSD file systems.&lt;/p&gt;
6441
6442 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
6443 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6444 where I set up the machine with one large encrypted partition (in
6445 addition to /boot), put LVM on top of this and set up partitions on
6446 top of this again. See the README file in the package source for the
6447 references I used to pick the settings. At the moment these
6448 parameters are tuned:&lt;/p&gt;
6449
6450 &lt;ul&gt;
6451
6452 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
6453 (adding discard to /etc/crypttab)&lt;/li&gt;
6454
6455 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
6456 this case a cryptsetup partition) by changing issue_discards from
6457 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
6458
6459 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
6460 systems.&lt;/li&gt;
6461
6462 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
6463 /etc/fstab.&lt;/li&gt;
6464
6465 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
6466
6467 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
6468 cron.daily).&lt;/li&gt;
6469
6470 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
6471 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
6472
6473 &lt;/ul&gt;
6474
6475 &lt;p&gt;During installation, I cancelled the part where the installer fill
6476 the disk with random data, as this would kill the SSD performance for
6477 little gain. My goal with the encrypted file system is to ensure
6478 those stealing my laptop end up with a brick and not a working
6479 computer. I have no hope in keeping the really resourceful people
6480 from getting the data on the disk (see
6481 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
6482 Thus I concluded that adding the discard option to crypttab is the
6483 right thing to do.&lt;/p&gt;
6484
6485 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
6486 it for SSD, but others recommended deadline and a benchmark I found
6487 indicated that deadline might be better for interactive use.&lt;/p&gt;
6488
6489 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
6490 and ext4, but read that it would give a performance hit ever time a
6491 file is removed, and thought it best to that that slowdown once a day
6492 instead of during my work.&lt;/p&gt;
6493
6494 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6495 this is already done by Debian Edu.&lt;/p&gt;
6496
6497 &lt;p&gt;I have not yet started on the user space tuning. I expect
6498 iceweasel need some tuning, and perhaps other applications too, but
6499 have not yet had time to investigate those parts.&lt;/p&gt;
6500
6501 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
6502 there.&lt;/p&gt;
6503
6504 &lt;p&gt;As for the answer to the question in the title of this blog post,
6505 as far as I know, the only solution I know about is to replace the
6506 disk. It might be possible to flash it with Intel firmware instead of
6507 the Lenovo firmware. But I have not tried and did not want to do so
6508 without approval from Lenovo as I wanted to keep the warranty on the
6509 disk until a solution was found and they wanted the broken disks
6510 back.&lt;/p&gt;
6511 </description>
6512 </item>
6513
6514 <item>
6515 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
6516 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
6517 <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>
6518 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
6519 <description>&lt;p&gt;A few days ago, I wrote about
6520 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
6521 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
6522 was dying during installation because it is unable to cope with
6523 sustained write. My supplier is in contact with
6524 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
6525 replacement disk to try to fix the problem. They decided to send an
6526 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
6527
6528 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
6529 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6530 same firmware version as the original. This time my hope raised
6531 slightly as the installation progressed, as the original disk used to
6532 die after 4-7% of the disk was written to, while this time it kept
6533 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
6534 died again and I was back on square one. I still do not have a new
6535 laptop with a disk I can trust. I can not live with a disk that might
6536 lock up when I download a new
6537 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
6538 other large files. I look forward to hearing from my supplier with
6539 the next proposal from Lenovo.&lt;/p&gt;
6540
6541 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
6542 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6543 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6544 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
6545 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6546 P/N 45N8295, P0C38732.&lt;/p&gt;
6547
6548 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
6549 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
6550 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
6551 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
6552 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
6553 P/N 45N8295, P0C38732.&lt;/p&gt;
6554
6555 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
6556 SA, date and WNPP values. Mentioning all the details here in case
6557 someone is able to use the information to find a way to identify the
6558 failing disk among working ones (if any such working disk actually
6559 exist).&lt;/p&gt;
6560 </description>
6561 </item>
6562
6563 <item>
6564 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
6565 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
6566 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
6567 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
6568 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
6569 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6570 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
6571 member assosiation NUUG&lt;/a&gt; and
6572 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
6573 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
6574 Bitraf&lt;/a&gt;.&lt;/p&gt;
6575
6576 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
6577 welcome, and there is no fee to participate. There is on the other
6578 hand limited space, and only room for 30 people. Please put your name
6579 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
6580 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
6581 </description>
6582 </item>
6583
6584 <item>
6585 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
6586 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
6587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
6588 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
6589 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
6590 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
6591 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
6592 time to spend on it, and it took a while to find a model I believe
6593 will do the job, but two days ago the replacement finally arrived. I
6594 ended up picking a
6595 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
6596 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6597 a roaming workstation, and it seemed to work flawlessly. But my
6598 second installation with encrypted disk was not as successful. More
6599 on that below.&lt;/p&gt;
6600
6601 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6602 important requirements (robust and with a good keyboard) are never
6603 listed in the feature list. But I did get good help from the search
6604 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6605 allowed me to limit the list of interesting laptops based on my other
6606 requirements. A bit surprising that SSD disk are not disks according
6607 to that search interface, so I had to drop specifying the number of
6608 disks from my search parameters. I also asked around among friends to
6609 get their impression on keyboards and robustness.&lt;/p&gt;
6610
6611 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
6612 X41. I am not quite convinced about the keyboard, as it is
6613 significantly wider than my old keyboard, and I have to stretch my
6614 hand a lot more to reach the edges. But the key response is fairly
6615 good and the individual key shape is fairly easy to handle, so I hope
6616 I will get used to it. My old X40 was starting to fail, and I really
6617 needed a new laptop now. :)&lt;/p&gt;
6618
6619 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
6620 visit to the BIOS during boot it disable it.&lt;/p&gt;
6621
6622 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
6623 lock up during load. And this happen when installing Debian Wheezy
6624 with encrypted disk, while the disk is being filled with random data.
6625 I also tested to install Ubuntu Raring, and it happen there too if I
6626 reenable the code to fill the disk with random data (it is disabled by
6627 default in Ubuntu). And the bug with is already known. It was
6628 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
6629 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
6630 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6631 kernel developers as
6632 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
6633 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
6634 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6635 Lenovo forums, both for
6636 &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
6637 2012-11-10&lt;/a&gt; and for
6638 &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
6639 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
6640 reports state that the disk lock up during use if many writes are done
6641 on the disk, so it is much no use to work around the installation
6642 problem and end up with a computer that can lock up at any moment.
6643 There is even a
6644 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
6645 available&lt;/a&gt; that will lock up the hard drive after running a few
6646 minutes by writing to a file.&lt;/p&gt;
6647
6648 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
6649 contacting PCHELP Norway (request 01D1FDP) which handle support
6650 requests for Lenovo, his first suggestion was to upgrade the disk
6651 firmware. Unfortunately there is no newer firmware available from
6652 Lenovo, as my disk already have the most recent one (version LF1i). I
6653 hope to hear more from him today and hope the problem can be
6654 fixed. :)&lt;/p&gt;
6655 </description>
6656 </item>
6657
6658 <item>
6659 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
6660 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
6661 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
6662 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
6663 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
6664 trusty old Thinkpad X41. Unfortunately I did not have much time to
6665 spend on it, but today the replacement finally arrived. I ended up
6666 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
6667 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
6668 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6669 this, it is installing what I hope will be a more final installation,
6670 with a encrypted hard drive to ensure any dope head stealing it end up
6671 with an expencive door stop.&lt;/p&gt;
6672
6673 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
6674 important requirements (robust and with a good keyboard) are never
6675 listed in the feature list. But I did get good help from the search
6676 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
6677 allowed me to limit the list of interesting laptops based on my other
6678 requirements. A bit surprising that SSD disk are not disks, so I had
6679 to drop number of disks from my search parameters.&lt;/p&gt;
6680
6681 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
6682 wider than my old keyboard, and I have to stretch my hand a lot more
6683 to reach the edges. But the key response is fairly good and the
6684 individual key shape is fairly easy to handle, so I hope I will get
6685 used to it. My old X40 was starting to fail, and I really needed a
6686 new laptop now. :)&lt;/p&gt;
6687
6688 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
6689 </description>
6690 </item>
6691
6692 <item>
6693 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
6694 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
6695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
6696 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
6697 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
6698 perfectly capable of, and I have to do it manually to get things
6699 working. One such task is to find out what firmware packages are
6700 needed to get the hardware on my computer working. Most often this
6701 affect the wifi card, but some times it even affect the RAID
6702 controller or the ethernet card. Today I pushed version 0.4 of the
6703 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
6704 including a new script isenkram-autoinstall-firmware handling the
6705 process of asking all the loaded kernel modules what firmware files
6706 they want, find debian packages providing these files and install the
6707 debian packages. Here is a test run on my laptop:&lt;/p&gt;
6708
6709 &lt;p&gt;&lt;pre&gt;
6710 # isenkram-autoinstall-firmware
6711 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6712 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6713 info: locating packages with the requested firmware files
6714 info: Updating APT sources after adding non-free APT source
6715 info: trying to install firmware-ipw2x00
6716 firmware-ipw2x00
6717 firmware-ipw2x00
6718 Preconfiguring packages ...
6719 Selecting previously deselected package firmware-ipw2x00.
6720 (Reading database ... 259727 files and directories currently installed.)
6721 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6722 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
6723 #
6724 &lt;/pre&gt;&lt;/p&gt;
6725
6726 &lt;p&gt;When all the requested firmware is present, a simple message is
6727 printed instead:&lt;/p&gt;
6728
6729 &lt;p&gt;&lt;pre&gt;
6730 # isenkram-autoinstall-firmware
6731 info: did not find any firmware files requested by loaded kernel modules. exiting
6732 #
6733 &lt;/pre&gt;&lt;/p&gt;
6734
6735 &lt;p&gt;It could use some polish, but it is already working well and saving
6736 me some time when setting up new machines. :)&lt;/p&gt;
6737
6738 &lt;p&gt;So, how does it work? It look at the set of currently loaded
6739 kernel modules, and look up each one of them using modinfo, to find
6740 the firmware files listed in the module meta-information. Next, it
6741 download the Contents file from a nearby APT mirror, and search for
6742 the firmware files in this file to locate the package with the
6743 requested firmware file. If the package is in the non-free section, a
6744 non-free APT source is added and the package is installed using
6745 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
6746 machine.&lt;/p&gt;
6747
6748 &lt;p&gt;I hope someone find time to implement a more polished version of
6749 this script as part of the hw-detect debian-installer module, to
6750 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
6751 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
6752 firmware during a PXE install when the packages already are available
6753 from the nearby Debian mirror.&lt;/p&gt;
6754 </description>
6755 </item>
6756
6757 <item>
6758 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
6759 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
6760 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
6761 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
6762 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6763 the screen just turn black when Linux boot, either during installation
6764 or on first boot from the hard disk. I&#39;ve seen it once in a while the
6765 last few years, but only recently understood the cause. I&#39;ve seen it
6766 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6767 The reason seem to be in the wiring of some laptops. The system to
6768 control the screen background light is inverted, so when Linux try to
6769 turn the brightness fully on, it end up turning it off instead. I do
6770 not know which Linux drivers are affected, but this post is about the
6771 i915 driver used by the
6772 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6773 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
6774
6775 &lt;p&gt;The problem can be worked around two ways. Either by adding
6776 i915.invert_brightness=1 as a kernel option, or by adding a file in
6777 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
6778 option when it load the i915 kernel module. On Debian and Ubuntu, it
6779 can be done by running these commands as root:&lt;/p&gt;
6780
6781 &lt;pre&gt;
6782 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
6783 update-initramfs -u -k all
6784 &lt;/pre&gt;
6785
6786 &lt;p&gt;Since March 2012 there is
6787 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
6788 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
6789 hardware have this problem, and get the driver to invert the
6790 brightness setting automatically. To use it, one need to add a row in
6791 &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
6792 intel_quirks array&lt;/a&gt; in the driver source
6793 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
6794 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
6795 number (vendor number 8086 is assumed) and subdevice vendor and device
6796 number.&lt;/p&gt;
6797
6798 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
6799 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
6800
6801 &lt;p&gt;&lt;pre&gt;
6802 00:02.0 VGA compatible controller [0300]: Intel Corporation \
6803 3rd Gen Core processor Graphics Controller [8086:0156] \
6804 (rev 09) (prog-if 00 [VGA controller])
6805 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
6806 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6807 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6808 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
6809 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
6810 Latency: 0
6811 Interrupt: pin A routed to IRQ 42
6812 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
6813 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
6814 Region 4: I/O ports at 4000 [size=64]
6815 Expansion ROM at &lt;unassigned&gt; [disabled]
6816 Capabilities: &lt;access denied&gt;
6817 Kernel driver in use: i915
6818 &lt;/pre&gt;&lt;/p&gt;
6819
6820 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
6821
6822 &lt;p&gt;&lt;pre&gt;
6823 struct intel_quirk intel_quirks[] = {
6824 ...
6825 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6826 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
6827 ...
6828 }
6829 &lt;/pre&gt;&lt;/p&gt;
6830
6831 &lt;p&gt;According to the kernel module instructions (as seen using
6832 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
6833 invert_brightness flag should be sent to the
6834 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
6835 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
6836 developers. But my email about the laptop sent 2013-06-03 have not
6837 yet shown up in
6838 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
6839 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
6840 emails from non-subscribers. Because of this, I sent my patch also to
6841 the Debian bug tracking system instead as
6842 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
6843 sure the patch is not lost.&lt;/p&gt;
6844
6845 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
6846 with this problem working properly with Linux. If you use Gnome, your
6847 worries should be over at this point. But if you use KDE, there is
6848 something in KDE ignoring the invert_brightness setting and turning on
6849 the screen during login. I&#39;ve reported it to Debian as
6850 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
6851 have no idea yet how to figure out exactly what subsystem is doing
6852 this. Perhaps you can help? Perhaps you know what the Gnome
6853 developers did to handle this, and this can give a clue to the KDE
6854 developers? Or you know where in KDE the screen brightness is changed
6855 during login? If so, please update the BTS report (or get in touch if
6856 you do not know how to update BTS).&lt;/p&gt;
6857
6858 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
6859 acpi_backlight=vendor, to disable ACPI backlight support completely,
6860 as the ACPI information on the machine is trash and it is better to
6861 leave it to the intel video driver to control the screen
6862 backlight.&lt;/p&gt;
6863 </description>
6864 </item>
6865
6866 <item>
6867 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
6868 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
6869 <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>
6870 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
6871 <description>&lt;p&gt;Two days ago, I asked
6872 &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
6873 I could install Linux on a Packard Bell EasyNote LV computer
6874 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
6875 with the obstacles put in the way of Linux users on a laptop with UEFI
6876 and Windows 8.&lt;/p&gt;
6877
6878 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
6879 secure booting or fast boot. I suspect fast boot was the problem,
6880 causing the firmware to boot directly from HD without considering any
6881 key presses and alternative devices, but do not know UEFI settings
6882 enough to tell.&lt;/p&gt;
6883
6884 &lt;p&gt;There is no way to install Linux on the machine in question without
6885 opening the box and disconnecting the hard drive! This is as far as I
6886 can tell, the only way to get access to the firmware setup menu
6887 without accepting the Windows 8 license agreement. I am told (and
6888 found description on how to) that it is possible to configure the
6889 firmware setup once booted into Windows 8. But as I believe the terms
6890 of that agreement are completely unacceptable, accepting the license
6891 was never an alternative. I do not enter agreements I do not intend
6892 to follow.&lt;/p&gt;
6893
6894 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6895 waste many hours on this, but luckily there was a way to get it to
6896 work. But I would not recommend it to anyone planning to run Linux on
6897 it, and I have become sceptical to Windows 8 certified laptops. Is
6898 this the way Linux will be forced out of the market place, by making
6899 it close to impossible for &quot;normal&quot; users to install Linux without
6900 accepting the Microsoft Windows license terms? Or at least not
6901 without risking to loose the warranty?&lt;/p&gt;
6902
6903 &lt;p&gt;I&#39;ve updated the
6904 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6905 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6906 do not have to struggle as much as I did to get Linux into the
6907 machine.&lt;/p&gt;
6908
6909 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6910 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6911 </description>
6912 </item>
6913
6914 <item>
6915 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6916 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6917 <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>
6918 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6919 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6920 new laptops for my parents and a few others. I bought Packard Bell
6921 Easynote LV to run Kubuntu on and use as their home computer. But I
6922 am completely unable to figure out how to install Linux on it. The
6923 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6924 instead of a BIOS to boot.&lt;/p&gt;
6925
6926 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6927 to get it to boot the Linux installer from my USB stick. I have yet
6928 to try the DVD install, and still hope it will work. when I turn on
6929 the computer, there is no information on what buttons to press to get
6930 the normal boot menu. I expect to get some boot menu to select PXE or
6931 USB stick booting. When booting, it first ask for the language to
6932 use, then for some regional settings, and finally if I will accept the
6933 Windows 8 terms of use. As these terms are completely unacceptable to
6934 me, I have no other choice but to turn off the computer and try again
6935 to get it to boot the Linux installer.&lt;/p&gt;
6936
6937 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6938 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6939 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6940 installed on this machine, please get in touch or update that wiki
6941 page. If I can&#39;t find a way to install Linux, I will have to return
6942 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6943
6944 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6945 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6946 on new Laptops?&lt;/p&gt;
6947 </description>
6948 </item>
6949
6950 <item>
6951 <title>How to transform a Debian based system to a Debian Edu installation</title>
6952 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6953 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6954 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6955 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6956 an operating system based on Debian intended for use in schools. It
6957 contain a turn-key solution for the computer network provided to
6958 pupils in the primary schools. It provide both the central server,
6959 network boot servers and desktop environments with heaps of
6960 educational software. The project was founded almost 12 years ago,
6961 2001-07-02. If you want to support the project, which is in need for
6962 cash to fund developer gatherings and other project related activity,
6963 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6964 donate some money&lt;/a&gt;.
6965
6966 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6967 lists and elsewhere, is the question on how to transform a Debian or
6968 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6969 hard, and last week I wrote a script to replicate the steps done by
6970 the Debian Edu installer.&lt;/p&gt;
6971
6972 &lt;p&gt;The script,
6973 &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;
6974 in the debian-edu-config package, will go through these six steps and
6975 transform an existing Debian Wheezy or Ubuntu (untested) installation
6976 into a Debian Edu Workstation:&lt;/p&gt;
6977
6978 &lt;ol&gt;
6979
6980 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6981 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6982 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6983 our configuration.&lt;/li&gt;
6984 &lt;li&gt;Preseed debconf database with profile setup in
6985 /etc/debian-edu/config, and run tasksel to install packages
6986 according to the profile specified in the config above,
6987 overriding some of the Debian automation machinery.&lt;/li&gt;
6988 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6989 that could not be done using preseeding.&lt;/li&gt;
6990 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6991
6992 &lt;/ol&gt;
6993
6994 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6995 replicated like this. Disk partitioning and LVM setup, for example.
6996 So this script just assume there is enough disk space to install all
6997 the needed packages.&lt;/p&gt;
6998
6999 &lt;p&gt;The script was created to help a Debian Edu student working on
7000 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
7001 Debian Edu client, and using it he can take the existing
7002 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
7003 transform it into a fully functioning Debian Edu Workstation (or
7004 Roaming Workstation, or whatever :).&lt;/p&gt;
7005
7006 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
7007 If a LXDE based Roaming workstation is wanted instead, modify the
7008 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
7009
7010 &lt;p&gt;&lt;pre&gt;
7011 PROFILE=&quot;Roaming-Workstation&quot;
7012 DESKTOP=&quot;lxde&quot;
7013 &lt;/pre&gt;&lt;/p&gt;
7014
7015 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
7016 the cloud, by starting with a virtual Debian installation at some
7017 virtual hosting service and setting up all the services on first
7018 boot.&lt;/p&gt;
7019 </description>
7020 </item>
7021
7022 <item>
7023 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
7024 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
7025 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
7026 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
7027 <description>&lt;P&gt;In January,
7028 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
7029 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
7030 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
7031 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
7032 marvellous construction system from Denmark. We also created
7033 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
7034 a place to take notes and write down our plans and hopes. And several
7035 people showed up to help. I was very happy to see the effect of my
7036 call. Since the small start, we have a debtags tag
7037 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
7038 tag for LEGO related packages, and now count 10 packages related to
7039 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
7040
7041 &lt;p&gt;&lt;table&gt;
7042 &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;
7043 &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;
7044 &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;
7045 &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;
7046 &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;
7047 &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;
7048 &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;
7049 &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;
7050 &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;
7051 &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;
7052 &lt;/table&gt;&lt;/p&gt;
7053
7054 &lt;p&gt;Some of these are available in Wheezy, and all but one are
7055 currently available in Jessie/testing. leocad is so far only
7056 available in experimental.&lt;/p&gt;
7057
7058 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
7059 adding the rest of the great free software tools available on Linux
7060 for LEGO designers.&lt;/p&gt;
7061 </description>
7062 </item>
7063
7064 <item>
7065 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
7066 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
7067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
7068 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
7069 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
7070 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
7071 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
7072 Debian release, and I expect to move my machines at home over to it fairly
7073 soon.&lt;/p&gt;
7074
7075 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
7076 in particular make me very happy to see included. The
7077 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
7078 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
7079 included for the first time. Alongside similar programs like
7080 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
7081 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
7082 it allow for visual programming where syntax errors can not happen,
7083 and a friendly programming environment for learning to control the
7084 computer. Scratch will also be included in the next release of Debian
7085 Edu.&lt;/a&gt;
7086
7087 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
7088 Edu/Skolelinux release too. The
7089 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
7090 alpha release&lt;/a&gt; went out last week, and the next should soon
7091 follow.&lt;p&gt;
7092 </description>
7093 </item>
7094
7095 <item>
7096 <title>Isenkram 0.2 finally in the Debian archive</title>
7097 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
7098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
7099 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
7100 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
7101 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
7102 for many months. I uploaded it to the Debian experimental suite
7103 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
7104
7105 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
7106 install to work with a pluggable hardware device. The suggestion pop
7107 up when the device is plugged in. For example if a Lego Mindstorm NXT
7108 is inserted, it will suggest to install the program needed to program
7109 the NXT controller. Give it a go, and report bugs and suggestions to
7110 BTS. :)&lt;/p&gt;
7111 </description>
7112 </item>
7113
7114 <item>
7115 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
7116 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
7117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
7118 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
7119 <description>&lt;p&gt;My
7120 &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
7121 bitcoin related blog post&lt;/a&gt; mentioned that the new
7122 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
7123 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7124 2013-01-19, and have been available in unstable since then. It was
7125 automatically copied to Ubuntu, and is available in their Raring
7126 version too.&lt;/p&gt;
7127
7128 &lt;p&gt;But there is a strange problem with the build that block this new
7129 version from being available on the i386 and kfreebsd-i386
7130 architectures. For some strange reason, the autobuilders in Debian
7131 for these architectures fail to run the test suite on these
7132 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
7133 We are so far unable to reproduce it when building it manually, and
7134 no-one have been able to propose a fix. If you got an idea what is
7135 failing, please let us know via the BTS.&lt;/p&gt;
7136
7137 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
7138 I often run low on disk space, is the fact that the client will exit
7139 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
7140 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
7141 it. :)&lt;/p&gt;
7142
7143 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7144 activities, please send Bitcoin donations to my address
7145 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7146 </description>
7147 </item>
7148
7149 <item>
7150 <title>Welcome to the world, Isenkram!</title>
7151 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
7152 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
7153 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
7154 <description>&lt;p&gt;Yesterday, I
7155 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
7156 for testers&lt;/a&gt; for my prototype for making Debian better at handling
7157 pluggable hardware devices, which I
7158 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
7159 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
7160 up, and caused me to really want to to open up the development to more
7161 people. But before I did this, I want to come up with a sensible name
7162 for this project. Today I finally decided on a new name, and I have
7163 renamed the project from hw-support-handler to this new name. In the
7164 process, I moved the source to git and made it available as a
7165 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
7166 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
7167 To fetch and build the latest version of the source, use&lt;/p&gt;
7168
7169 &lt;pre&gt;
7170 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
7171 cd isenkram &amp;&amp; git-buildpackage -us -uc
7172 &lt;/pre&gt;
7173
7174 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
7175 want to hack on the source or improve the package, please go ahead.
7176 But please talk to me first on IRC or via email before you do major
7177 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
7178
7179 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
7180 stuff, typically meaning tools, nails, screws, etc. Typical hardware
7181 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
7182 the German word eisenkram, for those that are familiar with that
7183 word.&lt;/p&gt;
7184
7185 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
7186 instructions, to avoid confusing people with an error from the signing
7187 process.&lt;/p&gt;
7188
7189 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
7190 clone argument to avoid the need for authentication.&lt;/p&gt;
7191 </description>
7192 </item>
7193
7194 <item>
7195 <title>First prototype ready making hardware easier to use in Debian</title>
7196 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
7197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
7198 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
7199 <description>&lt;p&gt;Early this month I set out to try to
7200 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
7201 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
7202 prototype is working, and it is ready for a larger audience. To test
7203 it, fetch the
7204 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
7205 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
7206 package. You might have to log out and in again activate the
7207 autostart script.&lt;/p&gt;
7208
7209 &lt;p&gt;The design is simple:&lt;/p&gt;
7210
7211 &lt;ul&gt;
7212
7213 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
7214 hw-support-handlerd to start when the user log in.&lt;/li&gt;
7215
7216 &lt;li&gt;This program listen for kernel events about new hardware (directly
7217 from the kernel like udev does), not using HAL dbus events as I
7218 initially did.&lt;/li&gt;
7219
7220 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
7221 the APT database, a database
7222 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
7223 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
7224
7225 &lt;li&gt;If a package is mapped to the hardware in question, the package
7226 isn&#39;t installed yet and this is the first time the hardware was
7227 plugged in, show a desktop notification suggesting to install the
7228 package or packages.&lt;/li&gt;
7229
7230 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
7231 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
7232
7233 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
7234 package while showing progress information in a window.&lt;/li&gt;
7235
7236 &lt;/ul&gt;
7237
7238 &lt;p&gt;I still need to come up with a better name for the system. Here
7239 are some screen shots showing the prototype in action. First the
7240 notification, then the password request, and finally the request to
7241 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
7242
7243 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
7244 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
7245 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
7246 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
7247 &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;
7248
7249 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
7250 is already useful. The database of hardware to package mappings also
7251 need more work. It is currently compatible with the Ubuntu way of
7252 storing such information in the package control file, but could be
7253 changed to use other formats instead or in addition to the current
7254 method. I&#39;ve dropped the use of discover for this mapping, as the
7255 modalias approach is more flexible and easier to use on Linux as long
7256 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
7257
7258 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
7259 here is the command required to check out and build the source: Use
7260 &#39;&lt;tt&gt;svn checkout
7261 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
7262 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
7263 devscripts package.&lt;/p&gt;
7264
7265 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
7266 renamed to Isenkram and the source moved from the Debian Edu
7267 subversion repository to a Debian collab-maint git repository. See
7268 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
7269 instructions&lt;/a&gt; for details.&lt;/p&gt;
7270 </description>
7271 </item>
7272
7273 <item>
7274 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
7275 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
7276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
7277 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
7278 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
7279 suddenly in bed. With a quiet whimper, it went completely quiet and
7280 black. The power button was no longer able to turn it on. It was a
7281 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7282 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7283 Compaq I had before that. Now I need to find a replacement. To keep
7284 going during Christmas, I moved the one year old SSD disk to my old
7285 X40 where it fitted (only one I had left that could use it), but it is
7286 not a durable solution.
7287
7288 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
7289 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
7290
7291 &lt;ul&gt;
7292
7293 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
7294 than A4).&lt;/li&gt;
7295 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
7296 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
7297 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
7298 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
7299 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
7300 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
7301 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
7302 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
7303 size).&lt;/li&gt;
7304 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
7305 X.org packages.&lt;/li&gt;
7306 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
7307 the time).
7308
7309 &lt;/ul&gt;
7310
7311 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
7312 list. The reason is simply that the specifications on laptops the
7313 last 10-15 years have been sufficient for my needs, and I have to look
7314 at other features to choose my laptop. But are there still made as
7315 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7316 robust, and Thinkpads seem to be heading in the wrong direction since
7317 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
7318 still be useful.&lt;/p&gt;
7319
7320 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
7321 external keyboard? I&#39;ll have to check the
7322 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
7323 well-supported laptops, or perhaps just buy one preinstalled from one
7324 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
7325 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
7326 </description>
7327 </item>
7328
7329 <item>
7330 <title>How to find a browser plugin supporting a given MIME type</title>
7331 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
7332 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
7333 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
7334 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
7335 install to get support for a given MIME type. Thanks to
7336 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
7337 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
7338 Unfortunately, not very many packages provide the needed meta
7339 information, Anyway, here is a small script to look up all browser
7340 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
7341
7342 &lt;pre&gt;
7343 #!/usr/bin/python
7344 import sys
7345 import apt
7346 def pkgs_handling_mimetype(mimetype):
7347 cache = apt.Cache()
7348 cache.open(None)
7349 thepkgs = []
7350 for pkg in cache:
7351 version = pkg.candidate
7352 if version is None:
7353 version = pkg.installed
7354 if version is None:
7355 continue
7356 record = version.record
7357 if not record.has_key(&#39;Npp-MimeType&#39;):
7358 continue
7359 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
7360 for t in mime_types:
7361 t = t.rstrip().strip()
7362 if t == mimetype:
7363 thepkgs.append(pkg.name)
7364 return thepkgs
7365 mimetype = &quot;audio/ogg&quot;
7366 if 1 &lt; len(sys.argv):
7367 mimetype = sys.argv[1]
7368 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
7369 for pkg in pkgs_handling_mimetype(mimetype):
7370 print &quot; %s&quot; %pkg
7371 &lt;/pre&gt;
7372
7373 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
7374
7375 &lt;pre&gt;
7376 % ./apt-find-browserplug-for-mimetype
7377 Browser plugin packages supporting audio/ogg:
7378 gecko-mediaplayer
7379 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7380 Browser plugin packages supporting application/x-shockwave-flash:
7381 browser-plugin-gnash
7382 %
7383 &lt;/pre&gt;
7384
7385 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
7386 itself to query for plugins and propose to install the needed
7387 packages. It would be great if Debian supported such feature too. Is
7388 anyone working on adding it?&lt;/p&gt;
7389
7390 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
7391 request for icweasel support for this feature is
7392 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
7393 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
7394 of manpower and wish for a different design is the reason thus feature
7395 is not yet in iceweasel from Debian.&lt;/p&gt;
7396 </description>
7397 </item>
7398
7399 <item>
7400 <title>What is the most supported MIME type in Debian?</title>
7401 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
7402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
7403 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
7404 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
7405 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
7406 proposal to make it possible for a Desktop application to propose to
7407 the user some package to install to gain support for a given MIME
7408 type, font, library etc. that is currently missing. With such
7409 mechanism in place, it would be possible for the desktop to
7410 automatically propose and install leocad if some LDraw file is
7411 downloaded by the browser.&lt;/p&gt;
7412
7413 &lt;p&gt;To get some idea about the current content of the archive, I decided
7414 to write a simple program to extract all .desktop files from the
7415 Debian archive and look up the claimed MIME support there. The result
7416 can be found on the
7417 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
7418 site&lt;/a&gt;. Using the collected information, it become possible to
7419 answer the question in the title. Here are the 20 most supported MIME
7420 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7421 The complete list is available from the link above.&lt;/p&gt;
7422
7423 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
7424
7425 &lt;pre&gt;
7426 count MIME type
7427 ----- -----------------------
7428 32 text/plain
7429 30 audio/mpeg
7430 29 image/png
7431 28 image/jpeg
7432 27 application/ogg
7433 26 audio/x-mp3
7434 25 image/tiff
7435 25 image/gif
7436 22 image/bmp
7437 22 audio/x-wav
7438 20 audio/x-flac
7439 19 audio/x-mpegurl
7440 18 video/x-ms-asf
7441 18 audio/x-musepack
7442 18 audio/x-mpeg
7443 18 application/x-ogg
7444 17 video/mpeg
7445 17 audio/x-scpls
7446 17 audio/ogg
7447 16 video/x-ms-wmv
7448 &lt;/pre&gt;
7449
7450 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
7451
7452 &lt;pre&gt;
7453 count MIME type
7454 ----- -----------------------
7455 33 text/plain
7456 32 image/png
7457 32 image/jpeg
7458 29 audio/mpeg
7459 27 image/gif
7460 26 image/tiff
7461 26 application/ogg
7462 25 audio/x-mp3
7463 22 image/bmp
7464 21 audio/x-wav
7465 19 audio/x-mpegurl
7466 19 audio/x-mpeg
7467 18 video/mpeg
7468 18 audio/x-scpls
7469 18 audio/x-flac
7470 18 application/x-ogg
7471 17 video/x-ms-asf
7472 17 text/html
7473 17 audio/x-musepack
7474 16 image/x-xbitmap
7475 &lt;/pre&gt;
7476
7477 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
7478
7479 &lt;pre&gt;
7480 count MIME type
7481 ----- -----------------------
7482 31 text/plain
7483 31 image/png
7484 31 image/jpeg
7485 29 audio/mpeg
7486 28 application/ogg
7487 27 image/gif
7488 26 image/tiff
7489 26 audio/x-mp3
7490 23 audio/x-wav
7491 22 image/bmp
7492 21 audio/x-flac
7493 20 audio/x-mpegurl
7494 19 audio/x-mpeg
7495 18 video/x-ms-asf
7496 18 video/mpeg
7497 18 audio/x-scpls
7498 18 application/x-ogg
7499 17 audio/x-musepack
7500 16 video/x-ms-wmv
7501 16 video/x-msvideo
7502 &lt;/pre&gt;
7503
7504 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
7505 information mentioned in DEP-11. I have not yet had time to look at
7506 it, but hope the PackageKit people in Debian are on top of these
7507 issues.&lt;/p&gt;
7508
7509 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
7510 discovering a typo in my script.&lt;/p&gt;
7511 </description>
7512 </item>
7513
7514 <item>
7515 <title>Using modalias info to find packages handling my hardware</title>
7516 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
7517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
7518 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
7519 <description>&lt;p&gt;Yesterday, I wrote about the
7520 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
7521 values provided by the Linux kernel&lt;/a&gt; following my hope for
7522 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
7523 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
7524 modalias values attached to package names can be used to map packages
7525 to hardware. This allow the system to look up and suggest relevant
7526 packages when I plug in some new hardware into my machine, and replace
7527 discover and discover-data as the database used to map hardware to
7528 packages.&lt;/p&gt;
7529
7530 &lt;p&gt;I create a modaliases file with entries like the following,
7531 containing package name, kernel module name (if relevant, otherwise
7532 the package name) and globs matching the relevant hardware
7533 modalias.&lt;/p&gt;
7534
7535 &lt;p&gt;&lt;blockquote&gt;
7536 Package: package-name
7537 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
7538 &lt;/blockquote&gt;&lt;/p&gt;
7539
7540 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
7541 for a given modalias value using this file.&lt;/p&gt;
7542
7543 &lt;p&gt;An entry like this would suggest the video and picture application
7544 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
7545
7546 &lt;p&gt;&lt;blockquote&gt;
7547 Package: cheese
7548 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
7549 &lt;/blockquote&gt;&lt;/p&gt;
7550
7551 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
7552 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
7553
7554 &lt;p&gt;&lt;blockquote&gt;
7555 Package: pcmciautils
7556 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7557 &lt;/blockquote&gt;&lt;/p&gt;
7558
7559 &lt;p&gt;An entry like this would suggest the package colorhug-client when
7560 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
7561
7562 &lt;p&gt;&lt;blockquote&gt;
7563 Package: colorhug-client
7564 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
7565 &lt;/blockquote&gt;&lt;/p&gt;
7566
7567 &lt;p&gt;I believe the format is compatible with the format of the Packages
7568 file in the Debian archive. Ubuntu already uses their Packages file
7569 to store their mappings from packages to hardware.&lt;/p&gt;
7570
7571 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
7572 announce the hardware it support in a way my prototype understand.
7573 This allow those publishing packages in an APT source outside the
7574 Debian archive as well as those backporting packages to make sure the
7575 hardware mapping are included in the package meta information. I&#39;ve
7576 tested such header in the pymissile package, and its modalias mapping
7577 is working as it should with my prototype. It even made it to Ubuntu
7578 Raring.&lt;/p&gt;
7579
7580 &lt;p&gt;To test if it was possible to look up supported hardware using only
7581 the shell tools available in the Debian installer, I wrote a shell
7582 implementation of the lookup code. The idea is to create files for
7583 each modalias and let the shell do the matching. Please check out and
7584 try the
7585 &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;
7586 shell script. It run without any extra dependencies and fetch the
7587 hardware mappings from the Debian archive and the subversion
7588 repository where I currently work on my prototype.&lt;/p&gt;
7589
7590 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
7591 install yubikey-personalization:&lt;/p&gt;
7592
7593 &lt;p&gt;&lt;blockquote&gt;
7594 % ./hw-support-lookup
7595 &lt;br&gt;yubikey-personalization
7596 &lt;br&gt;%
7597 &lt;/blockquote&gt;&lt;/p&gt;
7598
7599 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7600 propose to install the pcmciautils package:&lt;/p&gt;
7601
7602 &lt;p&gt;&lt;blockquote&gt;
7603 % ./hw-support-lookup
7604 &lt;br&gt;pcmciautils
7605 &lt;br&gt;%
7606 &lt;/blockquote&gt;&lt;/p&gt;
7607
7608 &lt;p&gt;If you know of any hardware-package mapping that should be added to
7609 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
7610 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
7611
7612 &lt;p&gt;It could be possible to generate several of the mappings between
7613 packages and hardware. One source would be to look at packages with
7614 kernel modules, ie packages with *.ko files in /lib/modules/, and
7615 extract their modalias information. Another would be to look at
7616 packages with udev rules, ie packages with files in
7617 /lib/udev/rules.d/, and extract their vendor/model information to
7618 generate a modalias matching rule. I have not tested any of these to
7619 see if it work.&lt;/p&gt;
7620
7621 &lt;p&gt;If you want to help implementing a system to let us propose what
7622 packages to install when new hardware is plugged into a Debian
7623 machine, please send me an email or talk to me on
7624 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7625 </description>
7626 </item>
7627
7628 <item>
7629 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
7630 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
7631 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
7632 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
7633 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
7634 information, to find the packages that support a given piece of
7635 hardware, I refreshed my memory regarding modalias values, and decided
7636 to document the details. Here are my findings so far, also available
7637 in
7638 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7639 Debian Edu subversion repository&lt;/a&gt;:
7640
7641 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
7642
7643 &lt;p&gt;This document try to explain what the different types of modalias
7644 values stands for. It is in part based on information from
7645 &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;,
7646 &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;,
7647 &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
7648 &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;.
7649
7650 &lt;p&gt;The modalias entries for a given Linux machine can be found using
7651 this shell script:&lt;/p&gt;
7652
7653 &lt;pre&gt;
7654 find /sys -name modalias -print0 | xargs -0 cat | sort -u
7655 &lt;/pre&gt;
7656
7657 &lt;p&gt;The supported modalias globs for a given kernel module can be found
7658 using modinfo:&lt;/p&gt;
7659
7660 &lt;pre&gt;
7661 % /sbin/modinfo psmouse | grep alias:
7662 alias: serio:ty05pr*id*ex*
7663 alias: serio:ty01pr*id*ex*
7664 %
7665 &lt;/pre&gt;
7666
7667 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
7668
7669 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
7670 Bridge memory controller:&lt;/p&gt;
7671
7672 &lt;p&gt;&lt;blockquote&gt;
7673 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7674 &lt;/blockquote&gt;&lt;/p&gt;
7675
7676 &lt;p&gt;This represent these values:&lt;/p&gt;
7677
7678 &lt;pre&gt;
7679 v 00008086 (vendor)
7680 d 00002770 (device)
7681 sv 00001028 (subvendor)
7682 sd 000001AD (subdevice)
7683 bc 06 (bus class)
7684 sc 00 (bus subclass)
7685 i 00 (interface)
7686 &lt;/pre&gt;
7687
7688 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
7689 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
7690 0600. The 0600 class is a host bridge. Other useful bus values are
7691 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
7692
7693 &lt;p&gt;Not sure how to figure out the interface value, nor what it
7694 means.&lt;/p&gt;
7695
7696 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
7697
7698 &lt;p&gt;Some typical USB entries can look like this. This is an internal
7699 USB hub in a laptop:&lt;/p&gt;
7700
7701 &lt;p&gt;&lt;blockquote&gt;
7702 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7703 &lt;/blockquote&gt;&lt;/p&gt;
7704
7705 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
7706
7707 &lt;pre&gt;
7708 v 1D6B (device vendor)
7709 p 0001 (device product)
7710 d 0206 (bcddevice)
7711 dc 09 (device class)
7712 dsc 00 (device subclass)
7713 dp 00 (device protocol)
7714 ic 09 (interface class)
7715 isc 00 (interface subclass)
7716 ip 00 (interface protocol)
7717 &lt;/pre&gt;
7718
7719 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
7720 class is in the interface class section. For a simple USB web camera,
7721 these alias entries show up:&lt;/p&gt;
7722
7723 &lt;p&gt;&lt;blockquote&gt;
7724 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7725 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7726 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7727 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7728 &lt;/blockquote&gt;&lt;/p&gt;
7729
7730 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
7731 camera), 0101 is audio control device and 0102 is audio streaming (aka
7732 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
7733
7734 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
7735
7736 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
7737 receiver in a Thinkpad X40:&lt;/p&gt;
7738
7739 &lt;p&gt;&lt;blockquote&gt;
7740 acpi:IBM0071:PNP0511:
7741 &lt;/blockquote&gt;&lt;/p&gt;
7742
7743 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
7744
7745 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
7746
7747 &lt;p&gt;The DMI table contain lots of information about the computer case
7748 and model. This is an entry for a IBM Thinkpad X40, fetched from
7749 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
7750
7751 &lt;p&gt;&lt;blockquote&gt;
7752 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7753 &lt;/blockquote&gt;&lt;/p&gt;
7754
7755 &lt;p&gt;The values present are&lt;/p&gt;
7756
7757 &lt;pre&gt;
7758 bvn IBM (BIOS vendor)
7759 bvr 1UETB6WW(1.66) (BIOS version)
7760 bd 06/15/2005 (BIOS date)
7761 svn IBM (system vendor)
7762 pn 2371H4G (product name)
7763 pvr ThinkPadX40 (product version)
7764 rvn IBM (board vendor)
7765 rn 2371H4G (board name)
7766 rvr NotAvailable (board version)
7767 cvn IBM (chassis vendor)
7768 ct 10 (chassis type)
7769 cvr NotAvailable (chassis version)
7770 &lt;/pre&gt;
7771
7772 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
7773 found in the dmidecode source:&lt;/p&gt;
7774
7775 &lt;pre&gt;
7776 3 Desktop
7777 4 Low Profile Desktop
7778 5 Pizza Box
7779 6 Mini Tower
7780 7 Tower
7781 8 Portable
7782 9 Laptop
7783 10 Notebook
7784 11 Hand Held
7785 12 Docking Station
7786 13 All In One
7787 14 Sub Notebook
7788 15 Space-saving
7789 16 Lunch Box
7790 17 Main Server Chassis
7791 18 Expansion Chassis
7792 19 Sub Chassis
7793 20 Bus Expansion Chassis
7794 21 Peripheral Chassis
7795 22 RAID Chassis
7796 23 Rack Mount Chassis
7797 24 Sealed-case PC
7798 25 Multi-system
7799 26 CompactPCI
7800 27 AdvancedTCA
7801 28 Blade
7802 29 Blade Enclosing
7803 &lt;/pre&gt;
7804
7805 &lt;p&gt;The chassis type values are not always accurately set in the DMI
7806 table. For example my home server is a tower, but the DMI modalias
7807 claim it is a desktop.&lt;/p&gt;
7808
7809 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
7810
7811 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
7812 test machine:&lt;/p&gt;
7813
7814 &lt;p&gt;&lt;blockquote&gt;
7815 serio:ty01pr00id00ex00
7816 &lt;/blockquote&gt;&lt;/p&gt;
7817
7818 &lt;p&gt;The values present are&lt;/p&gt;
7819
7820 &lt;pre&gt;
7821 ty 01 (type)
7822 pr 00 (prototype)
7823 id 00 (id)
7824 ex 00 (extra)
7825 &lt;/pre&gt;
7826
7827 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
7828 the valid values are.&lt;/p&gt;
7829
7830 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
7831
7832 &lt;p&gt;There are heaps of other modalias subtypes according to
7833 file2alias.c. There is the rest of the list from that source: amba,
7834 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7835 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7836 vmbus, x86cpu and zorro. I did not spend time documenting all of
7837 these, as they do not seem relevant for my intended use with mapping
7838 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
7839
7840 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
7841
7842 &lt;p&gt;To check which kernel modules provide support for a given modalias,
7843 one can use the following shell script:&lt;/p&gt;
7844
7845 &lt;pre&gt;
7846 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
7847 echo &quot;$id&quot; ; \
7848 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
7849 done
7850 &lt;/pre&gt;
7851
7852 &lt;p&gt;The output can look like this (only the first few entries as the
7853 list is very long on my test machine):&lt;/p&gt;
7854
7855 &lt;pre&gt;
7856 acpi:ACPI0003:
7857 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
7858 acpi:device:
7859 FATAL: Module acpi:device: not found.
7860 acpi:IBM0068:
7861 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
7862 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
7863 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
7864 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7865 acpi:IBM0071:PNP0511:
7866 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
7867 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
7868 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
7869 [...]
7870 &lt;/pre&gt;
7871
7872 &lt;p&gt;If you want to help implementing a system to let us propose what
7873 packages to install when new hardware is plugged into a Debian
7874 machine, please send me an email or talk to me on
7875 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
7876
7877 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
7878 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
7879 in /sys/ with space in them.&lt;/p&gt;
7880 </description>
7881 </item>
7882
7883 <item>
7884 <title>Moved the pymissile Debian packaging to collab-maint</title>
7885 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7887 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7888 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7889 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7890 Launcher and updated the Debian package
7891 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7892 sure udev will fix the device permissions when it is plugged in. I
7893 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7894 hopefully make the package be proposed by jockey in Ubuntu when a user
7895 plug in his rocket launcher. In the process I moved the source to a
7896 git repository under collab-maint, to make it easier for any DD to
7897 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7898 is not very active, but the software still work for me even after five
7899 years of relative silence. The new git repository is not listed in
7900 the uploaded package yet, because I want to test the other changes a
7901 bit more before I upload the new version. If you want to check out
7902 the new version with a .desktop file included, visit the
7903 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7904 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7905 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7906 </description>
7907 </item>
7908
7909 <item>
7910 <title>Lets make hardware dongles easier to use in Debian</title>
7911 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7913 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7914 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7915 general, is that there is a great package management system with the
7916 ability to automatically install software packages by downloading them
7917 from the distribution mirrors, but no way to get it to automatically
7918 install the packages I need to use the hardware I plug into my
7919 machine. Even if the package to use it is easily available from the
7920 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7921 suggest to automatically install the python-nxt, nbc and t2n packages
7922 I need to talk to it. When I plug in a Yubikey, it could propose the
7923 yubikey-personalization package. The information required to do this
7924 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7925
7926 &lt;p&gt;Some years ago, I proposed to
7927 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7928 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7929 simple:
7930
7931 &lt;ul&gt;
7932
7933 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7934 starting when a user log in.&lt;/li&gt;
7935
7936 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7937 hardware is inserted into the computer.&lt;/li&gt;
7938
7939 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7940 database mapping to packages, and take note of any non-installed
7941 packages.&lt;/li&gt;
7942
7943 &lt;li&gt;Show a message to the user proposing to install the discovered
7944 package, and make it easy to install it.&lt;/li&gt;
7945
7946 &lt;/ul&gt;
7947
7948 &lt;p&gt;I am not sure what the best way to implement this is, but my
7949 initial idea was to use dbus events to discover new hardware, the
7950 discover database to find packages and
7951 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7952 packages.&lt;/p&gt;
7953
7954 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7955 draft package is now checked into
7956 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7957 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7958 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7959 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7960 the relevant packages in Debian, and uploaded a new version
7961 2.2013.01.09 to unstable. I also discovered that the current
7962 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7963 package in Debian no longer discovered any USB devices, because
7964 /proc/bus/usb/devices is no longer present. I ported it to use
7965 libusb as a fall back option to get it working. The fixed package
7966 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7967 because of the freeze).&lt;/p&gt;
7968
7969 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7970 desktop notification to show up (only once, the first time it is
7971 inserted):&lt;/p&gt;
7972
7973 &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;
7974
7975 &lt;p&gt;For this prototype to be really useful, some way to automatically
7976 install the proposed packages by pressing the &quot;Please install
7977 program(s)&quot; button should to be implemented.&lt;/p&gt;
7978
7979 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7980 happen, please help me update the discover-data database with mappings
7981 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7982 list the package you would like to have installed when a given
7983 hardware device is inserted into your computer, and report bugs using
7984 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7985 such mapping, please let me know.&lt;/p&gt;
7986
7987 &lt;p&gt;This prototype need more work, and there are several questions that
7988 should be considered before it is ready for production use. Is dbus
7989 the correct way to detect new hardware? At the moment I look for HAL
7990 dbus events on the system bus, because that is the events I could see
7991 on my Debian Squeeze KDE desktop. Are there better events to use?
7992 How should the user be notified? Is the desktop notification
7993 mechanism the best option, or should the background daemon raise a
7994 popup instead? How should packages be installed? When should they
7995 not be installed?&lt;/p&gt;
7996
7997 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7998 please send me an email. :)&lt;/p&gt;
7999 </description>
8000 </item>
8001
8002 <item>
8003 <title>New IRC channel for LEGO designers using Debian</title>
8004 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
8005 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
8006 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
8007 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
8008 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
8009 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
8010 discovered I had to build all the tools myself because none were
8011 already in Debian Squeeze. If Debian support for LEGO is something
8012 you care about, please join me on the IRC channel
8013 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
8014 irc.debian.org). There is a lot that could be done to improve the
8015 Debian support for LEGO designers. For example both CAD software
8016 and Mindstorm compilers are missing. :)&lt;/p&gt;
8017
8018 &lt;p&gt;Update 2012-01-03: A
8019 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
8020 including links to Lego related packages is now available.&lt;/p&gt;
8021 </description>
8022 </item>
8023
8024 <item>
8025 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
8026 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
8027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
8028 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
8029 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
8030 year! I hope next year will prove to be a good year.&lt;/p&gt;
8031
8032 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
8033 decentralised &quot;currency&quot; that allow people to transfer bitcoins
8034 between each other with minimal overhead, is a very interesting
8035 experiment. And as I wrote a few days ago, the bitcoin situation in
8036 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
8037 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
8038 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
8039 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
8040 for one of the ftpmasters to approve the new bitcoin-qt package
8041 name.&lt;/p&gt;
8042
8043 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
8044 team in Debian, you can easily test the package in Debian Squeeze
8045 using the following steps to get a set of working packages:&lt;/p&gt;
8046
8047 &lt;blockquote&gt;&lt;pre&gt;
8048 git clone git://git.debian.org/git/collab-maint/bitcoin
8049 cd bitcoin
8050 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8051 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8052 &lt;/pre&gt;&lt;/blockquote&gt;
8053
8054 &lt;p&gt;You might have to install some build dependencies as well. The
8055 list of commands should give you two packages, bitcoind and
8056 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8057 client will download the complete set of bitcoin &quot;blocks&quot;, which need
8058 around 5.6 GiB of data on my machine at the moment. Make sure your
8059 ~/.bitcoin/ directory have lots of spare room if you want to download
8060 all the blocks. The client will warn if the disk is getting full, so
8061 there is not really a problem if you got too little room, but you will
8062 not be able to get all the features out of the client.&lt;/p&gt;
8063
8064 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8065 activities, please send Bitcoin donations to my address
8066 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8067 </description>
8068 </item>
8069
8070 <item>
8071 <title>A word on bitcoin support in Debian</title>
8072 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
8073 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
8074 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
8075 <description>&lt;p&gt;It has been a while since I wrote about
8076 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
8077 peer-to-peer based crypto-currency, and the reason is simply that I
8078 have been busy elsewhere. But two days ago, I started looking at the
8079 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
8080 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
8081 is now maintained by a
8082 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
8083 people&lt;/a&gt;, and the grunt work had already been done by this team. We
8084 owe a huge thank you to all these team members. :)
8085 But I was sad to discover that the bitcoin client is missing in
8086 Wheezy. It is only available in Sid (and an outdated client from
8087 backports). The client had several RC bugs registered in BTS blocking
8088 it from entering testing. To try to help the team and improve the
8089 situation, I spent some time providing patches and triaging the bug
8090 reports. I also had a look at the bitcoin package available from Matt
8091 Corallo in a
8092 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
8093 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
8094 Debian package.&lt;/p&gt;
8095
8096 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
8097 IRC, I pushed several patches into the collab-maint git repository to
8098 improve the package. It now contains fixes for the RC issues (not from
8099 me, but fixed by Scott Howard), build rules for a Qt GUI client
8100 package, konqueror support for the bitcoin: URI and bash completion
8101 setup. As I work on Debian Squeeze, I also created
8102 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
8103 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
8104 it and try to integrate it into the git repository before uploading a
8105 new version to unstable.
8106
8107 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
8108 centralized control currently exercised in the monetary system. I
8109 find it completely unacceptable that the USA government is collecting
8110 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8111 that the major credit card companies can block legal money
8112 transactions to Wikileaks. But for bitcoin to succeed, more people
8113 need to use bitcoins, and more people need to accept bitcoins when
8114 they sell products and services. Improving the bitcoin support in
8115 Debian is a small step in the right direction, but not enough.
8116 Unfortunately the user experience when browsing the web and wanting to
8117 pay with bitcoin is still not very good. The bitcoin: URI is a step
8118 in the right direction, but need to work in most or every browser in
8119 use. Also the bitcoin-qt client is too heavy to fire up to do a
8120 quick transaction. I believe there are other clients available, but
8121 have not tested them.&lt;/p&gt;
8122
8123 &lt;p&gt;My
8124 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
8125 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
8126 I received 20.15 BTC so far on the address I provided in my blog two
8127 years ago, as can be
8128 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
8129 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
8130 donation. The blockexplorer service demonstrates quite well that
8131 bitcoin is not quite anonymous and untracked. :) I wonder if the
8132 number of users have gone up since then. If you use bitcoin and want
8133 to show your support of my activity, please send Bitcoin donations to
8134 the same address as last time,
8135 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8136 </description>
8137 </item>
8138
8139 <item>
8140 <title>Git repository for song book for Computer Scientists</title>
8141 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
8142 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
8143 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
8144 <description>&lt;p&gt;As I
8145 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
8146 this summer&lt;/a&gt;, I have created a Computer Science song book a few
8147 years ago, and today I finally found time to create a public
8148 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
8149 repository for the project&lt;/a&gt;.&lt;/p&gt;
8150
8151 &lt;p&gt;If you want to help out, please clone the source and submit patches
8152 to the HTML version. To generate the PDF and PostScript version,
8153 please use prince XML, or let me know about a useful free software
8154 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
8155
8156 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
8157 PostScript formats at
8158 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
8159 Science Songbook&lt;/a&gt;.&lt;/p&gt;
8160 </description>
8161 </item>
8162
8163 <item>
8164 <title>Gratulerer med 19-årsdagen, Debian!</title>
8165 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
8166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
8167 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
8168 <description>&lt;p&gt;I dag fyller
8169 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
8170 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
8171 si gratulerer med dagen, Debian!&lt;/p&gt;
8172 </description>
8173 </item>
8174
8175 <item>
8176 <title>Song book for Computer Scientists</title>
8177 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
8178 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
8179 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
8180 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
8181 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
8182 collecting computer related songs for use at parties. The original
8183 version was written in LaTeX, but a few years ago I got help from
8184 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
8185 while keeping the ability to create a nice book in PDF format. I have
8186 not had time to maintain the book for a while now, and guess I should
8187 put it up on some public version control repository where others can
8188 help me extend and update the book. If anyone is volunteering to help
8189 me with this, send me an email. Also let me know if there are songs
8190 missing in my book.&lt;/p&gt;
8191
8192 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
8193 me today that I really should let all my readers share the joys of
8194 singing out load about programming, computers and computer networks.
8195 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
8196 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
8197 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
8198 Computer Science Songbook&lt;/a&gt;.
8199 </description>
8200 </item>
8201
8202 <item>
8203 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
8204 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
8205 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
8206 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
8207 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
8208 around 1000 at the moment. To be able to get help from the vendors
8209 when something go wrong, we want to keep the firmware on the servers
8210 up to date. If the firmware isn&#39;t the latest and greatest, the
8211 vendors typically refuse to start debugging any problems until the
8212 firmware is upgraded. So before every reboot, we want to upgrade the
8213 firmware, and we would really like everyone handling servers at the
8214 university to do this themselves when they plan to reboot a machine.
8215 For that to happen we at the unix server admin group need to provide
8216 the tools to do so.&lt;/p&gt;
8217
8218 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
8219 fetch and install the latest firmware for the servers we got. Most of
8220 our hardware are from Dell and HP, so I have focused on these servers
8221 so far. This blog post is about the Dell part.&lt;/P&gt;
8222
8223 &lt;p&gt;On the Dell FTP site I was lucky enough to find
8224 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
8225 with firmware information for all 11th generation servers, listing
8226 which firmware should be used on a given model and where on the FTP
8227 site I can find it. Using a simple perl XML parser I can then
8228 download the shell scripts Dell provides to do firmware upgrades from
8229 within Linux and reboot when all the firmware is primed and ready to
8230 be activated on the first reboot.&lt;/p&gt;
8231
8232 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
8233 Are there anyone working on similar tools for firmware upgrading all
8234 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
8235
8236 &lt;p&gt;&lt;pre&gt;
8237 #!/usr/bin/perl
8238 use strict;
8239 use warnings;
8240 use File::Temp qw(tempdir);
8241 BEGIN {
8242 # Install needed RHEL packages if missing
8243 my %rhelmodules = (
8244 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
8245 );
8246 for my $module (keys %rhelmodules) {
8247 eval &quot;use $module;&quot;;
8248 if ($@) {
8249 my $pkg = $rhelmodules{$module};
8250 system(&quot;yum install -y $pkg&quot;);
8251 eval &quot;use $module;&quot;;
8252 }
8253 }
8254 }
8255 my $errorsto = &#39;pere@hungry.com&#39;;
8256
8257 upgrade_dell();
8258
8259 exit 0;
8260
8261 sub run_firmware_script {
8262 my ($opts, $script) = @_;
8263 unless ($script) {
8264 print STDERR &quot;fail: missing script name\n&quot;;
8265 exit 1
8266 }
8267 print STDERR &quot;Running $script\n\n&quot;;
8268
8269 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
8270 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
8271 } else {
8272 print STDERR &quot;fail: firmware script returned error\n&quot;;
8273 }
8274 }
8275
8276 sub run_firmware_scripts {
8277 my ($opts, @dirs) = @_;
8278 # Run firmware packages
8279 for my $dir (@dirs) {
8280 print STDERR &quot;info: Running scripts in $dir\n&quot;;
8281 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
8282 while (my $s = readdir $dh) {
8283 next if $s =~ m/^\.\.?/;
8284 run_firmware_script($opts, &quot;$dir/$s&quot;);
8285 }
8286 closedir $dh;
8287 }
8288 }
8289
8290 sub download {
8291 my $url = shift;
8292 print STDERR &quot;info: Downloading $url\n&quot;;
8293 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
8294 }
8295
8296 sub upgrade_dell {
8297 my @dirs;
8298 my $product = `dmidecode -s system-product-name`;
8299 chomp $product;
8300
8301 if ($product =~ m/PowerEdge/) {
8302
8303 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8304 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
8305
8306 my $tmpdir = tempdir(
8307 CLEANUP =&gt; 1
8308 );
8309 chdir($tmpdir);
8310 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
8311 system(&#39;gunzip Catalog.xml.gz&#39;);
8312 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
8313 # -q is quiet, disabling interactivity and reducing console output
8314 my $fwopts = &quot;-q&quot;;
8315 if (@paths) {
8316 for my $url (@paths) {
8317 fetch_dell_fw($url);
8318 }
8319 run_firmware_scripts($fwopts, $tmpdir);
8320 } else {
8321 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8322 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8323 }
8324 chdir(&#39;/&#39;);
8325 } else {
8326 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
8327 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
8328 }
8329 }
8330
8331 sub fetch_dell_fw {
8332 my $path = shift;
8333 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
8334 download($url);
8335 }
8336
8337 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8338 # firmware packages to download from Dell. Only work for Linux
8339 # machines and 11th generation Dell servers.
8340 sub fetch_dell_fw_list {
8341 my $filename = shift;
8342
8343 my $product = `dmidecode -s system-product-name`;
8344 chomp $product;
8345 my ($mybrand, $mymodel) = split(/\s+/, $product);
8346
8347 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
8348
8349 my $xml = XMLin($filename);
8350 my @paths;
8351 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
8352 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
8353 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
8354 my $oscode;
8355 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
8356 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
8357 } else {
8358 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
8359 }
8360 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
8361 {
8362 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
8363 }
8364 }
8365 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
8366 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
8367
8368 # Drop application packages, only firmware and BIOS
8369 next if &#39;APAC&#39; eq $componenttype;
8370
8371 my $cpath = $component-&gt;{path};
8372 for my $path (@paths) {
8373 if ($cpath =~ m%/$path$%) {
8374 push(@paths, $cpath);
8375 }
8376 }
8377 }
8378 return @paths;
8379 }
8380 &lt;/pre&gt;
8381
8382 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
8383 it could work on other platforms with some tweaking. Anyone know a
8384 index like Catalog.xml is available from HP for HP servers? At the
8385 moment I maintain a similar list manually and it is quickly getting
8386 outdated.&lt;/p&gt;
8387 </description>
8388 </item>
8389
8390 <item>
8391 <title>How is booting into runlevel 1 different from single user boots?</title>
8392 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
8393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
8394 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
8395 <description>&lt;p&gt;Wouter Verhelst have some
8396 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
8397 comments and opinions&lt;/a&gt; on my blog post on
8398 &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
8399 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
8400 &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
8401 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
8402 small piece of his comment now, and though it best to address the
8403 misunderstanding he bring forward:&lt;/p&gt;
8404
8405 &lt;p&gt;&lt;blockquote&gt;
8406 Currently, a system admin has four options: [...] boot to a
8407 single-user system (by adding &#39;single&#39; to the kernel command line;
8408 this runs rcS and rc1 scripts)
8409 &lt;/blockquote&gt;&lt;/p&gt;
8410
8411 &lt;p&gt;This make me believe Wouter believe booting into single user mode
8412 and booting into runlevel 1 is the same. I am not surprised he
8413 believe this, because it would make sense and is a quite sensible
8414 thing to believe. But because the boot in Debian is slightly broken,
8415 runlevel 1 do not work properly and it isn&#39;t the same as single user
8416 mode. I&#39;ll try to explain what is actually happing, but it is a bit
8417 hard to explain.&lt;/p&gt;
8418
8419 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
8420 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
8421 executed in single user mode is sulogin. Single user mode is a boot
8422 state &quot;between&quot; the runlevels, and when booting into single user mode,
8423 only the scripts in /etc/rcS.d/ are executed before the init process
8424 enters the single user state. When switching to runlevel 1, the state
8425 is in fact not ending in runlevel 1, but it passes through runlevel 1
8426 and end up in the single user mode (see /etc/rc1.d/S03single, which
8427 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
8428 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
8429 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8430 mode).&lt;/p&gt;
8431
8432 &lt;p&gt;This summary might make it clearer. When booting for the first
8433 time into single user mode, the following commands are executed:
8434 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
8435 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
8436 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
8437 trying to continue after visiting single user mode. Not all services
8438 are started again as they should, causing the machine to end up in an
8439 unpredicatble state. This is why Debian admins recommend rebooting
8440 after visiting single user mode.&lt;/p&gt;
8441
8442 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
8443 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
8444 to runlevel 1, the services started from /etc/rcS.d/ are not properly
8445 stopped when passing through the scripts in /etc/rc1.d/, and not
8446 started again when switching away from runlevel 1 to the runlevels
8447 2-5. I believe the problem is best fixed by moving all the scripts
8448 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
8449 functioning single user mode during boot.&lt;/p&gt;
8450
8451 &lt;p&gt;I have spent several years investigating the Debian boot system,
8452 and discovered this problem a few years ago. I suspect it originates
8453 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
8454 </description>
8455 </item>
8456
8457 <item>
8458 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
8459 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
8460 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
8461 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
8462 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
8463 are started from /etc/rcS.d/. In fact, there is a bite more of them
8464 than make sense, and this causes a few problems. What kind of
8465 problems, you might ask. There are at least two problems. The first
8466 is that it is not possible to recover a machine after switching to
8467 runlevel 1. One need to actually reboot to get the machine back to
8468 the expected state. The other is that single user boot will sometimes
8469 run into problems because some of the subsystems are activated before
8470 the root login is presented, causing problems when trying to recover a
8471 machine from a problem in that subsystem. A minor additional point is
8472 that moving more scripts out of rcS.d/ and into the other rc#.d/
8473 directories will increase the amount of scripts that can run in
8474 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
8475
8476 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
8477 scripts that _have_ to execute before the root login prompt is
8478 presented during a single user boot should go there. Everything else
8479 should go into the numeric runlevels. This means things like
8480 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8481 the numeric runlevels. Today in Debian, there are around 115 init.d
8482 scripts that are started from rcS.d/, and most of them should be moved
8483 out. Do your package have one of them? Please help us make single
8484 user and runlevel 1 better by moving it.&lt;/p&gt;
8485
8486 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
8487 etc. should still be started from rcS.d/, but there is for example no
8488 need to have the network enabled before the single user login prompt
8489 is presented.&lt;/p&gt;
8490
8491 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
8492 Debian systems working while scripts migrate and during upgrades, the
8493 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8494 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8495 and the next ones can only be moved when their dependencies have been
8496 moved first. This migration must be done sequentially while we ensure
8497 that the package system upgrade packages in the right order to keep
8498 the system state correct. This will require some coordination when it
8499 comes to network related packages, but most of the packages with
8500 scripts that should migrate do not have anything in rcS.d/ depending
8501 on them. Some packages have already been updated, like the sudo
8502 package, while others are still left to do. I wish I had time to work
8503 on this myself, but real live constrains make it unlikely that I will
8504 find time to push this forward.&lt;/p&gt;
8505 </description>
8506 </item>
8507
8508 <item>
8509 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
8510 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
8511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
8512 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
8513 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
8514 mentioned the issues I believe should be improved in Debian for its
8515 desktop to be useful for more people. The use case for this is my
8516 parents, which are currently running Kubuntu which solve the
8517 issues.&lt;/p&gt;
8518
8519 &lt;p&gt;I suspect these four missing features are not very hard to
8520 implement. After all, they are present in Ubuntu, so if we wanted to
8521 do this in Debian we would have a source.&lt;/p&gt;
8522
8523 &lt;ol&gt;
8524
8525 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
8526 are new packages available for upgrades, a icon in the KDE status bar
8527 indicate this, and clicking on it will activate the simple upgrade
8528 tool to handle it. I have no problem guiding both of my parents
8529 through the process over the phone. If a kernel reboot is required,
8530 this too is indicated by the status bars and the upgrade tool. Last
8531 time I checked, nothing with the same features was working in KDE in
8532 Debian.&lt;/li&gt;
8533
8534 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
8535 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
8536 currently have a handler for, it will ask the user if the system
8537 should search for a package that would add support for this MIME type,
8538 and if the user say yes, the APT sources will be searched for packages
8539 advertising the MIME type in their control file (visible in the
8540 Packages file in the APT archive). If one or more packages are found,
8541 it is a simple click of the mouse to add support for the missing mime
8542 type. If the package require the user to accept some non-free
8543 license, this is explained to the user. The entire process make it
8544 more clear to the user why something do not work in the browser, and
8545 make the chances higher for the user to blame the web page authors and
8546 not the browser for any missing features.&lt;/li&gt;
8547
8548 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
8549 handlers.&lt;/strong&gt; When the media players encounter a format or codec
8550 it is not supporting, a dialog pop up asking the user if the system
8551 should search for a package that would add support for it. This
8552 happen with things like MP3, Windows Media or H.264. The selection
8553 and installation procedure is very similar to the Firefox browser
8554 plugin handling. This is as far as I know implemented using a
8555 gstreamer hook. The end result is that the user easily get access to
8556 the codecs that are present from the APT archives available, while
8557 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
8558
8559 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
8560 displaying a text/plain file in my Debian browser, it will propose to
8561 start emacs to show it. If I remember correctly, when doing the same
8562 in Kunbutu it show the file as a text file in the browser. At least I
8563 know Opera will show text files within the browser. I much prefer the
8564 latter behaviour.&lt;/li&gt;
8565
8566 &lt;/ol&gt;
8567
8568 &lt;p&gt;There are other nice features as well, like the simplified suite
8569 upgrader, but given that I am the one mostly doing the dist-upgrade,
8570 it do not matter much.&lt;/p&gt;
8571
8572 &lt;p&gt;I really hope we could get these features in place for the next
8573 Debian release. It would require the coordinated effort of several
8574 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
8575 </description>
8576 </item>
8577
8578 <item>
8579 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
8580 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
8581 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
8582 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
8583 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
8584 site is build on Debian/Squeeze, and this platform was chosen because
8585 I am most familiar with Debian (being a Debian Developer for around 10
8586 years) because it is the latest stable Debian release which should get
8587 security support for a few years.&lt;/p&gt;
8588
8589 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
8590 that are missing in Debian at the moment. It would be great if these
8591 modules were added to the Debian archive, allowing anyone to set up
8592 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
8593 in their own country using only Debian packages. The list of modules
8594 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
8595 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
8596 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8597 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8598 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8599 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8600 easier in the future.&lt;/p&gt;
8601
8602 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
8603 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
8604 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
8605 with the responsibility of tracking security problems, which I really
8606 do not have time for.&lt;/p&gt;
8607 </description>
8608 </item>
8609
8610 <item>
8611 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
8612 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
8613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
8614 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
8615 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
8616 posts have been in Norwegian the last few weeks, so here is a short
8617 update in English.&lt;/p&gt;
8618
8619 &lt;p&gt;The kids still keep me too busy to get much free software work
8620 done, but I did manage to organise a project to get a Norwegian port
8621 of the British service
8622 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
8623 and it has been running for a month now. The entire project has been
8624 organised by me and two others. Around Christmas we gathered sponsors
8625 to fund the development work. In January I drafted a contract with
8626 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
8627 and in February the development took place. Most of it involved
8628 converting the source to use GPS coordinates instead of British
8629 easting/northing, and the resulting code should be a lot easier to get
8630 running in any country by now. The Norwegian
8631 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
8632 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
8633 source and the source for administrative borders in Norway, and
8634 support for this had to be added/fixed.&lt;/p&gt;
8635
8636 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
8637 polishing the system before we announced it March 7th. The system is
8638 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
8639 problem reports in a few weeks. Soon we hope to announce the Android
8640 and iPhone versions making it even easier to report problems with the
8641 public infrastructure.&lt;/p&gt;
8642
8643 &lt;p&gt;Perhaps something to consider for those of you in countries without
8644 such service?&lt;/p&gt;
8645 </description>
8646 </item>
8647
8648 <item>
8649 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
8650 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
8651 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
8652 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
8653 <description>&lt;p&gt;The last few days I have looked at ways to track open security
8654 issues here at my work with the University of Oslo. My idea is that
8655 it should be possible to use the information about security issues
8656 available on the Internet, and check our locally
8657 maintained/distributed software against this information. It should
8658 allow us to verify that no known security issues are forgotten. The
8659 CVE database listing vulnerabilities seem like a great central point,
8660 and by using the package lists from Debian mapped to CVEs provided by
8661 the testing security team, I believed it should be possible to figure
8662 out which security holes were present in our free software
8663 collection.&lt;/p&gt;
8664
8665 &lt;p&gt;After reading up on the topic, it became obvious that the first
8666 building block is to be able to name software packages in a unique and
8667 consistent way across data sources. I considered several ways to do
8668 this, for example coming up with my own naming scheme like using URLs
8669 to project home pages or URLs to the Freshmeat entries, or using some
8670 existing naming scheme. And it seem like I am not the first one to
8671 come across this problem, as MITRE already proposed and implemented a
8672 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
8673 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
8674 software, hardware and other platform components. The CPE ids are
8675 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
8676 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
8677 issues for any CPE name. With this in place, all I need to do is to
8678 locate the CPE id for the software packages we use at the university.
8679 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
8680 NVD entry if a CVE for the package exist).&lt;/p&gt;
8681
8682 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
8683 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
8684 check out, one could look up
8685 &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
8686 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
8687 The most recent one is
8688 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
8689 and at the bottom of the NVD page for this vulnerability the complete
8690 list of affected versions is provided.&lt;/p&gt;
8691
8692 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
8693 for offline processing of issues. Using this dump, I&#39;ve written a
8694 small script taking a list of CPEs as input and list all CVEs
8695 affecting the packages represented by these CPEs. One give it CPEs
8696 with version numbers as specified above and get a list of open
8697 security issues out.&lt;/p&gt;
8698
8699 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
8700 information need to be high. For that to happen, I believe as many as
8701 possible need to use and contribute to the NVD database. I notice
8702 RHEL is providing
8703 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
8704 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
8705 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
8706
8707 &lt;p&gt;To get an idea about the quality for free software, I spent some
8708 time making it possible to compare the CVE database from Debian with
8709 the CVE database in NVD. The result look fairly good, but there are
8710 some inconsistencies in NVD (same software package having several
8711 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8712 Debian believe are affected by a CVE). Hope to find time to improve
8713 the quality of NVD, but that require being able to get in touch with
8714 someone maintaining it. So far my three emails with questions and
8715 corrections have not seen any reply, but I hope contact can be
8716 established soon.&lt;/p&gt;
8717
8718 &lt;p&gt;An interesting application for CPEs is cross platform package
8719 mapping. It would be useful to know which packages in for example
8720 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8721 this would be trivial if all linux distributions provided CPE entries
8722 for their packages.&lt;/p&gt;
8723 </description>
8724 </item>
8725
8726 <item>
8727 <title>Which module is loaded for a given PCI and USB device?</title>
8728 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
8729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
8730 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
8731 <description>&lt;p&gt;In the
8732 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
8733 package in Debian, there is a script to report useful information
8734 about the running hardware for use when people report missing
8735 information. One part of this script that I find very useful when
8736 debugging hardware problems, is the part mapping loaded kernel module
8737 to the PCI device it claims. It allow me to quickly see if the kernel
8738 module I expect is driving the hardware I am struggling with. To see
8739 the output, make sure discover-data is installed and run
8740 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
8741 one of my machines like this:&lt;/p&gt;
8742
8743 &lt;pre&gt;
8744 loaded modules:
8745 10de:03eb i2c_nforce2
8746 10de:03f1 ohci_hcd
8747 10de:03f2 ehci_hcd
8748 10de:03f0 snd_hda_intel
8749 10de:03ec pata_amd
8750 10de:03f6 sata_nv
8751 1022:1103 k8temp
8752 109e:036e bttv
8753 109e:0878 snd_bt87x
8754 11ab:4364 sky2
8755 &lt;/pre&gt;
8756
8757 &lt;p&gt;The code in question look like this, slightly modified for
8758 readability and to drop the output to file descriptor 3:&lt;/p&gt;
8759
8760 &lt;pre&gt;
8761 if [ -d /sys/bus/pci/devices/ ] ; then
8762 echo loaded pci modules:
8763 (
8764 cd /sys/bus/pci/devices/
8765 for address in * ; do
8766 if [ -d &quot;$address/driver/module&quot; ] ; then
8767 module=`cd $address/driver/module ; pwd -P | xargs basename`
8768 if grep -q &quot;^$module &quot; /proc/modules ; then
8769 address=$(echo $address |sed s/0000://)
8770 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
8771 echo &quot;$id $module&quot;
8772 fi
8773 fi
8774 done
8775 )
8776 echo
8777 fi
8778 &lt;/pre&gt;
8779
8780 &lt;p&gt;Similar code could be used to extract USB device module
8781 mappings:&lt;/p&gt;
8782
8783 &lt;pre&gt;
8784 if [ -d /sys/bus/usb/devices/ ] ; then
8785 echo loaded usb modules:
8786 (
8787 cd /sys/bus/usb/devices/
8788 for address in * ; do
8789 if [ -d &quot;$address/driver/module&quot; ] ; then
8790 module=`cd $address/driver/module ; pwd -P | xargs basename`
8791 if grep -q &quot;^$module &quot; /proc/modules ; then
8792 address=$(echo $address |sed s/0000://)
8793 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
8794 if [ &quot;$id&quot; ] ; then
8795 echo &quot;$id $module&quot;
8796 fi
8797 fi
8798 fi
8799 done
8800 )
8801 echo
8802 fi
8803 &lt;/pre&gt;
8804
8805 &lt;p&gt;This might perhaps be something to include in other tools as
8806 well.&lt;/p&gt;
8807 </description>
8808 </item>
8809
8810 <item>
8811 <title>How to test if a laptop is working with Linux</title>
8812 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
8813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
8814 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
8815 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
8816 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
8817 batch of computers will work with Linux. Every year for the last few
8818 years the university have organised shared bid of a few thousand
8819 computers, and this year HP won the bid. Two different desktops and
8820 five different laptops are on the list this year. We in the UNIX
8821 group want to know which one of these computers work well with RHEL
8822 and Ubuntu, the two Linux distributions we currently handle at the
8823 university.&lt;/p&gt;
8824
8825 &lt;p&gt;My test method is simple, and I share it here to get feedback and
8826 perhaps inspire others to test hardware as well. To test, I PXE
8827 install the OS version of choice, and log in as my normal user and run
8828 a few applications and plug in selected pieces of hardware. When
8829 something fail, I make a note about this in the test matrix and move
8830 on. If I have some spare time I try to report the bug to the OS
8831 vendor, but as I only have the machines for a short time, I rarely
8832 have the time to do this for all the problems I find.&lt;/p&gt;
8833
8834 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
8835 I perform on a new model.&lt;/p&gt;
8836
8837 &lt;ul&gt;
8838
8839 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
8840 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8841 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
8842
8843 &lt;li&gt;Is X.org working? If the graphical login screen show up after
8844 installation, X.org is working.&lt;/li&gt;
8845
8846 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
8847 package mesa-utils on Ubuntu) and writing down the frames per second
8848 reported by the program.&lt;/li&gt;
8849
8850 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
8851 logging in, and if I can hear this the test is successful. If there
8852 are several audio exits on the machine, I try them all and check if
8853 the Gnome/KDE audio mixer can control where to send the sound. I
8854 normally test this by playing
8855 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
8856 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
8857
8858 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
8859 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
8860
8861 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
8862 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
8863
8864 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
8865 picture from the v4l device show up.&lt;/li&gt;
8866
8867 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8868 any bluetooth devices are discovered. In my office, I normally see a
8869 few.&lt;/li&gt;
8870
8871 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
8872 memory modules lying around, and stick them in and see if Gnome/KDE
8873 notice this.&lt;/li&gt;
8874
8875 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
8876 special button work, and if the laptop continue to work after
8877 resume.&lt;/li&gt;
8878
8879 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
8880 adjusting background light, switching on/off external video output,
8881 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8882 laptop to laptop, so I just write down which are working and which are
8883 not.&lt;/li&gt;
8884
8885 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8886 acceleration sensors etc. I rarely test these, as I do not know how
8887 to quickly test if they are working or not, so I only document their
8888 existence.&lt;/li&gt;
8889
8890 &lt;/ul&gt;
8891
8892 &lt;p&gt;By now I suspect you are really curious what the test results are
8893 for the HP machines I am testing. I&#39;m not done yet, so I will report
8894 the test results later. For now I can report that HP 8100 Elite work
8895 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8896 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8897 can see, I have most machines left to test. One interesting
8898 observation is that Ubuntu Lucid has almost twice the frame rate than
8899 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8900 </description>
8901 </item>
8902
8903 <item>
8904 <title>Some thoughts on BitCoins</title>
8905 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8906 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8907 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8908 <description>&lt;p&gt;As I continue to explore
8909 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8910 what properties the system have, and how it will be affected by laws
8911 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8912
8913 &lt;p&gt;One interesting thing to note is that since the transactions are
8914 verified using a peer to peer network, all details about a transaction
8915 is known to everyone. This means that if a BitCoin address has been
8916 published like I did with mine in my initial post about BitCoin, it is
8917 possible for everyone to see how many BitCoins have been transfered to
8918 that address. There is even a web service to look at the details for
8919 all transactions. There I can see that my address
8920 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8921 have received 16.06 Bitcoin, the
8922 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8923 address of Simon Phipps have received 181.97 BitCoin and the address
8924 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8925 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8926 every one of you that donated bitcoins to support my activity. The
8927 fact that anyone can see how much money was transfered to a given
8928 address make it more obvious why the BitCoin community recommend to
8929 generate and hand out a new address for each transaction. I&#39;m told
8930 there is no way to track which addresses belong to a given person or
8931 organisation without the person or organisation revealing it
8932 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8933
8934 &lt;p&gt;In Norway, and in most other countries, there are laws and
8935 regulations limiting how much money one can transfer across the border
8936 without declaring it. There are money laundering, tax and accounting
8937 laws and regulations I would expect to apply to the use of BitCoin.
8938 If the Skolelinux foundation
8939 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8940 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8941 normal bank transfers like EFF is doing, how should this be accounted?
8942 Given that it is impossible to know if money can cross the border or
8943 not, should everything or nothing be declared? What exchange rate
8944 should be used when calculating taxes? Would receivers have to pay
8945 income tax if the foundation were to pay Skolelinux contributors in
8946 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8947
8948 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8949 accepted by a lot of users. It must be possible to get easy access to
8950 the currency (as a wage or using currency exchanges), and it must be
8951 easy to spend it. At the moment BitCoin seem fairly easy to get
8952 access to, but there are very few places to spend it. I am not really
8953 a regular user of any of the vendor types currently accepting BitCoin,
8954 so I wonder when my kind of shop would start accepting BitCoins. I
8955 would like to buy electronics, travels and subway tickets, not herbs
8956 and books. :) The currency is young, and this will improve over time
8957 if it become popular, but I suspect regular banks will start to lobby
8958 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8959 will claim it is helping fund terrorism and money laundering (which
8960 probably would be true, as is any currency in existence), but I
8961 believe the problems should be solved elsewhere and not by blaming
8962 currencies.&lt;/p&gt;
8963
8964 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8965 CPU intensive process that depend on a bit of luck as well (as one is
8966 competing against all the other miners currently spending CPU cycles
8967 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8968 BitCoin when this happen. Yesterday I came across the obvious way to
8969 join forces to increase ones changes of getting at least some coins,
8970 by coordinating the work on mining BitCoins across several machines
8971 and people, and sharing the result if one is lucky and get the 50
8972 BitCoins. Check out
8973 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8974 if this sounds interesting. I have not had time to try to set up a
8975 machine to participate there yet, but have seen that running on ones
8976 own for a few days have not yield any BitCoins througth mining
8977 yet.&lt;/p&gt;
8978
8979 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8980 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8981 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8982 it was interesting to read. The arguments presented seem to be
8983 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8984 </description>
8985 </item>
8986
8987 <item>
8988 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8989 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8991 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8992 <description>&lt;p&gt;With this weeks lawless
8993 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8994 attacks&lt;/a&gt; on Wikileak and
8995 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8996 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8997 not be trusted to handle money transactions.
8998 A blog post from
8999 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
9000 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
9001 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
9002 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
9003 some help from my friend to get it all running, and he even handed me
9004 some bitcoins to get started. I even donated a few bitcoins to Simon
9005 for helping me remember BitCoin.&lt;/p&gt;
9006
9007 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
9008 crypto-currency, decentralised and handled using peer-to-peer
9009 networks. It allows anonymous transactions and prohibits central
9010 control over the transactions, making it impossible for governments
9011 and companies alike to block donations and other transactions. The
9012 source is free software, and while the key dependency wxWidgets 2.9
9013 for the graphical user interface is missing in Debian, the command
9014 line client builds just fine. Hopefully Jonas
9015 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
9016 Debian&lt;/a&gt; soon.&lt;/p&gt;
9017
9018 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
9019 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
9020 bitcoins&lt;/a&gt; when selling services and goods, and there are even
9021 currency &quot;stock&quot; markets where the exchange rate is decided. There
9022 are not many users so far, but the concept seems promising. If you
9023 want to get started and lack a friend with any bitcoins to spare,
9024 you can even get
9025 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
9026 bitcoin at the time of writing). Use
9027 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
9028 on the current exchange rates.&lt;/p&gt;
9029
9030 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
9031 machines. If you want to support my activity, please send Bitcoin
9032 donations to the address
9033 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
9034 </description>
9035 </item>
9036
9037 <item>
9038 <title>Why isn&#39;t Debian Edu using VLC?</title>
9039 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
9040 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
9041 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
9042 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
9043 presented, and the winner among the multimedia player were VLC.
9044 Personally, I like VLC, and it is my player of choice when I first try
9045 to play a video file or stream. Only if VLC fail will I drag out
9046 gmplayer to see if it can do better. The reason is mostly the failure
9047 model and trust. When VLC fail, it normally pop up a error message
9048 reporting the problem. When mplayer fail, it normally segfault or
9049 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
9050
9051 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
9052 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9053 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
9054 plugin to play web videos seamlessly, and the VLC browser plugin is
9055 not very good. For example, it lack in-line control buttons, so there
9056 is no way for the user to pause the video. Also, when I
9057 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
9058 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
9059 failed on several video pages where mplayer based plugins worked. If
9060 the browser plugin for VLC was as good as the gecko-mediaplayer
9061 package (which uses mplayer), we would switch.&lt;/P&gt;
9062
9063 &lt;p&gt;While VLC is a good player, its user interface is slightly
9064 annoying. The most annoying feature is its inconsistent use of
9065 keyboard shortcuts. When the player is in full screen mode, its
9066 shortcuts are different from when it is playing the video in a window.
9067 For example, space only work as pause when in full screen mode. I
9068 wish it had consisten shortcuts and that space also would work when in
9069 window mode. Another nice shortcut in gmplayer is [enter] to restart
9070 the current video. It is very nice when playing short videos from the
9071 web and want to restart it when new people arrive to have a look at
9072 what is going on.&lt;/p&gt;
9073 </description>
9074 </item>
9075
9076 <item>
9077 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
9078 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
9079 <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>
9080 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
9081 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
9082 upgrade testing of the
9083 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9084 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
9085 This seem like a very good idea, so I adjusted by test scripts and
9086 can now present the updated result from today:&lt;/p&gt;
9087
9088 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9089
9090 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9091
9092 &lt;blockquote&gt;&lt;p&gt;
9093 apache2.2-bin
9094 aptdaemon
9095 baobab
9096 binfmt-support
9097 browser-plugin-gnash
9098 cheese-common
9099 cli-common
9100 cups-pk-helper
9101 dmz-cursor-theme
9102 empathy
9103 empathy-common
9104 freedesktop-sound-theme
9105 freeglut3
9106 gconf-defaults-service
9107 gdm-themes
9108 gedit-plugins
9109 geoclue
9110 geoclue-hostip
9111 geoclue-localnet
9112 geoclue-manual
9113 geoclue-yahoo
9114 gnash
9115 gnash-common
9116 gnome
9117 gnome-backgrounds
9118 gnome-cards-data
9119 gnome-codec-install
9120 gnome-core
9121 gnome-desktop-environment
9122 gnome-disk-utility
9123 gnome-screenshot
9124 gnome-search-tool
9125 gnome-session-canberra
9126 gnome-system-log
9127 gnome-themes-extras
9128 gnome-themes-more
9129 gnome-user-share
9130 gstreamer0.10-fluendo-mp3
9131 gstreamer0.10-tools
9132 gtk2-engines
9133 gtk2-engines-pixbuf
9134 gtk2-engines-smooth
9135 hamster-applet
9136 libapache2-mod-dnssd
9137 libapr1
9138 libaprutil1
9139 libaprutil1-dbd-sqlite3
9140 libaprutil1-ldap
9141 libart2.0-cil
9142 libboost-date-time1.42.0
9143 libboost-python1.42.0
9144 libboost-thread1.42.0
9145 libchamplain-0.4-0
9146 libchamplain-gtk-0.4-0
9147 libcheese-gtk18
9148 libclutter-gtk-0.10-0
9149 libcryptui0
9150 libdiscid0
9151 libelf1
9152 libepc-1.0-2
9153 libepc-common
9154 libepc-ui-1.0-2
9155 libfreerdp-plugins-standard
9156 libfreerdp0
9157 libgconf2.0-cil
9158 libgdata-common
9159 libgdata7
9160 libgdu-gtk0
9161 libgee2
9162 libgeoclue0
9163 libgexiv2-0
9164 libgif4
9165 libglade2.0-cil
9166 libglib2.0-cil
9167 libgmime2.4-cil
9168 libgnome-vfs2.0-cil
9169 libgnome2.24-cil
9170 libgnomepanel2.24-cil
9171 libgpod-common
9172 libgpod4
9173 libgtk2.0-cil
9174 libgtkglext1
9175 libgtksourceview2.0-common
9176 libmono-addins-gui0.2-cil
9177 libmono-addins0.2-cil
9178 libmono-cairo2.0-cil
9179 libmono-corlib2.0-cil
9180 libmono-i18n-west2.0-cil
9181 libmono-posix2.0-cil
9182 libmono-security2.0-cil
9183 libmono-sharpzip2.84-cil
9184 libmono-system2.0-cil
9185 libmtp8
9186 libmusicbrainz3-6
9187 libndesk-dbus-glib1.0-cil
9188 libndesk-dbus1.0-cil
9189 libopal3.6.8
9190 libpolkit-gtk-1-0
9191 libpt2.6.7
9192 libpython2.6
9193 librpm1
9194 librpmio1
9195 libsdl1.2debian
9196 libsrtp0
9197 libssh-4
9198 libtelepathy-farsight0
9199 libtelepathy-glib0
9200 libtidy-0.99-0
9201 media-player-info
9202 mesa-utils
9203 mono-2.0-gac
9204 mono-gac
9205 mono-runtime
9206 nautilus-sendto
9207 nautilus-sendto-empathy
9208 p7zip-full
9209 pkg-config
9210 python-aptdaemon
9211 python-aptdaemon-gtk
9212 python-axiom
9213 python-beautifulsoup
9214 python-bugbuddy
9215 python-clientform
9216 python-coherence
9217 python-configobj
9218 python-crypto
9219 python-cupshelpers
9220 python-elementtree
9221 python-epsilon
9222 python-evolution
9223 python-feedparser
9224 python-gdata
9225 python-gdbm
9226 python-gst0.10
9227 python-gtkglext1
9228 python-gtksourceview2
9229 python-httplib2
9230 python-louie
9231 python-mako
9232 python-markupsafe
9233 python-mechanize
9234 python-nevow
9235 python-notify
9236 python-opengl
9237 python-openssl
9238 python-pam
9239 python-pkg-resources
9240 python-pyasn1
9241 python-pysqlite2
9242 python-rdflib
9243 python-serial
9244 python-tagpy
9245 python-twisted-bin
9246 python-twisted-conch
9247 python-twisted-core
9248 python-twisted-web
9249 python-utidylib
9250 python-webkit
9251 python-xdg
9252 python-zope.interface
9253 remmina
9254 remmina-plugin-data
9255 remmina-plugin-rdp
9256 remmina-plugin-vnc
9257 rhythmbox-plugin-cdrecorder
9258 rhythmbox-plugins
9259 rpm-common
9260 rpm2cpio
9261 seahorse-plugins
9262 shotwell
9263 software-center
9264 system-config-printer-udev
9265 telepathy-gabble
9266 telepathy-mission-control-5
9267 telepathy-salut
9268 tomboy
9269 totem
9270 totem-coherence
9271 totem-mozilla
9272 totem-plugins
9273 transmission-common
9274 xdg-user-dirs
9275 xdg-user-dirs-gtk
9276 xserver-xephyr
9277 &lt;/p&gt;&lt;/blockquote&gt;
9278
9279 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9280
9281 &lt;blockquote&gt;&lt;p&gt;
9282 cheese
9283 ekiga
9284 eog
9285 epiphany-extensions
9286 evolution-exchange
9287 fast-user-switch-applet
9288 file-roller
9289 gcalctool
9290 gconf-editor
9291 gdm
9292 gedit
9293 gedit-common
9294 gnome-games
9295 gnome-games-data
9296 gnome-nettool
9297 gnome-system-tools
9298 gnome-themes
9299 gnuchess
9300 gucharmap
9301 guile-1.8-libs
9302 libavahi-ui0
9303 libdmx1
9304 libgalago3
9305 libgtk-vnc-1.0-0
9306 libgtksourceview2.0-0
9307 liblircclient0
9308 libsdl1.2debian-alsa
9309 libspeexdsp1
9310 libsvga1
9311 rhythmbox
9312 seahorse
9313 sound-juicer
9314 system-config-printer
9315 totem-common
9316 transmission-gtk
9317 vinagre
9318 vino
9319 &lt;/p&gt;&lt;/blockquote&gt;
9320
9321 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9322
9323 &lt;blockquote&gt;&lt;p&gt;
9324 gstreamer0.10-gnomevfs
9325 &lt;/p&gt;&lt;/blockquote&gt;
9326
9327 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9328
9329 &lt;blockquote&gt;&lt;p&gt;
9330 [nothing]
9331 &lt;/p&gt;&lt;/blockquote&gt;
9332
9333 &lt;p&gt;This is for KDE:&lt;/p&gt;
9334
9335 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9336
9337 &lt;blockquote&gt;&lt;p&gt;
9338 ksmserver
9339 &lt;/p&gt;&lt;/blockquote&gt;
9340
9341 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9342
9343 &lt;blockquote&gt;&lt;p&gt;
9344 kwin
9345 network-manager-kde
9346 &lt;/p&gt;&lt;/blockquote&gt;
9347
9348 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9349
9350 &lt;blockquote&gt;&lt;p&gt;
9351 arts
9352 dolphin
9353 freespacenotifier
9354 google-gadgets-gst
9355 google-gadgets-xul
9356 kappfinder
9357 kcalc
9358 kcharselect
9359 kde-core
9360 kde-plasma-desktop
9361 kde-standard
9362 kde-window-manager
9363 kdeartwork
9364 kdeartwork-emoticons
9365 kdeartwork-style
9366 kdeartwork-theme-icon
9367 kdebase
9368 kdebase-apps
9369 kdebase-workspace
9370 kdebase-workspace-bin
9371 kdebase-workspace-data
9372 kdeeject
9373 kdelibs
9374 kdeplasma-addons
9375 kdeutils
9376 kdewallpapers
9377 kdf
9378 kfloppy
9379 kgpg
9380 khelpcenter4
9381 kinfocenter
9382 konq-plugins-l10n
9383 konqueror-nsplugins
9384 kscreensaver
9385 kscreensaver-xsavers
9386 ktimer
9387 kwrite
9388 libgle3
9389 libkde4-ruby1.8
9390 libkonq5
9391 libkonq5-templates
9392 libnetpbm10
9393 libplasma-ruby
9394 libplasma-ruby1.8
9395 libqt4-ruby1.8
9396 marble-data
9397 marble-plugins
9398 netpbm
9399 nuvola-icon-theme
9400 plasma-dataengines-workspace
9401 plasma-desktop
9402 plasma-desktopthemes-artwork
9403 plasma-runners-addons
9404 plasma-scriptengine-googlegadgets
9405 plasma-scriptengine-python
9406 plasma-scriptengine-qedje
9407 plasma-scriptengine-ruby
9408 plasma-scriptengine-webkit
9409 plasma-scriptengines
9410 plasma-wallpapers-addons
9411 plasma-widget-folderview
9412 plasma-widget-networkmanagement
9413 ruby
9414 sweeper
9415 update-notifier-kde
9416 xscreensaver-data-extra
9417 xscreensaver-gl
9418 xscreensaver-gl-extra
9419 xscreensaver-screensaver-bsod
9420 &lt;/p&gt;&lt;/blockquote&gt;
9421
9422 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9423
9424 &lt;blockquote&gt;&lt;p&gt;
9425 ark
9426 google-gadgets-common
9427 google-gadgets-qt
9428 htdig
9429 kate
9430 kdebase-bin
9431 kdebase-data
9432 kdepasswd
9433 kfind
9434 klipper
9435 konq-plugins
9436 konqueror
9437 ksysguard
9438 ksysguardd
9439 libarchive1
9440 libcln6
9441 libeet1
9442 libeina-svn-06
9443 libggadget-1.0-0b
9444 libggadget-qt-1.0-0b
9445 libgps19
9446 libkdecorations4
9447 libkephal4
9448 libkonq4
9449 libkonqsidebarplugin4a
9450 libkscreensaver5
9451 libksgrd4
9452 libksignalplotter4
9453 libkunitconversion4
9454 libkwineffects1a
9455 libmarblewidget4
9456 libntrack-qt4-1
9457 libntrack0
9458 libplasma-geolocation-interface4
9459 libplasmaclock4a
9460 libplasmagenericshell4
9461 libprocesscore4a
9462 libprocessui4a
9463 libqalculate5
9464 libqedje0a
9465 libqtruby4shared2
9466 libqzion0a
9467 libruby1.8
9468 libscim8c2a
9469 libsmokekdecore4-3
9470 libsmokekdeui4-3
9471 libsmokekfile3
9472 libsmokekhtml3
9473 libsmokekio3
9474 libsmokeknewstuff2-3
9475 libsmokeknewstuff3-3
9476 libsmokekparts3
9477 libsmokektexteditor3
9478 libsmokekutils3
9479 libsmokenepomuk3
9480 libsmokephonon3
9481 libsmokeplasma3
9482 libsmokeqtcore4-3
9483 libsmokeqtdbus4-3
9484 libsmokeqtgui4-3
9485 libsmokeqtnetwork4-3
9486 libsmokeqtopengl4-3
9487 libsmokeqtscript4-3
9488 libsmokeqtsql4-3
9489 libsmokeqtsvg4-3
9490 libsmokeqttest4-3
9491 libsmokeqtuitools4-3
9492 libsmokeqtwebkit4-3
9493 libsmokeqtxml4-3
9494 libsmokesolid3
9495 libsmokesoprano3
9496 libtaskmanager4a
9497 libtidy-0.99-0
9498 libweather-ion4a
9499 libxklavier16
9500 libxxf86misc1
9501 okteta
9502 oxygencursors
9503 plasma-dataengines-addons
9504 plasma-scriptengine-superkaramba
9505 plasma-widget-lancelot
9506 plasma-widgets-addons
9507 plasma-widgets-workspace
9508 polkit-kde-1
9509 ruby1.8
9510 systemsettings
9511 update-notifier-common
9512 &lt;/p&gt;&lt;/blockquote&gt;
9513
9514 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
9515 aptitude a bit more similar, but there are still quite a lott of
9516 differences. I have no idea what packages should be installed after
9517 the upgrade, but hope those that do can have a look.&lt;/p&gt;
9518 </description>
9519 </item>
9520
9521 <item>
9522 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
9523 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
9524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
9525 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
9526 <description>&lt;p&gt;Most of the computers in use by the
9527 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
9528 are virtual machines. And they have been Xen machines running on a
9529 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
9530 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
9531 bit harder that it could have been, because we set up the Xen virtual
9532 machines to get the virtual partitions from LVM, which as far as I
9533 know is not supported by KVM. So to migrate, we had to convert
9534 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
9535
9536 &lt;p&gt;I found
9537 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
9538 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
9539 migration. It uses qemu-img from the qemu package to make the disk
9540 image, parted to partition it, losetup and kpartx to present the disk
9541 image partions as devices, and dd to copy the data. I NFS mounted the
9542 new servers storage area on the old server to do the migration.&lt;/p&gt;
9543
9544 &lt;pre&gt;
9545 #!/bin/sh
9546
9547 # Based on
9548 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9549
9550 set -e
9551 set -x
9552
9553 if [ -z &quot;$1&quot; ] ; then
9554 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
9555 exit 1
9556 else
9557 host=&quot;$1&quot;
9558 fi
9559
9560 if [ ! -e /dev/vg_data/$host-disk ] ; then
9561 echo &quot;error: unable to find LVM volume for $host&quot;
9562 exit 1
9563 fi
9564
9565 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9566 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9567 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
9568 totalsize=$(( ( $disksize + $swapsize ) ))
9569
9570 img=$host.img
9571 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
9572 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9573
9574 parted $img mklabel msdos
9575 parted $img mkpart primary linux-swap 0 $disksize
9576 parted $img mkpart primary ext2 $disksize $totalsize
9577 parted $img set 1 boot on
9578
9579 modprobe dm-mod
9580 losetup /dev/loop0 $img
9581 kpartx -a /dev/loop0
9582
9583 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
9584 fsck.ext3 -f /dev/mapper/loop0p1 || true
9585 mkswap /dev/mapper/loop0p2
9586
9587 kpartx -d /dev/loop0
9588 losetup -d /dev/loop0
9589 &lt;/pre&gt;
9590
9591 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
9592 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
9593
9594 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
9595 the new disk image attached, installed grub-pc and linux-image-686 and
9596 set up grub to boot from the disk image. After this, the KVM machines
9597 seem to work just fine.&lt;/p&gt;
9598 </description>
9599 </item>
9600
9601 <item>
9602 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
9603 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
9604 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
9605 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
9606 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
9607 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9608 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
9609 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
9610
9611 &lt;p&gt;I still do not know what a correct migration should look like, so I
9612 report any differences between apt and aptitude and hope someone else
9613 can see if anything should be changed.&lt;/p&gt;
9614
9615 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9616
9617 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9618
9619 &lt;blockquote&gt;&lt;p&gt;
9620 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9621 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
9622 dmz-cursor-theme empathy empathy-common finger
9623 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9624 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9625 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9626 gnome-cards-data gnome-codec-install gnome-core
9627 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9628 gnome-search-tool gnome-session-canberra gnome-spell
9629 gnome-system-log gnome-themes-extras gnome-themes-more
9630 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9631 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9632 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9633 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9634 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
9635 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
9636 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
9637 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
9638 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
9639 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9640 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
9641 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9642 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9643 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9644 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9645 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9646 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9647 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9648 libmono-security2.0-cil libmono-sharpzip2.84-cil
9649 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
9650 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
9651 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
9652 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
9653 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
9654 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
9655 libxalan2-java libxerces2-java media-player-info mesa-utils
9656 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
9657 nautilus-sendto-empathy openoffice.org-writer2latex
9658 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
9659 python-aptdaemon python-aptdaemon-gtk python-axiom
9660 python-beautifulsoup python-bugbuddy python-clientform
9661 python-coherence python-configobj python-crypto python-cupshelpers
9662 python-cupsutils python-eggtrayicon python-elementtree
9663 python-epsilon python-evolution python-feedparser python-gdata
9664 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9665 python-gtksourceview2 python-httplib2 python-louie python-mako
9666 python-markupsafe python-mechanize python-nevow python-notify
9667 python-opengl python-openssl python-pam python-pkg-resources
9668 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9669 python-tagpy python-twisted-bin python-twisted-conch
9670 python-twisted-core python-twisted-web python-utidylib python-webkit
9671 python-xdg python-zope.interface remmina remmina-plugin-data
9672 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9673 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9674 software-center svgalibg1 system-config-printer-udev
9675 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
9676 totem totem-coherence totem-mozilla totem-plugins
9677 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9678 zip
9679 &lt;/p&gt;&lt;/blockquote&gt;
9680
9681 Installed using apt-get, removed with aptitude
9682
9683 &lt;blockquote&gt;&lt;p&gt;
9684 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9685 epiphany-extensions epiphany-gecko evolution-exchange
9686 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9687 gedit-common gnome-app-install gnome-games gnome-games-data
9688 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9689 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9690 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9691 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
9692 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
9693 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
9694 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
9695 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9696 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9697 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9698 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
9699 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
9700 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9701 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9702 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9703 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9704 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
9705 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
9706 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
9707 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
9708 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
9709 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9710 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9711 sound-juicer swfdec-gnome system-config-printer totem-common
9712 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9713 &lt;/p&gt;&lt;/blockquote&gt;
9714
9715 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9716
9717 &lt;blockquote&gt;&lt;p&gt;
9718 gstreamer0.10-gnomevfs
9719 &lt;/p&gt;&lt;/blockquote&gt;
9720
9721 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9722
9723 &lt;blockquote&gt;&lt;p&gt;
9724 [nothing]
9725 &lt;/p&gt;&lt;/blockquote&gt;
9726
9727 &lt;p&gt;This is for KDE:&lt;/p&gt;
9728
9729 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9730
9731 &lt;blockquote&gt;&lt;p&gt;
9732 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
9733 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9734 ghostscript-x git gnome-audio gnugo granatier gs-common
9735 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9736 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9737 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9738 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9739 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9740 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9741 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9742 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9743 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9744 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9745 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9746 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
9747 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9748 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9749 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9750 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9751 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9752 libkrossui4 libmailtools-perl libmime-tools-perl
9753 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9754 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9755 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9756 lirc luatex marble networkstatus noatun-plugins
9757 openoffice.org-writer2latex palapeli palapeli-data parley
9758 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9759 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9760 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9761 ttf-sazanami-gothic
9762 &lt;/p&gt;&lt;/blockquote&gt;
9763
9764 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9765
9766 &lt;blockquote&gt;&lt;p&gt;
9767 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9768 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9769 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9770 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9771 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9772 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9773 kitchensync kiten kjumpingcube klatin klettres klickety klines
9774 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9775 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9776 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9777 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9778 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9779 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9780 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9781 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9782 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9783 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
9784 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
9785 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9786 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
9787 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
9788 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9789 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9790 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9791 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9792 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9793 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9794 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
9795 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
9796 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9797 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9798 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9799 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9800 &lt;/p&gt;&lt;/blockquote&gt;
9801
9802 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9803
9804 &lt;blockquote&gt;&lt;p&gt;
9805 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9806 kdeartwork kdebase kdebase-apps kdebase-workspace
9807 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9808 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9809 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9810 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9811 xscreensaver-screensaver-bsod
9812 &lt;/p&gt;&lt;/blockquote&gt;
9813
9814 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9815
9816 &lt;blockquote&gt;&lt;p&gt;
9817 kdebase-bin konq-plugins konqueror
9818 &lt;/p&gt;&lt;/blockquote&gt;
9819 </description>
9820 </item>
9821
9822 <item>
9823 <title>Gnash buildbot slave and Debian kfreebsd</title>
9824 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
9825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
9826 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
9827 <description>&lt;p&gt;Answering
9828 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
9829 call from the Gnash project&lt;/a&gt; for
9830 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
9831 current source, I have set up a virtual KVM machine on the Debian
9832 Edu/Skolelinux virtualization host to test the git source on
9833 Debian/Squeeze. I hope this can help the developers in getting new
9834 releases out more often.&lt;/p&gt;
9835
9836 &lt;p&gt;As the developers want less main-stream build platforms tested to,
9837 I have considered setting up a &lt;a
9838 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
9839 machine as well. I have also considered using the kfreebsd
9840 architecture in Debian as a file server in NUUG to get access to the 5
9841 TB zfs volume we currently use to store DV video. Because of this, I
9842 finally got around to do a test installation of Debian/Squeeze with
9843 kfreebsd. Installation went fairly smooth, thought I noticed some
9844 visual glitches in the cdebconf dialogs (black cursor left on the
9845 screen at random locations). Have not gotten very far with the
9846 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9847 fatal problem. Have to spend some more time on it to see if it is
9848 useful as a file server for NUUG. Will try to find time to set up a
9849 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
9850 </description>
9851 </item>
9852
9853 <item>
9854 <title>Debian in 3D</title>
9855 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
9856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
9857 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
9858 <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;
9859
9860 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
9861 3D linked in from
9862 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
9863 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
9864 </description>
9865 </item>
9866
9867 <item>
9868 <title>Software updates 2010-10-24</title>
9869 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
9870 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
9871 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
9872 <description>&lt;p&gt;Some updates.&lt;/p&gt;
9873
9874 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
9875 raise money for the project is going well. The lower limit of 10
9876 signers was reached in 24 hours, and so far 13 people have signed it.
9877 More signers and more funding is most welcome, and I am really curious
9878 how far we can get before the time limit of December 24 is reached.
9879 :)&lt;/p&gt;
9880
9881 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9882 about what appear to be a great code coverage tool capable of
9883 generating code coverage stats without any changes to the source code.
9884 It is called
9885 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9886 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9887 It is missing in Debian, but the git source built just fine in Squeeze
9888 after I installed libelf-dev, libdwarf-dev, pkg-config and
9889 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9890 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9891
9892 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9893 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9894 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9895 alpha test release of the Squeeze based Debian Edu /
9896 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9897 release. Give it a try if you need a complete linux solution for your
9898 school, including central infrastructure server, workstations, thin
9899 client servers and diskless workstations. A nice touch added
9900 yesterday is RDP support on the thin client servers, for windows
9901 clients to get a Linux desktop on request.&lt;/p&gt;
9902 </description>
9903 </item>
9904
9905 <item>
9906 <title>Some notes on Flash in Debian and Debian Edu</title>
9907 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9908 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9909 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9910 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9911 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9912 second most popular used package that is missing in Debian. The sixth
9913 most popular is flashplayer-mozilla. This is a clear indication that
9914 working flash is important for Debian users. Around 10 percent of the
9915 users submitting data to popcon.debian.org have this package
9916 installed.&lt;/p&gt;
9917
9918 &lt;p&gt;In the report written by Lars Risan in August 2008
9919&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
9920 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9921 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9922 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9923 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9924 web sites require Flash to work, and lacking working Flash support in
9925 the web browser and the problems with installing it was perceived as a
9926 good reason to stay with Windows.&lt;/p&gt;
9927
9928 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9929 said to be the retarded cousin that did not really understand
9930 everything you told him but could work fairly well. This was a
9931 comment regarding the problems Linux have with proprietary formats and
9932 non-standard web pages, and is sad because it exposes a fairly common
9933 understanding of whose fault it is if web pages that only work in for
9934 example Internet Explorer 6 fail to work on Firefox, and funny because
9935 it explain very well how annoying it is for users when Linux
9936 distributions do not work with the documents they receive or the web
9937 pages they want to visit.&lt;/p&gt;
9938
9939 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9940 and Debian Edu to have a well working Flash implementation in the
9941 distribution, to get at least popular sites as Youtube and Google
9942 Video to working out of the box. For Squeeze, Debian have the chance
9943 to include the latest version of Gnash that will make this happen, as
9944 the new release 0.8.8 was published a few weeks ago and is resting in
9945 unstable. The new version work with more sites that version 0.8.7.
9946 The Gnash maintainers have asked for a freeze exception, but the
9947 release team have not had time to reply to it yet. I hope they agree
9948 with me that Flash is important for the Debian desktop users, and thus
9949 accept the new package into Squeeze.&lt;/p&gt;
9950 </description>
9951 </item>
9952
9953 <item>
9954 <title>Circular package dependencies harms apt recovery</title>
9955 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9957 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9958 <description>&lt;p&gt;I discovered this while doing
9959 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9960 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9961 in Debian still got circular dependencies, and it is often claimed
9962 that apt and aptitude should be able to handle this just fine, but
9963 some times these dependency loops causes apt to fail.&lt;/p&gt;
9964
9965 &lt;p&gt;An example is from todays
9966 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9967 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9968 causes perl-modules to fail to upgrade. The cause is simple. If a
9969 package fail to unpack, then only part of packages with the circular
9970 dependency might end up being unpacked when unpacking aborts, and the
9971 ones already unpacked will fail to configure in the recovery phase
9972 because its dependencies are unavailable.&lt;/p&gt;
9973
9974 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9975
9976 &lt;blockquote&gt;&lt;pre&gt;
9977 dpkg: dependency problems prevent configuration of perl-modules:
9978 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9979 Version of perl on system is 5.10.0-19lenny2.
9980 dpkg: error processing perl-modules (--configure):
9981 dependency problems - leaving unconfigured
9982 &lt;/pre&gt;&lt;/blockquote&gt;
9983
9984 &lt;p&gt;The perl/perl-modules circular dependency is already
9985 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9986 hopefully be solved as soon as possible, but it is not the only one,
9987 and each one of these loops in the dependency tree can cause similar
9988 failures. Of course, they only occur when there are bugs in other
9989 packages causing the unpacking to fail, but it is rather nasty when
9990 the failure of one package causes the problem to become worse because
9991 of dependency loops.&lt;/p&gt;
9992
9993 &lt;p&gt;Thanks to
9994 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9995 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9996 dependencies
9997 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9998 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9999
10000 &lt;p&gt;Todays testing also exposed a bug in
10001 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
10002 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
10003 apt-get and aptitude, the latter possibly caused by some circular
10004 dependency. Reported both to BTS to try to get someone to look at
10005 it.&lt;/p&gt;
10006 </description>
10007 </item>
10008
10009 <item>
10010 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
10011 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
10012 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
10013 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
10014 <description>&lt;p&gt;This is a
10015 &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;
10016 on my
10017 &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
10018 work&lt;/a&gt; on
10019 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
10020 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
10021
10022 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
10023 LDAP objects, I have had a look at how the packages pdns-backend-ldap
10024 and dhcp3-server-ldap in Debian use the LDAP server. The two
10025 implementations are quite different in how they use LDAP.&lt;/p&gt;
10026
10027 To get this information, I started slapd with debugging enabled and
10028 dumped the debug output to a file to get the LDAP searches performed
10029 on a Debian Edu main-server. Here is a summary.
10030
10031 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
10032
10033 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
10034 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
10035 the web.
10036
10037 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
10038 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
10039 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
10040 reverse entries are in two different subtrees in LDAP with a structure
10041 based on the DNS names, as in tjener.intern and
10042 2.2.0.10.in-addr.arpa.&lt;/p&gt;
10043
10044 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
10045 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
10046 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
10047 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
10048 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
10049 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
10050 forward entries, it is looking for attributes named dnsttl, arecord,
10051 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10052 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10053 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10054 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10055 spfrecord and modifytimestamp. For reverse entries it is looking for
10056 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10057 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10058 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10059 ldapsearch commands could look like this:&lt;/p&gt;
10060
10061 &lt;blockquote&gt;&lt;pre&gt;
10062 ldapsearch -h ldap \
10063 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10064 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10065 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10066 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10067 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10068 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10069
10070 ldapsearch -h ldap \
10071 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10072 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
10073 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10074 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10075 srvrecord naptrrecord modifytimestamp
10076 &lt;/pre&gt;&lt;/blockquote&gt;
10077
10078 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
10079 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10080 example LDAP objects used there. In addition to these objects, the
10081 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10082 also exist.&lt;/p&gt;
10083
10084 &lt;blockquote&gt;&lt;pre&gt;
10085 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10086 objectclass: top
10087 objectclass: dnsdomain
10088 objectclass: domainrelatedobject
10089 dc: tjener
10090 arecord: 10.0.2.2
10091 associateddomain: tjener.intern
10092
10093 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10094 objectclass: top
10095 objectclass: dnsdomain2
10096 objectclass: domainrelatedobject
10097 dc: 2
10098 ptrrecord: tjener.intern
10099 associateddomain: 2.2.0.10.in-addr.arpa
10100 &lt;/pre&gt;&lt;/blockquote&gt;
10101
10102 &lt;p&gt;In strict mode, the server behaves differently. When looking for
10103 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
10104 same base as in the tree mode for a object with filter
10105 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
10106 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10107 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10108 naptrrecord and modifytimestamp. For reverse entires it also do a
10109 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
10110 and the requested attributes are associateddomain, dnsttl and
10111 modifytimestamp. In short, in strict mode the objects with ptrrecord
10112 go away, and the arecord attribute in the forward object is used
10113 instead.&lt;/p&gt;
10114
10115 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
10116 like this:&lt;/p&gt;
10117
10118 &lt;blockquote&gt;&lt;pre&gt;
10119 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10120 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10121 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10122 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10123 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10124 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10125
10126 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10127 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
10128 &lt;/pre&gt;&lt;/blockquote&gt;
10129
10130 &lt;p&gt;In addition to the forward and reverse searches , there is also a
10131 search for SOA records, which behave similar to the forward and
10132 reverse lookups.&lt;/p&gt;
10133
10134 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
10135 specify any objectclass names, and instead look for the attributes it
10136 need to generate a DNS reply. This make it able to work with any
10137 objectclass that provide the needed attributes.&lt;/p&gt;
10138
10139 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
10140 dnsdomain2 schemas. The latter is used for reverse entries like
10141 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
10142
10143 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
10144 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
10145 attributes) and domainrelatedobject (for associatedDomain). The use
10146 of structural object classes make it impossible to combine these
10147 classes with the object classes used by DHCP.&lt;/p&gt;
10148
10149 &lt;p&gt;There are other schemas that could be used too, for example the
10150 dnszone structural object class used by Gosa and bind-sdb for the DNS
10151 attributes combined with the domainrelatedobject object class, but in
10152 this case some unused attributes would have to be included as well
10153 (zonename and relativedomainname).&lt;/p&gt;
10154
10155 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
10156 mode and not use any of the existing objectclasses (dnsdomain,
10157 dnsdomain2 and dnszone) when one want to combine the DNS information
10158 with DHCP information, and instead create a auxiliary object class
10159 defined something like this (using the attributes defined for
10160 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
10161
10162 &lt;blockquote&gt;&lt;pre&gt;
10163 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
10164 SUP top
10165 AUXILIARY
10166 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
10167 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
10168 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
10169 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
10170 A6Record $ DNAMERecord
10171 ))
10172 &lt;/pre&gt;&lt;/blockquote&gt;
10173
10174 &lt;p&gt;This will allow any object to become a DNS entry when combined with
10175 the domainrelatedobject object class, and allow any entity to include
10176 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
10177 developers asking for their view on this schema and if they are
10178 interested in providing such schema with PowerDNS, and I hope my
10179 message will be accepted into their mailing list soon.&lt;/p&gt;
10180
10181 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
10182
10183 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
10184 the object attributes, and then uses the attributes it want. This
10185 make it harder to figure out exactly what attributes are used, but
10186 thanks to the working example in Debian Edu I can at least get an idea
10187 what is needed without having to read the source code.&lt;/p&gt;
10188
10189 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
10190 search filter to use to locate the correct dhcpServer entity is
10191 stored. These are the relevant entries from
10192 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
10193
10194 &lt;blockquote&gt;&lt;pre&gt;
10195 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
10196 ldap-dhcp-server-cn &quot;dhcp&quot;;
10197 &lt;/pre&gt;&lt;/blockquote&gt;
10198
10199 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
10200 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
10201 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
10202 search result is this entry:&lt;/p&gt;
10203
10204 &lt;blockquote&gt;&lt;pre&gt;
10205 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10206 cn: dhcp
10207 objectClass: top
10208 objectClass: dhcpServer
10209 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10210 &lt;/pre&gt;&lt;/blockquote&gt;
10211
10212 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
10213 subtree with DHCP configuration. The DHCP configuration subtree base
10214 is located using a base scope search with base &quot;cn=DHCP
10215 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
10216 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
10217 The search result is this entry:&lt;/p&gt;
10218
10219 &lt;blockquote&gt;&lt;pre&gt;
10220 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10221 cn: DHCP Config
10222 objectClass: top
10223 objectClass: dhcpService
10224 objectClass: dhcpOptions
10225 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
10226 dhcpStatements: ddns-update-style none
10227 dhcpStatements: authoritative
10228 dhcpOption: smtp-server code 69 = array of ip-address
10229 dhcpOption: www-server code 72 = array of ip-address
10230 dhcpOption: wpad-url code 252 = text
10231 &lt;/pre&gt;&lt;/blockquote&gt;
10232
10233 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
10234 all the DHCP configuration is loaded, it is ready to receive requests.
10235 The subtree in Debian Edu contain objects with object classes
10236 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
10237 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
10238 and information about netmasks, dynamic range etc. Leaving out the
10239 details here because it is not relevant for the focus of my
10240 investigation, which is to see if it is possible to merge dns and dhcp
10241 related computer objects.&lt;/p&gt;
10242
10243 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
10244 of the client (00:00:00:00:00:00 in this example), using a subtree
10245 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
10246 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
10247 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
10248 like:&lt;/p&gt;
10249
10250 &lt;blockquote&gt;&lt;pre&gt;
10251 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10252 cn: hostname
10253 objectClass: top
10254 objectClass: dhcpHost
10255 dhcpHWAddress: ethernet 00:00:00:00:00:00
10256 dhcpStatements: fixed-address hostname
10257 &lt;/pre&gt;&lt;/blockquote&gt;
10258
10259 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
10260 The object classes need to have fixed names, and the configuration
10261 need to be stored in a fairly specific LDAP structure. On the
10262 positive side, the invidiual dhcpHost entires can be anywhere without
10263 the DN pointed to by the dhcpServer entries. The latter should make
10264 it possible to group all host entries in a subtree next to the
10265 configuration entries, and this subtree can also be shared with the
10266 DNS server if the schema proposed above is combined with the dhcpHost
10267 structural object class.
10268
10269 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
10270
10271 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
10272 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
10273 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
10274 allowing DNS objects to be stored anywhere under the base cn specified
10275 in the configuration.&lt;/p&gt;
10276
10277 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
10278 regarding which LDAP schemas to use and which LDAP structure to use.
10279 I guess one could implement ones own schema, as long as the
10280 objectclasses and attributes have the names used, but this do not
10281 really help when the DHCP subtree need to have a fairly fixed
10282 structure.&lt;/p&gt;
10283
10284 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
10285 this might work for Debian Edu:&lt;/p&gt;
10286
10287 &lt;blockquote&gt;&lt;pre&gt;
10288 ou=services
10289 cn=machine-info (dhcpService) - dhcpServiceDN points here
10290 cn=dhcp (dhcpServer)
10291 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10292 cn=10.0.2.0 (dhcpSubnet)
10293 cn=group1 (dhcpGroup/dhcpOptions)
10294 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10295 cn=192.168.0.0 (dhcpSubnet)
10296 cn=group1 (dhcpGroup/dhcpOptions)
10297 ou=machines - PowerDNS base points here
10298 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10299 &lt;/pre&gt;&lt;/blockquote&gt;
10300
10301 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
10302 entries to be in the dhcpGroup subtrees, the entries can be stored
10303 there instead of a common machines subtree, and the PowerDNS base
10304 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
10305
10306 &lt;p&gt;The combined object under the machines subtree would look something
10307 like this:&lt;/p&gt;
10308
10309 &lt;blockquote&gt;&lt;pre&gt;
10310 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10311 dc: hostname
10312 objectClass: top
10313 objectClass: dhcpHost
10314 objectclass: domainrelatedobject
10315 objectclass: dnsDomainAux
10316 associateddomain: hostname.intern
10317 arecord: 10.11.12.13
10318 dhcpHWAddress: ethernet 00:00:00:00:00:00
10319 dhcpStatements: fixed-address hostname.intern
10320 &lt;/pre&gt;&lt;/blockquote&gt;
10321
10322 &lt;/p&gt;One could even add the LTSP configuration associated with a given
10323 machine, as long as the required attributes are available in a
10324 auxiliary object class.&lt;/p&gt;
10325 </description>
10326 </item>
10327
10328 <item>
10329 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
10330 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
10331 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
10332 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
10333 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
10334 DHCP services in Debian Edu to use the same LDAP objects for a given
10335 computer, to avoid the possibility of having a inconsistent state for
10336 a computer in LDAP (as in DHCP but no DNS entry or the other way
10337 around) and make it easier to add computers to LDAP.&lt;/p&gt;
10338
10339 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
10340 information finally found a solution that seem to work.&lt;/p&gt;
10341
10342 &lt;p&gt;The old setup required three LDAP objects for a given computer.
10343 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10344 we switch powerdns to use its strict LDAP method (ldap-method=strict
10345 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10346 merged into one while making it impossible to transfer the reverse map
10347 to a slave DNS server.&lt;/p&gt;
10348
10349 &lt;p&gt;If we also replace the object class used to get the DNS related
10350 attributes to one allowing these attributes to be combined with the
10351 dhcphost object class, we can merge the DNS and DHCP entries into one.
10352 I&#39;ve written such object class in the dnsdomainaux.schema file (need
10353 proper OIDs, but that is a minor issue), and tested the setup. It
10354 seem to work.&lt;/p&gt;
10355
10356 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
10357 for both DNS and DHCP, and even the LTSP configuration I suggested in
10358 an earlier email. The combined LDAP object will look something like
10359 this:&lt;/p&gt;
10360
10361 &lt;blockquote&gt;&lt;pre&gt;
10362 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10363 cn: hostname
10364 objectClass: dhcphost
10365 objectclass: domainrelatedobject
10366 objectclass: dnsdomainaux
10367 associateddomain: hostname.intern
10368 arecord: 10.11.12.13
10369 dhcphwaddress: ethernet 00:00:00:00:00:00
10370 dhcpstatements: fixed-address hostname
10371 ldapconfigsound: Y
10372 &lt;/pre&gt;&lt;/blockquote&gt;
10373
10374 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
10375 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10376 before asking DNS to resolve the fixed-adddress. LTSP will use
10377 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
10378
10379 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
10380 dhcphost in a different location, to allow us to put the objects
10381 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
10382 that. If I can&#39;t figure out a way to do that, we can still get rid of
10383 the hosts subtree and move all its content into the DHCP Config tree
10384 (which probably should be renamed to be more related to the new
10385 content. I suspect cn=dnsdhcp,ou=services or something like that
10386 might be a good place to put it.&lt;/p&gt;
10387
10388 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10389 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10390 </description>
10391 </item>
10392
10393 <item>
10394 <title>Idea for storing LTSP configuration in LDAP</title>
10395 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
10396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
10397 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
10398 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
10399 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10400 clients, and that this can be used to fetch configuration from LDAP if
10401 Debian Edu choose to store configuration there.&lt;/p&gt;
10402
10403 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
10404 to get configuration from LDAP. The idea is to look up the MAC
10405 address of the client in LDAP, and look for attributes on the form
10406 ltspconfigsetting=value, and use this to export SETTING=value to the
10407 LTSP clients.&lt;/p&gt;
10408
10409 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
10410 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
10411 allowing us to store all information about a computer in one place.&lt;/p&gt;
10412
10413 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
10414 this approach. A real LDAP schema for the ltspClientAux objectclass
10415 need to be written. Comments, suggestions, etc?&lt;/p&gt;
10416
10417 &lt;blockquote&gt;&lt;pre&gt;
10418 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10419 #
10420 # Fetch LTSP client settings from LDAP based on MAC address
10421 #
10422 # Uses ethernet address as stored in the dhcpHost objectclass using
10423 # the dhcpHWAddress attribute or ethernet address stored in the
10424 # ieee802Device objectclass with the macAddress attribute.
10425 #
10426 # This module is written to be schema agnostic, and only depend on the
10427 # existence of attribute names.
10428 #
10429 # The LTSP configuration variables are saved directly using a
10430 # ltspConfig prefix and uppercasing the rest of the attribute name.
10431 # To set the SERVER variable, set the ltspConfigServer attribute.
10432 #
10433 # Some LDAP schema should be created with all the relevant
10434 # configuration settings. Something like this should work:
10435 #
10436 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
10437 # SUP top
10438 # AUXILIARY
10439 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10440
10441 LDAPSERVER=$(debian-edu-ldapserver)
10442 if [ &quot;$LDAPSERVER&quot; ] ; then
10443 LDAPBASE=$(debian-edu-ldapserver -b)
10444 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
10445 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
10446 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
10447 grep &#39;^ltspConfig&#39; | while read attr value ; do
10448 # Remove prefix and convert to upper case
10449 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
10450 # bass value on to clients
10451 eval &quot;$attr=$value; export $attr&quot;
10452 done
10453 done
10454 fi
10455 &lt;/pre&gt;&lt;/blockquote&gt;
10456
10457 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
10458 the while block might end up in a subshell causing the variables set
10459 there to not show up in ltsp-config, but if that is the case I am sure
10460 the code can be restructured to make sure the variables are passed on.
10461 I expect that can be solved with some testing. :)&lt;/p&gt;
10462
10463 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10464 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10465
10466 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
10467 configuration in LDAP that was created around year 2000 by
10468 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
10469 Xperience, Inc., 2000&lt;/a&gt;. I found its
10470 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
10471 personal home page over at redhat.com.&lt;/p&gt;
10472 </description>
10473 </item>
10474
10475 <item>
10476 <title>jXplorer, a very nice LDAP GUI</title>
10477 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
10478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
10479 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
10480 <description>&lt;p&gt;Since
10481 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
10482 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
10483 LDAP GUI that is even better than luma. The java application
10484 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
10485 moving LDAP objects and subtrees using drag-and-drop, and can
10486 authenticate using Kerberos. I have only tested the Kerberos
10487 authentication, but do not have a LDAP setup allowing me to rewrite
10488 LDAP with my test user yet. It is
10489 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
10490 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
10491 have with it is how it handle errors. If something go wrong, its
10492 non-intuitive behaviour require me to go through some query work list
10493 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
10494 </description>
10495 </item>
10496
10497 <item>
10498 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
10499 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
10500 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
10501 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
10502 <description>&lt;p&gt;Here is a short update on my &lt;a
10503 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
10504 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
10505 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
10506 not reporting the status for KDE, because the upgrade crashes when
10507 aptitude try because of missing conflicts
10508 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
10509 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
10510
10511 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
10512 complete list of the installed packages. Based on this I see these
10513 differences when I did a test run today. As usual, I do not really
10514 know what the correct set of packages would be, but thought it best to
10515 publish the difference.&lt;/p&gt;
10516
10517 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10518
10519 &lt;blockquote&gt;&lt;p&gt;
10520 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
10521 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
10522 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10523 libgtksourceview-common libpt-1.10.10-plugins-alsa
10524 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10525 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10526 python-4suite-xml python-eggtrayicon python-gtkhtml2
10527 python-gtkmozembed svgalibg1 xserver-xephyr zip
10528 &lt;/p&gt;&lt;/blockquote&gt;
10529
10530 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10531
10532 &lt;blockquote&gt;&lt;p&gt;
10533 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10534 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10535 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
10536 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
10537 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
10538 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
10539 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10540 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10541 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10542 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
10543 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
10544 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
10545 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10546 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
10547 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10548 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
10549 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
10550 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10551 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10552 mysql-common swfdec-gnome totem-gstreamer wodim
10553 &lt;/p&gt;&lt;/blockquote&gt;
10554
10555 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10556
10557 &lt;blockquote&gt;&lt;p&gt;
10558 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10559 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10560 xserver-xorg-input-all xserver-xorg-input-evdev
10561 xserver-xorg-input-kbd xserver-xorg-input-mouse
10562 xserver-xorg-input-synaptics xserver-xorg-video-all
10563 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10564 xserver-xorg-video-chips xserver-xorg-video-cirrus
10565 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10566 xserver-xorg-video-glint xserver-xorg-video-i128
10567 xserver-xorg-video-i740 xserver-xorg-video-mach64
10568 xserver-xorg-video-mga xserver-xorg-video-neomagic
10569 xserver-xorg-video-nouveau xserver-xorg-video-nv
10570 xserver-xorg-video-r128 xserver-xorg-video-radeon
10571 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10572 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10573 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10574 xserver-xorg-video-sis xserver-xorg-video-sisusb
10575 xserver-xorg-video-tdfx xserver-xorg-video-tga
10576 xserver-xorg-video-trident xserver-xorg-video-tseng
10577 xserver-xorg-video-vesa xserver-xorg-video-vmware
10578 xserver-xorg-video-voodoo
10579 &lt;/p&gt;&lt;/blockquote&gt;
10580
10581 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10582
10583 &lt;blockquote&gt;&lt;p&gt;
10584 deskbar-applet xserver-xorg xserver-xorg-core
10585 xserver-xorg-input-wacom xserver-xorg-video-intel
10586 xserver-xorg-video-openchrome
10587 &lt;/p&gt;&lt;/blockquote&gt;
10588
10589 &lt;p&gt;I was told on IRC that the xorg-xserver package was
10590 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
10591 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
10592 No idea when it hits Squeeze, but when it does I hope it will reduce
10593 the difference somewhat.
10594 </description>
10595 </item>
10596
10597 <item>
10598 <title>LUMA, a very nice LDAP GUI</title>
10599 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
10600 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
10601 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
10602 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
10603 directory in Debian Edu, and in the process I started to miss a GUI
10604 tool to browse the LDAP tree. The only one I was able to find in
10605 Debian/Squeeze and Lenny is
10606 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
10607 be a great tool to get a overview of the current LDAP directory
10608 populated by default in Skolelinux. Thanks to it, I have been able to
10609 find empty and obsolete subtrees, misplaced objects and duplicate
10610 objects. It will be installed by default in Debian/Squeeze. If you
10611 are working with LDAP, give it a go. :)&lt;/p&gt;
10612
10613 &lt;p&gt;I did notice one problem with it I have not had time to report to
10614 the BTS yet. There is no .desktop file in the package, so the tool do
10615 not show up in the Gnome and KDE menus, but only deep down in in the
10616 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10617 released.&lt;/p&gt;
10618
10619 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
10620 like to move objects and remove subtrees directly in the GUI, but have
10621 not found a way to do that with LUMA yet. So in the mean time, I use
10622 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
10623
10624 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
10625 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10626
10627 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
10628 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
10629 useful GUI alternative. It seem like a good tool, but is unmaintained
10630 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10631 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
10632 </description>
10633 </item>
10634
10635 <item>
10636 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
10637 <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>
10638 <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>
10639 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
10640 <description>&lt;p&gt;A while back, I
10641 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
10642 about the fact&lt;/a&gt; that it is not possible with the provided schemas
10643 for storing DNS and DHCP information in LDAP to combine the two sets
10644 of information into one LDAP object representing a computer.&lt;/p&gt;
10645
10646 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
10647 the dhcpHost object class auxiliary, to allow it to be combined with
10648 the dNSDomain object class, and thus forming one object for one
10649 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
10650
10651 &lt;p&gt;If I understand this correctly, it is not safe to do this change
10652 without also changing the assigned number for the object class, and I
10653 do not know enough about LDAP schema design to do that properly for
10654 Debian Edu.&lt;/p&gt;
10655
10656 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
10657 the
10658 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
10659 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
10660 available today from IETF.&lt;/p&gt;
10661
10662 &lt;pre&gt;
10663 --- dhcp.schema (revision 65192)
10664 +++ dhcp.schema (working copy)
10665 @@ -376,7 +376,7 @@
10666 objectclass ( 2.16.840.1.113719.1.203.6.6
10667 NAME &#39;dhcpHost&#39;
10668 DESC &#39;This represents information about a particular client&#39;
10669 - SUP top
10670 + SUP top AUXILIARY
10671 MUST cn
10672 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10673 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
10674 &lt;/pre&gt;
10675
10676 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
10677 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10678 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
10679
10680 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
10681 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
10682 </description>
10683 </item>
10684
10685 <item>
10686 <title>Calling tasksel like the installer, while still getting useful output</title>
10687 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
10688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
10689 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
10690 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
10691 installs packages during the normal debian-installer run. Until now,
10692 I have ended up letting tasksel do the work, with the annoying problem
10693 of not getting any feedback at all when something fails (like a
10694 conffile question from dpkg or a download that fails), using code like
10695 this:
10696
10697 &lt;blockquote&gt;&lt;pre&gt;
10698 export DEBIAN_FRONTEND=noninteractive
10699 tasksel --new-install
10700 &lt;/pre&gt;&lt;/blockquote&gt;
10701
10702 This would invoke tasksel, let its automatic task selection pick the
10703 tasks to install, and continue to install the requested tasks without
10704 any output what so ever.
10705
10706 Recently I revisited this problem while working on the automatic
10707 package upgrade testing, because tasksel would some times hang without
10708 any useful feedback, and I want to see what is going on when it
10709 happen. Then it occured to me, I can parse the output from tasksel
10710 when asked to run in test mode, and use that aptitude command line
10711 printed by tasksel then to simulate the tasksel run. I ended up using
10712 code like this:
10713
10714 &lt;blockquote&gt;&lt;pre&gt;
10715 export DEBIAN_FRONTEND=noninteractive
10716 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
10717 $cmd
10718 &lt;/pre&gt;&lt;/blockquote&gt;
10719
10720 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
10721 --without-recommends -o APT::Install-Recommends=no -y install
10722 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10723 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
10724 laptop task and all packages with priority standard , required and
10725 important, just like tasksel would have done it during
10726 installation.&lt;/p&gt;
10727
10728 &lt;p&gt;A better approach is probably to extend tasksel to be able to
10729 install packages without using debconf-apt-progress, for use cases
10730 like this.&lt;/p&gt;
10731 </description>
10732 </item>
10733
10734 <item>
10735 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
10736 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
10737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
10738 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
10739 <description>&lt;p&gt;My
10740 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
10741 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
10742 finally made the upgrade logs available from
10743 &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;.
10744 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10745 apt and aptitude, and found their differences interesting. This time
10746 I will only focus on their removal plans.&lt;/p&gt;
10747
10748 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
10749 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
10750 surprising part is that it want to remove xorg and all
10751 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10752 sure why. When asking aptitude to do the same, it want to remove 129
10753 packages, but most of them are library packages I suspect are no
10754 longer needed. Both of them want to remove bluetooth packages, which
10755 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
10756
10757 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
10758 which seem like a bad idea and xorg the same way as with Gnome. Asking
10759 aptitude for the same, it wants to remove 192 packages, none which are
10760 too surprising.&lt;/p&gt;
10761
10762 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
10763 and avoided, and perhaps others as well. Here are the complete list
10764 of planned removals. The complete logs is available from the URL
10765 above. Note if you want to repeat these tests, that the upgrade test
10766 for kde+apt-get hung in the tasksel setup because of dpkg asking
10767 conffile questions. No idea why. I worked around it by using
10768 &#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
10769 continue.&lt;/p&gt;
10770
10771 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
10772 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
10773 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10774 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
10775 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10776 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10777 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10778 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10779 xserver-xorg-input-kbd xserver-xorg-input-mouse
10780 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10781 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10782 xserver-xorg-video-ati xserver-xorg-video-chips
10783 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10784 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10785 xserver-xorg-video-glint xserver-xorg-video-i128
10786 xserver-xorg-video-i740 xserver-xorg-video-imstt
10787 xserver-xorg-video-intel xserver-xorg-video-mach64
10788 xserver-xorg-video-mga xserver-xorg-video-neomagic
10789 xserver-xorg-video-nsc xserver-xorg-video-nv
10790 xserver-xorg-video-openchrome xserver-xorg-video-r128
10791 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10792 xserver-xorg-video-rendition xserver-xorg-video-s3
10793 xserver-xorg-video-s3virge xserver-xorg-video-savage
10794 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10795 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10796 xserver-xorg-video-tga xserver-xorg-video-trident
10797 xserver-xorg-video-tseng xserver-xorg-video-v4l
10798 xserver-xorg-video-vesa xserver-xorg-video-vga
10799 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
10800 xulrunner-1.9-gnome-support&lt;/p&gt;
10801
10802 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
10803
10804 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
10805 djvulibre-desktop finger gnome-app-install gnome-mount
10806 gnome-network-admin gnome-spell gnome-vfs-obexftp
10807 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10808 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10809 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10810 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
10811 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
10812 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
10813 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
10814 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
10815 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
10816 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
10817 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
10818 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
10819 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10820 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
10821 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
10822 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
10823 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
10824 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
10825 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10826 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10827 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10828 openoffice.org-writer2latex openssl-blacklist p7zip
10829 python-4suite-xml python-eggtrayicon python-gnome2-desktop
10830 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10831 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10832 swfdec-mozilla totem-gstreamer update-manager wodim
10833 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10834 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10835 zip&lt;/p&gt;
10836
10837 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
10838
10839 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10840 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10841 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10842 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10843 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10844 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10845 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10846 xserver-xorg-input-kbd xserver-xorg-input-mouse
10847 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10848 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10849 xserver-xorg-video-ati xserver-xorg-video-chips
10850 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10851 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10852 xserver-xorg-video-glint xserver-xorg-video-i128
10853 xserver-xorg-video-i740 xserver-xorg-video-imstt
10854 xserver-xorg-video-intel xserver-xorg-video-mach64
10855 xserver-xorg-video-mga xserver-xorg-video-neomagic
10856 xserver-xorg-video-nsc xserver-xorg-video-nv
10857 xserver-xorg-video-openchrome xserver-xorg-video-r128
10858 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10859 xserver-xorg-video-rendition xserver-xorg-video-s3
10860 xserver-xorg-video-s3virge xserver-xorg-video-savage
10861 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10862 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10863 xserver-xorg-video-tga xserver-xorg-video-trident
10864 xserver-xorg-video-tseng xserver-xorg-video-v4l
10865 xserver-xorg-video-vesa xserver-xorg-video-vga
10866 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
10867
10868 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
10869 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
10870 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10871 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10872 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10873 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10874 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10875 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10876 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10877 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10878 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10879 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10880 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10881 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10882 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10883 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10884 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10885 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10886 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10887 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10888 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10889 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10890 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10891 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10892 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10893 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10894 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10895 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10896 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10897 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10898 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10899 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10900 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10901 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10902 texlive-common texlive-doc-base texlive-fonts-recommended
10903 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10904 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10905 xulrunner-1.9&lt;/p&gt;
10906
10907 </description>
10908 </item>
10909
10910 <item>
10911 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10912 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10914 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10915 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10916 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10917 have been discovered and reported in the process
10918 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10919 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10920 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10921 kdebase-workspace-data), and to get a more regular testing going on, I
10922 am working on a script to automate the test.&lt;/p&gt;
10923
10924 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10925 Gnome or KDE desktop installation inside the chroot before upgrading
10926 it. To ensure no services are started in the chroot, a policy-rc.d
10927 script is inserted. To make sure tasksel believe it is to install a
10928 desktop on a laptop, the tasksel tests are replaced in the chroot
10929 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10930
10931 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10932 currently always fail because udev refuses to upgrade with the kernel
10933 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10934 is created. The bug report
10935 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10936 this problem do not trigger in a chroot, but I touch the file anyway
10937 to make sure the upgrade go well. Testing on virtual and real
10938 hardware have failed me because of udev so far, and creating this file
10939 do the trick in such settings anyway. This is a
10940 &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
10941 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10942 maintainer because he lack the resources to rewrite udev to keep
10943 working with old kernels or something like that. I really wish the
10944 udev upstream would keep udev backwards compatible, to avoid such
10945 upgrade problem, but given that they fail to do so, I guess
10946 documenting the way out of this mess is the best option we got for
10947 Debian Squeeze.&lt;/p&gt;
10948
10949 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10950 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10951 trick:&lt;/p&gt;
10952
10953 &lt;blockquote&gt;&lt;pre&gt;
10954 #!/bin/sh
10955 set -ex
10956
10957 if [ &quot;$1&quot; ] ; then
10958 desktop=$1
10959 else
10960 desktop=gnome
10961 fi
10962
10963 from=lenny
10964 to=squeeze
10965
10966 exec &amp;lt; /dev/null
10967 unset LANG
10968 mirror=http://ftp.skolelinux.org/debian
10969 tmpdir=chroot-$from-upgrade-$to-$desktop
10970 fuser -mv .
10971 debootstrap $from $tmpdir $mirror
10972 chroot $tmpdir aptitude update
10973 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10974 #!/bin/sh
10975 exit 101
10976 EOF
10977 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10978 exit_cleanup() {
10979 umount $tmpdir/proc
10980 }
10981 mount -t proc proc $tmpdir/proc
10982 # Make sure proc is unmounted also on failure
10983 trap exit_cleanup EXIT INT
10984
10985 chroot $tmpdir aptitude -y install debconf-utils
10986
10987 # Make sure tasksel autoselection trigger. It need the test scripts
10988 # to return the correct answers.
10989 echo tasksel tasksel/desktop multiselect $desktop | \
10990 chroot $tmpdir debconf-set-selections
10991
10992 # Include the desktop and laptop task
10993 for test in desktop laptop ; do
10994 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10995 #!/bin/sh
10996 exit 2
10997 EOF
10998 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10999 done
11000
11001 DEBIAN_FRONTEND=noninteractive
11002 DEBIAN_PRIORITY=critical
11003 export DEBIAN_FRONTEND DEBIAN_PRIORITY
11004 chroot $tmpdir tasksel --new-install
11005
11006 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
11007 chroot $tmpdir aptitude update
11008 touch $tmpdir/etc/udev/kernel-upgrade
11009 chroot $tmpdir aptitude -y dist-upgrade
11010 fuser -mv
11011 &lt;/pre&gt;&lt;/blockquote&gt;
11012
11013 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
11014 with aptitude, but I have not had time to look at how they behave
11015 differently so far. I hope to get a cron job running to do the test
11016 regularly and post the result on the web. The Gnome upgrade currently
11017 work, while the KDE upgrade fail because of the bug in
11018 kdebase-workspace-data&lt;/p&gt;
11019
11020 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
11021 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
11022 post, so I will refrain from trying. I can report that for Gnome,
11023 aptitude report 760 packages upgraded, 448 newly installed, 129 to
11024 remove and 1 not upgraded and 1024MB need to be downloaded while for
11025 KDE the same numbers are 702 packages upgraded, 507 newly installed,
11026 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
11027
11028 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
11029 is able to migrate to dependency based boot sequencing and parallel
11030 booting without a hitch. Was unsure if there were still bugs with
11031 packages failing to clean up their obsolete init.d script during
11032 upgrades, and no such problem seem to affect the Gnome desktop+laptop
11033 packages.&lt;/p&gt;
11034 </description>
11035 </item>
11036
11037 <item>
11038 <title>Upstart or sysvinit - as init.d scripts see it</title>
11039 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
11040 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
11041 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
11042 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
11043 scripts to migrate (some of) their operations to upstart job while
11044 keeping the init.d for hurd and kfreebsd. The packages with such
11045 needs will need a way to get their init.d scripts to behave
11046 differently when used with sysvinit and with upstart. Because of
11047 this, I had a look at the environment variables set when a init.d
11048 script is running under upstart, and when it is not.&lt;/p&gt;
11049
11050 &lt;p&gt;With upstart, I notice these environment variables are set when a
11051 script is started from rcS.d/ (ignoring some irrelevant ones like
11052 COLUMNS):&lt;/p&gt;
11053
11054 &lt;blockquote&gt;&lt;pre&gt;
11055 DEFAULT_RUNLEVEL=2
11056 previous=N
11057 PREVLEVEL=
11058 RUNLEVEL=
11059 runlevel=S
11060 UPSTART_EVENTS=startup
11061 UPSTART_INSTANCE=
11062 UPSTART_JOB=rc-sysinit
11063 &lt;/pre&gt;&lt;/blockquote&gt;
11064
11065 &lt;p&gt;With sysvinit, these environment variables are set for the same
11066 script.&lt;/p&gt;
11067
11068 &lt;blockquote&gt;&lt;pre&gt;
11069 INIT_VERSION=sysvinit-2.88
11070 previous=N
11071 PREVLEVEL=N
11072 RUNLEVEL=S
11073 runlevel=S
11074 &lt;/pre&gt;&lt;/blockquote&gt;
11075
11076 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
11077 sysvinit are not set by upstart. Not sure if it is intentional or not
11078 to not be compatible with sysvinit in this regard.&lt;/p&gt;
11079
11080 &lt;p&gt;For scripts needing to behave differently when upstart is used,
11081 looking for the UPSTART_JOB environment variable seem to be a good
11082 choice.&lt;/p&gt;
11083 </description>
11084 </item>
11085
11086 <item>
11087 <title>A manual for standards wars...</title>
11088 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
11089 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
11090 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
11091 <description>&lt;p&gt;Via the
11092 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
11093 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
11094 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
11095 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
11096 following the standards wars of today.&lt;/p&gt;
11097 </description>
11098 </item>
11099
11100 <item>
11101 <title>Sitesummary tip: Listing computer hardware models used at site</title>
11102 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
11103 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
11104 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
11105 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
11106 to get a list of the machine types in use thanks to the DMI
11107 information extracted from each machine. The script to do so is
11108 included in the sitesummary package, and here is example output from
11109 the Skolelinux build servers:&lt;/p&gt;
11110
11111 &lt;blockquote&gt;&lt;pre&gt;
11112 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11113 vendor count
11114 Dell Computer Corporation 1
11115 PowerEdge 1750 1
11116 IBM 1
11117 eserver xSeries 345 -[8670M1X]- 1
11118 Intel 2
11119 [no-dmi-info] 3
11120 maintainer:~#
11121 &lt;/pre&gt;&lt;/blockquote&gt;
11122
11123 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
11124 provided in each machine. Here there are Intel machines without model
11125 information listed with Intel as vendor and no model, and virtual Xen
11126 machines listed as [no-dmi-info]. One can add -l as a command line
11127 option to list the individual machines.&lt;/p&gt;
11128
11129 &lt;p&gt;A larger list is
11130 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
11131 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
11132 provide the basic sitesummary report publicly. In their report there
11133 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
11134 their machines, and as sitesummary is available in both distributions,
11135 it is trivial to get all of them to report to the same central
11136 collector.&lt;/p&gt;
11137 </description>
11138 </item>
11139
11140 <item>
11141 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
11142 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
11143 <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>
11144 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
11145 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
11146 start at boot when an NVidia video card is used is handled. The
11147 problem seem to be that the nvidia X.org driver uses a long time to
11148 initialize, and this duration is longer than kdm is configured to
11149 wait.&lt;/p&gt;
11150
11151 &lt;p&gt;I came across two bugs related to this issue,
11152 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
11153 against initscripts and passed on to nvidia-glx when it became obvious
11154 that the nvidia drivers were involved, and
11155 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
11156 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
11157
11158 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
11159 problem nvidia video card owners experience and make sure the Debian
11160 distribution work out of the box for these users. The nvidia driver
11161 maintainers expect kdm to be set up to wait longer, while kdm expect
11162 the nvidia driver maintainers to fix the driver to start faster, and
11163 while they wait for each other I guess the users end up switching to a
11164 distribution that work for them. I have no idea what the solution is,
11165 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
11166
11167 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
11168 </description>
11169 </item>
11170
11171 <item>
11172 <title>Parallellized boot seem to hold up well in Debian/testing</title>
11173 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
11174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
11175 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
11176 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
11177 The feature seem to hold up pretty well, but three fairly serious
11178 issues are known and should be solved:
11179
11180 &lt;p&gt;&lt;ul&gt;
11181
11182 &lt;li&gt;The wicd package seen to
11183 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
11184 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
11185 parallel booting is enabled. No idea why, but the wicd maintainer
11186 seem to be on the case.&lt;/li&gt;
11187
11188 &lt;li&gt;The nvidia X driver seem to
11189 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
11190 triggered more easily when parallel booting is in effect. The
11191 maintainer is on the case.&lt;/li&gt;
11192
11193 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
11194 sequencing (the shutdown is broken) when old file-rc users
11195 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
11196 sysv-rc. One way to solve it would be for file-rc to create
11197 /etc/init.d/.legacy-bootordering, and another is to try to make
11198 sysv-rc more robust. Will investigate some more and probably upload a
11199 workaround in sysv-rc to help those trying to move from file-rc to
11200 sysv-rc get a working shutdown.&lt;/li&gt;
11201
11202 &lt;/ul&gt;&lt;/p&gt;
11203
11204 &lt;p&gt;All in all not many surprising issues, and all of them seem
11205 solvable before Squeeze is released. In addition to these there are
11206 some packages with bugs in their dependencies and run level settings,
11207 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
11208
11209 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11210 the BTS, please usertag the report to get it to show up at
11211 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11212 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11213
11214 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
11215 </description>
11216 </item>
11217
11218 <item>
11219 <title>More flexible firmware handling in debian-installer</title>
11220 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
11221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
11222 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
11223 <description>&lt;p&gt;After a long break from debian-installer development, I finally
11224 found time today to return to the project. Having to spend less time
11225 working dependency based boot in debian, as it is almost complete now,
11226 definitely helped freeing some time.&lt;/p&gt;
11227
11228 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
11229 include some firmware packages on the Debian Edu CDs, those needed to
11230 get disk and network controllers working. Without having these
11231 firmware packages available during installation, it is impossible to
11232 install Debian Edu on the given machine, and because our target group
11233 are non-technical people, asking them to provide firmware packages on
11234 an external medium is a support pain. Initially, I expected it to be
11235 enough to include the firmware packages on the CD to get
11236 debian-installer to find and use them. This proved to be wrong.
11237 Next, I hoped it was enough to symlink the relevant firmware packages
11238 to some useful location on the CD (tried /cdrom/ and
11239 /cdrom/firmware/). This also proved to not work, and at this point I
11240 found time to look at the debian-installer code to figure out what was
11241 going to work.&lt;/p&gt;
11242
11243 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
11244 look revealed that it would only look for firmware packages outside
11245 the installation media, so the CD was never checked for firmware
11246 packages. It would only check USB sticks, floppies and other
11247 &quot;external&quot; media devices. Today I changed it to also look in the
11248 /cdrom/firmware/ directory on the mounted CD or DVD, which should
11249 solve the problem I ran into with Debian edu. I also changed it to
11250 look in /firmware/, to make sure the installer also find firmware
11251 provided in the initrd when booting the installer via PXE, to allow us
11252 to provide the same feature in the PXE setup included in Debian
11253 Edu.&lt;/p&gt;
11254
11255 &lt;p&gt;To make sure firmware deb packages with a license questions are not
11256 activated without asking if the license is accepted, I extended
11257 hw-detect to look for preinst scripts in the firmware packages, and
11258 run these before activating the firmware during installation. The
11259 license question is asked using debconf in the preinst, so this should
11260 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
11261
11262 &lt;p&gt;If you want to discuss the details of these features, please
11263 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
11264 </description>
11265 </item>
11266
11267 <item>
11268 <title>Parallellized boot is now the default in Debian/unstable</title>
11269 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
11270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
11271 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
11272 <description>&lt;p&gt;Since this evening, parallel booting is the default in
11273 Debian/unstable for machines using dependency based boot sequencing.
11274 Apparently the testing of concurrent booting has been wider than
11275 expected, if I am to believe the
11276 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11277 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
11278 with the feature this weekend, to give us some time to detect any
11279 remaining problems before Squeeze is frozen. If serious problems are
11280 detected, it is simple to change the default back to sequential boot.
11281 The upload of the new sysvinit package also activate a new upstream
11282 version.&lt;/p&gt;
11283
11284 More information about
11285 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11286 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
11287 currently possible to disable parallel booting when one run into
11288 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
11289
11290 &lt;blockquote&gt;&lt;pre&gt;
11291 CONCURRENCY=none
11292 &lt;/pre&gt;&lt;/blockquote&gt;
11293
11294 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11295 the BTS, please usertag the report to get it to show up at
11296 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11297 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11298 </description>
11299 </item>
11300
11301 <item>
11302 <title>Sitesummary tip: Listing MAC address of all clients</title>
11303 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
11304 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
11305 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
11306 <description>&lt;p&gt;In the recent Debian Edu versions, the
11307 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
11308 system&lt;/a&gt; is used to keep track of the machines in the school
11309 network. Each machine will automatically report its status to the
11310 central server after boot and once per night. The network setup is
11311 also reported, and using this information it is possible to get the
11312 MAC address of all network interfaces in the machines. This is useful
11313 to update the DHCP configuration.&lt;/p&gt;
11314
11315 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
11316 ist all MAC addresses of all machines reporting to sitesummary. Run
11317 this on the collector host:&lt;/p&gt;
11318
11319 &lt;blockquote&gt;&lt;pre&gt;
11320 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
11321 &lt;/pre&gt;&lt;/blockquote&gt;
11322
11323 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
11324 line per machine and with space between the MAC addresses.&lt;/p&gt;
11325
11326 &lt;p&gt;To allow system administrators easier job at adding static DHCP
11327 addresses for hosts, it would be possible to extend this to fetch
11328 machine information from sitesummary and update the DHCP and DNS
11329 tables in LDAP using this information. Such tool is unfortunately not
11330 written yet.&lt;/p&gt;
11331 </description>
11332 </item>
11333
11334 <item>
11335 <title>systemd, an interesting alternative to upstart</title>
11336 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
11337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
11338 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
11339 <description>&lt;p&gt;The last few days a new boot system called
11340 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
11341 has been
11342 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
11343
11344 to the free software world. I have not yet had time to play around
11345 with it, but it seem to be a very interesting alternative to
11346 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
11347 a good alternative for Debian when we are able to switch to an event
11348 based boot system. Tollef is
11349 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
11350 systemd into Debian, and I look forward to seeing how well it work. I
11351 like the fact that systemd handles init.d scripts with dependency
11352 information natively, allowing them to run in parallel where upstart
11353 at the moment do not.&lt;/p&gt;
11354
11355 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
11356 platform support. It only work on recent Linux kernels, and also need
11357 some new kernel features enabled to function properly. This means
11358 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11359 system. Not sure how that will be handled if systemd proves to be the
11360 way forward.&lt;/p&gt;
11361
11362 &lt;p&gt;In the mean time, based on the
11363 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
11364 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
11365 decided to enable full parallel booting as the default in Debian as
11366 soon as possible (probably this weekend or early next week), to see if
11367 there are any remaining serious bugs in the init.d dependencies. A
11368 new version of the sysvinit package implementing this change is
11369 already in experimental. If all go well, Squeeze will be released
11370 with parallel booting enabled by default.&lt;/p&gt;
11371 </description>
11372 </item>
11373
11374 <item>
11375 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
11376 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
11377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
11378 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
11379 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
11380 complete, so complete that it is actually possible to run all the
11381 init.d scripts in parallell based on these dependencies. If you want
11382 to test your Squeeze system, make sure
11383 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11384 based boot sequencing&lt;/a&gt; is enabled, and add this line to
11385 /etc/default/rcS:&lt;/p&gt;
11386
11387 &lt;blockquote&gt;&lt;pre&gt;
11388 CONCURRENCY=makefile
11389 &lt;/pre&gt;&lt;/blockquote&gt;
11390
11391 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
11392 scripts in parallel using the dependency information stored in
11393 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11394 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11395 to try to start the kdm and gdm scripts as early as possible, and will
11396 start the facilities required by kdm or gdm as early as possible to
11397 make this happen.&lt;/p&gt;
11398
11399 &lt;p&gt;Give it a try, and see if you like the result. If some services
11400 fail to start properly, it is most likely because they have incomplete
11401 init.d script dependencies in their startup script (or some of their
11402 dependent scripts have incomplete dependencies). Report bugs and get
11403 the package maintainers to fix it. :)&lt;/p&gt;
11404
11405 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
11406 manage to get the init.d script dependencies complete and correct. I
11407 expect we will get there in Squeeze+1, if we get manage to test and
11408 fix the remaining issues.&lt;/p&gt;
11409
11410 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11411 the BTS, please usertag the report to get it to show up at
11412 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11413 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11414 </description>
11415 </item>
11416
11417 <item>
11418 <title>Debian has switched to dependency based boot sequencing</title>
11419 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
11420 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
11421 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
11422 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
11423 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
11424 have been migrated to using dependency based boot sequencing. This
11425 conclude work me and others have been doing for the last three days.
11426 It feels great to see this finally part of the default Debian
11427 installation. Now we just need to weed out the last few problems that
11428 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
11429
11430 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
11431 fixing the more fundamental problem of handing the event based
11432 non-predictable kernel in the early boot.&lt;/p&gt;
11433 </description>
11434 </item>
11435
11436 <item>
11437 <title>Taking over sysvinit development</title>
11438 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
11439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
11440 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
11441 <description>&lt;p&gt;After several years of frustration with the lack of activity from
11442 the existing sysvinit upstream developer, I decided a few weeks ago to
11443 take over the package and become the new upstream. The number of
11444 patches to track for the Debian package was becoming a burden, and the
11445 lack of synchronization between the distribution made it hard to keep
11446 the package up to date.&lt;/p&gt;
11447
11448 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11449 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
11450 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
11451 and Fedora), based on the patches currently in use in these
11452 distributions. We Debian maintainers plan to move to this tarball as
11453 the new upstream as soon as we find time to do the merge. Since the
11454 new tarball was created, we agreed with Werner at SuSe to make a new
11455 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
11456 development there. The project is registered and currently waiting
11457 for approval by the Savannah administrators, and as soon as it is
11458 approved, we will import the old versions from svn and continue
11459 working on the future release.&lt;/p&gt;
11460
11461 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
11462 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
11463 </description>
11464 </item>
11465
11466 <item>
11467 <title>Debian boots quicker and quicker</title>
11468 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
11469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
11470 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
11471 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
11472 people involved in the boot system on Debian and Ubuntu, to see if we
11473 could find more ways to speed up the boot system. This was an Ubuntu
11474 funded
11475 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
11476 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
11477 of boot systems, and ways to handle the increasing number of boot
11478 issues introduced by the Linux kernel becoming more and more
11479 asynchronous and event base. The Ubuntu approach using udev and
11480 upstart might be a good way forward. Time will show.&lt;/p&gt;
11481
11482 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
11483 process in Debian. All of these should be applied to get a quick
11484 boot:&lt;/p&gt;
11485
11486 &lt;ul&gt;
11487
11488 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
11489
11490 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
11491 clock is in UTC.&lt;/li&gt;
11492
11493 &lt;li&gt;Install and activate the insserv package to enable
11494 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
11495 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
11496
11497 &lt;/ul&gt;
11498
11499 These points are based on the Google summer of code work done by
11500 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
11501 Villegas&lt;/a&gt;.
11502
11503 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
11504 unstable yesterday. When we tested it, we were able to cut 6 seconds
11505 from the boot sequence. It depend on very correct dependency
11506 declaration in all init.d scripts, so I expect us to find edge cases
11507 where the dependences in some scripts are slightly wrong when we start
11508 using this.&lt;/p&gt;
11509
11510 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11511 introduced by Raphael Geissert today, one that could affect the
11512 startup speed as well. Instead of starting some scripts concurrently
11513 from rcS.d/ and another set of scripts from rc2.d/, it would be
11514 possible to run a of them in the same process. A quick way to test
11515 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
11516 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
11517 </description>
11518 </item>
11519
11520 <item>
11521 <title>BSAs påstander om piratkopiering møter motstand</title>
11522 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
11523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
11524 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
11525 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
11526 programvareselskapene som Microsoft og Apple, publisert en rapport der
11527 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11528 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11529 dager siden kom
11530 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
11531 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
11532 dagene. Et spesielt interessant kommentar fra Sverige,
11533 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
11534 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
11535
11536 &lt;blockquote&gt;
11537 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
11538 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11539 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
11540 exakta&quot;, säger BSAs Sverigechef John Hugosson.
11541 &lt;/blockquote&gt;
11542
11543 &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
11544 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
11545 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
11546 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
11547 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
11548
11549 &lt;p&gt;Fant lenkene via &lt;a
11550 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
11551 på Slashdot&lt;/a&gt;.&lt;/p&gt;
11552 </description>
11553 </item>
11554
11555 <item>
11556 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
11557 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
11558 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
11559 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
11560 <description>&lt;p&gt;Kom over
11561 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
11562 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11563 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11564 jobber til daglig. En rask opptelling forteller meg at vi har 490
11565 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
11566 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
11567 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
11568 </description>
11569 </item>
11570
11571 <item>
11572 <title>Kryptert harddisk - naturligvis</title>
11573 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
11574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
11575 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
11576 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
11577 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
11578 når en tar tap av arbeidstid, fortrolige dokumenter,
11579 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11580 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11581 til at jeg har kryptert harddisken på både kontormaskinen og min
11582 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11583 komme på avveie, den første informasjon relatert til jobben min ved
11584 Universitetet i Oslo, og den andre relatert til blant annet
11585 foreningsarbeide. Kryptering av diskene gjør at det er lite
11586 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11587 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11588 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11589 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11590 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11591 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11592 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11593 det er gjort slik jeg gjør det er minimale, og gevinstene er
11594 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11595 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
11596
11597 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11598 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11599 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11600 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11601 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11602 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11603 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11604 betydelige.&lt;/p&gt;
11605 </description>
11606 </item>
11607
11608 <item>
11609 <title>Two projects that have improved the quality of free software a lot</title>
11610 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
11611 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
11612 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
11613 <description>&lt;p&gt;There are two software projects that have had huge influence on the
11614 quality of free software, and I wanted to mention both in case someone
11615 do not yet know them.&lt;/p&gt;
11616
11617 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
11618 tool to detect and expose errors in the memory handling of programs.
11619 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
11620 and it will report any problems on stdout. It is even better if the
11621 program include debug information. With debug information, it is able
11622 to report the source file name and line number where the problem
11623 occurs. It can report things like &#39;reading past memory block in file
11624 X line N, the memory block was allocated in file Y, line M&#39;, and
11625 &#39;using uninitialised value in control logic&#39;. This tool has made it
11626 trivial to investigate reproducible crash bugs in programs, and have
11627 reduced the number of this kind of bugs in free software a lot.
11628
11629 &lt;p&gt;The second one is
11630 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
11631 a source code checker. It is able to process the source of a program
11632 and find problems in the logic without running the program. It
11633 started out as the Stanford Checker and became well known when it was
11634 used to find bugs in the Linux kernel. It is now a commercial tool
11635 and the company behind it is running
11636 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
11637 free software community, where a lot of free software projects get
11638 their source checked for free. Several thousand defects have been
11639 found and fixed so far. It can find errors like &#39;lock L taken in file
11640 X line N is never released if exiting in line M&#39;, or &#39;the code in file
11641 Y lines O to P can never be executed&#39;. The projects included in the
11642 community service project have managed to get rid of a lot of
11643 reliability problems thanks to Coverity.&lt;/p&gt;
11644
11645 &lt;p&gt;I believe tools like this, that are able to automatically find
11646 errors in the source, are vital to improve the quality of software and
11647 make sure we can get rid of the crashing and failing software we are
11648 surrounded by today.&lt;/p&gt;
11649 </description>
11650 </item>
11651
11652 <item>
11653 <title>No patch is not better than a useless patch</title>
11654 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
11655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
11656 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
11657 <description>&lt;p&gt;Julien Blache
11658 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
11659 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
11660 patch allow one to discuss a concrete and proposed solution, and also
11661 prove that the issue at hand is important enough for someone to spent
11662 time on fixing it. No patch do not provide any of these positive
11663 properties.&lt;/p&gt;
11664 </description>
11665 </item>
11666
11667 <item>
11668 <title>Standardize on protocols and formats, not vendors and applications</title>
11669 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
11670 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
11671 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
11672 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
11673 very good one to form a long lived computer infrastructure. It is the
11674 simple one, lost by many in todays computer industry: Standardize on
11675 open network protocols and open exchange/storage formats, not applications.
11676 Applications come and go, while protocols and files tend to stay, and
11677 thus one want to make it easy to change application and vendor, while
11678 avoiding conversion costs and locking users to a specific platform or
11679 application.&lt;/p&gt;
11680
11681 &lt;p&gt;This approach make it possible to replace the client applications
11682 independently of the server applications. One can even allow users to
11683 use several different applications as long as they handle the selected
11684 protocol and format. In the normal case, only one client application
11685 is recommended and users only get help if they choose to use this
11686 application, but those that want to deviate from the easy path are not
11687 blocked from doing so.&lt;/p&gt;
11688
11689 &lt;p&gt;It also allow us to replace the server side without forcing the
11690 users to replace their applications, and thus allow us to select the
11691 best server implementation at any moment, when scale and resouce
11692 requirements change.&lt;/p&gt;
11693
11694 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
11695 open formats, but I would never recommend standardizing on a single
11696 application that do not use open network protocol or open formats.&lt;/p&gt;
11697 </description>
11698 </item>
11699
11700 <item>
11701 <title>Returning from Skolelinux developer gathering</title>
11702 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
11703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
11704 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
11705 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
11706 Edu/Skolelinux development gathering. I got a bit done tuning the
11707 desktop, and looked into the dynamic service location protocol
11708 implementation avahi. It look like it could be useful for us. Almost
11709 30 people participated, and I believe it was a great environment to
11710 get to know the Skolelinux system. Walter Bender, involved in the
11711 development of the Sugar educational platform, presented his stuff and
11712 also helped me improve my OLPC installation. He also showed me that
11713 his Turtle Art application can be used in standalone mode, and we
11714 agreed that I would help getting it packaged for Debian. As a
11715 standalone application it would be great for Debian Edu. We also
11716 tried to get the video conferencing working with two OLPCs, but that
11717 proved to be too hard for us. The application seem to need more work
11718 before it is ready for me. I look forward to getting home and relax
11719 now. :)&lt;/p&gt;
11720 </description>
11721 </item>
11722
11723 <item>
11724 <title>Time for new LDAP schemas replacing RFC 2307?</title>
11725 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
11726 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
11727 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
11728 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
11729 optimal. There is RFC 2307 documenting one way to store NIS maps in
11730 LDAP, and a modified version of this normally called RFC 2307bis, with
11731 some modifications to be compatible with Active Directory. The RFC
11732 specification handle the content of a lot of system databases, but do
11733 not handle DNS zones and DHCP configuration.&lt;/p&gt;
11734
11735 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
11736 we would like to store information about users, SMB clients/hosts,
11737 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11738 and LTSP configuration in LDAP. These objects have a lot in common,
11739 but with the current LDAP schemas it is not possible to have one
11740 object per entity. For example, one need to have at least three LDAP
11741 objects for a given computer, one with the SMB related stuff, one with
11742 DNS information and another with DHCP information. The schemas
11743 provided for DNS and DHCP are impossible to combine into one LDAP
11744 object. In addition, it is impossible to implement quick queries for
11745 netgroup membership, because of the way NIS triples are implemented.
11746 It just do not scale. I believe it is time for a few RFC
11747 specifications to cleam up this mess.&lt;/p&gt;
11748
11749 &lt;p&gt;I would like to have one LDAP object representing each computer in
11750 the network, and this object can then keep the SMB (ie host key), DHCP
11751 (mac address/name) and DNS (name/IP address) settings in one place.
11752 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
11753
11754 &lt;p&gt;I would also like to have a quick way to map from a user or
11755 computer and to the net group this user or computer is a member.&lt;/p&gt;
11756
11757 &lt;p&gt;Active Directory have done a better job than unix heads like myself
11758 in this regard, and the unix side need to catch up. Time to start a
11759 new IETF work group?&lt;/p&gt;
11760 </description>
11761 </item>
11762
11763 <item>
11764 <title>Endelig er Debian Lenny gitt ut</title>
11765 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
11766 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
11767 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
11768 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
11769 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
11770 Et langt steg videre for Debian-prosjektet, og en rekke nye
11771 programpakker blir nå tilgjengelig for de av oss som bruker den
11772 stabile utgaven av Debian. Neste steg er nå å få
11773 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
11774 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
11775 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11776 slippes løs på skolene. Takk til alle debian-utviklerne som har
11777 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11778 bootsekvens tilgjengelig i stabil utgave, vha pakken
11779 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
11780 </description>
11781 </item>
11782
11783 <item>
11784 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
11785 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
11786 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
11787 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
11788 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
11789 Oslo. Most of Saturday was used for the general assemly for the
11790 member organization, but the rest of the weekend I used to tune the
11791 LTSP installation. LTSP now work out of the box on the 10-network.
11792 Acer Aspire One proved to be a very nice thin client, with both
11793 screen, mouse and keybard in a small box. Was working on getting the
11794 diskless workstation setup configured out of the box, but did not
11795 finish it before the weekend was up.&lt;/p&gt;
11796
11797 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
11798 the Brazilian group, so that will have to wait for the next
11799 development gathering. Would love to have the Debian Edu installer
11800 automatically detect and configure a multiseat setup when it find one
11801 of these cards.&lt;/p&gt;
11802 </description>
11803 </item>
11804
11805 <item>
11806 <title>The sorry state of multimedia browser plugins in Debian</title>
11807 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
11808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
11809 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
11810 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
11811 plugins available in Debian Lenny, to see which one we should use by
11812 default in Debian Edu. We need an embedded video playing plugin with
11813 control buttons to pause or stop the video, and capable of streaming
11814 all the multimedia content available on the web. The test results and
11815 notes are available on
11816 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
11817 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
11818 fill this need. My personal video player favorite, VLC, has a really
11819 bad plugin which fail on a lot of the test pages. A lot of the MIME
11820 types I would expect to work with any free software player (like
11821 video/ogg), just do not work. And simple formats like the
11822 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
11823 totem and vlc plugins. I hope the situation will improve soon. No
11824 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
11825
11826 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
11827 be the only one fitting our needs. :/&lt;/p&gt;
11828 </description>
11829 </item>
11830
11831 </channel>
11832 </rss>