]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
c2f7772fa14b34c17aaf87d7a1ef183cb773adee
[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>Isenkram updated with a lot more hardware-package mappings</title>
11 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
13 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
14 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
15 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
16 and install packages to get your hardware dongles to work, is still
17 going strong. It is a system to look up the hardware present on or
18 connected to the current system, and map the hardware to Debian
19 packages. It can either be done using the tools in isenkram-cli or
20 using the user space daemon in the isenkram package. The latter will
21 notify you, when inserting new hardware, about what packages to
22 install to get the dongle working. It will even provide a button to
23 click on to ask packagekit to install the packages.&lt;/p&gt;
24
25 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
26
27 &lt;p&gt;&lt;pre&gt;
28 % isenkram-lookup
29 bluez
30 cheese
31 ethtool
32 fprintd
33 fprintd-demo
34 gkrellm-thinkbat
35 hdapsd
36 libpam-fprintd
37 pidgin-blinklight
38 thinkfan
39 tlp
40 tp-smapi-dkms
41 tp-smapi-source
42 tpb
43 %
44 &lt;/pre&gt;&lt;/p&gt;
45
46 &lt;p&gt;It can also list the firware package providing firmware requested
47 by the load kernel modules, which in my case is an empty list because
48 I have all the firmware my machine need:
49
50 &lt;p&gt;&lt;pre&gt;
51 % /usr/sbin/isenkram-autoinstall-firmware -l
52 info: did not find any firmware files requested by loaded kernel modules. exiting
53 %
54 &lt;/pre&gt;&lt;/p&gt;
55
56 &lt;p&gt;The last few days I had a look at several of the around 250
57 packages in Debian with udev rules. These seem like good candidates
58 to install when a given hardware dongle is inserted, and I found
59 several that should be proposed by isenkram. I have not had time to
60 check all of them, but am happy to report that now there are 97
61 packages packages mapped to hardware by Isenkram. 11 of these
62 packages provide hardware mapping using AppStream, while the rest are
63 listed in the modaliases file provided in isenkram.&lt;/p&gt;
64
65 &lt;p&gt;These are the packages with hardware mappings at the moment. The
66 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
67 support using AppStream, for everyone to use:&lt;/p&gt;
68
69 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
70 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
71 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
72 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
73 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
74 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
75 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
76 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
77 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
78 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
79 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
80 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
81 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
82 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
83 pcscd, pidgin-blinklight, printer-driver-splix,
84 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
85 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
86 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
87 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
88 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
89 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
90 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
91 xserver-xorg-video-vmware, yubikey-personalization and
92 zd1211-firmware&lt;/p&gt;
93
94 &lt;p&gt;If you know of other packages, please let me know with a wishlist
95 bug report against the isenkram-cli package, and ask the package
96 maintainer to
97 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
98 metadata according to the guidelines&lt;/a&gt; to provide the information
99 for everyone. In time, I hope to get rid of the isenkram specific
100 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
101
102 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
103 much hardware, and suggest that the package with with any ethernet
104 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
105 the details. I hope the maintainer find time to address it soon. In
106 the mean time I provide an override in isenkram.&lt;/p&gt;
107 </description>
108 </item>
109
110 <item>
111 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
112 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
113 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
114 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
115 <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;
116
117 &lt;p&gt;In my early years, I played
118 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
119 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
120 space, and reached the &#39;elite&#39; fighting status before I moved on. The
121 original Elite game was available on Commodore 64 and the IBM PC
122 edition I played had a 64 KB executable. I am still impressed today
123 that the authors managed to squeeze both a 3D engine and details about
124 more than 2000 planet systems across 7 galaxies into a binary so
125 small.&lt;/p&gt;
126
127 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
128 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
129 really have time to test it properly until a few days ago. It was
130 great to discover that my old knowledge about trading routes were
131 still valid. But my fighting and flying abilities were gone, so I had
132 to retrain to be able to dock on a space station. And I am still not
133 able to make much resistance when I am attacked by pirates, so I
134 bougth and mounted the most powerful laser in the rear to be able to
135 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
136
137 &lt;p&gt;When playing Elite in the late eighties, I had to discover
138 everything on my own, and I had long lists of prices seen on different
139 planets to be able to decide where to trade what. This time I had the
140 advantages of the
141 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
142 where information about each planet is easily available with common
143 price ranges and suggested trading routes. This improved my ability
144 to earn money and I have been able to earn enough to buy a lot of
145 useful equipent in a few days. I believe I originally played for
146 months before I could get a docking computer, while now I could get it
147 after less then a week.&lt;/p&gt;
148
149 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
150 space, you should try out Oolite. It is available for Linux, MacOSX
151 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
152
153 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
154 activities, please send Bitcoin donations to my address
155 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
156 </description>
157 </item>
158
159 <item>
160 <title>Quicker Debian installations using eatmydata</title>
161 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
162 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
163 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
164 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
165 installation system, observing how using
166 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
167 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
168 speedup around 20-40 percent for Debian Edu, where we install around
169 1000 packages from within the installer. The eatmydata package
170 provide a way to disable/delay file system flushing. This is a bit
171 risky in the general case, as files that should be stored on disk will
172 stay only in memory a bit longer than expected, causing problems if a
173 machine crashes at an inconvenient time. But for an installation, if
174 the machine crashes during installation the process is normally
175 restarted, and avoiding disk operations as much as possible to speed
176 up the process make perfect sense.
177
178 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
179 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
180 but did not have time to push it any further. But a few months ago I
181 picked it up again and worked with the libeatmydata package maintainer
182 Mattia Rizzolo to make it easier for everyone to get this installation
183 speedup in Debian. Thanks to our cooperation There is now an
184 eatmydata-udeb package in Debian testing and unstable, and simply
185 enabling/installing it in debian-installer (d-i) is enough to get the
186 quicker installations. It can be enabled using preseeding. The
187 following untested kernel argument should do the trick:&lt;/p&gt;
188
189 &lt;blockquote&gt;&lt;pre&gt;
190 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
191 &lt;/pre&gt;&lt;/blockquote&gt;
192
193 &lt;p&gt;This should ask d-i to install the package inside the d-i
194 environment early in the installation sequence. Having it installed
195 in d-i in turn will make sure the relevant scripts are called just
196 after debootstrap filled /target/ with the freshly installed Debian
197 system to configure apt to run dpkg with eatmydata. This is enough to
198 speed up the installation process. There is a proposal to
199 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
200 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
201 tested its impact.&lt;/p&gt;
202
203 </description>
204 </item>
205
206 <item>
207 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
208 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
209 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
210 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
211 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
212 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
213 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
214 elever over det ganske land skal levere inn hvert år. Det mange ikke
215 vet er at selv om de kommersielle alternativene
216 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
217 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
218 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
219 utmerket fri programvarealternativ som kan. Oversetterverktøyet
220 Apertium har støtte for en rekke språkkombinasjoner, og takket være
221 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
222 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
223 nynorsk, og få den automatoversatt til det andre skriftspråket.
224 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
225 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
226 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
227 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
228 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
229 teksten din i webskjemaet der.
230
231 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
232 teknologien kan du enten installere pakken
233 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
234 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
235 api.apertium.org. Se
236 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
237 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
238 denne teksten som ble skrevet på bokmål over maskinoversatt til
239 nynorsk.&lt;/p&gt;
240
241 &lt;hr/&gt;
242
243 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
244 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
245 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
246 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
247 veit er at sjølv om dei kommersielle alternativa
248 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
249 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
250 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
251 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
252 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
253 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
254 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
255 nynorsk, og få den *automatoversatt til det andre skriftspråket.
256 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
257 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
258 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
259 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
260 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
261 teksta di i *webskjemaet der.
262
263 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
264 teknologien kan du anten installera pakken
265 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
266 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
267 *api.*apertium.org. Sjå
268 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
269 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
270 for denne teksta som vart skreva på bokmål over *maskinoversatt til
271 nynorsk.&lt;/p&gt;
272 </description>
273 </item>
274
275 <item>
276 <title>Coz profiler for multi-threaded software is now in Debian</title>
277 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
278 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
279 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
280 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
281 profiler able to run benchmarking experiments on the instrumented
282 multi-threaded program, finally
283 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
284 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
285 months since
286 &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
287 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
288 it suitable for Debian. There are still issues with clang
289 compatibility, inline assembly only working x86 and minimized
290 JavaScript libraries.&lt;/p&gt;
291
292 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
293
294 &lt;p&gt;&lt;blockquote&gt;
295 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
296 &lt;/blockquote&gt;&lt;/p&gt;
297
298 &lt;p&gt;This will produce a profile.coz file in the current working
299 directory with the profiling information. This is then given to a
300 JavaScript application provided in the package and available from
301 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
302 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
303
304 &lt;p&gt;&lt;blockquote&gt;
305 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
306 &lt;/blockquote&gt;&lt;/p&gt;
307
308 &lt;p&gt;See the project home page and the
309 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
310 ;login: article on Coz&lt;/a&gt; for more information on how it is
311 working.&lt;/p&gt;
312 </description>
313 </item>
314
315 <item>
316 <title>My own self balancing Lego Segway</title>
317 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
318 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
319 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
320 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
321 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
322 present. It had been on my wishlist for a while, because I wanted to
323 build a Segway like balancing lego robot. I had already built
324 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
325 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
326 NXT kit as the balance sensor, but it was not working very well. It
327 could balance for a while, but was very sensitive to the light
328 condition in the room and the reflective properties of the surface and
329 would fall over after a short while. I wanted something more robust,
330 and had
331 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
332 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
333 wishlist for some years before it suddenly showed up as a gift from my
334 loved ones. :)&lt;/p&gt;
335
336 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
337 since then. But that changed some days ago, when I was searching for
338 lego segway information and came across a recipe from HiTechnic for
339 building
340 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
341 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
342 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
343 code&lt;/a&gt; was included, so it was just a question of putting it all
344 together. And thanks to the great work of many Debian developers, the
345 compiler needed to build the source for the NXT is already included in
346 Debian, so I was read to go in less than an hour. The resulting robot
347 do not look very impressive in its simplicity:&lt;/p&gt;
348
349 &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;
350
351 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
352 design from HiTechnic, I had to comment out the last task
353 (taskControl). I simply placed /* and */ around it get the program
354 working without that sensor present. Now it balances just fine until
355 the battery status run low:&lt;/p&gt;
356
357 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
358 &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;
359 &lt;/video&gt;&lt;/p&gt;
360
361 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
362 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
363
364 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
365 they need to work with LEGO in Debian and all our derivative
366 distributions like Ubuntu, check out
367 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
368 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
369 RCX and NXT controller (no EV3), and would like to make sure the
370 Debian tools needed to program the systems I own work as they
371 should.&lt;/p&gt;
372 </description>
373 </item>
374
375 <item>
376 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
377 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
378 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
379 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
380 <description>&lt;p&gt;In July
381 &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
382 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
383 the ability to receive SMS messages (aka without a cell phone). It is
384 time to share some experiences and provide an updated setup.&lt;/p&gt;
385
386 &lt;p&gt;The Signal app have worked fine for several months now, and I use
387 it regularly to chat with my loved ones. I had a major snag at the
388 end of my summer vacation, when the the app completely forgot my
389 setup, identity and keys. The reason behind this major mess was
390 running out of disk space. To avoid that ever happening again I have
391 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
392 roll back to an earlier version if the files are wiped by mistake. I
393 had to use it once after introducing the git backup. When rolling
394 back to an earlier version, one need to use the &#39;reset session&#39; option
395 in Signal to get going, and notify the people you talk with about the
396 problem. I assume there is some sequence number tracking in the
397 protocol to detect rollback attacks. The git repository is rather big
398 (674 MiB so far), but I have not tried to figure out if some of the
399 content can be added to a .gitignore file due to lack of spare
400 time.&lt;/p&gt;
401
402 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
403 make it impossible to send messages using Signal. I could still
404 receive them, but had to patch the code with a new timestamp to send.
405 I believe the timeout is added by the developers to force people to
406 upgrade to the latest version of the app, even when there is no
407 protocol changes, to reduce the version skew among the user base and
408 thus try to keep the number of support requests down.&lt;/p&gt;
409
410 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
411 making the old patch fail to apply cleanly. Below is an updated
412 patch, including the shell wrapper I use to start Signal. The
413 original version required a new user to locate the JavaScript console
414 and call a function from there. I got help from a friend with more
415 JavaScript knowledge than me to modify the code to provide a GUI
416 button instead. This mean that to get started you just need to run
417 the wrapper and click the &#39;Register without mobile phone&#39; to get going
418 now. I&#39;ve also modified the timeout code to always set it to 90 days
419 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
420
421 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
422
423 &lt;ol&gt;
424
425 &lt;li&gt;First, install required packages to get the source code and the
426 browser you need. Signal only work with Chrome/Chromium, as far as I
427 know, so you need to install it.
428
429 &lt;pre&gt;
430 apt install git tor chromium
431 git clone https://github.com/WhisperSystems/Signal-Desktop.git
432 &lt;/pre&gt;&lt;/li&gt;
433
434 &lt;li&gt;Modify the source code using command listed in the the patch
435 block below.&lt;/li&gt;
436
437 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
438 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
439
440 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
441 number you can receive calls to the next minute, receive the
442 verification code and enter it into the form field and press
443 &#39;Register&#39;. Note, the phone number you use will be user Signal
444 username, ie the way others can find you on Signal.&lt;/li&gt;
445
446 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
447 not show up in the contact list until you restart Signal, and there is
448 no way to assign names to Contacts. There is also no way to create or
449 update chat groups. I suspect this is because the web app do not have
450 a associated contact database.&lt;/li&gt;
451
452 &lt;/ol&gt;
453
454 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
455 main author moxie0 reject federation and accept dependencies to major
456 corporations like Google (part of the code is fetched from Google) and
457 Amazon (the central coordination point is owned by Amazon). See for
458 example
459 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
460 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
461 view on these issues. But the network effect is strong in this case,
462 and several of the people I want to communicate with already use
463 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
464 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
465 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
466 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
467 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
468 working on Debian Stable.&lt;/p&gt;
469
470 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
471 working. It switch to the production servers, disable to timeout,
472 make registration easier and add the shell wrapper:&lt;/p&gt;
473
474 &lt;pre&gt;
475 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
476 diff --git a/js/background.js b/js/background.js
477 index 24b4c1d..579345f 100644
478 --- a/js/background.js
479 +++ b/js/background.js
480 @@ -33,9 +33,9 @@
481 });
482 });
483
484 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
485 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
486 var SERVER_PORTS = [80, 4433, 8443];
487 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
488 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
489 var messageReceiver;
490 window.getSocketStatus = function() {
491 if (messageReceiver) {
492 diff --git a/js/expire.js b/js/expire.js
493 index 639aeae..beb91c3 100644
494 --- a/js/expire.js
495 +++ b/js/expire.js
496 @@ -1,6 +1,6 @@
497 ;(function() {
498 &#39;use strict&#39;;
499 - var BUILD_EXPIRATION = 0;
500 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
501
502 window.extension = window.extension || {};
503
504 diff --git a/js/views/install_view.js b/js/views/install_view.js
505 index 7816f4f..1d6233b 100644
506 --- a/js/views/install_view.js
507 +++ b/js/views/install_view.js
508 @@ -38,7 +38,8 @@
509 return {
510 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
511 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
512 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
513 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
514 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
515 };
516 },
517 clearQR: function() {
518 diff --git a/options.html b/options.html
519 index dc0f28e..8d709f6 100644
520 --- a/options.html
521 +++ b/options.html
522 @@ -14,7 +14,10 @@
523 &amp;lt;div class=&#39;nav&#39;&gt;
524 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
525 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
526 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
527 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
528 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
529 +
530 + &amp;lt;/div&gt;
531 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
532 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
533 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
534 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
535 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
536 @@ -0,0 +1,12 @@
537 +#!/bin/sh
538 +set -e
539 +cd $(dirname $0)
540 +mkdir -p userdata
541 +userdata=&quot;`pwd`/userdata&quot;
542 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
543 + (cd $userdata &amp;&amp; git init)
544 +fi
545 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
546 +exec chromium \
547 + --proxy-server=&quot;socks://localhost:9050&quot; \
548 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
549 EOF
550 chmod a+rx run-signal-app
551 &lt;/pre&gt;
552
553 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
554 activities, please send Bitcoin donations to my address
555 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
556 </description>
557 </item>
558
559 <item>
560 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
561 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
562 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
563 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
564 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
565 system&lt;/a&gt; provide a practical and easy way to figure out which
566 packages support the hardware in a given machine. The command line
567 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
568 convenient way to list and install packages relevant for the current
569 hardware during system installation, both user space packages and
570 firmware packages. The GUI background daemon on the other hand provide
571 a pop-up proposing to install packages when a new dongle is inserted
572 while using the computer. For example, if you plug in a smart card
573 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
574 that package isn&#39;t already installed, and if you plug in a USB video
575 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
576 cheese is currently missing. This already work just fine.&lt;/p&gt;
577
578 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
579 package names. When I started no such database existed in Debian, so
580 I made my own data set and included it with the isenkram package and
581 made isenkram fetch the latest version of this database from git using
582 http. This way the isenkram users would get updated package proposals
583 as soon as I learned more about hardware related packages.&lt;/p&gt;
584
585 &lt;p&gt;The hardware is identified using modalias strings. The modalias
586 design is from the Linux kernel where most hardware descriptors are
587 made available as a strings that can be matched using filename style
588 globbing. It handle USB, PCI, DMI and a lot of other hardware related
589 identifiers.&lt;/p&gt;
590
591 &lt;p&gt;The downside to the Isenkram specific database is that there is no
592 information about relevant distribution / Debian version, making
593 isenkram propose obsolete packages too. But along came AppStream, a
594 cross distribution mechanism to store and collect metadata about
595 software packages. When I heard about the proposal, I contacted the
596 people involved and suggested to add a hardware matching rule using
597 modalias strings in the specification, to be able to use AppStream for
598 mapping hardware to packages. This idea was accepted and AppStream is
599 now a great way for a package to announce the hardware it support in a
600 distribution neutral way. I wrote
601 &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
602 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
603 December. If you have a hardware related package in Debian, please
604 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
605
606 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
607 RCX or NXT unit, announce this support using AppStream. The effect is
608 that when you insert such LEGO robot controller into your Debian
609 machine, Isenkram will propose to install the packages needed to get
610 it working. The intention is that this should allow the local user to
611 start programming his robot controller right away without having to
612 guess what packages to use or which permissions to fix.&lt;/p&gt;
613
614 &lt;p&gt;But when I sat down with my son the other day to program our NXT
615 unit using his Debian Stretch computer, I discovered something
616 annoying. The local console user (ie my son) did not get access to
617 the USB device for programming the unit. This used to work, but no
618 longer in Jessie and Stretch. After some investigation and asking
619 around on #debian-devel, I discovered that this was because udev had
620 changed the mechanism used to grant access to local devices. The
621 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
622 no longer applied, because LDAP users no longer was added to the
623 plugdev group during login. Michael Biebl told me that this method
624 was obsolete and the new method used ACLs instead. This was good
625 news, as the plugdev mechanism is a mess when using a remote user
626 directory like LDAP. Using ACLs would make sure a user lost device
627 access when she logged out, even if the user left behind a background
628 process which would retain the plugdev membership with the ConsoleKit
629 setup. Armed with this knowledge I moved on to fix the access problem
630 for the LEGO Mindstorms related packages.&lt;/p&gt;
631
632 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
633 applied directly for a device, or is applied in
634 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
635 LEGO Mindstorms udev rules did not have a class, I decided to add the
636 tag directly in the udev rules files included in the packages. Here
637 is one example. For the nqc C compiler for the RCX, the
638 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
639
640 &lt;p&gt;&lt;pre&gt;
641 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
642 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
643 &lt;/pre&gt;&lt;/p&gt;
644
645 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
646 packages using plugdev in their /lib/udev/rules.d/ files should be
647 changed to use this tag (either directly or indirectly via
648 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
649 to detect this?&lt;/p&gt;
650
651 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
652 It is unclear to me if the uaccess tag is an internal implementation
653 detail like the udev-acl tag used by
654 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
655 indirect method is the preferred way. Michael
656 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
657 documentation from the systemd project&lt;/a&gt; and I hope it will make
658 this clearer. For now I use the generic classes when they exist and
659 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
660 directly if no such class exist.&lt;/p&gt;
661
662 &lt;p&gt;To learn more about the isenkram system, please check out
663 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
664 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
665
666 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
667 please join us on our IRC channel
668 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
669 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
670 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
671 list is not yet created, but we are working on it. :)&lt;/p&gt;
672
673 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
674 activities, please send Bitcoin donations to my address
675 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
676 </description>
677 </item>
678
679 <item>
680 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
681 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
682 <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>
683 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
684 <description>&lt;p&gt;In April we
685 &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
686 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
687 how to set up and administrate a Debian system. Today I am happy to
688 report that the first draft is now publicly available. You can find
689 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
690 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
691 eight chapters have a first draft translation, and we are working on
692 proofreading the content. If you want to help out, please start
693 contributing using
694 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
695 hosted weblate project page&lt;/a&gt;, and get in touch using
696 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
697 translators mailing list&lt;/a&gt;. Please also check out
698 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
699 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
700 and update weblate if you find errors.&lt;/p&gt;
701
702 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
703 electronic form.&lt;/p&gt;
704 </description>
705 </item>
706
707 <item>
708 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
709 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
710 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
711 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
712 <description>&lt;p&gt;This summer, I read a great article
713 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
714 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
715 how to profile multi-threaded programs. It presented a system for
716 profiling software by running experiences in the running program,
717 testing how run time performance is affected by &quot;speeding up&quot; parts of
718 the code to various degrees compared to a normal run. It does this by
719 slowing down parallel threads while the &quot;faster up&quot; code is running
720 and measure how this affect processing time. The processing time is
721 measured using probes inserted into the code, either using progress
722 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
723 can also measure unmodified code by measuring complete the program
724 runtime and running the program several times instead.&lt;/p&gt;
725
726 &lt;p&gt;The project and presentation was so inspiring that I would like to
727 get the system into Debian. I
728 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
729 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
730 system ready for Debian by sending patches. The build process need to
731 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
732 to include the JavaScript web page used to visualize the collected
733 profiling information included in the source package.
734 But I expect that should work out fairly soon.&lt;/p&gt;
735
736 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
737 on a binary with debug symbols available, start the program like this:
738
739 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
740 coz run --- program-to-run
741 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
742
743 &lt;p&gt;This will create a text file profile.coz with the instrumentation
744 information. To show what part of the code affect the performance
745 most, use a web browser and either point it to
746 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
747 or use the copy from git (in the gh-pages branch). Check out this web
748 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
749 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
750 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
751 code, rebuild and run the profiler. This allow coz to do more
752 targeted experiments.&lt;/p&gt;
753
754 &lt;p&gt;A video published by ACM
755 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
756 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
757 from the 25th Symposium on Operating Systems Principles available
758 titled
759 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
760 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
761
762 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
763 for Coz is available from github. It will only build with clang
764 because it uses a
765 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
766 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
767 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
768 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
769
770 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
771 of software in Debian. I would very much like some help with the
772 packaging effort, as I lack the in depth knowledge on how to package
773 C++ libraries.&lt;/p&gt;
774 </description>
775 </item>
776
777 <item>
778 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
779 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
780 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
781 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
782 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
783 to be a slight challenge. Here is the recipe if I ever need to do it
784 again. It all started by me wanting to try the recipe to set up
785 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
786 hardened Android installation&lt;/a&gt; from the Tor project blog on a
787 device I had access to. It is a old mobile phone with a broken
788 microphone The initial idea had been to just
789 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
790 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
791 until a few days ago.&lt;/p&gt;
792
793 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
794 loader (press volume down and power at the same time), (2) select
795 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
796 machine, (4) request the device identifier token by running &#39;fastboot
797 oem get_identifier_token&#39;, (5) request the device unlocking key using
798 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
799 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
800
801 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
802 or newer, and the device I was working on had 2.00.0027. This
803 apparently can be easily fixed by downloading a Windows program and
804 running it on your Windows machine, if you accept the terms Microsoft
805 require you to accept to use Windows - which I do not. So I had to
806 come up with a different approach. I got a lot of help from AndyCap
807 on #nuug, and would not have been able to get this working without
808 him.&lt;/p&gt;
809
810 &lt;p&gt;First I needed to extract the hboot firmware from
811 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
812 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
813 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
814 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
815 recognise the file format, but unruu worked and extracted rom.zip,
816 containing the new hboot firmware and a text file describing which
817 devices it would work for.&lt;/p&gt;
818
819 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
820 followed some instructions
821 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
822 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
823 machine with Debian testing:&lt;/p&gt;
824
825 &lt;p&gt;&lt;pre&gt;
826 adb reboot-bootloader
827 fastboot oem rebootRUU
828 fastboot flash zip rom.zip
829 fastboot flash zip rom.zip
830 fastboot reboot
831 &lt;/pre&gt;&lt;/p&gt;
832
833 &lt;p&gt;The flash command apparently need to be done twice to take effect,
834 as the first is just preparations and the second one do the flashing.
835 The adb command is just to get to the boot loader menu, so turning the
836 device on while holding volume down and the power button should work
837 too.&lt;/p&gt;
838
839 &lt;p&gt;With the new hboot version in place I could start following the
840 instructions on the HTC developer web site. I got the device token
841 like this:&lt;/p&gt;
842
843 &lt;p&gt;&lt;pre&gt;
844 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
845 &lt;/pre&gt;
846
847 &lt;p&gt;And once I got the unlock code via email, I could use it like
848 this:&lt;/p&gt;
849
850 &lt;p&gt;&lt;pre&gt;
851 fastboot flash unlocktoken Unlock_code.bin
852 &lt;/pre&gt;&lt;/p&gt;
853
854 &lt;p&gt;And with that final step in place, the phone was unlocked and I
855 could start stuffing the software of my own choosing into the device.
856 So far I only inserted a replacement recovery image to wipe the phone
857 before I start. We will see what happen next. Perhaps I should
858 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
859 </description>
860 </item>
861
862 <item>
863 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
864 <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>
865 <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>
866 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
867 <description>&lt;p&gt;For a while now, I have wanted to test
868 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
869 said to provide end to end encrypted communication and several of my
870 friends and family are already using it. As I by choice do not own a
871 mobile phone, this proved to be harder than expected. And I wanted to
872 have the source of the client and know that it was the code used on my
873 machine. But yesterday I managed to get it working. I used the
874 Github source, compared it to the source in
875 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
876 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
877 patches to use the production Signal servers, started the app and
878 asked for the hidden &quot;register without a smart phone&quot; form. Here is
879 the recipe how I did it.&lt;/p&gt;
880
881 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
882
883 &lt;pre&gt;
884 git clone https://github.com/WhisperSystems/Signal-Desktop.git
885 &lt;/pre&gt;
886
887 &lt;p&gt;Next, I patched the source to use the production servers, to be
888 able to talk to other Signal users:&lt;/p&gt;
889
890 &lt;pre&gt;
891 cat &amp;lt;&amp;lt;EOF | patch -p0
892 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
893 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
894 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
895 @@ -47,8 +47,8 @@
896 });
897 });
898
899 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
900 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
901 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
902 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
903 var messageReceiver;
904 window.getSocketStatus = function() {
905 if (messageReceiver) {
906 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
907 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
908 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
909 @@ -1,6 +1,6 @@
910 ;(function() {
911 &#39;use strict&#39;;
912 - var BUILD_EXPIRATION = 0;
913 + var BUILD_EXPIRATION = 1474492690000;
914
915 window.extension = window.extension || {};
916
917 EOF
918 &lt;/pre&gt;
919
920 &lt;p&gt;The first part is changing the servers, and the second is updating
921 an expiration timestamp. This timestamp need to be updated regularly.
922 It is set 90 days in the future by the build process (Gruntfile.js).
923 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
924
925 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
926 script to launch Signal in Chromium.&lt;/p&gt;
927
928 &lt;pre&gt;
929 #!/bin/sh
930 cd $(dirname $0)
931 mkdir -p userdata
932 exec chromium \
933 --proxy-server=&quot;socks://localhost:9050&quot; \
934 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
935 &lt;/pre&gt;
936
937 &lt;p&gt; The script start the app and configure Chromium to use the Tor
938 SOCKS5 proxy to make sure those controlling the Signal servers (today
939 Amazon and Whisper Systems) as well as those listening on the lines
940 will have a harder time location my laptop based on the Signal
941 connections if they use source IP address.&lt;/p&gt;
942
943 &lt;p&gt;When the script starts, one need to follow the instructions under
944 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
945 repository. I right clicked on the Signal window to get up the
946 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
947 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
948 registration form. Then I entered by land line phone number and
949 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
950 repeated the verification code three times. After entering the number
951 into the verification code field in the form, I could start using
952 Signal from my laptop.
953
954 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
955 whom and thus who know who to those controlling the central server,
956 but such leakage is hard to avoid with a centrally controlled server
957 setup. It is something to keep in mind when using Signal - the
958 content of your chats are harder to intercept, but the meta data
959 exposing your contact network is available to people you do not know.
960 So better than many options, but not great. And sadly the usage is
961 connected to my land line, thus allowing those controlling the server
962 to associate it to my home and person. I would prefer it if only
963 those I knew could tell who I was on Signal. There are options
964 avoiding such information leakage, but most of my friends are not
965 using them, so I am stuck with Signal for now.&lt;/p&gt;
966 </description>
967 </item>
968
969 <item>
970 <title>The new &quot;best&quot; multimedia player in Debian?</title>
971 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
972 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
973 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
974 <description>&lt;p&gt;When I set out a few weeks ago to figure out
975 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
976 multimedia player in Debian claimed to support most file formats /
977 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
978 the various players claimed support for. The range was from 55 to 130
979 MIME types. I suspect most media formats are supported by all
980 players, but this is not really reflected in the MimeTypes values in
981 their desktop files. There are probably also some bogus MIME types
982 listed, but it is hard to identify which one this is.&lt;/p&gt;
983
984 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
985 the players suggesting to add more MIME types to their desktop files,
986 and decided to spend some time myself improving the situation for my
987 favorite media player VLC. The fixes for VLC entered Debian unstable
988 yesterday. The complete list of MIME types can be seen on the
989 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
990 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
991
992 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
993 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
994 kmplayer. I am sure some of the other players desktop files support
995 several of the formats currently listed as working only with vlc,
996 toten and parole.&lt;/p&gt;
997
998 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
999 supported by all the tested multimedia players in Debian in their
1000 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1001 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1002 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1003 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1004 it sad that video/ogg and video/webm is not supported by all the media
1005 players in Debian. As far as I can tell, all of them can handle both
1006 formats.&lt;/p&gt;
1007 </description>
1008 </item>
1009
1010 <item>
1011 <title>A program should be able to open its own files on Linux</title>
1012 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1014 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1015 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1016 decided to test its presentation tool when making the slides for a
1017 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1018 wrote the first draft of the slides, saved the result and went to bed
1019 the day before I would give the talk. The next day I took a plane to
1020 the location where the meeting should take place, and on the plane I
1021 started up koffice again to polish the talk a bit, only to discover
1022 that kpresenter refused to load its own data file. I cursed a bit and
1023 started making the slides again from memory, to have something to
1024 present when I arrived. I tested that the saved files could be
1025 loaded, and the day seemed to be rescued. I continued to polish the
1026 slides until I suddenly discovered that the saved file could no longer
1027 be loaded into kpresenter. In the end I had to rewrite the slides
1028 three times, condensing the content until the talk became shorter and
1029 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1030 kpresenter wrote inline images in a way itself could not understand.
1031 Eventually that bug was fixed and kpresenter ended up being a great
1032 program to make slides. The point I&#39;m trying to make is that we
1033 expect a program to be able to load its own data files, and it is
1034 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1035
1036 &lt;p&gt;Did you ever experience a program failing to load its own data
1037 files from the desktop file browser? It is not a uncommon problem. A
1038 while back I discovered that the screencast recorder
1039 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1040 browser would refuse to open. No video player claimed to understand
1041 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1042 returning the application/ogg MIME type, which no video player I had
1043 installed listed as a MIME type they would understand. I asked for
1044 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1045 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1046 several video players to add video/ogg to their desktop files, to give
1047 the file browser an idea what to do about Ogg Theora files. After a
1048 while, the desktop file browsers in Debian started to handle the
1049 output from gtk-recordmydesktop properly.&lt;/p&gt;
1050
1051 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1052 system Rosegarden again, and I discovered that the KDE and xfce file
1053 browsers did not know what to do with the Rosegarden project files
1054 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1055 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1056 included in the next upload. To increase the chance of me remembering
1057 how to fix the problem next time some program fail to load its files
1058 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1059
1060 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1061 There are two sources for the MIME type of a given file. The output from
1062 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1063 shared MIME type registry (under /usr/share/mime/). The file MIME
1064 type is mapped to programs supporting the MIME type, and this
1065 information is collected from
1066 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1067 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1068 one desktop file claiming support for the MIME type of the file, it is
1069 activated when asking to open a given file. If there are more, one
1070 can normally select which one to use by right-clicking on the file and
1071 selecting the wanted one using &#39;Open with&#39; or similar. In general
1072 this work well. But it depend on each program picking a good MIME
1073 type (preferably
1074 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1075 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1076 registry recognizing the file and the desktop file to list the MIME
1077 type in its list of supported MIME types.&lt;/p&gt;
1078
1079 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1080 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1081 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1082
1083 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1084 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1085 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1086 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1087 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1088 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1089 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1090 &amp;lt;/mime-type&amp;gt;
1091 &amp;lt;/mime-info&amp;gt;
1092 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1093
1094 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1095 (it is a gzipped XML file). Note, it is much better to use an
1096 official MIME type registered with IANA than it is to make up ones own
1097 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1098
1099 &lt;p&gt;The desktop file of the rosegarden program failed to list
1100 audio/x-rosegarden in its list of supported MIME types, causing the
1101 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1102
1103 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1104 % grep Mime /usr/share/applications/rosegarden.desktop
1105 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1106 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1107 %
1108 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1109
1110 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
1111 MimeType= line.&lt;/p&gt;
1112
1113 &lt;p&gt;If you run into a file which fail to open the correct program when
1114 selected from the file browser, please check out the output from
1115 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
1116 MIME type is registered somewhere under /usr/share/mime/ and check
1117 that some desktop file under /usr/share/applications/ is claiming
1118 support for this MIME type. If not, please report a bug to have it
1119 fixed. :)&lt;/p&gt;
1120 </description>
1121 </item>
1122
1123 <item>
1124 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
1125 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
1126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
1127 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
1128 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
1129 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
1130 related packages. The idea is to have a database of mappings between
1131 hardware and packages, and pop up a dialog suggesting for the user to
1132 install the packages to use a given hardware dongle. Some use cases
1133 are when you insert a Yubikey, it proposes to install the software
1134 needed to control it; when you insert a braille reader list it
1135 proposes to install the packages needed to send text to the reader;
1136 and when you insert a ColorHug screen calibrator it suggests to
1137 install the driver for it. The system work well, and even have a few
1138 command line tools to install firmware packages and packages for the
1139 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
1140
1141 &lt;p&gt;The system was initially written using aptdaemon, because I found
1142 good documentation and example code on how to use it. But aptdaemon
1143 is going away and is generally being replaced by
1144 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
1145 so Isenkram needed a rewrite. And today, thanks to the great patch
1146 from my college Sunil Mohan Adapa in the FreedomBox project, the
1147 rewrite finally took place. I&#39;ve just uploaded a new version of
1148 Isenkram into Debian Unstable with the patch included, and the default
1149 for the background daemon is now to use PackageKit. To check it out,
1150 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
1151 and see if it is recognised.&lt;/p&gt;
1152
1153 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
1154 the machine it is running on, you can check out the isenkram-lookup
1155 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
1156
1157 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1158 % isenkram-lookup
1159 bluez
1160 cheese
1161 fprintd
1162 fprintd-demo
1163 gkrellm-thinkbat
1164 hdapsd
1165 libpam-fprintd
1166 pidgin-blinklight
1167 thinkfan
1168 tleds
1169 tp-smapi-dkms
1170 tp-smapi-source
1171 tpb
1172 %p
1173 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1174
1175 &lt;p&gt;The hardware mappings come from several places. The preferred way
1176 is for packages to announce their hardware support using
1177 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1178 cross distribution appstream system&lt;/a&gt;.
1179 See
1180 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
1181 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
1182 </description>
1183 </item>
1184
1185 <item>
1186 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
1187 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
1188 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
1189 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
1190 <description>&lt;p&gt;Yesterday I updated the
1191 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
1192 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
1193 enterprising users. There were some nice user and visible changes.
1194 First of all, both desktop menu entries now work. A design flaw in
1195 one of the script made the history graph fail to show up (its PNG was
1196 dumped in ~/.xsession-errors) if no controlling TTY was available.
1197 The script worked when called from the command line, but not when
1198 called from the desktop menu. I changed this to look for a DISPLAY
1199 variable or a TTY before deciding where to draw the graph, and now the
1200 graph window pop up as expected.&lt;/p&gt;
1201
1202 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
1203 graphs (the one showing the last few hours). New is also the user of
1204 colours showing charging in blue and discharge in red. The percentages
1205 of this graph is relative to last full charge, not battery design
1206 capacity.&lt;/p&gt;
1207
1208 &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;
1209
1210 &lt;p&gt;The other graph show the entire history of the collected battery
1211 statistics, comparing it to the design capacity of the battery to
1212 visualise how the battery life time get shorter over time. The red
1213 line in this graph is what the previous graph considers 100 percent:
1214
1215 &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;
1216
1217 &lt;p&gt;In this graph you can see that I only charge the battery to 80
1218 percent of last full capacity, and how the capacity of the battery is
1219 shrinking. :(&lt;/p&gt;
1220
1221 &lt;p&gt;The last new feature is in the collector, which now will handle
1222 more hardware models. On some hardware, Linux power supply
1223 information is stored in /sys/class/power_supply/ACAD/, while the
1224 collector previously only looked in /sys/class/power_supply/AC/. Now
1225 both are checked to figure if there is power connected to the
1226 machine.&lt;/p&gt;
1227
1228 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1229 check out the
1230 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1231 in Debian unstable, or rebuild it on Jessie to get it working on
1232 Debian stable. :) The upstream source is available from &lt;a
1233 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1234 Patches are very welcome.&lt;/p&gt;
1235
1236 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1237 activities, please send Bitcoin donations to my address
1238 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1239 </description>
1240 </item>
1241
1242 <item>
1243 <title>Debian now with ZFS on Linux included</title>
1244 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
1245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
1246 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
1247 <description>&lt;p&gt;Today, after many years of hard work from many people,
1248 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
1249 Debian. The package status can be seen on
1250 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
1251 for zfs-linux&lt;/a&gt;. and
1252 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1253 team status page&lt;/a&gt;. If you want to help out, please join us.
1254 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
1255 source code&lt;/a&gt; is available via git on Alioth. It would also be
1256 great if you could help out with
1257 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
1258 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
1259 </description>
1260 </item>
1261
1262 <item>
1263 <title>What is the best multimedia player in Debian?</title>
1264 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
1265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
1266 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
1267 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
1268 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
1269
1270 &lt;p&gt;A few years ago, I had a look at the media support for Browser
1271 plugins in Debian, to get an idea which plugins to include in Debian
1272 Edu. I created a script to extract the set of supported MIME types
1273 for each plugin, and used this to find out which multimedia browser
1274 plugin supported most file formats / media types.
1275 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
1276 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
1277 not been updated for a while. But browser plugins are less relevant
1278 these days, so I thought it was time to look at standalone
1279 players.&lt;/p&gt;
1280
1281 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
1282 player when I wanted to play videos from the Norwegian National
1283 Broadcasting Company, and decided to investigate why. The cause is a
1284 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
1285 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
1286 of MIME types announced in the desktop file and the browser plugin,
1287 only to discover that there is quite a large difference between the
1288 two for VLC. This discovery made me dig up the script I used to
1289 compare browser plugins, and adjust it to compare desktop files
1290 instead, to try to figure out which multimedia player in Debian
1291 support most file formats.&lt;/p&gt;
1292
1293 &lt;p&gt;The result can be seen on the Debian Wiki, as
1294 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
1295 table listing all MIME types supported by one of the packages included
1296 in the table&lt;/a&gt;, with the package supporting most MIME types being
1297 listed first in the table.&lt;/p&gt;
1298
1299 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
1300 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1301 kmplayer. Time for the other players to update their announced MIME
1302 support?&lt;/p&gt;
1303 </description>
1304 </item>
1305
1306 <item>
1307 <title>The Pyra - handheld computer with Debian preinstalled</title>
1308 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1310 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1311 <description>A friend of mine made me aware of
1312 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1313 handheld computer which will be delivered with Debian preinstalled. I
1314 would love to get one of those for my birthday. :)&lt;/p&gt;
1315
1316 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1317 plugs and many others connectors, and include a full keyboard and a 5&quot;
1318 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1319 day of battery life time, but I have not seen any independent tests
1320 confirming this. The vendor is still collecting preorders, and the
1321 last I heard last night was that 22 more orders were needed before
1322 production started.&lt;/p&gt;
1323
1324 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1325 Debian. Please let me know if you know of any others. Is it the
1326 first computer being sold with Debian preinstalled?&lt;/p&gt;
1327 </description>
1328 </item>
1329
1330 <item>
1331 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1332 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1334 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1335 <description>&lt;p&gt;During this weekends
1336 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1337 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1338 to make sure there are good books about Debian available in Norwegian
1339 Bokmål, and got in touch with the people behind the
1340 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1341 project&lt;/a&gt; to get started. If you want to help out, please start
1342 contributing using
1343 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1344 hosted weblate project page&lt;/a&gt;, and get in touch using
1345 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1346 translators mailing list&lt;/a&gt;. Please also check out
1347 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1348 contributors&lt;/a&gt;.&lt;/p&gt;
1349
1350 &lt;p&gt;The book is already available on paper in English, French and
1351 Japanese, and our goal is to get it available on paper in Norwegian
1352 Bokmål too. In addition to the paper edition, there are also EPUB and
1353 Mobi versions available. And there are incomplete translations
1354 available for many more languages.&lt;/p&gt;
1355 </description>
1356 </item>
1357
1358 <item>
1359 <title>One in two hundred Debian users using ZFS on Linux?</title>
1360 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1361 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1362 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1363 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1364 packages in Debian, and was quite surprised with what I found. I use
1365 ZFS myself at home, but did not really expect many others to do so.
1366 But I might be wrong.&lt;/p&gt;
1367
1368 &lt;p&gt;According to
1369 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1370 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1371 0.53% of the population, with the package installed. As far as I know
1372 the only use of the spl-linux package is as a support library for ZFS
1373 on Linux, so I use it here as proxy for measuring the number of ZFS
1374 installation on Linux in Debian. In the kFreeBSD variant of Debian
1375 the ZFS feature is already available, and there
1376 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1377 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1378 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1379
1380 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1381 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1382 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1383 cleared, the package is still not in Debian. The package is again in
1384 the NEW queue. Several uploads have been rejected so far because the
1385 debian/copyright file was incomplete or wrong, but there is no reason
1386 to give up. The current status can be seen on
1387 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1388 team status page&lt;/a&gt;, and
1389 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1390 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1391
1392 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1393 my home server can function in the future using only official Debian
1394 packages, and the current blocker is to get the debian/copyright file
1395 accepted by the FTP masters in Debian, I decided a while back to try
1396 to help out the team. This was the background for my blog post about
1397 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1398 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1399 used the techniques I explored there to try to find any errors in the
1400 copyright file. It is not very easy to check every one of the around
1401 2000 files in the source package, but I hope we this time got it
1402 right. If you want to help out, check out the git source and try to
1403 find missing entries in the debian/copyright file.&lt;/p&gt;
1404 </description>
1405 </item>
1406
1407 <item>
1408 <title>Full battery stats collector is now available in Debian</title>
1409 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1410 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1411 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1412 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1413 extended collector that will collect the complete battery history for
1414 later processing and graphing. The original collector store the
1415 battery level as percentage of last full level, while the new
1416 collector also record battery vendor, model, serial number, design
1417 full level, last full level and current battery level. This make it
1418 possible to predict the lifetime of the battery as well as visualise
1419 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1420
1421 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1422 in the version 0.5.1 package in unstable. Get the new battery level graph
1423 and lifetime prediction by running:
1424
1425 &lt;p&gt;&lt;pre&gt;
1426 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1427 &lt;/pre&gt;&lt;/p&gt;
1428
1429 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1430
1431 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1432 entry yet):&lt;/p&gt;
1433
1434 &lt;p&gt;&lt;pre&gt;
1435 /usr/share/battery-stats/battery-stats-graph-flow
1436 &lt;/pre&gt;&lt;/p&gt;
1437
1438 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1439 when there are few data points. The graphs look a bit better with a
1440 few years of data.&lt;/p&gt;
1441
1442 &lt;p&gt;A while back one important feature I use in the battery stats
1443 collector broke in Debian. The scripts in
1444 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1445 suspect it happened when Jessie started using systemd, but I do not
1446 know. The issue is reported as
1447 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1448 pm-utils. I managed to work around it by adding an udev rule to call
1449 the collector script every time the power connector is connected and
1450 disconnected. With this fix in place it was finally time to make a
1451 new release of the package, and get it into Debian.&lt;/p&gt;
1452
1453 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1454 check out the
1455 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1456 in Debian unstable, or rebuild it on Jessie to get it working on
1457 Debian stable. :) The upstream source is available from
1458 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1459 As always, patches are very welcome.&lt;/p&gt;
1460 </description>
1461 </item>
1462
1463 <item>
1464 <title>Making battery measurements a little easier in Debian</title>
1465 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1467 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1468 <description>&lt;p&gt;Back in September, I blogged about
1469 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1470 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1471 how it showed the decay and death of this battery (now replaced). I
1472 created a simple deb package to handle the collection and graphing,
1473 but did not want to upload it to Debian as there were already
1474 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1475 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1476 a point of uploading a competing package when battery-stats could be
1477 fixed instead. I reported a few bugs about its non-function, and
1478 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1479
1480 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1481 hands. The end result is that I am now the new upstream developer of
1482 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
1483 battery-stats in Debian, and the package in Debian unstable is finally
1484 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1485 information provided by the Linux kernel. If you install the
1486 battery-stats package from unstable now, you will be able to get a
1487 graph of the current battery fill level, to get some idea about the
1488 status of the battery. The source package build and work just fine in
1489 Debian testing and stable (and probably oldstable too, but I have not
1490 tested). The default graph you get for that system look like this:&lt;/p&gt;
1491
1492 &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;
1493
1494 &lt;p&gt;My plans for the future is to merge my old scripts into the
1495 battery-stats package, as my old scripts collected a lot more details
1496 about the battery. The scripts are merged into the upstream
1497 battery-stats git repository already, but I am not convinced they work
1498 yet, as I changed a lot of paths along the way. Will have to test a
1499 bit more before I make a new release.&lt;/p&gt;
1500
1501 &lt;p&gt;I will also consider changing the file format slightly, as I
1502 suspect the way I combine several values into one field might make it
1503 impossible to know the type of the value when using it for processing
1504 and graphing.&lt;/p&gt;
1505
1506 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1507 battery, check out the battery-stats package in
1508 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1509 on
1510 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1511 I would love some help to improve the system further.&lt;/p&gt;
1512 </description>
1513 </item>
1514
1515 <item>
1516 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1517 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1518 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1519 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1520 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1521 details. And one of the details is the content of the
1522 debian/copyright file, which should list all relevant licenses used by
1523 the code in the package in question, preferably in
1524 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1525 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1526
1527 &lt;p&gt;For large packages with lots of contributors it is hard to write
1528 and update this file manually, and if you get some detail wrong, the
1529 package is normally rejected by the ftpmasters. So getting it right
1530 the first time around get the package into Debian faster, and save
1531 both you and the ftpmasters some work.. Today, while trying to figure
1532 out what was wrong with
1533 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1534 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
1535 figuring out the options for doing this job automatically, or at least
1536 semi-automatically.&lt;/p&gt;
1537
1538 &lt;p&gt;Lucikly, there are at least two tools available for generating the
1539 file based on the code in the source package,
1540 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
1541 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
1542 not sure which one of them came first, but both seem to be able to
1543 create a sensible draft file. As far as I can tell, none of them can
1544 be trusted to get the result just right, so the content need to be
1545 polished a bit before the file is OK to upload. I found the debmake
1546 option in
1547 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
1548 blog posts from 2014&lt;/a&gt;.
1549
1550 &lt;p&gt;To generate using debmake, use the -cc option:
1551
1552 &lt;p&gt;&lt;pre&gt;
1553 debmake -cc &gt; debian/copyright
1554 &lt;/pre&gt;&lt;/p&gt;
1555
1556 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
1557 this might not be the best option.&lt;/p&gt;
1558
1559 &lt;p&gt;The cme option is based on a config parsing library, and I found
1560 this approach in
1561 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
1562 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
1563 dpkg-copyright&#39; option:
1564
1565 &lt;p&gt;&lt;pre&gt;
1566 cme update dpkg-copyright
1567 &lt;/pre&gt;&lt;/p&gt;
1568
1569 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
1570 handle UTF-8 names better than debmake.&lt;/p&gt;
1571
1572 &lt;p&gt;When the copyright file is created, I would also like some help to
1573 check if the file is correct. For this I found two good options,
1574 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
1575 to focus on license types and file matching, and is able to detect
1576 ineffective blocks in the copyright file. The latter reports missing
1577 copyright holders and years, but was confused by inconsistent license
1578 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
1579 fix all issues reported by them before uploading. But I do not know
1580 if the tools and the ftpmasters agree on what is important to fix in a
1581 copyright file, so the package might still be rejected.&lt;/p&gt;
1582
1583 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
1584 will read through the source and try to find all copyright statements.
1585 It is not comparing the result to the content of debian/copyright, but
1586 can be useful when verifying the content of the copyright file.&lt;/p&gt;
1587
1588 &lt;p&gt;Are you aware of better tools in Debian to create and update
1589 debian/copyright file. Please let me know, or blog about it on
1590 planet.debian.org.&lt;/p&gt;
1591
1592 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1593 activities, please send Bitcoin donations to my address
1594 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1595
1596 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
1597 on how to use licensecheck and cdbs to create a draft copyright file
1598
1599 &lt;p&gt;&lt;pre&gt;
1600 licensecheck --copyright -r `find * -type f` | \
1601 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
1602 &lt;/pre&gt;&lt;/p&gt;
1603
1604 &lt;p&gt;He mentioned that he normally check the generated file into the
1605 version control system to make it easier to discover license and
1606 copyright changes in the upstream source. I will try to do the same
1607 with my packages in the future.&lt;/p&gt;
1608
1609 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
1610 against using -quiet for new users, so I removed it from the proposed
1611 command line.&lt;/p&gt;
1612 </description>
1613 </item>
1614
1615 <item>
1616 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
1617 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
1618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
1619 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
1620 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
1621 is taking shape in Debian, and one provided feature is a very
1622 convenient way to tell you which package to install to make a given
1623 firmware file available when the kernel is looking for it. This can
1624 be done using apt-file too, but that is for someone else to blog
1625 about. :)&lt;/p&gt;
1626
1627 &lt;p&gt;Here is a small recipe to find the package with a given firmware
1628 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
1629 picked from the set of firmware announced using appstream in Debian
1630 unstable. In general you would be looking for the firmware requested
1631 by the kernel during kernel module loading. To find the package
1632 providing the example file, do like this:&lt;/p&gt;
1633
1634 &lt;blockquote&gt;&lt;pre&gt;
1635 % apt install appstream
1636 [...]
1637 % apt update
1638 [...]
1639 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
1640 awk &#39;/Package:/ {print $2}&#39;
1641 firmware-qlogic
1642 %
1643 &lt;/pre&gt;&lt;/blockquote&gt;
1644
1645 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
1646 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
1647 a way appstream can use.&lt;/p&gt;
1648
1649 &lt;p&gt;This same approach can be used to find any package supporting a
1650 given MIME type. This is very useful when you get a file you do not
1651 know how to handle. First find the mime type using &lt;tt&gt;file
1652 --mime-type&lt;/tt&gt;, and next look up the package providing support for
1653 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1654 and you can find all packages handling this type like this:&lt;/p&gt;
1655
1656 &lt;blockquote&gt;&lt;pre&gt;
1657 % apt install appstream
1658 [...]
1659 % apt update
1660 [...]
1661 % appstreamcli what-provides mimetype image/svg+xml | \
1662 awk &#39;/Package:/ {print $2}&#39;
1663 bkchem
1664 phototonic
1665 inkscape
1666 shutter
1667 tetzle
1668 geeqie
1669 xia
1670 pinta
1671 gthumb
1672 karbon
1673 comix
1674 mirage
1675 viewnior
1676 postr
1677 ristretto
1678 kolourpaint4
1679 eog
1680 eom
1681 gimagereader
1682 midori
1683 %
1684 &lt;/pre&gt;&lt;/blockquote&gt;
1685
1686 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
1687 packages providing appstream metadata.&lt;/p&gt;
1688 </description>
1689 </item>
1690
1691 <item>
1692 <title>Creepy, visualise geotagged social media information - nice free software</title>
1693 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
1694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
1695 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
1696 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
1697 with the computerised radio beacon known as a mobile phone their
1698 position is tracked by the phone company and often stored for a long
1699 time (like every time a SMS is received or sent). And if their
1700 computerised radio beacon is capable of running programs (often called
1701 mobile apps) downloaded from the Internet, these programs are often
1702 also capable of tracking their location (if the app requested access
1703 during installation). And when these programs send out information to
1704 central collection points, the location is often included, unless
1705 extra care is taken to not send the location. The provided
1706 information is used by several entities, for good and bad (what is
1707 good and bad, depend on your point of view). What is certain, is that
1708 the private sphere and the right to free movement is challenged and
1709 perhaps even eradicated for those announcing their location this way,
1710 when they share their whereabouts with private and public
1711 entities.&lt;/p&gt;
1712
1713 &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;
1714
1715 &lt;p&gt;The phone company logs provide a register of locations to check out
1716 when one want to figure out what the tracked person was doing. It is
1717 unavailable for most of us, but provided to selected government
1718 officials, company staff, those illegally buying information from
1719 unfaithful servants and crackers stealing the information. But the
1720 public information can be collected and analysed, and a free software
1721 tool to do so is called
1722 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
1723 discovered it when I read
1724 &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
1725 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
1726 November 2014, and decided to check if it was available in Debian.
1727 The python program was in Debian, but
1728 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
1729 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
1730 uploaded a new version which did not work quite right, but did not
1731 have time to fix it then. This Christmas I decided to finally try to
1732 get Creepy operational in Debian. Now a fixed version is available in
1733 Debian unstable and testing, and almost all Debian specific patches
1734 are now included
1735 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
1736
1737 &lt;p&gt;The Creepy program visualises geolocation information fetched from
1738 Twitter, Instagram, Flickr and Google+, and allow one to get a
1739 complete picture of every social media message posted recently in a
1740 given area, or track the movement of a given individual across all
1741 these services. Earlier it was possible to use the search API of at
1742 least some of these services without identifying oneself, but these
1743 days it is impossible. This mean that to use Creepy, you need to
1744 configure it to log in as yourself on these services, and provide
1745 information to them about your search interests. This should be taken
1746 into account when using Creepy, as it will also share information
1747 about yourself with the services.&lt;/p&gt;
1748
1749 &lt;p&gt;The picture above show the twitter messages sent from (or at least
1750 geotagged with a position from) the city centre of Oslo, the capital
1751 of Norway. One useful way to use Creepy is to first look at
1752 information tagged with an area of interest, and next look at all the
1753 information provided by one or more individuals who was in the area.
1754 I tested it by checking out which celebrity provide their location in
1755 twitter messages by checkout out who sent twitter messages near a
1756 Norwegian TV station, and next could track their position over time,
1757 making it possible to locate their home and work place, among other
1758 things. A similar technique have been
1759 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
1760 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
1761 tool to discover lying governments, and a useful tool to help people
1762 understand the value of the private information they provide to the
1763 public.&lt;/p&gt;
1764
1765 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
1766 it depend on several python modules currently missing in Jessie (at
1767 least python-instagram, python-flickrapi and
1768 python-requests-toolbelt).&lt;/p&gt;
1769
1770 &lt;p&gt;(I have uploaded
1771 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
1772 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
1773 Creepy program in Debian.)&lt;/p&gt;
1774 </description>
1775 </item>
1776
1777 <item>
1778 <title>Always download Debian packages using Tor - the simple recipe</title>
1779 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
1780 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
1781 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
1782 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
1783 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
1784 that those listening on the Internet lines would have good reason to
1785 believe a computer have a given security hole&lt;/a&gt; if it download a
1786 security fix from a Debian mirror. This is a good reason to always
1787 use encrypted connections to the Debian mirror, to make sure those
1788 listening do not know which IP address to attack. In August, Richard
1789 Hartmann observed that encryption was not enough, when it was possible
1790 to interfere download size to security patches or the fact that
1791 download took place shortly after a security fix was released, and
1792 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
1793 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
1794 was not the first to propose this, as the
1795 &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;
1796 package by Tim Retout already existed to make it easy to convince apt
1797 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
1798 aware of that package when I read the blog post from Richard.&lt;/p&gt;
1799
1800 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
1801 sysadmins, and he set up a Tor hidden service on one of the central
1802 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1803 it possible to download packages directly between two tor nodes,
1804 making sure the network traffic always were encrypted.&lt;/p&gt;
1805
1806 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
1807 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
1808 urls with tor+http and tor+https, and using the hidden service instead
1809 of the official Debian mirror site. I recommend installing
1810 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
1811 done in /etc/.&lt;/p&gt;
1812
1813 &lt;blockquote&gt;&lt;pre&gt;
1814 apt install apt-transport-tor
1815 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
1816 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
1817 &lt;/pre&gt;&lt;/blockquote&gt;
1818
1819 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
1820 the sed commands for these too. The sed command is assuming your are
1821 using the ftp.debian.org Debian mirror. Adjust the command (or just
1822 edit the file manually) to match your mirror.&lt;/p&gt;
1823
1824 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
1825 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
1826 system, and do not work with these tor+http URLs. For
1827 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
1828 which need a recent apt version currently only in unstable. So if you
1829 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
1830
1831 &lt;p&gt;Another advantage from this change is that your machine will start
1832 using Tor regularly and at fairly random intervals (every time you
1833 update the package lists or upgrade or install a new package), thus
1834 masking other Tor traffic done from the same machine. Using Tor will
1835 become normal for the machine in question.&lt;/p&gt;
1836
1837 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
1838 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
1839 enabled. It would be great if it was the default on any Debian
1840 system.&lt;/p&gt;
1841 </description>
1842 </item>
1843
1844 <item>
1845 <title>OpenALPR, find car license plates in video streams - nice free software</title>
1846 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
1847 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
1848 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
1849 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
1850 call the car license plate numbers in those days. I would write the
1851 numbers down in my little book and compare notes with the other kids
1852 to see how many region codes we had seen and if we had seen some
1853 exotic or special region codes and numbers. It was a fun game to pass
1854 time, as we kids have plenty of it.&lt;/p&gt;
1855
1856 &lt;p&gt;A few days I came across
1857 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
1858 project&lt;/a&gt;, a free software project to automatically discover and
1859 report license plates in images and video streams, and provide the
1860 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
1861 such system for a while now, because I believe it is a bad idea that the
1862 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
1863 number plate recognition&lt;/a&gt; tool only is available in the hands of
1864 the powerful, and want it to be available also for the powerless to
1865 even the score when it comes to surveillance and sousveillance. I
1866 discovered the developer
1867 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
1868 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
1869 help him get it into shape to get the package uploaded into the Debian
1870 archive.&lt;/p&gt;
1871
1872 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
1873 it into Debian, where it currently
1874 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
1875 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
1876
1877 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
1878 for the common folks, ie those not running a large government
1879 surveillance system? Well, I plan to put it in a computer on my bike
1880 and in my car, tracking the cars nearby and allowing me to be notified
1881 when number plates on my watch list are discovered. Another use case
1882 was suggested by a friend of mine, who wanted to set it up at his home
1883 to open the car port automatically when it discovered the plate on his
1884 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1885 capable of placing his license plate number of a piece of cardboard to
1886 open his car port, men replied that it was always unlocked anyway. I
1887 guess for such use case it make sense. I am sure there are other use
1888 cases too, for those with imagination and a vision.&lt;/p&gt;
1889
1890 &lt;p&gt;If you want to build your own version of the Debian package, check
1891 out the upstream git source and symlink ./distros/debian to ./debian/
1892 before running &quot;debuild&quot; to build the source. Or wait a bit until the
1893 package show up in unstable.&lt;/p&gt;
1894 </description>
1895 </item>
1896
1897 <item>
1898 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
1899 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
1900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
1901 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
1902 <description>&lt;p&gt;Around three years ago, I created
1903 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
1904 system&lt;/a&gt; to get a more practical solution in Debian for handing
1905 hardware related packages. A GUI system in the isenkram package will
1906 present a pop-up dialog when some hardware dongle supported by
1907 relevant packages in Debian is inserted into the machine. The same
1908 lookup mechanism to detect packages is available as command line
1909 tools in the isenkram-cli package. In addition to mapping hardware,
1910 it will also map kernel firmware files to packages and make it easy to
1911 install needed firmware packages automatically. The key for this
1912 system to work is a good way to map hardware to packages, in other
1913 words, allow packages to announce what hardware they will work
1914 with.&lt;/p&gt;
1915
1916 &lt;p&gt;I started by providing data files in the isenkram source, and
1917 adding code to download the latest version of these data files at run
1918 time, to ensure every user had the most up to date mapping available.
1919 I also added support for storing the mapping in the Packages file in
1920 the apt repositories, but did not push this approach because while I
1921 was trying to figure out how to best store hardware/package mappings,
1922 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1923 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
1924 add the hardware mapping into that data set to be able to use
1925 appstream as a data source, and this was accepted at least for the
1926 Debian version of appstream.&lt;/p&gt;
1927
1928 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
1929 and today I uploaded a new version 0.20 of isenkram adding support for
1930 appstream as a data source for mapping hardware to packages. The only
1931 package so far using appstream to announce its hardware support is my
1932 pymissile package. I got help from Matthias Klumpp with figuring out
1933 how do add the required
1934 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
1935 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
1936 this content:&lt;/p&gt;
1937
1938 &lt;blockquote&gt;&lt;pre&gt;
1939 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1940 &amp;lt;component&amp;gt;
1941 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
1942 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
1943 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
1944 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
1945 &amp;lt;description&amp;gt;
1946 &amp;lt;p&amp;gt;
1947 Pymissile provides a curses interface to control an original
1948 Marks and Spencer / Striker USB Missile Launcher, as well as a
1949 motion control script to allow a webcamera to control the
1950 launcher.
1951 &amp;lt;/p&amp;gt;
1952 &amp;lt;/description&amp;gt;
1953 &amp;lt;provides&amp;gt;
1954 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
1955 &amp;lt;/provides&amp;gt;
1956 &amp;lt;/component&amp;gt;
1957 &lt;/pre&gt;&lt;/blockquote&gt;
1958
1959 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
1960 which is a glob style match rule for hardware specific strings
1961 (modalias strings) provided by the Linux kernel. In this case, it
1962 will map to all USB devices with vendor code 1130 and product code
1963 0202.&lt;/p&gt;
1964
1965 &lt;p&gt;Note, it is important that the license of all the metadata files
1966 are compatible to have permissions to aggregate them into archive wide
1967 appstream files. Matthias suggested to use MIT or BSD licenses for
1968 these files. A challenge is figuring out a good id for the data, as
1969 it is supposed to be globally unique and shared across distributions
1970 (in other words, best to coordinate with upstream what to use). But
1971 it can be changed later or, so we went with the package name as
1972 upstream for this project is dormant.&lt;/p&gt;
1973
1974 &lt;p&gt;To get the metadata file installed in the correct location for the
1975 mirror update scripts to pick it up and include its content the
1976 appstream data source, the file must be installed in the binary
1977 package under /usr/share/appdata/. I did this by adding the following
1978 line to debian/pymissile.install:&lt;/p&gt;
1979
1980 &lt;blockquote&gt;&lt;pre&gt;
1981 debian/pymissile.metainfo.xml usr/share/appdata
1982 &lt;/pre&gt;&lt;/blockquote&gt;
1983
1984 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
1985 all packages useful on the current computer automatically, and the GUI
1986 pop-up handler will propose to install the package not already
1987 installed if a hardware dongle is inserted into the machine in
1988 question.&lt;/p&gt;
1989
1990 &lt;p&gt;Details of the modalias field in appstream is available from the
1991 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
1992
1993 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
1994 try running this command on the command line:&lt;/p&gt;
1995
1996 &lt;blockquote&gt;&lt;pre&gt;
1997 cat $(find /sys/devices/|grep modalias)
1998 &lt;/pre&gt;&lt;/blockquote&gt;
1999
2000 &lt;p&gt;To learn more about the isenkram system, please check out
2001 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2002 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2003 </description>
2004 </item>
2005
2006 <item>
2007 <title>The GNU General Public License is not magic pixie dust</title>
2008 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2009 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2010 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2011 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2012 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2013 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2014 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2015 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2016
2017 &lt;blockquote&gt;
2018
2019 &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;
2020
2021 &lt;blockquote&gt;
2022 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2023
2024 The first step is to choose a
2025 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2026 code.&lt;br/&gt;
2027
2028 The next step is, when someone fails to follow that copyleft license,
2029 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2030
2031 and its a simple fact of our modern society that such type of
2032 work&lt;br/&gt;
2033
2034 is incredibly expensive to do and incredibly difficult to do.
2035 &lt;/blockquote&gt;
2036
2037 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2038 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2039 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2040 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2041
2042 &lt;p&gt;As the Debian Website
2043 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2044 &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;
2045 imply, public domain and permissively licensed software can lead to
2046 the production of more proprietary software as people discover useful
2047 software, extend it and or incorporate it into their hardware or
2048 software products. Copyleft licenses such as the GNU GPL were created
2049 to close off this avenue to the production of proprietary software but
2050 such licenses are not enough. With the ongoing adoption of Free
2051 Software by individuals and groups, inevitably the community&#39;s
2052 expectations of license compliance are violated, usually out of
2053 ignorance of the way Free Software works, but not always. As Karen
2054 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2055 Freedom&quot;&gt;FaiF&lt;/a&gt;
2056 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2057 copyleft is nothing if no-one is willing and able to stand up in court
2058 to protect it. The reality of today&#39;s world is that legal
2059 representation is expensive, difficult and time consuming. With
2060 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2061 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2062 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2063 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2064 of the Linux project, Debian and other groups against GPL violations.
2065 In March the SFC supported a
2066 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2067 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2068 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2069 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2070 kernel. Since then two of their sponsors pulled corporate funding and
2071 conferences
2072 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2073 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2074 less on corporate funding and more on the broad community of
2075 individuals who support Free Software and copyleft. So the SFC has
2076 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2077 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2078 a community of folks who stand up for copyleft and the GPL by
2079 supporting their work on promoting and supporting copyleft and Free
2080 Software.&lt;/p&gt;
2081
2082 &lt;p&gt;If you support Free Software,
2083 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2084 what the SFC do, agree with their
2085 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2086 principles&lt;/a&gt;, are happy about their
2087 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2088 work on a project that is an SFC
2089 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2090 just want to stand up for copyleft, please join
2091 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2092 Allan Webber&lt;/a&gt;,
2093 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2094 Smith&lt;/a&gt;,
2095 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2096 Bacon&lt;/a&gt;, myself and
2097 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2098 becoming a
2099 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2100 next week your donation will be
2101 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2102 by an anonymous donor. Please also consider asking your employer to
2103 match your donation or become a sponsor of SFC. Don&#39;t forget to
2104 spread the word about your support for SFC via email, your blog and or
2105 social media accounts.&lt;/p&gt;
2106
2107 &lt;/blockquote&gt;
2108
2109 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
2110 of Software Freedom Conservancy myself. Perhaps you should be a
2111 supporter too?&lt;/p&gt;
2112 </description>
2113 </item>
2114
2115 <item>
2116 <title>PGP key transition statement for key EE4E02F9</title>
2117 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
2118 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
2119 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
2120 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
2121 set it up properly. I wanted to generate it offline and have it
2122 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
2123 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
2124 time to sit down with an offline machine almost took forever. But
2125 finally I&#39;ve been able to complete the process, and have now moved
2126 from my old GPG key to a new GPG key. See
2127 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
2128 full transition statement, signed with both my old and new key&lt;/a&gt; for
2129 the details. This is my new key:&lt;/p&gt;
2130
2131 &lt;pre&gt;
2132 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]
2133 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
2134 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
2135 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
2136 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
2137 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
2138 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
2139 &lt;/pre&gt;
2140
2141 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
2142 my old key.&lt;/p&gt;
2143
2144 &lt;p&gt;If you signed my old key
2145 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
2146 I&#39;d very much appreciate a signature on my new key, details and
2147 instructions in the transition statement. I m happy to reciprocate if
2148 you have a similarly signed transition statement to present.&lt;/p&gt;
2149 </description>
2150 </item>
2151
2152 <item>
2153 <title>The life and death of a laptop battery</title>
2154 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
2155 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
2156 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
2157 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
2158 But this do not last. The last few laptops gave me a feeling that
2159 within a year, the life time is just a fraction of what it used to be,
2160 and it slowly become painful to use the laptop without power connected
2161 all the time. Because of this, when I got a new Thinkpad X230 laptop
2162 about two years ago, I decided to monitor its battery state to have
2163 more hard facts when the battery started to fail.&lt;/p&gt;
2164
2165 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
2166
2167 &lt;p&gt;First I tried to find a sensible Debian package to record the
2168 battery status, assuming that this must be a problem already handled
2169 by someone else. I found
2170 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
2171 which collects statistics from the battery, but it was completely
2172 broken. I sent a few suggestions to the maintainer, but decided to
2173 write my own collector as a shell script while I waited for feedback
2174 from him. Via
2175 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
2176 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
2177 discovered
2178 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
2179 available in Debian.&lt;/p&gt;
2180
2181 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
2182 battery stats ever since. Now my
2183 /var/log/hjemmenett-battery-status.log file contain around 115,000
2184 measurements, from the time the battery was working great until now,
2185 when it is unable to charge above 7% of original capacity. My
2186 collector shell script is quite simple and look like this:&lt;/p&gt;
2187
2188 &lt;pre&gt;
2189 #!/bin/sh
2190 # Inspired by
2191 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
2192 # See also
2193 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
2194 logfile=/var/log/hjemmenett-battery-status.log
2195
2196 files=&quot;manufacturer model_name technology serial_number \
2197 energy_full energy_full_design energy_now cycle_count status&quot;
2198
2199 if [ ! -e &quot;$logfile&quot; ] ; then
2200 (
2201 printf &quot;timestamp,&quot;
2202 for f in $files; do
2203 printf &quot;%s,&quot; $f
2204 done
2205 echo
2206 ) &gt; &quot;$logfile&quot;
2207 fi
2208
2209 log_battery() {
2210 # Print complete message in one echo call, to avoid race condition
2211 # when several log processes run in parallel.
2212 msg=$(printf &quot;%s,&quot; $(date +%s); \
2213 for f in $files; do \
2214 printf &quot;%s,&quot; $(cat $f); \
2215 done)
2216 echo &quot;$msg&quot;
2217 }
2218
2219 cd /sys/class/power_supply
2220
2221 for bat in BAT*; do
2222 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
2223 done
2224 &lt;/pre&gt;
2225
2226 &lt;p&gt;The script is called when the power management system detect a
2227 change in the power status (power plug in or out), and when going into
2228 and out of hibernation and suspend. In addition, it collect a value
2229 every 10 minutes. This make it possible for me know when the battery
2230 is discharging, charging and how the maximum charge change over time.
2231 The code for the Debian package
2232 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
2233 available on github&lt;/a&gt;.&lt;/p&gt;
2234
2235 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
2236
2237 &lt;pre&gt;
2238 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2239 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
2240 [...]
2241 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2242 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2243 &lt;/pre&gt;
2244
2245 &lt;p&gt;I wrote a small script to create a graph of the charge development
2246 over time. This graph depicted above show the slow death of my laptop
2247 battery.&lt;/p&gt;
2248
2249 &lt;p&gt;But why is this happening? Why are my laptop batteries always
2250 dying in a year or two, while the batteries of space probes and
2251 satellites keep working year after year. If we are to believe
2252 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
2253 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
2254 chance, and the fix is to not charge the Lithium-ion batteries to 100%
2255 all the time, but to stay below 90% of full charge most of the time.
2256 I&#39;ve been told that the Tesla electric cars
2257 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
2258 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
2259 100% when preparing for a longer trip (not that I would want a car
2260 like Tesla where rights to privacy is abandoned, but that is another
2261 story), which I guess is the option we should have for laptops on
2262 Linux too.&lt;/p&gt;
2263
2264 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
2265 stop charging at 80%, unless requested to charge to 100% once in
2266 preparation for a longer trip? I found
2267 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
2268 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2269 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
2270 load).&lt;/p&gt;
2271
2272 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
2273 at the start. I also wonder why the &quot;full capacity&quot; increases some
2274 times, and if it is possible to repeat the process to get the battery
2275 back to design capacity. And I wonder if the discharge and charge
2276 speed change over time, or if this stay the same. I did not yet try
2277 to write a tool to calculate the derivative values of the battery
2278 level, but suspect some interesting insights might be learned from
2279 those.&lt;/p&gt;
2280
2281 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
2282 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2283 packages instead of the tp-smapi-dkms package I had tried to use
2284 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
2285 and stop. I&#39;ve done so now, but expect my existing battery is toast
2286 and need to be replaced. The proposal is unfortunately Thinkpad
2287 specific.&lt;/p&gt;
2288 </description>
2289 </item>
2290
2291 <item>
2292 <title>New laptop - some more clues and ideas based on feedback</title>
2293 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
2294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
2295 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
2296 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
2297 need for a new laptop, and provided very useful feedback. I wish to
2298 thank every one of these. Several pointed me to the possibility of
2299 fixing my X230, and I am already in the process of getting Lenovo to
2300 do so thanks to the on site, next day support contract covering the
2301 machine. But the battery is almost useless (I expect to replace it
2302 with a non-official battery) and I do not expect the machine to live
2303 for many more years, so it is time to plan its replacement. If I did
2304 not have a support contract, it was suggested to find replacement parts
2305 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2306 might present a language barrier as I do not understand French.&lt;/p&gt;
2307
2308 &lt;p&gt;One tip I got was to use the
2309 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2310 compare laptop models. It seem to have more models available than
2311 prisjakt.no. Another tip I got from someone I know have similar
2312 keyboard preferences was that the HP EliteBook 840 keyboard is not
2313 very good, and this matches my experience with earlier EliteBook
2314 keyboards I tested. Because of this, I will not consider it any further.
2315
2316 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2317 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2318 (which is missing from the X240), and is working fairly well with
2319 Debian Sid/Unstable according to
2320 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2321 got on the keyboard quality are not consistent. Some say the keyboard
2322 is good, others say it is ok, while others say it is not very good.
2323 Those with experience from X41 and and X60 agree that the X250
2324 keyboard is not as good as those trusty old laptops, and suggest I
2325 keep and fix my X230 instead of upgrading, or get a used X230 to
2326 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2327 activity and battery status, which is very convenient on my X230. I&#39;m
2328 also told that the CPU fan is running very often, making it a bit
2329 noisy. In any case, the X250 do not work out of the box with Debian
2330 Stable/Jessie, one of my requirements.&lt;/p&gt;
2331
2332 &lt;p&gt;I have also gotten a few vendor proposals, one was
2333 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2334 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2335 The latter look very attractive to me.&lt;/p&gt;
2336
2337 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2338 as I keep looking for a replacement.&lt;/p&gt;
2339
2340 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2341 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2342 different
2343 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2344 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2345 </description>
2346 </item>
2347
2348 <item>
2349 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2350 <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>
2351 <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>
2352 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2353 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2354 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2355 started flickering yesterday, and I suspect the cause is a broken
2356 cable, as changing the angle of the screen some times get rid of the
2357 flickering.&lt;/p&gt;
2358
2359 &lt;p&gt;My requirements have not really changed since I bought it, and is
2360 still as
2361 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2362 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2363 good help from
2364 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2365 where I could select at least a few of the requirements (mouse pin,
2366 wifi, weight) and go through the rest manually. Three button mouse
2367 and a good keyboard is not available as an option, and all the three
2368 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2369 G2) lack three mouse buttons). It is also unclear to me how good the
2370 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2371 the keyboard, even if the quality and robustness in the X series have
2372 deteriorated since X41.&lt;/p&gt;
2373
2374 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2375 seem sensible to me? Are there better services around to search the
2376 set of available laptops for features? Please send me an email if you
2377 have suggestions.&lt;/p&gt;
2378
2379 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2380 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2381 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2382 </description>
2383 </item>
2384
2385 <item>
2386 <title>How to stay with sysvinit in Debian Jessie</title>
2387 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2389 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2390 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2391 sysvinit as its boot system by default. But how can one keep using
2392 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2393 courtesy of
2394 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2395 Schubert&lt;/a&gt; and
2396 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2397 McVittie&lt;/a&gt;.
2398
2399 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2400 keep sysvinit as your boot system, create a file
2401 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2402 you upgrade:&lt;/p&gt;
2403
2404 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2405 Package: systemd-sysv
2406 Pin: release o=Debian
2407 Pin-Priority: -1
2408 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2409
2410 &lt;p&gt;This file content will tell apt and aptitude to not consider
2411 installing systemd-sysv as part of any installation and upgrade
2412 solution when resolving dependencies, and thus tell it to avoid
2413 systemd as a default boot system. The end result should be that the
2414 upgraded system keep using sysvinit.&lt;/p&gt;
2415
2416 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2417 get sysvinit installed by default (debootstrap used by
2418 debian-installer have no option for this), but one can tell the
2419 installer to switch to sysvinit before the first boot. Either by
2420 using a kernel argument to the installer, or by adding a line to the
2421 preseed file used. First, the kernel command line argument:
2422
2423 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2424 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2425 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2426
2427 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2428
2429 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2430 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2431 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2432
2433 &lt;p&gt;One can of course also do this after the first boot by installing
2434 the sysvinit-core package.&lt;/p&gt;
2435
2436 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2437 sysvinit boot sequence in Debian have several hardware specific bugs
2438 on Linux caused by the fact that it is unpredictable when hardware
2439 devices show up during boot. But on the other hand, the new default
2440 boot system still have a few rough edges I hope will be fixed before
2441 Jessie is released.&lt;/p&gt;
2442
2443 &lt;p&gt;Update 2014-11-26: Inspired by
2444 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2445 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2446 line.&lt;/p&gt;
2447 </description>
2448 </item>
2449
2450 <item>
2451 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2452 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2454 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2455 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2456 without anyone snooping, is a right every citicen have in a liberal
2457 democracy. But this right is under serious attack these days.&lt;/p&gt;
2458
2459 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2460 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2461 the whisleblower Snowden) more expensive for Internet email,
2462 is to deliver all email using SMTP via Tor. Such SMTP option would be
2463 a nice addition to the FreedomBox project if we could send email
2464 between FreedomBox machines without leaking metadata about the emails
2465 to the people peeking on the wire. I
2466 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2467 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2468 lot of useful feedback and suggestions. It also became obvious to me
2469 that this was not a novel idea, as the same idea was tested and
2470 documented by Johannes Berg as early as 2006, and both
2471 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2472 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2473 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2474
2475 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2476 providing the SMTP protocol on port 25, and use email addresses
2477 looking like username@hidden-service-name.onion. With such addresses
2478 the connections to port 25 on hidden-service-name.onion using Tor will
2479 go to the correct SMTP server. To do this, one need to configure the
2480 Tor daemon to provide the hidden service and the mail server to accept
2481 emails for this .onion domain. To learn more about Exim configuration
2482 in Debian and test the design provided by Johannes Berg in his FAQ, I
2483 set out yesterday to create a Debian package for making it trivial to
2484 set up such SMTP over Tor service based on Debian. Getting it to work
2485 were fairly easy, and
2486 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2487 source code for the Debian package&lt;/a&gt; is available from github. I
2488 plan to move it into Debian if further testing prove this to be a
2489 useful approach.&lt;/p&gt;
2490
2491 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2492 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2493 get rid of exim4). Install tor, clone the git repository mentioned
2494 above, build the deb and install it on the machine. Next, run
2495 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2496 the instructions to get the service up and running. Restart tor and
2497 exim when it is done, and test mail delivery using swaks like
2498 this:&lt;/p&gt;
2499
2500 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2501 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2502 --to fbx@dutlqrrmjhtfa3vp.onion
2503 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2504
2505 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2506 address with your own address to test your server. :)&lt;/p&gt;
2507
2508 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2509 easier and more automatic. Especially the tor setup need more work.
2510 Also, the package include a tor-smtp tool written in C, but its task
2511 should probably be rewritten in some script language to make the deb
2512 architecture independent. It would probably also make the code easier
2513 to review. The tor-smtp tool currently need to listen on a socket for
2514 exim to talk to it and is started using xinetd. It would be better if
2515 no daemon and no socket is needed. I suspect it is possible to get
2516 exim to run a command line tool for delivery instead of talking to a
2517 socket, and hope to figure out how in a future version of this
2518 system.&lt;/p&gt;
2519
2520 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2521 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2522 SMTorP. :)&lt;/p&gt;
2523 </description>
2524 </item>
2525
2526 <item>
2527 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2528 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2530 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2531 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2532 alioth.debian.org, you know the web interface is fairly slow to
2533 operate. First you visit one web page, enter the moderation password
2534 and get a new page shown with a list of all the messages to moderate
2535 and various options for each email address. This take a while for
2536 every list you moderate, and you need to do it regularly to do a good
2537 job as a list moderator. But there is a quick alternative,
2538 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
2539 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
2540 to moderate in a fraction of a second. Here is a test run on two
2541 lists I recently took over:&lt;/p&gt;
2542
2543 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2544 % time listadmin xiph
2545 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2546 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2547
2548 real 0m1.709s
2549 user 0m0.232s
2550 sys 0m0.012s
2551 %
2552 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2553
2554 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
2555 there are no message in the moderation queue. Every morning I
2556 currently moderate 68 mailman lists, and it normally take around two
2557 minutes. When I took over the two pkg-xiph lists above a few days
2558 ago, there were 400 emails waiting in the moderator queue. It took me
2559 less than 15 minutes to process them all using the listadmin
2560 program.&lt;/p&gt;
2561
2562 &lt;p&gt;If you install
2563 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
2564 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
2565 with content like this, the moderation task is a breeze:&lt;/p&gt;
2566
2567 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2568 username username@example.org
2569 spamlevel 23
2570 default discard
2571 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
2572
2573 password secret
2574 adminurl https://{domain}/mailman/admindb/{list}
2575 mailman-list@lists.example.com
2576
2577 password hidden
2578 other-list@otherserver.example.org
2579 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2580
2581 &lt;p&gt;There are other options to set as well. Check the manual page to
2582 learn the details.&lt;/p&gt;
2583
2584 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
2585 the SSL certificate is self signed or not properly signed by a
2586 generally accepted signing authority, you can set a environment
2587 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
2588
2589 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2590 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
2591 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2592
2593 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
2594 can provide an argument to the listadmin script like I do in the
2595 initial screen dump (the xiph argument). Using an argument, only
2596 lists matching the argument string will be processed. This make it
2597 quick to accept messages if you notice the moderation request in your
2598 email.&lt;/p&gt;
2599
2600 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
2601 mailing lists, as I simply do not have time to spend on that if the
2602 process was any slower. The listadmin program have saved me hours of
2603 time I could spend elsewhere over the years. It truly is nice free
2604 software.&lt;/p&gt;
2605
2606 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2607 activities, please send Bitcoin donations to my address
2608 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2609
2610 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
2611 configuration example. Also, I&#39;ve been told that the
2612 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
2613 sure why.&lt;/p&gt;
2614 </description>
2615 </item>
2616
2617 <item>
2618 <title>Debian Jessie, PXE and automatic firmware installation</title>
2619 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
2620 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
2621 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
2622 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
2623 problem that the WiFi card require some firmware to work properly.
2624 And it has been a pain to fix this using preseeding in Debian.
2625 Normally something more is needed. But thanks to
2626 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
2627 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
2628 to do this using simple preseeding.&lt;/p&gt;
2629
2630 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
2631 firmware for the hardware found in the machine (actually, requested by
2632 the kernel modules for the hardware). (It can also install user space
2633 programs supporting the hardware detected, but that is not the focus
2634 of this story.)&lt;/p&gt;
2635
2636 &lt;p&gt;To get this working in the default installation, two preeseding
2637 values are needed. First, the isenkram-cli package must be installed
2638 into the target chroot (aka the hard drive) before tasksel is executed
2639 in the pkgsel step of the debian-installer system. This is done by
2640 preseeding the base-installer/includes debconf value to include the
2641 isenkram-cli package. The package name is next passed to debootstrap
2642 for installation. With the isenkram-cli package in place, tasksel
2643 will automatically use the isenkram tasks to detect hardware specific
2644 packages for the machine being installed and install them, because
2645 isenkram-cli contain tasksel tasks.&lt;/p&gt;
2646
2647 &lt;p&gt;Second, one need to enable the non-free APT repository, because
2648 most firmware unfortunately is non-free. This is done by preseeding
2649 the apt-mirror-setup step. This is unfortunate, but for a lot of
2650 hardware it is the only option in Debian.&lt;/p&gt;
2651
2652 &lt;p&gt;The end result is two lines needed in your preseeding file to get
2653 firmware installed automatically by the installer:&lt;/p&gt;
2654
2655 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2656 base-installer base-installer/includes string isenkram-cli
2657 apt-mirror-setup apt-setup/non-free boolean true
2658 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2659
2660 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
2661 both firmware and user space packages when using this method. It also
2662 do not work well, so use version 0.15 or later. Installing both
2663 firmware and user space packages might give you a bit more than you
2664 want, so I decided to split the tasksel task in two, one for firmware
2665 and one for user space programs. The firmware task is enabled by
2666 default, while the one for user space programs is not. This split is
2667 implemented in the package currently in unstable.&lt;/p&gt;
2668
2669 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
2670 this recipe work for you. :)&lt;/p&gt;
2671
2672 &lt;p&gt;So, I bet you are wondering, how can this work. First and
2673 foremost, it work because tasksel is modular, and driven by whatever
2674 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2675 isenkram-cli package place two files for tasksel to find. First there
2676 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
2677
2678 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2679 Task: isenkram-packages
2680 Section: hardware
2681 Description: Hardware specific packages (autodetected by isenkram)
2682 Based on the detected hardware various hardware specific packages are
2683 proposed.
2684 Test-new-install: show show
2685 Relevance: 8
2686 Packages: for-current-hardware
2687
2688 Task: isenkram-firmware
2689 Section: hardware
2690 Description: Hardware specific firmware packages (autodetected by isenkram)
2691 Based on the detected hardware various hardware specific firmware
2692 packages are proposed.
2693 Test-new-install: mark show
2694 Relevance: 8
2695 Packages: for-current-hardware-firmware
2696 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2697
2698 &lt;p&gt;The key parts are Test-new-install which indicate how the task
2699 should be handled and the Packages line referencing to a script in
2700 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2701 list of packages to install. The for-current-hardware-firmware script
2702 look like this to list relevant firmware for the machine:
2703
2704 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2705 #!/bin/sh
2706 #
2707 PATH=/usr/sbin:$PATH
2708 export PATH
2709 isenkram-autoinstall-firmware -l
2710 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2711
2712 &lt;p&gt;With those two pieces in place, the firmware is installed by
2713 tasksel during the normal d-i run. :)&lt;/p&gt;
2714
2715 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
2716 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
2717 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
2718 install.&lt;/p&gt;
2719
2720 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
2721 pilots in testing this feature, as isenkram is used there now to
2722 install firmware, replacing the earlier scripts.&lt;/p&gt;
2723 </description>
2724 </item>
2725
2726 <item>
2727 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
2728 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
2729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
2730 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
2731 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
2732 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2733 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
2734 on a screen normally showing the bread types and prizes:&lt;/p&gt;
2735
2736 &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;
2737
2738 &lt;p&gt;If it had booted as it was supposed to, I would never had known
2739 about this hidden Linux installation. It is interesting what
2740 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
2741 </description>
2742 </item>
2743
2744 <item>
2745 <title>New lsdvd release version 0.17 is ready</title>
2746 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
2747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
2748 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
2749 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
2750 got a new set of developers a few weeks ago, after the original
2751 developer decided to step down and pass the project to fresh blood.
2752 This project is now maintained by Petter Reinholdtsen and Steve
2753 Dibb.&lt;/p&gt;
2754
2755 &lt;p&gt;I just wrapped up
2756 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
2757 new lsdvd release&lt;/a&gt;, available in git or from
2758 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
2759 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
2760 0.17.&lt;/p&gt;
2761
2762 &lt;ul&gt;
2763
2764 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
2765 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
2766 non-existant, to work around additional copy protection&lt;/li&gt;
2767 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
2768 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
2769 &lt;li&gt;Fix include orders&lt;/li&gt;
2770 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
2771 &lt;li&gt;Fix the chapter count&lt;/li&gt;
2772 &lt;li&gt;Make sure the array size and the array limit used when initialising
2773 the palette size is the same.&lt;/li&gt;
2774 &lt;li&gt;Fix array printing.&lt;/li&gt;
2775 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
2776 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
2777 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
2778 with more GCC compiler warnings.&lt;/li&gt;
2779
2780 &lt;/ul&gt;
2781
2782 &lt;p&gt;This change bring together patches for lsdvd in use in various
2783 Linux and Unix distributions, as well as patches submitted to the
2784 project the last nine years. Please check it out. :)&lt;/p&gt;
2785 </description>
2786 </item>
2787
2788 <item>
2789 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
2790 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
2791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
2792 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
2793 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2794 project&lt;/a&gt; provide a Linux solution for schools, including a
2795 powerful desktop with education software, a central server providing
2796 web pages, user database, user home directories, central login and PXE
2797 boot of both clients without disk and the installation to install Debian
2798 Edu on machines with disk (and a few other services perhaps to small
2799 to mention here). We in the Debian Edu team are currently working on
2800 the Jessie based version, trying to get everything in shape before the
2801 freeze, to avoid having to maintain our own package repository in the
2802 future. The
2803 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
2804 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
2805 work left. Some fatal problems block testing, breaking the installer,
2806 but it is possible to work around these to get anyway. Here is a
2807 recipe on how to get the installation limping along.&lt;/p&gt;
2808
2809 &lt;p&gt;First, download the test ISO via
2810 &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;,
2811 &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;
2812 or rsync (use
2813 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
2814 The ISO build was broken on Tuesday, so we do not get a new ISO every
2815 12 hours or so, but thankfully the ISO we already got we are able to
2816 install with some tweaking.&lt;/p&gt;
2817
2818 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
2819 (use Alt-Ctrl-F2), run&lt;/p&gt;
2820
2821 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2822 nano /usr/bin/edu-eatmydata-install
2823 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2824
2825 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
2826 optimization. Return to the installation, select the profile you want
2827 and continue. Without this change, exim4-config will fail to install
2828 due to a known bug in eatmydata.&lt;/p&gt;
2829
2830 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
2831 this do not work, figure out what your correct value would be. All my
2832 test machines need /dev/sda, so I have no advice if it do not fit
2833 your need.&lt;/p&gt;
2834
2835 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
2836 root after the initial boot from hard drive, and install the
2837 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2838 or mate. If you want several desktop options, install more than one
2839 metapackage. Once this is done, reboot and you should have a working
2840 graphical login screen. This workaround should no longer be needed
2841 once the education-tasks package version 1.801 enter testing in two
2842 days.&lt;/p&gt;
2843
2844 &lt;p&gt;I believe the ISO build will start working on two days when the new
2845 tasksel package enter testing and Steve McIntyre get a chance to
2846 update the debian-cd git repository. The eatmydata, grub and desktop
2847 issues are already fixed in unstable and testing, and should show up
2848 on the ISO as soon as the ISO build start working again. Well the
2849 eatmydata optimization is really just disabled. The proper fix
2850 require an upload by the eatmydata maintainer applying the patch
2851 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
2852 The rest have proper fixes in unstable.&lt;/p&gt;
2853
2854 &lt;p&gt;I hope this get you going with the installation testing, as we are
2855 quickly running out of time trying to get our Jessie based
2856 installation ready before the distribution freeze in a month.&lt;/p&gt;
2857 </description>
2858 </item>
2859
2860 <item>
2861 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
2862 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
2863 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
2864 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
2865 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
2866 to handle my fairly large DVD collection. It is a nice command line
2867 tool to get details about a DVD, like title, tracks, track length,
2868 etc, in XML, Perl or human readable format. But lsdvd have not seen
2869 any new development since 2006 and had a few irritating bugs affecting
2870 its use with some DVDs. Upstream seemed to be dead, and in January I
2871 sent a small probe asking for a version control repository for the
2872 project, without any reply. But I use it regularly and would like to
2873 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
2874 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
2875 the project admin, and after getting a reply from him explaining that
2876 he was no longer interested in the project, I asked if I could take
2877 over. And yesterday, I became project admin.&lt;/p&gt;
2878
2879 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
2880 maintainer interested in joining forces to maintain the upstream
2881 project, and I hope we can get a new release out fairly quickly,
2882 collecting the patches spread around on the internet into on place.
2883 I&#39;ve added the relevant Debian patches to the freshly created git
2884 repository, and expect the Gentoo patches to make it too. If you got
2885 a DVD collection and care about command line tools, check out
2886 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
2887 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
2888 list&lt;/a&gt;. :)&lt;/p&gt;
2889 </description>
2890 </item>
2891
2892 <item>
2893 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
2894 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
2895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
2896 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
2897 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
2898 a lot quicker. When we install more than 2000 packages in
2899 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
2900 tasksel in the installer, unpacking the binary packages take forever.
2901 A part of the slow I/O issue was discussed in
2902 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
2903 much file system sync-ing done by dpkg, which is the package
2904 responsible for unpacking the binary packages. Other parts (like code
2905 executed by postinst scripts) might also sync to disk during
2906 installation. All this sync-ing to disk do not really make sense to
2907 me. If the machine crash half-way through, I start over, I do not try
2908 to salvage the half installed system. So the failure sync-ing is
2909 supposed to protect against, hardware or system crash, is not really
2910 relevant while the installer is running.&lt;/p&gt;
2911
2912 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
2913 system sync()-ing in a fairly non-intrusive way, without the need to
2914 change the code in several packages. The idea is not new, but I have
2915 not heard anyone propose the approach using dpkg-divert before. It
2916 depend on the small and clever package
2917 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
2918 uses LD_PRELOAD to replace the system functions for syncing data to
2919 disk with functions doing nothing, thus allowing programs to live
2920 dangerous while speeding up disk I/O significantly. Instead of
2921 modifying the implementation of dpkg, apt and tasksel (which are the
2922 packages responsible for selecting, fetching and installing packages),
2923 it occurred to me that we could just divert the programs away, replace
2924 them with a simple shell wrapper calling
2925 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
2926 Two days ago I decided to test the idea, and wrapped up a simple
2927 implementation for the Debian Edu udeb.&lt;/p&gt;
2928
2929 &lt;p&gt;The effect was stunning. In my first test it reduced the running
2930 time of the pkgsel step (installing tasks) from 64 to less than 44
2931 minutes (20 minutes shaved off the installation) on an old Dell
2932 Latitude D505 machine. I am not quite sure what the optimised time
2933 would have been, as I messed up the testing a bit, causing the debconf
2934 priority to get low enough for two questions to pop up during
2935 installation. As soon as I saw the questions I moved the installation
2936 along, but do not know how long the question were holding up the
2937 installation. I did some more measurements using Debian Edu Jessie,
2938 and got these results. The time measured is the time stamp in
2939 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
2940 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
2941 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2942 timing thus do not depend on how quickly the user handle the tasksel
2943 dialog.&lt;/p&gt;
2944
2945 &lt;p&gt;&lt;table&gt;
2946
2947 &lt;tr&gt;
2948 &lt;th&gt;Machine/setup&lt;/th&gt;
2949 &lt;th&gt;Original tasksel&lt;/th&gt;
2950 &lt;th&gt;Optimised tasksel&lt;/th&gt;
2951 &lt;th&gt;Reduction&lt;/th&gt;
2952 &lt;/tr&gt;
2953
2954 &lt;tr&gt;
2955 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
2956 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
2957 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
2958 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
2959 &lt;/tr&gt;
2960
2961 &lt;tr&gt;
2962 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
2963 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
2964 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
2965 &lt;td&gt;23 min 40%&lt;/td&gt;
2966 &lt;/tr&gt;
2967
2968 &lt;tr&gt;
2969 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
2970 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
2971 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
2972 &lt;td&gt;11 min 50%&lt;/td&gt;
2973 &lt;/tr&gt;
2974
2975 &lt;tr&gt;
2976 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
2977 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
2978 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
2979 &lt;td&gt;2 min 33%&lt;/td&gt;
2980 &lt;/tr&gt;
2981
2982 &lt;tr&gt;
2983 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
2984 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
2985 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
2986 &lt;td&gt;4 min 21%&lt;/td&gt;
2987 &lt;/tr&gt;
2988
2989 &lt;/table&gt;&lt;/p&gt;
2990
2991 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
2992 time is spent downloading packages. The connection to the Internet
2993 was 100Mbit/s during testing, so downloading should not be a
2994 significant factor in the measurement. Download typically took a few
2995 seconds to a few minutes, depending on the amount of packages being
2996 installed.&lt;/p&gt;
2997
2998 &lt;p&gt;The speedup is implemented by using two hooks in
2999 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3000 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3001 finish-install.d hook to remove the divert at the end of the
3002 installation. I picked the pre-pkgsel.d hook instead of the
3003 post-base-installer.d hook because I test using an ISO without the
3004 eatmydata package included, and the post-base-installer.d hook in
3005 Debian Edu can only operate on packages included in the ISO. The
3006 negative effect of this is that I am unable to activate this
3007 optimization for the kernel installation step in d-i. If the code is
3008 moved to the post-base-installer.d hook, the speedup would be larger
3009 for the entire installation.&lt;/p&gt;
3010
3011 &lt;p&gt;I&#39;ve implemented this in the
3012 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3013 git repository, and plan to provide the optimization as part of the
3014 Debian Edu installation. If you want to test this yourself, you can
3015 create two files in the installer (or in an udeb). One shell script
3016 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3017
3018 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3019 #!/bin/sh
3020 set -e
3021 . /usr/share/debconf/confmodule
3022 info() {
3023 logger -t my-pkgsel &quot;info: $*&quot;
3024 }
3025 error() {
3026 logger -t my-pkgsel &quot;error: $*&quot;
3027 }
3028 override_install() {
3029 apt-install eatmydata || true
3030 if [ -x /target/usr/bin/eatmydata ] ; then
3031 for bin in dpkg apt-get aptitude tasksel ; do
3032 file=/usr/bin/$bin
3033 # Test that the file exist and have not been diverted already.
3034 if [ -f /target$file ] ; then
3035 info &quot;diverting $file using eatmydata&quot;
3036 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3037 &gt; /target$file.edu
3038 chmod 755 /target$file.edu
3039 in-target dpkg-divert --package debian-edu-config \
3040 --rename --quiet --add $file
3041 ln -sf ./$bin.edu /target$file
3042 else
3043 error &quot;unable to divert $file, as it is missing.&quot;
3044 fi
3045 done
3046 else
3047 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3048 fi
3049 }
3050
3051 override_install
3052 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3053
3054 &lt;p&gt;To clean up, another shell script should go into
3055 /usr/lib/finish-install.d/ with code like this:
3056
3057 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3058 #! /bin/sh -e
3059 . /usr/share/debconf/confmodule
3060 error() {
3061 logger -t my-finish-install &quot;error: $@&quot;
3062 }
3063 remove_install_override() {
3064 for bin in dpkg apt-get aptitude tasksel ; do
3065 file=/usr/bin/$bin
3066 if [ -x /target$file.edu ] ; then
3067 rm /target$file
3068 in-target dpkg-divert --package debian-edu-config \
3069 --rename --quiet --remove $file
3070 rm /target$file.edu
3071 else
3072 error &quot;Missing divert for $file.&quot;
3073 fi
3074 done
3075 sync # Flush file buffers before continuing
3076 }
3077
3078 remove_install_override
3079 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3080
3081 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3082 edu-eatmydata-install and call it from the pre-pkgsel.d and
3083 finish-install.d scripts.&lt;/p&gt;
3084
3085 &lt;p&gt;By now you might ask if this change should get into the normal
3086 Debian installer too? I suspect it should, but am not sure the
3087 current debian-installer coordinators find it useful enough. It also
3088 depend on the side effects of the change. I&#39;m not aware of any, but I
3089 guess we will see if the change is safe after some more testing.
3090 Perhaps there is some package in Debian depending on sync() and
3091 fsync() having effect? Perhaps it should go into its own udeb, to
3092 allow those of us wanting to enable it to do so without affecting
3093 everyone.&lt;/p&gt;
3094
3095 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3096 will break installation of all programs using gnutls because of
3097 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3098 eatmydata package in Debian will solve it.&lt;/p&gt;
3099
3100 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3101 the optimization work again. And I have discovered that the
3102 dpkg-divert trick is not really needed and implemented a slightly
3103 simpler approach as part of the debian-edu-install package. See
3104 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3105
3106 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
3107 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
3108 triggering on i386 made it into testing, and broke this installation
3109 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
3110 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
3111 </description>
3112 </item>
3113
3114 <item>
3115 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
3116 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
3117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
3118 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
3119 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
3120 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
3121 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
3122 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
3123 learn that there is a large set of publicly available key servers to
3124 use when looking for peoples public key. So far I have used
3125 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3126 were misbehaving, but those days are ended. The servers I have used
3127 up until yesterday have been slow and some times unavailable. I hope
3128 those problems are gone now.&lt;/p&gt;
3129
3130 &lt;p&gt;Behind the round robin DNS entry of the
3131 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
3132 there is a pool of more than 100 keyservers which are checked every
3133 day to ensure they are well connected and up to date. It must be
3134 better than what I have used so far. :)&lt;/p&gt;
3135
3136 &lt;p&gt;Yesterdays speaker told me that the service is the default
3137 keyserver provided by the default configuration in GnuPG, but this do
3138 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
3139
3140 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
3141 line:&lt;/p&gt;
3142
3143 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3144 keyserver pool.sks-keyservers.net
3145 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3146
3147 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
3148 entries in DNS. Just for fun, I did just that at work, so now every
3149 user of GnuPG at the University of Oslo should find a OpenGPG
3150 keyserver automatically should their need it:&lt;/p&gt;
3151
3152 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3153 % host -t srv _pgpkey-http._tcp.uio.no
3154 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
3155 %
3156 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3157
3158 &lt;p&gt;Now if only
3159 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
3160 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
3161 very happy. It can look up a given key or search for a user ID, but I
3162 normally do not want that, but to find a trust path from my key to
3163 another key. Given a user ID or key ID, I would like to find (and
3164 download) the keys representing a signature path from my key to the
3165 key in question, to be able to get a trust path between the two keys.
3166 This is as far as I can tell not possible today. Perhaps something
3167 for a future version of the protocol?&lt;/p&gt;
3168 </description>
3169 </item>
3170
3171 <item>
3172 <title>From English wiki to translated PDF and epub via Docbook</title>
3173 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
3174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
3175 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
3176 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3177 project&lt;/a&gt; provide an instruction manual for teachers, system
3178 administrators and other users that contain useful tips for setting up
3179 and maintaining a Debian Edu installation. This text is about how the
3180 text processing of this manual is handled in the project.&lt;/p&gt;
3181
3182 &lt;p&gt;One goal of the project is to provide information in the native
3183 language of its users, and for this we need to handle translations.
3184 But we also want to make sure each language contain the same
3185 information, so for this we need a good way to keep the translations
3186 in sync. And we want it to be easy for our users to improve the
3187 documentation, avoiding the need to learn special formats or tools to
3188 contribute, and the obvious way to do this is to make it possible to
3189 edit the documentation using a web browser. We also want it to be
3190 easy for translators to keep the translation up to date, and give them
3191 help in figuring out what need to be translated. Here is the list of
3192 tools and the process we have found trying to reach all these
3193 goals.&lt;/p&gt;
3194
3195 &lt;p&gt;We maintain the authoritative source of our manual in the
3196 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
3197 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
3198 front page with references to the different chapters, several pages
3199 for each chapter, and finally one &quot;collection page&quot; gluing all the
3200 chapters together into one large web page (aka
3201 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
3202 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
3203 processing and translations. Thanks to the fact that the
3204 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
3205 wiki.debian.org support exporting pages in
3206 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
3207 the list of pages to export using the raw version of the AllInOne
3208 page, loop over each of them to generate a Docbook XML version of the
3209 manual. This process also download images and transform image
3210 references to use the locally downloaded images. The generated
3211 Docbook XML files are slightly broken, so some post-processing is done
3212 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
3213 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3214 a handfull of images. The XML file can now be used to generate PDF, HTML
3215 and epub versions of the English manual. This is the basic step of
3216 our process, making PDF (using dblatex), HTML (using xsltproc) and
3217 epub (using dbtoepub) version from Docbook XML, and the resulting files
3218 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
3219
3220 &lt;p&gt;But English documentation is not enough for us. We want translated
3221 documentation too, and we want to make it easy for translators to
3222 track the English original. For this we use the
3223 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
3224 which allow us to transform the English Docbook XML file into a
3225 translation file (a .pot file), usable with the normal gettext based
3226 translation tools used by those translating free software. The pot
3227 file is used to create and maintain translation files (several .po
3228 files), which the translations update with the native language
3229 translations of all titles, paragraphs and blocks of text in the
3230 original. The next step is combining the original English Docbook XML
3231 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3232 create a translated Docbook XML file (in this case
3233 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3234 translated, if the translation is not complete) Docbook XML file can
3235 then be used like the original to create a PDF, HTML and epub version
3236 of the documentation.&lt;/p&gt;
3237
3238 &lt;p&gt;The translators use different tools to edit the .po files. We
3239 recommend using
3240 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
3241 while some use emacs and vi, others can use web based editors like
3242 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
3243 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
3244 is where the .po file end up, in our git repository. Updated
3245 translations can either be committed directly to git, or submitted as
3246 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
3247 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
3248
3249 &lt;p&gt;One challenge is images, which both might need to be translated (if
3250 they show translated user applications), and are needed in different
3251 formats when creating PDF and HTML versions (epub is a HTML version in
3252 this regard). For this we transform the original PNG images to the
3253 needed density and format during build, and have a way to provide
3254 translated images by storing translated versions in
3255 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3256 package maintainers know more.&lt;/p&gt;
3257
3258 &lt;p&gt;If you wonder what the result look like, we provide
3259 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
3260 of the documentation packages on the web&lt;/a&gt;. See for example the
3261 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
3262 PDF version&lt;/a&gt; or the
3263 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
3264 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
3265 but perhaps it will be done in the future.&lt;/p&gt;
3266
3267 &lt;p&gt;To learn more, check out
3268 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
3269 debian-edu-doc package&lt;/a&gt;,
3270 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
3271 manual on the wiki&lt;/a&gt; and
3272 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
3273 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
3274 </description>
3275 </item>
3276
3277 <item>
3278 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
3279 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
3280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
3281 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
3282 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
3283 related packages relevant for the computer installed automatically.
3284 So I implemented one, using
3285 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
3286 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
3287 run tasksel as user root. You should be presented with a new option,
3288 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
3289 select it, tasksel will install the packages isenkram claim is fit for
3290 the current hardware, hot pluggable or not.&lt;p&gt;
3291
3292 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
3293 description, and the other is the script used to extract the list of
3294 packages to install. The first part is in
3295 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
3296 this:&lt;/p&gt;
3297
3298 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3299 Task: isenkram
3300 Section: hardware
3301 Description: Hardware specific packages (autodetected by isenkram)
3302 Based on the detected hardware various hardware specific packages are
3303 proposed.
3304 Test-new-install: mark show
3305 Relevance: 8
3306 Packages: for-current-hardware
3307 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3308
3309 &lt;p&gt;The second part is in
3310 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3311 this:&lt;/p&gt;
3312
3313 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3314 #!/bin/sh
3315 #
3316 (
3317 isenkram-lookup
3318 isenkram-autoinstall-firmware -l
3319 ) | sort -u
3320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3321
3322 &lt;p&gt;All in all, a very short and simple implementation making it
3323 trivial to install the hardware dependent package we all may want to
3324 have installed on our machines. I&#39;ve not been able to find a way to
3325 get tasksel to tell you exactly which packages it plan to install
3326 before doing the installation. So if you are curious or careful,
3327 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3328
3329 &lt;p&gt;The information about which packages are handling which hardware is
3330 fetched either from the isenkram package itself in
3331 /usr/share/isenkram/, from git.debian.org or from the APT package
3332 database (using the Modaliases header). The APT package database
3333 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3334 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3335 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3336 the python-apt code (bug
3337 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3338 workaround I was able to get rid of the file descriptor leak and
3339 reduce the memory leak from ~30 MiB per hardware detection down to
3340 around 2 MiB per hardware detection. It should make the desktop
3341 daemon a lot more useful. The fix is in version 0.7 uploaded to
3342 unstable today.&lt;/p&gt;
3343
3344 &lt;p&gt;I believe the current way of mapping hardware to packages in
3345 Isenkram is is a good draft, but in the future I expect isenkram to
3346 use the AppStream data source for this. A proposal for getting proper
3347 AppStream support into Debian is floating around as
3348 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3349 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3350 project&lt;/a&gt; will take place this summer to improve the situation. I
3351 look forward to seeing the result, and welcome patches for isenkram to
3352 start using the information when it is ready.&lt;/p&gt;
3353
3354 &lt;p&gt;If you want your package to map to some specific hardware, either
3355 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3356 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3357 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3358 package. See also
3359 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3360 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3361 the information will be migrated to AppStream eventually, but for the
3362 moment I got no better place to store it.&lt;/p&gt;
3363 </description>
3364 </item>
3365
3366 <item>
3367 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3368 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3370 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3371 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3372 project&lt;/a&gt; is working on providing the software and hardware to make
3373 it easy for non-technical people to host their data and communication
3374 at home, and being able to communicate with their friends and family
3375 encrypted and away from prying eyes. It is still going strong, and
3376 today a major mile stone was reached.&lt;/p&gt;
3377
3378 &lt;p&gt;Today, the last of the packages currently used by the project to
3379 created the system images were accepted into Debian Unstable. It was
3380 the freedombox-setup package, which is used to configure the images
3381 during build and on the first boot. Now all one need to get going is
3382 the build code from the freedom-maker git repository and packages from
3383 Debian. And once the freedombox-setup package enter testing, we can
3384 build everything directly from Debian. :)&lt;/p&gt;
3385
3386 &lt;p&gt;Some key packages used by Freedombox are
3387 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3388 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3389 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3390 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3391 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3392 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3393 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3394 are plans to integrate more packages into the setup. User
3395 documentation is maintained on the Debian wiki. Please
3396 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3397 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3398
3399 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3400 setup, run this on a Debian machine using a user with sudo rights to
3401 become root:&lt;/p&gt;
3402
3403 &lt;p&gt;&lt;pre&gt;
3404 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3405 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3406 u-boot-tools
3407 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3408 freedom-maker
3409 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3410 &lt;/pre&gt;&lt;/p&gt;
3411
3412 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3413 devices. See the README in the freedom-maker git repo for more
3414 details on the build. If you do not want all three images, trim the
3415 make line. Note that the virtualbox-image target is not really
3416 virtualbox specific. It create a x86 image usable in kvm, qemu,
3417 vmware and any other x86 virtual machine environment. You might need
3418 the version of vmdebootstrap in Jessie to get the build working, as it
3419 include fixes for a race condition with kpartx.&lt;/p&gt;
3420
3421 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3422 method, boot a Debian Wheezy ISO and use this boot argument to load
3423 the preseed values:&lt;/p&gt;
3424
3425 &lt;p&gt;&lt;pre&gt;
3426 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;
3427 &lt;/pre&gt;&lt;/p&gt;
3428
3429 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3430 it still work.&lt;/p&gt;
3431
3432 &lt;p&gt;If you wonder how to help, one task you could look at is using
3433 systemd as the boot system. It will become the default for Linux in
3434 Jessie, so we need to make sure it is usable on the Freedombox. I did
3435 a simple test a few weeks ago, and noticed dnsmasq failed to start
3436 during boot when using systemd. I suspect there are other problems
3437 too. :) To detect problems, there is a test suite included, which can
3438 be run from the plinth web interface.&lt;/p&gt;
3439
3440 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3441 us get the new release published. :) Please join us on
3442 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3443 irc.debian.org)&lt;/a&gt; and
3444 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3445 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3446 </description>
3447 </item>
3448
3449 <item>
3450 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3451 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3453 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3454 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3455 solution for use at home. My requirements are simple, it must be
3456 cheap and locally encrypted (in other words, I keep the encryption
3457 keys, the storage provider do not have access to my private files).
3458 One idea me and my friends had many years ago, before the cloud
3459 storage providers showed up, was to use Google mail as storage,
3460 writing a Linux block device storing blocks as emails in the mail
3461 service provided by Google, and thus get heaps of free space. On top
3462 of this one can add encryption, RAID and volume management to have
3463 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3464 I never found time to implement such system. But the last few weeks I
3465 have looked at a system called
3466 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3467 mounted network backed file system with the features I need.&lt;/p&gt;
3468
3469 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3470 handling several different storage providers, any with Amazon S3,
3471 Google Drive or OpenStack API. There are heaps of such storage
3472 providers. S3QL can also use a local directory as storage, which
3473 combined with sshfs allow for file storage on any ssh server. S3QL
3474 include support for encryption, compression, de-duplication, snapshots
3475 and immutable file systems, allowing me to mount the remote storage as
3476 a local mount point, look at and use the files as if they were local,
3477 while the content is stored in the cloud as well. This allow me to
3478 have a backup that should survive fire. The file system can not be
3479 shared between several machines at the same time, as only one can
3480 mount it at the time, but any machine with the encryption key and
3481 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3482
3483 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3484 package is included already. So to get started, run &lt;tt&gt;apt-get
3485 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3486 Greenqloud, after reading their nice recipe on
3487 &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
3488 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3489 in Iceland more than those in USA when it come to keeping my personal
3490 data safe and private, and thus would rather spend money on a company
3491 in Iceland. Another nice recipe is available from the article
3492 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3493 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3494 Admin magazine. When the provider is picked, figure out how to get
3495 the API key needed to connect to the storage API. With Greencloud,
3496 the key did not show up until I had added payment details to my
3497 account.&lt;/p&gt;
3498
3499 &lt;p&gt;Armed with the API access details, it is time to create the file
3500 system. First, create a new bucket in the cloud. This bucket is the
3501 file system storage area. I picked a bucket name reflecting the
3502 machine that was going to store data there, but any name will do.
3503 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3504 the API login and password, and a locally created password. Store it
3505 all in ~root/.s3ql/authinfo2 like this:
3506
3507 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3508 [s3c]
3509 storage-url: s3c://s.greenqloud.com:443/bucket-name
3510 backend-login: API-login
3511 backend-password: API-password
3512 fs-passphrase: local-password
3513 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3514
3515 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3516 but any sensible way to create a fairly random password should do it.
3517 Armed with these details, it is now time to run mkfs, entering the API
3518 details and password to create it:&lt;/p&gt;
3519
3520 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3521 # mkdir -m 700 /var/lib/s3ql-cache
3522 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3523 --ssl s3c://s.greenqloud.com:443/bucket-name
3524 Enter backend login:
3525 Enter backend password:
3526 Before using S3QL, make sure to read the user&#39;s guide, especially
3527 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3528 Enter encryption password:
3529 Confirm encryption password:
3530 Generating random encryption key...
3531 Creating metadata tables...
3532 Dumping metadata...
3533 ..objects..
3534 ..blocks..
3535 ..inodes..
3536 ..inode_blocks..
3537 ..symlink_targets..
3538 ..names..
3539 ..contents..
3540 ..ext_attributes..
3541 Compressing and uploading metadata...
3542 Wrote 0.00 MB of compressed metadata.
3543 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3544
3545 &lt;p&gt;The next step is mounting the file system to make the storage available.
3546
3547 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3548 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3549 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3550 Using 4 upload threads.
3551 Downloading and decompressing metadata...
3552 Reading metadata...
3553 ..objects..
3554 ..blocks..
3555 ..inodes..
3556 ..inode_blocks..
3557 ..symlink_targets..
3558 ..names..
3559 ..contents..
3560 ..ext_attributes..
3561 Mounting filesystem...
3562 # df -h /s3ql
3563 Filesystem Size Used Avail Use% Mounted on
3564 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
3565 #
3566 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3567
3568 &lt;p&gt;The file system is now ready for use. I use rsync to store my
3569 backups in it, and as the metadata used by rsync is downloaded at
3570 mount time, no network traffic (and storage cost) is triggered by
3571 running rsync. To unmount, one should not use the normal umount
3572 command, as this will not flush the cache to the cloud storage, but
3573 instead running the umount.s3ql command like this:
3574
3575 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3576 # umount.s3ql /s3ql
3577 #
3578 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3579
3580 &lt;p&gt;There is a fsck command available to check the file system and
3581 correct any problems detected. This can be used if the local server
3582 crashes while the file system is mounted, to reset the &quot;already
3583 mounted&quot; flag. This is what it look like when processing a working
3584 file system:&lt;/p&gt;
3585
3586 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3587 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
3588 Using cached metadata.
3589 File system seems clean, checking anyway.
3590 Checking DB integrity...
3591 Creating temporary extra indices...
3592 Checking lost+found...
3593 Checking cached objects...
3594 Checking names (refcounts)...
3595 Checking contents (names)...
3596 Checking contents (inodes)...
3597 Checking contents (parent inodes)...
3598 Checking objects (reference counts)...
3599 Checking objects (backend)...
3600 ..processed 5000 objects so far..
3601 ..processed 10000 objects so far..
3602 ..processed 15000 objects so far..
3603 Checking objects (sizes)...
3604 Checking blocks (referenced objects)...
3605 Checking blocks (refcounts)...
3606 Checking inode-block mapping (blocks)...
3607 Checking inode-block mapping (inodes)...
3608 Checking inodes (refcounts)...
3609 Checking inodes (sizes)...
3610 Checking extended attributes (names)...
3611 Checking extended attributes (inodes)...
3612 Checking symlinks (inodes)...
3613 Checking directory reachability...
3614 Checking unix conventions...
3615 Checking referential integrity...
3616 Dropping temporary indices...
3617 Backing up old metadata...
3618 Dumping metadata...
3619 ..objects..
3620 ..blocks..
3621 ..inodes..
3622 ..inode_blocks..
3623 ..symlink_targets..
3624 ..names..
3625 ..contents..
3626 ..ext_attributes..
3627 Compressing and uploading metadata...
3628 Wrote 0.89 MB of compressed metadata.
3629 #
3630 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3631
3632 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
3633 quick, about the same speed as local file access. Uploading large
3634 amount of data is to me limited by the bandwidth out of and into my
3635 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
3636 which is very close to my upload speed, and downloading the same
3637 Debian installation ISO gave me 610 kiB/s, close to my download speed.
3638 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
3639 network, not the file system code. I do not know what a good cache
3640 size would be, but suspect that the cache should e larger than your
3641 working set.&lt;/p&gt;
3642
3643 &lt;p&gt;I mentioned that only one machine can mount the file system at the
3644 time. If another machine try, it is told that the file system is
3645 busy:&lt;/p&gt;
3646
3647 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3648 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3649 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3650 Using 8 upload threads.
3651 Backend reports that fs is still mounted elsewhere, aborting.
3652 #
3653 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3654
3655 &lt;p&gt;The file content is uploaded when the cache is full, while the
3656 metadata is uploaded once every 24 hour by default. To ensure the
3657 file system content is flushed to the cloud, one can either umount the
3658 file system, or ask S3QL to flush the cache and metadata using
3659 s3qlctrl:
3660
3661 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3662 # s3qlctrl upload-meta /s3ql
3663 # s3qlctrl flushcache /s3ql
3664 #
3665 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3666
3667 &lt;p&gt;If you are curious about how much space your data uses in the
3668 cloud, and how much compression and deduplication cut down on the
3669 storage usage, you can use s3qlstat on the mounted file system to get
3670 a report:&lt;/p&gt;
3671
3672 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3673 # s3qlstat /s3ql
3674 Directory entries: 9141
3675 Inodes: 9143
3676 Data blocks: 8851
3677 Total data size: 22049.38 MB
3678 After de-duplication: 21955.46 MB (99.57% of total)
3679 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
3680 Database size: 2.39 MB (uncompressed)
3681 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3682 #
3683 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3684
3685 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
3686 storage. I did not try to locate them all, but am aware of at least
3687 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
3688 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
3689 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
3690 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
3691 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
3692 accept payment in Bitcoin. Pick one that suit your need. Some of
3693 them provide several GiB of free storage, but the prize models are
3694 quite different and you will have to figure out what suits you
3695 best.&lt;/p&gt;
3696
3697 &lt;p&gt;While researching this blog post, I had a look at research papers
3698 and posters discussing the S3QL file system. There are several, which
3699 told me that the file system is getting a critical check by the
3700 science community and increased my confidence in using it. One nice
3701 poster is titled
3702 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
3703 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3704 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
3705 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3706 and Pamela Smith. Please have a look.&lt;/p&gt;
3707
3708 &lt;p&gt;Given my problems with different file systems earlier, I decided to
3709 check out the mounted S3QL file system to see if it would be usable as
3710 a home directory (in other word, that it provided POSIX semantics when
3711 it come to locking and umask handling etc). Running
3712 &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
3713 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
3714 no error was found. So the file system can be used for home
3715 directories, if one chooses to do so.&lt;/p&gt;
3716
3717 &lt;p&gt;If you do not want a locally file system, and want something that
3718 work without the Linux fuse file system, I would like to mention the
3719 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
3720 provide locally encrypted backup using a command line client. It have
3721 a nicer access control system, where one can split out read and write
3722 access, allowing some systems to write to the backup and others to
3723 only read from it.&lt;/p&gt;
3724
3725 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3726 activities, please send Bitcoin donations to my address
3727 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3728 </description>
3729 </item>
3730
3731 <item>
3732 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
3733 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
3734 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
3735 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
3736 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3737 project&lt;/a&gt; is working on providing the software and hardware for
3738 making it easy for non-technical people to host their data and
3739 communication at home, and being able to communicate with their
3740 friends and family encrypted and away from prying eyes. It has been
3741 going on for a while, and is slowly progressing towards a new test
3742 release (0.2).&lt;/p&gt;
3743
3744 &lt;p&gt;And what day could be better than the Pi day to announce that the
3745 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
3746 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3747 system), and can also be installed using a Debian installer preseed
3748 file. The Debian based Freedombox is now based on Debian Jessie,
3749 where most of the needed packages used are already present. Only one,
3750 the freedombox-setup package, is missing. To try to build your own
3751 boot image to test the current status, fetch the freedom-maker scripts
3752 and build using
3753 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
3754 with a user with sudo access to become root:
3755
3756 &lt;pre&gt;
3757 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3758 freedom-maker
3759 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3760 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3761 u-boot-tools
3762 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3763 &lt;/pre&gt;
3764
3765 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3766 devices. See the README for more details on the build. If you do not
3767 want all three images, trim the make line. But note that thanks to &lt;a
3768 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
3769 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
3770 kpartx call.&lt;/p&gt;
3771
3772 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3773 method, boot a Debian Wheezy ISO and use this boot argument to load
3774 the preseed values:&lt;/p&gt;
3775
3776 &lt;pre&gt;
3777 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;
3778 &lt;/pre&gt;
3779
3780 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
3781 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
3782 currently hang while setting up APT sources. Killing the
3783 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
3784 installation will get the installation going. This affect all
3785 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
3786
3787 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3788 us get the new release published. :) Please join us on
3789 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3790 irc.debian.org)&lt;/a&gt; and
3791 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3792 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3793 </description>
3794 </item>
3795
3796 <item>
3797 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
3798 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
3799 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
3800 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
3801 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
3802 innetgr tools, because I needed them in
3803 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
3804 ng-utils, and it has served me well. I placed the project under the
3805 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
3806 repository. But many years ago, the CVS repository was dropped (lost,
3807 not migrated to new hardware, not sure), and the project have lacked a
3808 proper home since then.&lt;/p&gt;
3809
3810 &lt;p&gt;Last summer, I had a look at the package and made a new release
3811 fixing a irritating crash bug, but was unable to store the changes in
3812 a proper source control system. I applied for a project on
3813 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
3814 to follow up on it. Until today. :)&lt;/p&gt;
3815
3816 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
3817 now have a new home, and a git repository with the highlight of the
3818 history of the project. I published all release tarballs and imported
3819 them into the git repository. As the project is really stable and not
3820 expected to gain new features any time soon, I decided to make a new
3821 release and call it 1.0. Visit the new project home on
3822 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
3823 if you want to check it out. The new version is also uploaded into
3824 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
3825 </description>
3826 </item>
3827
3828 <item>
3829 <title>Testing sysvinit from experimental in Debian Hurd</title>
3830 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
3831 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
3832 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
3833 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
3834 their changes into sysvinit, to allow them to use the normal sysvinit
3835 boot system instead of their old one. This follow up on the
3836 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
3837 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
3838 get Debian on Hurd working more like Debian on Linux. To get started,
3839 I downloaded a prebuilt hard disk image from
3840 &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;,
3841 and started it using virt-manager.&lt;/p&gt;
3842
3843 &lt;p&gt;The first think I had to do after logging in (root without any
3844 password) was to get the network operational. I followed
3845 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
3846 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
3847 commands as root to get the machine to accept a IP address from the
3848 kvm internal DHCP server:&lt;/p&gt;
3849
3850 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3851 settrans -fgap /dev/netdde /hurd/netdde
3852 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
3853 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
3854 dhclient /dev/eth0
3855 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3856
3857 &lt;p&gt;After this, the machine had internet connectivity, and I could
3858 upgrade it and install the sysvinit packages from experimental and
3859 enable it as the default boot system in Hurd.&lt;/p&gt;
3860
3861 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
3862 running on the machine it for ssh login to work a password need to be
3863 set. Also, note that a bug somewhere in openssh on Hurd block
3864 compression from working. Remember to turn that off on the client
3865 side.&lt;/p&gt;
3866
3867 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
3868 stuff:&lt;/p&gt;
3869
3870 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3871 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
3872 deb http://http.debian.net/debian/ experimental main
3873 EOF
3874 apt-get update
3875 apt-get dist-upgrade
3876 apt-get install -t experimental initscripts sysv-rc sysvinit \
3877 sysvinit-core sysvinit-utils
3878 update-alternatives --config runsystem
3879 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3880
3881 &lt;p&gt;To reboot after switching boot system, you have to use
3882 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
3883 yet a sysvinit process able to receive the signals from the normal
3884 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
3885 upgrading every package and rebooting, the network come up with DHCP
3886 after boot as it should, and the settrans/pkill hack mentioned at the
3887 start is no longer needed. But for some strange reason, there are no
3888 longer any login prompt in the virtual console, so I logged in using
3889 ssh instead.
3890
3891 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
3892 fail some times. No idea what the cause is, but hope the Hurd porters
3893 figure it out. At least Justus said on IRC (#debian-hurd on
3894 irc.debian.org) that they are aware of the problem. A way to reduce
3895 the impact is to upgrade to the Hurd packages built by Justus by
3896 adding this repository to the machine:&lt;/p&gt;
3897
3898 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3899 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
3900 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3901 EOF
3902 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3903
3904 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
3905 http://ftp.debian-ports.org/debian, because some of the packages in
3906 unstable do not yet include the required patches that are lingering in
3907 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
3908
3909 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3910 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
3911 i emacs - GNU Emacs editor (metapackage)
3912 i gdb - GNU Debugger
3913 i hurd-recommended - Miscellaneous translators
3914 i isc-dhcp-client - ISC DHCP client
3915 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3916 i libc-bin - Embedded GNU C Library: Binaries
3917 i libc-dev-bin - Embedded GNU C Library: Development binaries
3918 i libc0.3 - Embedded GNU C Library: Shared libraries
3919 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3920 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3921 i multiarch-support - Transitional package to ensure multiarch compatibilit
3922 i A x11-common - X Window System (X.Org) infrastructure
3923 i xorg - X.Org X Window System
3924 i A xserver-xorg - X.Org X server
3925 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3926 #
3927 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3928
3929 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
3930 X.org did not work out of the box and I never took the time to follow
3931 the porters instructions to fix it. This time I was interested in the
3932 command line stuff.&lt;p&gt;
3933 </description>
3934 </item>
3935
3936 <item>
3937 <title>New chrpath release 0.16</title>
3938 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
3939 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
3940 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
3941 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
3942 find problems in C, C++ and Java code using static source code
3943 analysis. It can detect a lot of different problems, and is very
3944 useful to find memory and locking bugs in the error handling part of
3945 the source. The company behind it provide
3946 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
3947 a community service&lt;/a&gt;, and many hundred free software projects are
3948 already checked. A few days ago I decided to have a closer look at
3949 the Coverity system, and discovered that the
3950 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
3951 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
3952 projects I am involved with was already registered. But these are
3953 fairly big, and I would also like to have a small and easy project to
3954 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
3955 checking of the chrpath project&lt;/a&gt;. It was
3956 added to the checker and discovered seven potential defects. Six of
3957 these were real, mostly resource &quot;leak&quot; when the program detected an
3958 error. Nothing serious, as the resources would be released a fraction
3959 of a second later when the program exited because of the error, but it
3960 is nice to do it right in case the source of the program some time in
3961 the future end up in a library. Having fixed all defects and added
3962 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
3963 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
3964 publish a new release. These are the release notes:&lt;/p&gt;
3965
3966 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
3967
3968 &lt;ul&gt;
3969
3970 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
3971 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
3972 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
3973
3974 &lt;/ul&gt;
3975
3976 &lt;p&gt;You can
3977 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3978 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
3979 project if something is wrong with the new release. The test suite
3980 did not discover any old errors, so if you find a new one, please also
3981 include a test suite check.&lt;/p&gt;
3982 </description>
3983 </item>
3984
3985 <item>
3986 <title>New chrpath release 0.15</title>
3987 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
3988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
3989 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
3990 <description>&lt;p&gt;After many years break from the package and a vain hope that
3991 development would be continued by someone else, I finally pulled my
3992 acts together this morning and wrapped up a new release of chrpath,
3993 the command line tool to modify the rpath and runpath of already
3994 compiled ELF programs. The update was triggered by the persistence of
3995 Isha Vishnoi at IBM, which needed a new config.guess file to get
3996 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
3997 is working on. I checked the
3998 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
3999 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4000 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4001 packages for interesting patches (failed to find the source from
4002 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4003 These are the release notes:&lt;/p&gt;
4004
4005 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4006
4007 &lt;ul&gt;
4008
4009 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4010 with newer architectures. Thanks to isha vishnoi for the heads
4011 up.&lt;/li&gt;
4012
4013 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4014
4015 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4016 Matthias Klose.&lt;/li&gt;
4017
4018 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4019 Petr Machata found in Fedora.&lt;/li&gt;
4020
4021 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4022 .dynamic is a NULL terminated string. Based on patch found in
4023 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4024
4025 &lt;/ul&gt;
4026
4027 &lt;p&gt;You can
4028 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4029 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4030 project if something is wrong with the new release. The test suite
4031 did not discover any old errors, so if you find a new one, please also
4032 include a testsuite check.&lt;/p&gt;
4033 </description>
4034 </item>
4035
4036 <item>
4037 <title>Debian init.d boot script example for rsyslog</title>
4038 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4040 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4041 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4042 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4043 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4044 init.d scripts at all. Here is an example init.d script, ie a rewrite
4045 of /etc/init.d/rsyslog:&lt;/p&gt;
4046
4047 &lt;p&gt;&lt;pre&gt;
4048 #!/lib/init/init-d-script
4049 ### BEGIN INIT INFO
4050 # Provides: rsyslog
4051 # Required-Start: $remote_fs $time
4052 # Required-Stop: umountnfs $time
4053 # X-Stop-After: sendsigs
4054 # Default-Start: 2 3 4 5
4055 # Default-Stop: 0 1 6
4056 # Short-Description: enhanced syslogd
4057 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4058 # It is quite compatible to stock sysklogd and can be
4059 # used as a drop-in replacement.
4060 ### END INIT INFO
4061 DESC=&quot;enhanced syslogd&quot;
4062 DAEMON=/usr/sbin/rsyslogd
4063 &lt;/pre&gt;&lt;/p&gt;
4064
4065 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4066 script was 137 lines, and the above is just 15 lines, most of it meta
4067 info/comments.&lt;/p&gt;
4068
4069 &lt;p&gt;How to do this, you ask? Well, one create a new script
4070 /lib/init/init-d-script looking something like this:
4071
4072 &lt;p&gt;&lt;pre&gt;
4073 #!/bin/sh
4074
4075 # Define LSB log_* functions.
4076 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4077 # and status_of_proc is working.
4078 . /lib/lsb/init-functions
4079
4080 #
4081 # Function that starts the daemon/service
4082
4083 #
4084 do_start()
4085 {
4086 # Return
4087 # 0 if daemon has been started
4088 # 1 if daemon was already running
4089 # 2 if daemon could not be started
4090 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4091 || return 1
4092 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4093 $DAEMON_ARGS \
4094 || return 2
4095 # Add code here, if necessary, that waits for the process to be ready
4096 # to handle requests from services started subsequently which depend
4097 # on this one. As a last resort, sleep for some time.
4098 }
4099
4100 #
4101 # Function that stops the daemon/service
4102 #
4103 do_stop()
4104 {
4105 # Return
4106 # 0 if daemon has been stopped
4107 # 1 if daemon was already stopped
4108 # 2 if daemon could not be stopped
4109 # other if a failure occurred
4110 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
4111 RETVAL=&quot;$?&quot;
4112 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
4113 # Wait for children to finish too if this is a daemon that forks
4114 # and if the daemon is only ever run from this initscript.
4115 # If the above conditions are not satisfied then add some other code
4116 # that waits for the process to drop all resources that could be
4117 # needed by services started subsequently. A last resort is to
4118 # sleep for some time.
4119 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
4120 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
4121 # Many daemons don&#39;t delete their pidfiles when they exit.
4122 rm -f $PIDFILE
4123 return &quot;$RETVAL&quot;
4124 }
4125
4126 #
4127 # Function that sends a SIGHUP to the daemon/service
4128 #
4129 do_reload() {
4130 #
4131 # If the daemon can reload its configuration without
4132 # restarting (for example, when it is sent a SIGHUP),
4133 # then implement that here.
4134 #
4135 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
4136 return 0
4137 }
4138
4139 SCRIPTNAME=$1
4140 scriptbasename=&quot;$(basename $1)&quot;
4141 echo &quot;SN: $scriptbasename&quot;
4142 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
4143 script=&quot;$1&quot;
4144 shift
4145 . $script
4146 else
4147 exit 0
4148 fi
4149
4150 NAME=$(basename $DAEMON)
4151 PIDFILE=/var/run/$NAME.pid
4152
4153 # Exit if the package is not installed
4154 #[ -x &quot;$DAEMON&quot; ] || exit 0
4155
4156 # Read configuration variable file if it is present
4157 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
4158
4159 # Load the VERBOSE setting and other rcS variables
4160 . /lib/init/vars.sh
4161
4162 case &quot;$1&quot; in
4163 start)
4164 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
4165 do_start
4166 case &quot;$?&quot; in
4167 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4168 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4169 esac
4170 ;;
4171 stop)
4172 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
4173 do_stop
4174 case &quot;$?&quot; in
4175 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4176 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4177 esac
4178 ;;
4179 status)
4180 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
4181 ;;
4182 #reload|force-reload)
4183 #
4184 # If do_reload() is not implemented then leave this commented out
4185 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
4186 #
4187 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
4188 #do_reload
4189 #log_end_msg $?
4190 #;;
4191 restart|force-reload)
4192 #
4193 # If the &quot;reload&quot; option is implemented then remove the
4194 # &#39;force-reload&#39; alias
4195 #
4196 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
4197 do_stop
4198 case &quot;$?&quot; in
4199 0|1)
4200 do_start
4201 case &quot;$?&quot; in
4202 0) log_end_msg 0 ;;
4203 1) log_end_msg 1 ;; # Old process is still running
4204 *) log_end_msg 1 ;; # Failed to start
4205 esac
4206 ;;
4207 *)
4208 # Failed to stop
4209 log_end_msg 1
4210 ;;
4211 esac
4212 ;;
4213 *)
4214 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
4215 exit 3
4216 ;;
4217 esac
4218
4219 :
4220 &lt;/pre&gt;&lt;/p&gt;
4221
4222 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
4223 lot. I did not really polish the approach, so it might not always
4224 work out of the box, but you get the idea. I did not try very hard to
4225 optimize it nor make it more robust either.&lt;/p&gt;
4226
4227 &lt;p&gt;A better argument for switching init system in Debian than reducing
4228 the size of init scripts (which is a good thing to do anyway), is to
4229 get boot system that is able to handle the kernel events sensibly and
4230 robustly, and do not depend on the boot to run sequentially. The boot
4231 and the kernel have not behaved sequentially in years.&lt;/p&gt;
4232 </description>
4233 </item>
4234
4235 <item>
4236 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
4237 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
4238 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
4239 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
4240 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
4241 remote display access is the preferred solution with oVirt and RedHat
4242 Enterprise Virtualization, and I was sad to discover the other day
4243 that the browser plugin needed to use these systems seamlessly was
4244 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
4245 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
4246 2013-04-01, so I decided to wrap up a package based on the great work
4247 from Cajus Pollmeier and put it in a collab-maint maintained git
4248 repository to get a package I could use. I would very much like
4249 others to help me maintain the package (or just take over, I do not
4250 mind), but as no-one had volunteered so far, I just uploaded it to
4251 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
4252
4253 &lt;p&gt;The source is now available from
4254 &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;
4255 </description>
4256 </item>
4257
4258 <item>
4259 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
4260 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
4261 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
4262 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
4263 <description>&lt;p&gt;The
4264 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
4265 program is a a very nice system to create virtual machine images. It
4266 create a image file, add a partition table, mount it and run
4267 debootstrap in the mounted directory to create a Debian system on a
4268 stick. Yesterday, I decided to try to teach it how to make images for
4269 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
4270 of a plan to simplify the build system for
4271 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
4272 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
4273 the virtualbox images, but its current build system made multistrap
4274 based system for Dreamplug images, and it is lacking support for
4275 Raspberry Pi.&lt;/p&gt;
4276
4277 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
4278 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4279 code and adjusted it to be able to build armel images on my amd64
4280 Debian laptop. I ended up giving vmdebootstrap five new options,
4281 allowing me to replicate the image creation process I use to make
4282 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
4283 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
4284 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
4285 call debootstrap with --foreign and to copy the handler into the
4286 generated chroot before running the second stage. This allow
4287 vmdebootstrap to create armel images on an amd64 host. Next I added
4288 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
4289 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
4290 given file system type, allowing me to create an image with a vfat
4291 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
4292 variant&lt;/tt&gt; option to allow me to create smaller images without the
4293 Debian base system packages installed. Finally, I added an option
4294 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
4295 as a boot loader. It is not needed on the Raspberry Pi and probably
4296 most other non-x86 architectures. The changes were accepted by the
4297 upstream author of vmdebootstrap yesterday and today, and is now
4298 available from
4299 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
4300 upstream project page&lt;/a&gt;.&lt;/p&gt;
4301
4302 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
4303 create a small script (the customize script) to add the non-free
4304 binary blob needed to boot the Raspberry Pi and the APT source
4305 list:&lt;/p&gt;
4306
4307 &lt;p&gt;&lt;pre&gt;
4308 #!/bin/sh
4309 set -e # Exit on first error
4310 rootdir=&quot;$1&quot;
4311 cd &quot;$rootdir&quot;
4312 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4313 deb http://http.debian.net/debian/ jessie main contrib non-free
4314 EOF
4315 # Install non-free binary blob needed to boot Raspberry Pi. This
4316 # install a kernel somewhere too.
4317 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4318 -O $rootdir/usr/bin/rpi-update
4319 chmod a+x $rootdir/usr/bin/rpi-update
4320 mkdir -p $rootdir/lib/modules
4321 touch $rootdir/boot/start.elf
4322 chroot $rootdir rpi-update
4323 &lt;/pre&gt;&lt;/p&gt;
4324
4325 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4326 to build the image:&lt;/p&gt;
4327
4328 &lt;pre&gt;
4329 sudo ./vmdebootstrap \
4330 --variant minbase \
4331 --arch armel \
4332 --distribution jessie \
4333 --mirror http://http.debian.net/debian \
4334 --image test.img \
4335 --size 600M \
4336 --bootsize 64M \
4337 --boottype vfat \
4338 --log-level debug \
4339 --verbose \
4340 --no-kernel \
4341 --no-extlinux \
4342 --root-password raspberry \
4343 --hostname raspberrypi \
4344 --foreign /usr/bin/qemu-arm-static \
4345 --customize `pwd`/customize \
4346 --package netbase \
4347 --package git-core \
4348 --package binutils \
4349 --package ca-certificates \
4350 --package wget \
4351 --package kmod
4352 &lt;/pre&gt;&lt;/p&gt;
4353
4354 &lt;p&gt;The list of packages being installed are the ones needed by
4355 rpi-update to make the image bootable on the Raspberry Pi, with the
4356 exception of netbase, which is needed by debootstrap to find
4357 /etc/hosts with the minbase variant. I really wish there was a way to
4358 set up an Raspberry Pi using only packages in the Debian archive, but
4359 that is not possible as far as I know, because it boots from the GPU
4360 using a non-free binary blob.&lt;/p&gt;
4361
4362 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4363 probably a few others installed. I have not checked the complete
4364 build dependency list.&lt;/p&gt;
4365
4366 &lt;p&gt;The resulting image will not use the hardware floating point unit
4367 on the Raspberry PI, because the armel architecture in Debian is not
4368 optimized for that use. So the images created will be a bit slower
4369 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4370 </description>
4371 </item>
4372
4373 <item>
4374 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4375 <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>
4376 <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>
4377 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4378 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4379 wider attention. I recommend signing and donating to each one of
4380 these. :)&lt;/p&gt;
4381
4382 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4383 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4384 Women program which is a Google Summer of Code like initiative to get
4385 more women involved in free software. One debian sponsor has offered
4386 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4387 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4388 hope you will to. :)&lt;/p&gt;
4389
4390 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4391 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4392 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4393 take place these days, and their need to fund the work. I&#39;ve already
4394 donated. Are you next?&lt;/p&gt;
4395
4396 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4397 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4398 statement under the heading
4399 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4400 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4401 Norwegian government. So far 499 signatures. I hope you will sign it
4402 too.&lt;/p&gt;
4403 </description>
4404 </item>
4405
4406 <item>
4407 <title>Videos about the Freedombox project - for inspiration and learning</title>
4408 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4410 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4411 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4412 project&lt;/a&gt; have been going on for a while, and have presented the
4413 vision, ideas and solution several places. Here is a little
4414 collection of videos of talks and presentation of the project.&lt;/p&gt;
4415
4416 &lt;ul&gt;
4417
4418 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4419 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4420
4421 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4422 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4423
4424 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4425 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4426 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4427 (Youtube)&lt;/li&gt;
4428
4429 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4430 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4431
4432 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4433 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4434
4435 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4436 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4437 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4438
4439 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4440 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4441 (Youtube)&lt;/li&gt;
4442
4443 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4444 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4445
4446 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4447 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4448
4449 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4450 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4451 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4452
4453 &lt;/ul&gt;
4454
4455 &lt;p&gt;A larger list is available from
4456 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4457 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4458
4459 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4460 Jessie is coming along quite well, and soon both Owncloud and using
4461 Tor should be available for testers of the Freedombox solution. :) In
4462 a few weeks I hope everything needed to test it is included in Debian.
4463 The withsqlite package is already in Debian, and the plinth package is
4464 pending in NEW. The third and vital part of that puzzle is the
4465 metapackage/setup framework, which is still pending an upload. Join
4466 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4467 (#freedombox on irc.debian.org)&lt;/a&gt; and
4468 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4469 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4470 </description>
4471 </item>
4472
4473 <item>
4474 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4475 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4477 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4478 <description>&lt;p&gt;I was introduced to the
4479 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4480 in 2010, when Eben Moglen presented his vision about serving the need
4481 of non-technical people to keep their personal information private and
4482 within the legal protection of their own homes. The idea is to give
4483 people back the power over their network and machines, and return
4484 Internet back to its intended peer-to-peer architecture. Instead of
4485 depending on a central service, the Freedombox will give everyone
4486 control over their own basic infrastructure.&lt;/p&gt;
4487
4488 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4489 taken priority. But this summers nasty news about the misuse of trust
4490 and privilege exercised by the &quot;western&quot; intelligence gathering
4491 communities increased my eagerness to contribute to a point where I
4492 actually started working on the project a while back.&lt;/p&gt;
4493
4494 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4495 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4496 create a simple and cheap Debian based appliance that anyone can hook
4497 up in their home and get access to secure and private services and
4498 communication. The initial deployment platform have been the
4499 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4500 which is a piece of hardware I do not own. So to be able to test what
4501 the current Freedombox setup look like, I had to come up with a way to install
4502 it on some hardware I do have access to. I have rewritten the
4503 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4504 image build framework to use .deb packages instead of only copying
4505 setup into the boot images, and thanks to this rewrite I am able to
4506 set up any machine supported by Debian Wheezy as a Freedombox, using
4507 the previously mentioned deb (and a few support debs for packages
4508 missing in Debian).&lt;/p&gt;
4509
4510 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4511 scripts
4512 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4513 and a administrative web interface
4514 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4515 withsqlite), as well as a privacy enhancing proxy based on
4516 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4517 (freedombox-privoxy). There is also a web/javascript based XMPP
4518 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4519 trying (unsuccessfully so far) to talk to the XMPP server
4520 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4521 web interface is pluggable, and the goal is to use it to enable OpenID
4522 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4523 this is really working yet, see
4524 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4525 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4526 on github at the moment. The HTTP proxy is operational out of the
4527 box, and the admin web interface can be used to add/remove plinth
4528 users. I&#39;ve not been able to do anything else with it so far, but
4529 know there are several branches spread around github and other places
4530 with lots of half baked features.&lt;/p&gt;
4531
4532 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4533 following recipes should work to give you a test machine to poke
4534 at.&lt;/p&gt;
4535
4536 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
4537
4538 &lt;ol&gt;
4539
4540 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
4541 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
4542 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
4543 to the Debian installer:&lt;p&gt;
4544 &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;
4545
4546 &lt;li&gt;Answer the few language/region/password questions and pick disk to
4547 install on.&lt;/li&gt;
4548
4549 &lt;li&gt;When the installation is finished and the machine have rebooted a
4550 few times, your Freedombox is ready for testing.&lt;/li&gt;
4551
4552 &lt;/ol&gt;
4553
4554 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
4555
4556 &lt;ol&gt;
4557
4558 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
4559 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
4560 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
4561 &lt;pre&gt;
4562 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
4563 &lt;/pre&gt;&lt;/li&gt;
4564 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
4565 &lt;pre&gt;
4566 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4567 apt-key add -
4568 apt-get update
4569 apt-get install freedombox-setup
4570 /usr/lib/freedombox/setup
4571 &lt;/pre&gt;&lt;/li&gt;
4572 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
4573
4574 &lt;/ol&gt;
4575
4576 &lt;p&gt;You can test it on other architectures too, but because the
4577 freedombox-privoxy package is binary, it will only work as intended on
4578 the architectures where I have had time to build the binary and put it
4579 in my APT repository. But do not let this stop you. It is only a
4580 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
4581
4582 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
4583 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
4584 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
4585 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
4586
4587 &lt;p&gt;Please let me know if this works for you, or if you have any
4588 problems. We gather on the IRC channel
4589 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
4590 irc.debian.org and the
4591 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
4592 mailing list&lt;/a&gt;.&lt;/p&gt;
4593
4594 &lt;p&gt;Once you get your freedombox operational, you can visit
4595 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
4596 welcome screen (dead end - do not be surprised if you are unable to
4597 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
4598 to look at the rest of plinth. The default user is &#39;admin&#39; and the
4599 default password is &#39;secret&#39;.&lt;/p&gt;
4600 </description>
4601 </item>
4602
4603 <item>
4604 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
4605 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
4606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
4607 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
4608 <description>&lt;p&gt;Earlier, I reported about
4609 &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
4610 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
4611 told by IBM that the original disk should be thrown away. And as
4612 there no longer was a problem if I bricked the firmware, I decided
4613 today to try to install Intel firmware to replace the Lenovo firmware
4614 currently on the disk.&lt;/p&gt;
4615
4616 &lt;p&gt;I searched the Intel site for firmware, and found
4617 &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;
4618 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4619 according to the site should contain the latest firmware for SSD
4620 disks. I inserted the broken disk in one of my spare laptops and
4621 booted the ISO from a USB stick. The disk was recognized, but the
4622 program claimed the newest firmware already were installed and refused
4623 to insert any Intel firmware. So no change, and the disk is still
4624 unable to handle write load. :( I guess the only way to get them
4625 working would be if Lenovo releases new firmware. No idea how likely
4626 that is. Anyway, just blogging about this test for completeness. I
4627 got a working Samsung disk, and see no point in spending more time on
4628 the broken disks.&lt;/p&gt;
4629 </description>
4630 </item>
4631
4632 <item>
4633 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
4634 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
4635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
4636 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
4637 <description>&lt;p&gt;Today I switched to
4638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
4639 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
4640 my new Thinkpad X230, which was delivered with an
4641 &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
4642 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
4643 sustained writes. My hardware supplier have been very forthcoming in
4644 trying to find a solution, and after first trying with another
4645 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
4646 disk instead to fix it once and for all. The Samsung disk survived
4647 the installation of Debian with encrypted disks (filling the disk with
4648 random data during installation killed the first two), and I thus
4649 decided to trust it with my data. I have installed it as a Debian Edu
4650 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4651 server at home using Kerberos and LDAP, and will use it as my work
4652 station from now on.&lt;/p&gt;
4653
4654 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
4655 Debian Wheezy default installation need to be tuned a bit to increase
4656 performance and increase life time of the disk. The Linux kernel and
4657 user space applications do not yet adjust automatically to such
4658 environment. To make it easier for my self, I created a draft Debian
4659 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
4660 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
4661 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
4662 is set up to adjust the setup of the machine by just installing the
4663 package. If there is any non-SSD disk in the machine, the package
4664 will refuse to install, as I did not try to write any logic to sort
4665 file systems in SSD and non-SSD file systems.&lt;/p&gt;
4666
4667 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
4668 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4669 where I set up the machine with one large encrypted partition (in
4670 addition to /boot), put LVM on top of this and set up partitions on
4671 top of this again. See the README file in the package source for the
4672 references I used to pick the settings. At the moment these
4673 parameters are tuned:&lt;/p&gt;
4674
4675 &lt;ul&gt;
4676
4677 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
4678 (adding discard to /etc/crypttab)&lt;/li&gt;
4679
4680 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
4681 this case a cryptsetup partition) by changing issue_discards from
4682 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
4683
4684 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
4685 systems.&lt;/li&gt;
4686
4687 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
4688 /etc/fstab.&lt;/li&gt;
4689
4690 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
4691
4692 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
4693 cron.daily).&lt;/li&gt;
4694
4695 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
4696 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
4697
4698 &lt;/ul&gt;
4699
4700 &lt;p&gt;During installation, I cancelled the part where the installer fill
4701 the disk with random data, as this would kill the SSD performance for
4702 little gain. My goal with the encrypted file system is to ensure
4703 those stealing my laptop end up with a brick and not a working
4704 computer. I have no hope in keeping the really resourceful people
4705 from getting the data on the disk (see
4706 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
4707 Thus I concluded that adding the discard option to crypttab is the
4708 right thing to do.&lt;/p&gt;
4709
4710 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
4711 it for SSD, but others recommended deadline and a benchmark I found
4712 indicated that deadline might be better for interactive use.&lt;/p&gt;
4713
4714 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
4715 and ext4, but read that it would give a performance hit ever time a
4716 file is removed, and thought it best to that that slowdown once a day
4717 instead of during my work.&lt;/p&gt;
4718
4719 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4720 this is already done by Debian Edu.&lt;/p&gt;
4721
4722 &lt;p&gt;I have not yet started on the user space tuning. I expect
4723 iceweasel need some tuning, and perhaps other applications too, but
4724 have not yet had time to investigate those parts.&lt;/p&gt;
4725
4726 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
4727 there.&lt;/p&gt;
4728
4729 &lt;p&gt;As for the answer to the question in the title of this blog post,
4730 as far as I know, the only solution I know about is to replace the
4731 disk. It might be possible to flash it with Intel firmware instead of
4732 the Lenovo firmware. But I have not tried and did not want to do so
4733 without approval from Lenovo as I wanted to keep the warranty on the
4734 disk until a solution was found and they wanted the broken disks
4735 back.&lt;/p&gt;
4736 </description>
4737 </item>
4738
4739 <item>
4740 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
4741 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
4742 <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>
4743 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
4744 <description>&lt;p&gt;A few days ago, I wrote about
4745 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
4746 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
4747 was dying during installation because it is unable to cope with
4748 sustained write. My supplier is in contact with
4749 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
4750 replacement disk to try to fix the problem. They decided to send an
4751 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
4752
4753 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
4754 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4755 same firmware version as the original. This time my hope raised
4756 slightly as the installation progressed, as the original disk used to
4757 die after 4-7% of the disk was written to, while this time it kept
4758 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
4759 died again and I was back on square one. I still do not have a new
4760 laptop with a disk I can trust. I can not live with a disk that might
4761 lock up when I download a new
4762 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
4763 other large files. I look forward to hearing from my supplier with
4764 the next proposal from Lenovo.&lt;/p&gt;
4765
4766 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
4767 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4768 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4769 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
4770 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4771 P/N 45N8295, P0C38732.&lt;/p&gt;
4772
4773 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
4774 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
4775 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4776 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
4777 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4778 P/N 45N8295, P0C38732.&lt;/p&gt;
4779
4780 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
4781 SA, date and WNPP values. Mentioning all the details here in case
4782 someone is able to use the information to find a way to identify the
4783 failing disk among working ones (if any such working disk actually
4784 exist).&lt;/p&gt;
4785 </description>
4786 </item>
4787
4788 <item>
4789 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
4790 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
4791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
4792 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
4793 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
4794 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4795 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
4796 member assosiation NUUG&lt;/a&gt; and
4797 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
4798 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
4799 Bitraf&lt;/a&gt;.&lt;/p&gt;
4800
4801 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
4802 welcome, and there is no fee to participate. There is on the other
4803 hand limited space, and only room for 30 people. Please put your name
4804 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
4805 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
4806 </description>
4807 </item>
4808
4809 <item>
4810 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
4811 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
4812 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
4813 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
4814 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
4815 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
4816 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
4817 time to spend on it, and it took a while to find a model I believe
4818 will do the job, but two days ago the replacement finally arrived. I
4819 ended up picking a
4820 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
4821 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4822 a roaming workstation, and it seemed to work flawlessly. But my
4823 second installation with encrypted disk was not as successful. More
4824 on that below.&lt;/p&gt;
4825
4826 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4827 important requirements (robust and with a good keyboard) are never
4828 listed in the feature list. But I did get good help from the search
4829 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4830 allowed me to limit the list of interesting laptops based on my other
4831 requirements. A bit surprising that SSD disk are not disks according
4832 to that search interface, so I had to drop specifying the number of
4833 disks from my search parameters. I also asked around among friends to
4834 get their impression on keyboards and robustness.&lt;/p&gt;
4835
4836 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
4837 X41. I am not quite convinced about the keyboard, as it is
4838 significantly wider than my old keyboard, and I have to stretch my
4839 hand a lot more to reach the edges. But the key response is fairly
4840 good and the individual key shape is fairly easy to handle, so I hope
4841 I will get used to it. My old X40 was starting to fail, and I really
4842 needed a new laptop now. :)&lt;/p&gt;
4843
4844 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
4845 visit to the BIOS during boot it disable it.&lt;/p&gt;
4846
4847 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
4848 lock up during load. And this happen when installing Debian Wheezy
4849 with encrypted disk, while the disk is being filled with random data.
4850 I also tested to install Ubuntu Raring, and it happen there too if I
4851 reenable the code to fill the disk with random data (it is disabled by
4852 default in Ubuntu). And the bug with is already known. It was
4853 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
4854 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
4855 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4856 kernel developers as
4857 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
4858 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
4859 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4860 Lenovo forums, both for
4861 &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
4862 2012-11-10&lt;/a&gt; and for
4863 &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
4864 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
4865 reports state that the disk lock up during use if many writes are done
4866 on the disk, so it is much no use to work around the installation
4867 problem and end up with a computer that can lock up at any moment.
4868 There is even a
4869 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
4870 available&lt;/a&gt; that will lock up the hard drive after running a few
4871 minutes by writing to a file.&lt;/p&gt;
4872
4873 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
4874 contacting PCHELP Norway (request 01D1FDP) which handle support
4875 requests for Lenovo, his first suggestion was to upgrade the disk
4876 firmware. Unfortunately there is no newer firmware available from
4877 Lenovo, as my disk already have the most recent one (version LF1i). I
4878 hope to hear more from him today and hope the problem can be
4879 fixed. :)&lt;/p&gt;
4880 </description>
4881 </item>
4882
4883 <item>
4884 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
4885 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
4886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
4887 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
4888 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
4889 trusty old Thinkpad X41. Unfortunately I did not have much time to
4890 spend on it, but today the replacement finally arrived. I ended up
4891 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
4892 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
4893 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4894 this, it is installing what I hope will be a more final installation,
4895 with a encrypted hard drive to ensure any dope head stealing it end up
4896 with an expencive door stop.&lt;/p&gt;
4897
4898 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4899 important requirements (robust and with a good keyboard) are never
4900 listed in the feature list. But I did get good help from the search
4901 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4902 allowed me to limit the list of interesting laptops based on my other
4903 requirements. A bit surprising that SSD disk are not disks, so I had
4904 to drop number of disks from my search parameters.&lt;/p&gt;
4905
4906 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
4907 wider than my old keyboard, and I have to stretch my hand a lot more
4908 to reach the edges. But the key response is fairly good and the
4909 individual key shape is fairly easy to handle, so I hope I will get
4910 used to it. My old X40 was starting to fail, and I really needed a
4911 new laptop now. :)&lt;/p&gt;
4912
4913 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
4914 </description>
4915 </item>
4916
4917 <item>
4918 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
4919 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
4920 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
4921 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
4922 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
4923 perfectly capable of, and I have to do it manually to get things
4924 working. One such task is to find out what firmware packages are
4925 needed to get the hardware on my computer working. Most often this
4926 affect the wifi card, but some times it even affect the RAID
4927 controller or the ethernet card. Today I pushed version 0.4 of the
4928 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
4929 including a new script isenkram-autoinstall-firmware handling the
4930 process of asking all the loaded kernel modules what firmware files
4931 they want, find debian packages providing these files and install the
4932 debian packages. Here is a test run on my laptop:&lt;/p&gt;
4933
4934 &lt;p&gt;&lt;pre&gt;
4935 # isenkram-autoinstall-firmware
4936 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4937 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4938 info: locating packages with the requested firmware files
4939 info: Updating APT sources after adding non-free APT source
4940 info: trying to install firmware-ipw2x00
4941 firmware-ipw2x00
4942 firmware-ipw2x00
4943 Preconfiguring packages ...
4944 Selecting previously deselected package firmware-ipw2x00.
4945 (Reading database ... 259727 files and directories currently installed.)
4946 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4947 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
4948 #
4949 &lt;/pre&gt;&lt;/p&gt;
4950
4951 &lt;p&gt;When all the requested firmware is present, a simple message is
4952 printed instead:&lt;/p&gt;
4953
4954 &lt;p&gt;&lt;pre&gt;
4955 # isenkram-autoinstall-firmware
4956 info: did not find any firmware files requested by loaded kernel modules. exiting
4957 #
4958 &lt;/pre&gt;&lt;/p&gt;
4959
4960 &lt;p&gt;It could use some polish, but it is already working well and saving
4961 me some time when setting up new machines. :)&lt;/p&gt;
4962
4963 &lt;p&gt;So, how does it work? It look at the set of currently loaded
4964 kernel modules, and look up each one of them using modinfo, to find
4965 the firmware files listed in the module meta-information. Next, it
4966 download the Contents file from a nearby APT mirror, and search for
4967 the firmware files in this file to locate the package with the
4968 requested firmware file. If the package is in the non-free section, a
4969 non-free APT source is added and the package is installed using
4970 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
4971 machine.&lt;/p&gt;
4972
4973 &lt;p&gt;I hope someone find time to implement a more polished version of
4974 this script as part of the hw-detect debian-installer module, to
4975 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
4976 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
4977 firmware during a PXE install when the packages already are available
4978 from the nearby Debian mirror.&lt;/p&gt;
4979 </description>
4980 </item>
4981
4982 <item>
4983 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
4984 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
4985 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
4986 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
4987 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4988 the screen just turn black when Linux boot, either during installation
4989 or on first boot from the hard disk. I&#39;ve seen it once in a while the
4990 last few years, but only recently understood the cause. I&#39;ve seen it
4991 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4992 The reason seem to be in the wiring of some laptops. The system to
4993 control the screen background light is inverted, so when Linux try to
4994 turn the brightness fully on, it end up turning it off instead. I do
4995 not know which Linux drivers are affected, but this post is about the
4996 i915 driver used by the
4997 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4998 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
4999
5000 &lt;p&gt;The problem can be worked around two ways. Either by adding
5001 i915.invert_brightness=1 as a kernel option, or by adding a file in
5002 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5003 option when it load the i915 kernel module. On Debian and Ubuntu, it
5004 can be done by running these commands as root:&lt;/p&gt;
5005
5006 &lt;pre&gt;
5007 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5008 update-initramfs -u -k all
5009 &lt;/pre&gt;
5010
5011 &lt;p&gt;Since March 2012 there is
5012 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5013 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5014 hardware have this problem, and get the driver to invert the
5015 brightness setting automatically. To use it, one need to add a row in
5016 &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
5017 intel_quirks array&lt;/a&gt; in the driver source
5018 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5019 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5020 number (vendor number 8086 is assumed) and subdevice vendor and device
5021 number.&lt;/p&gt;
5022
5023 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5024 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5025
5026 &lt;p&gt;&lt;pre&gt;
5027 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5028 3rd Gen Core processor Graphics Controller [8086:0156] \
5029 (rev 09) (prog-if 00 [VGA controller])
5030 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5031 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5032 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5033 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5034 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5035 Latency: 0
5036 Interrupt: pin A routed to IRQ 42
5037 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5038 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5039 Region 4: I/O ports at 4000 [size=64]
5040 Expansion ROM at &lt;unassigned&gt; [disabled]
5041 Capabilities: &lt;access denied&gt;
5042 Kernel driver in use: i915
5043 &lt;/pre&gt;&lt;/p&gt;
5044
5045 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5046
5047 &lt;p&gt;&lt;pre&gt;
5048 struct intel_quirk intel_quirks[] = {
5049 ...
5050 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5051 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5052 ...
5053 }
5054 &lt;/pre&gt;&lt;/p&gt;
5055
5056 &lt;p&gt;According to the kernel module instructions (as seen using
5057 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5058 invert_brightness flag should be sent to the
5059 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5060 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5061 developers. But my email about the laptop sent 2013-06-03 have not
5062 yet shown up in
5063 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5064 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5065 emails from non-subscribers. Because of this, I sent my patch also to
5066 the Debian bug tracking system instead as
5067 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5068 sure the patch is not lost.&lt;/p&gt;
5069
5070 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5071 with this problem working properly with Linux. If you use Gnome, your
5072 worries should be over at this point. But if you use KDE, there is
5073 something in KDE ignoring the invert_brightness setting and turning on
5074 the screen during login. I&#39;ve reported it to Debian as
5075 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5076 have no idea yet how to figure out exactly what subsystem is doing
5077 this. Perhaps you can help? Perhaps you know what the Gnome
5078 developers did to handle this, and this can give a clue to the KDE
5079 developers? Or you know where in KDE the screen brightness is changed
5080 during login? If so, please update the BTS report (or get in touch if
5081 you do not know how to update BTS).&lt;/p&gt;
5082
5083 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5084 acpi_backlight=vendor, to disable ACPI backlight support completely,
5085 as the ACPI information on the machine is trash and it is better to
5086 leave it to the intel video driver to control the screen
5087 backlight.&lt;/p&gt;
5088 </description>
5089 </item>
5090
5091 <item>
5092 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5093 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5094 <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>
5095 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5096 <description>&lt;p&gt;Two days ago, I asked
5097 &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
5098 I could install Linux on a Packard Bell EasyNote LV computer
5099 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5100 with the obstacles put in the way of Linux users on a laptop with UEFI
5101 and Windows 8.&lt;/p&gt;
5102
5103 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5104 secure booting or fast boot. I suspect fast boot was the problem,
5105 causing the firmware to boot directly from HD without considering any
5106 key presses and alternative devices, but do not know UEFI settings
5107 enough to tell.&lt;/p&gt;
5108
5109 &lt;p&gt;There is no way to install Linux on the machine in question without
5110 opening the box and disconnecting the hard drive! This is as far as I
5111 can tell, the only way to get access to the firmware setup menu
5112 without accepting the Windows 8 license agreement. I am told (and
5113 found description on how to) that it is possible to configure the
5114 firmware setup once booted into Windows 8. But as I believe the terms
5115 of that agreement are completely unacceptable, accepting the license
5116 was never an alternative. I do not enter agreements I do not intend
5117 to follow.&lt;/p&gt;
5118
5119 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
5120 waste many hours on this, but luckily there was a way to get it to
5121 work. But I would not recommend it to anyone planning to run Linux on
5122 it, and I have become sceptical to Windows 8 certified laptops. Is
5123 this the way Linux will be forced out of the market place, by making
5124 it close to impossible for &quot;normal&quot; users to install Linux without
5125 accepting the Microsoft Windows license terms? Or at least not
5126 without risking to loose the warranty?&lt;/p&gt;
5127
5128 &lt;p&gt;I&#39;ve updated the
5129 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
5130 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
5131 do not have to struggle as much as I did to get Linux into the
5132 machine.&lt;/p&gt;
5133
5134 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5135 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
5136 </description>
5137 </item>
5138
5139 <item>
5140 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
5141 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
5142 <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>
5143 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
5144 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
5145 new laptops for my parents and a few others. I bought Packard Bell
5146 Easynote LV to run Kubuntu on and use as their home computer. But I
5147 am completely unable to figure out how to install Linux on it. The
5148 computer is preinstalled with Windows 8, and I suspect it uses UEFI
5149 instead of a BIOS to boot.&lt;/p&gt;
5150
5151 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
5152 to get it to boot the Linux installer from my USB stick. I have yet
5153 to try the DVD install, and still hope it will work. when I turn on
5154 the computer, there is no information on what buttons to press to get
5155 the normal boot menu. I expect to get some boot menu to select PXE or
5156 USB stick booting. When booting, it first ask for the language to
5157 use, then for some regional settings, and finally if I will accept the
5158 Windows 8 terms of use. As these terms are completely unacceptable to
5159 me, I have no other choice but to turn off the computer and try again
5160 to get it to boot the Linux installer.&lt;/p&gt;
5161
5162 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
5163 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5164 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
5165 installed on this machine, please get in touch or update that wiki
5166 page. If I can&#39;t find a way to install Linux, I will have to return
5167 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
5168
5169 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
5170 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
5171 on new Laptops?&lt;/p&gt;
5172 </description>
5173 </item>
5174
5175 <item>
5176 <title>How to transform a Debian based system to a Debian Edu installation</title>
5177 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
5178 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
5179 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
5180 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
5181 an operating system based on Debian intended for use in schools. It
5182 contain a turn-key solution for the computer network provided to
5183 pupils in the primary schools. It provide both the central server,
5184 network boot servers and desktop environments with heaps of
5185 educational software. The project was founded almost 12 years ago,
5186 2001-07-02. If you want to support the project, which is in need for
5187 cash to fund developer gatherings and other project related activity,
5188 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
5189 donate some money&lt;/a&gt;.
5190
5191 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
5192 lists and elsewhere, is the question on how to transform a Debian or
5193 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
5194 hard, and last week I wrote a script to replicate the steps done by
5195 the Debian Edu installer.&lt;/p&gt;
5196
5197 &lt;p&gt;The script,
5198 &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;
5199 in the debian-edu-config package, will go through these six steps and
5200 transform an existing Debian Wheezy or Ubuntu (untested) installation
5201 into a Debian Edu Workstation:&lt;/p&gt;
5202
5203 &lt;ol&gt;
5204
5205 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
5206 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
5207 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
5208 our configuration.&lt;/li&gt;
5209 &lt;li&gt;Preseed debconf database with profile setup in
5210 /etc/debian-edu/config, and run tasksel to install packages
5211 according to the profile specified in the config above,
5212 overriding some of the Debian automation machinery.&lt;/li&gt;
5213 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
5214 that could not be done using preseeding.&lt;/li&gt;
5215 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
5216
5217 &lt;/ol&gt;
5218
5219 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
5220 replicated like this. Disk partitioning and LVM setup, for example.
5221 So this script just assume there is enough disk space to install all
5222 the needed packages.&lt;/p&gt;
5223
5224 &lt;p&gt;The script was created to help a Debian Edu student working on
5225 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
5226 Debian Edu client, and using it he can take the existing
5227 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
5228 transform it into a fully functioning Debian Edu Workstation (or
5229 Roaming Workstation, or whatever :).&lt;/p&gt;
5230
5231 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
5232 If a LXDE based Roaming workstation is wanted instead, modify the
5233 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
5234
5235 &lt;p&gt;&lt;pre&gt;
5236 PROFILE=&quot;Roaming-Workstation&quot;
5237 DESKTOP=&quot;lxde&quot;
5238 &lt;/pre&gt;&lt;/p&gt;
5239
5240 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
5241 the cloud, by starting with a virtual Debian installation at some
5242 virtual hosting service and setting up all the services on first
5243 boot.&lt;/p&gt;
5244 </description>
5245 </item>
5246
5247 <item>
5248 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
5249 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
5250 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
5251 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
5252 <description>&lt;P&gt;In January,
5253 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
5254 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
5255 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
5256 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
5257 marvellous construction system from Denmark. We also created
5258 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
5259 a place to take notes and write down our plans and hopes. And several
5260 people showed up to help. I was very happy to see the effect of my
5261 call. Since the small start, we have a debtags tag
5262 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
5263 tag for LEGO related packages, and now count 10 packages related to
5264 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
5265
5266 &lt;p&gt;&lt;table&gt;
5267 &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;
5268 &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;
5269 &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;
5270 &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;
5271 &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;
5272 &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;
5273 &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;
5274 &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;
5275 &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;
5276 &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;
5277 &lt;/table&gt;&lt;/p&gt;
5278
5279 &lt;p&gt;Some of these are available in Wheezy, and all but one are
5280 currently available in Jessie/testing. leocad is so far only
5281 available in experimental.&lt;/p&gt;
5282
5283 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
5284 adding the rest of the great free software tools available on Linux
5285 for LEGO designers.&lt;/p&gt;
5286 </description>
5287 </item>
5288
5289 <item>
5290 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
5291 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
5292 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
5293 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
5294 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
5295 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
5296 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
5297 Debian release, and I expect to move my machines at home over to it fairly
5298 soon.&lt;/p&gt;
5299
5300 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
5301 in particular make me very happy to see included. The
5302 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
5303 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
5304 included for the first time. Alongside similar programs like
5305 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5306 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5307 it allow for visual programming where syntax errors can not happen,
5308 and a friendly programming environment for learning to control the
5309 computer. Scratch will also be included in the next release of Debian
5310 Edu.&lt;/a&gt;
5311
5312 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5313 Edu/Skolelinux release too. The
5314 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5315 alpha release&lt;/a&gt; went out last week, and the next should soon
5316 follow.&lt;p&gt;
5317 </description>
5318 </item>
5319
5320 <item>
5321 <title>Isenkram 0.2 finally in the Debian archive</title>
5322 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5324 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5325 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5326 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5327 for many months. I uploaded it to the Debian experimental suite
5328 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5329
5330 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5331 install to work with a pluggable hardware device. The suggestion pop
5332 up when the device is plugged in. For example if a Lego Mindstorm NXT
5333 is inserted, it will suggest to install the program needed to program
5334 the NXT controller. Give it a go, and report bugs and suggestions to
5335 BTS. :)&lt;/p&gt;
5336 </description>
5337 </item>
5338
5339 <item>
5340 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5341 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5342 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5343 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5344 <description>&lt;p&gt;My
5345 &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
5346 bitcoin related blog post&lt;/a&gt; mentioned that the new
5347 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5348 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5349 2013-01-19, and have been available in unstable since then. It was
5350 automatically copied to Ubuntu, and is available in their Raring
5351 version too.&lt;/p&gt;
5352
5353 &lt;p&gt;But there is a strange problem with the build that block this new
5354 version from being available on the i386 and kfreebsd-i386
5355 architectures. For some strange reason, the autobuilders in Debian
5356 for these architectures fail to run the test suite on these
5357 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5358 We are so far unable to reproduce it when building it manually, and
5359 no-one have been able to propose a fix. If you got an idea what is
5360 failing, please let us know via the BTS.&lt;/p&gt;
5361
5362 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5363 I often run low on disk space, is the fact that the client will exit
5364 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5365 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5366 it. :)&lt;/p&gt;
5367
5368 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5369 activities, please send Bitcoin donations to my address
5370 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5371 </description>
5372 </item>
5373
5374 <item>
5375 <title>Welcome to the world, Isenkram!</title>
5376 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5378 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5379 <description>&lt;p&gt;Yesterday, I
5380 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5381 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5382 pluggable hardware devices, which I
5383 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5384 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5385 up, and caused me to really want to to open up the development to more
5386 people. But before I did this, I want to come up with a sensible name
5387 for this project. Today I finally decided on a new name, and I have
5388 renamed the project from hw-support-handler to this new name. In the
5389 process, I moved the source to git and made it available as a
5390 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5391 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5392 To fetch and build the latest version of the source, use&lt;/p&gt;
5393
5394 &lt;pre&gt;
5395 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5396 cd isenkram &amp;&amp; git-buildpackage -us -uc
5397 &lt;/pre&gt;
5398
5399 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5400 want to hack on the source or improve the package, please go ahead.
5401 But please talk to me first on IRC or via email before you do major
5402 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5403
5404 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5405 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5406 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5407 the German word eisenkram, for those that are familiar with that
5408 word.&lt;/p&gt;
5409
5410 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5411 instructions, to avoid confusing people with an error from the signing
5412 process.&lt;/p&gt;
5413
5414 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5415 clone argument to avoid the need for authentication.&lt;/p&gt;
5416 </description>
5417 </item>
5418
5419 <item>
5420 <title>First prototype ready making hardware easier to use in Debian</title>
5421 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5423 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5424 <description>&lt;p&gt;Early this month I set out to try to
5425 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5426 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5427 prototype is working, and it is ready for a larger audience. To test
5428 it, fetch the
5429 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5430 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5431 package. You might have to log out and in again activate the
5432 autostart script.&lt;/p&gt;
5433
5434 &lt;p&gt;The design is simple:&lt;/p&gt;
5435
5436 &lt;ul&gt;
5437
5438 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5439 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5440
5441 &lt;li&gt;This program listen for kernel events about new hardware (directly
5442 from the kernel like udev does), not using HAL dbus events as I
5443 initially did.&lt;/li&gt;
5444
5445 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5446 the APT database, a database
5447 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5448 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5449
5450 &lt;li&gt;If a package is mapped to the hardware in question, the package
5451 isn&#39;t installed yet and this is the first time the hardware was
5452 plugged in, show a desktop notification suggesting to install the
5453 package or packages.&lt;/li&gt;
5454
5455 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5456 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5457
5458 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5459 package while showing progress information in a window.&lt;/li&gt;
5460
5461 &lt;/ul&gt;
5462
5463 &lt;p&gt;I still need to come up with a better name for the system. Here
5464 are some screen shots showing the prototype in action. First the
5465 notification, then the password request, and finally the request to
5466 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5467
5468 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5469 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5470 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5471 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5472 &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;
5473
5474 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5475 is already useful. The database of hardware to package mappings also
5476 need more work. It is currently compatible with the Ubuntu way of
5477 storing such information in the package control file, but could be
5478 changed to use other formats instead or in addition to the current
5479 method. I&#39;ve dropped the use of discover for this mapping, as the
5480 modalias approach is more flexible and easier to use on Linux as long
5481 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5482
5483 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5484 here is the command required to check out and build the source: Use
5485 &#39;&lt;tt&gt;svn checkout
5486 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5487 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5488 devscripts package.&lt;/p&gt;
5489
5490 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5491 renamed to Isenkram and the source moved from the Debian Edu
5492 subversion repository to a Debian collab-maint git repository. See
5493 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5494 instructions&lt;/a&gt; for details.&lt;/p&gt;
5495 </description>
5496 </item>
5497
5498 <item>
5499 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5500 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5502 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5503 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5504 suddenly in bed. With a quiet whimper, it went completely quiet and
5505 black. The power button was no longer able to turn it on. It was a
5506 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5507 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5508 Compaq I had before that. Now I need to find a replacement. To keep
5509 going during Christmas, I moved the one year old SSD disk to my old
5510 X40 where it fitted (only one I had left that could use it), but it is
5511 not a durable solution.
5512
5513 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5514 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5515
5516 &lt;ul&gt;
5517
5518 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5519 than A4).&lt;/li&gt;
5520 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5521 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5522 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5523 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5524 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5525 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5526 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5527 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5528 size).&lt;/li&gt;
5529 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5530 X.org packages.&lt;/li&gt;
5531 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5532 the time).
5533
5534 &lt;/ul&gt;
5535
5536 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
5537 list. The reason is simply that the specifications on laptops the
5538 last 10-15 years have been sufficient for my needs, and I have to look
5539 at other features to choose my laptop. But are there still made as
5540 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5541 robust, and Thinkpads seem to be heading in the wrong direction since
5542 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
5543 still be useful.&lt;/p&gt;
5544
5545 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
5546 external keyboard? I&#39;ll have to check the
5547 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
5548 well-supported laptops, or perhaps just buy one preinstalled from one
5549 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
5550 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
5551 </description>
5552 </item>
5553
5554 <item>
5555 <title>How to find a browser plugin supporting a given MIME type</title>
5556 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
5557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
5558 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
5559 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
5560 install to get support for a given MIME type. Thanks to
5561 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
5562 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
5563 Unfortunately, not very many packages provide the needed meta
5564 information, Anyway, here is a small script to look up all browser
5565 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
5566
5567 &lt;pre&gt;
5568 #!/usr/bin/python
5569 import sys
5570 import apt
5571 def pkgs_handling_mimetype(mimetype):
5572 cache = apt.Cache()
5573 cache.open(None)
5574 thepkgs = []
5575 for pkg in cache:
5576 version = pkg.candidate
5577 if version is None:
5578 version = pkg.installed
5579 if version is None:
5580 continue
5581 record = version.record
5582 if not record.has_key(&#39;Npp-MimeType&#39;):
5583 continue
5584 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
5585 for t in mime_types:
5586 t = t.rstrip().strip()
5587 if t == mimetype:
5588 thepkgs.append(pkg.name)
5589 return thepkgs
5590 mimetype = &quot;audio/ogg&quot;
5591 if 1 &lt; len(sys.argv):
5592 mimetype = sys.argv[1]
5593 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
5594 for pkg in pkgs_handling_mimetype(mimetype):
5595 print &quot; %s&quot; %pkg
5596 &lt;/pre&gt;
5597
5598 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
5599
5600 &lt;pre&gt;
5601 % ./apt-find-browserplug-for-mimetype
5602 Browser plugin packages supporting audio/ogg:
5603 gecko-mediaplayer
5604 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5605 Browser plugin packages supporting application/x-shockwave-flash:
5606 browser-plugin-gnash
5607 %
5608 &lt;/pre&gt;
5609
5610 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
5611 itself to query for plugins and propose to install the needed
5612 packages. It would be great if Debian supported such feature too. Is
5613 anyone working on adding it?&lt;/p&gt;
5614
5615 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
5616 request for icweasel support for this feature is
5617 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
5618 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
5619 of manpower and wish for a different design is the reason thus feature
5620 is not yet in iceweasel from Debian.&lt;/p&gt;
5621 </description>
5622 </item>
5623
5624 <item>
5625 <title>What is the most supported MIME type in Debian?</title>
5626 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
5627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
5628 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
5629 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
5630 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
5631 proposal to make it possible for a Desktop application to propose to
5632 the user some package to install to gain support for a given MIME
5633 type, font, library etc. that is currently missing. With such
5634 mechanism in place, it would be possible for the desktop to
5635 automatically propose and install leocad if some LDraw file is
5636 downloaded by the browser.&lt;/p&gt;
5637
5638 &lt;p&gt;To get some idea about the current content of the archive, I decided
5639 to write a simple program to extract all .desktop files from the
5640 Debian archive and look up the claimed MIME support there. The result
5641 can be found on the
5642 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
5643 site&lt;/a&gt;. Using the collected information, it become possible to
5644 answer the question in the title. Here are the 20 most supported MIME
5645 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5646 The complete list is available from the link above.&lt;/p&gt;
5647
5648 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
5649
5650 &lt;pre&gt;
5651 count MIME type
5652 ----- -----------------------
5653 32 text/plain
5654 30 audio/mpeg
5655 29 image/png
5656 28 image/jpeg
5657 27 application/ogg
5658 26 audio/x-mp3
5659 25 image/tiff
5660 25 image/gif
5661 22 image/bmp
5662 22 audio/x-wav
5663 20 audio/x-flac
5664 19 audio/x-mpegurl
5665 18 video/x-ms-asf
5666 18 audio/x-musepack
5667 18 audio/x-mpeg
5668 18 application/x-ogg
5669 17 video/mpeg
5670 17 audio/x-scpls
5671 17 audio/ogg
5672 16 video/x-ms-wmv
5673 &lt;/pre&gt;
5674
5675 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
5676
5677 &lt;pre&gt;
5678 count MIME type
5679 ----- -----------------------
5680 33 text/plain
5681 32 image/png
5682 32 image/jpeg
5683 29 audio/mpeg
5684 27 image/gif
5685 26 image/tiff
5686 26 application/ogg
5687 25 audio/x-mp3
5688 22 image/bmp
5689 21 audio/x-wav
5690 19 audio/x-mpegurl
5691 19 audio/x-mpeg
5692 18 video/mpeg
5693 18 audio/x-scpls
5694 18 audio/x-flac
5695 18 application/x-ogg
5696 17 video/x-ms-asf
5697 17 text/html
5698 17 audio/x-musepack
5699 16 image/x-xbitmap
5700 &lt;/pre&gt;
5701
5702 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
5703
5704 &lt;pre&gt;
5705 count MIME type
5706 ----- -----------------------
5707 31 text/plain
5708 31 image/png
5709 31 image/jpeg
5710 29 audio/mpeg
5711 28 application/ogg
5712 27 image/gif
5713 26 image/tiff
5714 26 audio/x-mp3
5715 23 audio/x-wav
5716 22 image/bmp
5717 21 audio/x-flac
5718 20 audio/x-mpegurl
5719 19 audio/x-mpeg
5720 18 video/x-ms-asf
5721 18 video/mpeg
5722 18 audio/x-scpls
5723 18 application/x-ogg
5724 17 audio/x-musepack
5725 16 video/x-ms-wmv
5726 16 video/x-msvideo
5727 &lt;/pre&gt;
5728
5729 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
5730 information mentioned in DEP-11. I have not yet had time to look at
5731 it, but hope the PackageKit people in Debian are on top of these
5732 issues.&lt;/p&gt;
5733
5734 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
5735 discovering a typo in my script.&lt;/p&gt;
5736 </description>
5737 </item>
5738
5739 <item>
5740 <title>Using modalias info to find packages handling my hardware</title>
5741 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
5742 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
5743 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
5744 <description>&lt;p&gt;Yesterday, I wrote about the
5745 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
5746 values provided by the Linux kernel&lt;/a&gt; following my hope for
5747 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
5748 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
5749 modalias values attached to package names can be used to map packages
5750 to hardware. This allow the system to look up and suggest relevant
5751 packages when I plug in some new hardware into my machine, and replace
5752 discover and discover-data as the database used to map hardware to
5753 packages.&lt;/p&gt;
5754
5755 &lt;p&gt;I create a modaliases file with entries like the following,
5756 containing package name, kernel module name (if relevant, otherwise
5757 the package name) and globs matching the relevant hardware
5758 modalias.&lt;/p&gt;
5759
5760 &lt;p&gt;&lt;blockquote&gt;
5761 Package: package-name
5762 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
5763 &lt;/blockquote&gt;&lt;/p&gt;
5764
5765 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
5766 for a given modalias value using this file.&lt;/p&gt;
5767
5768 &lt;p&gt;An entry like this would suggest the video and picture application
5769 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
5770
5771 &lt;p&gt;&lt;blockquote&gt;
5772 Package: cheese
5773 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
5774 &lt;/blockquote&gt;&lt;/p&gt;
5775
5776 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
5777 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
5778
5779 &lt;p&gt;&lt;blockquote&gt;
5780 Package: pcmciautils
5781 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5782 &lt;/blockquote&gt;&lt;/p&gt;
5783
5784 &lt;p&gt;An entry like this would suggest the package colorhug-client when
5785 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
5786
5787 &lt;p&gt;&lt;blockquote&gt;
5788 Package: colorhug-client
5789 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
5790 &lt;/blockquote&gt;&lt;/p&gt;
5791
5792 &lt;p&gt;I believe the format is compatible with the format of the Packages
5793 file in the Debian archive. Ubuntu already uses their Packages file
5794 to store their mappings from packages to hardware.&lt;/p&gt;
5795
5796 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
5797 announce the hardware it support in a way my prototype understand.
5798 This allow those publishing packages in an APT source outside the
5799 Debian archive as well as those backporting packages to make sure the
5800 hardware mapping are included in the package meta information. I&#39;ve
5801 tested such header in the pymissile package, and its modalias mapping
5802 is working as it should with my prototype. It even made it to Ubuntu
5803 Raring.&lt;/p&gt;
5804
5805 &lt;p&gt;To test if it was possible to look up supported hardware using only
5806 the shell tools available in the Debian installer, I wrote a shell
5807 implementation of the lookup code. The idea is to create files for
5808 each modalias and let the shell do the matching. Please check out and
5809 try the
5810 &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;
5811 shell script. It run without any extra dependencies and fetch the
5812 hardware mappings from the Debian archive and the subversion
5813 repository where I currently work on my prototype.&lt;/p&gt;
5814
5815 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
5816 install yubikey-personalization:&lt;/p&gt;
5817
5818 &lt;p&gt;&lt;blockquote&gt;
5819 % ./hw-support-lookup
5820 &lt;br&gt;yubikey-personalization
5821 &lt;br&gt;%
5822 &lt;/blockquote&gt;&lt;/p&gt;
5823
5824 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5825 propose to install the pcmciautils package:&lt;/p&gt;
5826
5827 &lt;p&gt;&lt;blockquote&gt;
5828 % ./hw-support-lookup
5829 &lt;br&gt;pcmciautils
5830 &lt;br&gt;%
5831 &lt;/blockquote&gt;&lt;/p&gt;
5832
5833 &lt;p&gt;If you know of any hardware-package mapping that should be added to
5834 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
5835 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
5836
5837 &lt;p&gt;It could be possible to generate several of the mappings between
5838 packages and hardware. One source would be to look at packages with
5839 kernel modules, ie packages with *.ko files in /lib/modules/, and
5840 extract their modalias information. Another would be to look at
5841 packages with udev rules, ie packages with files in
5842 /lib/udev/rules.d/, and extract their vendor/model information to
5843 generate a modalias matching rule. I have not tested any of these to
5844 see if it work.&lt;/p&gt;
5845
5846 &lt;p&gt;If you want to help implementing a system to let us propose what
5847 packages to install when new hardware is plugged into a Debian
5848 machine, please send me an email or talk to me on
5849 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5850 </description>
5851 </item>
5852
5853 <item>
5854 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
5855 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
5856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
5857 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
5858 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
5859 information, to find the packages that support a given piece of
5860 hardware, I refreshed my memory regarding modalias values, and decided
5861 to document the details. Here are my findings so far, also available
5862 in
5863 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5864 Debian Edu subversion repository&lt;/a&gt;:
5865
5866 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
5867
5868 &lt;p&gt;This document try to explain what the different types of modalias
5869 values stands for. It is in part based on information from
5870 &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;,
5871 &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;,
5872 &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
5873 &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;.
5874
5875 &lt;p&gt;The modalias entries for a given Linux machine can be found using
5876 this shell script:&lt;/p&gt;
5877
5878 &lt;pre&gt;
5879 find /sys -name modalias -print0 | xargs -0 cat | sort -u
5880 &lt;/pre&gt;
5881
5882 &lt;p&gt;The supported modalias globs for a given kernel module can be found
5883 using modinfo:&lt;/p&gt;
5884
5885 &lt;pre&gt;
5886 % /sbin/modinfo psmouse | grep alias:
5887 alias: serio:ty05pr*id*ex*
5888 alias: serio:ty01pr*id*ex*
5889 %
5890 &lt;/pre&gt;
5891
5892 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
5893
5894 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
5895 Bridge memory controller:&lt;/p&gt;
5896
5897 &lt;p&gt;&lt;blockquote&gt;
5898 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5899 &lt;/blockquote&gt;&lt;/p&gt;
5900
5901 &lt;p&gt;This represent these values:&lt;/p&gt;
5902
5903 &lt;pre&gt;
5904 v 00008086 (vendor)
5905 d 00002770 (device)
5906 sv 00001028 (subvendor)
5907 sd 000001AD (subdevice)
5908 bc 06 (bus class)
5909 sc 00 (bus subclass)
5910 i 00 (interface)
5911 &lt;/pre&gt;
5912
5913 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
5914 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
5915 0600. The 0600 class is a host bridge. Other useful bus values are
5916 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
5917
5918 &lt;p&gt;Not sure how to figure out the interface value, nor what it
5919 means.&lt;/p&gt;
5920
5921 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
5922
5923 &lt;p&gt;Some typical USB entries can look like this. This is an internal
5924 USB hub in a laptop:&lt;/p&gt;
5925
5926 &lt;p&gt;&lt;blockquote&gt;
5927 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5928 &lt;/blockquote&gt;&lt;/p&gt;
5929
5930 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
5931
5932 &lt;pre&gt;
5933 v 1D6B (device vendor)
5934 p 0001 (device product)
5935 d 0206 (bcddevice)
5936 dc 09 (device class)
5937 dsc 00 (device subclass)
5938 dp 00 (device protocol)
5939 ic 09 (interface class)
5940 isc 00 (interface subclass)
5941 ip 00 (interface protocol)
5942 &lt;/pre&gt;
5943
5944 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
5945 class is in the interface class section. For a simple USB web camera,
5946 these alias entries show up:&lt;/p&gt;
5947
5948 &lt;p&gt;&lt;blockquote&gt;
5949 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5950 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5951 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5952 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5953 &lt;/blockquote&gt;&lt;/p&gt;
5954
5955 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
5956 camera), 0101 is audio control device and 0102 is audio streaming (aka
5957 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
5958
5959 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
5960
5961 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
5962 receiver in a Thinkpad X40:&lt;/p&gt;
5963
5964 &lt;p&gt;&lt;blockquote&gt;
5965 acpi:IBM0071:PNP0511:
5966 &lt;/blockquote&gt;&lt;/p&gt;
5967
5968 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
5969
5970 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
5971
5972 &lt;p&gt;The DMI table contain lots of information about the computer case
5973 and model. This is an entry for a IBM Thinkpad X40, fetched from
5974 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
5975
5976 &lt;p&gt;&lt;blockquote&gt;
5977 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5978 &lt;/blockquote&gt;&lt;/p&gt;
5979
5980 &lt;p&gt;The values present are&lt;/p&gt;
5981
5982 &lt;pre&gt;
5983 bvn IBM (BIOS vendor)
5984 bvr 1UETB6WW(1.66) (BIOS version)
5985 bd 06/15/2005 (BIOS date)
5986 svn IBM (system vendor)
5987 pn 2371H4G (product name)
5988 pvr ThinkPadX40 (product version)
5989 rvn IBM (board vendor)
5990 rn 2371H4G (board name)
5991 rvr NotAvailable (board version)
5992 cvn IBM (chassis vendor)
5993 ct 10 (chassis type)
5994 cvr NotAvailable (chassis version)
5995 &lt;/pre&gt;
5996
5997 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
5998 found in the dmidecode source:&lt;/p&gt;
5999
6000 &lt;pre&gt;
6001 3 Desktop
6002 4 Low Profile Desktop
6003 5 Pizza Box
6004 6 Mini Tower
6005 7 Tower
6006 8 Portable
6007 9 Laptop
6008 10 Notebook
6009 11 Hand Held
6010 12 Docking Station
6011 13 All In One
6012 14 Sub Notebook
6013 15 Space-saving
6014 16 Lunch Box
6015 17 Main Server Chassis
6016 18 Expansion Chassis
6017 19 Sub Chassis
6018 20 Bus Expansion Chassis
6019 21 Peripheral Chassis
6020 22 RAID Chassis
6021 23 Rack Mount Chassis
6022 24 Sealed-case PC
6023 25 Multi-system
6024 26 CompactPCI
6025 27 AdvancedTCA
6026 28 Blade
6027 29 Blade Enclosing
6028 &lt;/pre&gt;
6029
6030 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6031 table. For example my home server is a tower, but the DMI modalias
6032 claim it is a desktop.&lt;/p&gt;
6033
6034 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6035
6036 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6037 test machine:&lt;/p&gt;
6038
6039 &lt;p&gt;&lt;blockquote&gt;
6040 serio:ty01pr00id00ex00
6041 &lt;/blockquote&gt;&lt;/p&gt;
6042
6043 &lt;p&gt;The values present are&lt;/p&gt;
6044
6045 &lt;pre&gt;
6046 ty 01 (type)
6047 pr 00 (prototype)
6048 id 00 (id)
6049 ex 00 (extra)
6050 &lt;/pre&gt;
6051
6052 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6053 the valid values are.&lt;/p&gt;
6054
6055 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6056
6057 &lt;p&gt;There are heaps of other modalias subtypes according to
6058 file2alias.c. There is the rest of the list from that source: amba,
6059 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6060 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6061 vmbus, x86cpu and zorro. I did not spend time documenting all of
6062 these, as they do not seem relevant for my intended use with mapping
6063 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6064
6065 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6066
6067 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6068 one can use the following shell script:&lt;/p&gt;
6069
6070 &lt;pre&gt;
6071 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6072 echo &quot;$id&quot; ; \
6073 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6074 done
6075 &lt;/pre&gt;
6076
6077 &lt;p&gt;The output can look like this (only the first few entries as the
6078 list is very long on my test machine):&lt;/p&gt;
6079
6080 &lt;pre&gt;
6081 acpi:ACPI0003:
6082 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6083 acpi:device:
6084 FATAL: Module acpi:device: not found.
6085 acpi:IBM0068:
6086 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6087 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6088 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6089 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6090 acpi:IBM0071:PNP0511:
6091 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6092 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6093 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6094 [...]
6095 &lt;/pre&gt;
6096
6097 &lt;p&gt;If you want to help implementing a system to let us propose what
6098 packages to install when new hardware is plugged into a Debian
6099 machine, please send me an email or talk to me on
6100 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6101
6102 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6103 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6104 in /sys/ with space in them.&lt;/p&gt;
6105 </description>
6106 </item>
6107
6108 <item>
6109 <title>Moved the pymissile Debian packaging to collab-maint</title>
6110 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
6111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
6112 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
6113 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
6114 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6115 Launcher and updated the Debian package
6116 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
6117 sure udev will fix the device permissions when it is plugged in. I
6118 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
6119 hopefully make the package be proposed by jockey in Ubuntu when a user
6120 plug in his rocket launcher. In the process I moved the source to a
6121 git repository under collab-maint, to make it easier for any DD to
6122 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
6123 is not very active, but the software still work for me even after five
6124 years of relative silence. The new git repository is not listed in
6125 the uploaded package yet, because I want to test the other changes a
6126 bit more before I upload the new version. If you want to check out
6127 the new version with a .desktop file included, visit the
6128 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
6129 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
6130 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
6131 </description>
6132 </item>
6133
6134 <item>
6135 <title>Lets make hardware dongles easier to use in Debian</title>
6136 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
6137 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
6138 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
6139 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
6140 general, is that there is a great package management system with the
6141 ability to automatically install software packages by downloading them
6142 from the distribution mirrors, but no way to get it to automatically
6143 install the packages I need to use the hardware I plug into my
6144 machine. Even if the package to use it is easily available from the
6145 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6146 suggest to automatically install the python-nxt, nbc and t2n packages
6147 I need to talk to it. When I plug in a Yubikey, it could propose the
6148 yubikey-personalization package. The information required to do this
6149 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
6150
6151 &lt;p&gt;Some years ago, I proposed to
6152 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
6153 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
6154 simple:
6155
6156 &lt;ul&gt;
6157
6158 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
6159 starting when a user log in.&lt;/li&gt;
6160
6161 &lt;li&gt;Set this program up to listen for kernel events emitted when new
6162 hardware is inserted into the computer.&lt;/li&gt;
6163
6164 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
6165 database mapping to packages, and take note of any non-installed
6166 packages.&lt;/li&gt;
6167
6168 &lt;li&gt;Show a message to the user proposing to install the discovered
6169 package, and make it easy to install it.&lt;/li&gt;
6170
6171 &lt;/ul&gt;
6172
6173 &lt;p&gt;I am not sure what the best way to implement this is, but my
6174 initial idea was to use dbus events to discover new hardware, the
6175 discover database to find packages and
6176 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
6177 packages.&lt;/p&gt;
6178
6179 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
6180 draft package is now checked into
6181 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6182 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
6183 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
6184 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6185 the relevant packages in Debian, and uploaded a new version
6186 2.2013.01.09 to unstable. I also discovered that the current
6187 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
6188 package in Debian no longer discovered any USB devices, because
6189 /proc/bus/usb/devices is no longer present. I ported it to use
6190 libusb as a fall back option to get it working. The fixed package
6191 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
6192 because of the freeze).&lt;/p&gt;
6193
6194 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
6195 desktop notification to show up (only once, the first time it is
6196 inserted):&lt;/p&gt;
6197
6198 &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;
6199
6200 &lt;p&gt;For this prototype to be really useful, some way to automatically
6201 install the proposed packages by pressing the &quot;Please install
6202 program(s)&quot; button should to be implemented.&lt;/p&gt;
6203
6204 &lt;p&gt;If this idea seem useful to you, and you want to help make it
6205 happen, please help me update the discover-data database with mappings
6206 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
6207 list the package you would like to have installed when a given
6208 hardware device is inserted into your computer, and report bugs using
6209 reportbug if it isn&#39;t. Or, if you know of a better way to provide
6210 such mapping, please let me know.&lt;/p&gt;
6211
6212 &lt;p&gt;This prototype need more work, and there are several questions that
6213 should be considered before it is ready for production use. Is dbus
6214 the correct way to detect new hardware? At the moment I look for HAL
6215 dbus events on the system bus, because that is the events I could see
6216 on my Debian Squeeze KDE desktop. Are there better events to use?
6217 How should the user be notified? Is the desktop notification
6218 mechanism the best option, or should the background daemon raise a
6219 popup instead? How should packages be installed? When should they
6220 not be installed?&lt;/p&gt;
6221
6222 &lt;p&gt;If you want to help getting such feature implemented in Debian,
6223 please send me an email. :)&lt;/p&gt;
6224 </description>
6225 </item>
6226
6227 <item>
6228 <title>New IRC channel for LEGO designers using Debian</title>
6229 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
6230 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
6231 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
6232 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
6233 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
6234 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
6235 discovered I had to build all the tools myself because none were
6236 already in Debian Squeeze. If Debian support for LEGO is something
6237 you care about, please join me on the IRC channel
6238 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
6239 irc.debian.org). There is a lot that could be done to improve the
6240 Debian support for LEGO designers. For example both CAD software
6241 and Mindstorm compilers are missing. :)&lt;/p&gt;
6242
6243 &lt;p&gt;Update 2012-01-03: A
6244 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
6245 including links to Lego related packages is now available.&lt;/p&gt;
6246 </description>
6247 </item>
6248
6249 <item>
6250 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
6251 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
6252 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
6253 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
6254 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
6255 year! I hope next year will prove to be a good year.&lt;/p&gt;
6256
6257 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
6258 decentralised &quot;currency&quot; that allow people to transfer bitcoins
6259 between each other with minimal overhead, is a very interesting
6260 experiment. And as I wrote a few days ago, the bitcoin situation in
6261 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
6262 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
6263 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
6264 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
6265 for one of the ftpmasters to approve the new bitcoin-qt package
6266 name.&lt;/p&gt;
6267
6268 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
6269 team in Debian, you can easily test the package in Debian Squeeze
6270 using the following steps to get a set of working packages:&lt;/p&gt;
6271
6272 &lt;blockquote&gt;&lt;pre&gt;
6273 git clone git://git.debian.org/git/collab-maint/bitcoin
6274 cd bitcoin
6275 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6276 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6277 &lt;/pre&gt;&lt;/blockquote&gt;
6278
6279 &lt;p&gt;You might have to install some build dependencies as well. The
6280 list of commands should give you two packages, bitcoind and
6281 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6282 client will download the complete set of bitcoin &quot;blocks&quot;, which need
6283 around 5.6 GiB of data on my machine at the moment. Make sure your
6284 ~/.bitcoin/ directory have lots of spare room if you want to download
6285 all the blocks. The client will warn if the disk is getting full, so
6286 there is not really a problem if you got too little room, but you will
6287 not be able to get all the features out of the client.&lt;/p&gt;
6288
6289 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6290 activities, please send Bitcoin donations to my address
6291 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6292 </description>
6293 </item>
6294
6295 <item>
6296 <title>A word on bitcoin support in Debian</title>
6297 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
6298 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
6299 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
6300 <description>&lt;p&gt;It has been a while since I wrote about
6301 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
6302 peer-to-peer based crypto-currency, and the reason is simply that I
6303 have been busy elsewhere. But two days ago, I started looking at the
6304 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
6305 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6306 is now maintained by a
6307 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6308 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6309 owe a huge thank you to all these team members. :)
6310 But I was sad to discover that the bitcoin client is missing in
6311 Wheezy. It is only available in Sid (and an outdated client from
6312 backports). The client had several RC bugs registered in BTS blocking
6313 it from entering testing. To try to help the team and improve the
6314 situation, I spent some time providing patches and triaging the bug
6315 reports. I also had a look at the bitcoin package available from Matt
6316 Corallo in a
6317 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6318 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6319 Debian package.&lt;/p&gt;
6320
6321 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6322 IRC, I pushed several patches into the collab-maint git repository to
6323 improve the package. It now contains fixes for the RC issues (not from
6324 me, but fixed by Scott Howard), build rules for a Qt GUI client
6325 package, konqueror support for the bitcoin: URI and bash completion
6326 setup. As I work on Debian Squeeze, I also created
6327 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6328 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6329 it and try to integrate it into the git repository before uploading a
6330 new version to unstable.
6331
6332 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6333 centralized control currently exercised in the monetary system. I
6334 find it completely unacceptable that the USA government is collecting
6335 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6336 that the major credit card companies can block legal money
6337 transactions to Wikileaks. But for bitcoin to succeed, more people
6338 need to use bitcoins, and more people need to accept bitcoins when
6339 they sell products and services. Improving the bitcoin support in
6340 Debian is a small step in the right direction, but not enough.
6341 Unfortunately the user experience when browsing the web and wanting to
6342 pay with bitcoin is still not very good. The bitcoin: URI is a step
6343 in the right direction, but need to work in most or every browser in
6344 use. Also the bitcoin-qt client is too heavy to fire up to do a
6345 quick transaction. I believe there are other clients available, but
6346 have not tested them.&lt;/p&gt;
6347
6348 &lt;p&gt;My
6349 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6350 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6351 I received 20.15 BTC so far on the address I provided in my blog two
6352 years ago, as can be
6353 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6354 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6355 donation. The blockexplorer service demonstrates quite well that
6356 bitcoin is not quite anonymous and untracked. :) I wonder if the
6357 number of users have gone up since then. If you use bitcoin and want
6358 to show your support of my activity, please send Bitcoin donations to
6359 the same address as last time,
6360 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6361 </description>
6362 </item>
6363
6364 <item>
6365 <title>Git repository for song book for Computer Scientists</title>
6366 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6367 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6368 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6369 <description>&lt;p&gt;As I
6370 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6371 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6372 years ago, and today I finally found time to create a public
6373 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6374 repository for the project&lt;/a&gt;.&lt;/p&gt;
6375
6376 &lt;p&gt;If you want to help out, please clone the source and submit patches
6377 to the HTML version. To generate the PDF and PostScript version,
6378 please use prince XML, or let me know about a useful free software
6379 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6380
6381 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6382 PostScript formats at
6383 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6384 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6385 </description>
6386 </item>
6387
6388 <item>
6389 <title>Gratulerer med 19-årsdagen, Debian!</title>
6390 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6391 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6392 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6393 <description>&lt;p&gt;I dag fyller
6394 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6395 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6396 si gratulerer med dagen, Debian!&lt;/p&gt;
6397 </description>
6398 </item>
6399
6400 <item>
6401 <title>Song book for Computer Scientists</title>
6402 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6404 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6405 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6406 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6407 collecting computer related songs for use at parties. The original
6408 version was written in LaTeX, but a few years ago I got help from
6409 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6410 while keeping the ability to create a nice book in PDF format. I have
6411 not had time to maintain the book for a while now, and guess I should
6412 put it up on some public version control repository where others can
6413 help me extend and update the book. If anyone is volunteering to help
6414 me with this, send me an email. Also let me know if there are songs
6415 missing in my book.&lt;/p&gt;
6416
6417 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6418 me today that I really should let all my readers share the joys of
6419 singing out load about programming, computers and computer networks.
6420 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6421 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6422 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6423 Computer Science Songbook&lt;/a&gt;.
6424 </description>
6425 </item>
6426
6427 <item>
6428 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6429 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6431 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6432 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6433 around 1000 at the moment. To be able to get help from the vendors
6434 when something go wrong, we want to keep the firmware on the servers
6435 up to date. If the firmware isn&#39;t the latest and greatest, the
6436 vendors typically refuse to start debugging any problems until the
6437 firmware is upgraded. So before every reboot, we want to upgrade the
6438 firmware, and we would really like everyone handling servers at the
6439 university to do this themselves when they plan to reboot a machine.
6440 For that to happen we at the unix server admin group need to provide
6441 the tools to do so.&lt;/p&gt;
6442
6443 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6444 fetch and install the latest firmware for the servers we got. Most of
6445 our hardware are from Dell and HP, so I have focused on these servers
6446 so far. This blog post is about the Dell part.&lt;/P&gt;
6447
6448 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6449 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6450 with firmware information for all 11th generation servers, listing
6451 which firmware should be used on a given model and where on the FTP
6452 site I can find it. Using a simple perl XML parser I can then
6453 download the shell scripts Dell provides to do firmware upgrades from
6454 within Linux and reboot when all the firmware is primed and ready to
6455 be activated on the first reboot.&lt;/p&gt;
6456
6457 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6458 Are there anyone working on similar tools for firmware upgrading all
6459 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6460
6461 &lt;p&gt;&lt;pre&gt;
6462 #!/usr/bin/perl
6463 use strict;
6464 use warnings;
6465 use File::Temp qw(tempdir);
6466 BEGIN {
6467 # Install needed RHEL packages if missing
6468 my %rhelmodules = (
6469 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6470 );
6471 for my $module (keys %rhelmodules) {
6472 eval &quot;use $module;&quot;;
6473 if ($@) {
6474 my $pkg = $rhelmodules{$module};
6475 system(&quot;yum install -y $pkg&quot;);
6476 eval &quot;use $module;&quot;;
6477 }
6478 }
6479 }
6480 my $errorsto = &#39;pere@hungry.com&#39;;
6481
6482 upgrade_dell();
6483
6484 exit 0;
6485
6486 sub run_firmware_script {
6487 my ($opts, $script) = @_;
6488 unless ($script) {
6489 print STDERR &quot;fail: missing script name\n&quot;;
6490 exit 1
6491 }
6492 print STDERR &quot;Running $script\n\n&quot;;
6493
6494 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6495 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6496 } else {
6497 print STDERR &quot;fail: firmware script returned error\n&quot;;
6498 }
6499 }
6500
6501 sub run_firmware_scripts {
6502 my ($opts, @dirs) = @_;
6503 # Run firmware packages
6504 for my $dir (@dirs) {
6505 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6506 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6507 while (my $s = readdir $dh) {
6508 next if $s =~ m/^\.\.?/;
6509 run_firmware_script($opts, &quot;$dir/$s&quot;);
6510 }
6511 closedir $dh;
6512 }
6513 }
6514
6515 sub download {
6516 my $url = shift;
6517 print STDERR &quot;info: Downloading $url\n&quot;;
6518 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6519 }
6520
6521 sub upgrade_dell {
6522 my @dirs;
6523 my $product = `dmidecode -s system-product-name`;
6524 chomp $product;
6525
6526 if ($product =~ m/PowerEdge/) {
6527
6528 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6529 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6530
6531 my $tmpdir = tempdir(
6532 CLEANUP =&gt; 1
6533 );
6534 chdir($tmpdir);
6535 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
6536 system(&#39;gunzip Catalog.xml.gz&#39;);
6537 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
6538 # -q is quiet, disabling interactivity and reducing console output
6539 my $fwopts = &quot;-q&quot;;
6540 if (@paths) {
6541 for my $url (@paths) {
6542 fetch_dell_fw($url);
6543 }
6544 run_firmware_scripts($fwopts, $tmpdir);
6545 } else {
6546 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6547 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6548 }
6549 chdir(&#39;/&#39;);
6550 } else {
6551 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6552 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6553 }
6554 }
6555
6556 sub fetch_dell_fw {
6557 my $path = shift;
6558 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
6559 download($url);
6560 }
6561
6562 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6563 # firmware packages to download from Dell. Only work for Linux
6564 # machines and 11th generation Dell servers.
6565 sub fetch_dell_fw_list {
6566 my $filename = shift;
6567
6568 my $product = `dmidecode -s system-product-name`;
6569 chomp $product;
6570 my ($mybrand, $mymodel) = split(/\s+/, $product);
6571
6572 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
6573
6574 my $xml = XMLin($filename);
6575 my @paths;
6576 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
6577 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
6578 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
6579 my $oscode;
6580 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
6581 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
6582 } else {
6583 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
6584 }
6585 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
6586 {
6587 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
6588 }
6589 }
6590 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
6591 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
6592
6593 # Drop application packages, only firmware and BIOS
6594 next if &#39;APAC&#39; eq $componenttype;
6595
6596 my $cpath = $component-&gt;{path};
6597 for my $path (@paths) {
6598 if ($cpath =~ m%/$path$%) {
6599 push(@paths, $cpath);
6600 }
6601 }
6602 }
6603 return @paths;
6604 }
6605 &lt;/pre&gt;
6606
6607 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
6608 it could work on other platforms with some tweaking. Anyone know a
6609 index like Catalog.xml is available from HP for HP servers? At the
6610 moment I maintain a similar list manually and it is quickly getting
6611 outdated.&lt;/p&gt;
6612 </description>
6613 </item>
6614
6615 <item>
6616 <title>How is booting into runlevel 1 different from single user boots?</title>
6617 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
6618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
6619 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
6620 <description>&lt;p&gt;Wouter Verhelst have some
6621 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
6622 comments and opinions&lt;/a&gt; on my blog post on
6623 &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
6624 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
6625 &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
6626 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
6627 small piece of his comment now, and though it best to address the
6628 misunderstanding he bring forward:&lt;/p&gt;
6629
6630 &lt;p&gt;&lt;blockquote&gt;
6631 Currently, a system admin has four options: [...] boot to a
6632 single-user system (by adding &#39;single&#39; to the kernel command line;
6633 this runs rcS and rc1 scripts)
6634 &lt;/blockquote&gt;&lt;/p&gt;
6635
6636 &lt;p&gt;This make me believe Wouter believe booting into single user mode
6637 and booting into runlevel 1 is the same. I am not surprised he
6638 believe this, because it would make sense and is a quite sensible
6639 thing to believe. But because the boot in Debian is slightly broken,
6640 runlevel 1 do not work properly and it isn&#39;t the same as single user
6641 mode. I&#39;ll try to explain what is actually happing, but it is a bit
6642 hard to explain.&lt;/p&gt;
6643
6644 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
6645 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
6646 executed in single user mode is sulogin. Single user mode is a boot
6647 state &quot;between&quot; the runlevels, and when booting into single user mode,
6648 only the scripts in /etc/rcS.d/ are executed before the init process
6649 enters the single user state. When switching to runlevel 1, the state
6650 is in fact not ending in runlevel 1, but it passes through runlevel 1
6651 and end up in the single user mode (see /etc/rc1.d/S03single, which
6652 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
6653 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
6654 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6655 mode).&lt;/p&gt;
6656
6657 &lt;p&gt;This summary might make it clearer. When booting for the first
6658 time into single user mode, the following commands are executed:
6659 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
6660 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
6661 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
6662 trying to continue after visiting single user mode. Not all services
6663 are started again as they should, causing the machine to end up in an
6664 unpredicatble state. This is why Debian admins recommend rebooting
6665 after visiting single user mode.&lt;/p&gt;
6666
6667 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
6668 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
6669 to runlevel 1, the services started from /etc/rcS.d/ are not properly
6670 stopped when passing through the scripts in /etc/rc1.d/, and not
6671 started again when switching away from runlevel 1 to the runlevels
6672 2-5. I believe the problem is best fixed by moving all the scripts
6673 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
6674 functioning single user mode during boot.&lt;/p&gt;
6675
6676 &lt;p&gt;I have spent several years investigating the Debian boot system,
6677 and discovered this problem a few years ago. I suspect it originates
6678 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
6679 </description>
6680 </item>
6681
6682 <item>
6683 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
6684 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
6685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
6686 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
6687 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
6688 are started from /etc/rcS.d/. In fact, there is a bite more of them
6689 than make sense, and this causes a few problems. What kind of
6690 problems, you might ask. There are at least two problems. The first
6691 is that it is not possible to recover a machine after switching to
6692 runlevel 1. One need to actually reboot to get the machine back to
6693 the expected state. The other is that single user boot will sometimes
6694 run into problems because some of the subsystems are activated before
6695 the root login is presented, causing problems when trying to recover a
6696 machine from a problem in that subsystem. A minor additional point is
6697 that moving more scripts out of rcS.d/ and into the other rc#.d/
6698 directories will increase the amount of scripts that can run in
6699 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
6700
6701 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
6702 scripts that _have_ to execute before the root login prompt is
6703 presented during a single user boot should go there. Everything else
6704 should go into the numeric runlevels. This means things like
6705 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6706 the numeric runlevels. Today in Debian, there are around 115 init.d
6707 scripts that are started from rcS.d/, and most of them should be moved
6708 out. Do your package have one of them? Please help us make single
6709 user and runlevel 1 better by moving it.&lt;/p&gt;
6710
6711 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
6712 etc. should still be started from rcS.d/, but there is for example no
6713 need to have the network enabled before the single user login prompt
6714 is presented.&lt;/p&gt;
6715
6716 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
6717 Debian systems working while scripts migrate and during upgrades, the
6718 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6719 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6720 and the next ones can only be moved when their dependencies have been
6721 moved first. This migration must be done sequentially while we ensure
6722 that the package system upgrade packages in the right order to keep
6723 the system state correct. This will require some coordination when it
6724 comes to network related packages, but most of the packages with
6725 scripts that should migrate do not have anything in rcS.d/ depending
6726 on them. Some packages have already been updated, like the sudo
6727 package, while others are still left to do. I wish I had time to work
6728 on this myself, but real live constrains make it unlikely that I will
6729 find time to push this forward.&lt;/p&gt;
6730 </description>
6731 </item>
6732
6733 <item>
6734 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
6735 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
6736 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
6737 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
6738 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
6739 mentioned the issues I believe should be improved in Debian for its
6740 desktop to be useful for more people. The use case for this is my
6741 parents, which are currently running Kubuntu which solve the
6742 issues.&lt;/p&gt;
6743
6744 &lt;p&gt;I suspect these four missing features are not very hard to
6745 implement. After all, they are present in Ubuntu, so if we wanted to
6746 do this in Debian we would have a source.&lt;/p&gt;
6747
6748 &lt;ol&gt;
6749
6750 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
6751 are new packages available for upgrades, a icon in the KDE status bar
6752 indicate this, and clicking on it will activate the simple upgrade
6753 tool to handle it. I have no problem guiding both of my parents
6754 through the process over the phone. If a kernel reboot is required,
6755 this too is indicated by the status bars and the upgrade tool. Last
6756 time I checked, nothing with the same features was working in KDE in
6757 Debian.&lt;/li&gt;
6758
6759 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
6760 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
6761 currently have a handler for, it will ask the user if the system
6762 should search for a package that would add support for this MIME type,
6763 and if the user say yes, the APT sources will be searched for packages
6764 advertising the MIME type in their control file (visible in the
6765 Packages file in the APT archive). If one or more packages are found,
6766 it is a simple click of the mouse to add support for the missing mime
6767 type. If the package require the user to accept some non-free
6768 license, this is explained to the user. The entire process make it
6769 more clear to the user why something do not work in the browser, and
6770 make the chances higher for the user to blame the web page authors and
6771 not the browser for any missing features.&lt;/li&gt;
6772
6773 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
6774 handlers.&lt;/strong&gt; When the media players encounter a format or codec
6775 it is not supporting, a dialog pop up asking the user if the system
6776 should search for a package that would add support for it. This
6777 happen with things like MP3, Windows Media or H.264. The selection
6778 and installation procedure is very similar to the Firefox browser
6779 plugin handling. This is as far as I know implemented using a
6780 gstreamer hook. The end result is that the user easily get access to
6781 the codecs that are present from the APT archives available, while
6782 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
6783
6784 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
6785 displaying a text/plain file in my Debian browser, it will propose to
6786 start emacs to show it. If I remember correctly, when doing the same
6787 in Kunbutu it show the file as a text file in the browser. At least I
6788 know Opera will show text files within the browser. I much prefer the
6789 latter behaviour.&lt;/li&gt;
6790
6791 &lt;/ol&gt;
6792
6793 &lt;p&gt;There are other nice features as well, like the simplified suite
6794 upgrader, but given that I am the one mostly doing the dist-upgrade,
6795 it do not matter much.&lt;/p&gt;
6796
6797 &lt;p&gt;I really hope we could get these features in place for the next
6798 Debian release. It would require the coordinated effort of several
6799 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
6800 </description>
6801 </item>
6802
6803 <item>
6804 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
6805 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
6806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
6807 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
6808 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
6809 site is build on Debian/Squeeze, and this platform was chosen because
6810 I am most familiar with Debian (being a Debian Developer for around 10
6811 years) because it is the latest stable Debian release which should get
6812 security support for a few years.&lt;/p&gt;
6813
6814 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
6815 that are missing in Debian at the moment. It would be great if these
6816 modules were added to the Debian archive, allowing anyone to set up
6817 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
6818 in their own country using only Debian packages. The list of modules
6819 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
6820 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
6821 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6822 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6823 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6824 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6825 easier in the future.&lt;/p&gt;
6826
6827 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
6828 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
6829 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
6830 with the responsibility of tracking security problems, which I really
6831 do not have time for.&lt;/p&gt;
6832 </description>
6833 </item>
6834
6835 <item>
6836 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
6837 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
6838 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
6839 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
6840 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
6841 posts have been in Norwegian the last few weeks, so here is a short
6842 update in English.&lt;/p&gt;
6843
6844 &lt;p&gt;The kids still keep me too busy to get much free software work
6845 done, but I did manage to organise a project to get a Norwegian port
6846 of the British service
6847 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
6848 and it has been running for a month now. The entire project has been
6849 organised by me and two others. Around Christmas we gathered sponsors
6850 to fund the development work. In January I drafted a contract with
6851 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
6852 and in February the development took place. Most of it involved
6853 converting the source to use GPS coordinates instead of British
6854 easting/northing, and the resulting code should be a lot easier to get
6855 running in any country by now. The Norwegian
6856 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
6857 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
6858 source and the source for administrative borders in Norway, and
6859 support for this had to be added/fixed.&lt;/p&gt;
6860
6861 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
6862 polishing the system before we announced it March 7th. The system is
6863 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
6864 problem reports in a few weeks. Soon we hope to announce the Android
6865 and iPhone versions making it even easier to report problems with the
6866 public infrastructure.&lt;/p&gt;
6867
6868 &lt;p&gt;Perhaps something to consider for those of you in countries without
6869 such service?&lt;/p&gt;
6870 </description>
6871 </item>
6872
6873 <item>
6874 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
6875 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
6876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
6877 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
6878 <description>&lt;p&gt;The last few days I have looked at ways to track open security
6879 issues here at my work with the University of Oslo. My idea is that
6880 it should be possible to use the information about security issues
6881 available on the Internet, and check our locally
6882 maintained/distributed software against this information. It should
6883 allow us to verify that no known security issues are forgotten. The
6884 CVE database listing vulnerabilities seem like a great central point,
6885 and by using the package lists from Debian mapped to CVEs provided by
6886 the testing security team, I believed it should be possible to figure
6887 out which security holes were present in our free software
6888 collection.&lt;/p&gt;
6889
6890 &lt;p&gt;After reading up on the topic, it became obvious that the first
6891 building block is to be able to name software packages in a unique and
6892 consistent way across data sources. I considered several ways to do
6893 this, for example coming up with my own naming scheme like using URLs
6894 to project home pages or URLs to the Freshmeat entries, or using some
6895 existing naming scheme. And it seem like I am not the first one to
6896 come across this problem, as MITRE already proposed and implemented a
6897 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
6898 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
6899 software, hardware and other platform components. The CPE ids are
6900 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
6901 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
6902 issues for any CPE name. With this in place, all I need to do is to
6903 locate the CPE id for the software packages we use at the university.
6904 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
6905 NVD entry if a CVE for the package exist).&lt;/p&gt;
6906
6907 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
6908 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
6909 check out, one could look up
6910 &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
6911 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
6912 The most recent one is
6913 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
6914 and at the bottom of the NVD page for this vulnerability the complete
6915 list of affected versions is provided.&lt;/p&gt;
6916
6917 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
6918 for offline processing of issues. Using this dump, I&#39;ve written a
6919 small script taking a list of CPEs as input and list all CVEs
6920 affecting the packages represented by these CPEs. One give it CPEs
6921 with version numbers as specified above and get a list of open
6922 security issues out.&lt;/p&gt;
6923
6924 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
6925 information need to be high. For that to happen, I believe as many as
6926 possible need to use and contribute to the NVD database. I notice
6927 RHEL is providing
6928 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
6929 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
6930 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
6931
6932 &lt;p&gt;To get an idea about the quality for free software, I spent some
6933 time making it possible to compare the CVE database from Debian with
6934 the CVE database in NVD. The result look fairly good, but there are
6935 some inconsistencies in NVD (same software package having several
6936 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6937 Debian believe are affected by a CVE). Hope to find time to improve
6938 the quality of NVD, but that require being able to get in touch with
6939 someone maintaining it. So far my three emails with questions and
6940 corrections have not seen any reply, but I hope contact can be
6941 established soon.&lt;/p&gt;
6942
6943 &lt;p&gt;An interesting application for CPEs is cross platform package
6944 mapping. It would be useful to know which packages in for example
6945 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6946 this would be trivial if all linux distributions provided CPE entries
6947 for their packages.&lt;/p&gt;
6948 </description>
6949 </item>
6950
6951 <item>
6952 <title>Which module is loaded for a given PCI and USB device?</title>
6953 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
6954 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
6955 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
6956 <description>&lt;p&gt;In the
6957 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
6958 package in Debian, there is a script to report useful information
6959 about the running hardware for use when people report missing
6960 information. One part of this script that I find very useful when
6961 debugging hardware problems, is the part mapping loaded kernel module
6962 to the PCI device it claims. It allow me to quickly see if the kernel
6963 module I expect is driving the hardware I am struggling with. To see
6964 the output, make sure discover-data is installed and run
6965 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
6966 one of my machines like this:&lt;/p&gt;
6967
6968 &lt;pre&gt;
6969 loaded modules:
6970 10de:03eb i2c_nforce2
6971 10de:03f1 ohci_hcd
6972 10de:03f2 ehci_hcd
6973 10de:03f0 snd_hda_intel
6974 10de:03ec pata_amd
6975 10de:03f6 sata_nv
6976 1022:1103 k8temp
6977 109e:036e bttv
6978 109e:0878 snd_bt87x
6979 11ab:4364 sky2
6980 &lt;/pre&gt;
6981
6982 &lt;p&gt;The code in question look like this, slightly modified for
6983 readability and to drop the output to file descriptor 3:&lt;/p&gt;
6984
6985 &lt;pre&gt;
6986 if [ -d /sys/bus/pci/devices/ ] ; then
6987 echo loaded pci modules:
6988 (
6989 cd /sys/bus/pci/devices/
6990 for address in * ; do
6991 if [ -d &quot;$address/driver/module&quot; ] ; then
6992 module=`cd $address/driver/module ; pwd -P | xargs basename`
6993 if grep -q &quot;^$module &quot; /proc/modules ; then
6994 address=$(echo $address |sed s/0000://)
6995 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
6996 echo &quot;$id $module&quot;
6997 fi
6998 fi
6999 done
7000 )
7001 echo
7002 fi
7003 &lt;/pre&gt;
7004
7005 &lt;p&gt;Similar code could be used to extract USB device module
7006 mappings:&lt;/p&gt;
7007
7008 &lt;pre&gt;
7009 if [ -d /sys/bus/usb/devices/ ] ; then
7010 echo loaded usb modules:
7011 (
7012 cd /sys/bus/usb/devices/
7013 for address in * ; do
7014 if [ -d &quot;$address/driver/module&quot; ] ; then
7015 module=`cd $address/driver/module ; pwd -P | xargs basename`
7016 if grep -q &quot;^$module &quot; /proc/modules ; then
7017 address=$(echo $address |sed s/0000://)
7018 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7019 if [ &quot;$id&quot; ] ; then
7020 echo &quot;$id $module&quot;
7021 fi
7022 fi
7023 fi
7024 done
7025 )
7026 echo
7027 fi
7028 &lt;/pre&gt;
7029
7030 &lt;p&gt;This might perhaps be something to include in other tools as
7031 well.&lt;/p&gt;
7032 </description>
7033 </item>
7034
7035 <item>
7036 <title>How to test if a laptop is working with Linux</title>
7037 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7038 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7039 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7040 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7041 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7042 batch of computers will work with Linux. Every year for the last few
7043 years the university have organised shared bid of a few thousand
7044 computers, and this year HP won the bid. Two different desktops and
7045 five different laptops are on the list this year. We in the UNIX
7046 group want to know which one of these computers work well with RHEL
7047 and Ubuntu, the two Linux distributions we currently handle at the
7048 university.&lt;/p&gt;
7049
7050 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7051 perhaps inspire others to test hardware as well. To test, I PXE
7052 install the OS version of choice, and log in as my normal user and run
7053 a few applications and plug in selected pieces of hardware. When
7054 something fail, I make a note about this in the test matrix and move
7055 on. If I have some spare time I try to report the bug to the OS
7056 vendor, but as I only have the machines for a short time, I rarely
7057 have the time to do this for all the problems I find.&lt;/p&gt;
7058
7059 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7060 I perform on a new model.&lt;/p&gt;
7061
7062 &lt;ul&gt;
7063
7064 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7065 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7066 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7067
7068 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7069 installation, X.org is working.&lt;/li&gt;
7070
7071 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7072 package mesa-utils on Ubuntu) and writing down the frames per second
7073 reported by the program.&lt;/li&gt;
7074
7075 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7076 logging in, and if I can hear this the test is successful. If there
7077 are several audio exits on the machine, I try them all and check if
7078 the Gnome/KDE audio mixer can control where to send the sound. I
7079 normally test this by playing
7080 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7081 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7082
7083 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7084 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7085
7086 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7087 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7088
7089 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7090 picture from the v4l device show up.&lt;/li&gt;
7091
7092 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7093 any bluetooth devices are discovered. In my office, I normally see a
7094 few.&lt;/li&gt;
7095
7096 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7097 memory modules lying around, and stick them in and see if Gnome/KDE
7098 notice this.&lt;/li&gt;
7099
7100 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7101 special button work, and if the laptop continue to work after
7102 resume.&lt;/li&gt;
7103
7104 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7105 adjusting background light, switching on/off external video output,
7106 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7107 laptop to laptop, so I just write down which are working and which are
7108 not.&lt;/li&gt;
7109
7110 &lt;li&gt;Some laptops have smart card readers, finger print readers,
7111 acceleration sensors etc. I rarely test these, as I do not know how
7112 to quickly test if they are working or not, so I only document their
7113 existence.&lt;/li&gt;
7114
7115 &lt;/ul&gt;
7116
7117 &lt;p&gt;By now I suspect you are really curious what the test results are
7118 for the HP machines I am testing. I&#39;m not done yet, so I will report
7119 the test results later. For now I can report that HP 8100 Elite work
7120 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
7121 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
7122 can see, I have most machines left to test. One interesting
7123 observation is that Ubuntu Lucid has almost twice the frame rate than
7124 RHEL6 with glxgears. No idea why.&lt;/p&gt;
7125 </description>
7126 </item>
7127
7128 <item>
7129 <title>Some thoughts on BitCoins</title>
7130 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
7131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
7132 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
7133 <description>&lt;p&gt;As I continue to explore
7134 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
7135 what properties the system have, and how it will be affected by laws
7136 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
7137
7138 &lt;p&gt;One interesting thing to note is that since the transactions are
7139 verified using a peer to peer network, all details about a transaction
7140 is known to everyone. This means that if a BitCoin address has been
7141 published like I did with mine in my initial post about BitCoin, it is
7142 possible for everyone to see how many BitCoins have been transfered to
7143 that address. There is even a web service to look at the details for
7144 all transactions. There I can see that my address
7145 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
7146 have received 16.06 Bitcoin, the
7147 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
7148 address of Simon Phipps have received 181.97 BitCoin and the address
7149 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
7150 of EFF have received 2447.38 BitCoins so far. Thank you to each and
7151 every one of you that donated bitcoins to support my activity. The
7152 fact that anyone can see how much money was transfered to a given
7153 address make it more obvious why the BitCoin community recommend to
7154 generate and hand out a new address for each transaction. I&#39;m told
7155 there is no way to track which addresses belong to a given person or
7156 organisation without the person or organisation revealing it
7157 themselves, as Simon, EFF and I have done.&lt;/p&gt;
7158
7159 &lt;p&gt;In Norway, and in most other countries, there are laws and
7160 regulations limiting how much money one can transfer across the border
7161 without declaring it. There are money laundering, tax and accounting
7162 laws and regulations I would expect to apply to the use of BitCoin.
7163 If the Skolelinux foundation
7164 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
7165 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
7166 normal bank transfers like EFF is doing, how should this be accounted?
7167 Given that it is impossible to know if money can cross the border or
7168 not, should everything or nothing be declared? What exchange rate
7169 should be used when calculating taxes? Would receivers have to pay
7170 income tax if the foundation were to pay Skolelinux contributors in
7171 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
7172
7173 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
7174 accepted by a lot of users. It must be possible to get easy access to
7175 the currency (as a wage or using currency exchanges), and it must be
7176 easy to spend it. At the moment BitCoin seem fairly easy to get
7177 access to, but there are very few places to spend it. I am not really
7178 a regular user of any of the vendor types currently accepting BitCoin,
7179 so I wonder when my kind of shop would start accepting BitCoins. I
7180 would like to buy electronics, travels and subway tickets, not herbs
7181 and books. :) The currency is young, and this will improve over time
7182 if it become popular, but I suspect regular banks will start to lobby
7183 to get BitCoin declared illegal if it become popular. I&#39;m sure they
7184 will claim it is helping fund terrorism and money laundering (which
7185 probably would be true, as is any currency in existence), but I
7186 believe the problems should be solved elsewhere and not by blaming
7187 currencies.&lt;/p&gt;
7188
7189 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
7190 CPU intensive process that depend on a bit of luck as well (as one is
7191 competing against all the other miners currently spending CPU cycles
7192 to see which one get the next lump of cash). The &quot;winner&quot; get 50
7193 BitCoin when this happen. Yesterday I came across the obvious way to
7194 join forces to increase ones changes of getting at least some coins,
7195 by coordinating the work on mining BitCoins across several machines
7196 and people, and sharing the result if one is lucky and get the 50
7197 BitCoins. Check out
7198 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
7199 if this sounds interesting. I have not had time to try to set up a
7200 machine to participate there yet, but have seen that running on ones
7201 own for a few days have not yield any BitCoins througth mining
7202 yet.&lt;/p&gt;
7203
7204 &lt;p&gt;Update 2010-12-15: Found an &lt;a
7205 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
7206 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
7207 it was interesting to read. The arguments presented seem to be
7208 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
7209 </description>
7210 </item>
7211
7212 <item>
7213 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
7214 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
7215 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
7216 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
7217 <description>&lt;p&gt;With this weeks lawless
7218 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
7219 attacks&lt;/a&gt; on Wikileak and
7220 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
7221 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
7222 not be trusted to handle money transactions.
7223 A blog post from
7224 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
7225 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
7226 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
7227 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
7228 some help from my friend to get it all running, and he even handed me
7229 some bitcoins to get started. I even donated a few bitcoins to Simon
7230 for helping me remember BitCoin.&lt;/p&gt;
7231
7232 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
7233 crypto-currency, decentralised and handled using peer-to-peer
7234 networks. It allows anonymous transactions and prohibits central
7235 control over the transactions, making it impossible for governments
7236 and companies alike to block donations and other transactions. The
7237 source is free software, and while the key dependency wxWidgets 2.9
7238 for the graphical user interface is missing in Debian, the command
7239 line client builds just fine. Hopefully Jonas
7240 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
7241 Debian&lt;/a&gt; soon.&lt;/p&gt;
7242
7243 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
7244 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
7245 bitcoins&lt;/a&gt; when selling services and goods, and there are even
7246 currency &quot;stock&quot; markets where the exchange rate is decided. There
7247 are not many users so far, but the concept seems promising. If you
7248 want to get started and lack a friend with any bitcoins to spare,
7249 you can even get
7250 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
7251 bitcoin at the time of writing). Use
7252 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
7253 on the current exchange rates.&lt;/p&gt;
7254
7255 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
7256 machines. If you want to support my activity, please send Bitcoin
7257 donations to the address
7258 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
7259 </description>
7260 </item>
7261
7262 <item>
7263 <title>Why isn&#39;t Debian Edu using VLC?</title>
7264 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
7265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
7266 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
7267 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
7268 presented, and the winner among the multimedia player were VLC.
7269 Personally, I like VLC, and it is my player of choice when I first try
7270 to play a video file or stream. Only if VLC fail will I drag out
7271 gmplayer to see if it can do better. The reason is mostly the failure
7272 model and trust. When VLC fail, it normally pop up a error message
7273 reporting the problem. When mplayer fail, it normally segfault or
7274 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
7275
7276 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
7277 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7278 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
7279 plugin to play web videos seamlessly, and the VLC browser plugin is
7280 not very good. For example, it lack in-line control buttons, so there
7281 is no way for the user to pause the video. Also, when I
7282 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
7283 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
7284 failed on several video pages where mplayer based plugins worked. If
7285 the browser plugin for VLC was as good as the gecko-mediaplayer
7286 package (which uses mplayer), we would switch.&lt;/P&gt;
7287
7288 &lt;p&gt;While VLC is a good player, its user interface is slightly
7289 annoying. The most annoying feature is its inconsistent use of
7290 keyboard shortcuts. When the player is in full screen mode, its
7291 shortcuts are different from when it is playing the video in a window.
7292 For example, space only work as pause when in full screen mode. I
7293 wish it had consisten shortcuts and that space also would work when in
7294 window mode. Another nice shortcut in gmplayer is [enter] to restart
7295 the current video. It is very nice when playing short videos from the
7296 web and want to restart it when new people arrive to have a look at
7297 what is going on.&lt;/p&gt;
7298 </description>
7299 </item>
7300
7301 <item>
7302 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
7303 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
7304 <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>
7305 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7306 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7307 upgrade testing of the
7308 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7309 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7310 This seem like a very good idea, so I adjusted by test scripts and
7311 can now present the updated result from today:&lt;/p&gt;
7312
7313 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7314
7315 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7316
7317 &lt;blockquote&gt;&lt;p&gt;
7318 apache2.2-bin
7319 aptdaemon
7320 baobab
7321 binfmt-support
7322 browser-plugin-gnash
7323 cheese-common
7324 cli-common
7325 cups-pk-helper
7326 dmz-cursor-theme
7327 empathy
7328 empathy-common
7329 freedesktop-sound-theme
7330 freeglut3
7331 gconf-defaults-service
7332 gdm-themes
7333 gedit-plugins
7334 geoclue
7335 geoclue-hostip
7336 geoclue-localnet
7337 geoclue-manual
7338 geoclue-yahoo
7339 gnash
7340 gnash-common
7341 gnome
7342 gnome-backgrounds
7343 gnome-cards-data
7344 gnome-codec-install
7345 gnome-core
7346 gnome-desktop-environment
7347 gnome-disk-utility
7348 gnome-screenshot
7349 gnome-search-tool
7350 gnome-session-canberra
7351 gnome-system-log
7352 gnome-themes-extras
7353 gnome-themes-more
7354 gnome-user-share
7355 gstreamer0.10-fluendo-mp3
7356 gstreamer0.10-tools
7357 gtk2-engines
7358 gtk2-engines-pixbuf
7359 gtk2-engines-smooth
7360 hamster-applet
7361 libapache2-mod-dnssd
7362 libapr1
7363 libaprutil1
7364 libaprutil1-dbd-sqlite3
7365 libaprutil1-ldap
7366 libart2.0-cil
7367 libboost-date-time1.42.0
7368 libboost-python1.42.0
7369 libboost-thread1.42.0
7370 libchamplain-0.4-0
7371 libchamplain-gtk-0.4-0
7372 libcheese-gtk18
7373 libclutter-gtk-0.10-0
7374 libcryptui0
7375 libdiscid0
7376 libelf1
7377 libepc-1.0-2
7378 libepc-common
7379 libepc-ui-1.0-2
7380 libfreerdp-plugins-standard
7381 libfreerdp0
7382 libgconf2.0-cil
7383 libgdata-common
7384 libgdata7
7385 libgdu-gtk0
7386 libgee2
7387 libgeoclue0
7388 libgexiv2-0
7389 libgif4
7390 libglade2.0-cil
7391 libglib2.0-cil
7392 libgmime2.4-cil
7393 libgnome-vfs2.0-cil
7394 libgnome2.24-cil
7395 libgnomepanel2.24-cil
7396 libgpod-common
7397 libgpod4
7398 libgtk2.0-cil
7399 libgtkglext1
7400 libgtksourceview2.0-common
7401 libmono-addins-gui0.2-cil
7402 libmono-addins0.2-cil
7403 libmono-cairo2.0-cil
7404 libmono-corlib2.0-cil
7405 libmono-i18n-west2.0-cil
7406 libmono-posix2.0-cil
7407 libmono-security2.0-cil
7408 libmono-sharpzip2.84-cil
7409 libmono-system2.0-cil
7410 libmtp8
7411 libmusicbrainz3-6
7412 libndesk-dbus-glib1.0-cil
7413 libndesk-dbus1.0-cil
7414 libopal3.6.8
7415 libpolkit-gtk-1-0
7416 libpt2.6.7
7417 libpython2.6
7418 librpm1
7419 librpmio1
7420 libsdl1.2debian
7421 libsrtp0
7422 libssh-4
7423 libtelepathy-farsight0
7424 libtelepathy-glib0
7425 libtidy-0.99-0
7426 media-player-info
7427 mesa-utils
7428 mono-2.0-gac
7429 mono-gac
7430 mono-runtime
7431 nautilus-sendto
7432 nautilus-sendto-empathy
7433 p7zip-full
7434 pkg-config
7435 python-aptdaemon
7436 python-aptdaemon-gtk
7437 python-axiom
7438 python-beautifulsoup
7439 python-bugbuddy
7440 python-clientform
7441 python-coherence
7442 python-configobj
7443 python-crypto
7444 python-cupshelpers
7445 python-elementtree
7446 python-epsilon
7447 python-evolution
7448 python-feedparser
7449 python-gdata
7450 python-gdbm
7451 python-gst0.10
7452 python-gtkglext1
7453 python-gtksourceview2
7454 python-httplib2
7455 python-louie
7456 python-mako
7457 python-markupsafe
7458 python-mechanize
7459 python-nevow
7460 python-notify
7461 python-opengl
7462 python-openssl
7463 python-pam
7464 python-pkg-resources
7465 python-pyasn1
7466 python-pysqlite2
7467 python-rdflib
7468 python-serial
7469 python-tagpy
7470 python-twisted-bin
7471 python-twisted-conch
7472 python-twisted-core
7473 python-twisted-web
7474 python-utidylib
7475 python-webkit
7476 python-xdg
7477 python-zope.interface
7478 remmina
7479 remmina-plugin-data
7480 remmina-plugin-rdp
7481 remmina-plugin-vnc
7482 rhythmbox-plugin-cdrecorder
7483 rhythmbox-plugins
7484 rpm-common
7485 rpm2cpio
7486 seahorse-plugins
7487 shotwell
7488 software-center
7489 system-config-printer-udev
7490 telepathy-gabble
7491 telepathy-mission-control-5
7492 telepathy-salut
7493 tomboy
7494 totem
7495 totem-coherence
7496 totem-mozilla
7497 totem-plugins
7498 transmission-common
7499 xdg-user-dirs
7500 xdg-user-dirs-gtk
7501 xserver-xephyr
7502 &lt;/p&gt;&lt;/blockquote&gt;
7503
7504 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7505
7506 &lt;blockquote&gt;&lt;p&gt;
7507 cheese
7508 ekiga
7509 eog
7510 epiphany-extensions
7511 evolution-exchange
7512 fast-user-switch-applet
7513 file-roller
7514 gcalctool
7515 gconf-editor
7516 gdm
7517 gedit
7518 gedit-common
7519 gnome-games
7520 gnome-games-data
7521 gnome-nettool
7522 gnome-system-tools
7523 gnome-themes
7524 gnuchess
7525 gucharmap
7526 guile-1.8-libs
7527 libavahi-ui0
7528 libdmx1
7529 libgalago3
7530 libgtk-vnc-1.0-0
7531 libgtksourceview2.0-0
7532 liblircclient0
7533 libsdl1.2debian-alsa
7534 libspeexdsp1
7535 libsvga1
7536 rhythmbox
7537 seahorse
7538 sound-juicer
7539 system-config-printer
7540 totem-common
7541 transmission-gtk
7542 vinagre
7543 vino
7544 &lt;/p&gt;&lt;/blockquote&gt;
7545
7546 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7547
7548 &lt;blockquote&gt;&lt;p&gt;
7549 gstreamer0.10-gnomevfs
7550 &lt;/p&gt;&lt;/blockquote&gt;
7551
7552 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7553
7554 &lt;blockquote&gt;&lt;p&gt;
7555 [nothing]
7556 &lt;/p&gt;&lt;/blockquote&gt;
7557
7558 &lt;p&gt;This is for KDE:&lt;/p&gt;
7559
7560 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7561
7562 &lt;blockquote&gt;&lt;p&gt;
7563 ksmserver
7564 &lt;/p&gt;&lt;/blockquote&gt;
7565
7566 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7567
7568 &lt;blockquote&gt;&lt;p&gt;
7569 kwin
7570 network-manager-kde
7571 &lt;/p&gt;&lt;/blockquote&gt;
7572
7573 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7574
7575 &lt;blockquote&gt;&lt;p&gt;
7576 arts
7577 dolphin
7578 freespacenotifier
7579 google-gadgets-gst
7580 google-gadgets-xul
7581 kappfinder
7582 kcalc
7583 kcharselect
7584 kde-core
7585 kde-plasma-desktop
7586 kde-standard
7587 kde-window-manager
7588 kdeartwork
7589 kdeartwork-emoticons
7590 kdeartwork-style
7591 kdeartwork-theme-icon
7592 kdebase
7593 kdebase-apps
7594 kdebase-workspace
7595 kdebase-workspace-bin
7596 kdebase-workspace-data
7597 kdeeject
7598 kdelibs
7599 kdeplasma-addons
7600 kdeutils
7601 kdewallpapers
7602 kdf
7603 kfloppy
7604 kgpg
7605 khelpcenter4
7606 kinfocenter
7607 konq-plugins-l10n
7608 konqueror-nsplugins
7609 kscreensaver
7610 kscreensaver-xsavers
7611 ktimer
7612 kwrite
7613 libgle3
7614 libkde4-ruby1.8
7615 libkonq5
7616 libkonq5-templates
7617 libnetpbm10
7618 libplasma-ruby
7619 libplasma-ruby1.8
7620 libqt4-ruby1.8
7621 marble-data
7622 marble-plugins
7623 netpbm
7624 nuvola-icon-theme
7625 plasma-dataengines-workspace
7626 plasma-desktop
7627 plasma-desktopthemes-artwork
7628 plasma-runners-addons
7629 plasma-scriptengine-googlegadgets
7630 plasma-scriptengine-python
7631 plasma-scriptengine-qedje
7632 plasma-scriptengine-ruby
7633 plasma-scriptengine-webkit
7634 plasma-scriptengines
7635 plasma-wallpapers-addons
7636 plasma-widget-folderview
7637 plasma-widget-networkmanagement
7638 ruby
7639 sweeper
7640 update-notifier-kde
7641 xscreensaver-data-extra
7642 xscreensaver-gl
7643 xscreensaver-gl-extra
7644 xscreensaver-screensaver-bsod
7645 &lt;/p&gt;&lt;/blockquote&gt;
7646
7647 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7648
7649 &lt;blockquote&gt;&lt;p&gt;
7650 ark
7651 google-gadgets-common
7652 google-gadgets-qt
7653 htdig
7654 kate
7655 kdebase-bin
7656 kdebase-data
7657 kdepasswd
7658 kfind
7659 klipper
7660 konq-plugins
7661 konqueror
7662 ksysguard
7663 ksysguardd
7664 libarchive1
7665 libcln6
7666 libeet1
7667 libeina-svn-06
7668 libggadget-1.0-0b
7669 libggadget-qt-1.0-0b
7670 libgps19
7671 libkdecorations4
7672 libkephal4
7673 libkonq4
7674 libkonqsidebarplugin4a
7675 libkscreensaver5
7676 libksgrd4
7677 libksignalplotter4
7678 libkunitconversion4
7679 libkwineffects1a
7680 libmarblewidget4
7681 libntrack-qt4-1
7682 libntrack0
7683 libplasma-geolocation-interface4
7684 libplasmaclock4a
7685 libplasmagenericshell4
7686 libprocesscore4a
7687 libprocessui4a
7688 libqalculate5
7689 libqedje0a
7690 libqtruby4shared2
7691 libqzion0a
7692 libruby1.8
7693 libscim8c2a
7694 libsmokekdecore4-3
7695 libsmokekdeui4-3
7696 libsmokekfile3
7697 libsmokekhtml3
7698 libsmokekio3
7699 libsmokeknewstuff2-3
7700 libsmokeknewstuff3-3
7701 libsmokekparts3
7702 libsmokektexteditor3
7703 libsmokekutils3
7704 libsmokenepomuk3
7705 libsmokephonon3
7706 libsmokeplasma3
7707 libsmokeqtcore4-3
7708 libsmokeqtdbus4-3
7709 libsmokeqtgui4-3
7710 libsmokeqtnetwork4-3
7711 libsmokeqtopengl4-3
7712 libsmokeqtscript4-3
7713 libsmokeqtsql4-3
7714 libsmokeqtsvg4-3
7715 libsmokeqttest4-3
7716 libsmokeqtuitools4-3
7717 libsmokeqtwebkit4-3
7718 libsmokeqtxml4-3
7719 libsmokesolid3
7720 libsmokesoprano3
7721 libtaskmanager4a
7722 libtidy-0.99-0
7723 libweather-ion4a
7724 libxklavier16
7725 libxxf86misc1
7726 okteta
7727 oxygencursors
7728 plasma-dataengines-addons
7729 plasma-scriptengine-superkaramba
7730 plasma-widget-lancelot
7731 plasma-widgets-addons
7732 plasma-widgets-workspace
7733 polkit-kde-1
7734 ruby1.8
7735 systemsettings
7736 update-notifier-common
7737 &lt;/p&gt;&lt;/blockquote&gt;
7738
7739 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
7740 aptitude a bit more similar, but there are still quite a lott of
7741 differences. I have no idea what packages should be installed after
7742 the upgrade, but hope those that do can have a look.&lt;/p&gt;
7743 </description>
7744 </item>
7745
7746 <item>
7747 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
7748 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
7749 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
7750 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
7751 <description>&lt;p&gt;Most of the computers in use by the
7752 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
7753 are virtual machines. And they have been Xen machines running on a
7754 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
7755 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
7756 bit harder that it could have been, because we set up the Xen virtual
7757 machines to get the virtual partitions from LVM, which as far as I
7758 know is not supported by KVM. So to migrate, we had to convert
7759 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
7760
7761 &lt;p&gt;I found
7762 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
7763 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
7764 migration. It uses qemu-img from the qemu package to make the disk
7765 image, parted to partition it, losetup and kpartx to present the disk
7766 image partions as devices, and dd to copy the data. I NFS mounted the
7767 new servers storage area on the old server to do the migration.&lt;/p&gt;
7768
7769 &lt;pre&gt;
7770 #!/bin/sh
7771
7772 # Based on
7773 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7774
7775 set -e
7776 set -x
7777
7778 if [ -z &quot;$1&quot; ] ; then
7779 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
7780 exit 1
7781 else
7782 host=&quot;$1&quot;
7783 fi
7784
7785 if [ ! -e /dev/vg_data/$host-disk ] ; then
7786 echo &quot;error: unable to find LVM volume for $host&quot;
7787 exit 1
7788 fi
7789
7790 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7791 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7792 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7793 totalsize=$(( ( $disksize + $swapsize ) ))
7794
7795 img=$host.img
7796 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
7797 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7798
7799 parted $img mklabel msdos
7800 parted $img mkpart primary linux-swap 0 $disksize
7801 parted $img mkpart primary ext2 $disksize $totalsize
7802 parted $img set 1 boot on
7803
7804 modprobe dm-mod
7805 losetup /dev/loop0 $img
7806 kpartx -a /dev/loop0
7807
7808 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
7809 fsck.ext3 -f /dev/mapper/loop0p1 || true
7810 mkswap /dev/mapper/loop0p2
7811
7812 kpartx -d /dev/loop0
7813 losetup -d /dev/loop0
7814 &lt;/pre&gt;
7815
7816 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
7817 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
7818
7819 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
7820 the new disk image attached, installed grub-pc and linux-image-686 and
7821 set up grub to boot from the disk image. After this, the KVM machines
7822 seem to work just fine.&lt;/p&gt;
7823 </description>
7824 </item>
7825
7826 <item>
7827 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
7828 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
7829 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
7830 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
7831 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
7832 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7833 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
7834 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
7835
7836 &lt;p&gt;I still do not know what a correct migration should look like, so I
7837 report any differences between apt and aptitude and hope someone else
7838 can see if anything should be changed.&lt;/p&gt;
7839
7840 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7841
7842 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7843
7844 &lt;blockquote&gt;&lt;p&gt;
7845 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7846 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
7847 dmz-cursor-theme empathy empathy-common finger
7848 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7849 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7850 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7851 gnome-cards-data gnome-codec-install gnome-core
7852 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7853 gnome-search-tool gnome-session-canberra gnome-spell
7854 gnome-system-log gnome-themes-extras gnome-themes-more
7855 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7856 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7857 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7858 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7859 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
7860 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
7861 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
7862 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
7863 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
7864 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7865 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
7866 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7867 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7868 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7869 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7870 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7871 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7872 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7873 libmono-security2.0-cil libmono-sharpzip2.84-cil
7874 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
7875 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
7876 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
7877 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
7878 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
7879 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
7880 libxalan2-java libxerces2-java media-player-info mesa-utils
7881 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
7882 nautilus-sendto-empathy openoffice.org-writer2latex
7883 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
7884 python-aptdaemon python-aptdaemon-gtk python-axiom
7885 python-beautifulsoup python-bugbuddy python-clientform
7886 python-coherence python-configobj python-crypto python-cupshelpers
7887 python-cupsutils python-eggtrayicon python-elementtree
7888 python-epsilon python-evolution python-feedparser python-gdata
7889 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7890 python-gtksourceview2 python-httplib2 python-louie python-mako
7891 python-markupsafe python-mechanize python-nevow python-notify
7892 python-opengl python-openssl python-pam python-pkg-resources
7893 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7894 python-tagpy python-twisted-bin python-twisted-conch
7895 python-twisted-core python-twisted-web python-utidylib python-webkit
7896 python-xdg python-zope.interface remmina remmina-plugin-data
7897 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7898 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7899 software-center svgalibg1 system-config-printer-udev
7900 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
7901 totem totem-coherence totem-mozilla totem-plugins
7902 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7903 zip
7904 &lt;/p&gt;&lt;/blockquote&gt;
7905
7906 Installed using apt-get, removed with aptitude
7907
7908 &lt;blockquote&gt;&lt;p&gt;
7909 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7910 epiphany-extensions epiphany-gecko evolution-exchange
7911 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7912 gedit-common gnome-app-install gnome-games gnome-games-data
7913 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7914 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7915 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7916 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
7917 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
7918 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
7919 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
7920 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7921 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7922 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7923 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
7924 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
7925 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7926 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7927 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7928 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7929 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
7930 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
7931 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
7932 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
7933 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
7934 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7935 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7936 sound-juicer swfdec-gnome system-config-printer totem-common
7937 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7938 &lt;/p&gt;&lt;/blockquote&gt;
7939
7940 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7941
7942 &lt;blockquote&gt;&lt;p&gt;
7943 gstreamer0.10-gnomevfs
7944 &lt;/p&gt;&lt;/blockquote&gt;
7945
7946 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7947
7948 &lt;blockquote&gt;&lt;p&gt;
7949 [nothing]
7950 &lt;/p&gt;&lt;/blockquote&gt;
7951
7952 &lt;p&gt;This is for KDE:&lt;/p&gt;
7953
7954 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7955
7956 &lt;blockquote&gt;&lt;p&gt;
7957 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
7958 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7959 ghostscript-x git gnome-audio gnugo granatier gs-common
7960 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7961 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7962 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7963 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7964 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7965 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7966 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7967 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7968 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7969 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7970 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7971 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
7972 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7973 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7974 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7975 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7976 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7977 libkrossui4 libmailtools-perl libmime-tools-perl
7978 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7979 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7980 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7981 lirc luatex marble networkstatus noatun-plugins
7982 openoffice.org-writer2latex palapeli palapeli-data parley
7983 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7984 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7985 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7986 ttf-sazanami-gothic
7987 &lt;/p&gt;&lt;/blockquote&gt;
7988
7989 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7990
7991 &lt;blockquote&gt;&lt;p&gt;
7992 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7993 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7994 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7995 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7996 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7997 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7998 kitchensync kiten kjumpingcube klatin klettres klickety klines
7999 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8000 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8001 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8002 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8003 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8004 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8005 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8006 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8007 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8008 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8009 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8010 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8011 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8012 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8013 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8014 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8015 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8016 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8017 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8018 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8019 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8020 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8021 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8022 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8023 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8024 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8025 &lt;/p&gt;&lt;/blockquote&gt;
8026
8027 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8028
8029 &lt;blockquote&gt;&lt;p&gt;
8030 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8031 kdeartwork kdebase kdebase-apps kdebase-workspace
8032 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8033 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8034 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8035 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8036 xscreensaver-screensaver-bsod
8037 &lt;/p&gt;&lt;/blockquote&gt;
8038
8039 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8040
8041 &lt;blockquote&gt;&lt;p&gt;
8042 kdebase-bin konq-plugins konqueror
8043 &lt;/p&gt;&lt;/blockquote&gt;
8044 </description>
8045 </item>
8046
8047 <item>
8048 <title>Gnash buildbot slave and Debian kfreebsd</title>
8049 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8051 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8052 <description>&lt;p&gt;Answering
8053 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8054 call from the Gnash project&lt;/a&gt; for
8055 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8056 current source, I have set up a virtual KVM machine on the Debian
8057 Edu/Skolelinux virtualization host to test the git source on
8058 Debian/Squeeze. I hope this can help the developers in getting new
8059 releases out more often.&lt;/p&gt;
8060
8061 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8062 I have considered setting up a &lt;a
8063 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8064 machine as well. I have also considered using the kfreebsd
8065 architecture in Debian as a file server in NUUG to get access to the 5
8066 TB zfs volume we currently use to store DV video. Because of this, I
8067 finally got around to do a test installation of Debian/Squeeze with
8068 kfreebsd. Installation went fairly smooth, thought I noticed some
8069 visual glitches in the cdebconf dialogs (black cursor left on the
8070 screen at random locations). Have not gotten very far with the
8071 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8072 fatal problem. Have to spend some more time on it to see if it is
8073 useful as a file server for NUUG. Will try to find time to set up a
8074 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8075 </description>
8076 </item>
8077
8078 <item>
8079 <title>Debian in 3D</title>
8080 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8081 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8082 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8083 <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;
8084
8085 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8086 3D linked in from
8087 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8088 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8089 </description>
8090 </item>
8091
8092 <item>
8093 <title>Software updates 2010-10-24</title>
8094 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8096 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8097 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8098
8099 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8100 raise money for the project is going well. The lower limit of 10
8101 signers was reached in 24 hours, and so far 13 people have signed it.
8102 More signers and more funding is most welcome, and I am really curious
8103 how far we can get before the time limit of December 24 is reached.
8104 :)&lt;/p&gt;
8105
8106 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
8107 about what appear to be a great code coverage tool capable of
8108 generating code coverage stats without any changes to the source code.
8109 It is called
8110 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
8111 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
8112 It is missing in Debian, but the git source built just fine in Squeeze
8113 after I installed libelf-dev, libdwarf-dev, pkg-config and
8114 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8115 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
8116
8117 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
8118 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
8119 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
8120 alpha test release of the Squeeze based Debian Edu /
8121 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
8122 release. Give it a try if you need a complete linux solution for your
8123 school, including central infrastructure server, workstations, thin
8124 client servers and diskless workstations. A nice touch added
8125 yesterday is RDP support on the thin client servers, for windows
8126 clients to get a Linux desktop on request.&lt;/p&gt;
8127 </description>
8128 </item>
8129
8130 <item>
8131 <title>Some notes on Flash in Debian and Debian Edu</title>
8132 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
8133 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
8134 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
8135 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
8136 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
8137 second most popular used package that is missing in Debian. The sixth
8138 most popular is flashplayer-mozilla. This is a clear indication that
8139 working flash is important for Debian users. Around 10 percent of the
8140 users submitting data to popcon.debian.org have this package
8141 installed.&lt;/p&gt;
8142
8143 &lt;p&gt;In the report written by Lars Risan in August 2008
8144&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
8145 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8146 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
8147 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8148 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
8149 web sites require Flash to work, and lacking working Flash support in
8150 the web browser and the problems with installing it was perceived as a
8151 good reason to stay with Windows.&lt;/p&gt;
8152
8153 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
8154 said to be the retarded cousin that did not really understand
8155 everything you told him but could work fairly well. This was a
8156 comment regarding the problems Linux have with proprietary formats and
8157 non-standard web pages, and is sad because it exposes a fairly common
8158 understanding of whose fault it is if web pages that only work in for
8159 example Internet Explorer 6 fail to work on Firefox, and funny because
8160 it explain very well how annoying it is for users when Linux
8161 distributions do not work with the documents they receive or the web
8162 pages they want to visit.&lt;/p&gt;
8163
8164 &lt;p&gt;This is part of the reason why I believe it is important for Debian
8165 and Debian Edu to have a well working Flash implementation in the
8166 distribution, to get at least popular sites as Youtube and Google
8167 Video to working out of the box. For Squeeze, Debian have the chance
8168 to include the latest version of Gnash that will make this happen, as
8169 the new release 0.8.8 was published a few weeks ago and is resting in
8170 unstable. The new version work with more sites that version 0.8.7.
8171 The Gnash maintainers have asked for a freeze exception, but the
8172 release team have not had time to reply to it yet. I hope they agree
8173 with me that Flash is important for the Debian desktop users, and thus
8174 accept the new package into Squeeze.&lt;/p&gt;
8175 </description>
8176 </item>
8177
8178 <item>
8179 <title>Circular package dependencies harms apt recovery</title>
8180 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
8181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
8182 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
8183 <description>&lt;p&gt;I discovered this while doing
8184 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
8185 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
8186 in Debian still got circular dependencies, and it is often claimed
8187 that apt and aptitude should be able to handle this just fine, but
8188 some times these dependency loops causes apt to fail.&lt;/p&gt;
8189
8190 &lt;p&gt;An example is from todays
8191 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
8192 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
8193 causes perl-modules to fail to upgrade. The cause is simple. If a
8194 package fail to unpack, then only part of packages with the circular
8195 dependency might end up being unpacked when unpacking aborts, and the
8196 ones already unpacked will fail to configure in the recovery phase
8197 because its dependencies are unavailable.&lt;/p&gt;
8198
8199 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
8200
8201 &lt;blockquote&gt;&lt;pre&gt;
8202 dpkg: dependency problems prevent configuration of perl-modules:
8203 perl-modules depends on perl (&gt;= 5.10.1-1); however:
8204 Version of perl on system is 5.10.0-19lenny2.
8205 dpkg: error processing perl-modules (--configure):
8206 dependency problems - leaving unconfigured
8207 &lt;/pre&gt;&lt;/blockquote&gt;
8208
8209 &lt;p&gt;The perl/perl-modules circular dependency is already
8210 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
8211 hopefully be solved as soon as possible, but it is not the only one,
8212 and each one of these loops in the dependency tree can cause similar
8213 failures. Of course, they only occur when there are bugs in other
8214 packages causing the unpacking to fail, but it is rather nasty when
8215 the failure of one package causes the problem to become worse because
8216 of dependency loops.&lt;/p&gt;
8217
8218 &lt;p&gt;Thanks to
8219 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
8220 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
8221 dependencies
8222 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
8223 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
8224
8225 &lt;p&gt;Todays testing also exposed a bug in
8226 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
8227 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
8228 apt-get and aptitude, the latter possibly caused by some circular
8229 dependency. Reported both to BTS to try to get someone to look at
8230 it.&lt;/p&gt;
8231 </description>
8232 </item>
8233
8234 <item>
8235 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
8236 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
8237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
8238 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
8239 <description>&lt;p&gt;This is a
8240 &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;
8241 on my
8242 &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
8243 work&lt;/a&gt; on
8244 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
8245 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
8246
8247 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
8248 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8249 and dhcp3-server-ldap in Debian use the LDAP server. The two
8250 implementations are quite different in how they use LDAP.&lt;/p&gt;
8251
8252 To get this information, I started slapd with debugging enabled and
8253 dumped the debug output to a file to get the LDAP searches performed
8254 on a Debian Edu main-server. Here is a summary.
8255
8256 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
8257
8258 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
8259 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
8260 the web.
8261
8262 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
8263 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
8264 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
8265 reverse entries are in two different subtrees in LDAP with a structure
8266 based on the DNS names, as in tjener.intern and
8267 2.2.0.10.in-addr.arpa.&lt;/p&gt;
8268
8269 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
8270 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
8271 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
8272 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
8273 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
8274 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
8275 forward entries, it is looking for attributes named dnsttl, arecord,
8276 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8277 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8278 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8279 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8280 spfrecord and modifytimestamp. For reverse entries it is looking for
8281 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8282 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8283 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8284 ldapsearch commands could look like this:&lt;/p&gt;
8285
8286 &lt;blockquote&gt;&lt;pre&gt;
8287 ldapsearch -h ldap \
8288 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8289 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8290 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8291 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8292 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8293 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8294
8295 ldapsearch -h ldap \
8296 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8297 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
8298 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8299 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8300 srvrecord naptrrecord modifytimestamp
8301 &lt;/pre&gt;&lt;/blockquote&gt;
8302
8303 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
8304 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8305 example LDAP objects used there. In addition to these objects, the
8306 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8307 also exist.&lt;/p&gt;
8308
8309 &lt;blockquote&gt;&lt;pre&gt;
8310 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8311 objectclass: top
8312 objectclass: dnsdomain
8313 objectclass: domainrelatedobject
8314 dc: tjener
8315 arecord: 10.0.2.2
8316 associateddomain: tjener.intern
8317
8318 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8319 objectclass: top
8320 objectclass: dnsdomain2
8321 objectclass: domainrelatedobject
8322 dc: 2
8323 ptrrecord: tjener.intern
8324 associateddomain: 2.2.0.10.in-addr.arpa
8325 &lt;/pre&gt;&lt;/blockquote&gt;
8326
8327 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8328 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8329 same base as in the tree mode for a object with filter
8330 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8331 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8332 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8333 naptrrecord and modifytimestamp. For reverse entires it also do a
8334 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8335 and the requested attributes are associateddomain, dnsttl and
8336 modifytimestamp. In short, in strict mode the objects with ptrrecord
8337 go away, and the arecord attribute in the forward object is used
8338 instead.&lt;/p&gt;
8339
8340 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8341 like this:&lt;/p&gt;
8342
8343 &lt;blockquote&gt;&lt;pre&gt;
8344 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8345 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8346 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8347 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8348 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8349 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8350
8351 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8352 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8353 &lt;/pre&gt;&lt;/blockquote&gt;
8354
8355 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8356 search for SOA records, which behave similar to the forward and
8357 reverse lookups.&lt;/p&gt;
8358
8359 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8360 specify any objectclass names, and instead look for the attributes it
8361 need to generate a DNS reply. This make it able to work with any
8362 objectclass that provide the needed attributes.&lt;/p&gt;
8363
8364 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8365 dnsdomain2 schemas. The latter is used for reverse entries like
8366 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8367
8368 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8369 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8370 attributes) and domainrelatedobject (for associatedDomain). The use
8371 of structural object classes make it impossible to combine these
8372 classes with the object classes used by DHCP.&lt;/p&gt;
8373
8374 &lt;p&gt;There are other schemas that could be used too, for example the
8375 dnszone structural object class used by Gosa and bind-sdb for the DNS
8376 attributes combined with the domainrelatedobject object class, but in
8377 this case some unused attributes would have to be included as well
8378 (zonename and relativedomainname).&lt;/p&gt;
8379
8380 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8381 mode and not use any of the existing objectclasses (dnsdomain,
8382 dnsdomain2 and dnszone) when one want to combine the DNS information
8383 with DHCP information, and instead create a auxiliary object class
8384 defined something like this (using the attributes defined for
8385 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8386
8387 &lt;blockquote&gt;&lt;pre&gt;
8388 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8389 SUP top
8390 AUXILIARY
8391 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8392 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8393 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8394 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8395 A6Record $ DNAMERecord
8396 ))
8397 &lt;/pre&gt;&lt;/blockquote&gt;
8398
8399 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8400 the domainrelatedobject object class, and allow any entity to include
8401 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8402 developers asking for their view on this schema and if they are
8403 interested in providing such schema with PowerDNS, and I hope my
8404 message will be accepted into their mailing list soon.&lt;/p&gt;
8405
8406 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8407
8408 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8409 the object attributes, and then uses the attributes it want. This
8410 make it harder to figure out exactly what attributes are used, but
8411 thanks to the working example in Debian Edu I can at least get an idea
8412 what is needed without having to read the source code.&lt;/p&gt;
8413
8414 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8415 search filter to use to locate the correct dhcpServer entity is
8416 stored. These are the relevant entries from
8417 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8418
8419 &lt;blockquote&gt;&lt;pre&gt;
8420 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8421 ldap-dhcp-server-cn &quot;dhcp&quot;;
8422 &lt;/pre&gt;&lt;/blockquote&gt;
8423
8424 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8425 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8426 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8427 search result is this entry:&lt;/p&gt;
8428
8429 &lt;blockquote&gt;&lt;pre&gt;
8430 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8431 cn: dhcp
8432 objectClass: top
8433 objectClass: dhcpServer
8434 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8435 &lt;/pre&gt;&lt;/blockquote&gt;
8436
8437 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8438 subtree with DHCP configuration. The DHCP configuration subtree base
8439 is located using a base scope search with base &quot;cn=DHCP
8440 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8441 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8442 The search result is this entry:&lt;/p&gt;
8443
8444 &lt;blockquote&gt;&lt;pre&gt;
8445 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8446 cn: DHCP Config
8447 objectClass: top
8448 objectClass: dhcpService
8449 objectClass: dhcpOptions
8450 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8451 dhcpStatements: ddns-update-style none
8452 dhcpStatements: authoritative
8453 dhcpOption: smtp-server code 69 = array of ip-address
8454 dhcpOption: www-server code 72 = array of ip-address
8455 dhcpOption: wpad-url code 252 = text
8456 &lt;/pre&gt;&lt;/blockquote&gt;
8457
8458 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8459 all the DHCP configuration is loaded, it is ready to receive requests.
8460 The subtree in Debian Edu contain objects with object classes
8461 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8462 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8463 and information about netmasks, dynamic range etc. Leaving out the
8464 details here because it is not relevant for the focus of my
8465 investigation, which is to see if it is possible to merge dns and dhcp
8466 related computer objects.&lt;/p&gt;
8467
8468 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8469 of the client (00:00:00:00:00:00 in this example), using a subtree
8470 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8471 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8472 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8473 like:&lt;/p&gt;
8474
8475 &lt;blockquote&gt;&lt;pre&gt;
8476 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8477 cn: hostname
8478 objectClass: top
8479 objectClass: dhcpHost
8480 dhcpHWAddress: ethernet 00:00:00:00:00:00
8481 dhcpStatements: fixed-address hostname
8482 &lt;/pre&gt;&lt;/blockquote&gt;
8483
8484 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8485 The object classes need to have fixed names, and the configuration
8486 need to be stored in a fairly specific LDAP structure. On the
8487 positive side, the invidiual dhcpHost entires can be anywhere without
8488 the DN pointed to by the dhcpServer entries. The latter should make
8489 it possible to group all host entries in a subtree next to the
8490 configuration entries, and this subtree can also be shared with the
8491 DNS server if the schema proposed above is combined with the dhcpHost
8492 structural object class.
8493
8494 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8495
8496 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8497 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8498 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8499 allowing DNS objects to be stored anywhere under the base cn specified
8500 in the configuration.&lt;/p&gt;
8501
8502 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8503 regarding which LDAP schemas to use and which LDAP structure to use.
8504 I guess one could implement ones own schema, as long as the
8505 objectclasses and attributes have the names used, but this do not
8506 really help when the DHCP subtree need to have a fairly fixed
8507 structure.&lt;/p&gt;
8508
8509 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8510 this might work for Debian Edu:&lt;/p&gt;
8511
8512 &lt;blockquote&gt;&lt;pre&gt;
8513 ou=services
8514 cn=machine-info (dhcpService) - dhcpServiceDN points here
8515 cn=dhcp (dhcpServer)
8516 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8517 cn=10.0.2.0 (dhcpSubnet)
8518 cn=group1 (dhcpGroup/dhcpOptions)
8519 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8520 cn=192.168.0.0 (dhcpSubnet)
8521 cn=group1 (dhcpGroup/dhcpOptions)
8522 ou=machines - PowerDNS base points here
8523 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8524 &lt;/pre&gt;&lt;/blockquote&gt;
8525
8526 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8527 entries to be in the dhcpGroup subtrees, the entries can be stored
8528 there instead of a common machines subtree, and the PowerDNS base
8529 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8530
8531 &lt;p&gt;The combined object under the machines subtree would look something
8532 like this:&lt;/p&gt;
8533
8534 &lt;blockquote&gt;&lt;pre&gt;
8535 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8536 dc: hostname
8537 objectClass: top
8538 objectClass: dhcpHost
8539 objectclass: domainrelatedobject
8540 objectclass: dnsDomainAux
8541 associateddomain: hostname.intern
8542 arecord: 10.11.12.13
8543 dhcpHWAddress: ethernet 00:00:00:00:00:00
8544 dhcpStatements: fixed-address hostname.intern
8545 &lt;/pre&gt;&lt;/blockquote&gt;
8546
8547 &lt;/p&gt;One could even add the LTSP configuration associated with a given
8548 machine, as long as the required attributes are available in a
8549 auxiliary object class.&lt;/p&gt;
8550 </description>
8551 </item>
8552
8553 <item>
8554 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
8555 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
8556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
8557 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
8558 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
8559 DHCP services in Debian Edu to use the same LDAP objects for a given
8560 computer, to avoid the possibility of having a inconsistent state for
8561 a computer in LDAP (as in DHCP but no DNS entry or the other way
8562 around) and make it easier to add computers to LDAP.&lt;/p&gt;
8563
8564 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
8565 information finally found a solution that seem to work.&lt;/p&gt;
8566
8567 &lt;p&gt;The old setup required three LDAP objects for a given computer.
8568 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8569 we switch powerdns to use its strict LDAP method (ldap-method=strict
8570 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8571 merged into one while making it impossible to transfer the reverse map
8572 to a slave DNS server.&lt;/p&gt;
8573
8574 &lt;p&gt;If we also replace the object class used to get the DNS related
8575 attributes to one allowing these attributes to be combined with the
8576 dhcphost object class, we can merge the DNS and DHCP entries into one.
8577 I&#39;ve written such object class in the dnsdomainaux.schema file (need
8578 proper OIDs, but that is a minor issue), and tested the setup. It
8579 seem to work.&lt;/p&gt;
8580
8581 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
8582 for both DNS and DHCP, and even the LTSP configuration I suggested in
8583 an earlier email. The combined LDAP object will look something like
8584 this:&lt;/p&gt;
8585
8586 &lt;blockquote&gt;&lt;pre&gt;
8587 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8588 cn: hostname
8589 objectClass: dhcphost
8590 objectclass: domainrelatedobject
8591 objectclass: dnsdomainaux
8592 associateddomain: hostname.intern
8593 arecord: 10.11.12.13
8594 dhcphwaddress: ethernet 00:00:00:00:00:00
8595 dhcpstatements: fixed-address hostname
8596 ldapconfigsound: Y
8597 &lt;/pre&gt;&lt;/blockquote&gt;
8598
8599 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
8600 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8601 before asking DNS to resolve the fixed-adddress. LTSP will use
8602 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
8603
8604 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
8605 dhcphost in a different location, to allow us to put the objects
8606 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
8607 that. If I can&#39;t figure out a way to do that, we can still get rid of
8608 the hosts subtree and move all its content into the DHCP Config tree
8609 (which probably should be renamed to be more related to the new
8610 content. I suspect cn=dnsdhcp,ou=services or something like that
8611 might be a good place to put it.&lt;/p&gt;
8612
8613 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8614 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8615 </description>
8616 </item>
8617
8618 <item>
8619 <title>Idea for storing LTSP configuration in LDAP</title>
8620 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
8621 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
8622 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
8623 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
8624 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8625 clients, and that this can be used to fetch configuration from LDAP if
8626 Debian Edu choose to store configuration there.&lt;/p&gt;
8627
8628 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
8629 to get configuration from LDAP. The idea is to look up the MAC
8630 address of the client in LDAP, and look for attributes on the form
8631 ltspconfigsetting=value, and use this to export SETTING=value to the
8632 LTSP clients.&lt;/p&gt;
8633
8634 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
8635 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
8636 allowing us to store all information about a computer in one place.&lt;/p&gt;
8637
8638 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
8639 this approach. A real LDAP schema for the ltspClientAux objectclass
8640 need to be written. Comments, suggestions, etc?&lt;/p&gt;
8641
8642 &lt;blockquote&gt;&lt;pre&gt;
8643 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8644 #
8645 # Fetch LTSP client settings from LDAP based on MAC address
8646 #
8647 # Uses ethernet address as stored in the dhcpHost objectclass using
8648 # the dhcpHWAddress attribute or ethernet address stored in the
8649 # ieee802Device objectclass with the macAddress attribute.
8650 #
8651 # This module is written to be schema agnostic, and only depend on the
8652 # existence of attribute names.
8653 #
8654 # The LTSP configuration variables are saved directly using a
8655 # ltspConfig prefix and uppercasing the rest of the attribute name.
8656 # To set the SERVER variable, set the ltspConfigServer attribute.
8657 #
8658 # Some LDAP schema should be created with all the relevant
8659 # configuration settings. Something like this should work:
8660 #
8661 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
8662 # SUP top
8663 # AUXILIARY
8664 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8665
8666 LDAPSERVER=$(debian-edu-ldapserver)
8667 if [ &quot;$LDAPSERVER&quot; ] ; then
8668 LDAPBASE=$(debian-edu-ldapserver -b)
8669 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
8670 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
8671 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
8672 grep &#39;^ltspConfig&#39; | while read attr value ; do
8673 # Remove prefix and convert to upper case
8674 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
8675 # bass value on to clients
8676 eval &quot;$attr=$value; export $attr&quot;
8677 done
8678 done
8679 fi
8680 &lt;/pre&gt;&lt;/blockquote&gt;
8681
8682 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
8683 the while block might end up in a subshell causing the variables set
8684 there to not show up in ltsp-config, but if that is the case I am sure
8685 the code can be restructured to make sure the variables are passed on.
8686 I expect that can be solved with some testing. :)&lt;/p&gt;
8687
8688 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8689 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8690
8691 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
8692 configuration in LDAP that was created around year 2000 by
8693 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
8694 Xperience, Inc., 2000&lt;/a&gt;. I found its
8695 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
8696 personal home page over at redhat.com.&lt;/p&gt;
8697 </description>
8698 </item>
8699
8700 <item>
8701 <title>jXplorer, a very nice LDAP GUI</title>
8702 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
8703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
8704 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
8705 <description>&lt;p&gt;Since
8706 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
8707 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
8708 LDAP GUI that is even better than luma. The java application
8709 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
8710 moving LDAP objects and subtrees using drag-and-drop, and can
8711 authenticate using Kerberos. I have only tested the Kerberos
8712 authentication, but do not have a LDAP setup allowing me to rewrite
8713 LDAP with my test user yet. It is
8714 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
8715 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
8716 have with it is how it handle errors. If something go wrong, its
8717 non-intuitive behaviour require me to go through some query work list
8718 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
8719 </description>
8720 </item>
8721
8722 <item>
8723 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
8724 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
8725 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
8726 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
8727 <description>&lt;p&gt;Here is a short update on my &lt;a
8728 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
8729 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
8730 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
8731 not reporting the status for KDE, because the upgrade crashes when
8732 aptitude try because of missing conflicts
8733 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
8734 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
8735
8736 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
8737 complete list of the installed packages. Based on this I see these
8738 differences when I did a test run today. As usual, I do not really
8739 know what the correct set of packages would be, but thought it best to
8740 publish the difference.&lt;/p&gt;
8741
8742 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8743
8744 &lt;blockquote&gt;&lt;p&gt;
8745 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
8746 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
8747 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8748 libgtksourceview-common libpt-1.10.10-plugins-alsa
8749 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8750 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8751 python-4suite-xml python-eggtrayicon python-gtkhtml2
8752 python-gtkmozembed svgalibg1 xserver-xephyr zip
8753 &lt;/p&gt;&lt;/blockquote&gt;
8754
8755 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8756
8757 &lt;blockquote&gt;&lt;p&gt;
8758 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8759 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8760 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
8761 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
8762 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
8763 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
8764 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8765 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8766 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8767 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
8768 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
8769 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
8770 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8771 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
8772 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8773 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
8774 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
8775 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8776 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8777 mysql-common swfdec-gnome totem-gstreamer wodim
8778 &lt;/p&gt;&lt;/blockquote&gt;
8779
8780 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8781
8782 &lt;blockquote&gt;&lt;p&gt;
8783 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8784 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8785 xserver-xorg-input-all xserver-xorg-input-evdev
8786 xserver-xorg-input-kbd xserver-xorg-input-mouse
8787 xserver-xorg-input-synaptics xserver-xorg-video-all
8788 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8789 xserver-xorg-video-chips xserver-xorg-video-cirrus
8790 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8791 xserver-xorg-video-glint xserver-xorg-video-i128
8792 xserver-xorg-video-i740 xserver-xorg-video-mach64
8793 xserver-xorg-video-mga xserver-xorg-video-neomagic
8794 xserver-xorg-video-nouveau xserver-xorg-video-nv
8795 xserver-xorg-video-r128 xserver-xorg-video-radeon
8796 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8797 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8798 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8799 xserver-xorg-video-sis xserver-xorg-video-sisusb
8800 xserver-xorg-video-tdfx xserver-xorg-video-tga
8801 xserver-xorg-video-trident xserver-xorg-video-tseng
8802 xserver-xorg-video-vesa xserver-xorg-video-vmware
8803 xserver-xorg-video-voodoo
8804 &lt;/p&gt;&lt;/blockquote&gt;
8805
8806 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8807
8808 &lt;blockquote&gt;&lt;p&gt;
8809 deskbar-applet xserver-xorg xserver-xorg-core
8810 xserver-xorg-input-wacom xserver-xorg-video-intel
8811 xserver-xorg-video-openchrome
8812 &lt;/p&gt;&lt;/blockquote&gt;
8813
8814 &lt;p&gt;I was told on IRC that the xorg-xserver package was
8815 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
8816 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
8817 No idea when it hits Squeeze, but when it does I hope it will reduce
8818 the difference somewhat.
8819 </description>
8820 </item>
8821
8822 <item>
8823 <title>LUMA, a very nice LDAP GUI</title>
8824 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
8825 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
8826 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
8827 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
8828 directory in Debian Edu, and in the process I started to miss a GUI
8829 tool to browse the LDAP tree. The only one I was able to find in
8830 Debian/Squeeze and Lenny is
8831 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
8832 be a great tool to get a overview of the current LDAP directory
8833 populated by default in Skolelinux. Thanks to it, I have been able to
8834 find empty and obsolete subtrees, misplaced objects and duplicate
8835 objects. It will be installed by default in Debian/Squeeze. If you
8836 are working with LDAP, give it a go. :)&lt;/p&gt;
8837
8838 &lt;p&gt;I did notice one problem with it I have not had time to report to
8839 the BTS yet. There is no .desktop file in the package, so the tool do
8840 not show up in the Gnome and KDE menus, but only deep down in in the
8841 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8842 released.&lt;/p&gt;
8843
8844 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
8845 like to move objects and remove subtrees directly in the GUI, but have
8846 not found a way to do that with LUMA yet. So in the mean time, I use
8847 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
8848
8849 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
8850 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8851
8852 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
8853 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
8854 useful GUI alternative. It seem like a good tool, but is unmaintained
8855 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8856 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
8857 </description>
8858 </item>
8859
8860 <item>
8861 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
8862 <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>
8863 <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>
8864 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
8865 <description>&lt;p&gt;A while back, I
8866 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
8867 about the fact&lt;/a&gt; that it is not possible with the provided schemas
8868 for storing DNS and DHCP information in LDAP to combine the two sets
8869 of information into one LDAP object representing a computer.&lt;/p&gt;
8870
8871 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
8872 the dhcpHost object class auxiliary, to allow it to be combined with
8873 the dNSDomain object class, and thus forming one object for one
8874 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
8875
8876 &lt;p&gt;If I understand this correctly, it is not safe to do this change
8877 without also changing the assigned number for the object class, and I
8878 do not know enough about LDAP schema design to do that properly for
8879 Debian Edu.&lt;/p&gt;
8880
8881 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
8882 the
8883 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
8884 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
8885 available today from IETF.&lt;/p&gt;
8886
8887 &lt;pre&gt;
8888 --- dhcp.schema (revision 65192)
8889 +++ dhcp.schema (working copy)
8890 @@ -376,7 +376,7 @@
8891 objectclass ( 2.16.840.1.113719.1.203.6.6
8892 NAME &#39;dhcpHost&#39;
8893 DESC &#39;This represents information about a particular client&#39;
8894 - SUP top
8895 + SUP top AUXILIARY
8896 MUST cn
8897 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8898 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
8899 &lt;/pre&gt;
8900
8901 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
8902 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8903 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
8904
8905 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8906 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8907 </description>
8908 </item>
8909
8910 <item>
8911 <title>Calling tasksel like the installer, while still getting useful output</title>
8912 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
8913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
8914 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
8915 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
8916 installs packages during the normal debian-installer run. Until now,
8917 I have ended up letting tasksel do the work, with the annoying problem
8918 of not getting any feedback at all when something fails (like a
8919 conffile question from dpkg or a download that fails), using code like
8920 this:
8921
8922 &lt;blockquote&gt;&lt;pre&gt;
8923 export DEBIAN_FRONTEND=noninteractive
8924 tasksel --new-install
8925 &lt;/pre&gt;&lt;/blockquote&gt;
8926
8927 This would invoke tasksel, let its automatic task selection pick the
8928 tasks to install, and continue to install the requested tasks without
8929 any output what so ever.
8930
8931 Recently I revisited this problem while working on the automatic
8932 package upgrade testing, because tasksel would some times hang without
8933 any useful feedback, and I want to see what is going on when it
8934 happen. Then it occured to me, I can parse the output from tasksel
8935 when asked to run in test mode, and use that aptitude command line
8936 printed by tasksel then to simulate the tasksel run. I ended up using
8937 code like this:
8938
8939 &lt;blockquote&gt;&lt;pre&gt;
8940 export DEBIAN_FRONTEND=noninteractive
8941 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
8942 $cmd
8943 &lt;/pre&gt;&lt;/blockquote&gt;
8944
8945 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
8946 --without-recommends -o APT::Install-Recommends=no -y install
8947 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8948 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
8949 laptop task and all packages with priority standard , required and
8950 important, just like tasksel would have done it during
8951 installation.&lt;/p&gt;
8952
8953 &lt;p&gt;A better approach is probably to extend tasksel to be able to
8954 install packages without using debconf-apt-progress, for use cases
8955 like this.&lt;/p&gt;
8956 </description>
8957 </item>
8958
8959 <item>
8960 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
8961 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
8962 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
8963 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
8964 <description>&lt;p&gt;My
8965 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
8966 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
8967 finally made the upgrade logs available from
8968 &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;.
8969 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8970 apt and aptitude, and found their differences interesting. This time
8971 I will only focus on their removal plans.&lt;/p&gt;
8972
8973 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
8974 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
8975 surprising part is that it want to remove xorg and all
8976 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8977 sure why. When asking aptitude to do the same, it want to remove 129
8978 packages, but most of them are library packages I suspect are no
8979 longer needed. Both of them want to remove bluetooth packages, which
8980 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
8981
8982 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
8983 which seem like a bad idea and xorg the same way as with Gnome. Asking
8984 aptitude for the same, it wants to remove 192 packages, none which are
8985 too surprising.&lt;/p&gt;
8986
8987 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
8988 and avoided, and perhaps others as well. Here are the complete list
8989 of planned removals. The complete logs is available from the URL
8990 above. Note if you want to repeat these tests, that the upgrade test
8991 for kde+apt-get hung in the tasksel setup because of dpkg asking
8992 conffile questions. No idea why. I worked around it by using
8993 &#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
8994 continue.&lt;/p&gt;
8995
8996 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
8997 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
8998 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8999 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9000 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9001 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9002 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9003 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9004 xserver-xorg-input-kbd xserver-xorg-input-mouse
9005 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9006 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9007 xserver-xorg-video-ati xserver-xorg-video-chips
9008 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9009 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9010 xserver-xorg-video-glint xserver-xorg-video-i128
9011 xserver-xorg-video-i740 xserver-xorg-video-imstt
9012 xserver-xorg-video-intel xserver-xorg-video-mach64
9013 xserver-xorg-video-mga xserver-xorg-video-neomagic
9014 xserver-xorg-video-nsc xserver-xorg-video-nv
9015 xserver-xorg-video-openchrome xserver-xorg-video-r128
9016 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9017 xserver-xorg-video-rendition xserver-xorg-video-s3
9018 xserver-xorg-video-s3virge xserver-xorg-video-savage
9019 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9020 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9021 xserver-xorg-video-tga xserver-xorg-video-trident
9022 xserver-xorg-video-tseng xserver-xorg-video-v4l
9023 xserver-xorg-video-vesa xserver-xorg-video-vga
9024 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9025 xulrunner-1.9-gnome-support&lt;/p&gt;
9026
9027 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9028
9029 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9030 djvulibre-desktop finger gnome-app-install gnome-mount
9031 gnome-network-admin gnome-spell gnome-vfs-obexftp
9032 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9033 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9034 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9035 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9036 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9037 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9038 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9039 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9040 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9041 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9042 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9043 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9044 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9045 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9046 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9047 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9048 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9049 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9050 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9051 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9052 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9053 openoffice.org-writer2latex openssl-blacklist p7zip
9054 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9055 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9056 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9057 swfdec-mozilla totem-gstreamer update-manager wodim
9058 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9059 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9060 zip&lt;/p&gt;
9061
9062 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9063
9064 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9065 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9066 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9067 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9068 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9069 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9070 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9071 xserver-xorg-input-kbd xserver-xorg-input-mouse
9072 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9073 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9074 xserver-xorg-video-ati xserver-xorg-video-chips
9075 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9076 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9077 xserver-xorg-video-glint xserver-xorg-video-i128
9078 xserver-xorg-video-i740 xserver-xorg-video-imstt
9079 xserver-xorg-video-intel xserver-xorg-video-mach64
9080 xserver-xorg-video-mga xserver-xorg-video-neomagic
9081 xserver-xorg-video-nsc xserver-xorg-video-nv
9082 xserver-xorg-video-openchrome xserver-xorg-video-r128
9083 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9084 xserver-xorg-video-rendition xserver-xorg-video-s3
9085 xserver-xorg-video-s3virge xserver-xorg-video-savage
9086 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9087 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9088 xserver-xorg-video-tga xserver-xorg-video-trident
9089 xserver-xorg-video-tseng xserver-xorg-video-v4l
9090 xserver-xorg-video-vesa xserver-xorg-video-vga
9091 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9092
9093 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9094 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9095 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9096 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9097 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9098 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9099 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9100 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9101 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9102 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9103 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9104 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9105 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9106 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9107 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9108 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9109 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9110 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9111 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9112 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
9113 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9114 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9115 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
9116 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9117 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9118 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9119 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9120 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9121 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
9122 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
9123 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9124 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9125 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9126 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9127 texlive-common texlive-doc-base texlive-fonts-recommended
9128 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9129 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9130 xulrunner-1.9&lt;/p&gt;
9131
9132 </description>
9133 </item>
9134
9135 <item>
9136 <title>Automatic upgrade testing from Lenny to Squeeze</title>
9137 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
9138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
9139 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
9140 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
9141 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9142 have been discovered and reported in the process
9143 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
9144 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
9145 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
9146 kdebase-workspace-data), and to get a more regular testing going on, I
9147 am working on a script to automate the test.&lt;/p&gt;
9148
9149 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
9150 Gnome or KDE desktop installation inside the chroot before upgrading
9151 it. To ensure no services are started in the chroot, a policy-rc.d
9152 script is inserted. To make sure tasksel believe it is to install a
9153 desktop on a laptop, the tasksel tests are replaced in the chroot
9154 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
9155
9156 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9157 currently always fail because udev refuses to upgrade with the kernel
9158 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9159 is created. The bug report
9160 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
9161 this problem do not trigger in a chroot, but I touch the file anyway
9162 to make sure the upgrade go well. Testing on virtual and real
9163 hardware have failed me because of udev so far, and creating this file
9164 do the trick in such settings anyway. This is a
9165 &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
9166 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
9167 maintainer because he lack the resources to rewrite udev to keep
9168 working with old kernels or something like that. I really wish the
9169 udev upstream would keep udev backwards compatible, to avoid such
9170 upgrade problem, but given that they fail to do so, I guess
9171 documenting the way out of this mess is the best option we got for
9172 Debian Squeeze.&lt;/p&gt;
9173
9174 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
9175 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
9176 trick:&lt;/p&gt;
9177
9178 &lt;blockquote&gt;&lt;pre&gt;
9179 #!/bin/sh
9180 set -ex
9181
9182 if [ &quot;$1&quot; ] ; then
9183 desktop=$1
9184 else
9185 desktop=gnome
9186 fi
9187
9188 from=lenny
9189 to=squeeze
9190
9191 exec &amp;lt; /dev/null
9192 unset LANG
9193 mirror=http://ftp.skolelinux.org/debian
9194 tmpdir=chroot-$from-upgrade-$to-$desktop
9195 fuser -mv .
9196 debootstrap $from $tmpdir $mirror
9197 chroot $tmpdir aptitude update
9198 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
9199 #!/bin/sh
9200 exit 101
9201 EOF
9202 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9203 exit_cleanup() {
9204 umount $tmpdir/proc
9205 }
9206 mount -t proc proc $tmpdir/proc
9207 # Make sure proc is unmounted also on failure
9208 trap exit_cleanup EXIT INT
9209
9210 chroot $tmpdir aptitude -y install debconf-utils
9211
9212 # Make sure tasksel autoselection trigger. It need the test scripts
9213 # to return the correct answers.
9214 echo tasksel tasksel/desktop multiselect $desktop | \
9215 chroot $tmpdir debconf-set-selections
9216
9217 # Include the desktop and laptop task
9218 for test in desktop laptop ; do
9219 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
9220 #!/bin/sh
9221 exit 2
9222 EOF
9223 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9224 done
9225
9226 DEBIAN_FRONTEND=noninteractive
9227 DEBIAN_PRIORITY=critical
9228 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9229 chroot $tmpdir tasksel --new-install
9230
9231 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
9232 chroot $tmpdir aptitude update
9233 touch $tmpdir/etc/udev/kernel-upgrade
9234 chroot $tmpdir aptitude -y dist-upgrade
9235 fuser -mv
9236 &lt;/pre&gt;&lt;/blockquote&gt;
9237
9238 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
9239 with aptitude, but I have not had time to look at how they behave
9240 differently so far. I hope to get a cron job running to do the test
9241 regularly and post the result on the web. The Gnome upgrade currently
9242 work, while the KDE upgrade fail because of the bug in
9243 kdebase-workspace-data&lt;/p&gt;
9244
9245 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
9246 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
9247 post, so I will refrain from trying. I can report that for Gnome,
9248 aptitude report 760 packages upgraded, 448 newly installed, 129 to
9249 remove and 1 not upgraded and 1024MB need to be downloaded while for
9250 KDE the same numbers are 702 packages upgraded, 507 newly installed,
9251 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
9252
9253 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
9254 is able to migrate to dependency based boot sequencing and parallel
9255 booting without a hitch. Was unsure if there were still bugs with
9256 packages failing to clean up their obsolete init.d script during
9257 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9258 packages.&lt;/p&gt;
9259 </description>
9260 </item>
9261
9262 <item>
9263 <title>Upstart or sysvinit - as init.d scripts see it</title>
9264 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
9265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
9266 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
9267 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
9268 scripts to migrate (some of) their operations to upstart job while
9269 keeping the init.d for hurd and kfreebsd. The packages with such
9270 needs will need a way to get their init.d scripts to behave
9271 differently when used with sysvinit and with upstart. Because of
9272 this, I had a look at the environment variables set when a init.d
9273 script is running under upstart, and when it is not.&lt;/p&gt;
9274
9275 &lt;p&gt;With upstart, I notice these environment variables are set when a
9276 script is started from rcS.d/ (ignoring some irrelevant ones like
9277 COLUMNS):&lt;/p&gt;
9278
9279 &lt;blockquote&gt;&lt;pre&gt;
9280 DEFAULT_RUNLEVEL=2
9281 previous=N
9282 PREVLEVEL=
9283 RUNLEVEL=
9284 runlevel=S
9285 UPSTART_EVENTS=startup
9286 UPSTART_INSTANCE=
9287 UPSTART_JOB=rc-sysinit
9288 &lt;/pre&gt;&lt;/blockquote&gt;
9289
9290 &lt;p&gt;With sysvinit, these environment variables are set for the same
9291 script.&lt;/p&gt;
9292
9293 &lt;blockquote&gt;&lt;pre&gt;
9294 INIT_VERSION=sysvinit-2.88
9295 previous=N
9296 PREVLEVEL=N
9297 RUNLEVEL=S
9298 runlevel=S
9299 &lt;/pre&gt;&lt;/blockquote&gt;
9300
9301 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
9302 sysvinit are not set by upstart. Not sure if it is intentional or not
9303 to not be compatible with sysvinit in this regard.&lt;/p&gt;
9304
9305 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9306 looking for the UPSTART_JOB environment variable seem to be a good
9307 choice.&lt;/p&gt;
9308 </description>
9309 </item>
9310
9311 <item>
9312 <title>A manual for standards wars...</title>
9313 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9315 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9316 <description>&lt;p&gt;Via the
9317 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9318 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9319 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9320 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9321 following the standards wars of today.&lt;/p&gt;
9322 </description>
9323 </item>
9324
9325 <item>
9326 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9327 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9329 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9330 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9331 to get a list of the machine types in use thanks to the DMI
9332 information extracted from each machine. The script to do so is
9333 included in the sitesummary package, and here is example output from
9334 the Skolelinux build servers:&lt;/p&gt;
9335
9336 &lt;blockquote&gt;&lt;pre&gt;
9337 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9338 vendor count
9339 Dell Computer Corporation 1
9340 PowerEdge 1750 1
9341 IBM 1
9342 eserver xSeries 345 -[8670M1X]- 1
9343 Intel 2
9344 [no-dmi-info] 3
9345 maintainer:~#
9346 &lt;/pre&gt;&lt;/blockquote&gt;
9347
9348 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9349 provided in each machine. Here there are Intel machines without model
9350 information listed with Intel as vendor and no model, and virtual Xen
9351 machines listed as [no-dmi-info]. One can add -l as a command line
9352 option to list the individual machines.&lt;/p&gt;
9353
9354 &lt;p&gt;A larger list is
9355 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9356 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9357 provide the basic sitesummary report publicly. In their report there
9358 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9359 their machines, and as sitesummary is available in both distributions,
9360 it is trivial to get all of them to report to the same central
9361 collector.&lt;/p&gt;
9362 </description>
9363 </item>
9364
9365 <item>
9366 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9367 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9368 <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>
9369 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9370 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9371 start at boot when an NVidia video card is used is handled. The
9372 problem seem to be that the nvidia X.org driver uses a long time to
9373 initialize, and this duration is longer than kdm is configured to
9374 wait.&lt;/p&gt;
9375
9376 &lt;p&gt;I came across two bugs related to this issue,
9377 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9378 against initscripts and passed on to nvidia-glx when it became obvious
9379 that the nvidia drivers were involved, and
9380 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9381 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9382
9383 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9384 problem nvidia video card owners experience and make sure the Debian
9385 distribution work out of the box for these users. The nvidia driver
9386 maintainers expect kdm to be set up to wait longer, while kdm expect
9387 the nvidia driver maintainers to fix the driver to start faster, and
9388 while they wait for each other I guess the users end up switching to a
9389 distribution that work for them. I have no idea what the solution is,
9390 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9391
9392 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9393 </description>
9394 </item>
9395
9396 <item>
9397 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9398 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9399 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9400 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9401 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9402 The feature seem to hold up pretty well, but three fairly serious
9403 issues are known and should be solved:
9404
9405 &lt;p&gt;&lt;ul&gt;
9406
9407 &lt;li&gt;The wicd package seen to
9408 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9409 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9410 parallel booting is enabled. No idea why, but the wicd maintainer
9411 seem to be on the case.&lt;/li&gt;
9412
9413 &lt;li&gt;The nvidia X driver seem to
9414 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9415 triggered more easily when parallel booting is in effect. The
9416 maintainer is on the case.&lt;/li&gt;
9417
9418 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9419 sequencing (the shutdown is broken) when old file-rc users
9420 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9421 sysv-rc. One way to solve it would be for file-rc to create
9422 /etc/init.d/.legacy-bootordering, and another is to try to make
9423 sysv-rc more robust. Will investigate some more and probably upload a
9424 workaround in sysv-rc to help those trying to move from file-rc to
9425 sysv-rc get a working shutdown.&lt;/li&gt;
9426
9427 &lt;/ul&gt;&lt;/p&gt;
9428
9429 &lt;p&gt;All in all not many surprising issues, and all of them seem
9430 solvable before Squeeze is released. In addition to these there are
9431 some packages with bugs in their dependencies and run level settings,
9432 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9433
9434 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9435 the BTS, please usertag the report to get it to show up at
9436 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9437 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9438
9439 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9440 </description>
9441 </item>
9442
9443 <item>
9444 <title>More flexible firmware handling in debian-installer</title>
9445 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9446 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9447 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9448 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9449 found time today to return to the project. Having to spend less time
9450 working dependency based boot in debian, as it is almost complete now,
9451 definitely helped freeing some time.&lt;/p&gt;
9452
9453 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9454 include some firmware packages on the Debian Edu CDs, those needed to
9455 get disk and network controllers working. Without having these
9456 firmware packages available during installation, it is impossible to
9457 install Debian Edu on the given machine, and because our target group
9458 are non-technical people, asking them to provide firmware packages on
9459 an external medium is a support pain. Initially, I expected it to be
9460 enough to include the firmware packages on the CD to get
9461 debian-installer to find and use them. This proved to be wrong.
9462 Next, I hoped it was enough to symlink the relevant firmware packages
9463 to some useful location on the CD (tried /cdrom/ and
9464 /cdrom/firmware/). This also proved to not work, and at this point I
9465 found time to look at the debian-installer code to figure out what was
9466 going to work.&lt;/p&gt;
9467
9468 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9469 look revealed that it would only look for firmware packages outside
9470 the installation media, so the CD was never checked for firmware
9471 packages. It would only check USB sticks, floppies and other
9472 &quot;external&quot; media devices. Today I changed it to also look in the
9473 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9474 solve the problem I ran into with Debian edu. I also changed it to
9475 look in /firmware/, to make sure the installer also find firmware
9476 provided in the initrd when booting the installer via PXE, to allow us
9477 to provide the same feature in the PXE setup included in Debian
9478 Edu.&lt;/p&gt;
9479
9480 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9481 activated without asking if the license is accepted, I extended
9482 hw-detect to look for preinst scripts in the firmware packages, and
9483 run these before activating the firmware during installation. The
9484 license question is asked using debconf in the preinst, so this should
9485 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9486
9487 &lt;p&gt;If you want to discuss the details of these features, please
9488 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9489 </description>
9490 </item>
9491
9492 <item>
9493 <title>Parallellized boot is now the default in Debian/unstable</title>
9494 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9495 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9496 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9497 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9498 Debian/unstable for machines using dependency based boot sequencing.
9499 Apparently the testing of concurrent booting has been wider than
9500 expected, if I am to believe the
9501 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9502 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9503 with the feature this weekend, to give us some time to detect any
9504 remaining problems before Squeeze is frozen. If serious problems are
9505 detected, it is simple to change the default back to sequential boot.
9506 The upload of the new sysvinit package also activate a new upstream
9507 version.&lt;/p&gt;
9508
9509 More information about
9510 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9511 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9512 currently possible to disable parallel booting when one run into
9513 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9514
9515 &lt;blockquote&gt;&lt;pre&gt;
9516 CONCURRENCY=none
9517 &lt;/pre&gt;&lt;/blockquote&gt;
9518
9519 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9520 the BTS, please usertag the report to get it to show up at
9521 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9522 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9523 </description>
9524 </item>
9525
9526 <item>
9527 <title>Sitesummary tip: Listing MAC address of all clients</title>
9528 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9530 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9531 <description>&lt;p&gt;In the recent Debian Edu versions, the
9532 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9533 system&lt;/a&gt; is used to keep track of the machines in the school
9534 network. Each machine will automatically report its status to the
9535 central server after boot and once per night. The network setup is
9536 also reported, and using this information it is possible to get the
9537 MAC address of all network interfaces in the machines. This is useful
9538 to update the DHCP configuration.&lt;/p&gt;
9539
9540 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
9541 ist all MAC addresses of all machines reporting to sitesummary. Run
9542 this on the collector host:&lt;/p&gt;
9543
9544 &lt;blockquote&gt;&lt;pre&gt;
9545 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
9546 &lt;/pre&gt;&lt;/blockquote&gt;
9547
9548 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
9549 line per machine and with space between the MAC addresses.&lt;/p&gt;
9550
9551 &lt;p&gt;To allow system administrators easier job at adding static DHCP
9552 addresses for hosts, it would be possible to extend this to fetch
9553 machine information from sitesummary and update the DHCP and DNS
9554 tables in LDAP using this information. Such tool is unfortunately not
9555 written yet.&lt;/p&gt;
9556 </description>
9557 </item>
9558
9559 <item>
9560 <title>systemd, an interesting alternative to upstart</title>
9561 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
9562 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
9563 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
9564 <description>&lt;p&gt;The last few days a new boot system called
9565 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
9566 has been
9567 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
9568
9569 to the free software world. I have not yet had time to play around
9570 with it, but it seem to be a very interesting alternative to
9571 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
9572 a good alternative for Debian when we are able to switch to an event
9573 based boot system. Tollef is
9574 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
9575 systemd into Debian, and I look forward to seeing how well it work. I
9576 like the fact that systemd handles init.d scripts with dependency
9577 information natively, allowing them to run in parallel where upstart
9578 at the moment do not.&lt;/p&gt;
9579
9580 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
9581 platform support. It only work on recent Linux kernels, and also need
9582 some new kernel features enabled to function properly. This means
9583 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9584 system. Not sure how that will be handled if systemd proves to be the
9585 way forward.&lt;/p&gt;
9586
9587 &lt;p&gt;In the mean time, based on the
9588 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9589 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
9590 decided to enable full parallel booting as the default in Debian as
9591 soon as possible (probably this weekend or early next week), to see if
9592 there are any remaining serious bugs in the init.d dependencies. A
9593 new version of the sysvinit package implementing this change is
9594 already in experimental. If all go well, Squeeze will be released
9595 with parallel booting enabled by default.&lt;/p&gt;
9596 </description>
9597 </item>
9598
9599 <item>
9600 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
9601 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
9602 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
9603 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
9604 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
9605 complete, so complete that it is actually possible to run all the
9606 init.d scripts in parallell based on these dependencies. If you want
9607 to test your Squeeze system, make sure
9608 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9609 based boot sequencing&lt;/a&gt; is enabled, and add this line to
9610 /etc/default/rcS:&lt;/p&gt;
9611
9612 &lt;blockquote&gt;&lt;pre&gt;
9613 CONCURRENCY=makefile
9614 &lt;/pre&gt;&lt;/blockquote&gt;
9615
9616 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
9617 scripts in parallel using the dependency information stored in
9618 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9619 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9620 to try to start the kdm and gdm scripts as early as possible, and will
9621 start the facilities required by kdm or gdm as early as possible to
9622 make this happen.&lt;/p&gt;
9623
9624 &lt;p&gt;Give it a try, and see if you like the result. If some services
9625 fail to start properly, it is most likely because they have incomplete
9626 init.d script dependencies in their startup script (or some of their
9627 dependent scripts have incomplete dependencies). Report bugs and get
9628 the package maintainers to fix it. :)&lt;/p&gt;
9629
9630 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
9631 manage to get the init.d script dependencies complete and correct. I
9632 expect we will get there in Squeeze+1, if we get manage to test and
9633 fix the remaining issues.&lt;/p&gt;
9634
9635 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9636 the BTS, please usertag the report to get it to show up at
9637 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9638 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9639 </description>
9640 </item>
9641
9642 <item>
9643 <title>Debian has switched to dependency based boot sequencing</title>
9644 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
9645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
9646 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
9647 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
9648 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
9649 have been migrated to using dependency based boot sequencing. This
9650 conclude work me and others have been doing for the last three days.
9651 It feels great to see this finally part of the default Debian
9652 installation. Now we just need to weed out the last few problems that
9653 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
9654
9655 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
9656 fixing the more fundamental problem of handing the event based
9657 non-predictable kernel in the early boot.&lt;/p&gt;
9658 </description>
9659 </item>
9660
9661 <item>
9662 <title>Taking over sysvinit development</title>
9663 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
9664 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
9665 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
9666 <description>&lt;p&gt;After several years of frustration with the lack of activity from
9667 the existing sysvinit upstream developer, I decided a few weeks ago to
9668 take over the package and become the new upstream. The number of
9669 patches to track for the Debian package was becoming a burden, and the
9670 lack of synchronization between the distribution made it hard to keep
9671 the package up to date.&lt;/p&gt;
9672
9673 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9674 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
9675 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
9676 and Fedora), based on the patches currently in use in these
9677 distributions. We Debian maintainers plan to move to this tarball as
9678 the new upstream as soon as we find time to do the merge. Since the
9679 new tarball was created, we agreed with Werner at SuSe to make a new
9680 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
9681 development there. The project is registered and currently waiting
9682 for approval by the Savannah administrators, and as soon as it is
9683 approved, we will import the old versions from svn and continue
9684 working on the future release.&lt;/p&gt;
9685
9686 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
9687 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
9688 </description>
9689 </item>
9690
9691 <item>
9692 <title>Debian boots quicker and quicker</title>
9693 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
9694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
9695 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
9696 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
9697 people involved in the boot system on Debian and Ubuntu, to see if we
9698 could find more ways to speed up the boot system. This was an Ubuntu
9699 funded
9700 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
9701 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
9702 of boot systems, and ways to handle the increasing number of boot
9703 issues introduced by the Linux kernel becoming more and more
9704 asynchronous and event base. The Ubuntu approach using udev and
9705 upstart might be a good way forward. Time will show.&lt;/p&gt;
9706
9707 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
9708 process in Debian. All of these should be applied to get a quick
9709 boot:&lt;/p&gt;
9710
9711 &lt;ul&gt;
9712
9713 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
9714
9715 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
9716 clock is in UTC.&lt;/li&gt;
9717
9718 &lt;li&gt;Install and activate the insserv package to enable
9719 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9720 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
9721
9722 &lt;/ul&gt;
9723
9724 These points are based on the Google summer of code work done by
9725 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
9726 Villegas&lt;/a&gt;.
9727
9728 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
9729 unstable yesterday. When we tested it, we were able to cut 6 seconds
9730 from the boot sequence. It depend on very correct dependency
9731 declaration in all init.d scripts, so I expect us to find edge cases
9732 where the dependences in some scripts are slightly wrong when we start
9733 using this.&lt;/p&gt;
9734
9735 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9736 introduced by Raphael Geissert today, one that could affect the
9737 startup speed as well. Instead of starting some scripts concurrently
9738 from rcS.d/ and another set of scripts from rc2.d/, it would be
9739 possible to run a of them in the same process. A quick way to test
9740 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
9741 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
9742 </description>
9743 </item>
9744
9745 <item>
9746 <title>BSAs påstander om piratkopiering møter motstand</title>
9747 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
9748 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
9749 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
9750 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
9751 programvareselskapene som Microsoft og Apple, publisert en rapport der
9752 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9753 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9754 dager siden kom
9755 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
9756 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
9757 dagene. Et spesielt interessant kommentar fra Sverige,
9758 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
9759 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
9760
9761 &lt;blockquote&gt;
9762 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
9763 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9764 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
9765 exakta&quot;, säger BSAs Sverigechef John Hugosson.
9766 &lt;/blockquote&gt;
9767
9768 &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
9769 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
9770 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
9771 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
9772 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
9773
9774 &lt;p&gt;Fant lenkene via &lt;a
9775 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
9776 på Slashdot&lt;/a&gt;.&lt;/p&gt;
9777 </description>
9778 </item>
9779
9780 <item>
9781 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
9782 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
9783 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
9784 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
9785 <description>&lt;p&gt;Kom over
9786 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
9787 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9788 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9789 jobber til daglig. En rask opptelling forteller meg at vi har 490
9790 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
9791 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
9792 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
9793 </description>
9794 </item>
9795
9796 <item>
9797 <title>Kryptert harddisk - naturligvis</title>
9798 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
9799 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
9800 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
9801 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
9802 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
9803 når en tar tap av arbeidstid, fortrolige dokumenter,
9804 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9805 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9806 til at jeg har kryptert harddisken på både kontormaskinen og min
9807 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9808 komme på avveie, den første informasjon relatert til jobben min ved
9809 Universitetet i Oslo, og den andre relatert til blant annet
9810 foreningsarbeide. Kryptering av diskene gjør at det er lite
9811 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9812 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9813 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9814 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9815 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9816 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9817 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9818 det er gjort slik jeg gjør det er minimale, og gevinstene er
9819 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9820 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
9821
9822 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9823 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9824 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9825 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9826 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9827 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9828 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9829 betydelige.&lt;/p&gt;
9830 </description>
9831 </item>
9832
9833 <item>
9834 <title>Two projects that have improved the quality of free software a lot</title>
9835 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
9836 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
9837 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
9838 <description>&lt;p&gt;There are two software projects that have had huge influence on the
9839 quality of free software, and I wanted to mention both in case someone
9840 do not yet know them.&lt;/p&gt;
9841
9842 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
9843 tool to detect and expose errors in the memory handling of programs.
9844 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
9845 and it will report any problems on stdout. It is even better if the
9846 program include debug information. With debug information, it is able
9847 to report the source file name and line number where the problem
9848 occurs. It can report things like &#39;reading past memory block in file
9849 X line N, the memory block was allocated in file Y, line M&#39;, and
9850 &#39;using uninitialised value in control logic&#39;. This tool has made it
9851 trivial to investigate reproducible crash bugs in programs, and have
9852 reduced the number of this kind of bugs in free software a lot.
9853
9854 &lt;p&gt;The second one is
9855 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
9856 a source code checker. It is able to process the source of a program
9857 and find problems in the logic without running the program. It
9858 started out as the Stanford Checker and became well known when it was
9859 used to find bugs in the Linux kernel. It is now a commercial tool
9860 and the company behind it is running
9861 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
9862 free software community, where a lot of free software projects get
9863 their source checked for free. Several thousand defects have been
9864 found and fixed so far. It can find errors like &#39;lock L taken in file
9865 X line N is never released if exiting in line M&#39;, or &#39;the code in file
9866 Y lines O to P can never be executed&#39;. The projects included in the
9867 community service project have managed to get rid of a lot of
9868 reliability problems thanks to Coverity.&lt;/p&gt;
9869
9870 &lt;p&gt;I believe tools like this, that are able to automatically find
9871 errors in the source, are vital to improve the quality of software and
9872 make sure we can get rid of the crashing and failing software we are
9873 surrounded by today.&lt;/p&gt;
9874 </description>
9875 </item>
9876
9877 <item>
9878 <title>No patch is not better than a useless patch</title>
9879 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
9880 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
9881 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
9882 <description>&lt;p&gt;Julien Blache
9883 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
9884 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
9885 patch allow one to discuss a concrete and proposed solution, and also
9886 prove that the issue at hand is important enough for someone to spent
9887 time on fixing it. No patch do not provide any of these positive
9888 properties.&lt;/p&gt;
9889 </description>
9890 </item>
9891
9892 <item>
9893 <title>Standardize on protocols and formats, not vendors and applications</title>
9894 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
9895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
9896 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
9897 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
9898 very good one to form a long lived computer infrastructure. It is the
9899 simple one, lost by many in todays computer industry: Standardize on
9900 open network protocols and open exchange/storage formats, not applications.
9901 Applications come and go, while protocols and files tend to stay, and
9902 thus one want to make it easy to change application and vendor, while
9903 avoiding conversion costs and locking users to a specific platform or
9904 application.&lt;/p&gt;
9905
9906 &lt;p&gt;This approach make it possible to replace the client applications
9907 independently of the server applications. One can even allow users to
9908 use several different applications as long as they handle the selected
9909 protocol and format. In the normal case, only one client application
9910 is recommended and users only get help if they choose to use this
9911 application, but those that want to deviate from the easy path are not
9912 blocked from doing so.&lt;/p&gt;
9913
9914 &lt;p&gt;It also allow us to replace the server side without forcing the
9915 users to replace their applications, and thus allow us to select the
9916 best server implementation at any moment, when scale and resouce
9917 requirements change.&lt;/p&gt;
9918
9919 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
9920 open formats, but I would never recommend standardizing on a single
9921 application that do not use open network protocol or open formats.&lt;/p&gt;
9922 </description>
9923 </item>
9924
9925 <item>
9926 <title>Returning from Skolelinux developer gathering</title>
9927 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
9928 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
9929 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
9930 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
9931 Edu/Skolelinux development gathering. I got a bit done tuning the
9932 desktop, and looked into the dynamic service location protocol
9933 implementation avahi. It look like it could be useful for us. Almost
9934 30 people participated, and I believe it was a great environment to
9935 get to know the Skolelinux system. Walter Bender, involved in the
9936 development of the Sugar educational platform, presented his stuff and
9937 also helped me improve my OLPC installation. He also showed me that
9938 his Turtle Art application can be used in standalone mode, and we
9939 agreed that I would help getting it packaged for Debian. As a
9940 standalone application it would be great for Debian Edu. We also
9941 tried to get the video conferencing working with two OLPCs, but that
9942 proved to be too hard for us. The application seem to need more work
9943 before it is ready for me. I look forward to getting home and relax
9944 now. :)&lt;/p&gt;
9945 </description>
9946 </item>
9947
9948 <item>
9949 <title>Time for new LDAP schemas replacing RFC 2307?</title>
9950 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
9951 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
9952 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
9953 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
9954 optimal. There is RFC 2307 documenting one way to store NIS maps in
9955 LDAP, and a modified version of this normally called RFC 2307bis, with
9956 some modifications to be compatible with Active Directory. The RFC
9957 specification handle the content of a lot of system databases, but do
9958 not handle DNS zones and DHCP configuration.&lt;/p&gt;
9959
9960 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
9961 we would like to store information about users, SMB clients/hosts,
9962 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9963 and LTSP configuration in LDAP. These objects have a lot in common,
9964 but with the current LDAP schemas it is not possible to have one
9965 object per entity. For example, one need to have at least three LDAP
9966 objects for a given computer, one with the SMB related stuff, one with
9967 DNS information and another with DHCP information. The schemas
9968 provided for DNS and DHCP are impossible to combine into one LDAP
9969 object. In addition, it is impossible to implement quick queries for
9970 netgroup membership, because of the way NIS triples are implemented.
9971 It just do not scale. I believe it is time for a few RFC
9972 specifications to cleam up this mess.&lt;/p&gt;
9973
9974 &lt;p&gt;I would like to have one LDAP object representing each computer in
9975 the network, and this object can then keep the SMB (ie host key), DHCP
9976 (mac address/name) and DNS (name/IP address) settings in one place.
9977 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
9978
9979 &lt;p&gt;I would also like to have a quick way to map from a user or
9980 computer and to the net group this user or computer is a member.&lt;/p&gt;
9981
9982 &lt;p&gt;Active Directory have done a better job than unix heads like myself
9983 in this regard, and the unix side need to catch up. Time to start a
9984 new IETF work group?&lt;/p&gt;
9985 </description>
9986 </item>
9987
9988 <item>
9989 <title>Endelig er Debian Lenny gitt ut</title>
9990 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
9991 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
9992 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
9993 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
9994 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
9995 Et langt steg videre for Debian-prosjektet, og en rekke nye
9996 programpakker blir nå tilgjengelig for de av oss som bruker den
9997 stabile utgaven av Debian. Neste steg er nå å få
9998 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
9999 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10000 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10001 slippes løs på skolene. Takk til alle debian-utviklerne som har
10002 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10003 bootsekvens tilgjengelig i stabil utgave, vha pakken
10004 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10005 </description>
10006 </item>
10007
10008 <item>
10009 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10010 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10011 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10012 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10013 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10014 Oslo. Most of Saturday was used for the general assemly for the
10015 member organization, but the rest of the weekend I used to tune the
10016 LTSP installation. LTSP now work out of the box on the 10-network.
10017 Acer Aspire One proved to be a very nice thin client, with both
10018 screen, mouse and keybard in a small box. Was working on getting the
10019 diskless workstation setup configured out of the box, but did not
10020 finish it before the weekend was up.&lt;/p&gt;
10021
10022 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10023 the Brazilian group, so that will have to wait for the next
10024 development gathering. Would love to have the Debian Edu installer
10025 automatically detect and configure a multiseat setup when it find one
10026 of these cards.&lt;/p&gt;
10027 </description>
10028 </item>
10029
10030 <item>
10031 <title>The sorry state of multimedia browser plugins in Debian</title>
10032 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10034 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10035 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10036 plugins available in Debian Lenny, to see which one we should use by
10037 default in Debian Edu. We need an embedded video playing plugin with
10038 control buttons to pause or stop the video, and capable of streaming
10039 all the multimedia content available on the web. The test results and
10040 notes are available on
10041 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10042 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10043 fill this need. My personal video player favorite, VLC, has a really
10044 bad plugin which fail on a lot of the test pages. A lot of the MIME
10045 types I would expect to work with any free software player (like
10046 video/ogg), just do not work. And simple formats like the
10047 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10048 totem and vlc plugins. I hope the situation will improve soon. No
10049 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10050
10051 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10052 be the only one fitting our needs. :/&lt;/p&gt;
10053 </description>
10054 </item>
10055
10056 </channel>
10057 </rss>