]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
ad219a855e9e449a24a06c2afa43107f2f0819ec
[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>Appstream just learned how to map hardware to packages too!</title>
11 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
13 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
14 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
15 readers probably know, I have been working on the
16 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
17 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
18 it easier for users to figure out what to install to get a given piece
19 of hardware to work in Debian, and a key part of this system is a way
20 to map hardware to packages. Isenkram have its own mapping database,
21 and also uses data provided by each package using the AppStream
22 metadata format. And today,
23 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
24 Debian learned to look up hardware the same way Isenkram is doing it,
25 ie using fnmatch():&lt;/p&gt;
26
27 &lt;p&gt;&lt;pre&gt;
28 % appstreamcli what-provides modalias \
29 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
30 Identifier: pymissile [generic]
31 Name: pymissile
32 Summary: Control original Striker USB Missile Launcher
33 Package: pymissile
34 % appstreamcli what-provides modalias usb:v0694p0002d0000
35 Identifier: libnxt [generic]
36 Name: libnxt
37 Summary: utility library for talking to the LEGO Mindstorms NXT brick
38 Package: libnxt
39 ---
40 Identifier: t2n [generic]
41 Name: t2n
42 Summary: Simple command-line tool for Lego NXT
43 Package: t2n
44 ---
45 Identifier: python-nxt [generic]
46 Name: python-nxt
47 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
48 Package: python-nxt
49 ---
50 Identifier: nbc [generic]
51 Name: nbc
52 Summary: C compiler for LEGO Mindstorms NXT bricks
53 Package: nbc
54 %
55 &lt;/pre&gt;&lt;/p&gt;
56
57 &lt;p&gt;A similar query can be done using the combined AppStream and
58 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
59
60 &lt;p&gt;&lt;pre&gt;
61 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
62 pymissile
63 % isenkram-lookup usb:v0694p0002d0000
64 libnxt
65 nbc
66 python-nxt
67 t2n
68 %
69 &lt;/pre&gt;&lt;/p&gt;
70
71 &lt;p&gt;If you want to make this system a success and help Debian users
72 make the most of the hardware they have, please
73 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
74 AppStream metadata for your package following the guidelines&lt;/a&gt;
75 documented in the wiki. So far only 11 packages provide such
76 information, among the several hundred hardware specific packages in
77 Debian. The Isenkram database on the other hand contain 101 packages,
78 mostly related to USB dongles. Most of the packages with hardware
79 mapping in AppStream are LEGO Mindstorms related, because I have, as
80 part of my involvement in
81 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
82 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
83 complete set of packages in Debian for that particular hardware. The
84 team also got a nice Christmas present today. The
85 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
86 package&lt;/a&gt; made it into Debian. With this package in place, it is
87 not possible to use the LEGO Mindstorms NXT unit with only free
88 software, as the nxt-firmware package contain the source and firmware
89 binaries for the NXT brick.&lt;/p&gt;
90
91 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
92 activities, please send Bitcoin donations to my address
93 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
94 </description>
95 </item>
96
97 <item>
98 <title>Isenkram updated with a lot more hardware-package mappings</title>
99 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
101 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
102 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
103 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
104 and install packages to get your hardware dongles to work, is still
105 going strong. It is a system to look up the hardware present on or
106 connected to the current system, and map the hardware to Debian
107 packages. It can either be done using the tools in isenkram-cli or
108 using the user space daemon in the isenkram package. The latter will
109 notify you, when inserting new hardware, about what packages to
110 install to get the dongle working. It will even provide a button to
111 click on to ask packagekit to install the packages.&lt;/p&gt;
112
113 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
114
115 &lt;p&gt;&lt;pre&gt;
116 % isenkram-lookup
117 bluez
118 cheese
119 ethtool
120 fprintd
121 fprintd-demo
122 gkrellm-thinkbat
123 hdapsd
124 libpam-fprintd
125 pidgin-blinklight
126 thinkfan
127 tlp
128 tp-smapi-dkms
129 tp-smapi-source
130 tpb
131 %
132 &lt;/pre&gt;&lt;/p&gt;
133
134 &lt;p&gt;It can also list the firware package providing firmware requested
135 by the load kernel modules, which in my case is an empty list because
136 I have all the firmware my machine need:
137
138 &lt;p&gt;&lt;pre&gt;
139 % /usr/sbin/isenkram-autoinstall-firmware -l
140 info: did not find any firmware files requested by loaded kernel modules. exiting
141 %
142 &lt;/pre&gt;&lt;/p&gt;
143
144 &lt;p&gt;The last few days I had a look at several of the around 250
145 packages in Debian with udev rules. These seem like good candidates
146 to install when a given hardware dongle is inserted, and I found
147 several that should be proposed by isenkram. I have not had time to
148 check all of them, but am happy to report that now there are 97
149 packages packages mapped to hardware by Isenkram. 11 of these
150 packages provide hardware mapping using AppStream, while the rest are
151 listed in the modaliases file provided in isenkram.&lt;/p&gt;
152
153 &lt;p&gt;These are the packages with hardware mappings at the moment. The
154 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
155 support using AppStream, for everyone to use:&lt;/p&gt;
156
157 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
158 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
159 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
160 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
161 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
162 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
163 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
164 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
165 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
166 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
167 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
168 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
169 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
170 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
171 pcscd, pidgin-blinklight, printer-driver-splix,
172 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
173 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
174 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
175 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
176 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
177 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
178 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
179 xserver-xorg-video-vmware, yubikey-personalization and
180 zd1211-firmware&lt;/p&gt;
181
182 &lt;p&gt;If you know of other packages, please let me know with a wishlist
183 bug report against the isenkram-cli package, and ask the package
184 maintainer to
185 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
186 metadata according to the guidelines&lt;/a&gt; to provide the information
187 for everyone. In time, I hope to get rid of the isenkram specific
188 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
189
190 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
191 much hardware, and suggest that the package with with any ethernet
192 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
193 the details. I hope the maintainer find time to address it soon. In
194 the mean time I provide an override in isenkram.&lt;/p&gt;
195 </description>
196 </item>
197
198 <item>
199 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
200 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
201 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
202 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
203 <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;
204
205 &lt;p&gt;In my early years, I played
206 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
207 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
208 space, and reached the &#39;elite&#39; fighting status before I moved on. The
209 original Elite game was available on Commodore 64 and the IBM PC
210 edition I played had a 64 KB executable. I am still impressed today
211 that the authors managed to squeeze both a 3D engine and details about
212 more than 2000 planet systems across 7 galaxies into a binary so
213 small.&lt;/p&gt;
214
215 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
216 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
217 really have time to test it properly until a few days ago. It was
218 great to discover that my old knowledge about trading routes were
219 still valid. But my fighting and flying abilities were gone, so I had
220 to retrain to be able to dock on a space station. And I am still not
221 able to make much resistance when I am attacked by pirates, so I
222 bougth and mounted the most powerful laser in the rear to be able to
223 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
224
225 &lt;p&gt;When playing Elite in the late eighties, I had to discover
226 everything on my own, and I had long lists of prices seen on different
227 planets to be able to decide where to trade what. This time I had the
228 advantages of the
229 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
230 where information about each planet is easily available with common
231 price ranges and suggested trading routes. This improved my ability
232 to earn money and I have been able to earn enough to buy a lot of
233 useful equipent in a few days. I believe I originally played for
234 months before I could get a docking computer, while now I could get it
235 after less then a week.&lt;/p&gt;
236
237 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
238 space, you should try out Oolite. It is available for Linux, MacOSX
239 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
240
241 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
242 activities, please send Bitcoin donations to my address
243 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
244 </description>
245 </item>
246
247 <item>
248 <title>Quicker Debian installations using eatmydata</title>
249 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
250 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
251 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
252 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
253 installation system, observing how using
254 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
255 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
256 speedup around 20-40 percent for Debian Edu, where we install around
257 1000 packages from within the installer. The eatmydata package
258 provide a way to disable/delay file system flushing. This is a bit
259 risky in the general case, as files that should be stored on disk will
260 stay only in memory a bit longer than expected, causing problems if a
261 machine crashes at an inconvenient time. But for an installation, if
262 the machine crashes during installation the process is normally
263 restarted, and avoiding disk operations as much as possible to speed
264 up the process make perfect sense.
265
266 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
267 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
268 but did not have time to push it any further. But a few months ago I
269 picked it up again and worked with the libeatmydata package maintainer
270 Mattia Rizzolo to make it easier for everyone to get this installation
271 speedup in Debian. Thanks to our cooperation There is now an
272 eatmydata-udeb package in Debian testing and unstable, and simply
273 enabling/installing it in debian-installer (d-i) is enough to get the
274 quicker installations. It can be enabled using preseeding. The
275 following untested kernel argument should do the trick:&lt;/p&gt;
276
277 &lt;blockquote&gt;&lt;pre&gt;
278 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
279 &lt;/pre&gt;&lt;/blockquote&gt;
280
281 &lt;p&gt;This should ask d-i to install the package inside the d-i
282 environment early in the installation sequence. Having it installed
283 in d-i in turn will make sure the relevant scripts are called just
284 after debootstrap filled /target/ with the freshly installed Debian
285 system to configure apt to run dpkg with eatmydata. This is enough to
286 speed up the installation process. There is a proposal to
287 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
288 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
289 tested its impact.&lt;/p&gt;
290
291 </description>
292 </item>
293
294 <item>
295 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
296 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
297 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
298 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
299 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
300 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
301 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
302 elever over det ganske land skal levere inn hvert år. Det mange ikke
303 vet er at selv om de kommersielle alternativene
304 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
305 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
306 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
307 utmerket fri programvarealternativ som kan. Oversetterverktøyet
308 Apertium har støtte for en rekke språkkombinasjoner, og takket være
309 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
310 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
311 nynorsk, og få den automatoversatt til det andre skriftspråket.
312 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
313 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
314 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
315 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
316 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
317 teksten din i webskjemaet der.
318
319 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
320 teknologien kan du enten installere pakken
321 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
322 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
323 api.apertium.org. Se
324 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
325 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
326 denne teksten som ble skrevet på bokmål over maskinoversatt til
327 nynorsk.&lt;/p&gt;
328
329 &lt;hr/&gt;
330
331 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
332 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
333 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
334 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
335 veit er at sjølv om dei kommersielle alternativa
336 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
337 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
338 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
339 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
340 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
341 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
342 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
343 nynorsk, og få den *automatoversatt til det andre skriftspråket.
344 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
345 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
346 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
347 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
348 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
349 teksta di i *webskjemaet der.
350
351 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
352 teknologien kan du anten installera pakken
353 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
354 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
355 *api.*apertium.org. Sjå
356 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
357 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
358 for denne teksta som vart skreva på bokmål over *maskinoversatt til
359 nynorsk.&lt;/p&gt;
360 </description>
361 </item>
362
363 <item>
364 <title>Coz profiler for multi-threaded software is now in Debian</title>
365 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
366 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
367 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
368 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
369 profiler able to run benchmarking experiments on the instrumented
370 multi-threaded program, finally
371 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
372 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
373 months since
374 &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
375 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
376 it suitable for Debian. There are still issues with clang
377 compatibility, inline assembly only working x86 and minimized
378 JavaScript libraries.&lt;/p&gt;
379
380 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
381
382 &lt;p&gt;&lt;blockquote&gt;
383 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
384 &lt;/blockquote&gt;&lt;/p&gt;
385
386 &lt;p&gt;This will produce a profile.coz file in the current working
387 directory with the profiling information. This is then given to a
388 JavaScript application provided in the package and available from
389 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
390 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
391
392 &lt;p&gt;&lt;blockquote&gt;
393 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
394 &lt;/blockquote&gt;&lt;/p&gt;
395
396 &lt;p&gt;See the project home page and the
397 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
398 ;login: article on Coz&lt;/a&gt; for more information on how it is
399 working.&lt;/p&gt;
400 </description>
401 </item>
402
403 <item>
404 <title>My own self balancing Lego Segway</title>
405 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
406 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
407 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
408 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
409 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
410 present. It had been on my wishlist for a while, because I wanted to
411 build a Segway like balancing lego robot. I had already built
412 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
413 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
414 NXT kit as the balance sensor, but it was not working very well. It
415 could balance for a while, but was very sensitive to the light
416 condition in the room and the reflective properties of the surface and
417 would fall over after a short while. I wanted something more robust,
418 and had
419 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
420 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
421 wishlist for some years before it suddenly showed up as a gift from my
422 loved ones. :)&lt;/p&gt;
423
424 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
425 since then. But that changed some days ago, when I was searching for
426 lego segway information and came across a recipe from HiTechnic for
427 building
428 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
429 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
430 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
431 code&lt;/a&gt; was included, so it was just a question of putting it all
432 together. And thanks to the great work of many Debian developers, the
433 compiler needed to build the source for the NXT is already included in
434 Debian, so I was read to go in less than an hour. The resulting robot
435 do not look very impressive in its simplicity:&lt;/p&gt;
436
437 &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;
438
439 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
440 design from HiTechnic, I had to comment out the last task
441 (taskControl). I simply placed /* and */ around it get the program
442 working without that sensor present. Now it balances just fine until
443 the battery status run low:&lt;/p&gt;
444
445 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
446 &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;
447 &lt;/video&gt;&lt;/p&gt;
448
449 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
450 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
451
452 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
453 they need to work with LEGO in Debian and all our derivative
454 distributions like Ubuntu, check out
455 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
456 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
457 RCX and NXT controller (no EV3), and would like to make sure the
458 Debian tools needed to program the systems I own work as they
459 should.&lt;/p&gt;
460 </description>
461 </item>
462
463 <item>
464 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
465 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
467 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
468 <description>&lt;p&gt;In July
469 &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
470 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
471 the ability to receive SMS messages (aka without a cell phone). It is
472 time to share some experiences and provide an updated setup.&lt;/p&gt;
473
474 &lt;p&gt;The Signal app have worked fine for several months now, and I use
475 it regularly to chat with my loved ones. I had a major snag at the
476 end of my summer vacation, when the the app completely forgot my
477 setup, identity and keys. The reason behind this major mess was
478 running out of disk space. To avoid that ever happening again I have
479 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
480 roll back to an earlier version if the files are wiped by mistake. I
481 had to use it once after introducing the git backup. When rolling
482 back to an earlier version, one need to use the &#39;reset session&#39; option
483 in Signal to get going, and notify the people you talk with about the
484 problem. I assume there is some sequence number tracking in the
485 protocol to detect rollback attacks. The git repository is rather big
486 (674 MiB so far), but I have not tried to figure out if some of the
487 content can be added to a .gitignore file due to lack of spare
488 time.&lt;/p&gt;
489
490 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
491 make it impossible to send messages using Signal. I could still
492 receive them, but had to patch the code with a new timestamp to send.
493 I believe the timeout is added by the developers to force people to
494 upgrade to the latest version of the app, even when there is no
495 protocol changes, to reduce the version skew among the user base and
496 thus try to keep the number of support requests down.&lt;/p&gt;
497
498 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
499 making the old patch fail to apply cleanly. Below is an updated
500 patch, including the shell wrapper I use to start Signal. The
501 original version required a new user to locate the JavaScript console
502 and call a function from there. I got help from a friend with more
503 JavaScript knowledge than me to modify the code to provide a GUI
504 button instead. This mean that to get started you just need to run
505 the wrapper and click the &#39;Register without mobile phone&#39; to get going
506 now. I&#39;ve also modified the timeout code to always set it to 90 days
507 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
508
509 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
510
511 &lt;ol&gt;
512
513 &lt;li&gt;First, install required packages to get the source code and the
514 browser you need. Signal only work with Chrome/Chromium, as far as I
515 know, so you need to install it.
516
517 &lt;pre&gt;
518 apt install git tor chromium
519 git clone https://github.com/WhisperSystems/Signal-Desktop.git
520 &lt;/pre&gt;&lt;/li&gt;
521
522 &lt;li&gt;Modify the source code using command listed in the the patch
523 block below.&lt;/li&gt;
524
525 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
526 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
527
528 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
529 number you can receive calls to the next minute, receive the
530 verification code and enter it into the form field and press
531 &#39;Register&#39;. Note, the phone number you use will be user Signal
532 username, ie the way others can find you on Signal.&lt;/li&gt;
533
534 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
535 not show up in the contact list until you restart Signal, and there is
536 no way to assign names to Contacts. There is also no way to create or
537 update chat groups. I suspect this is because the web app do not have
538 a associated contact database.&lt;/li&gt;
539
540 &lt;/ol&gt;
541
542 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
543 main author moxie0 reject federation and accept dependencies to major
544 corporations like Google (part of the code is fetched from Google) and
545 Amazon (the central coordination point is owned by Amazon). See for
546 example
547 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
548 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
549 view on these issues. But the network effect is strong in this case,
550 and several of the people I want to communicate with already use
551 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
552 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
553 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
554 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
555 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
556 working on Debian Stable.&lt;/p&gt;
557
558 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
559 working. It switch to the production servers, disable to timeout,
560 make registration easier and add the shell wrapper:&lt;/p&gt;
561
562 &lt;pre&gt;
563 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
564 diff --git a/js/background.js b/js/background.js
565 index 24b4c1d..579345f 100644
566 --- a/js/background.js
567 +++ b/js/background.js
568 @@ -33,9 +33,9 @@
569 });
570 });
571
572 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
573 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
574 var SERVER_PORTS = [80, 4433, 8443];
575 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
576 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
577 var messageReceiver;
578 window.getSocketStatus = function() {
579 if (messageReceiver) {
580 diff --git a/js/expire.js b/js/expire.js
581 index 639aeae..beb91c3 100644
582 --- a/js/expire.js
583 +++ b/js/expire.js
584 @@ -1,6 +1,6 @@
585 ;(function() {
586 &#39;use strict&#39;;
587 - var BUILD_EXPIRATION = 0;
588 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
589
590 window.extension = window.extension || {};
591
592 diff --git a/js/views/install_view.js b/js/views/install_view.js
593 index 7816f4f..1d6233b 100644
594 --- a/js/views/install_view.js
595 +++ b/js/views/install_view.js
596 @@ -38,7 +38,8 @@
597 return {
598 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
599 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
600 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
601 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
602 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
603 };
604 },
605 clearQR: function() {
606 diff --git a/options.html b/options.html
607 index dc0f28e..8d709f6 100644
608 --- a/options.html
609 +++ b/options.html
610 @@ -14,7 +14,10 @@
611 &amp;lt;div class=&#39;nav&#39;&gt;
612 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
613 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
614 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
615 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
616 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
617 +
618 + &amp;lt;/div&gt;
619 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
620 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
621 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
622 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
623 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
624 @@ -0,0 +1,12 @@
625 +#!/bin/sh
626 +set -e
627 +cd $(dirname $0)
628 +mkdir -p userdata
629 +userdata=&quot;`pwd`/userdata&quot;
630 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
631 + (cd $userdata &amp;&amp; git init)
632 +fi
633 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
634 +exec chromium \
635 + --proxy-server=&quot;socks://localhost:9050&quot; \
636 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
637 EOF
638 chmod a+rx run-signal-app
639 &lt;/pre&gt;
640
641 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
642 activities, please send Bitcoin donations to my address
643 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
644 </description>
645 </item>
646
647 <item>
648 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
649 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
650 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
651 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
652 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
653 system&lt;/a&gt; provide a practical and easy way to figure out which
654 packages support the hardware in a given machine. The command line
655 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
656 convenient way to list and install packages relevant for the current
657 hardware during system installation, both user space packages and
658 firmware packages. The GUI background daemon on the other hand provide
659 a pop-up proposing to install packages when a new dongle is inserted
660 while using the computer. For example, if you plug in a smart card
661 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
662 that package isn&#39;t already installed, and if you plug in a USB video
663 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
664 cheese is currently missing. This already work just fine.&lt;/p&gt;
665
666 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
667 package names. When I started no such database existed in Debian, so
668 I made my own data set and included it with the isenkram package and
669 made isenkram fetch the latest version of this database from git using
670 http. This way the isenkram users would get updated package proposals
671 as soon as I learned more about hardware related packages.&lt;/p&gt;
672
673 &lt;p&gt;The hardware is identified using modalias strings. The modalias
674 design is from the Linux kernel where most hardware descriptors are
675 made available as a strings that can be matched using filename style
676 globbing. It handle USB, PCI, DMI and a lot of other hardware related
677 identifiers.&lt;/p&gt;
678
679 &lt;p&gt;The downside to the Isenkram specific database is that there is no
680 information about relevant distribution / Debian version, making
681 isenkram propose obsolete packages too. But along came AppStream, a
682 cross distribution mechanism to store and collect metadata about
683 software packages. When I heard about the proposal, I contacted the
684 people involved and suggested to add a hardware matching rule using
685 modalias strings in the specification, to be able to use AppStream for
686 mapping hardware to packages. This idea was accepted and AppStream is
687 now a great way for a package to announce the hardware it support in a
688 distribution neutral way. I wrote
689 &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
690 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
691 December. If you have a hardware related package in Debian, please
692 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
693
694 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
695 RCX or NXT unit, announce this support using AppStream. The effect is
696 that when you insert such LEGO robot controller into your Debian
697 machine, Isenkram will propose to install the packages needed to get
698 it working. The intention is that this should allow the local user to
699 start programming his robot controller right away without having to
700 guess what packages to use or which permissions to fix.&lt;/p&gt;
701
702 &lt;p&gt;But when I sat down with my son the other day to program our NXT
703 unit using his Debian Stretch computer, I discovered something
704 annoying. The local console user (ie my son) did not get access to
705 the USB device for programming the unit. This used to work, but no
706 longer in Jessie and Stretch. After some investigation and asking
707 around on #debian-devel, I discovered that this was because udev had
708 changed the mechanism used to grant access to local devices. The
709 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
710 no longer applied, because LDAP users no longer was added to the
711 plugdev group during login. Michael Biebl told me that this method
712 was obsolete and the new method used ACLs instead. This was good
713 news, as the plugdev mechanism is a mess when using a remote user
714 directory like LDAP. Using ACLs would make sure a user lost device
715 access when she logged out, even if the user left behind a background
716 process which would retain the plugdev membership with the ConsoleKit
717 setup. Armed with this knowledge I moved on to fix the access problem
718 for the LEGO Mindstorms related packages.&lt;/p&gt;
719
720 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
721 applied directly for a device, or is applied in
722 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
723 LEGO Mindstorms udev rules did not have a class, I decided to add the
724 tag directly in the udev rules files included in the packages. Here
725 is one example. For the nqc C compiler for the RCX, the
726 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
727
728 &lt;p&gt;&lt;pre&gt;
729 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
730 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
731 &lt;/pre&gt;&lt;/p&gt;
732
733 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
734 packages using plugdev in their /lib/udev/rules.d/ files should be
735 changed to use this tag (either directly or indirectly via
736 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
737 to detect this?&lt;/p&gt;
738
739 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
740 It is unclear to me if the uaccess tag is an internal implementation
741 detail like the udev-acl tag used by
742 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
743 indirect method is the preferred way. Michael
744 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
745 documentation from the systemd project&lt;/a&gt; and I hope it will make
746 this clearer. For now I use the generic classes when they exist and
747 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
748 directly if no such class exist.&lt;/p&gt;
749
750 &lt;p&gt;To learn more about the isenkram system, please check out
751 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
752 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
753
754 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
755 please join us on our IRC channel
756 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
757 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
758 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
759 list is not yet created, but we are working on it. :)&lt;/p&gt;
760
761 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
762 activities, please send Bitcoin donations to my address
763 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
764 </description>
765 </item>
766
767 <item>
768 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
769 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
770 <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>
771 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
772 <description>&lt;p&gt;In April we
773 &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
774 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
775 how to set up and administrate a Debian system. Today I am happy to
776 report that the first draft is now publicly available. You can find
777 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
778 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
779 eight chapters have a first draft translation, and we are working on
780 proofreading the content. If you want to help out, please start
781 contributing using
782 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
783 hosted weblate project page&lt;/a&gt;, and get in touch using
784 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
785 translators mailing list&lt;/a&gt;. Please also check out
786 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
787 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
788 and update weblate if you find errors.&lt;/p&gt;
789
790 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
791 electronic form.&lt;/p&gt;
792 </description>
793 </item>
794
795 <item>
796 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
797 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
799 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
800 <description>&lt;p&gt;This summer, I read a great article
801 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
802 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
803 how to profile multi-threaded programs. It presented a system for
804 profiling software by running experiences in the running program,
805 testing how run time performance is affected by &quot;speeding up&quot; parts of
806 the code to various degrees compared to a normal run. It does this by
807 slowing down parallel threads while the &quot;faster up&quot; code is running
808 and measure how this affect processing time. The processing time is
809 measured using probes inserted into the code, either using progress
810 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
811 can also measure unmodified code by measuring complete the program
812 runtime and running the program several times instead.&lt;/p&gt;
813
814 &lt;p&gt;The project and presentation was so inspiring that I would like to
815 get the system into Debian. I
816 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
817 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
818 system ready for Debian by sending patches. The build process need to
819 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
820 to include the JavaScript web page used to visualize the collected
821 profiling information included in the source package.
822 But I expect that should work out fairly soon.&lt;/p&gt;
823
824 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
825 on a binary with debug symbols available, start the program like this:
826
827 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
828 coz run --- program-to-run
829 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
830
831 &lt;p&gt;This will create a text file profile.coz with the instrumentation
832 information. To show what part of the code affect the performance
833 most, use a web browser and either point it to
834 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
835 or use the copy from git (in the gh-pages branch). Check out this web
836 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
837 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
838 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
839 code, rebuild and run the profiler. This allow coz to do more
840 targeted experiments.&lt;/p&gt;
841
842 &lt;p&gt;A video published by ACM
843 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
844 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
845 from the 25th Symposium on Operating Systems Principles available
846 titled
847 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
848 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
849
850 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
851 for Coz is available from github. It will only build with clang
852 because it uses a
853 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
854 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
855 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
856 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
857
858 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
859 of software in Debian. I would very much like some help with the
860 packaging effort, as I lack the in depth knowledge on how to package
861 C++ libraries.&lt;/p&gt;
862 </description>
863 </item>
864
865 <item>
866 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
867 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
869 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
870 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
871 to be a slight challenge. Here is the recipe if I ever need to do it
872 again. It all started by me wanting to try the recipe to set up
873 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
874 hardened Android installation&lt;/a&gt; from the Tor project blog on a
875 device I had access to. It is a old mobile phone with a broken
876 microphone The initial idea had been to just
877 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
878 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
879 until a few days ago.&lt;/p&gt;
880
881 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
882 loader (press volume down and power at the same time), (2) select
883 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
884 machine, (4) request the device identifier token by running &#39;fastboot
885 oem get_identifier_token&#39;, (5) request the device unlocking key using
886 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
887 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
888
889 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
890 or newer, and the device I was working on had 2.00.0027. This
891 apparently can be easily fixed by downloading a Windows program and
892 running it on your Windows machine, if you accept the terms Microsoft
893 require you to accept to use Windows - which I do not. So I had to
894 come up with a different approach. I got a lot of help from AndyCap
895 on #nuug, and would not have been able to get this working without
896 him.&lt;/p&gt;
897
898 &lt;p&gt;First I needed to extract the hboot firmware from
899 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
900 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
901 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
902 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
903 recognise the file format, but unruu worked and extracted rom.zip,
904 containing the new hboot firmware and a text file describing which
905 devices it would work for.&lt;/p&gt;
906
907 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
908 followed some instructions
909 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
910 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
911 machine with Debian testing:&lt;/p&gt;
912
913 &lt;p&gt;&lt;pre&gt;
914 adb reboot-bootloader
915 fastboot oem rebootRUU
916 fastboot flash zip rom.zip
917 fastboot flash zip rom.zip
918 fastboot reboot
919 &lt;/pre&gt;&lt;/p&gt;
920
921 &lt;p&gt;The flash command apparently need to be done twice to take effect,
922 as the first is just preparations and the second one do the flashing.
923 The adb command is just to get to the boot loader menu, so turning the
924 device on while holding volume down and the power button should work
925 too.&lt;/p&gt;
926
927 &lt;p&gt;With the new hboot version in place I could start following the
928 instructions on the HTC developer web site. I got the device token
929 like this:&lt;/p&gt;
930
931 &lt;p&gt;&lt;pre&gt;
932 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
933 &lt;/pre&gt;
934
935 &lt;p&gt;And once I got the unlock code via email, I could use it like
936 this:&lt;/p&gt;
937
938 &lt;p&gt;&lt;pre&gt;
939 fastboot flash unlocktoken Unlock_code.bin
940 &lt;/pre&gt;&lt;/p&gt;
941
942 &lt;p&gt;And with that final step in place, the phone was unlocked and I
943 could start stuffing the software of my own choosing into the device.
944 So far I only inserted a replacement recovery image to wipe the phone
945 before I start. We will see what happen next. Perhaps I should
946 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
947 </description>
948 </item>
949
950 <item>
951 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
952 <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>
953 <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>
954 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
955 <description>&lt;p&gt;For a while now, I have wanted to test
956 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
957 said to provide end to end encrypted communication and several of my
958 friends and family are already using it. As I by choice do not own a
959 mobile phone, this proved to be harder than expected. And I wanted to
960 have the source of the client and know that it was the code used on my
961 machine. But yesterday I managed to get it working. I used the
962 Github source, compared it to the source in
963 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
964 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
965 patches to use the production Signal servers, started the app and
966 asked for the hidden &quot;register without a smart phone&quot; form. Here is
967 the recipe how I did it.&lt;/p&gt;
968
969 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
970
971 &lt;pre&gt;
972 git clone https://github.com/WhisperSystems/Signal-Desktop.git
973 &lt;/pre&gt;
974
975 &lt;p&gt;Next, I patched the source to use the production servers, to be
976 able to talk to other Signal users:&lt;/p&gt;
977
978 &lt;pre&gt;
979 cat &amp;lt;&amp;lt;EOF | patch -p0
980 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
981 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
982 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
983 @@ -47,8 +47,8 @@
984 });
985 });
986
987 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
988 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
989 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
990 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
991 var messageReceiver;
992 window.getSocketStatus = function() {
993 if (messageReceiver) {
994 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
995 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
996 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
997 @@ -1,6 +1,6 @@
998 ;(function() {
999 &#39;use strict&#39;;
1000 - var BUILD_EXPIRATION = 0;
1001 + var BUILD_EXPIRATION = 1474492690000;
1002
1003 window.extension = window.extension || {};
1004
1005 EOF
1006 &lt;/pre&gt;
1007
1008 &lt;p&gt;The first part is changing the servers, and the second is updating
1009 an expiration timestamp. This timestamp need to be updated regularly.
1010 It is set 90 days in the future by the build process (Gruntfile.js).
1011 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
1012
1013 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
1014 script to launch Signal in Chromium.&lt;/p&gt;
1015
1016 &lt;pre&gt;
1017 #!/bin/sh
1018 cd $(dirname $0)
1019 mkdir -p userdata
1020 exec chromium \
1021 --proxy-server=&quot;socks://localhost:9050&quot; \
1022 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1023 &lt;/pre&gt;
1024
1025 &lt;p&gt; The script start the app and configure Chromium to use the Tor
1026 SOCKS5 proxy to make sure those controlling the Signal servers (today
1027 Amazon and Whisper Systems) as well as those listening on the lines
1028 will have a harder time location my laptop based on the Signal
1029 connections if they use source IP address.&lt;/p&gt;
1030
1031 &lt;p&gt;When the script starts, one need to follow the instructions under
1032 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
1033 repository. I right clicked on the Signal window to get up the
1034 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
1035 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
1036 registration form. Then I entered by land line phone number and
1037 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
1038 repeated the verification code three times. After entering the number
1039 into the verification code field in the form, I could start using
1040 Signal from my laptop.
1041
1042 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
1043 whom and thus who know who to those controlling the central server,
1044 but such leakage is hard to avoid with a centrally controlled server
1045 setup. It is something to keep in mind when using Signal - the
1046 content of your chats are harder to intercept, but the meta data
1047 exposing your contact network is available to people you do not know.
1048 So better than many options, but not great. And sadly the usage is
1049 connected to my land line, thus allowing those controlling the server
1050 to associate it to my home and person. I would prefer it if only
1051 those I knew could tell who I was on Signal. There are options
1052 avoiding such information leakage, but most of my friends are not
1053 using them, so I am stuck with Signal for now.&lt;/p&gt;
1054 </description>
1055 </item>
1056
1057 <item>
1058 <title>The new &quot;best&quot; multimedia player in Debian?</title>
1059 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
1060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
1061 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
1062 <description>&lt;p&gt;When I set out a few weeks ago to figure out
1063 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
1064 multimedia player in Debian claimed to support most file formats /
1065 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
1066 the various players claimed support for. The range was from 55 to 130
1067 MIME types. I suspect most media formats are supported by all
1068 players, but this is not really reflected in the MimeTypes values in
1069 their desktop files. There are probably also some bogus MIME types
1070 listed, but it is hard to identify which one this is.&lt;/p&gt;
1071
1072 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
1073 the players suggesting to add more MIME types to their desktop files,
1074 and decided to spend some time myself improving the situation for my
1075 favorite media player VLC. The fixes for VLC entered Debian unstable
1076 yesterday. The complete list of MIME types can be seen on the
1077 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
1078 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
1079
1080 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
1081 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1082 kmplayer. I am sure some of the other players desktop files support
1083 several of the formats currently listed as working only with vlc,
1084 toten and parole.&lt;/p&gt;
1085
1086 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
1087 supported by all the tested multimedia players in Debian in their
1088 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1089 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1090 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1091 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1092 it sad that video/ogg and video/webm is not supported by all the media
1093 players in Debian. As far as I can tell, all of them can handle both
1094 formats.&lt;/p&gt;
1095 </description>
1096 </item>
1097
1098 <item>
1099 <title>A program should be able to open its own files on Linux</title>
1100 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1102 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1103 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1104 decided to test its presentation tool when making the slides for a
1105 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1106 wrote the first draft of the slides, saved the result and went to bed
1107 the day before I would give the talk. The next day I took a plane to
1108 the location where the meeting should take place, and on the plane I
1109 started up koffice again to polish the talk a bit, only to discover
1110 that kpresenter refused to load its own data file. I cursed a bit and
1111 started making the slides again from memory, to have something to
1112 present when I arrived. I tested that the saved files could be
1113 loaded, and the day seemed to be rescued. I continued to polish the
1114 slides until I suddenly discovered that the saved file could no longer
1115 be loaded into kpresenter. In the end I had to rewrite the slides
1116 three times, condensing the content until the talk became shorter and
1117 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1118 kpresenter wrote inline images in a way itself could not understand.
1119 Eventually that bug was fixed and kpresenter ended up being a great
1120 program to make slides. The point I&#39;m trying to make is that we
1121 expect a program to be able to load its own data files, and it is
1122 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1123
1124 &lt;p&gt;Did you ever experience a program failing to load its own data
1125 files from the desktop file browser? It is not a uncommon problem. A
1126 while back I discovered that the screencast recorder
1127 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1128 browser would refuse to open. No video player claimed to understand
1129 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1130 returning the application/ogg MIME type, which no video player I had
1131 installed listed as a MIME type they would understand. I asked for
1132 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1133 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1134 several video players to add video/ogg to their desktop files, to give
1135 the file browser an idea what to do about Ogg Theora files. After a
1136 while, the desktop file browsers in Debian started to handle the
1137 output from gtk-recordmydesktop properly.&lt;/p&gt;
1138
1139 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1140 system Rosegarden again, and I discovered that the KDE and xfce file
1141 browsers did not know what to do with the Rosegarden project files
1142 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1143 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1144 included in the next upload. To increase the chance of me remembering
1145 how to fix the problem next time some program fail to load its files
1146 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1147
1148 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1149 There are two sources for the MIME type of a given file. The output from
1150 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1151 shared MIME type registry (under /usr/share/mime/). The file MIME
1152 type is mapped to programs supporting the MIME type, and this
1153 information is collected from
1154 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1155 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1156 one desktop file claiming support for the MIME type of the file, it is
1157 activated when asking to open a given file. If there are more, one
1158 can normally select which one to use by right-clicking on the file and
1159 selecting the wanted one using &#39;Open with&#39; or similar. In general
1160 this work well. But it depend on each program picking a good MIME
1161 type (preferably
1162 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1163 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1164 registry recognizing the file and the desktop file to list the MIME
1165 type in its list of supported MIME types.&lt;/p&gt;
1166
1167 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1168 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1169 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1170
1171 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1172 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1173 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1174 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1175 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1176 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1177 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1178 &amp;lt;/mime-type&amp;gt;
1179 &amp;lt;/mime-info&amp;gt;
1180 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1181
1182 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1183 (it is a gzipped XML file). Note, it is much better to use an
1184 official MIME type registered with IANA than it is to make up ones own
1185 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1186
1187 &lt;p&gt;The desktop file of the rosegarden program failed to list
1188 audio/x-rosegarden in its list of supported MIME types, causing the
1189 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1190
1191 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1192 % grep Mime /usr/share/applications/rosegarden.desktop
1193 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1194 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1195 %
1196 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1197
1198 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
1199 MimeType= line.&lt;/p&gt;
1200
1201 &lt;p&gt;If you run into a file which fail to open the correct program when
1202 selected from the file browser, please check out the output from
1203 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
1204 MIME type is registered somewhere under /usr/share/mime/ and check
1205 that some desktop file under /usr/share/applications/ is claiming
1206 support for this MIME type. If not, please report a bug to have it
1207 fixed. :)&lt;/p&gt;
1208 </description>
1209 </item>
1210
1211 <item>
1212 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
1213 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
1214 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
1215 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
1216 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
1217 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
1218 related packages. The idea is to have a database of mappings between
1219 hardware and packages, and pop up a dialog suggesting for the user to
1220 install the packages to use a given hardware dongle. Some use cases
1221 are when you insert a Yubikey, it proposes to install the software
1222 needed to control it; when you insert a braille reader list it
1223 proposes to install the packages needed to send text to the reader;
1224 and when you insert a ColorHug screen calibrator it suggests to
1225 install the driver for it. The system work well, and even have a few
1226 command line tools to install firmware packages and packages for the
1227 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
1228
1229 &lt;p&gt;The system was initially written using aptdaemon, because I found
1230 good documentation and example code on how to use it. But aptdaemon
1231 is going away and is generally being replaced by
1232 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
1233 so Isenkram needed a rewrite. And today, thanks to the great patch
1234 from my college Sunil Mohan Adapa in the FreedomBox project, the
1235 rewrite finally took place. I&#39;ve just uploaded a new version of
1236 Isenkram into Debian Unstable with the patch included, and the default
1237 for the background daemon is now to use PackageKit. To check it out,
1238 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
1239 and see if it is recognised.&lt;/p&gt;
1240
1241 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
1242 the machine it is running on, you can check out the isenkram-lookup
1243 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
1244
1245 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1246 % isenkram-lookup
1247 bluez
1248 cheese
1249 fprintd
1250 fprintd-demo
1251 gkrellm-thinkbat
1252 hdapsd
1253 libpam-fprintd
1254 pidgin-blinklight
1255 thinkfan
1256 tleds
1257 tp-smapi-dkms
1258 tp-smapi-source
1259 tpb
1260 %p
1261 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1262
1263 &lt;p&gt;The hardware mappings come from several places. The preferred way
1264 is for packages to announce their hardware support using
1265 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1266 cross distribution appstream system&lt;/a&gt;.
1267 See
1268 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
1269 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
1270 </description>
1271 </item>
1272
1273 <item>
1274 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
1275 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
1276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
1277 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
1278 <description>&lt;p&gt;Yesterday I updated the
1279 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
1280 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
1281 enterprising users. There were some nice user and visible changes.
1282 First of all, both desktop menu entries now work. A design flaw in
1283 one of the script made the history graph fail to show up (its PNG was
1284 dumped in ~/.xsession-errors) if no controlling TTY was available.
1285 The script worked when called from the command line, but not when
1286 called from the desktop menu. I changed this to look for a DISPLAY
1287 variable or a TTY before deciding where to draw the graph, and now the
1288 graph window pop up as expected.&lt;/p&gt;
1289
1290 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
1291 graphs (the one showing the last few hours). New is also the user of
1292 colours showing charging in blue and discharge in red. The percentages
1293 of this graph is relative to last full charge, not battery design
1294 capacity.&lt;/p&gt;
1295
1296 &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;
1297
1298 &lt;p&gt;The other graph show the entire history of the collected battery
1299 statistics, comparing it to the design capacity of the battery to
1300 visualise how the battery life time get shorter over time. The red
1301 line in this graph is what the previous graph considers 100 percent:
1302
1303 &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;
1304
1305 &lt;p&gt;In this graph you can see that I only charge the battery to 80
1306 percent of last full capacity, and how the capacity of the battery is
1307 shrinking. :(&lt;/p&gt;
1308
1309 &lt;p&gt;The last new feature is in the collector, which now will handle
1310 more hardware models. On some hardware, Linux power supply
1311 information is stored in /sys/class/power_supply/ACAD/, while the
1312 collector previously only looked in /sys/class/power_supply/AC/. Now
1313 both are checked to figure if there is power connected to the
1314 machine.&lt;/p&gt;
1315
1316 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1317 check out the
1318 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1319 in Debian unstable, or rebuild it on Jessie to get it working on
1320 Debian stable. :) The upstream source is available from &lt;a
1321 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1322 Patches are very welcome.&lt;/p&gt;
1323
1324 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1325 activities, please send Bitcoin donations to my address
1326 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1327 </description>
1328 </item>
1329
1330 <item>
1331 <title>Debian now with ZFS on Linux included</title>
1332 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
1333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
1334 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
1335 <description>&lt;p&gt;Today, after many years of hard work from many people,
1336 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
1337 Debian. The package status can be seen on
1338 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
1339 for zfs-linux&lt;/a&gt;. and
1340 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1341 team status page&lt;/a&gt;. If you want to help out, please join us.
1342 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
1343 source code&lt;/a&gt; is available via git on Alioth. It would also be
1344 great if you could help out with
1345 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
1346 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
1347 </description>
1348 </item>
1349
1350 <item>
1351 <title>What is the best multimedia player in Debian?</title>
1352 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
1353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
1354 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
1355 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
1356 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
1357
1358 &lt;p&gt;A few years ago, I had a look at the media support for Browser
1359 plugins in Debian, to get an idea which plugins to include in Debian
1360 Edu. I created a script to extract the set of supported MIME types
1361 for each plugin, and used this to find out which multimedia browser
1362 plugin supported most file formats / media types.
1363 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
1364 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
1365 not been updated for a while. But browser plugins are less relevant
1366 these days, so I thought it was time to look at standalone
1367 players.&lt;/p&gt;
1368
1369 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
1370 player when I wanted to play videos from the Norwegian National
1371 Broadcasting Company, and decided to investigate why. The cause is a
1372 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
1373 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
1374 of MIME types announced in the desktop file and the browser plugin,
1375 only to discover that there is quite a large difference between the
1376 two for VLC. This discovery made me dig up the script I used to
1377 compare browser plugins, and adjust it to compare desktop files
1378 instead, to try to figure out which multimedia player in Debian
1379 support most file formats.&lt;/p&gt;
1380
1381 &lt;p&gt;The result can be seen on the Debian Wiki, as
1382 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
1383 table listing all MIME types supported by one of the packages included
1384 in the table&lt;/a&gt;, with the package supporting most MIME types being
1385 listed first in the table.&lt;/p&gt;
1386
1387 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
1388 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1389 kmplayer. Time for the other players to update their announced MIME
1390 support?&lt;/p&gt;
1391 </description>
1392 </item>
1393
1394 <item>
1395 <title>The Pyra - handheld computer with Debian preinstalled</title>
1396 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1398 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1399 <description>A friend of mine made me aware of
1400 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1401 handheld computer which will be delivered with Debian preinstalled. I
1402 would love to get one of those for my birthday. :)&lt;/p&gt;
1403
1404 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1405 plugs and many others connectors, and include a full keyboard and a 5&quot;
1406 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1407 day of battery life time, but I have not seen any independent tests
1408 confirming this. The vendor is still collecting preorders, and the
1409 last I heard last night was that 22 more orders were needed before
1410 production started.&lt;/p&gt;
1411
1412 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1413 Debian. Please let me know if you know of any others. Is it the
1414 first computer being sold with Debian preinstalled?&lt;/p&gt;
1415 </description>
1416 </item>
1417
1418 <item>
1419 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1420 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1421 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1422 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1423 <description>&lt;p&gt;During this weekends
1424 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1425 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1426 to make sure there are good books about Debian available in Norwegian
1427 Bokmål, and got in touch with the people behind the
1428 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1429 project&lt;/a&gt; to get started. If you want to help out, please start
1430 contributing using
1431 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1432 hosted weblate project page&lt;/a&gt;, and get in touch using
1433 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1434 translators mailing list&lt;/a&gt;. Please also check out
1435 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1436 contributors&lt;/a&gt;.&lt;/p&gt;
1437
1438 &lt;p&gt;The book is already available on paper in English, French and
1439 Japanese, and our goal is to get it available on paper in Norwegian
1440 Bokmål too. In addition to the paper edition, there are also EPUB and
1441 Mobi versions available. And there are incomplete translations
1442 available for many more languages.&lt;/p&gt;
1443 </description>
1444 </item>
1445
1446 <item>
1447 <title>One in two hundred Debian users using ZFS on Linux?</title>
1448 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1450 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1451 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1452 packages in Debian, and was quite surprised with what I found. I use
1453 ZFS myself at home, but did not really expect many others to do so.
1454 But I might be wrong.&lt;/p&gt;
1455
1456 &lt;p&gt;According to
1457 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1458 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1459 0.53% of the population, with the package installed. As far as I know
1460 the only use of the spl-linux package is as a support library for ZFS
1461 on Linux, so I use it here as proxy for measuring the number of ZFS
1462 installation on Linux in Debian. In the kFreeBSD variant of Debian
1463 the ZFS feature is already available, and there
1464 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1465 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1466 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1467
1468 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1469 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1470 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1471 cleared, the package is still not in Debian. The package is again in
1472 the NEW queue. Several uploads have been rejected so far because the
1473 debian/copyright file was incomplete or wrong, but there is no reason
1474 to give up. The current status can be seen on
1475 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1476 team status page&lt;/a&gt;, and
1477 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1478 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1479
1480 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1481 my home server can function in the future using only official Debian
1482 packages, and the current blocker is to get the debian/copyright file
1483 accepted by the FTP masters in Debian, I decided a while back to try
1484 to help out the team. This was the background for my blog post about
1485 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1486 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1487 used the techniques I explored there to try to find any errors in the
1488 copyright file. It is not very easy to check every one of the around
1489 2000 files in the source package, but I hope we this time got it
1490 right. If you want to help out, check out the git source and try to
1491 find missing entries in the debian/copyright file.&lt;/p&gt;
1492 </description>
1493 </item>
1494
1495 <item>
1496 <title>Full battery stats collector is now available in Debian</title>
1497 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1499 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1500 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1501 extended collector that will collect the complete battery history for
1502 later processing and graphing. The original collector store the
1503 battery level as percentage of last full level, while the new
1504 collector also record battery vendor, model, serial number, design
1505 full level, last full level and current battery level. This make it
1506 possible to predict the lifetime of the battery as well as visualise
1507 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1508
1509 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1510 in the version 0.5.1 package in unstable. Get the new battery level graph
1511 and lifetime prediction by running:
1512
1513 &lt;p&gt;&lt;pre&gt;
1514 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1515 &lt;/pre&gt;&lt;/p&gt;
1516
1517 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1518
1519 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1520 entry yet):&lt;/p&gt;
1521
1522 &lt;p&gt;&lt;pre&gt;
1523 /usr/share/battery-stats/battery-stats-graph-flow
1524 &lt;/pre&gt;&lt;/p&gt;
1525
1526 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1527 when there are few data points. The graphs look a bit better with a
1528 few years of data.&lt;/p&gt;
1529
1530 &lt;p&gt;A while back one important feature I use in the battery stats
1531 collector broke in Debian. The scripts in
1532 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1533 suspect it happened when Jessie started using systemd, but I do not
1534 know. The issue is reported as
1535 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1536 pm-utils. I managed to work around it by adding an udev rule to call
1537 the collector script every time the power connector is connected and
1538 disconnected. With this fix in place it was finally time to make a
1539 new release of the package, and get it into Debian.&lt;/p&gt;
1540
1541 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1542 check out the
1543 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1544 in Debian unstable, or rebuild it on Jessie to get it working on
1545 Debian stable. :) The upstream source is available from
1546 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1547 As always, patches are very welcome.&lt;/p&gt;
1548 </description>
1549 </item>
1550
1551 <item>
1552 <title>Making battery measurements a little easier in Debian</title>
1553 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1554 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1555 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1556 <description>&lt;p&gt;Back in September, I blogged about
1557 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1558 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1559 how it showed the decay and death of this battery (now replaced). I
1560 created a simple deb package to handle the collection and graphing,
1561 but did not want to upload it to Debian as there were already
1562 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1563 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1564 a point of uploading a competing package when battery-stats could be
1565 fixed instead. I reported a few bugs about its non-function, and
1566 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1567
1568 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1569 hands. The end result is that I am now the new upstream developer of
1570 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
1571 battery-stats in Debian, and the package in Debian unstable is finally
1572 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1573 information provided by the Linux kernel. If you install the
1574 battery-stats package from unstable now, you will be able to get a
1575 graph of the current battery fill level, to get some idea about the
1576 status of the battery. The source package build and work just fine in
1577 Debian testing and stable (and probably oldstable too, but I have not
1578 tested). The default graph you get for that system look like this:&lt;/p&gt;
1579
1580 &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;
1581
1582 &lt;p&gt;My plans for the future is to merge my old scripts into the
1583 battery-stats package, as my old scripts collected a lot more details
1584 about the battery. The scripts are merged into the upstream
1585 battery-stats git repository already, but I am not convinced they work
1586 yet, as I changed a lot of paths along the way. Will have to test a
1587 bit more before I make a new release.&lt;/p&gt;
1588
1589 &lt;p&gt;I will also consider changing the file format slightly, as I
1590 suspect the way I combine several values into one field might make it
1591 impossible to know the type of the value when using it for processing
1592 and graphing.&lt;/p&gt;
1593
1594 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1595 battery, check out the battery-stats package in
1596 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1597 on
1598 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1599 I would love some help to improve the system further.&lt;/p&gt;
1600 </description>
1601 </item>
1602
1603 <item>
1604 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1605 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1607 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1608 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1609 details. And one of the details is the content of the
1610 debian/copyright file, which should list all relevant licenses used by
1611 the code in the package in question, preferably in
1612 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1613 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1614
1615 &lt;p&gt;For large packages with lots of contributors it is hard to write
1616 and update this file manually, and if you get some detail wrong, the
1617 package is normally rejected by the ftpmasters. So getting it right
1618 the first time around get the package into Debian faster, and save
1619 both you and the ftpmasters some work.. Today, while trying to figure
1620 out what was wrong with
1621 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1622 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
1623 figuring out the options for doing this job automatically, or at least
1624 semi-automatically.&lt;/p&gt;
1625
1626 &lt;p&gt;Lucikly, there are at least two tools available for generating the
1627 file based on the code in the source package,
1628 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
1629 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
1630 not sure which one of them came first, but both seem to be able to
1631 create a sensible draft file. As far as I can tell, none of them can
1632 be trusted to get the result just right, so the content need to be
1633 polished a bit before the file is OK to upload. I found the debmake
1634 option in
1635 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
1636 blog posts from 2014&lt;/a&gt;.
1637
1638 &lt;p&gt;To generate using debmake, use the -cc option:
1639
1640 &lt;p&gt;&lt;pre&gt;
1641 debmake -cc &gt; debian/copyright
1642 &lt;/pre&gt;&lt;/p&gt;
1643
1644 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
1645 this might not be the best option.&lt;/p&gt;
1646
1647 &lt;p&gt;The cme option is based on a config parsing library, and I found
1648 this approach in
1649 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
1650 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
1651 dpkg-copyright&#39; option:
1652
1653 &lt;p&gt;&lt;pre&gt;
1654 cme update dpkg-copyright
1655 &lt;/pre&gt;&lt;/p&gt;
1656
1657 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
1658 handle UTF-8 names better than debmake.&lt;/p&gt;
1659
1660 &lt;p&gt;When the copyright file is created, I would also like some help to
1661 check if the file is correct. For this I found two good options,
1662 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
1663 to focus on license types and file matching, and is able to detect
1664 ineffective blocks in the copyright file. The latter reports missing
1665 copyright holders and years, but was confused by inconsistent license
1666 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
1667 fix all issues reported by them before uploading. But I do not know
1668 if the tools and the ftpmasters agree on what is important to fix in a
1669 copyright file, so the package might still be rejected.&lt;/p&gt;
1670
1671 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
1672 will read through the source and try to find all copyright statements.
1673 It is not comparing the result to the content of debian/copyright, but
1674 can be useful when verifying the content of the copyright file.&lt;/p&gt;
1675
1676 &lt;p&gt;Are you aware of better tools in Debian to create and update
1677 debian/copyright file. Please let me know, or blog about it on
1678 planet.debian.org.&lt;/p&gt;
1679
1680 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1681 activities, please send Bitcoin donations to my address
1682 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1683
1684 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
1685 on how to use licensecheck and cdbs to create a draft copyright file
1686
1687 &lt;p&gt;&lt;pre&gt;
1688 licensecheck --copyright -r `find * -type f` | \
1689 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
1690 &lt;/pre&gt;&lt;/p&gt;
1691
1692 &lt;p&gt;He mentioned that he normally check the generated file into the
1693 version control system to make it easier to discover license and
1694 copyright changes in the upstream source. I will try to do the same
1695 with my packages in the future.&lt;/p&gt;
1696
1697 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
1698 against using -quiet for new users, so I removed it from the proposed
1699 command line.&lt;/p&gt;
1700 </description>
1701 </item>
1702
1703 <item>
1704 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
1705 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
1706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
1707 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
1708 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
1709 is taking shape in Debian, and one provided feature is a very
1710 convenient way to tell you which package to install to make a given
1711 firmware file available when the kernel is looking for it. This can
1712 be done using apt-file too, but that is for someone else to blog
1713 about. :)&lt;/p&gt;
1714
1715 &lt;p&gt;Here is a small recipe to find the package with a given firmware
1716 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
1717 picked from the set of firmware announced using appstream in Debian
1718 unstable. In general you would be looking for the firmware requested
1719 by the kernel during kernel module loading. To find the package
1720 providing the example file, do like this:&lt;/p&gt;
1721
1722 &lt;blockquote&gt;&lt;pre&gt;
1723 % apt install appstream
1724 [...]
1725 % apt update
1726 [...]
1727 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
1728 awk &#39;/Package:/ {print $2}&#39;
1729 firmware-qlogic
1730 %
1731 &lt;/pre&gt;&lt;/blockquote&gt;
1732
1733 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
1734 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
1735 a way appstream can use.&lt;/p&gt;
1736
1737 &lt;p&gt;This same approach can be used to find any package supporting a
1738 given MIME type. This is very useful when you get a file you do not
1739 know how to handle. First find the mime type using &lt;tt&gt;file
1740 --mime-type&lt;/tt&gt;, and next look up the package providing support for
1741 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1742 and you can find all packages handling this type like this:&lt;/p&gt;
1743
1744 &lt;blockquote&gt;&lt;pre&gt;
1745 % apt install appstream
1746 [...]
1747 % apt update
1748 [...]
1749 % appstreamcli what-provides mimetype image/svg+xml | \
1750 awk &#39;/Package:/ {print $2}&#39;
1751 bkchem
1752 phototonic
1753 inkscape
1754 shutter
1755 tetzle
1756 geeqie
1757 xia
1758 pinta
1759 gthumb
1760 karbon
1761 comix
1762 mirage
1763 viewnior
1764 postr
1765 ristretto
1766 kolourpaint4
1767 eog
1768 eom
1769 gimagereader
1770 midori
1771 %
1772 &lt;/pre&gt;&lt;/blockquote&gt;
1773
1774 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
1775 packages providing appstream metadata.&lt;/p&gt;
1776 </description>
1777 </item>
1778
1779 <item>
1780 <title>Creepy, visualise geotagged social media information - nice free software</title>
1781 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
1782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
1783 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
1784 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
1785 with the computerised radio beacon known as a mobile phone their
1786 position is tracked by the phone company and often stored for a long
1787 time (like every time a SMS is received or sent). And if their
1788 computerised radio beacon is capable of running programs (often called
1789 mobile apps) downloaded from the Internet, these programs are often
1790 also capable of tracking their location (if the app requested access
1791 during installation). And when these programs send out information to
1792 central collection points, the location is often included, unless
1793 extra care is taken to not send the location. The provided
1794 information is used by several entities, for good and bad (what is
1795 good and bad, depend on your point of view). What is certain, is that
1796 the private sphere and the right to free movement is challenged and
1797 perhaps even eradicated for those announcing their location this way,
1798 when they share their whereabouts with private and public
1799 entities.&lt;/p&gt;
1800
1801 &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;
1802
1803 &lt;p&gt;The phone company logs provide a register of locations to check out
1804 when one want to figure out what the tracked person was doing. It is
1805 unavailable for most of us, but provided to selected government
1806 officials, company staff, those illegally buying information from
1807 unfaithful servants and crackers stealing the information. But the
1808 public information can be collected and analysed, and a free software
1809 tool to do so is called
1810 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
1811 discovered it when I read
1812 &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
1813 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
1814 November 2014, and decided to check if it was available in Debian.
1815 The python program was in Debian, but
1816 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
1817 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
1818 uploaded a new version which did not work quite right, but did not
1819 have time to fix it then. This Christmas I decided to finally try to
1820 get Creepy operational in Debian. Now a fixed version is available in
1821 Debian unstable and testing, and almost all Debian specific patches
1822 are now included
1823 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
1824
1825 &lt;p&gt;The Creepy program visualises geolocation information fetched from
1826 Twitter, Instagram, Flickr and Google+, and allow one to get a
1827 complete picture of every social media message posted recently in a
1828 given area, or track the movement of a given individual across all
1829 these services. Earlier it was possible to use the search API of at
1830 least some of these services without identifying oneself, but these
1831 days it is impossible. This mean that to use Creepy, you need to
1832 configure it to log in as yourself on these services, and provide
1833 information to them about your search interests. This should be taken
1834 into account when using Creepy, as it will also share information
1835 about yourself with the services.&lt;/p&gt;
1836
1837 &lt;p&gt;The picture above show the twitter messages sent from (or at least
1838 geotagged with a position from) the city centre of Oslo, the capital
1839 of Norway. One useful way to use Creepy is to first look at
1840 information tagged with an area of interest, and next look at all the
1841 information provided by one or more individuals who was in the area.
1842 I tested it by checking out which celebrity provide their location in
1843 twitter messages by checkout out who sent twitter messages near a
1844 Norwegian TV station, and next could track their position over time,
1845 making it possible to locate their home and work place, among other
1846 things. A similar technique have been
1847 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
1848 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
1849 tool to discover lying governments, and a useful tool to help people
1850 understand the value of the private information they provide to the
1851 public.&lt;/p&gt;
1852
1853 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
1854 it depend on several python modules currently missing in Jessie (at
1855 least python-instagram, python-flickrapi and
1856 python-requests-toolbelt).&lt;/p&gt;
1857
1858 &lt;p&gt;(I have uploaded
1859 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
1860 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
1861 Creepy program in Debian.)&lt;/p&gt;
1862 </description>
1863 </item>
1864
1865 <item>
1866 <title>Always download Debian packages using Tor - the simple recipe</title>
1867 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
1868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
1869 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
1870 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
1871 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
1872 that those listening on the Internet lines would have good reason to
1873 believe a computer have a given security hole&lt;/a&gt; if it download a
1874 security fix from a Debian mirror. This is a good reason to always
1875 use encrypted connections to the Debian mirror, to make sure those
1876 listening do not know which IP address to attack. In August, Richard
1877 Hartmann observed that encryption was not enough, when it was possible
1878 to interfere download size to security patches or the fact that
1879 download took place shortly after a security fix was released, and
1880 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
1881 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
1882 was not the first to propose this, as the
1883 &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;
1884 package by Tim Retout already existed to make it easy to convince apt
1885 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
1886 aware of that package when I read the blog post from Richard.&lt;/p&gt;
1887
1888 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
1889 sysadmins, and he set up a Tor hidden service on one of the central
1890 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1891 it possible to download packages directly between two tor nodes,
1892 making sure the network traffic always were encrypted.&lt;/p&gt;
1893
1894 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
1895 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
1896 urls with tor+http and tor+https, and using the hidden service instead
1897 of the official Debian mirror site. I recommend installing
1898 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
1899 done in /etc/.&lt;/p&gt;
1900
1901 &lt;blockquote&gt;&lt;pre&gt;
1902 apt install apt-transport-tor
1903 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
1904 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
1905 &lt;/pre&gt;&lt;/blockquote&gt;
1906
1907 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
1908 the sed commands for these too. The sed command is assuming your are
1909 using the ftp.debian.org Debian mirror. Adjust the command (or just
1910 edit the file manually) to match your mirror.&lt;/p&gt;
1911
1912 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
1913 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
1914 system, and do not work with these tor+http URLs. For
1915 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
1916 which need a recent apt version currently only in unstable. So if you
1917 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
1918
1919 &lt;p&gt;Another advantage from this change is that your machine will start
1920 using Tor regularly and at fairly random intervals (every time you
1921 update the package lists or upgrade or install a new package), thus
1922 masking other Tor traffic done from the same machine. Using Tor will
1923 become normal for the machine in question.&lt;/p&gt;
1924
1925 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
1926 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
1927 enabled. It would be great if it was the default on any Debian
1928 system.&lt;/p&gt;
1929 </description>
1930 </item>
1931
1932 <item>
1933 <title>OpenALPR, find car license plates in video streams - nice free software</title>
1934 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
1935 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
1936 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
1937 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
1938 call the car license plate numbers in those days. I would write the
1939 numbers down in my little book and compare notes with the other kids
1940 to see how many region codes we had seen and if we had seen some
1941 exotic or special region codes and numbers. It was a fun game to pass
1942 time, as we kids have plenty of it.&lt;/p&gt;
1943
1944 &lt;p&gt;A few days I came across
1945 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
1946 project&lt;/a&gt;, a free software project to automatically discover and
1947 report license plates in images and video streams, and provide the
1948 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
1949 such system for a while now, because I believe it is a bad idea that the
1950 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
1951 number plate recognition&lt;/a&gt; tool only is available in the hands of
1952 the powerful, and want it to be available also for the powerless to
1953 even the score when it comes to surveillance and sousveillance. I
1954 discovered the developer
1955 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
1956 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
1957 help him get it into shape to get the package uploaded into the Debian
1958 archive.&lt;/p&gt;
1959
1960 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
1961 it into Debian, where it currently
1962 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
1963 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
1964
1965 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
1966 for the common folks, ie those not running a large government
1967 surveillance system? Well, I plan to put it in a computer on my bike
1968 and in my car, tracking the cars nearby and allowing me to be notified
1969 when number plates on my watch list are discovered. Another use case
1970 was suggested by a friend of mine, who wanted to set it up at his home
1971 to open the car port automatically when it discovered the plate on his
1972 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1973 capable of placing his license plate number of a piece of cardboard to
1974 open his car port, men replied that it was always unlocked anyway. I
1975 guess for such use case it make sense. I am sure there are other use
1976 cases too, for those with imagination and a vision.&lt;/p&gt;
1977
1978 &lt;p&gt;If you want to build your own version of the Debian package, check
1979 out the upstream git source and symlink ./distros/debian to ./debian/
1980 before running &quot;debuild&quot; to build the source. Or wait a bit until the
1981 package show up in unstable.&lt;/p&gt;
1982 </description>
1983 </item>
1984
1985 <item>
1986 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
1987 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
1988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
1989 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
1990 <description>&lt;p&gt;Around three years ago, I created
1991 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
1992 system&lt;/a&gt; to get a more practical solution in Debian for handing
1993 hardware related packages. A GUI system in the isenkram package will
1994 present a pop-up dialog when some hardware dongle supported by
1995 relevant packages in Debian is inserted into the machine. The same
1996 lookup mechanism to detect packages is available as command line
1997 tools in the isenkram-cli package. In addition to mapping hardware,
1998 it will also map kernel firmware files to packages and make it easy to
1999 install needed firmware packages automatically. The key for this
2000 system to work is a good way to map hardware to packages, in other
2001 words, allow packages to announce what hardware they will work
2002 with.&lt;/p&gt;
2003
2004 &lt;p&gt;I started by providing data files in the isenkram source, and
2005 adding code to download the latest version of these data files at run
2006 time, to ensure every user had the most up to date mapping available.
2007 I also added support for storing the mapping in the Packages file in
2008 the apt repositories, but did not push this approach because while I
2009 was trying to figure out how to best store hardware/package mappings,
2010 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2011 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
2012 add the hardware mapping into that data set to be able to use
2013 appstream as a data source, and this was accepted at least for the
2014 Debian version of appstream.&lt;/p&gt;
2015
2016 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
2017 and today I uploaded a new version 0.20 of isenkram adding support for
2018 appstream as a data source for mapping hardware to packages. The only
2019 package so far using appstream to announce its hardware support is my
2020 pymissile package. I got help from Matthias Klumpp with figuring out
2021 how do add the required
2022 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
2023 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
2024 this content:&lt;/p&gt;
2025
2026 &lt;blockquote&gt;&lt;pre&gt;
2027 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2028 &amp;lt;component&amp;gt;
2029 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
2030 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
2031 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
2032 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
2033 &amp;lt;description&amp;gt;
2034 &amp;lt;p&amp;gt;
2035 Pymissile provides a curses interface to control an original
2036 Marks and Spencer / Striker USB Missile Launcher, as well as a
2037 motion control script to allow a webcamera to control the
2038 launcher.
2039 &amp;lt;/p&amp;gt;
2040 &amp;lt;/description&amp;gt;
2041 &amp;lt;provides&amp;gt;
2042 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
2043 &amp;lt;/provides&amp;gt;
2044 &amp;lt;/component&amp;gt;
2045 &lt;/pre&gt;&lt;/blockquote&gt;
2046
2047 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
2048 which is a glob style match rule for hardware specific strings
2049 (modalias strings) provided by the Linux kernel. In this case, it
2050 will map to all USB devices with vendor code 1130 and product code
2051 0202.&lt;/p&gt;
2052
2053 &lt;p&gt;Note, it is important that the license of all the metadata files
2054 are compatible to have permissions to aggregate them into archive wide
2055 appstream files. Matthias suggested to use MIT or BSD licenses for
2056 these files. A challenge is figuring out a good id for the data, as
2057 it is supposed to be globally unique and shared across distributions
2058 (in other words, best to coordinate with upstream what to use). But
2059 it can be changed later or, so we went with the package name as
2060 upstream for this project is dormant.&lt;/p&gt;
2061
2062 &lt;p&gt;To get the metadata file installed in the correct location for the
2063 mirror update scripts to pick it up and include its content the
2064 appstream data source, the file must be installed in the binary
2065 package under /usr/share/appdata/. I did this by adding the following
2066 line to debian/pymissile.install:&lt;/p&gt;
2067
2068 &lt;blockquote&gt;&lt;pre&gt;
2069 debian/pymissile.metainfo.xml usr/share/appdata
2070 &lt;/pre&gt;&lt;/blockquote&gt;
2071
2072 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
2073 all packages useful on the current computer automatically, and the GUI
2074 pop-up handler will propose to install the package not already
2075 installed if a hardware dongle is inserted into the machine in
2076 question.&lt;/p&gt;
2077
2078 &lt;p&gt;Details of the modalias field in appstream is available from the
2079 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
2080
2081 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
2082 try running this command on the command line:&lt;/p&gt;
2083
2084 &lt;blockquote&gt;&lt;pre&gt;
2085 cat $(find /sys/devices/|grep modalias)
2086 &lt;/pre&gt;&lt;/blockquote&gt;
2087
2088 &lt;p&gt;To learn more about the isenkram system, please check out
2089 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2090 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2091 </description>
2092 </item>
2093
2094 <item>
2095 <title>The GNU General Public License is not magic pixie dust</title>
2096 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2098 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2099 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2100 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2101 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2102 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2103 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2104
2105 &lt;blockquote&gt;
2106
2107 &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;
2108
2109 &lt;blockquote&gt;
2110 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2111
2112 The first step is to choose a
2113 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2114 code.&lt;br/&gt;
2115
2116 The next step is, when someone fails to follow that copyleft license,
2117 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2118
2119 and its a simple fact of our modern society that such type of
2120 work&lt;br/&gt;
2121
2122 is incredibly expensive to do and incredibly difficult to do.
2123 &lt;/blockquote&gt;
2124
2125 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2126 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2127 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2128 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2129
2130 &lt;p&gt;As the Debian Website
2131 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2132 &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;
2133 imply, public domain and permissively licensed software can lead to
2134 the production of more proprietary software as people discover useful
2135 software, extend it and or incorporate it into their hardware or
2136 software products. Copyleft licenses such as the GNU GPL were created
2137 to close off this avenue to the production of proprietary software but
2138 such licenses are not enough. With the ongoing adoption of Free
2139 Software by individuals and groups, inevitably the community&#39;s
2140 expectations of license compliance are violated, usually out of
2141 ignorance of the way Free Software works, but not always. As Karen
2142 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2143 Freedom&quot;&gt;FaiF&lt;/a&gt;
2144 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2145 copyleft is nothing if no-one is willing and able to stand up in court
2146 to protect it. The reality of today&#39;s world is that legal
2147 representation is expensive, difficult and time consuming. With
2148 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2149 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2150 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2151 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2152 of the Linux project, Debian and other groups against GPL violations.
2153 In March the SFC supported a
2154 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2155 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2156 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2157 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2158 kernel. Since then two of their sponsors pulled corporate funding and
2159 conferences
2160 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2161 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2162 less on corporate funding and more on the broad community of
2163 individuals who support Free Software and copyleft. So the SFC has
2164 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2165 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2166 a community of folks who stand up for copyleft and the GPL by
2167 supporting their work on promoting and supporting copyleft and Free
2168 Software.&lt;/p&gt;
2169
2170 &lt;p&gt;If you support Free Software,
2171 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2172 what the SFC do, agree with their
2173 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2174 principles&lt;/a&gt;, are happy about their
2175 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2176 work on a project that is an SFC
2177 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2178 just want to stand up for copyleft, please join
2179 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2180 Allan Webber&lt;/a&gt;,
2181 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2182 Smith&lt;/a&gt;,
2183 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2184 Bacon&lt;/a&gt;, myself and
2185 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2186 becoming a
2187 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2188 next week your donation will be
2189 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2190 by an anonymous donor. Please also consider asking your employer to
2191 match your donation or become a sponsor of SFC. Don&#39;t forget to
2192 spread the word about your support for SFC via email, your blog and or
2193 social media accounts.&lt;/p&gt;
2194
2195 &lt;/blockquote&gt;
2196
2197 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
2198 of Software Freedom Conservancy myself. Perhaps you should be a
2199 supporter too?&lt;/p&gt;
2200 </description>
2201 </item>
2202
2203 <item>
2204 <title>PGP key transition statement for key EE4E02F9</title>
2205 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
2206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
2207 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
2208 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
2209 set it up properly. I wanted to generate it offline and have it
2210 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
2211 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
2212 time to sit down with an offline machine almost took forever. But
2213 finally I&#39;ve been able to complete the process, and have now moved
2214 from my old GPG key to a new GPG key. See
2215 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
2216 full transition statement, signed with both my old and new key&lt;/a&gt; for
2217 the details. This is my new key:&lt;/p&gt;
2218
2219 &lt;pre&gt;
2220 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]
2221 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
2222 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
2223 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
2224 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
2225 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
2226 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
2227 &lt;/pre&gt;
2228
2229 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
2230 my old key.&lt;/p&gt;
2231
2232 &lt;p&gt;If you signed my old key
2233 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
2234 I&#39;d very much appreciate a signature on my new key, details and
2235 instructions in the transition statement. I m happy to reciprocate if
2236 you have a similarly signed transition statement to present.&lt;/p&gt;
2237 </description>
2238 </item>
2239
2240 <item>
2241 <title>The life and death of a laptop battery</title>
2242 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
2243 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
2244 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
2245 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
2246 But this do not last. The last few laptops gave me a feeling that
2247 within a year, the life time is just a fraction of what it used to be,
2248 and it slowly become painful to use the laptop without power connected
2249 all the time. Because of this, when I got a new Thinkpad X230 laptop
2250 about two years ago, I decided to monitor its battery state to have
2251 more hard facts when the battery started to fail.&lt;/p&gt;
2252
2253 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
2254
2255 &lt;p&gt;First I tried to find a sensible Debian package to record the
2256 battery status, assuming that this must be a problem already handled
2257 by someone else. I found
2258 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
2259 which collects statistics from the battery, but it was completely
2260 broken. I sent a few suggestions to the maintainer, but decided to
2261 write my own collector as a shell script while I waited for feedback
2262 from him. Via
2263 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
2264 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
2265 discovered
2266 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
2267 available in Debian.&lt;/p&gt;
2268
2269 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
2270 battery stats ever since. Now my
2271 /var/log/hjemmenett-battery-status.log file contain around 115,000
2272 measurements, from the time the battery was working great until now,
2273 when it is unable to charge above 7% of original capacity. My
2274 collector shell script is quite simple and look like this:&lt;/p&gt;
2275
2276 &lt;pre&gt;
2277 #!/bin/sh
2278 # Inspired by
2279 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
2280 # See also
2281 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
2282 logfile=/var/log/hjemmenett-battery-status.log
2283
2284 files=&quot;manufacturer model_name technology serial_number \
2285 energy_full energy_full_design energy_now cycle_count status&quot;
2286
2287 if [ ! -e &quot;$logfile&quot; ] ; then
2288 (
2289 printf &quot;timestamp,&quot;
2290 for f in $files; do
2291 printf &quot;%s,&quot; $f
2292 done
2293 echo
2294 ) &gt; &quot;$logfile&quot;
2295 fi
2296
2297 log_battery() {
2298 # Print complete message in one echo call, to avoid race condition
2299 # when several log processes run in parallel.
2300 msg=$(printf &quot;%s,&quot; $(date +%s); \
2301 for f in $files; do \
2302 printf &quot;%s,&quot; $(cat $f); \
2303 done)
2304 echo &quot;$msg&quot;
2305 }
2306
2307 cd /sys/class/power_supply
2308
2309 for bat in BAT*; do
2310 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
2311 done
2312 &lt;/pre&gt;
2313
2314 &lt;p&gt;The script is called when the power management system detect a
2315 change in the power status (power plug in or out), and when going into
2316 and out of hibernation and suspend. In addition, it collect a value
2317 every 10 minutes. This make it possible for me know when the battery
2318 is discharging, charging and how the maximum charge change over time.
2319 The code for the Debian package
2320 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
2321 available on github&lt;/a&gt;.&lt;/p&gt;
2322
2323 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
2324
2325 &lt;pre&gt;
2326 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2327 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
2328 [...]
2329 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2330 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2331 &lt;/pre&gt;
2332
2333 &lt;p&gt;I wrote a small script to create a graph of the charge development
2334 over time. This graph depicted above show the slow death of my laptop
2335 battery.&lt;/p&gt;
2336
2337 &lt;p&gt;But why is this happening? Why are my laptop batteries always
2338 dying in a year or two, while the batteries of space probes and
2339 satellites keep working year after year. If we are to believe
2340 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
2341 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
2342 chance, and the fix is to not charge the Lithium-ion batteries to 100%
2343 all the time, but to stay below 90% of full charge most of the time.
2344 I&#39;ve been told that the Tesla electric cars
2345 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
2346 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
2347 100% when preparing for a longer trip (not that I would want a car
2348 like Tesla where rights to privacy is abandoned, but that is another
2349 story), which I guess is the option we should have for laptops on
2350 Linux too.&lt;/p&gt;
2351
2352 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
2353 stop charging at 80%, unless requested to charge to 100% once in
2354 preparation for a longer trip? I found
2355 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
2356 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2357 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
2358 load).&lt;/p&gt;
2359
2360 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
2361 at the start. I also wonder why the &quot;full capacity&quot; increases some
2362 times, and if it is possible to repeat the process to get the battery
2363 back to design capacity. And I wonder if the discharge and charge
2364 speed change over time, or if this stay the same. I did not yet try
2365 to write a tool to calculate the derivative values of the battery
2366 level, but suspect some interesting insights might be learned from
2367 those.&lt;/p&gt;
2368
2369 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
2370 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2371 packages instead of the tp-smapi-dkms package I had tried to use
2372 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
2373 and stop. I&#39;ve done so now, but expect my existing battery is toast
2374 and need to be replaced. The proposal is unfortunately Thinkpad
2375 specific.&lt;/p&gt;
2376 </description>
2377 </item>
2378
2379 <item>
2380 <title>New laptop - some more clues and ideas based on feedback</title>
2381 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
2382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
2383 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
2384 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
2385 need for a new laptop, and provided very useful feedback. I wish to
2386 thank every one of these. Several pointed me to the possibility of
2387 fixing my X230, and I am already in the process of getting Lenovo to
2388 do so thanks to the on site, next day support contract covering the
2389 machine. But the battery is almost useless (I expect to replace it
2390 with a non-official battery) and I do not expect the machine to live
2391 for many more years, so it is time to plan its replacement. If I did
2392 not have a support contract, it was suggested to find replacement parts
2393 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2394 might present a language barrier as I do not understand French.&lt;/p&gt;
2395
2396 &lt;p&gt;One tip I got was to use the
2397 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2398 compare laptop models. It seem to have more models available than
2399 prisjakt.no. Another tip I got from someone I know have similar
2400 keyboard preferences was that the HP EliteBook 840 keyboard is not
2401 very good, and this matches my experience with earlier EliteBook
2402 keyboards I tested. Because of this, I will not consider it any further.
2403
2404 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2405 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2406 (which is missing from the X240), and is working fairly well with
2407 Debian Sid/Unstable according to
2408 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2409 got on the keyboard quality are not consistent. Some say the keyboard
2410 is good, others say it is ok, while others say it is not very good.
2411 Those with experience from X41 and and X60 agree that the X250
2412 keyboard is not as good as those trusty old laptops, and suggest I
2413 keep and fix my X230 instead of upgrading, or get a used X230 to
2414 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2415 activity and battery status, which is very convenient on my X230. I&#39;m
2416 also told that the CPU fan is running very often, making it a bit
2417 noisy. In any case, the X250 do not work out of the box with Debian
2418 Stable/Jessie, one of my requirements.&lt;/p&gt;
2419
2420 &lt;p&gt;I have also gotten a few vendor proposals, one was
2421 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2422 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2423 The latter look very attractive to me.&lt;/p&gt;
2424
2425 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2426 as I keep looking for a replacement.&lt;/p&gt;
2427
2428 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2429 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2430 different
2431 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2432 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2433 </description>
2434 </item>
2435
2436 <item>
2437 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2438 <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>
2439 <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>
2440 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2441 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2442 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2443 started flickering yesterday, and I suspect the cause is a broken
2444 cable, as changing the angle of the screen some times get rid of the
2445 flickering.&lt;/p&gt;
2446
2447 &lt;p&gt;My requirements have not really changed since I bought it, and is
2448 still as
2449 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2450 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2451 good help from
2452 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2453 where I could select at least a few of the requirements (mouse pin,
2454 wifi, weight) and go through the rest manually. Three button mouse
2455 and a good keyboard is not available as an option, and all the three
2456 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2457 G2) lack three mouse buttons). It is also unclear to me how good the
2458 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2459 the keyboard, even if the quality and robustness in the X series have
2460 deteriorated since X41.&lt;/p&gt;
2461
2462 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2463 seem sensible to me? Are there better services around to search the
2464 set of available laptops for features? Please send me an email if you
2465 have suggestions.&lt;/p&gt;
2466
2467 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2468 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2469 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2470 </description>
2471 </item>
2472
2473 <item>
2474 <title>How to stay with sysvinit in Debian Jessie</title>
2475 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2477 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2478 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2479 sysvinit as its boot system by default. But how can one keep using
2480 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2481 courtesy of
2482 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2483 Schubert&lt;/a&gt; and
2484 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2485 McVittie&lt;/a&gt;.
2486
2487 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2488 keep sysvinit as your boot system, create a file
2489 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2490 you upgrade:&lt;/p&gt;
2491
2492 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2493 Package: systemd-sysv
2494 Pin: release o=Debian
2495 Pin-Priority: -1
2496 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2497
2498 &lt;p&gt;This file content will tell apt and aptitude to not consider
2499 installing systemd-sysv as part of any installation and upgrade
2500 solution when resolving dependencies, and thus tell it to avoid
2501 systemd as a default boot system. The end result should be that the
2502 upgraded system keep using sysvinit.&lt;/p&gt;
2503
2504 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2505 get sysvinit installed by default (debootstrap used by
2506 debian-installer have no option for this), but one can tell the
2507 installer to switch to sysvinit before the first boot. Either by
2508 using a kernel argument to the installer, or by adding a line to the
2509 preseed file used. First, the kernel command line argument:
2510
2511 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2512 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2513 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2514
2515 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2516
2517 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2518 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2519 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2520
2521 &lt;p&gt;One can of course also do this after the first boot by installing
2522 the sysvinit-core package.&lt;/p&gt;
2523
2524 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2525 sysvinit boot sequence in Debian have several hardware specific bugs
2526 on Linux caused by the fact that it is unpredictable when hardware
2527 devices show up during boot. But on the other hand, the new default
2528 boot system still have a few rough edges I hope will be fixed before
2529 Jessie is released.&lt;/p&gt;
2530
2531 &lt;p&gt;Update 2014-11-26: Inspired by
2532 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2533 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2534 line.&lt;/p&gt;
2535 </description>
2536 </item>
2537
2538 <item>
2539 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2540 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2541 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2542 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2543 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2544 without anyone snooping, is a right every citicen have in a liberal
2545 democracy. But this right is under serious attack these days.&lt;/p&gt;
2546
2547 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2548 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2549 the whisleblower Snowden) more expensive for Internet email,
2550 is to deliver all email using SMTP via Tor. Such SMTP option would be
2551 a nice addition to the FreedomBox project if we could send email
2552 between FreedomBox machines without leaking metadata about the emails
2553 to the people peeking on the wire. I
2554 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2555 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2556 lot of useful feedback and suggestions. It also became obvious to me
2557 that this was not a novel idea, as the same idea was tested and
2558 documented by Johannes Berg as early as 2006, and both
2559 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2560 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2561 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2562
2563 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2564 providing the SMTP protocol on port 25, and use email addresses
2565 looking like username@hidden-service-name.onion. With such addresses
2566 the connections to port 25 on hidden-service-name.onion using Tor will
2567 go to the correct SMTP server. To do this, one need to configure the
2568 Tor daemon to provide the hidden service and the mail server to accept
2569 emails for this .onion domain. To learn more about Exim configuration
2570 in Debian and test the design provided by Johannes Berg in his FAQ, I
2571 set out yesterday to create a Debian package for making it trivial to
2572 set up such SMTP over Tor service based on Debian. Getting it to work
2573 were fairly easy, and
2574 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2575 source code for the Debian package&lt;/a&gt; is available from github. I
2576 plan to move it into Debian if further testing prove this to be a
2577 useful approach.&lt;/p&gt;
2578
2579 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2580 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2581 get rid of exim4). Install tor, clone the git repository mentioned
2582 above, build the deb and install it on the machine. Next, run
2583 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2584 the instructions to get the service up and running. Restart tor and
2585 exim when it is done, and test mail delivery using swaks like
2586 this:&lt;/p&gt;
2587
2588 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2589 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2590 --to fbx@dutlqrrmjhtfa3vp.onion
2591 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2592
2593 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2594 address with your own address to test your server. :)&lt;/p&gt;
2595
2596 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2597 easier and more automatic. Especially the tor setup need more work.
2598 Also, the package include a tor-smtp tool written in C, but its task
2599 should probably be rewritten in some script language to make the deb
2600 architecture independent. It would probably also make the code easier
2601 to review. The tor-smtp tool currently need to listen on a socket for
2602 exim to talk to it and is started using xinetd. It would be better if
2603 no daemon and no socket is needed. I suspect it is possible to get
2604 exim to run a command line tool for delivery instead of talking to a
2605 socket, and hope to figure out how in a future version of this
2606 system.&lt;/p&gt;
2607
2608 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2609 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2610 SMTorP. :)&lt;/p&gt;
2611 </description>
2612 </item>
2613
2614 <item>
2615 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2616 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2617 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2618 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2619 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2620 alioth.debian.org, you know the web interface is fairly slow to
2621 operate. First you visit one web page, enter the moderation password
2622 and get a new page shown with a list of all the messages to moderate
2623 and various options for each email address. This take a while for
2624 every list you moderate, and you need to do it regularly to do a good
2625 job as a list moderator. But there is a quick alternative,
2626 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
2627 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
2628 to moderate in a fraction of a second. Here is a test run on two
2629 lists I recently took over:&lt;/p&gt;
2630
2631 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2632 % time listadmin xiph
2633 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2634 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2635
2636 real 0m1.709s
2637 user 0m0.232s
2638 sys 0m0.012s
2639 %
2640 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2641
2642 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
2643 there are no message in the moderation queue. Every morning I
2644 currently moderate 68 mailman lists, and it normally take around two
2645 minutes. When I took over the two pkg-xiph lists above a few days
2646 ago, there were 400 emails waiting in the moderator queue. It took me
2647 less than 15 minutes to process them all using the listadmin
2648 program.&lt;/p&gt;
2649
2650 &lt;p&gt;If you install
2651 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
2652 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
2653 with content like this, the moderation task is a breeze:&lt;/p&gt;
2654
2655 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2656 username username@example.org
2657 spamlevel 23
2658 default discard
2659 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
2660
2661 password secret
2662 adminurl https://{domain}/mailman/admindb/{list}
2663 mailman-list@lists.example.com
2664
2665 password hidden
2666 other-list@otherserver.example.org
2667 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2668
2669 &lt;p&gt;There are other options to set as well. Check the manual page to
2670 learn the details.&lt;/p&gt;
2671
2672 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
2673 the SSL certificate is self signed or not properly signed by a
2674 generally accepted signing authority, you can set a environment
2675 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
2676
2677 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2678 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
2679 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2680
2681 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
2682 can provide an argument to the listadmin script like I do in the
2683 initial screen dump (the xiph argument). Using an argument, only
2684 lists matching the argument string will be processed. This make it
2685 quick to accept messages if you notice the moderation request in your
2686 email.&lt;/p&gt;
2687
2688 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
2689 mailing lists, as I simply do not have time to spend on that if the
2690 process was any slower. The listadmin program have saved me hours of
2691 time I could spend elsewhere over the years. It truly is nice free
2692 software.&lt;/p&gt;
2693
2694 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2695 activities, please send Bitcoin donations to my address
2696 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2697
2698 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
2699 configuration example. Also, I&#39;ve been told that the
2700 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
2701 sure why.&lt;/p&gt;
2702 </description>
2703 </item>
2704
2705 <item>
2706 <title>Debian Jessie, PXE and automatic firmware installation</title>
2707 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
2708 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
2709 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
2710 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
2711 problem that the WiFi card require some firmware to work properly.
2712 And it has been a pain to fix this using preseeding in Debian.
2713 Normally something more is needed. But thanks to
2714 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
2715 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
2716 to do this using simple preseeding.&lt;/p&gt;
2717
2718 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
2719 firmware for the hardware found in the machine (actually, requested by
2720 the kernel modules for the hardware). (It can also install user space
2721 programs supporting the hardware detected, but that is not the focus
2722 of this story.)&lt;/p&gt;
2723
2724 &lt;p&gt;To get this working in the default installation, two preeseding
2725 values are needed. First, the isenkram-cli package must be installed
2726 into the target chroot (aka the hard drive) before tasksel is executed
2727 in the pkgsel step of the debian-installer system. This is done by
2728 preseeding the base-installer/includes debconf value to include the
2729 isenkram-cli package. The package name is next passed to debootstrap
2730 for installation. With the isenkram-cli package in place, tasksel
2731 will automatically use the isenkram tasks to detect hardware specific
2732 packages for the machine being installed and install them, because
2733 isenkram-cli contain tasksel tasks.&lt;/p&gt;
2734
2735 &lt;p&gt;Second, one need to enable the non-free APT repository, because
2736 most firmware unfortunately is non-free. This is done by preseeding
2737 the apt-mirror-setup step. This is unfortunate, but for a lot of
2738 hardware it is the only option in Debian.&lt;/p&gt;
2739
2740 &lt;p&gt;The end result is two lines needed in your preseeding file to get
2741 firmware installed automatically by the installer:&lt;/p&gt;
2742
2743 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2744 base-installer base-installer/includes string isenkram-cli
2745 apt-mirror-setup apt-setup/non-free boolean true
2746 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2747
2748 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
2749 both firmware and user space packages when using this method. It also
2750 do not work well, so use version 0.15 or later. Installing both
2751 firmware and user space packages might give you a bit more than you
2752 want, so I decided to split the tasksel task in two, one for firmware
2753 and one for user space programs. The firmware task is enabled by
2754 default, while the one for user space programs is not. This split is
2755 implemented in the package currently in unstable.&lt;/p&gt;
2756
2757 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
2758 this recipe work for you. :)&lt;/p&gt;
2759
2760 &lt;p&gt;So, I bet you are wondering, how can this work. First and
2761 foremost, it work because tasksel is modular, and driven by whatever
2762 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2763 isenkram-cli package place two files for tasksel to find. First there
2764 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
2765
2766 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2767 Task: isenkram-packages
2768 Section: hardware
2769 Description: Hardware specific packages (autodetected by isenkram)
2770 Based on the detected hardware various hardware specific packages are
2771 proposed.
2772 Test-new-install: show show
2773 Relevance: 8
2774 Packages: for-current-hardware
2775
2776 Task: isenkram-firmware
2777 Section: hardware
2778 Description: Hardware specific firmware packages (autodetected by isenkram)
2779 Based on the detected hardware various hardware specific firmware
2780 packages are proposed.
2781 Test-new-install: mark show
2782 Relevance: 8
2783 Packages: for-current-hardware-firmware
2784 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2785
2786 &lt;p&gt;The key parts are Test-new-install which indicate how the task
2787 should be handled and the Packages line referencing to a script in
2788 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2789 list of packages to install. The for-current-hardware-firmware script
2790 look like this to list relevant firmware for the machine:
2791
2792 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2793 #!/bin/sh
2794 #
2795 PATH=/usr/sbin:$PATH
2796 export PATH
2797 isenkram-autoinstall-firmware -l
2798 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2799
2800 &lt;p&gt;With those two pieces in place, the firmware is installed by
2801 tasksel during the normal d-i run. :)&lt;/p&gt;
2802
2803 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
2804 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
2805 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
2806 install.&lt;/p&gt;
2807
2808 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
2809 pilots in testing this feature, as isenkram is used there now to
2810 install firmware, replacing the earlier scripts.&lt;/p&gt;
2811 </description>
2812 </item>
2813
2814 <item>
2815 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
2816 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
2817 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
2818 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
2819 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
2820 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2821 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
2822 on a screen normally showing the bread types and prizes:&lt;/p&gt;
2823
2824 &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;
2825
2826 &lt;p&gt;If it had booted as it was supposed to, I would never had known
2827 about this hidden Linux installation. It is interesting what
2828 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
2829 </description>
2830 </item>
2831
2832 <item>
2833 <title>New lsdvd release version 0.17 is ready</title>
2834 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
2835 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
2836 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
2837 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
2838 got a new set of developers a few weeks ago, after the original
2839 developer decided to step down and pass the project to fresh blood.
2840 This project is now maintained by Petter Reinholdtsen and Steve
2841 Dibb.&lt;/p&gt;
2842
2843 &lt;p&gt;I just wrapped up
2844 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
2845 new lsdvd release&lt;/a&gt;, available in git or from
2846 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
2847 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
2848 0.17.&lt;/p&gt;
2849
2850 &lt;ul&gt;
2851
2852 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
2853 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
2854 non-existant, to work around additional copy protection&lt;/li&gt;
2855 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
2856 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
2857 &lt;li&gt;Fix include orders&lt;/li&gt;
2858 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
2859 &lt;li&gt;Fix the chapter count&lt;/li&gt;
2860 &lt;li&gt;Make sure the array size and the array limit used when initialising
2861 the palette size is the same.&lt;/li&gt;
2862 &lt;li&gt;Fix array printing.&lt;/li&gt;
2863 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
2864 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
2865 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
2866 with more GCC compiler warnings.&lt;/li&gt;
2867
2868 &lt;/ul&gt;
2869
2870 &lt;p&gt;This change bring together patches for lsdvd in use in various
2871 Linux and Unix distributions, as well as patches submitted to the
2872 project the last nine years. Please check it out. :)&lt;/p&gt;
2873 </description>
2874 </item>
2875
2876 <item>
2877 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
2878 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
2879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
2880 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
2881 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2882 project&lt;/a&gt; provide a Linux solution for schools, including a
2883 powerful desktop with education software, a central server providing
2884 web pages, user database, user home directories, central login and PXE
2885 boot of both clients without disk and the installation to install Debian
2886 Edu on machines with disk (and a few other services perhaps to small
2887 to mention here). We in the Debian Edu team are currently working on
2888 the Jessie based version, trying to get everything in shape before the
2889 freeze, to avoid having to maintain our own package repository in the
2890 future. The
2891 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
2892 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
2893 work left. Some fatal problems block testing, breaking the installer,
2894 but it is possible to work around these to get anyway. Here is a
2895 recipe on how to get the installation limping along.&lt;/p&gt;
2896
2897 &lt;p&gt;First, download the test ISO via
2898 &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;,
2899 &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;
2900 or rsync (use
2901 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
2902 The ISO build was broken on Tuesday, so we do not get a new ISO every
2903 12 hours or so, but thankfully the ISO we already got we are able to
2904 install with some tweaking.&lt;/p&gt;
2905
2906 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
2907 (use Alt-Ctrl-F2), run&lt;/p&gt;
2908
2909 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2910 nano /usr/bin/edu-eatmydata-install
2911 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2912
2913 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
2914 optimization. Return to the installation, select the profile you want
2915 and continue. Without this change, exim4-config will fail to install
2916 due to a known bug in eatmydata.&lt;/p&gt;
2917
2918 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
2919 this do not work, figure out what your correct value would be. All my
2920 test machines need /dev/sda, so I have no advice if it do not fit
2921 your need.&lt;/p&gt;
2922
2923 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
2924 root after the initial boot from hard drive, and install the
2925 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2926 or mate. If you want several desktop options, install more than one
2927 metapackage. Once this is done, reboot and you should have a working
2928 graphical login screen. This workaround should no longer be needed
2929 once the education-tasks package version 1.801 enter testing in two
2930 days.&lt;/p&gt;
2931
2932 &lt;p&gt;I believe the ISO build will start working on two days when the new
2933 tasksel package enter testing and Steve McIntyre get a chance to
2934 update the debian-cd git repository. The eatmydata, grub and desktop
2935 issues are already fixed in unstable and testing, and should show up
2936 on the ISO as soon as the ISO build start working again. Well the
2937 eatmydata optimization is really just disabled. The proper fix
2938 require an upload by the eatmydata maintainer applying the patch
2939 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
2940 The rest have proper fixes in unstable.&lt;/p&gt;
2941
2942 &lt;p&gt;I hope this get you going with the installation testing, as we are
2943 quickly running out of time trying to get our Jessie based
2944 installation ready before the distribution freeze in a month.&lt;/p&gt;
2945 </description>
2946 </item>
2947
2948 <item>
2949 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
2950 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
2951 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
2952 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
2953 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
2954 to handle my fairly large DVD collection. It is a nice command line
2955 tool to get details about a DVD, like title, tracks, track length,
2956 etc, in XML, Perl or human readable format. But lsdvd have not seen
2957 any new development since 2006 and had a few irritating bugs affecting
2958 its use with some DVDs. Upstream seemed to be dead, and in January I
2959 sent a small probe asking for a version control repository for the
2960 project, without any reply. But I use it regularly and would like to
2961 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
2962 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
2963 the project admin, and after getting a reply from him explaining that
2964 he was no longer interested in the project, I asked if I could take
2965 over. And yesterday, I became project admin.&lt;/p&gt;
2966
2967 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
2968 maintainer interested in joining forces to maintain the upstream
2969 project, and I hope we can get a new release out fairly quickly,
2970 collecting the patches spread around on the internet into on place.
2971 I&#39;ve added the relevant Debian patches to the freshly created git
2972 repository, and expect the Gentoo patches to make it too. If you got
2973 a DVD collection and care about command line tools, check out
2974 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
2975 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
2976 list&lt;/a&gt;. :)&lt;/p&gt;
2977 </description>
2978 </item>
2979
2980 <item>
2981 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
2982 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
2983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
2984 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
2985 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
2986 a lot quicker. When we install more than 2000 packages in
2987 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
2988 tasksel in the installer, unpacking the binary packages take forever.
2989 A part of the slow I/O issue was discussed in
2990 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
2991 much file system sync-ing done by dpkg, which is the package
2992 responsible for unpacking the binary packages. Other parts (like code
2993 executed by postinst scripts) might also sync to disk during
2994 installation. All this sync-ing to disk do not really make sense to
2995 me. If the machine crash half-way through, I start over, I do not try
2996 to salvage the half installed system. So the failure sync-ing is
2997 supposed to protect against, hardware or system crash, is not really
2998 relevant while the installer is running.&lt;/p&gt;
2999
3000 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
3001 system sync()-ing in a fairly non-intrusive way, without the need to
3002 change the code in several packages. The idea is not new, but I have
3003 not heard anyone propose the approach using dpkg-divert before. It
3004 depend on the small and clever package
3005 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
3006 uses LD_PRELOAD to replace the system functions for syncing data to
3007 disk with functions doing nothing, thus allowing programs to live
3008 dangerous while speeding up disk I/O significantly. Instead of
3009 modifying the implementation of dpkg, apt and tasksel (which are the
3010 packages responsible for selecting, fetching and installing packages),
3011 it occurred to me that we could just divert the programs away, replace
3012 them with a simple shell wrapper calling
3013 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
3014 Two days ago I decided to test the idea, and wrapped up a simple
3015 implementation for the Debian Edu udeb.&lt;/p&gt;
3016
3017 &lt;p&gt;The effect was stunning. In my first test it reduced the running
3018 time of the pkgsel step (installing tasks) from 64 to less than 44
3019 minutes (20 minutes shaved off the installation) on an old Dell
3020 Latitude D505 machine. I am not quite sure what the optimised time
3021 would have been, as I messed up the testing a bit, causing the debconf
3022 priority to get low enough for two questions to pop up during
3023 installation. As soon as I saw the questions I moved the installation
3024 along, but do not know how long the question were holding up the
3025 installation. I did some more measurements using Debian Edu Jessie,
3026 and got these results. The time measured is the time stamp in
3027 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
3028 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
3029 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3030 timing thus do not depend on how quickly the user handle the tasksel
3031 dialog.&lt;/p&gt;
3032
3033 &lt;p&gt;&lt;table&gt;
3034
3035 &lt;tr&gt;
3036 &lt;th&gt;Machine/setup&lt;/th&gt;
3037 &lt;th&gt;Original tasksel&lt;/th&gt;
3038 &lt;th&gt;Optimised tasksel&lt;/th&gt;
3039 &lt;th&gt;Reduction&lt;/th&gt;
3040 &lt;/tr&gt;
3041
3042 &lt;tr&gt;
3043 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
3044 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
3045 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
3046 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
3047 &lt;/tr&gt;
3048
3049 &lt;tr&gt;
3050 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
3051 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
3052 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
3053 &lt;td&gt;23 min 40%&lt;/td&gt;
3054 &lt;/tr&gt;
3055
3056 &lt;tr&gt;
3057 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
3058 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
3059 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
3060 &lt;td&gt;11 min 50%&lt;/td&gt;
3061 &lt;/tr&gt;
3062
3063 &lt;tr&gt;
3064 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
3065 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
3066 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
3067 &lt;td&gt;2 min 33%&lt;/td&gt;
3068 &lt;/tr&gt;
3069
3070 &lt;tr&gt;
3071 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
3072 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
3073 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
3074 &lt;td&gt;4 min 21%&lt;/td&gt;
3075 &lt;/tr&gt;
3076
3077 &lt;/table&gt;&lt;/p&gt;
3078
3079 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
3080 time is spent downloading packages. The connection to the Internet
3081 was 100Mbit/s during testing, so downloading should not be a
3082 significant factor in the measurement. Download typically took a few
3083 seconds to a few minutes, depending on the amount of packages being
3084 installed.&lt;/p&gt;
3085
3086 &lt;p&gt;The speedup is implemented by using two hooks in
3087 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3088 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3089 finish-install.d hook to remove the divert at the end of the
3090 installation. I picked the pre-pkgsel.d hook instead of the
3091 post-base-installer.d hook because I test using an ISO without the
3092 eatmydata package included, and the post-base-installer.d hook in
3093 Debian Edu can only operate on packages included in the ISO. The
3094 negative effect of this is that I am unable to activate this
3095 optimization for the kernel installation step in d-i. If the code is
3096 moved to the post-base-installer.d hook, the speedup would be larger
3097 for the entire installation.&lt;/p&gt;
3098
3099 &lt;p&gt;I&#39;ve implemented this in the
3100 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3101 git repository, and plan to provide the optimization as part of the
3102 Debian Edu installation. If you want to test this yourself, you can
3103 create two files in the installer (or in an udeb). One shell script
3104 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3105
3106 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3107 #!/bin/sh
3108 set -e
3109 . /usr/share/debconf/confmodule
3110 info() {
3111 logger -t my-pkgsel &quot;info: $*&quot;
3112 }
3113 error() {
3114 logger -t my-pkgsel &quot;error: $*&quot;
3115 }
3116 override_install() {
3117 apt-install eatmydata || true
3118 if [ -x /target/usr/bin/eatmydata ] ; then
3119 for bin in dpkg apt-get aptitude tasksel ; do
3120 file=/usr/bin/$bin
3121 # Test that the file exist and have not been diverted already.
3122 if [ -f /target$file ] ; then
3123 info &quot;diverting $file using eatmydata&quot;
3124 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3125 &gt; /target$file.edu
3126 chmod 755 /target$file.edu
3127 in-target dpkg-divert --package debian-edu-config \
3128 --rename --quiet --add $file
3129 ln -sf ./$bin.edu /target$file
3130 else
3131 error &quot;unable to divert $file, as it is missing.&quot;
3132 fi
3133 done
3134 else
3135 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3136 fi
3137 }
3138
3139 override_install
3140 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3141
3142 &lt;p&gt;To clean up, another shell script should go into
3143 /usr/lib/finish-install.d/ with code like this:
3144
3145 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3146 #! /bin/sh -e
3147 . /usr/share/debconf/confmodule
3148 error() {
3149 logger -t my-finish-install &quot;error: $@&quot;
3150 }
3151 remove_install_override() {
3152 for bin in dpkg apt-get aptitude tasksel ; do
3153 file=/usr/bin/$bin
3154 if [ -x /target$file.edu ] ; then
3155 rm /target$file
3156 in-target dpkg-divert --package debian-edu-config \
3157 --rename --quiet --remove $file
3158 rm /target$file.edu
3159 else
3160 error &quot;Missing divert for $file.&quot;
3161 fi
3162 done
3163 sync # Flush file buffers before continuing
3164 }
3165
3166 remove_install_override
3167 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3168
3169 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3170 edu-eatmydata-install and call it from the pre-pkgsel.d and
3171 finish-install.d scripts.&lt;/p&gt;
3172
3173 &lt;p&gt;By now you might ask if this change should get into the normal
3174 Debian installer too? I suspect it should, but am not sure the
3175 current debian-installer coordinators find it useful enough. It also
3176 depend on the side effects of the change. I&#39;m not aware of any, but I
3177 guess we will see if the change is safe after some more testing.
3178 Perhaps there is some package in Debian depending on sync() and
3179 fsync() having effect? Perhaps it should go into its own udeb, to
3180 allow those of us wanting to enable it to do so without affecting
3181 everyone.&lt;/p&gt;
3182
3183 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3184 will break installation of all programs using gnutls because of
3185 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3186 eatmydata package in Debian will solve it.&lt;/p&gt;
3187
3188 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3189 the optimization work again. And I have discovered that the
3190 dpkg-divert trick is not really needed and implemented a slightly
3191 simpler approach as part of the debian-edu-install package. See
3192 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3193
3194 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
3195 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
3196 triggering on i386 made it into testing, and broke this installation
3197 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
3198 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
3199 </description>
3200 </item>
3201
3202 <item>
3203 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
3204 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
3205 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
3206 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
3207 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
3208 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
3209 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
3210 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
3211 learn that there is a large set of publicly available key servers to
3212 use when looking for peoples public key. So far I have used
3213 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3214 were misbehaving, but those days are ended. The servers I have used
3215 up until yesterday have been slow and some times unavailable. I hope
3216 those problems are gone now.&lt;/p&gt;
3217
3218 &lt;p&gt;Behind the round robin DNS entry of the
3219 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
3220 there is a pool of more than 100 keyservers which are checked every
3221 day to ensure they are well connected and up to date. It must be
3222 better than what I have used so far. :)&lt;/p&gt;
3223
3224 &lt;p&gt;Yesterdays speaker told me that the service is the default
3225 keyserver provided by the default configuration in GnuPG, but this do
3226 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
3227
3228 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
3229 line:&lt;/p&gt;
3230
3231 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3232 keyserver pool.sks-keyservers.net
3233 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3234
3235 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
3236 entries in DNS. Just for fun, I did just that at work, so now every
3237 user of GnuPG at the University of Oslo should find a OpenGPG
3238 keyserver automatically should their need it:&lt;/p&gt;
3239
3240 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3241 % host -t srv _pgpkey-http._tcp.uio.no
3242 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
3243 %
3244 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3245
3246 &lt;p&gt;Now if only
3247 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
3248 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
3249 very happy. It can look up a given key or search for a user ID, but I
3250 normally do not want that, but to find a trust path from my key to
3251 another key. Given a user ID or key ID, I would like to find (and
3252 download) the keys representing a signature path from my key to the
3253 key in question, to be able to get a trust path between the two keys.
3254 This is as far as I can tell not possible today. Perhaps something
3255 for a future version of the protocol?&lt;/p&gt;
3256 </description>
3257 </item>
3258
3259 <item>
3260 <title>From English wiki to translated PDF and epub via Docbook</title>
3261 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
3262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
3263 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
3264 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3265 project&lt;/a&gt; provide an instruction manual for teachers, system
3266 administrators and other users that contain useful tips for setting up
3267 and maintaining a Debian Edu installation. This text is about how the
3268 text processing of this manual is handled in the project.&lt;/p&gt;
3269
3270 &lt;p&gt;One goal of the project is to provide information in the native
3271 language of its users, and for this we need to handle translations.
3272 But we also want to make sure each language contain the same
3273 information, so for this we need a good way to keep the translations
3274 in sync. And we want it to be easy for our users to improve the
3275 documentation, avoiding the need to learn special formats or tools to
3276 contribute, and the obvious way to do this is to make it possible to
3277 edit the documentation using a web browser. We also want it to be
3278 easy for translators to keep the translation up to date, and give them
3279 help in figuring out what need to be translated. Here is the list of
3280 tools and the process we have found trying to reach all these
3281 goals.&lt;/p&gt;
3282
3283 &lt;p&gt;We maintain the authoritative source of our manual in the
3284 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
3285 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
3286 front page with references to the different chapters, several pages
3287 for each chapter, and finally one &quot;collection page&quot; gluing all the
3288 chapters together into one large web page (aka
3289 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
3290 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
3291 processing and translations. Thanks to the fact that the
3292 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
3293 wiki.debian.org support exporting pages in
3294 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
3295 the list of pages to export using the raw version of the AllInOne
3296 page, loop over each of them to generate a Docbook XML version of the
3297 manual. This process also download images and transform image
3298 references to use the locally downloaded images. The generated
3299 Docbook XML files are slightly broken, so some post-processing is done
3300 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
3301 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3302 a handfull of images. The XML file can now be used to generate PDF, HTML
3303 and epub versions of the English manual. This is the basic step of
3304 our process, making PDF (using dblatex), HTML (using xsltproc) and
3305 epub (using dbtoepub) version from Docbook XML, and the resulting files
3306 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
3307
3308 &lt;p&gt;But English documentation is not enough for us. We want translated
3309 documentation too, and we want to make it easy for translators to
3310 track the English original. For this we use the
3311 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
3312 which allow us to transform the English Docbook XML file into a
3313 translation file (a .pot file), usable with the normal gettext based
3314 translation tools used by those translating free software. The pot
3315 file is used to create and maintain translation files (several .po
3316 files), which the translations update with the native language
3317 translations of all titles, paragraphs and blocks of text in the
3318 original. The next step is combining the original English Docbook XML
3319 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3320 create a translated Docbook XML file (in this case
3321 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3322 translated, if the translation is not complete) Docbook XML file can
3323 then be used like the original to create a PDF, HTML and epub version
3324 of the documentation.&lt;/p&gt;
3325
3326 &lt;p&gt;The translators use different tools to edit the .po files. We
3327 recommend using
3328 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
3329 while some use emacs and vi, others can use web based editors like
3330 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
3331 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
3332 is where the .po file end up, in our git repository. Updated
3333 translations can either be committed directly to git, or submitted as
3334 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
3335 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
3336
3337 &lt;p&gt;One challenge is images, which both might need to be translated (if
3338 they show translated user applications), and are needed in different
3339 formats when creating PDF and HTML versions (epub is a HTML version in
3340 this regard). For this we transform the original PNG images to the
3341 needed density and format during build, and have a way to provide
3342 translated images by storing translated versions in
3343 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3344 package maintainers know more.&lt;/p&gt;
3345
3346 &lt;p&gt;If you wonder what the result look like, we provide
3347 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
3348 of the documentation packages on the web&lt;/a&gt;. See for example the
3349 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
3350 PDF version&lt;/a&gt; or the
3351 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
3352 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
3353 but perhaps it will be done in the future.&lt;/p&gt;
3354
3355 &lt;p&gt;To learn more, check out
3356 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
3357 debian-edu-doc package&lt;/a&gt;,
3358 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
3359 manual on the wiki&lt;/a&gt; and
3360 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
3361 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
3362 </description>
3363 </item>
3364
3365 <item>
3366 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
3367 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
3368 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
3369 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
3370 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
3371 related packages relevant for the computer installed automatically.
3372 So I implemented one, using
3373 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
3374 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
3375 run tasksel as user root. You should be presented with a new option,
3376 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
3377 select it, tasksel will install the packages isenkram claim is fit for
3378 the current hardware, hot pluggable or not.&lt;p&gt;
3379
3380 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
3381 description, and the other is the script used to extract the list of
3382 packages to install. The first part is in
3383 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
3384 this:&lt;/p&gt;
3385
3386 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3387 Task: isenkram
3388 Section: hardware
3389 Description: Hardware specific packages (autodetected by isenkram)
3390 Based on the detected hardware various hardware specific packages are
3391 proposed.
3392 Test-new-install: mark show
3393 Relevance: 8
3394 Packages: for-current-hardware
3395 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3396
3397 &lt;p&gt;The second part is in
3398 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3399 this:&lt;/p&gt;
3400
3401 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3402 #!/bin/sh
3403 #
3404 (
3405 isenkram-lookup
3406 isenkram-autoinstall-firmware -l
3407 ) | sort -u
3408 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3409
3410 &lt;p&gt;All in all, a very short and simple implementation making it
3411 trivial to install the hardware dependent package we all may want to
3412 have installed on our machines. I&#39;ve not been able to find a way to
3413 get tasksel to tell you exactly which packages it plan to install
3414 before doing the installation. So if you are curious or careful,
3415 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3416
3417 &lt;p&gt;The information about which packages are handling which hardware is
3418 fetched either from the isenkram package itself in
3419 /usr/share/isenkram/, from git.debian.org or from the APT package
3420 database (using the Modaliases header). The APT package database
3421 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3422 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3423 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3424 the python-apt code (bug
3425 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3426 workaround I was able to get rid of the file descriptor leak and
3427 reduce the memory leak from ~30 MiB per hardware detection down to
3428 around 2 MiB per hardware detection. It should make the desktop
3429 daemon a lot more useful. The fix is in version 0.7 uploaded to
3430 unstable today.&lt;/p&gt;
3431
3432 &lt;p&gt;I believe the current way of mapping hardware to packages in
3433 Isenkram is is a good draft, but in the future I expect isenkram to
3434 use the AppStream data source for this. A proposal for getting proper
3435 AppStream support into Debian is floating around as
3436 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3437 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3438 project&lt;/a&gt; will take place this summer to improve the situation. I
3439 look forward to seeing the result, and welcome patches for isenkram to
3440 start using the information when it is ready.&lt;/p&gt;
3441
3442 &lt;p&gt;If you want your package to map to some specific hardware, either
3443 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3444 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3445 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3446 package. See also
3447 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3448 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3449 the information will be migrated to AppStream eventually, but for the
3450 moment I got no better place to store it.&lt;/p&gt;
3451 </description>
3452 </item>
3453
3454 <item>
3455 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3456 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3458 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3459 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3460 project&lt;/a&gt; is working on providing the software and hardware to make
3461 it easy for non-technical people to host their data and communication
3462 at home, and being able to communicate with their friends and family
3463 encrypted and away from prying eyes. It is still going strong, and
3464 today a major mile stone was reached.&lt;/p&gt;
3465
3466 &lt;p&gt;Today, the last of the packages currently used by the project to
3467 created the system images were accepted into Debian Unstable. It was
3468 the freedombox-setup package, which is used to configure the images
3469 during build and on the first boot. Now all one need to get going is
3470 the build code from the freedom-maker git repository and packages from
3471 Debian. And once the freedombox-setup package enter testing, we can
3472 build everything directly from Debian. :)&lt;/p&gt;
3473
3474 &lt;p&gt;Some key packages used by Freedombox are
3475 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3476 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3477 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3478 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3479 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3480 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3481 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3482 are plans to integrate more packages into the setup. User
3483 documentation is maintained on the Debian wiki. Please
3484 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3485 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3486
3487 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3488 setup, run this on a Debian machine using a user with sudo rights to
3489 become root:&lt;/p&gt;
3490
3491 &lt;p&gt;&lt;pre&gt;
3492 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3493 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3494 u-boot-tools
3495 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3496 freedom-maker
3497 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3498 &lt;/pre&gt;&lt;/p&gt;
3499
3500 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3501 devices. See the README in the freedom-maker git repo for more
3502 details on the build. If you do not want all three images, trim the
3503 make line. Note that the virtualbox-image target is not really
3504 virtualbox specific. It create a x86 image usable in kvm, qemu,
3505 vmware and any other x86 virtual machine environment. You might need
3506 the version of vmdebootstrap in Jessie to get the build working, as it
3507 include fixes for a race condition with kpartx.&lt;/p&gt;
3508
3509 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3510 method, boot a Debian Wheezy ISO and use this boot argument to load
3511 the preseed values:&lt;/p&gt;
3512
3513 &lt;p&gt;&lt;pre&gt;
3514 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;
3515 &lt;/pre&gt;&lt;/p&gt;
3516
3517 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3518 it still work.&lt;/p&gt;
3519
3520 &lt;p&gt;If you wonder how to help, one task you could look at is using
3521 systemd as the boot system. It will become the default for Linux in
3522 Jessie, so we need to make sure it is usable on the Freedombox. I did
3523 a simple test a few weeks ago, and noticed dnsmasq failed to start
3524 during boot when using systemd. I suspect there are other problems
3525 too. :) To detect problems, there is a test suite included, which can
3526 be run from the plinth web interface.&lt;/p&gt;
3527
3528 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3529 us get the new release published. :) Please join us on
3530 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3531 irc.debian.org)&lt;/a&gt; and
3532 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3533 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3534 </description>
3535 </item>
3536
3537 <item>
3538 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3539 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3540 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3541 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3542 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3543 solution for use at home. My requirements are simple, it must be
3544 cheap and locally encrypted (in other words, I keep the encryption
3545 keys, the storage provider do not have access to my private files).
3546 One idea me and my friends had many years ago, before the cloud
3547 storage providers showed up, was to use Google mail as storage,
3548 writing a Linux block device storing blocks as emails in the mail
3549 service provided by Google, and thus get heaps of free space. On top
3550 of this one can add encryption, RAID and volume management to have
3551 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3552 I never found time to implement such system. But the last few weeks I
3553 have looked at a system called
3554 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3555 mounted network backed file system with the features I need.&lt;/p&gt;
3556
3557 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3558 handling several different storage providers, any with Amazon S3,
3559 Google Drive or OpenStack API. There are heaps of such storage
3560 providers. S3QL can also use a local directory as storage, which
3561 combined with sshfs allow for file storage on any ssh server. S3QL
3562 include support for encryption, compression, de-duplication, snapshots
3563 and immutable file systems, allowing me to mount the remote storage as
3564 a local mount point, look at and use the files as if they were local,
3565 while the content is stored in the cloud as well. This allow me to
3566 have a backup that should survive fire. The file system can not be
3567 shared between several machines at the same time, as only one can
3568 mount it at the time, but any machine with the encryption key and
3569 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3570
3571 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3572 package is included already. So to get started, run &lt;tt&gt;apt-get
3573 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3574 Greenqloud, after reading their nice recipe on
3575 &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
3576 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3577 in Iceland more than those in USA when it come to keeping my personal
3578 data safe and private, and thus would rather spend money on a company
3579 in Iceland. Another nice recipe is available from the article
3580 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3581 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3582 Admin magazine. When the provider is picked, figure out how to get
3583 the API key needed to connect to the storage API. With Greencloud,
3584 the key did not show up until I had added payment details to my
3585 account.&lt;/p&gt;
3586
3587 &lt;p&gt;Armed with the API access details, it is time to create the file
3588 system. First, create a new bucket in the cloud. This bucket is the
3589 file system storage area. I picked a bucket name reflecting the
3590 machine that was going to store data there, but any name will do.
3591 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3592 the API login and password, and a locally created password. Store it
3593 all in ~root/.s3ql/authinfo2 like this:
3594
3595 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3596 [s3c]
3597 storage-url: s3c://s.greenqloud.com:443/bucket-name
3598 backend-login: API-login
3599 backend-password: API-password
3600 fs-passphrase: local-password
3601 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3602
3603 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3604 but any sensible way to create a fairly random password should do it.
3605 Armed with these details, it is now time to run mkfs, entering the API
3606 details and password to create it:&lt;/p&gt;
3607
3608 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3609 # mkdir -m 700 /var/lib/s3ql-cache
3610 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3611 --ssl s3c://s.greenqloud.com:443/bucket-name
3612 Enter backend login:
3613 Enter backend password:
3614 Before using S3QL, make sure to read the user&#39;s guide, especially
3615 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3616 Enter encryption password:
3617 Confirm encryption password:
3618 Generating random encryption key...
3619 Creating metadata tables...
3620 Dumping metadata...
3621 ..objects..
3622 ..blocks..
3623 ..inodes..
3624 ..inode_blocks..
3625 ..symlink_targets..
3626 ..names..
3627 ..contents..
3628 ..ext_attributes..
3629 Compressing and uploading metadata...
3630 Wrote 0.00 MB of compressed metadata.
3631 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3632
3633 &lt;p&gt;The next step is mounting the file system to make the storage available.
3634
3635 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3636 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3637 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3638 Using 4 upload threads.
3639 Downloading and decompressing metadata...
3640 Reading metadata...
3641 ..objects..
3642 ..blocks..
3643 ..inodes..
3644 ..inode_blocks..
3645 ..symlink_targets..
3646 ..names..
3647 ..contents..
3648 ..ext_attributes..
3649 Mounting filesystem...
3650 # df -h /s3ql
3651 Filesystem Size Used Avail Use% Mounted on
3652 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
3653 #
3654 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3655
3656 &lt;p&gt;The file system is now ready for use. I use rsync to store my
3657 backups in it, and as the metadata used by rsync is downloaded at
3658 mount time, no network traffic (and storage cost) is triggered by
3659 running rsync. To unmount, one should not use the normal umount
3660 command, as this will not flush the cache to the cloud storage, but
3661 instead running the umount.s3ql command like this:
3662
3663 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3664 # umount.s3ql /s3ql
3665 #
3666 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3667
3668 &lt;p&gt;There is a fsck command available to check the file system and
3669 correct any problems detected. This can be used if the local server
3670 crashes while the file system is mounted, to reset the &quot;already
3671 mounted&quot; flag. This is what it look like when processing a working
3672 file system:&lt;/p&gt;
3673
3674 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3675 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
3676 Using cached metadata.
3677 File system seems clean, checking anyway.
3678 Checking DB integrity...
3679 Creating temporary extra indices...
3680 Checking lost+found...
3681 Checking cached objects...
3682 Checking names (refcounts)...
3683 Checking contents (names)...
3684 Checking contents (inodes)...
3685 Checking contents (parent inodes)...
3686 Checking objects (reference counts)...
3687 Checking objects (backend)...
3688 ..processed 5000 objects so far..
3689 ..processed 10000 objects so far..
3690 ..processed 15000 objects so far..
3691 Checking objects (sizes)...
3692 Checking blocks (referenced objects)...
3693 Checking blocks (refcounts)...
3694 Checking inode-block mapping (blocks)...
3695 Checking inode-block mapping (inodes)...
3696 Checking inodes (refcounts)...
3697 Checking inodes (sizes)...
3698 Checking extended attributes (names)...
3699 Checking extended attributes (inodes)...
3700 Checking symlinks (inodes)...
3701 Checking directory reachability...
3702 Checking unix conventions...
3703 Checking referential integrity...
3704 Dropping temporary indices...
3705 Backing up old metadata...
3706 Dumping metadata...
3707 ..objects..
3708 ..blocks..
3709 ..inodes..
3710 ..inode_blocks..
3711 ..symlink_targets..
3712 ..names..
3713 ..contents..
3714 ..ext_attributes..
3715 Compressing and uploading metadata...
3716 Wrote 0.89 MB of compressed metadata.
3717 #
3718 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3719
3720 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
3721 quick, about the same speed as local file access. Uploading large
3722 amount of data is to me limited by the bandwidth out of and into my
3723 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
3724 which is very close to my upload speed, and downloading the same
3725 Debian installation ISO gave me 610 kiB/s, close to my download speed.
3726 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
3727 network, not the file system code. I do not know what a good cache
3728 size would be, but suspect that the cache should e larger than your
3729 working set.&lt;/p&gt;
3730
3731 &lt;p&gt;I mentioned that only one machine can mount the file system at the
3732 time. If another machine try, it is told that the file system is
3733 busy:&lt;/p&gt;
3734
3735 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3736 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3737 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3738 Using 8 upload threads.
3739 Backend reports that fs is still mounted elsewhere, aborting.
3740 #
3741 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3742
3743 &lt;p&gt;The file content is uploaded when the cache is full, while the
3744 metadata is uploaded once every 24 hour by default. To ensure the
3745 file system content is flushed to the cloud, one can either umount the
3746 file system, or ask S3QL to flush the cache and metadata using
3747 s3qlctrl:
3748
3749 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3750 # s3qlctrl upload-meta /s3ql
3751 # s3qlctrl flushcache /s3ql
3752 #
3753 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3754
3755 &lt;p&gt;If you are curious about how much space your data uses in the
3756 cloud, and how much compression and deduplication cut down on the
3757 storage usage, you can use s3qlstat on the mounted file system to get
3758 a report:&lt;/p&gt;
3759
3760 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3761 # s3qlstat /s3ql
3762 Directory entries: 9141
3763 Inodes: 9143
3764 Data blocks: 8851
3765 Total data size: 22049.38 MB
3766 After de-duplication: 21955.46 MB (99.57% of total)
3767 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
3768 Database size: 2.39 MB (uncompressed)
3769 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3770 #
3771 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3772
3773 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
3774 storage. I did not try to locate them all, but am aware of at least
3775 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
3776 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
3777 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
3778 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
3779 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
3780 accept payment in Bitcoin. Pick one that suit your need. Some of
3781 them provide several GiB of free storage, but the prize models are
3782 quite different and you will have to figure out what suits you
3783 best.&lt;/p&gt;
3784
3785 &lt;p&gt;While researching this blog post, I had a look at research papers
3786 and posters discussing the S3QL file system. There are several, which
3787 told me that the file system is getting a critical check by the
3788 science community and increased my confidence in using it. One nice
3789 poster is titled
3790 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
3791 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3792 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
3793 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3794 and Pamela Smith. Please have a look.&lt;/p&gt;
3795
3796 &lt;p&gt;Given my problems with different file systems earlier, I decided to
3797 check out the mounted S3QL file system to see if it would be usable as
3798 a home directory (in other word, that it provided POSIX semantics when
3799 it come to locking and umask handling etc). Running
3800 &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
3801 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
3802 no error was found. So the file system can be used for home
3803 directories, if one chooses to do so.&lt;/p&gt;
3804
3805 &lt;p&gt;If you do not want a locally file system, and want something that
3806 work without the Linux fuse file system, I would like to mention the
3807 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
3808 provide locally encrypted backup using a command line client. It have
3809 a nicer access control system, where one can split out read and write
3810 access, allowing some systems to write to the backup and others to
3811 only read from it.&lt;/p&gt;
3812
3813 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3814 activities, please send Bitcoin donations to my address
3815 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3816 </description>
3817 </item>
3818
3819 <item>
3820 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
3821 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
3822 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
3823 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
3824 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3825 project&lt;/a&gt; is working on providing the software and hardware for
3826 making it easy for non-technical people to host their data and
3827 communication at home, and being able to communicate with their
3828 friends and family encrypted and away from prying eyes. It has been
3829 going on for a while, and is slowly progressing towards a new test
3830 release (0.2).&lt;/p&gt;
3831
3832 &lt;p&gt;And what day could be better than the Pi day to announce that the
3833 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
3834 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3835 system), and can also be installed using a Debian installer preseed
3836 file. The Debian based Freedombox is now based on Debian Jessie,
3837 where most of the needed packages used are already present. Only one,
3838 the freedombox-setup package, is missing. To try to build your own
3839 boot image to test the current status, fetch the freedom-maker scripts
3840 and build using
3841 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
3842 with a user with sudo access to become root:
3843
3844 &lt;pre&gt;
3845 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3846 freedom-maker
3847 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3848 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3849 u-boot-tools
3850 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3851 &lt;/pre&gt;
3852
3853 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3854 devices. See the README for more details on the build. If you do not
3855 want all three images, trim the make line. But note that thanks to &lt;a
3856 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
3857 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
3858 kpartx call.&lt;/p&gt;
3859
3860 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3861 method, boot a Debian Wheezy ISO and use this boot argument to load
3862 the preseed values:&lt;/p&gt;
3863
3864 &lt;pre&gt;
3865 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;
3866 &lt;/pre&gt;
3867
3868 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
3869 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
3870 currently hang while setting up APT sources. Killing the
3871 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
3872 installation will get the installation going. This affect all
3873 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
3874
3875 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3876 us get the new release published. :) Please join us on
3877 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3878 irc.debian.org)&lt;/a&gt; and
3879 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3880 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3881 </description>
3882 </item>
3883
3884 <item>
3885 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
3886 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
3887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
3888 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
3889 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
3890 innetgr tools, because I needed them in
3891 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
3892 ng-utils, and it has served me well. I placed the project under the
3893 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
3894 repository. But many years ago, the CVS repository was dropped (lost,
3895 not migrated to new hardware, not sure), and the project have lacked a
3896 proper home since then.&lt;/p&gt;
3897
3898 &lt;p&gt;Last summer, I had a look at the package and made a new release
3899 fixing a irritating crash bug, but was unable to store the changes in
3900 a proper source control system. I applied for a project on
3901 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
3902 to follow up on it. Until today. :)&lt;/p&gt;
3903
3904 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
3905 now have a new home, and a git repository with the highlight of the
3906 history of the project. I published all release tarballs and imported
3907 them into the git repository. As the project is really stable and not
3908 expected to gain new features any time soon, I decided to make a new
3909 release and call it 1.0. Visit the new project home on
3910 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
3911 if you want to check it out. The new version is also uploaded into
3912 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
3913 </description>
3914 </item>
3915
3916 <item>
3917 <title>Testing sysvinit from experimental in Debian Hurd</title>
3918 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
3919 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
3920 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
3921 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
3922 their changes into sysvinit, to allow them to use the normal sysvinit
3923 boot system instead of their old one. This follow up on the
3924 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
3925 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
3926 get Debian on Hurd working more like Debian on Linux. To get started,
3927 I downloaded a prebuilt hard disk image from
3928 &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;,
3929 and started it using virt-manager.&lt;/p&gt;
3930
3931 &lt;p&gt;The first think I had to do after logging in (root without any
3932 password) was to get the network operational. I followed
3933 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
3934 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
3935 commands as root to get the machine to accept a IP address from the
3936 kvm internal DHCP server:&lt;/p&gt;
3937
3938 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3939 settrans -fgap /dev/netdde /hurd/netdde
3940 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
3941 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
3942 dhclient /dev/eth0
3943 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3944
3945 &lt;p&gt;After this, the machine had internet connectivity, and I could
3946 upgrade it and install the sysvinit packages from experimental and
3947 enable it as the default boot system in Hurd.&lt;/p&gt;
3948
3949 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
3950 running on the machine it for ssh login to work a password need to be
3951 set. Also, note that a bug somewhere in openssh on Hurd block
3952 compression from working. Remember to turn that off on the client
3953 side.&lt;/p&gt;
3954
3955 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
3956 stuff:&lt;/p&gt;
3957
3958 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3959 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
3960 deb http://http.debian.net/debian/ experimental main
3961 EOF
3962 apt-get update
3963 apt-get dist-upgrade
3964 apt-get install -t experimental initscripts sysv-rc sysvinit \
3965 sysvinit-core sysvinit-utils
3966 update-alternatives --config runsystem
3967 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3968
3969 &lt;p&gt;To reboot after switching boot system, you have to use
3970 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
3971 yet a sysvinit process able to receive the signals from the normal
3972 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
3973 upgrading every package and rebooting, the network come up with DHCP
3974 after boot as it should, and the settrans/pkill hack mentioned at the
3975 start is no longer needed. But for some strange reason, there are no
3976 longer any login prompt in the virtual console, so I logged in using
3977 ssh instead.
3978
3979 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
3980 fail some times. No idea what the cause is, but hope the Hurd porters
3981 figure it out. At least Justus said on IRC (#debian-hurd on
3982 irc.debian.org) that they are aware of the problem. A way to reduce
3983 the impact is to upgrade to the Hurd packages built by Justus by
3984 adding this repository to the machine:&lt;/p&gt;
3985
3986 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3987 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
3988 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3989 EOF
3990 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3991
3992 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
3993 http://ftp.debian-ports.org/debian, because some of the packages in
3994 unstable do not yet include the required patches that are lingering in
3995 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
3996
3997 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3998 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
3999 i emacs - GNU Emacs editor (metapackage)
4000 i gdb - GNU Debugger
4001 i hurd-recommended - Miscellaneous translators
4002 i isc-dhcp-client - ISC DHCP client
4003 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4004 i libc-bin - Embedded GNU C Library: Binaries
4005 i libc-dev-bin - Embedded GNU C Library: Development binaries
4006 i libc0.3 - Embedded GNU C Library: Shared libraries
4007 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4008 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4009 i multiarch-support - Transitional package to ensure multiarch compatibilit
4010 i A x11-common - X Window System (X.Org) infrastructure
4011 i xorg - X.Org X Window System
4012 i A xserver-xorg - X.Org X server
4013 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4014 #
4015 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4016
4017 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
4018 X.org did not work out of the box and I never took the time to follow
4019 the porters instructions to fix it. This time I was interested in the
4020 command line stuff.&lt;p&gt;
4021 </description>
4022 </item>
4023
4024 <item>
4025 <title>New chrpath release 0.16</title>
4026 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
4027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
4028 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
4029 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
4030 find problems in C, C++ and Java code using static source code
4031 analysis. It can detect a lot of different problems, and is very
4032 useful to find memory and locking bugs in the error handling part of
4033 the source. The company behind it provide
4034 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
4035 a community service&lt;/a&gt;, and many hundred free software projects are
4036 already checked. A few days ago I decided to have a closer look at
4037 the Coverity system, and discovered that the
4038 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
4039 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
4040 projects I am involved with was already registered. But these are
4041 fairly big, and I would also like to have a small and easy project to
4042 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
4043 checking of the chrpath project&lt;/a&gt;. It was
4044 added to the checker and discovered seven potential defects. Six of
4045 these were real, mostly resource &quot;leak&quot; when the program detected an
4046 error. Nothing serious, as the resources would be released a fraction
4047 of a second later when the program exited because of the error, but it
4048 is nice to do it right in case the source of the program some time in
4049 the future end up in a library. Having fixed all defects and added
4050 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
4051 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
4052 publish a new release. These are the release notes:&lt;/p&gt;
4053
4054 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
4055
4056 &lt;ul&gt;
4057
4058 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
4059 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
4060 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
4061
4062 &lt;/ul&gt;
4063
4064 &lt;p&gt;You can
4065 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4066 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
4067 project if something is wrong with the new release. The test suite
4068 did not discover any old errors, so if you find a new one, please also
4069 include a test suite check.&lt;/p&gt;
4070 </description>
4071 </item>
4072
4073 <item>
4074 <title>New chrpath release 0.15</title>
4075 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
4076 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
4077 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
4078 <description>&lt;p&gt;After many years break from the package and a vain hope that
4079 development would be continued by someone else, I finally pulled my
4080 acts together this morning and wrapped up a new release of chrpath,
4081 the command line tool to modify the rpath and runpath of already
4082 compiled ELF programs. The update was triggered by the persistence of
4083 Isha Vishnoi at IBM, which needed a new config.guess file to get
4084 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
4085 is working on. I checked the
4086 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
4087 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4088 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4089 packages for interesting patches (failed to find the source from
4090 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4091 These are the release notes:&lt;/p&gt;
4092
4093 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4094
4095 &lt;ul&gt;
4096
4097 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4098 with newer architectures. Thanks to isha vishnoi for the heads
4099 up.&lt;/li&gt;
4100
4101 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4102
4103 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4104 Matthias Klose.&lt;/li&gt;
4105
4106 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4107 Petr Machata found in Fedora.&lt;/li&gt;
4108
4109 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4110 .dynamic is a NULL terminated string. Based on patch found in
4111 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4112
4113 &lt;/ul&gt;
4114
4115 &lt;p&gt;You can
4116 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4117 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4118 project if something is wrong with the new release. The test suite
4119 did not discover any old errors, so if you find a new one, please also
4120 include a testsuite check.&lt;/p&gt;
4121 </description>
4122 </item>
4123
4124 <item>
4125 <title>Debian init.d boot script example for rsyslog</title>
4126 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4127 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4128 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4129 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4130 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4131 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4132 init.d scripts at all. Here is an example init.d script, ie a rewrite
4133 of /etc/init.d/rsyslog:&lt;/p&gt;
4134
4135 &lt;p&gt;&lt;pre&gt;
4136 #!/lib/init/init-d-script
4137 ### BEGIN INIT INFO
4138 # Provides: rsyslog
4139 # Required-Start: $remote_fs $time
4140 # Required-Stop: umountnfs $time
4141 # X-Stop-After: sendsigs
4142 # Default-Start: 2 3 4 5
4143 # Default-Stop: 0 1 6
4144 # Short-Description: enhanced syslogd
4145 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4146 # It is quite compatible to stock sysklogd and can be
4147 # used as a drop-in replacement.
4148 ### END INIT INFO
4149 DESC=&quot;enhanced syslogd&quot;
4150 DAEMON=/usr/sbin/rsyslogd
4151 &lt;/pre&gt;&lt;/p&gt;
4152
4153 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4154 script was 137 lines, and the above is just 15 lines, most of it meta
4155 info/comments.&lt;/p&gt;
4156
4157 &lt;p&gt;How to do this, you ask? Well, one create a new script
4158 /lib/init/init-d-script looking something like this:
4159
4160 &lt;p&gt;&lt;pre&gt;
4161 #!/bin/sh
4162
4163 # Define LSB log_* functions.
4164 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4165 # and status_of_proc is working.
4166 . /lib/lsb/init-functions
4167
4168 #
4169 # Function that starts the daemon/service
4170
4171 #
4172 do_start()
4173 {
4174 # Return
4175 # 0 if daemon has been started
4176 # 1 if daemon was already running
4177 # 2 if daemon could not be started
4178 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4179 || return 1
4180 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4181 $DAEMON_ARGS \
4182 || return 2
4183 # Add code here, if necessary, that waits for the process to be ready
4184 # to handle requests from services started subsequently which depend
4185 # on this one. As a last resort, sleep for some time.
4186 }
4187
4188 #
4189 # Function that stops the daemon/service
4190 #
4191 do_stop()
4192 {
4193 # Return
4194 # 0 if daemon has been stopped
4195 # 1 if daemon was already stopped
4196 # 2 if daemon could not be stopped
4197 # other if a failure occurred
4198 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
4199 RETVAL=&quot;$?&quot;
4200 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
4201 # Wait for children to finish too if this is a daemon that forks
4202 # and if the daemon is only ever run from this initscript.
4203 # If the above conditions are not satisfied then add some other code
4204 # that waits for the process to drop all resources that could be
4205 # needed by services started subsequently. A last resort is to
4206 # sleep for some time.
4207 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
4208 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
4209 # Many daemons don&#39;t delete their pidfiles when they exit.
4210 rm -f $PIDFILE
4211 return &quot;$RETVAL&quot;
4212 }
4213
4214 #
4215 # Function that sends a SIGHUP to the daemon/service
4216 #
4217 do_reload() {
4218 #
4219 # If the daemon can reload its configuration without
4220 # restarting (for example, when it is sent a SIGHUP),
4221 # then implement that here.
4222 #
4223 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
4224 return 0
4225 }
4226
4227 SCRIPTNAME=$1
4228 scriptbasename=&quot;$(basename $1)&quot;
4229 echo &quot;SN: $scriptbasename&quot;
4230 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
4231 script=&quot;$1&quot;
4232 shift
4233 . $script
4234 else
4235 exit 0
4236 fi
4237
4238 NAME=$(basename $DAEMON)
4239 PIDFILE=/var/run/$NAME.pid
4240
4241 # Exit if the package is not installed
4242 #[ -x &quot;$DAEMON&quot; ] || exit 0
4243
4244 # Read configuration variable file if it is present
4245 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
4246
4247 # Load the VERBOSE setting and other rcS variables
4248 . /lib/init/vars.sh
4249
4250 case &quot;$1&quot; in
4251 start)
4252 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
4253 do_start
4254 case &quot;$?&quot; in
4255 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4256 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4257 esac
4258 ;;
4259 stop)
4260 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
4261 do_stop
4262 case &quot;$?&quot; in
4263 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4264 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4265 esac
4266 ;;
4267 status)
4268 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
4269 ;;
4270 #reload|force-reload)
4271 #
4272 # If do_reload() is not implemented then leave this commented out
4273 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
4274 #
4275 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
4276 #do_reload
4277 #log_end_msg $?
4278 #;;
4279 restart|force-reload)
4280 #
4281 # If the &quot;reload&quot; option is implemented then remove the
4282 # &#39;force-reload&#39; alias
4283 #
4284 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
4285 do_stop
4286 case &quot;$?&quot; in
4287 0|1)
4288 do_start
4289 case &quot;$?&quot; in
4290 0) log_end_msg 0 ;;
4291 1) log_end_msg 1 ;; # Old process is still running
4292 *) log_end_msg 1 ;; # Failed to start
4293 esac
4294 ;;
4295 *)
4296 # Failed to stop
4297 log_end_msg 1
4298 ;;
4299 esac
4300 ;;
4301 *)
4302 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
4303 exit 3
4304 ;;
4305 esac
4306
4307 :
4308 &lt;/pre&gt;&lt;/p&gt;
4309
4310 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
4311 lot. I did not really polish the approach, so it might not always
4312 work out of the box, but you get the idea. I did not try very hard to
4313 optimize it nor make it more robust either.&lt;/p&gt;
4314
4315 &lt;p&gt;A better argument for switching init system in Debian than reducing
4316 the size of init scripts (which is a good thing to do anyway), is to
4317 get boot system that is able to handle the kernel events sensibly and
4318 robustly, and do not depend on the boot to run sequentially. The boot
4319 and the kernel have not behaved sequentially in years.&lt;/p&gt;
4320 </description>
4321 </item>
4322
4323 <item>
4324 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
4325 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
4326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
4327 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
4328 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
4329 remote display access is the preferred solution with oVirt and RedHat
4330 Enterprise Virtualization, and I was sad to discover the other day
4331 that the browser plugin needed to use these systems seamlessly was
4332 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
4333 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
4334 2013-04-01, so I decided to wrap up a package based on the great work
4335 from Cajus Pollmeier and put it in a collab-maint maintained git
4336 repository to get a package I could use. I would very much like
4337 others to help me maintain the package (or just take over, I do not
4338 mind), but as no-one had volunteered so far, I just uploaded it to
4339 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
4340
4341 &lt;p&gt;The source is now available from
4342 &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;
4343 </description>
4344 </item>
4345
4346 <item>
4347 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
4348 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
4349 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
4350 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
4351 <description>&lt;p&gt;The
4352 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
4353 program is a a very nice system to create virtual machine images. It
4354 create a image file, add a partition table, mount it and run
4355 debootstrap in the mounted directory to create a Debian system on a
4356 stick. Yesterday, I decided to try to teach it how to make images for
4357 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
4358 of a plan to simplify the build system for
4359 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
4360 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
4361 the virtualbox images, but its current build system made multistrap
4362 based system for Dreamplug images, and it is lacking support for
4363 Raspberry Pi.&lt;/p&gt;
4364
4365 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
4366 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4367 code and adjusted it to be able to build armel images on my amd64
4368 Debian laptop. I ended up giving vmdebootstrap five new options,
4369 allowing me to replicate the image creation process I use to make
4370 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
4371 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
4372 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
4373 call debootstrap with --foreign and to copy the handler into the
4374 generated chroot before running the second stage. This allow
4375 vmdebootstrap to create armel images on an amd64 host. Next I added
4376 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
4377 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
4378 given file system type, allowing me to create an image with a vfat
4379 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
4380 variant&lt;/tt&gt; option to allow me to create smaller images without the
4381 Debian base system packages installed. Finally, I added an option
4382 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
4383 as a boot loader. It is not needed on the Raspberry Pi and probably
4384 most other non-x86 architectures. The changes were accepted by the
4385 upstream author of vmdebootstrap yesterday and today, and is now
4386 available from
4387 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
4388 upstream project page&lt;/a&gt;.&lt;/p&gt;
4389
4390 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
4391 create a small script (the customize script) to add the non-free
4392 binary blob needed to boot the Raspberry Pi and the APT source
4393 list:&lt;/p&gt;
4394
4395 &lt;p&gt;&lt;pre&gt;
4396 #!/bin/sh
4397 set -e # Exit on first error
4398 rootdir=&quot;$1&quot;
4399 cd &quot;$rootdir&quot;
4400 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4401 deb http://http.debian.net/debian/ jessie main contrib non-free
4402 EOF
4403 # Install non-free binary blob needed to boot Raspberry Pi. This
4404 # install a kernel somewhere too.
4405 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4406 -O $rootdir/usr/bin/rpi-update
4407 chmod a+x $rootdir/usr/bin/rpi-update
4408 mkdir -p $rootdir/lib/modules
4409 touch $rootdir/boot/start.elf
4410 chroot $rootdir rpi-update
4411 &lt;/pre&gt;&lt;/p&gt;
4412
4413 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4414 to build the image:&lt;/p&gt;
4415
4416 &lt;pre&gt;
4417 sudo ./vmdebootstrap \
4418 --variant minbase \
4419 --arch armel \
4420 --distribution jessie \
4421 --mirror http://http.debian.net/debian \
4422 --image test.img \
4423 --size 600M \
4424 --bootsize 64M \
4425 --boottype vfat \
4426 --log-level debug \
4427 --verbose \
4428 --no-kernel \
4429 --no-extlinux \
4430 --root-password raspberry \
4431 --hostname raspberrypi \
4432 --foreign /usr/bin/qemu-arm-static \
4433 --customize `pwd`/customize \
4434 --package netbase \
4435 --package git-core \
4436 --package binutils \
4437 --package ca-certificates \
4438 --package wget \
4439 --package kmod
4440 &lt;/pre&gt;&lt;/p&gt;
4441
4442 &lt;p&gt;The list of packages being installed are the ones needed by
4443 rpi-update to make the image bootable on the Raspberry Pi, with the
4444 exception of netbase, which is needed by debootstrap to find
4445 /etc/hosts with the minbase variant. I really wish there was a way to
4446 set up an Raspberry Pi using only packages in the Debian archive, but
4447 that is not possible as far as I know, because it boots from the GPU
4448 using a non-free binary blob.&lt;/p&gt;
4449
4450 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4451 probably a few others installed. I have not checked the complete
4452 build dependency list.&lt;/p&gt;
4453
4454 &lt;p&gt;The resulting image will not use the hardware floating point unit
4455 on the Raspberry PI, because the armel architecture in Debian is not
4456 optimized for that use. So the images created will be a bit slower
4457 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4458 </description>
4459 </item>
4460
4461 <item>
4462 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4463 <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>
4464 <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>
4465 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4466 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4467 wider attention. I recommend signing and donating to each one of
4468 these. :)&lt;/p&gt;
4469
4470 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4471 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4472 Women program which is a Google Summer of Code like initiative to get
4473 more women involved in free software. One debian sponsor has offered
4474 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4475 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4476 hope you will to. :)&lt;/p&gt;
4477
4478 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4479 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4480 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4481 take place these days, and their need to fund the work. I&#39;ve already
4482 donated. Are you next?&lt;/p&gt;
4483
4484 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4485 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4486 statement under the heading
4487 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4488 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4489 Norwegian government. So far 499 signatures. I hope you will sign it
4490 too.&lt;/p&gt;
4491 </description>
4492 </item>
4493
4494 <item>
4495 <title>Videos about the Freedombox project - for inspiration and learning</title>
4496 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4497 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4498 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4499 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4500 project&lt;/a&gt; have been going on for a while, and have presented the
4501 vision, ideas and solution several places. Here is a little
4502 collection of videos of talks and presentation of the project.&lt;/p&gt;
4503
4504 &lt;ul&gt;
4505
4506 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4507 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4508
4509 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4510 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4511
4512 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4513 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4514 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4515 (Youtube)&lt;/li&gt;
4516
4517 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4518 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4519
4520 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4521 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4522
4523 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4524 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4525 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4526
4527 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4528 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4529 (Youtube)&lt;/li&gt;
4530
4531 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4532 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4533
4534 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4535 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4536
4537 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4538 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4539 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4540
4541 &lt;/ul&gt;
4542
4543 &lt;p&gt;A larger list is available from
4544 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4545 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4546
4547 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4548 Jessie is coming along quite well, and soon both Owncloud and using
4549 Tor should be available for testers of the Freedombox solution. :) In
4550 a few weeks I hope everything needed to test it is included in Debian.
4551 The withsqlite package is already in Debian, and the plinth package is
4552 pending in NEW. The third and vital part of that puzzle is the
4553 metapackage/setup framework, which is still pending an upload. Join
4554 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4555 (#freedombox on irc.debian.org)&lt;/a&gt; and
4556 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4557 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4558 </description>
4559 </item>
4560
4561 <item>
4562 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4563 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4565 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4566 <description>&lt;p&gt;I was introduced to the
4567 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4568 in 2010, when Eben Moglen presented his vision about serving the need
4569 of non-technical people to keep their personal information private and
4570 within the legal protection of their own homes. The idea is to give
4571 people back the power over their network and machines, and return
4572 Internet back to its intended peer-to-peer architecture. Instead of
4573 depending on a central service, the Freedombox will give everyone
4574 control over their own basic infrastructure.&lt;/p&gt;
4575
4576 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4577 taken priority. But this summers nasty news about the misuse of trust
4578 and privilege exercised by the &quot;western&quot; intelligence gathering
4579 communities increased my eagerness to contribute to a point where I
4580 actually started working on the project a while back.&lt;/p&gt;
4581
4582 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4583 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4584 create a simple and cheap Debian based appliance that anyone can hook
4585 up in their home and get access to secure and private services and
4586 communication. The initial deployment platform have been the
4587 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4588 which is a piece of hardware I do not own. So to be able to test what
4589 the current Freedombox setup look like, I had to come up with a way to install
4590 it on some hardware I do have access to. I have rewritten the
4591 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4592 image build framework to use .deb packages instead of only copying
4593 setup into the boot images, and thanks to this rewrite I am able to
4594 set up any machine supported by Debian Wheezy as a Freedombox, using
4595 the previously mentioned deb (and a few support debs for packages
4596 missing in Debian).&lt;/p&gt;
4597
4598 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4599 scripts
4600 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4601 and a administrative web interface
4602 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4603 withsqlite), as well as a privacy enhancing proxy based on
4604 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4605 (freedombox-privoxy). There is also a web/javascript based XMPP
4606 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4607 trying (unsuccessfully so far) to talk to the XMPP server
4608 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4609 web interface is pluggable, and the goal is to use it to enable OpenID
4610 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4611 this is really working yet, see
4612 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4613 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4614 on github at the moment. The HTTP proxy is operational out of the
4615 box, and the admin web interface can be used to add/remove plinth
4616 users. I&#39;ve not been able to do anything else with it so far, but
4617 know there are several branches spread around github and other places
4618 with lots of half baked features.&lt;/p&gt;
4619
4620 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4621 following recipes should work to give you a test machine to poke
4622 at.&lt;/p&gt;
4623
4624 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
4625
4626 &lt;ol&gt;
4627
4628 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
4629 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
4630 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
4631 to the Debian installer:&lt;p&gt;
4632 &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;
4633
4634 &lt;li&gt;Answer the few language/region/password questions and pick disk to
4635 install on.&lt;/li&gt;
4636
4637 &lt;li&gt;When the installation is finished and the machine have rebooted a
4638 few times, your Freedombox is ready for testing.&lt;/li&gt;
4639
4640 &lt;/ol&gt;
4641
4642 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
4643
4644 &lt;ol&gt;
4645
4646 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
4647 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
4648 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
4649 &lt;pre&gt;
4650 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
4651 &lt;/pre&gt;&lt;/li&gt;
4652 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
4653 &lt;pre&gt;
4654 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4655 apt-key add -
4656 apt-get update
4657 apt-get install freedombox-setup
4658 /usr/lib/freedombox/setup
4659 &lt;/pre&gt;&lt;/li&gt;
4660 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
4661
4662 &lt;/ol&gt;
4663
4664 &lt;p&gt;You can test it on other architectures too, but because the
4665 freedombox-privoxy package is binary, it will only work as intended on
4666 the architectures where I have had time to build the binary and put it
4667 in my APT repository. But do not let this stop you. It is only a
4668 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
4669
4670 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
4671 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
4672 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
4673 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
4674
4675 &lt;p&gt;Please let me know if this works for you, or if you have any
4676 problems. We gather on the IRC channel
4677 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
4678 irc.debian.org and the
4679 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
4680 mailing list&lt;/a&gt;.&lt;/p&gt;
4681
4682 &lt;p&gt;Once you get your freedombox operational, you can visit
4683 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
4684 welcome screen (dead end - do not be surprised if you are unable to
4685 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
4686 to look at the rest of plinth. The default user is &#39;admin&#39; and the
4687 default password is &#39;secret&#39;.&lt;/p&gt;
4688 </description>
4689 </item>
4690
4691 <item>
4692 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
4693 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
4694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
4695 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
4696 <description>&lt;p&gt;Earlier, I reported about
4697 &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
4698 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
4699 told by IBM that the original disk should be thrown away. And as
4700 there no longer was a problem if I bricked the firmware, I decided
4701 today to try to install Intel firmware to replace the Lenovo firmware
4702 currently on the disk.&lt;/p&gt;
4703
4704 &lt;p&gt;I searched the Intel site for firmware, and found
4705 &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;
4706 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4707 according to the site should contain the latest firmware for SSD
4708 disks. I inserted the broken disk in one of my spare laptops and
4709 booted the ISO from a USB stick. The disk was recognized, but the
4710 program claimed the newest firmware already were installed and refused
4711 to insert any Intel firmware. So no change, and the disk is still
4712 unable to handle write load. :( I guess the only way to get them
4713 working would be if Lenovo releases new firmware. No idea how likely
4714 that is. Anyway, just blogging about this test for completeness. I
4715 got a working Samsung disk, and see no point in spending more time on
4716 the broken disks.&lt;/p&gt;
4717 </description>
4718 </item>
4719
4720 <item>
4721 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
4722 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
4723 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
4724 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
4725 <description>&lt;p&gt;Today I switched to
4726 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
4727 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
4728 my new Thinkpad X230, which was delivered with an
4729 &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
4730 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
4731 sustained writes. My hardware supplier have been very forthcoming in
4732 trying to find a solution, and after first trying with another
4733 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
4734 disk instead to fix it once and for all. The Samsung disk survived
4735 the installation of Debian with encrypted disks (filling the disk with
4736 random data during installation killed the first two), and I thus
4737 decided to trust it with my data. I have installed it as a Debian Edu
4738 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4739 server at home using Kerberos and LDAP, and will use it as my work
4740 station from now on.&lt;/p&gt;
4741
4742 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
4743 Debian Wheezy default installation need to be tuned a bit to increase
4744 performance and increase life time of the disk. The Linux kernel and
4745 user space applications do not yet adjust automatically to such
4746 environment. To make it easier for my self, I created a draft Debian
4747 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
4748 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
4749 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
4750 is set up to adjust the setup of the machine by just installing the
4751 package. If there is any non-SSD disk in the machine, the package
4752 will refuse to install, as I did not try to write any logic to sort
4753 file systems in SSD and non-SSD file systems.&lt;/p&gt;
4754
4755 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
4756 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4757 where I set up the machine with one large encrypted partition (in
4758 addition to /boot), put LVM on top of this and set up partitions on
4759 top of this again. See the README file in the package source for the
4760 references I used to pick the settings. At the moment these
4761 parameters are tuned:&lt;/p&gt;
4762
4763 &lt;ul&gt;
4764
4765 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
4766 (adding discard to /etc/crypttab)&lt;/li&gt;
4767
4768 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
4769 this case a cryptsetup partition) by changing issue_discards from
4770 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
4771
4772 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
4773 systems.&lt;/li&gt;
4774
4775 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
4776 /etc/fstab.&lt;/li&gt;
4777
4778 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
4779
4780 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
4781 cron.daily).&lt;/li&gt;
4782
4783 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
4784 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
4785
4786 &lt;/ul&gt;
4787
4788 &lt;p&gt;During installation, I cancelled the part where the installer fill
4789 the disk with random data, as this would kill the SSD performance for
4790 little gain. My goal with the encrypted file system is to ensure
4791 those stealing my laptop end up with a brick and not a working
4792 computer. I have no hope in keeping the really resourceful people
4793 from getting the data on the disk (see
4794 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
4795 Thus I concluded that adding the discard option to crypttab is the
4796 right thing to do.&lt;/p&gt;
4797
4798 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
4799 it for SSD, but others recommended deadline and a benchmark I found
4800 indicated that deadline might be better for interactive use.&lt;/p&gt;
4801
4802 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
4803 and ext4, but read that it would give a performance hit ever time a
4804 file is removed, and thought it best to that that slowdown once a day
4805 instead of during my work.&lt;/p&gt;
4806
4807 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4808 this is already done by Debian Edu.&lt;/p&gt;
4809
4810 &lt;p&gt;I have not yet started on the user space tuning. I expect
4811 iceweasel need some tuning, and perhaps other applications too, but
4812 have not yet had time to investigate those parts.&lt;/p&gt;
4813
4814 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
4815 there.&lt;/p&gt;
4816
4817 &lt;p&gt;As for the answer to the question in the title of this blog post,
4818 as far as I know, the only solution I know about is to replace the
4819 disk. It might be possible to flash it with Intel firmware instead of
4820 the Lenovo firmware. But I have not tried and did not want to do so
4821 without approval from Lenovo as I wanted to keep the warranty on the
4822 disk until a solution was found and they wanted the broken disks
4823 back.&lt;/p&gt;
4824 </description>
4825 </item>
4826
4827 <item>
4828 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
4829 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
4830 <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>
4831 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
4832 <description>&lt;p&gt;A few days ago, I wrote about
4833 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
4834 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
4835 was dying during installation because it is unable to cope with
4836 sustained write. My supplier is in contact with
4837 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
4838 replacement disk to try to fix the problem. They decided to send an
4839 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
4840
4841 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
4842 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4843 same firmware version as the original. This time my hope raised
4844 slightly as the installation progressed, as the original disk used to
4845 die after 4-7% of the disk was written to, while this time it kept
4846 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
4847 died again and I was back on square one. I still do not have a new
4848 laptop with a disk I can trust. I can not live with a disk that might
4849 lock up when I download a new
4850 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
4851 other large files. I look forward to hearing from my supplier with
4852 the next proposal from Lenovo.&lt;/p&gt;
4853
4854 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
4855 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4856 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4857 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
4858 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4859 P/N 45N8295, P0C38732.&lt;/p&gt;
4860
4861 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
4862 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
4863 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
4864 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
4865 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
4866 P/N 45N8295, P0C38732.&lt;/p&gt;
4867
4868 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
4869 SA, date and WNPP values. Mentioning all the details here in case
4870 someone is able to use the information to find a way to identify the
4871 failing disk among working ones (if any such working disk actually
4872 exist).&lt;/p&gt;
4873 </description>
4874 </item>
4875
4876 <item>
4877 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
4878 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
4879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
4880 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
4881 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
4882 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4883 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
4884 member assosiation NUUG&lt;/a&gt; and
4885 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
4886 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
4887 Bitraf&lt;/a&gt;.&lt;/p&gt;
4888
4889 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
4890 welcome, and there is no fee to participate. There is on the other
4891 hand limited space, and only room for 30 people. Please put your name
4892 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
4893 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
4894 </description>
4895 </item>
4896
4897 <item>
4898 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
4899 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
4900 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
4901 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
4902 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
4903 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
4904 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
4905 time to spend on it, and it took a while to find a model I believe
4906 will do the job, but two days ago the replacement finally arrived. I
4907 ended up picking a
4908 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
4909 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4910 a roaming workstation, and it seemed to work flawlessly. But my
4911 second installation with encrypted disk was not as successful. More
4912 on that below.&lt;/p&gt;
4913
4914 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4915 important requirements (robust and with a good keyboard) are never
4916 listed in the feature list. But I did get good help from the search
4917 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4918 allowed me to limit the list of interesting laptops based on my other
4919 requirements. A bit surprising that SSD disk are not disks according
4920 to that search interface, so I had to drop specifying the number of
4921 disks from my search parameters. I also asked around among friends to
4922 get their impression on keyboards and robustness.&lt;/p&gt;
4923
4924 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
4925 X41. I am not quite convinced about the keyboard, as it is
4926 significantly wider than my old keyboard, and I have to stretch my
4927 hand a lot more to reach the edges. But the key response is fairly
4928 good and the individual key shape is fairly easy to handle, so I hope
4929 I will get used to it. My old X40 was starting to fail, and I really
4930 needed a new laptop now. :)&lt;/p&gt;
4931
4932 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
4933 visit to the BIOS during boot it disable it.&lt;/p&gt;
4934
4935 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
4936 lock up during load. And this happen when installing Debian Wheezy
4937 with encrypted disk, while the disk is being filled with random data.
4938 I also tested to install Ubuntu Raring, and it happen there too if I
4939 reenable the code to fill the disk with random data (it is disabled by
4940 default in Ubuntu). And the bug with is already known. It was
4941 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
4942 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
4943 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4944 kernel developers as
4945 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
4946 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
4947 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4948 Lenovo forums, both for
4949 &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
4950 2012-11-10&lt;/a&gt; and for
4951 &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
4952 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
4953 reports state that the disk lock up during use if many writes are done
4954 on the disk, so it is much no use to work around the installation
4955 problem and end up with a computer that can lock up at any moment.
4956 There is even a
4957 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
4958 available&lt;/a&gt; that will lock up the hard drive after running a few
4959 minutes by writing to a file.&lt;/p&gt;
4960
4961 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
4962 contacting PCHELP Norway (request 01D1FDP) which handle support
4963 requests for Lenovo, his first suggestion was to upgrade the disk
4964 firmware. Unfortunately there is no newer firmware available from
4965 Lenovo, as my disk already have the most recent one (version LF1i). I
4966 hope to hear more from him today and hope the problem can be
4967 fixed. :)&lt;/p&gt;
4968 </description>
4969 </item>
4970
4971 <item>
4972 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
4973 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
4974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
4975 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
4976 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
4977 trusty old Thinkpad X41. Unfortunately I did not have much time to
4978 spend on it, but today the replacement finally arrived. I ended up
4979 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
4980 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
4981 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4982 this, it is installing what I hope will be a more final installation,
4983 with a encrypted hard drive to ensure any dope head stealing it end up
4984 with an expencive door stop.&lt;/p&gt;
4985
4986 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4987 important requirements (robust and with a good keyboard) are never
4988 listed in the feature list. But I did get good help from the search
4989 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4990 allowed me to limit the list of interesting laptops based on my other
4991 requirements. A bit surprising that SSD disk are not disks, so I had
4992 to drop number of disks from my search parameters.&lt;/p&gt;
4993
4994 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
4995 wider than my old keyboard, and I have to stretch my hand a lot more
4996 to reach the edges. But the key response is fairly good and the
4997 individual key shape is fairly easy to handle, so I hope I will get
4998 used to it. My old X40 was starting to fail, and I really needed a
4999 new laptop now. :)&lt;/p&gt;
5000
5001 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
5002 </description>
5003 </item>
5004
5005 <item>
5006 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
5007 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
5008 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
5009 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
5010 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
5011 perfectly capable of, and I have to do it manually to get things
5012 working. One such task is to find out what firmware packages are
5013 needed to get the hardware on my computer working. Most often this
5014 affect the wifi card, but some times it even affect the RAID
5015 controller or the ethernet card. Today I pushed version 0.4 of the
5016 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
5017 including a new script isenkram-autoinstall-firmware handling the
5018 process of asking all the loaded kernel modules what firmware files
5019 they want, find debian packages providing these files and install the
5020 debian packages. Here is a test run on my laptop:&lt;/p&gt;
5021
5022 &lt;p&gt;&lt;pre&gt;
5023 # isenkram-autoinstall-firmware
5024 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5025 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5026 info: locating packages with the requested firmware files
5027 info: Updating APT sources after adding non-free APT source
5028 info: trying to install firmware-ipw2x00
5029 firmware-ipw2x00
5030 firmware-ipw2x00
5031 Preconfiguring packages ...
5032 Selecting previously deselected package firmware-ipw2x00.
5033 (Reading database ... 259727 files and directories currently installed.)
5034 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5035 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
5036 #
5037 &lt;/pre&gt;&lt;/p&gt;
5038
5039 &lt;p&gt;When all the requested firmware is present, a simple message is
5040 printed instead:&lt;/p&gt;
5041
5042 &lt;p&gt;&lt;pre&gt;
5043 # isenkram-autoinstall-firmware
5044 info: did not find any firmware files requested by loaded kernel modules. exiting
5045 #
5046 &lt;/pre&gt;&lt;/p&gt;
5047
5048 &lt;p&gt;It could use some polish, but it is already working well and saving
5049 me some time when setting up new machines. :)&lt;/p&gt;
5050
5051 &lt;p&gt;So, how does it work? It look at the set of currently loaded
5052 kernel modules, and look up each one of them using modinfo, to find
5053 the firmware files listed in the module meta-information. Next, it
5054 download the Contents file from a nearby APT mirror, and search for
5055 the firmware files in this file to locate the package with the
5056 requested firmware file. If the package is in the non-free section, a
5057 non-free APT source is added and the package is installed using
5058 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
5059 machine.&lt;/p&gt;
5060
5061 &lt;p&gt;I hope someone find time to implement a more polished version of
5062 this script as part of the hw-detect debian-installer module, to
5063 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
5064 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
5065 firmware during a PXE install when the packages already are available
5066 from the nearby Debian mirror.&lt;/p&gt;
5067 </description>
5068 </item>
5069
5070 <item>
5071 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
5072 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
5073 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
5074 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
5075 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5076 the screen just turn black when Linux boot, either during installation
5077 or on first boot from the hard disk. I&#39;ve seen it once in a while the
5078 last few years, but only recently understood the cause. I&#39;ve seen it
5079 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5080 The reason seem to be in the wiring of some laptops. The system to
5081 control the screen background light is inverted, so when Linux try to
5082 turn the brightness fully on, it end up turning it off instead. I do
5083 not know which Linux drivers are affected, but this post is about the
5084 i915 driver used by the
5085 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5086 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
5087
5088 &lt;p&gt;The problem can be worked around two ways. Either by adding
5089 i915.invert_brightness=1 as a kernel option, or by adding a file in
5090 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5091 option when it load the i915 kernel module. On Debian and Ubuntu, it
5092 can be done by running these commands as root:&lt;/p&gt;
5093
5094 &lt;pre&gt;
5095 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5096 update-initramfs -u -k all
5097 &lt;/pre&gt;
5098
5099 &lt;p&gt;Since March 2012 there is
5100 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5101 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5102 hardware have this problem, and get the driver to invert the
5103 brightness setting automatically. To use it, one need to add a row in
5104 &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
5105 intel_quirks array&lt;/a&gt; in the driver source
5106 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5107 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5108 number (vendor number 8086 is assumed) and subdevice vendor and device
5109 number.&lt;/p&gt;
5110
5111 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5112 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5113
5114 &lt;p&gt;&lt;pre&gt;
5115 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5116 3rd Gen Core processor Graphics Controller [8086:0156] \
5117 (rev 09) (prog-if 00 [VGA controller])
5118 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5119 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5120 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5121 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5122 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5123 Latency: 0
5124 Interrupt: pin A routed to IRQ 42
5125 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5126 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5127 Region 4: I/O ports at 4000 [size=64]
5128 Expansion ROM at &lt;unassigned&gt; [disabled]
5129 Capabilities: &lt;access denied&gt;
5130 Kernel driver in use: i915
5131 &lt;/pre&gt;&lt;/p&gt;
5132
5133 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5134
5135 &lt;p&gt;&lt;pre&gt;
5136 struct intel_quirk intel_quirks[] = {
5137 ...
5138 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5139 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5140 ...
5141 }
5142 &lt;/pre&gt;&lt;/p&gt;
5143
5144 &lt;p&gt;According to the kernel module instructions (as seen using
5145 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5146 invert_brightness flag should be sent to the
5147 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5148 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5149 developers. But my email about the laptop sent 2013-06-03 have not
5150 yet shown up in
5151 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5152 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5153 emails from non-subscribers. Because of this, I sent my patch also to
5154 the Debian bug tracking system instead as
5155 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5156 sure the patch is not lost.&lt;/p&gt;
5157
5158 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5159 with this problem working properly with Linux. If you use Gnome, your
5160 worries should be over at this point. But if you use KDE, there is
5161 something in KDE ignoring the invert_brightness setting and turning on
5162 the screen during login. I&#39;ve reported it to Debian as
5163 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5164 have no idea yet how to figure out exactly what subsystem is doing
5165 this. Perhaps you can help? Perhaps you know what the Gnome
5166 developers did to handle this, and this can give a clue to the KDE
5167 developers? Or you know where in KDE the screen brightness is changed
5168 during login? If so, please update the BTS report (or get in touch if
5169 you do not know how to update BTS).&lt;/p&gt;
5170
5171 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5172 acpi_backlight=vendor, to disable ACPI backlight support completely,
5173 as the ACPI information on the machine is trash and it is better to
5174 leave it to the intel video driver to control the screen
5175 backlight.&lt;/p&gt;
5176 </description>
5177 </item>
5178
5179 <item>
5180 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5181 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5182 <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>
5183 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5184 <description>&lt;p&gt;Two days ago, I asked
5185 &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
5186 I could install Linux on a Packard Bell EasyNote LV computer
5187 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5188 with the obstacles put in the way of Linux users on a laptop with UEFI
5189 and Windows 8.&lt;/p&gt;
5190
5191 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5192 secure booting or fast boot. I suspect fast boot was the problem,
5193 causing the firmware to boot directly from HD without considering any
5194 key presses and alternative devices, but do not know UEFI settings
5195 enough to tell.&lt;/p&gt;
5196
5197 &lt;p&gt;There is no way to install Linux on the machine in question without
5198 opening the box and disconnecting the hard drive! This is as far as I
5199 can tell, the only way to get access to the firmware setup menu
5200 without accepting the Windows 8 license agreement. I am told (and
5201 found description on how to) that it is possible to configure the
5202 firmware setup once booted into Windows 8. But as I believe the terms
5203 of that agreement are completely unacceptable, accepting the license
5204 was never an alternative. I do not enter agreements I do not intend
5205 to follow.&lt;/p&gt;
5206
5207 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
5208 waste many hours on this, but luckily there was a way to get it to
5209 work. But I would not recommend it to anyone planning to run Linux on
5210 it, and I have become sceptical to Windows 8 certified laptops. Is
5211 this the way Linux will be forced out of the market place, by making
5212 it close to impossible for &quot;normal&quot; users to install Linux without
5213 accepting the Microsoft Windows license terms? Or at least not
5214 without risking to loose the warranty?&lt;/p&gt;
5215
5216 &lt;p&gt;I&#39;ve updated the
5217 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
5218 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
5219 do not have to struggle as much as I did to get Linux into the
5220 machine.&lt;/p&gt;
5221
5222 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5223 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
5224 </description>
5225 </item>
5226
5227 <item>
5228 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
5229 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
5230 <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>
5231 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
5232 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
5233 new laptops for my parents and a few others. I bought Packard Bell
5234 Easynote LV to run Kubuntu on and use as their home computer. But I
5235 am completely unable to figure out how to install Linux on it. The
5236 computer is preinstalled with Windows 8, and I suspect it uses UEFI
5237 instead of a BIOS to boot.&lt;/p&gt;
5238
5239 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
5240 to get it to boot the Linux installer from my USB stick. I have yet
5241 to try the DVD install, and still hope it will work. when I turn on
5242 the computer, there is no information on what buttons to press to get
5243 the normal boot menu. I expect to get some boot menu to select PXE or
5244 USB stick booting. When booting, it first ask for the language to
5245 use, then for some regional settings, and finally if I will accept the
5246 Windows 8 terms of use. As these terms are completely unacceptable to
5247 me, I have no other choice but to turn off the computer and try again
5248 to get it to boot the Linux installer.&lt;/p&gt;
5249
5250 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
5251 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5252 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
5253 installed on this machine, please get in touch or update that wiki
5254 page. If I can&#39;t find a way to install Linux, I will have to return
5255 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
5256
5257 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
5258 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
5259 on new Laptops?&lt;/p&gt;
5260 </description>
5261 </item>
5262
5263 <item>
5264 <title>How to transform a Debian based system to a Debian Edu installation</title>
5265 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
5266 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
5267 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
5268 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
5269 an operating system based on Debian intended for use in schools. It
5270 contain a turn-key solution for the computer network provided to
5271 pupils in the primary schools. It provide both the central server,
5272 network boot servers and desktop environments with heaps of
5273 educational software. The project was founded almost 12 years ago,
5274 2001-07-02. If you want to support the project, which is in need for
5275 cash to fund developer gatherings and other project related activity,
5276 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
5277 donate some money&lt;/a&gt;.
5278
5279 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
5280 lists and elsewhere, is the question on how to transform a Debian or
5281 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
5282 hard, and last week I wrote a script to replicate the steps done by
5283 the Debian Edu installer.&lt;/p&gt;
5284
5285 &lt;p&gt;The script,
5286 &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;
5287 in the debian-edu-config package, will go through these six steps and
5288 transform an existing Debian Wheezy or Ubuntu (untested) installation
5289 into a Debian Edu Workstation:&lt;/p&gt;
5290
5291 &lt;ol&gt;
5292
5293 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
5294 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
5295 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
5296 our configuration.&lt;/li&gt;
5297 &lt;li&gt;Preseed debconf database with profile setup in
5298 /etc/debian-edu/config, and run tasksel to install packages
5299 according to the profile specified in the config above,
5300 overriding some of the Debian automation machinery.&lt;/li&gt;
5301 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
5302 that could not be done using preseeding.&lt;/li&gt;
5303 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
5304
5305 &lt;/ol&gt;
5306
5307 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
5308 replicated like this. Disk partitioning and LVM setup, for example.
5309 So this script just assume there is enough disk space to install all
5310 the needed packages.&lt;/p&gt;
5311
5312 &lt;p&gt;The script was created to help a Debian Edu student working on
5313 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
5314 Debian Edu client, and using it he can take the existing
5315 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
5316 transform it into a fully functioning Debian Edu Workstation (or
5317 Roaming Workstation, or whatever :).&lt;/p&gt;
5318
5319 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
5320 If a LXDE based Roaming workstation is wanted instead, modify the
5321 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
5322
5323 &lt;p&gt;&lt;pre&gt;
5324 PROFILE=&quot;Roaming-Workstation&quot;
5325 DESKTOP=&quot;lxde&quot;
5326 &lt;/pre&gt;&lt;/p&gt;
5327
5328 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
5329 the cloud, by starting with a virtual Debian installation at some
5330 virtual hosting service and setting up all the services on first
5331 boot.&lt;/p&gt;
5332 </description>
5333 </item>
5334
5335 <item>
5336 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
5337 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
5338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
5339 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
5340 <description>&lt;P&gt;In January,
5341 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
5342 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
5343 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
5344 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
5345 marvellous construction system from Denmark. We also created
5346 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
5347 a place to take notes and write down our plans and hopes. And several
5348 people showed up to help. I was very happy to see the effect of my
5349 call. Since the small start, we have a debtags tag
5350 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
5351 tag for LEGO related packages, and now count 10 packages related to
5352 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
5353
5354 &lt;p&gt;&lt;table&gt;
5355 &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;
5356 &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;
5357 &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;
5358 &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;
5359 &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;
5360 &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;
5361 &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;
5362 &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;
5363 &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;
5364 &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;
5365 &lt;/table&gt;&lt;/p&gt;
5366
5367 &lt;p&gt;Some of these are available in Wheezy, and all but one are
5368 currently available in Jessie/testing. leocad is so far only
5369 available in experimental.&lt;/p&gt;
5370
5371 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
5372 adding the rest of the great free software tools available on Linux
5373 for LEGO designers.&lt;/p&gt;
5374 </description>
5375 </item>
5376
5377 <item>
5378 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
5379 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
5380 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
5381 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
5382 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
5383 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
5384 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
5385 Debian release, and I expect to move my machines at home over to it fairly
5386 soon.&lt;/p&gt;
5387
5388 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
5389 in particular make me very happy to see included. The
5390 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
5391 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
5392 included for the first time. Alongside similar programs like
5393 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5394 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5395 it allow for visual programming where syntax errors can not happen,
5396 and a friendly programming environment for learning to control the
5397 computer. Scratch will also be included in the next release of Debian
5398 Edu.&lt;/a&gt;
5399
5400 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5401 Edu/Skolelinux release too. The
5402 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5403 alpha release&lt;/a&gt; went out last week, and the next should soon
5404 follow.&lt;p&gt;
5405 </description>
5406 </item>
5407
5408 <item>
5409 <title>Isenkram 0.2 finally in the Debian archive</title>
5410 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5412 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5413 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5414 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5415 for many months. I uploaded it to the Debian experimental suite
5416 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5417
5418 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5419 install to work with a pluggable hardware device. The suggestion pop
5420 up when the device is plugged in. For example if a Lego Mindstorm NXT
5421 is inserted, it will suggest to install the program needed to program
5422 the NXT controller. Give it a go, and report bugs and suggestions to
5423 BTS. :)&lt;/p&gt;
5424 </description>
5425 </item>
5426
5427 <item>
5428 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5429 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5431 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5432 <description>&lt;p&gt;My
5433 &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
5434 bitcoin related blog post&lt;/a&gt; mentioned that the new
5435 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5436 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5437 2013-01-19, and have been available in unstable since then. It was
5438 automatically copied to Ubuntu, and is available in their Raring
5439 version too.&lt;/p&gt;
5440
5441 &lt;p&gt;But there is a strange problem with the build that block this new
5442 version from being available on the i386 and kfreebsd-i386
5443 architectures. For some strange reason, the autobuilders in Debian
5444 for these architectures fail to run the test suite on these
5445 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5446 We are so far unable to reproduce it when building it manually, and
5447 no-one have been able to propose a fix. If you got an idea what is
5448 failing, please let us know via the BTS.&lt;/p&gt;
5449
5450 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5451 I often run low on disk space, is the fact that the client will exit
5452 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5453 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5454 it. :)&lt;/p&gt;
5455
5456 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5457 activities, please send Bitcoin donations to my address
5458 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5459 </description>
5460 </item>
5461
5462 <item>
5463 <title>Welcome to the world, Isenkram!</title>
5464 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5465 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5466 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5467 <description>&lt;p&gt;Yesterday, I
5468 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5469 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5470 pluggable hardware devices, which I
5471 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5472 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5473 up, and caused me to really want to to open up the development to more
5474 people. But before I did this, I want to come up with a sensible name
5475 for this project. Today I finally decided on a new name, and I have
5476 renamed the project from hw-support-handler to this new name. In the
5477 process, I moved the source to git and made it available as a
5478 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5479 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5480 To fetch and build the latest version of the source, use&lt;/p&gt;
5481
5482 &lt;pre&gt;
5483 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5484 cd isenkram &amp;&amp; git-buildpackage -us -uc
5485 &lt;/pre&gt;
5486
5487 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5488 want to hack on the source or improve the package, please go ahead.
5489 But please talk to me first on IRC or via email before you do major
5490 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5491
5492 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5493 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5494 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5495 the German word eisenkram, for those that are familiar with that
5496 word.&lt;/p&gt;
5497
5498 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5499 instructions, to avoid confusing people with an error from the signing
5500 process.&lt;/p&gt;
5501
5502 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5503 clone argument to avoid the need for authentication.&lt;/p&gt;
5504 </description>
5505 </item>
5506
5507 <item>
5508 <title>First prototype ready making hardware easier to use in Debian</title>
5509 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5511 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5512 <description>&lt;p&gt;Early this month I set out to try to
5513 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5514 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5515 prototype is working, and it is ready for a larger audience. To test
5516 it, fetch the
5517 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5518 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5519 package. You might have to log out and in again activate the
5520 autostart script.&lt;/p&gt;
5521
5522 &lt;p&gt;The design is simple:&lt;/p&gt;
5523
5524 &lt;ul&gt;
5525
5526 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5527 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5528
5529 &lt;li&gt;This program listen for kernel events about new hardware (directly
5530 from the kernel like udev does), not using HAL dbus events as I
5531 initially did.&lt;/li&gt;
5532
5533 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5534 the APT database, a database
5535 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5536 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5537
5538 &lt;li&gt;If a package is mapped to the hardware in question, the package
5539 isn&#39;t installed yet and this is the first time the hardware was
5540 plugged in, show a desktop notification suggesting to install the
5541 package or packages.&lt;/li&gt;
5542
5543 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5544 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5545
5546 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5547 package while showing progress information in a window.&lt;/li&gt;
5548
5549 &lt;/ul&gt;
5550
5551 &lt;p&gt;I still need to come up with a better name for the system. Here
5552 are some screen shots showing the prototype in action. First the
5553 notification, then the password request, and finally the request to
5554 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5555
5556 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5557 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5558 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5559 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5560 &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;
5561
5562 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5563 is already useful. The database of hardware to package mappings also
5564 need more work. It is currently compatible with the Ubuntu way of
5565 storing such information in the package control file, but could be
5566 changed to use other formats instead or in addition to the current
5567 method. I&#39;ve dropped the use of discover for this mapping, as the
5568 modalias approach is more flexible and easier to use on Linux as long
5569 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5570
5571 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5572 here is the command required to check out and build the source: Use
5573 &#39;&lt;tt&gt;svn checkout
5574 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5575 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5576 devscripts package.&lt;/p&gt;
5577
5578 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5579 renamed to Isenkram and the source moved from the Debian Edu
5580 subversion repository to a Debian collab-maint git repository. See
5581 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5582 instructions&lt;/a&gt; for details.&lt;/p&gt;
5583 </description>
5584 </item>
5585
5586 <item>
5587 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5588 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5590 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5591 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5592 suddenly in bed. With a quiet whimper, it went completely quiet and
5593 black. The power button was no longer able to turn it on. It was a
5594 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5595 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5596 Compaq I had before that. Now I need to find a replacement. To keep
5597 going during Christmas, I moved the one year old SSD disk to my old
5598 X40 where it fitted (only one I had left that could use it), but it is
5599 not a durable solution.
5600
5601 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5602 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5603
5604 &lt;ul&gt;
5605
5606 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5607 than A4).&lt;/li&gt;
5608 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5609 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5610 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5611 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5612 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5613 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5614 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5615 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5616 size).&lt;/li&gt;
5617 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5618 X.org packages.&lt;/li&gt;
5619 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5620 the time).
5621
5622 &lt;/ul&gt;
5623
5624 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
5625 list. The reason is simply that the specifications on laptops the
5626 last 10-15 years have been sufficient for my needs, and I have to look
5627 at other features to choose my laptop. But are there still made as
5628 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5629 robust, and Thinkpads seem to be heading in the wrong direction since
5630 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
5631 still be useful.&lt;/p&gt;
5632
5633 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
5634 external keyboard? I&#39;ll have to check the
5635 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
5636 well-supported laptops, or perhaps just buy one preinstalled from one
5637 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
5638 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
5639 </description>
5640 </item>
5641
5642 <item>
5643 <title>How to find a browser plugin supporting a given MIME type</title>
5644 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
5645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
5646 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
5647 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
5648 install to get support for a given MIME type. Thanks to
5649 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
5650 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
5651 Unfortunately, not very many packages provide the needed meta
5652 information, Anyway, here is a small script to look up all browser
5653 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
5654
5655 &lt;pre&gt;
5656 #!/usr/bin/python
5657 import sys
5658 import apt
5659 def pkgs_handling_mimetype(mimetype):
5660 cache = apt.Cache()
5661 cache.open(None)
5662 thepkgs = []
5663 for pkg in cache:
5664 version = pkg.candidate
5665 if version is None:
5666 version = pkg.installed
5667 if version is None:
5668 continue
5669 record = version.record
5670 if not record.has_key(&#39;Npp-MimeType&#39;):
5671 continue
5672 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
5673 for t in mime_types:
5674 t = t.rstrip().strip()
5675 if t == mimetype:
5676 thepkgs.append(pkg.name)
5677 return thepkgs
5678 mimetype = &quot;audio/ogg&quot;
5679 if 1 &lt; len(sys.argv):
5680 mimetype = sys.argv[1]
5681 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
5682 for pkg in pkgs_handling_mimetype(mimetype):
5683 print &quot; %s&quot; %pkg
5684 &lt;/pre&gt;
5685
5686 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
5687
5688 &lt;pre&gt;
5689 % ./apt-find-browserplug-for-mimetype
5690 Browser plugin packages supporting audio/ogg:
5691 gecko-mediaplayer
5692 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5693 Browser plugin packages supporting application/x-shockwave-flash:
5694 browser-plugin-gnash
5695 %
5696 &lt;/pre&gt;
5697
5698 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
5699 itself to query for plugins and propose to install the needed
5700 packages. It would be great if Debian supported such feature too. Is
5701 anyone working on adding it?&lt;/p&gt;
5702
5703 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
5704 request for icweasel support for this feature is
5705 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
5706 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
5707 of manpower and wish for a different design is the reason thus feature
5708 is not yet in iceweasel from Debian.&lt;/p&gt;
5709 </description>
5710 </item>
5711
5712 <item>
5713 <title>What is the most supported MIME type in Debian?</title>
5714 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
5715 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
5716 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
5717 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
5718 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
5719 proposal to make it possible for a Desktop application to propose to
5720 the user some package to install to gain support for a given MIME
5721 type, font, library etc. that is currently missing. With such
5722 mechanism in place, it would be possible for the desktop to
5723 automatically propose and install leocad if some LDraw file is
5724 downloaded by the browser.&lt;/p&gt;
5725
5726 &lt;p&gt;To get some idea about the current content of the archive, I decided
5727 to write a simple program to extract all .desktop files from the
5728 Debian archive and look up the claimed MIME support there. The result
5729 can be found on the
5730 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
5731 site&lt;/a&gt;. Using the collected information, it become possible to
5732 answer the question in the title. Here are the 20 most supported MIME
5733 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5734 The complete list is available from the link above.&lt;/p&gt;
5735
5736 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
5737
5738 &lt;pre&gt;
5739 count MIME type
5740 ----- -----------------------
5741 32 text/plain
5742 30 audio/mpeg
5743 29 image/png
5744 28 image/jpeg
5745 27 application/ogg
5746 26 audio/x-mp3
5747 25 image/tiff
5748 25 image/gif
5749 22 image/bmp
5750 22 audio/x-wav
5751 20 audio/x-flac
5752 19 audio/x-mpegurl
5753 18 video/x-ms-asf
5754 18 audio/x-musepack
5755 18 audio/x-mpeg
5756 18 application/x-ogg
5757 17 video/mpeg
5758 17 audio/x-scpls
5759 17 audio/ogg
5760 16 video/x-ms-wmv
5761 &lt;/pre&gt;
5762
5763 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
5764
5765 &lt;pre&gt;
5766 count MIME type
5767 ----- -----------------------
5768 33 text/plain
5769 32 image/png
5770 32 image/jpeg
5771 29 audio/mpeg
5772 27 image/gif
5773 26 image/tiff
5774 26 application/ogg
5775 25 audio/x-mp3
5776 22 image/bmp
5777 21 audio/x-wav
5778 19 audio/x-mpegurl
5779 19 audio/x-mpeg
5780 18 video/mpeg
5781 18 audio/x-scpls
5782 18 audio/x-flac
5783 18 application/x-ogg
5784 17 video/x-ms-asf
5785 17 text/html
5786 17 audio/x-musepack
5787 16 image/x-xbitmap
5788 &lt;/pre&gt;
5789
5790 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
5791
5792 &lt;pre&gt;
5793 count MIME type
5794 ----- -----------------------
5795 31 text/plain
5796 31 image/png
5797 31 image/jpeg
5798 29 audio/mpeg
5799 28 application/ogg
5800 27 image/gif
5801 26 image/tiff
5802 26 audio/x-mp3
5803 23 audio/x-wav
5804 22 image/bmp
5805 21 audio/x-flac
5806 20 audio/x-mpegurl
5807 19 audio/x-mpeg
5808 18 video/x-ms-asf
5809 18 video/mpeg
5810 18 audio/x-scpls
5811 18 application/x-ogg
5812 17 audio/x-musepack
5813 16 video/x-ms-wmv
5814 16 video/x-msvideo
5815 &lt;/pre&gt;
5816
5817 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
5818 information mentioned in DEP-11. I have not yet had time to look at
5819 it, but hope the PackageKit people in Debian are on top of these
5820 issues.&lt;/p&gt;
5821
5822 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
5823 discovering a typo in my script.&lt;/p&gt;
5824 </description>
5825 </item>
5826
5827 <item>
5828 <title>Using modalias info to find packages handling my hardware</title>
5829 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
5830 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
5831 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
5832 <description>&lt;p&gt;Yesterday, I wrote about the
5833 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
5834 values provided by the Linux kernel&lt;/a&gt; following my hope for
5835 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
5836 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
5837 modalias values attached to package names can be used to map packages
5838 to hardware. This allow the system to look up and suggest relevant
5839 packages when I plug in some new hardware into my machine, and replace
5840 discover and discover-data as the database used to map hardware to
5841 packages.&lt;/p&gt;
5842
5843 &lt;p&gt;I create a modaliases file with entries like the following,
5844 containing package name, kernel module name (if relevant, otherwise
5845 the package name) and globs matching the relevant hardware
5846 modalias.&lt;/p&gt;
5847
5848 &lt;p&gt;&lt;blockquote&gt;
5849 Package: package-name
5850 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
5851 &lt;/blockquote&gt;&lt;/p&gt;
5852
5853 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
5854 for a given modalias value using this file.&lt;/p&gt;
5855
5856 &lt;p&gt;An entry like this would suggest the video and picture application
5857 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
5858
5859 &lt;p&gt;&lt;blockquote&gt;
5860 Package: cheese
5861 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
5862 &lt;/blockquote&gt;&lt;/p&gt;
5863
5864 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
5865 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
5866
5867 &lt;p&gt;&lt;blockquote&gt;
5868 Package: pcmciautils
5869 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5870 &lt;/blockquote&gt;&lt;/p&gt;
5871
5872 &lt;p&gt;An entry like this would suggest the package colorhug-client when
5873 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
5874
5875 &lt;p&gt;&lt;blockquote&gt;
5876 Package: colorhug-client
5877 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
5878 &lt;/blockquote&gt;&lt;/p&gt;
5879
5880 &lt;p&gt;I believe the format is compatible with the format of the Packages
5881 file in the Debian archive. Ubuntu already uses their Packages file
5882 to store their mappings from packages to hardware.&lt;/p&gt;
5883
5884 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
5885 announce the hardware it support in a way my prototype understand.
5886 This allow those publishing packages in an APT source outside the
5887 Debian archive as well as those backporting packages to make sure the
5888 hardware mapping are included in the package meta information. I&#39;ve
5889 tested such header in the pymissile package, and its modalias mapping
5890 is working as it should with my prototype. It even made it to Ubuntu
5891 Raring.&lt;/p&gt;
5892
5893 &lt;p&gt;To test if it was possible to look up supported hardware using only
5894 the shell tools available in the Debian installer, I wrote a shell
5895 implementation of the lookup code. The idea is to create files for
5896 each modalias and let the shell do the matching. Please check out and
5897 try the
5898 &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;
5899 shell script. It run without any extra dependencies and fetch the
5900 hardware mappings from the Debian archive and the subversion
5901 repository where I currently work on my prototype.&lt;/p&gt;
5902
5903 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
5904 install yubikey-personalization:&lt;/p&gt;
5905
5906 &lt;p&gt;&lt;blockquote&gt;
5907 % ./hw-support-lookup
5908 &lt;br&gt;yubikey-personalization
5909 &lt;br&gt;%
5910 &lt;/blockquote&gt;&lt;/p&gt;
5911
5912 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5913 propose to install the pcmciautils package:&lt;/p&gt;
5914
5915 &lt;p&gt;&lt;blockquote&gt;
5916 % ./hw-support-lookup
5917 &lt;br&gt;pcmciautils
5918 &lt;br&gt;%
5919 &lt;/blockquote&gt;&lt;/p&gt;
5920
5921 &lt;p&gt;If you know of any hardware-package mapping that should be added to
5922 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
5923 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
5924
5925 &lt;p&gt;It could be possible to generate several of the mappings between
5926 packages and hardware. One source would be to look at packages with
5927 kernel modules, ie packages with *.ko files in /lib/modules/, and
5928 extract their modalias information. Another would be to look at
5929 packages with udev rules, ie packages with files in
5930 /lib/udev/rules.d/, and extract their vendor/model information to
5931 generate a modalias matching rule. I have not tested any of these to
5932 see if it work.&lt;/p&gt;
5933
5934 &lt;p&gt;If you want to help implementing a system to let us propose what
5935 packages to install when new hardware is plugged into a Debian
5936 machine, please send me an email or talk to me on
5937 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5938 </description>
5939 </item>
5940
5941 <item>
5942 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
5943 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
5944 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
5945 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
5946 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
5947 information, to find the packages that support a given piece of
5948 hardware, I refreshed my memory regarding modalias values, and decided
5949 to document the details. Here are my findings so far, also available
5950 in
5951 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5952 Debian Edu subversion repository&lt;/a&gt;:
5953
5954 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
5955
5956 &lt;p&gt;This document try to explain what the different types of modalias
5957 values stands for. It is in part based on information from
5958 &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;,
5959 &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;,
5960 &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
5961 &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;.
5962
5963 &lt;p&gt;The modalias entries for a given Linux machine can be found using
5964 this shell script:&lt;/p&gt;
5965
5966 &lt;pre&gt;
5967 find /sys -name modalias -print0 | xargs -0 cat | sort -u
5968 &lt;/pre&gt;
5969
5970 &lt;p&gt;The supported modalias globs for a given kernel module can be found
5971 using modinfo:&lt;/p&gt;
5972
5973 &lt;pre&gt;
5974 % /sbin/modinfo psmouse | grep alias:
5975 alias: serio:ty05pr*id*ex*
5976 alias: serio:ty01pr*id*ex*
5977 %
5978 &lt;/pre&gt;
5979
5980 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
5981
5982 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
5983 Bridge memory controller:&lt;/p&gt;
5984
5985 &lt;p&gt;&lt;blockquote&gt;
5986 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5987 &lt;/blockquote&gt;&lt;/p&gt;
5988
5989 &lt;p&gt;This represent these values:&lt;/p&gt;
5990
5991 &lt;pre&gt;
5992 v 00008086 (vendor)
5993 d 00002770 (device)
5994 sv 00001028 (subvendor)
5995 sd 000001AD (subdevice)
5996 bc 06 (bus class)
5997 sc 00 (bus subclass)
5998 i 00 (interface)
5999 &lt;/pre&gt;
6000
6001 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
6002 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
6003 0600. The 0600 class is a host bridge. Other useful bus values are
6004 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
6005
6006 &lt;p&gt;Not sure how to figure out the interface value, nor what it
6007 means.&lt;/p&gt;
6008
6009 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
6010
6011 &lt;p&gt;Some typical USB entries can look like this. This is an internal
6012 USB hub in a laptop:&lt;/p&gt;
6013
6014 &lt;p&gt;&lt;blockquote&gt;
6015 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6016 &lt;/blockquote&gt;&lt;/p&gt;
6017
6018 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
6019
6020 &lt;pre&gt;
6021 v 1D6B (device vendor)
6022 p 0001 (device product)
6023 d 0206 (bcddevice)
6024 dc 09 (device class)
6025 dsc 00 (device subclass)
6026 dp 00 (device protocol)
6027 ic 09 (interface class)
6028 isc 00 (interface subclass)
6029 ip 00 (interface protocol)
6030 &lt;/pre&gt;
6031
6032 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
6033 class is in the interface class section. For a simple USB web camera,
6034 these alias entries show up:&lt;/p&gt;
6035
6036 &lt;p&gt;&lt;blockquote&gt;
6037 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6038 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6039 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6040 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6041 &lt;/blockquote&gt;&lt;/p&gt;
6042
6043 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
6044 camera), 0101 is audio control device and 0102 is audio streaming (aka
6045 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
6046
6047 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
6048
6049 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
6050 receiver in a Thinkpad X40:&lt;/p&gt;
6051
6052 &lt;p&gt;&lt;blockquote&gt;
6053 acpi:IBM0071:PNP0511:
6054 &lt;/blockquote&gt;&lt;/p&gt;
6055
6056 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
6057
6058 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
6059
6060 &lt;p&gt;The DMI table contain lots of information about the computer case
6061 and model. This is an entry for a IBM Thinkpad X40, fetched from
6062 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
6063
6064 &lt;p&gt;&lt;blockquote&gt;
6065 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6066 &lt;/blockquote&gt;&lt;/p&gt;
6067
6068 &lt;p&gt;The values present are&lt;/p&gt;
6069
6070 &lt;pre&gt;
6071 bvn IBM (BIOS vendor)
6072 bvr 1UETB6WW(1.66) (BIOS version)
6073 bd 06/15/2005 (BIOS date)
6074 svn IBM (system vendor)
6075 pn 2371H4G (product name)
6076 pvr ThinkPadX40 (product version)
6077 rvn IBM (board vendor)
6078 rn 2371H4G (board name)
6079 rvr NotAvailable (board version)
6080 cvn IBM (chassis vendor)
6081 ct 10 (chassis type)
6082 cvr NotAvailable (chassis version)
6083 &lt;/pre&gt;
6084
6085 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
6086 found in the dmidecode source:&lt;/p&gt;
6087
6088 &lt;pre&gt;
6089 3 Desktop
6090 4 Low Profile Desktop
6091 5 Pizza Box
6092 6 Mini Tower
6093 7 Tower
6094 8 Portable
6095 9 Laptop
6096 10 Notebook
6097 11 Hand Held
6098 12 Docking Station
6099 13 All In One
6100 14 Sub Notebook
6101 15 Space-saving
6102 16 Lunch Box
6103 17 Main Server Chassis
6104 18 Expansion Chassis
6105 19 Sub Chassis
6106 20 Bus Expansion Chassis
6107 21 Peripheral Chassis
6108 22 RAID Chassis
6109 23 Rack Mount Chassis
6110 24 Sealed-case PC
6111 25 Multi-system
6112 26 CompactPCI
6113 27 AdvancedTCA
6114 28 Blade
6115 29 Blade Enclosing
6116 &lt;/pre&gt;
6117
6118 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6119 table. For example my home server is a tower, but the DMI modalias
6120 claim it is a desktop.&lt;/p&gt;
6121
6122 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6123
6124 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6125 test machine:&lt;/p&gt;
6126
6127 &lt;p&gt;&lt;blockquote&gt;
6128 serio:ty01pr00id00ex00
6129 &lt;/blockquote&gt;&lt;/p&gt;
6130
6131 &lt;p&gt;The values present are&lt;/p&gt;
6132
6133 &lt;pre&gt;
6134 ty 01 (type)
6135 pr 00 (prototype)
6136 id 00 (id)
6137 ex 00 (extra)
6138 &lt;/pre&gt;
6139
6140 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6141 the valid values are.&lt;/p&gt;
6142
6143 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6144
6145 &lt;p&gt;There are heaps of other modalias subtypes according to
6146 file2alias.c. There is the rest of the list from that source: amba,
6147 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6148 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6149 vmbus, x86cpu and zorro. I did not spend time documenting all of
6150 these, as they do not seem relevant for my intended use with mapping
6151 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6152
6153 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6154
6155 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6156 one can use the following shell script:&lt;/p&gt;
6157
6158 &lt;pre&gt;
6159 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6160 echo &quot;$id&quot; ; \
6161 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6162 done
6163 &lt;/pre&gt;
6164
6165 &lt;p&gt;The output can look like this (only the first few entries as the
6166 list is very long on my test machine):&lt;/p&gt;
6167
6168 &lt;pre&gt;
6169 acpi:ACPI0003:
6170 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6171 acpi:device:
6172 FATAL: Module acpi:device: not found.
6173 acpi:IBM0068:
6174 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6175 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6176 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6177 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6178 acpi:IBM0071:PNP0511:
6179 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6180 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6181 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6182 [...]
6183 &lt;/pre&gt;
6184
6185 &lt;p&gt;If you want to help implementing a system to let us propose what
6186 packages to install when new hardware is plugged into a Debian
6187 machine, please send me an email or talk to me on
6188 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6189
6190 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6191 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6192 in /sys/ with space in them.&lt;/p&gt;
6193 </description>
6194 </item>
6195
6196 <item>
6197 <title>Moved the pymissile Debian packaging to collab-maint</title>
6198 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
6199 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
6200 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
6201 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
6202 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6203 Launcher and updated the Debian package
6204 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
6205 sure udev will fix the device permissions when it is plugged in. I
6206 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
6207 hopefully make the package be proposed by jockey in Ubuntu when a user
6208 plug in his rocket launcher. In the process I moved the source to a
6209 git repository under collab-maint, to make it easier for any DD to
6210 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
6211 is not very active, but the software still work for me even after five
6212 years of relative silence. The new git repository is not listed in
6213 the uploaded package yet, because I want to test the other changes a
6214 bit more before I upload the new version. If you want to check out
6215 the new version with a .desktop file included, visit the
6216 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
6217 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
6218 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
6219 </description>
6220 </item>
6221
6222 <item>
6223 <title>Lets make hardware dongles easier to use in Debian</title>
6224 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
6225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
6226 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
6227 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
6228 general, is that there is a great package management system with the
6229 ability to automatically install software packages by downloading them
6230 from the distribution mirrors, but no way to get it to automatically
6231 install the packages I need to use the hardware I plug into my
6232 machine. Even if the package to use it is easily available from the
6233 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6234 suggest to automatically install the python-nxt, nbc and t2n packages
6235 I need to talk to it. When I plug in a Yubikey, it could propose the
6236 yubikey-personalization package. The information required to do this
6237 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
6238
6239 &lt;p&gt;Some years ago, I proposed to
6240 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
6241 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
6242 simple:
6243
6244 &lt;ul&gt;
6245
6246 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
6247 starting when a user log in.&lt;/li&gt;
6248
6249 &lt;li&gt;Set this program up to listen for kernel events emitted when new
6250 hardware is inserted into the computer.&lt;/li&gt;
6251
6252 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
6253 database mapping to packages, and take note of any non-installed
6254 packages.&lt;/li&gt;
6255
6256 &lt;li&gt;Show a message to the user proposing to install the discovered
6257 package, and make it easy to install it.&lt;/li&gt;
6258
6259 &lt;/ul&gt;
6260
6261 &lt;p&gt;I am not sure what the best way to implement this is, but my
6262 initial idea was to use dbus events to discover new hardware, the
6263 discover database to find packages and
6264 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
6265 packages.&lt;/p&gt;
6266
6267 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
6268 draft package is now checked into
6269 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6270 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
6271 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
6272 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6273 the relevant packages in Debian, and uploaded a new version
6274 2.2013.01.09 to unstable. I also discovered that the current
6275 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
6276 package in Debian no longer discovered any USB devices, because
6277 /proc/bus/usb/devices is no longer present. I ported it to use
6278 libusb as a fall back option to get it working. The fixed package
6279 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
6280 because of the freeze).&lt;/p&gt;
6281
6282 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
6283 desktop notification to show up (only once, the first time it is
6284 inserted):&lt;/p&gt;
6285
6286 &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;
6287
6288 &lt;p&gt;For this prototype to be really useful, some way to automatically
6289 install the proposed packages by pressing the &quot;Please install
6290 program(s)&quot; button should to be implemented.&lt;/p&gt;
6291
6292 &lt;p&gt;If this idea seem useful to you, and you want to help make it
6293 happen, please help me update the discover-data database with mappings
6294 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
6295 list the package you would like to have installed when a given
6296 hardware device is inserted into your computer, and report bugs using
6297 reportbug if it isn&#39;t. Or, if you know of a better way to provide
6298 such mapping, please let me know.&lt;/p&gt;
6299
6300 &lt;p&gt;This prototype need more work, and there are several questions that
6301 should be considered before it is ready for production use. Is dbus
6302 the correct way to detect new hardware? At the moment I look for HAL
6303 dbus events on the system bus, because that is the events I could see
6304 on my Debian Squeeze KDE desktop. Are there better events to use?
6305 How should the user be notified? Is the desktop notification
6306 mechanism the best option, or should the background daemon raise a
6307 popup instead? How should packages be installed? When should they
6308 not be installed?&lt;/p&gt;
6309
6310 &lt;p&gt;If you want to help getting such feature implemented in Debian,
6311 please send me an email. :)&lt;/p&gt;
6312 </description>
6313 </item>
6314
6315 <item>
6316 <title>New IRC channel for LEGO designers using Debian</title>
6317 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
6318 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
6319 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
6320 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
6321 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
6322 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
6323 discovered I had to build all the tools myself because none were
6324 already in Debian Squeeze. If Debian support for LEGO is something
6325 you care about, please join me on the IRC channel
6326 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
6327 irc.debian.org). There is a lot that could be done to improve the
6328 Debian support for LEGO designers. For example both CAD software
6329 and Mindstorm compilers are missing. :)&lt;/p&gt;
6330
6331 &lt;p&gt;Update 2012-01-03: A
6332 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
6333 including links to Lego related packages is now available.&lt;/p&gt;
6334 </description>
6335 </item>
6336
6337 <item>
6338 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
6339 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
6340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
6341 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
6342 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
6343 year! I hope next year will prove to be a good year.&lt;/p&gt;
6344
6345 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
6346 decentralised &quot;currency&quot; that allow people to transfer bitcoins
6347 between each other with minimal overhead, is a very interesting
6348 experiment. And as I wrote a few days ago, the bitcoin situation in
6349 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
6350 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
6351 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
6352 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
6353 for one of the ftpmasters to approve the new bitcoin-qt package
6354 name.&lt;/p&gt;
6355
6356 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
6357 team in Debian, you can easily test the package in Debian Squeeze
6358 using the following steps to get a set of working packages:&lt;/p&gt;
6359
6360 &lt;blockquote&gt;&lt;pre&gt;
6361 git clone git://git.debian.org/git/collab-maint/bitcoin
6362 cd bitcoin
6363 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6364 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6365 &lt;/pre&gt;&lt;/blockquote&gt;
6366
6367 &lt;p&gt;You might have to install some build dependencies as well. The
6368 list of commands should give you two packages, bitcoind and
6369 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6370 client will download the complete set of bitcoin &quot;blocks&quot;, which need
6371 around 5.6 GiB of data on my machine at the moment. Make sure your
6372 ~/.bitcoin/ directory have lots of spare room if you want to download
6373 all the blocks. The client will warn if the disk is getting full, so
6374 there is not really a problem if you got too little room, but you will
6375 not be able to get all the features out of the client.&lt;/p&gt;
6376
6377 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6378 activities, please send Bitcoin donations to my address
6379 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6380 </description>
6381 </item>
6382
6383 <item>
6384 <title>A word on bitcoin support in Debian</title>
6385 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
6386 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
6387 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
6388 <description>&lt;p&gt;It has been a while since I wrote about
6389 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
6390 peer-to-peer based crypto-currency, and the reason is simply that I
6391 have been busy elsewhere. But two days ago, I started looking at the
6392 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
6393 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6394 is now maintained by a
6395 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6396 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6397 owe a huge thank you to all these team members. :)
6398 But I was sad to discover that the bitcoin client is missing in
6399 Wheezy. It is only available in Sid (and an outdated client from
6400 backports). The client had several RC bugs registered in BTS blocking
6401 it from entering testing. To try to help the team and improve the
6402 situation, I spent some time providing patches and triaging the bug
6403 reports. I also had a look at the bitcoin package available from Matt
6404 Corallo in a
6405 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6406 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6407 Debian package.&lt;/p&gt;
6408
6409 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6410 IRC, I pushed several patches into the collab-maint git repository to
6411 improve the package. It now contains fixes for the RC issues (not from
6412 me, but fixed by Scott Howard), build rules for a Qt GUI client
6413 package, konqueror support for the bitcoin: URI and bash completion
6414 setup. As I work on Debian Squeeze, I also created
6415 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6416 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6417 it and try to integrate it into the git repository before uploading a
6418 new version to unstable.
6419
6420 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6421 centralized control currently exercised in the monetary system. I
6422 find it completely unacceptable that the USA government is collecting
6423 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6424 that the major credit card companies can block legal money
6425 transactions to Wikileaks. But for bitcoin to succeed, more people
6426 need to use bitcoins, and more people need to accept bitcoins when
6427 they sell products and services. Improving the bitcoin support in
6428 Debian is a small step in the right direction, but not enough.
6429 Unfortunately the user experience when browsing the web and wanting to
6430 pay with bitcoin is still not very good. The bitcoin: URI is a step
6431 in the right direction, but need to work in most or every browser in
6432 use. Also the bitcoin-qt client is too heavy to fire up to do a
6433 quick transaction. I believe there are other clients available, but
6434 have not tested them.&lt;/p&gt;
6435
6436 &lt;p&gt;My
6437 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6438 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6439 I received 20.15 BTC so far on the address I provided in my blog two
6440 years ago, as can be
6441 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6442 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6443 donation. The blockexplorer service demonstrates quite well that
6444 bitcoin is not quite anonymous and untracked. :) I wonder if the
6445 number of users have gone up since then. If you use bitcoin and want
6446 to show your support of my activity, please send Bitcoin donations to
6447 the same address as last time,
6448 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6449 </description>
6450 </item>
6451
6452 <item>
6453 <title>Git repository for song book for Computer Scientists</title>
6454 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6456 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6457 <description>&lt;p&gt;As I
6458 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6459 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6460 years ago, and today I finally found time to create a public
6461 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6462 repository for the project&lt;/a&gt;.&lt;/p&gt;
6463
6464 &lt;p&gt;If you want to help out, please clone the source and submit patches
6465 to the HTML version. To generate the PDF and PostScript version,
6466 please use prince XML, or let me know about a useful free software
6467 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6468
6469 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6470 PostScript formats at
6471 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6472 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6473 </description>
6474 </item>
6475
6476 <item>
6477 <title>Gratulerer med 19-årsdagen, Debian!</title>
6478 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6480 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6481 <description>&lt;p&gt;I dag fyller
6482 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6483 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6484 si gratulerer med dagen, Debian!&lt;/p&gt;
6485 </description>
6486 </item>
6487
6488 <item>
6489 <title>Song book for Computer Scientists</title>
6490 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6491 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6492 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6493 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6494 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6495 collecting computer related songs for use at parties. The original
6496 version was written in LaTeX, but a few years ago I got help from
6497 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6498 while keeping the ability to create a nice book in PDF format. I have
6499 not had time to maintain the book for a while now, and guess I should
6500 put it up on some public version control repository where others can
6501 help me extend and update the book. If anyone is volunteering to help
6502 me with this, send me an email. Also let me know if there are songs
6503 missing in my book.&lt;/p&gt;
6504
6505 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6506 me today that I really should let all my readers share the joys of
6507 singing out load about programming, computers and computer networks.
6508 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6509 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6510 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6511 Computer Science Songbook&lt;/a&gt;.
6512 </description>
6513 </item>
6514
6515 <item>
6516 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6517 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6518 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6519 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6520 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6521 around 1000 at the moment. To be able to get help from the vendors
6522 when something go wrong, we want to keep the firmware on the servers
6523 up to date. If the firmware isn&#39;t the latest and greatest, the
6524 vendors typically refuse to start debugging any problems until the
6525 firmware is upgraded. So before every reboot, we want to upgrade the
6526 firmware, and we would really like everyone handling servers at the
6527 university to do this themselves when they plan to reboot a machine.
6528 For that to happen we at the unix server admin group need to provide
6529 the tools to do so.&lt;/p&gt;
6530
6531 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6532 fetch and install the latest firmware for the servers we got. Most of
6533 our hardware are from Dell and HP, so I have focused on these servers
6534 so far. This blog post is about the Dell part.&lt;/P&gt;
6535
6536 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6537 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6538 with firmware information for all 11th generation servers, listing
6539 which firmware should be used on a given model and where on the FTP
6540 site I can find it. Using a simple perl XML parser I can then
6541 download the shell scripts Dell provides to do firmware upgrades from
6542 within Linux and reboot when all the firmware is primed and ready to
6543 be activated on the first reboot.&lt;/p&gt;
6544
6545 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6546 Are there anyone working on similar tools for firmware upgrading all
6547 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6548
6549 &lt;p&gt;&lt;pre&gt;
6550 #!/usr/bin/perl
6551 use strict;
6552 use warnings;
6553 use File::Temp qw(tempdir);
6554 BEGIN {
6555 # Install needed RHEL packages if missing
6556 my %rhelmodules = (
6557 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6558 );
6559 for my $module (keys %rhelmodules) {
6560 eval &quot;use $module;&quot;;
6561 if ($@) {
6562 my $pkg = $rhelmodules{$module};
6563 system(&quot;yum install -y $pkg&quot;);
6564 eval &quot;use $module;&quot;;
6565 }
6566 }
6567 }
6568 my $errorsto = &#39;pere@hungry.com&#39;;
6569
6570 upgrade_dell();
6571
6572 exit 0;
6573
6574 sub run_firmware_script {
6575 my ($opts, $script) = @_;
6576 unless ($script) {
6577 print STDERR &quot;fail: missing script name\n&quot;;
6578 exit 1
6579 }
6580 print STDERR &quot;Running $script\n\n&quot;;
6581
6582 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6583 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6584 } else {
6585 print STDERR &quot;fail: firmware script returned error\n&quot;;
6586 }
6587 }
6588
6589 sub run_firmware_scripts {
6590 my ($opts, @dirs) = @_;
6591 # Run firmware packages
6592 for my $dir (@dirs) {
6593 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6594 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6595 while (my $s = readdir $dh) {
6596 next if $s =~ m/^\.\.?/;
6597 run_firmware_script($opts, &quot;$dir/$s&quot;);
6598 }
6599 closedir $dh;
6600 }
6601 }
6602
6603 sub download {
6604 my $url = shift;
6605 print STDERR &quot;info: Downloading $url\n&quot;;
6606 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6607 }
6608
6609 sub upgrade_dell {
6610 my @dirs;
6611 my $product = `dmidecode -s system-product-name`;
6612 chomp $product;
6613
6614 if ($product =~ m/PowerEdge/) {
6615
6616 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6617 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6618
6619 my $tmpdir = tempdir(
6620 CLEANUP =&gt; 1
6621 );
6622 chdir($tmpdir);
6623 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
6624 system(&#39;gunzip Catalog.xml.gz&#39;);
6625 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
6626 # -q is quiet, disabling interactivity and reducing console output
6627 my $fwopts = &quot;-q&quot;;
6628 if (@paths) {
6629 for my $url (@paths) {
6630 fetch_dell_fw($url);
6631 }
6632 run_firmware_scripts($fwopts, $tmpdir);
6633 } else {
6634 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6635 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6636 }
6637 chdir(&#39;/&#39;);
6638 } else {
6639 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6640 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6641 }
6642 }
6643
6644 sub fetch_dell_fw {
6645 my $path = shift;
6646 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
6647 download($url);
6648 }
6649
6650 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6651 # firmware packages to download from Dell. Only work for Linux
6652 # machines and 11th generation Dell servers.
6653 sub fetch_dell_fw_list {
6654 my $filename = shift;
6655
6656 my $product = `dmidecode -s system-product-name`;
6657 chomp $product;
6658 my ($mybrand, $mymodel) = split(/\s+/, $product);
6659
6660 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
6661
6662 my $xml = XMLin($filename);
6663 my @paths;
6664 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
6665 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
6666 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
6667 my $oscode;
6668 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
6669 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
6670 } else {
6671 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
6672 }
6673 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
6674 {
6675 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
6676 }
6677 }
6678 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
6679 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
6680
6681 # Drop application packages, only firmware and BIOS
6682 next if &#39;APAC&#39; eq $componenttype;
6683
6684 my $cpath = $component-&gt;{path};
6685 for my $path (@paths) {
6686 if ($cpath =~ m%/$path$%) {
6687 push(@paths, $cpath);
6688 }
6689 }
6690 }
6691 return @paths;
6692 }
6693 &lt;/pre&gt;
6694
6695 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
6696 it could work on other platforms with some tweaking. Anyone know a
6697 index like Catalog.xml is available from HP for HP servers? At the
6698 moment I maintain a similar list manually and it is quickly getting
6699 outdated.&lt;/p&gt;
6700 </description>
6701 </item>
6702
6703 <item>
6704 <title>How is booting into runlevel 1 different from single user boots?</title>
6705 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
6706 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
6707 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
6708 <description>&lt;p&gt;Wouter Verhelst have some
6709 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
6710 comments and opinions&lt;/a&gt; on my blog post on
6711 &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
6712 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
6713 &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
6714 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
6715 small piece of his comment now, and though it best to address the
6716 misunderstanding he bring forward:&lt;/p&gt;
6717
6718 &lt;p&gt;&lt;blockquote&gt;
6719 Currently, a system admin has four options: [...] boot to a
6720 single-user system (by adding &#39;single&#39; to the kernel command line;
6721 this runs rcS and rc1 scripts)
6722 &lt;/blockquote&gt;&lt;/p&gt;
6723
6724 &lt;p&gt;This make me believe Wouter believe booting into single user mode
6725 and booting into runlevel 1 is the same. I am not surprised he
6726 believe this, because it would make sense and is a quite sensible
6727 thing to believe. But because the boot in Debian is slightly broken,
6728 runlevel 1 do not work properly and it isn&#39;t the same as single user
6729 mode. I&#39;ll try to explain what is actually happing, but it is a bit
6730 hard to explain.&lt;/p&gt;
6731
6732 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
6733 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
6734 executed in single user mode is sulogin. Single user mode is a boot
6735 state &quot;between&quot; the runlevels, and when booting into single user mode,
6736 only the scripts in /etc/rcS.d/ are executed before the init process
6737 enters the single user state. When switching to runlevel 1, the state
6738 is in fact not ending in runlevel 1, but it passes through runlevel 1
6739 and end up in the single user mode (see /etc/rc1.d/S03single, which
6740 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
6741 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
6742 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6743 mode).&lt;/p&gt;
6744
6745 &lt;p&gt;This summary might make it clearer. When booting for the first
6746 time into single user mode, the following commands are executed:
6747 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
6748 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
6749 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
6750 trying to continue after visiting single user mode. Not all services
6751 are started again as they should, causing the machine to end up in an
6752 unpredicatble state. This is why Debian admins recommend rebooting
6753 after visiting single user mode.&lt;/p&gt;
6754
6755 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
6756 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
6757 to runlevel 1, the services started from /etc/rcS.d/ are not properly
6758 stopped when passing through the scripts in /etc/rc1.d/, and not
6759 started again when switching away from runlevel 1 to the runlevels
6760 2-5. I believe the problem is best fixed by moving all the scripts
6761 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
6762 functioning single user mode during boot.&lt;/p&gt;
6763
6764 &lt;p&gt;I have spent several years investigating the Debian boot system,
6765 and discovered this problem a few years ago. I suspect it originates
6766 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
6767 </description>
6768 </item>
6769
6770 <item>
6771 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
6772 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
6773 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
6774 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
6775 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
6776 are started from /etc/rcS.d/. In fact, there is a bite more of them
6777 than make sense, and this causes a few problems. What kind of
6778 problems, you might ask. There are at least two problems. The first
6779 is that it is not possible to recover a machine after switching to
6780 runlevel 1. One need to actually reboot to get the machine back to
6781 the expected state. The other is that single user boot will sometimes
6782 run into problems because some of the subsystems are activated before
6783 the root login is presented, causing problems when trying to recover a
6784 machine from a problem in that subsystem. A minor additional point is
6785 that moving more scripts out of rcS.d/ and into the other rc#.d/
6786 directories will increase the amount of scripts that can run in
6787 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
6788
6789 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
6790 scripts that _have_ to execute before the root login prompt is
6791 presented during a single user boot should go there. Everything else
6792 should go into the numeric runlevels. This means things like
6793 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6794 the numeric runlevels. Today in Debian, there are around 115 init.d
6795 scripts that are started from rcS.d/, and most of them should be moved
6796 out. Do your package have one of them? Please help us make single
6797 user and runlevel 1 better by moving it.&lt;/p&gt;
6798
6799 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
6800 etc. should still be started from rcS.d/, but there is for example no
6801 need to have the network enabled before the single user login prompt
6802 is presented.&lt;/p&gt;
6803
6804 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
6805 Debian systems working while scripts migrate and during upgrades, the
6806 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6807 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6808 and the next ones can only be moved when their dependencies have been
6809 moved first. This migration must be done sequentially while we ensure
6810 that the package system upgrade packages in the right order to keep
6811 the system state correct. This will require some coordination when it
6812 comes to network related packages, but most of the packages with
6813 scripts that should migrate do not have anything in rcS.d/ depending
6814 on them. Some packages have already been updated, like the sudo
6815 package, while others are still left to do. I wish I had time to work
6816 on this myself, but real live constrains make it unlikely that I will
6817 find time to push this forward.&lt;/p&gt;
6818 </description>
6819 </item>
6820
6821 <item>
6822 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
6823 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
6824 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
6825 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
6826 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
6827 mentioned the issues I believe should be improved in Debian for its
6828 desktop to be useful for more people. The use case for this is my
6829 parents, which are currently running Kubuntu which solve the
6830 issues.&lt;/p&gt;
6831
6832 &lt;p&gt;I suspect these four missing features are not very hard to
6833 implement. After all, they are present in Ubuntu, so if we wanted to
6834 do this in Debian we would have a source.&lt;/p&gt;
6835
6836 &lt;ol&gt;
6837
6838 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
6839 are new packages available for upgrades, a icon in the KDE status bar
6840 indicate this, and clicking on it will activate the simple upgrade
6841 tool to handle it. I have no problem guiding both of my parents
6842 through the process over the phone. If a kernel reboot is required,
6843 this too is indicated by the status bars and the upgrade tool. Last
6844 time I checked, nothing with the same features was working in KDE in
6845 Debian.&lt;/li&gt;
6846
6847 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
6848 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
6849 currently have a handler for, it will ask the user if the system
6850 should search for a package that would add support for this MIME type,
6851 and if the user say yes, the APT sources will be searched for packages
6852 advertising the MIME type in their control file (visible in the
6853 Packages file in the APT archive). If one or more packages are found,
6854 it is a simple click of the mouse to add support for the missing mime
6855 type. If the package require the user to accept some non-free
6856 license, this is explained to the user. The entire process make it
6857 more clear to the user why something do not work in the browser, and
6858 make the chances higher for the user to blame the web page authors and
6859 not the browser for any missing features.&lt;/li&gt;
6860
6861 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
6862 handlers.&lt;/strong&gt; When the media players encounter a format or codec
6863 it is not supporting, a dialog pop up asking the user if the system
6864 should search for a package that would add support for it. This
6865 happen with things like MP3, Windows Media or H.264. The selection
6866 and installation procedure is very similar to the Firefox browser
6867 plugin handling. This is as far as I know implemented using a
6868 gstreamer hook. The end result is that the user easily get access to
6869 the codecs that are present from the APT archives available, while
6870 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
6871
6872 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
6873 displaying a text/plain file in my Debian browser, it will propose to
6874 start emacs to show it. If I remember correctly, when doing the same
6875 in Kunbutu it show the file as a text file in the browser. At least I
6876 know Opera will show text files within the browser. I much prefer the
6877 latter behaviour.&lt;/li&gt;
6878
6879 &lt;/ol&gt;
6880
6881 &lt;p&gt;There are other nice features as well, like the simplified suite
6882 upgrader, but given that I am the one mostly doing the dist-upgrade,
6883 it do not matter much.&lt;/p&gt;
6884
6885 &lt;p&gt;I really hope we could get these features in place for the next
6886 Debian release. It would require the coordinated effort of several
6887 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
6888 </description>
6889 </item>
6890
6891 <item>
6892 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
6893 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
6894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
6895 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
6896 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
6897 site is build on Debian/Squeeze, and this platform was chosen because
6898 I am most familiar with Debian (being a Debian Developer for around 10
6899 years) because it is the latest stable Debian release which should get
6900 security support for a few years.&lt;/p&gt;
6901
6902 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
6903 that are missing in Debian at the moment. It would be great if these
6904 modules were added to the Debian archive, allowing anyone to set up
6905 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
6906 in their own country using only Debian packages. The list of modules
6907 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
6908 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
6909 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6910 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6911 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6912 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6913 easier in the future.&lt;/p&gt;
6914
6915 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
6916 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
6917 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
6918 with the responsibility of tracking security problems, which I really
6919 do not have time for.&lt;/p&gt;
6920 </description>
6921 </item>
6922
6923 <item>
6924 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
6925 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
6926 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
6927 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
6928 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
6929 posts have been in Norwegian the last few weeks, so here is a short
6930 update in English.&lt;/p&gt;
6931
6932 &lt;p&gt;The kids still keep me too busy to get much free software work
6933 done, but I did manage to organise a project to get a Norwegian port
6934 of the British service
6935 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
6936 and it has been running for a month now. The entire project has been
6937 organised by me and two others. Around Christmas we gathered sponsors
6938 to fund the development work. In January I drafted a contract with
6939 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
6940 and in February the development took place. Most of it involved
6941 converting the source to use GPS coordinates instead of British
6942 easting/northing, and the resulting code should be a lot easier to get
6943 running in any country by now. The Norwegian
6944 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
6945 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
6946 source and the source for administrative borders in Norway, and
6947 support for this had to be added/fixed.&lt;/p&gt;
6948
6949 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
6950 polishing the system before we announced it March 7th. The system is
6951 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
6952 problem reports in a few weeks. Soon we hope to announce the Android
6953 and iPhone versions making it even easier to report problems with the
6954 public infrastructure.&lt;/p&gt;
6955
6956 &lt;p&gt;Perhaps something to consider for those of you in countries without
6957 such service?&lt;/p&gt;
6958 </description>
6959 </item>
6960
6961 <item>
6962 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
6963 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
6964 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
6965 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
6966 <description>&lt;p&gt;The last few days I have looked at ways to track open security
6967 issues here at my work with the University of Oslo. My idea is that
6968 it should be possible to use the information about security issues
6969 available on the Internet, and check our locally
6970 maintained/distributed software against this information. It should
6971 allow us to verify that no known security issues are forgotten. The
6972 CVE database listing vulnerabilities seem like a great central point,
6973 and by using the package lists from Debian mapped to CVEs provided by
6974 the testing security team, I believed it should be possible to figure
6975 out which security holes were present in our free software
6976 collection.&lt;/p&gt;
6977
6978 &lt;p&gt;After reading up on the topic, it became obvious that the first
6979 building block is to be able to name software packages in a unique and
6980 consistent way across data sources. I considered several ways to do
6981 this, for example coming up with my own naming scheme like using URLs
6982 to project home pages or URLs to the Freshmeat entries, or using some
6983 existing naming scheme. And it seem like I am not the first one to
6984 come across this problem, as MITRE already proposed and implemented a
6985 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
6986 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
6987 software, hardware and other platform components. The CPE ids are
6988 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
6989 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
6990 issues for any CPE name. With this in place, all I need to do is to
6991 locate the CPE id for the software packages we use at the university.
6992 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
6993 NVD entry if a CVE for the package exist).&lt;/p&gt;
6994
6995 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
6996 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
6997 check out, one could look up
6998 &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
6999 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
7000 The most recent one is
7001 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
7002 and at the bottom of the NVD page for this vulnerability the complete
7003 list of affected versions is provided.&lt;/p&gt;
7004
7005 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
7006 for offline processing of issues. Using this dump, I&#39;ve written a
7007 small script taking a list of CPEs as input and list all CVEs
7008 affecting the packages represented by these CPEs. One give it CPEs
7009 with version numbers as specified above and get a list of open
7010 security issues out.&lt;/p&gt;
7011
7012 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
7013 information need to be high. For that to happen, I believe as many as
7014 possible need to use and contribute to the NVD database. I notice
7015 RHEL is providing
7016 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
7017 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
7018 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
7019
7020 &lt;p&gt;To get an idea about the quality for free software, I spent some
7021 time making it possible to compare the CVE database from Debian with
7022 the CVE database in NVD. The result look fairly good, but there are
7023 some inconsistencies in NVD (same software package having several
7024 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7025 Debian believe are affected by a CVE). Hope to find time to improve
7026 the quality of NVD, but that require being able to get in touch with
7027 someone maintaining it. So far my three emails with questions and
7028 corrections have not seen any reply, but I hope contact can be
7029 established soon.&lt;/p&gt;
7030
7031 &lt;p&gt;An interesting application for CPEs is cross platform package
7032 mapping. It would be useful to know which packages in for example
7033 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7034 this would be trivial if all linux distributions provided CPE entries
7035 for their packages.&lt;/p&gt;
7036 </description>
7037 </item>
7038
7039 <item>
7040 <title>Which module is loaded for a given PCI and USB device?</title>
7041 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
7042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
7043 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
7044 <description>&lt;p&gt;In the
7045 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
7046 package in Debian, there is a script to report useful information
7047 about the running hardware for use when people report missing
7048 information. One part of this script that I find very useful when
7049 debugging hardware problems, is the part mapping loaded kernel module
7050 to the PCI device it claims. It allow me to quickly see if the kernel
7051 module I expect is driving the hardware I am struggling with. To see
7052 the output, make sure discover-data is installed and run
7053 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
7054 one of my machines like this:&lt;/p&gt;
7055
7056 &lt;pre&gt;
7057 loaded modules:
7058 10de:03eb i2c_nforce2
7059 10de:03f1 ohci_hcd
7060 10de:03f2 ehci_hcd
7061 10de:03f0 snd_hda_intel
7062 10de:03ec pata_amd
7063 10de:03f6 sata_nv
7064 1022:1103 k8temp
7065 109e:036e bttv
7066 109e:0878 snd_bt87x
7067 11ab:4364 sky2
7068 &lt;/pre&gt;
7069
7070 &lt;p&gt;The code in question look like this, slightly modified for
7071 readability and to drop the output to file descriptor 3:&lt;/p&gt;
7072
7073 &lt;pre&gt;
7074 if [ -d /sys/bus/pci/devices/ ] ; then
7075 echo loaded pci modules:
7076 (
7077 cd /sys/bus/pci/devices/
7078 for address in * ; do
7079 if [ -d &quot;$address/driver/module&quot; ] ; then
7080 module=`cd $address/driver/module ; pwd -P | xargs basename`
7081 if grep -q &quot;^$module &quot; /proc/modules ; then
7082 address=$(echo $address |sed s/0000://)
7083 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
7084 echo &quot;$id $module&quot;
7085 fi
7086 fi
7087 done
7088 )
7089 echo
7090 fi
7091 &lt;/pre&gt;
7092
7093 &lt;p&gt;Similar code could be used to extract USB device module
7094 mappings:&lt;/p&gt;
7095
7096 &lt;pre&gt;
7097 if [ -d /sys/bus/usb/devices/ ] ; then
7098 echo loaded usb modules:
7099 (
7100 cd /sys/bus/usb/devices/
7101 for address in * ; do
7102 if [ -d &quot;$address/driver/module&quot; ] ; then
7103 module=`cd $address/driver/module ; pwd -P | xargs basename`
7104 if grep -q &quot;^$module &quot; /proc/modules ; then
7105 address=$(echo $address |sed s/0000://)
7106 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7107 if [ &quot;$id&quot; ] ; then
7108 echo &quot;$id $module&quot;
7109 fi
7110 fi
7111 fi
7112 done
7113 )
7114 echo
7115 fi
7116 &lt;/pre&gt;
7117
7118 &lt;p&gt;This might perhaps be something to include in other tools as
7119 well.&lt;/p&gt;
7120 </description>
7121 </item>
7122
7123 <item>
7124 <title>How to test if a laptop is working with Linux</title>
7125 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7127 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7128 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7129 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7130 batch of computers will work with Linux. Every year for the last few
7131 years the university have organised shared bid of a few thousand
7132 computers, and this year HP won the bid. Two different desktops and
7133 five different laptops are on the list this year. We in the UNIX
7134 group want to know which one of these computers work well with RHEL
7135 and Ubuntu, the two Linux distributions we currently handle at the
7136 university.&lt;/p&gt;
7137
7138 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7139 perhaps inspire others to test hardware as well. To test, I PXE
7140 install the OS version of choice, and log in as my normal user and run
7141 a few applications and plug in selected pieces of hardware. When
7142 something fail, I make a note about this in the test matrix and move
7143 on. If I have some spare time I try to report the bug to the OS
7144 vendor, but as I only have the machines for a short time, I rarely
7145 have the time to do this for all the problems I find.&lt;/p&gt;
7146
7147 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7148 I perform on a new model.&lt;/p&gt;
7149
7150 &lt;ul&gt;
7151
7152 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7153 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7154 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7155
7156 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7157 installation, X.org is working.&lt;/li&gt;
7158
7159 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7160 package mesa-utils on Ubuntu) and writing down the frames per second
7161 reported by the program.&lt;/li&gt;
7162
7163 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7164 logging in, and if I can hear this the test is successful. If there
7165 are several audio exits on the machine, I try them all and check if
7166 the Gnome/KDE audio mixer can control where to send the sound. I
7167 normally test this by playing
7168 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7169 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7170
7171 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7172 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7173
7174 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7175 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7176
7177 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7178 picture from the v4l device show up.&lt;/li&gt;
7179
7180 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7181 any bluetooth devices are discovered. In my office, I normally see a
7182 few.&lt;/li&gt;
7183
7184 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7185 memory modules lying around, and stick them in and see if Gnome/KDE
7186 notice this.&lt;/li&gt;
7187
7188 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7189 special button work, and if the laptop continue to work after
7190 resume.&lt;/li&gt;
7191
7192 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7193 adjusting background light, switching on/off external video output,
7194 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7195 laptop to laptop, so I just write down which are working and which are
7196 not.&lt;/li&gt;
7197
7198 &lt;li&gt;Some laptops have smart card readers, finger print readers,
7199 acceleration sensors etc. I rarely test these, as I do not know how
7200 to quickly test if they are working or not, so I only document their
7201 existence.&lt;/li&gt;
7202
7203 &lt;/ul&gt;
7204
7205 &lt;p&gt;By now I suspect you are really curious what the test results are
7206 for the HP machines I am testing. I&#39;m not done yet, so I will report
7207 the test results later. For now I can report that HP 8100 Elite work
7208 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
7209 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
7210 can see, I have most machines left to test. One interesting
7211 observation is that Ubuntu Lucid has almost twice the frame rate than
7212 RHEL6 with glxgears. No idea why.&lt;/p&gt;
7213 </description>
7214 </item>
7215
7216 <item>
7217 <title>Some thoughts on BitCoins</title>
7218 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
7219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
7220 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
7221 <description>&lt;p&gt;As I continue to explore
7222 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
7223 what properties the system have, and how it will be affected by laws
7224 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
7225
7226 &lt;p&gt;One interesting thing to note is that since the transactions are
7227 verified using a peer to peer network, all details about a transaction
7228 is known to everyone. This means that if a BitCoin address has been
7229 published like I did with mine in my initial post about BitCoin, it is
7230 possible for everyone to see how many BitCoins have been transfered to
7231 that address. There is even a web service to look at the details for
7232 all transactions. There I can see that my address
7233 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
7234 have received 16.06 Bitcoin, the
7235 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
7236 address of Simon Phipps have received 181.97 BitCoin and the address
7237 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
7238 of EFF have received 2447.38 BitCoins so far. Thank you to each and
7239 every one of you that donated bitcoins to support my activity. The
7240 fact that anyone can see how much money was transfered to a given
7241 address make it more obvious why the BitCoin community recommend to
7242 generate and hand out a new address for each transaction. I&#39;m told
7243 there is no way to track which addresses belong to a given person or
7244 organisation without the person or organisation revealing it
7245 themselves, as Simon, EFF and I have done.&lt;/p&gt;
7246
7247 &lt;p&gt;In Norway, and in most other countries, there are laws and
7248 regulations limiting how much money one can transfer across the border
7249 without declaring it. There are money laundering, tax and accounting
7250 laws and regulations I would expect to apply to the use of BitCoin.
7251 If the Skolelinux foundation
7252 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
7253 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
7254 normal bank transfers like EFF is doing, how should this be accounted?
7255 Given that it is impossible to know if money can cross the border or
7256 not, should everything or nothing be declared? What exchange rate
7257 should be used when calculating taxes? Would receivers have to pay
7258 income tax if the foundation were to pay Skolelinux contributors in
7259 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
7260
7261 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
7262 accepted by a lot of users. It must be possible to get easy access to
7263 the currency (as a wage or using currency exchanges), and it must be
7264 easy to spend it. At the moment BitCoin seem fairly easy to get
7265 access to, but there are very few places to spend it. I am not really
7266 a regular user of any of the vendor types currently accepting BitCoin,
7267 so I wonder when my kind of shop would start accepting BitCoins. I
7268 would like to buy electronics, travels and subway tickets, not herbs
7269 and books. :) The currency is young, and this will improve over time
7270 if it become popular, but I suspect regular banks will start to lobby
7271 to get BitCoin declared illegal if it become popular. I&#39;m sure they
7272 will claim it is helping fund terrorism and money laundering (which
7273 probably would be true, as is any currency in existence), but I
7274 believe the problems should be solved elsewhere and not by blaming
7275 currencies.&lt;/p&gt;
7276
7277 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
7278 CPU intensive process that depend on a bit of luck as well (as one is
7279 competing against all the other miners currently spending CPU cycles
7280 to see which one get the next lump of cash). The &quot;winner&quot; get 50
7281 BitCoin when this happen. Yesterday I came across the obvious way to
7282 join forces to increase ones changes of getting at least some coins,
7283 by coordinating the work on mining BitCoins across several machines
7284 and people, and sharing the result if one is lucky and get the 50
7285 BitCoins. Check out
7286 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
7287 if this sounds interesting. I have not had time to try to set up a
7288 machine to participate there yet, but have seen that running on ones
7289 own for a few days have not yield any BitCoins througth mining
7290 yet.&lt;/p&gt;
7291
7292 &lt;p&gt;Update 2010-12-15: Found an &lt;a
7293 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
7294 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
7295 it was interesting to read. The arguments presented seem to be
7296 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
7297 </description>
7298 </item>
7299
7300 <item>
7301 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
7302 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
7303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
7304 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
7305 <description>&lt;p&gt;With this weeks lawless
7306 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
7307 attacks&lt;/a&gt; on Wikileak and
7308 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
7309 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
7310 not be trusted to handle money transactions.
7311 A blog post from
7312 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
7313 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
7314 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
7315 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
7316 some help from my friend to get it all running, and he even handed me
7317 some bitcoins to get started. I even donated a few bitcoins to Simon
7318 for helping me remember BitCoin.&lt;/p&gt;
7319
7320 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
7321 crypto-currency, decentralised and handled using peer-to-peer
7322 networks. It allows anonymous transactions and prohibits central
7323 control over the transactions, making it impossible for governments
7324 and companies alike to block donations and other transactions. The
7325 source is free software, and while the key dependency wxWidgets 2.9
7326 for the graphical user interface is missing in Debian, the command
7327 line client builds just fine. Hopefully Jonas
7328 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
7329 Debian&lt;/a&gt; soon.&lt;/p&gt;
7330
7331 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
7332 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
7333 bitcoins&lt;/a&gt; when selling services and goods, and there are even
7334 currency &quot;stock&quot; markets where the exchange rate is decided. There
7335 are not many users so far, but the concept seems promising. If you
7336 want to get started and lack a friend with any bitcoins to spare,
7337 you can even get
7338 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
7339 bitcoin at the time of writing). Use
7340 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
7341 on the current exchange rates.&lt;/p&gt;
7342
7343 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
7344 machines. If you want to support my activity, please send Bitcoin
7345 donations to the address
7346 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
7347 </description>
7348 </item>
7349
7350 <item>
7351 <title>Why isn&#39;t Debian Edu using VLC?</title>
7352 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
7353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
7354 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
7355 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
7356 presented, and the winner among the multimedia player were VLC.
7357 Personally, I like VLC, and it is my player of choice when I first try
7358 to play a video file or stream. Only if VLC fail will I drag out
7359 gmplayer to see if it can do better. The reason is mostly the failure
7360 model and trust. When VLC fail, it normally pop up a error message
7361 reporting the problem. When mplayer fail, it normally segfault or
7362 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
7363
7364 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
7365 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7366 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
7367 plugin to play web videos seamlessly, and the VLC browser plugin is
7368 not very good. For example, it lack in-line control buttons, so there
7369 is no way for the user to pause the video. Also, when I
7370 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
7371 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
7372 failed on several video pages where mplayer based plugins worked. If
7373 the browser plugin for VLC was as good as the gecko-mediaplayer
7374 package (which uses mplayer), we would switch.&lt;/P&gt;
7375
7376 &lt;p&gt;While VLC is a good player, its user interface is slightly
7377 annoying. The most annoying feature is its inconsistent use of
7378 keyboard shortcuts. When the player is in full screen mode, its
7379 shortcuts are different from when it is playing the video in a window.
7380 For example, space only work as pause when in full screen mode. I
7381 wish it had consisten shortcuts and that space also would work when in
7382 window mode. Another nice shortcut in gmplayer is [enter] to restart
7383 the current video. It is very nice when playing short videos from the
7384 web and want to restart it when new people arrive to have a look at
7385 what is going on.&lt;/p&gt;
7386 </description>
7387 </item>
7388
7389 <item>
7390 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
7391 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
7392 <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>
7393 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7394 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7395 upgrade testing of the
7396 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7397 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7398 This seem like a very good idea, so I adjusted by test scripts and
7399 can now present the updated result from today:&lt;/p&gt;
7400
7401 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7402
7403 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7404
7405 &lt;blockquote&gt;&lt;p&gt;
7406 apache2.2-bin
7407 aptdaemon
7408 baobab
7409 binfmt-support
7410 browser-plugin-gnash
7411 cheese-common
7412 cli-common
7413 cups-pk-helper
7414 dmz-cursor-theme
7415 empathy
7416 empathy-common
7417 freedesktop-sound-theme
7418 freeglut3
7419 gconf-defaults-service
7420 gdm-themes
7421 gedit-plugins
7422 geoclue
7423 geoclue-hostip
7424 geoclue-localnet
7425 geoclue-manual
7426 geoclue-yahoo
7427 gnash
7428 gnash-common
7429 gnome
7430 gnome-backgrounds
7431 gnome-cards-data
7432 gnome-codec-install
7433 gnome-core
7434 gnome-desktop-environment
7435 gnome-disk-utility
7436 gnome-screenshot
7437 gnome-search-tool
7438 gnome-session-canberra
7439 gnome-system-log
7440 gnome-themes-extras
7441 gnome-themes-more
7442 gnome-user-share
7443 gstreamer0.10-fluendo-mp3
7444 gstreamer0.10-tools
7445 gtk2-engines
7446 gtk2-engines-pixbuf
7447 gtk2-engines-smooth
7448 hamster-applet
7449 libapache2-mod-dnssd
7450 libapr1
7451 libaprutil1
7452 libaprutil1-dbd-sqlite3
7453 libaprutil1-ldap
7454 libart2.0-cil
7455 libboost-date-time1.42.0
7456 libboost-python1.42.0
7457 libboost-thread1.42.0
7458 libchamplain-0.4-0
7459 libchamplain-gtk-0.4-0
7460 libcheese-gtk18
7461 libclutter-gtk-0.10-0
7462 libcryptui0
7463 libdiscid0
7464 libelf1
7465 libepc-1.0-2
7466 libepc-common
7467 libepc-ui-1.0-2
7468 libfreerdp-plugins-standard
7469 libfreerdp0
7470 libgconf2.0-cil
7471 libgdata-common
7472 libgdata7
7473 libgdu-gtk0
7474 libgee2
7475 libgeoclue0
7476 libgexiv2-0
7477 libgif4
7478 libglade2.0-cil
7479 libglib2.0-cil
7480 libgmime2.4-cil
7481 libgnome-vfs2.0-cil
7482 libgnome2.24-cil
7483 libgnomepanel2.24-cil
7484 libgpod-common
7485 libgpod4
7486 libgtk2.0-cil
7487 libgtkglext1
7488 libgtksourceview2.0-common
7489 libmono-addins-gui0.2-cil
7490 libmono-addins0.2-cil
7491 libmono-cairo2.0-cil
7492 libmono-corlib2.0-cil
7493 libmono-i18n-west2.0-cil
7494 libmono-posix2.0-cil
7495 libmono-security2.0-cil
7496 libmono-sharpzip2.84-cil
7497 libmono-system2.0-cil
7498 libmtp8
7499 libmusicbrainz3-6
7500 libndesk-dbus-glib1.0-cil
7501 libndesk-dbus1.0-cil
7502 libopal3.6.8
7503 libpolkit-gtk-1-0
7504 libpt2.6.7
7505 libpython2.6
7506 librpm1
7507 librpmio1
7508 libsdl1.2debian
7509 libsrtp0
7510 libssh-4
7511 libtelepathy-farsight0
7512 libtelepathy-glib0
7513 libtidy-0.99-0
7514 media-player-info
7515 mesa-utils
7516 mono-2.0-gac
7517 mono-gac
7518 mono-runtime
7519 nautilus-sendto
7520 nautilus-sendto-empathy
7521 p7zip-full
7522 pkg-config
7523 python-aptdaemon
7524 python-aptdaemon-gtk
7525 python-axiom
7526 python-beautifulsoup
7527 python-bugbuddy
7528 python-clientform
7529 python-coherence
7530 python-configobj
7531 python-crypto
7532 python-cupshelpers
7533 python-elementtree
7534 python-epsilon
7535 python-evolution
7536 python-feedparser
7537 python-gdata
7538 python-gdbm
7539 python-gst0.10
7540 python-gtkglext1
7541 python-gtksourceview2
7542 python-httplib2
7543 python-louie
7544 python-mako
7545 python-markupsafe
7546 python-mechanize
7547 python-nevow
7548 python-notify
7549 python-opengl
7550 python-openssl
7551 python-pam
7552 python-pkg-resources
7553 python-pyasn1
7554 python-pysqlite2
7555 python-rdflib
7556 python-serial
7557 python-tagpy
7558 python-twisted-bin
7559 python-twisted-conch
7560 python-twisted-core
7561 python-twisted-web
7562 python-utidylib
7563 python-webkit
7564 python-xdg
7565 python-zope.interface
7566 remmina
7567 remmina-plugin-data
7568 remmina-plugin-rdp
7569 remmina-plugin-vnc
7570 rhythmbox-plugin-cdrecorder
7571 rhythmbox-plugins
7572 rpm-common
7573 rpm2cpio
7574 seahorse-plugins
7575 shotwell
7576 software-center
7577 system-config-printer-udev
7578 telepathy-gabble
7579 telepathy-mission-control-5
7580 telepathy-salut
7581 tomboy
7582 totem
7583 totem-coherence
7584 totem-mozilla
7585 totem-plugins
7586 transmission-common
7587 xdg-user-dirs
7588 xdg-user-dirs-gtk
7589 xserver-xephyr
7590 &lt;/p&gt;&lt;/blockquote&gt;
7591
7592 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7593
7594 &lt;blockquote&gt;&lt;p&gt;
7595 cheese
7596 ekiga
7597 eog
7598 epiphany-extensions
7599 evolution-exchange
7600 fast-user-switch-applet
7601 file-roller
7602 gcalctool
7603 gconf-editor
7604 gdm
7605 gedit
7606 gedit-common
7607 gnome-games
7608 gnome-games-data
7609 gnome-nettool
7610 gnome-system-tools
7611 gnome-themes
7612 gnuchess
7613 gucharmap
7614 guile-1.8-libs
7615 libavahi-ui0
7616 libdmx1
7617 libgalago3
7618 libgtk-vnc-1.0-0
7619 libgtksourceview2.0-0
7620 liblircclient0
7621 libsdl1.2debian-alsa
7622 libspeexdsp1
7623 libsvga1
7624 rhythmbox
7625 seahorse
7626 sound-juicer
7627 system-config-printer
7628 totem-common
7629 transmission-gtk
7630 vinagre
7631 vino
7632 &lt;/p&gt;&lt;/blockquote&gt;
7633
7634 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7635
7636 &lt;blockquote&gt;&lt;p&gt;
7637 gstreamer0.10-gnomevfs
7638 &lt;/p&gt;&lt;/blockquote&gt;
7639
7640 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7641
7642 &lt;blockquote&gt;&lt;p&gt;
7643 [nothing]
7644 &lt;/p&gt;&lt;/blockquote&gt;
7645
7646 &lt;p&gt;This is for KDE:&lt;/p&gt;
7647
7648 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7649
7650 &lt;blockquote&gt;&lt;p&gt;
7651 ksmserver
7652 &lt;/p&gt;&lt;/blockquote&gt;
7653
7654 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7655
7656 &lt;blockquote&gt;&lt;p&gt;
7657 kwin
7658 network-manager-kde
7659 &lt;/p&gt;&lt;/blockquote&gt;
7660
7661 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7662
7663 &lt;blockquote&gt;&lt;p&gt;
7664 arts
7665 dolphin
7666 freespacenotifier
7667 google-gadgets-gst
7668 google-gadgets-xul
7669 kappfinder
7670 kcalc
7671 kcharselect
7672 kde-core
7673 kde-plasma-desktop
7674 kde-standard
7675 kde-window-manager
7676 kdeartwork
7677 kdeartwork-emoticons
7678 kdeartwork-style
7679 kdeartwork-theme-icon
7680 kdebase
7681 kdebase-apps
7682 kdebase-workspace
7683 kdebase-workspace-bin
7684 kdebase-workspace-data
7685 kdeeject
7686 kdelibs
7687 kdeplasma-addons
7688 kdeutils
7689 kdewallpapers
7690 kdf
7691 kfloppy
7692 kgpg
7693 khelpcenter4
7694 kinfocenter
7695 konq-plugins-l10n
7696 konqueror-nsplugins
7697 kscreensaver
7698 kscreensaver-xsavers
7699 ktimer
7700 kwrite
7701 libgle3
7702 libkde4-ruby1.8
7703 libkonq5
7704 libkonq5-templates
7705 libnetpbm10
7706 libplasma-ruby
7707 libplasma-ruby1.8
7708 libqt4-ruby1.8
7709 marble-data
7710 marble-plugins
7711 netpbm
7712 nuvola-icon-theme
7713 plasma-dataengines-workspace
7714 plasma-desktop
7715 plasma-desktopthemes-artwork
7716 plasma-runners-addons
7717 plasma-scriptengine-googlegadgets
7718 plasma-scriptengine-python
7719 plasma-scriptengine-qedje
7720 plasma-scriptengine-ruby
7721 plasma-scriptengine-webkit
7722 plasma-scriptengines
7723 plasma-wallpapers-addons
7724 plasma-widget-folderview
7725 plasma-widget-networkmanagement
7726 ruby
7727 sweeper
7728 update-notifier-kde
7729 xscreensaver-data-extra
7730 xscreensaver-gl
7731 xscreensaver-gl-extra
7732 xscreensaver-screensaver-bsod
7733 &lt;/p&gt;&lt;/blockquote&gt;
7734
7735 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7736
7737 &lt;blockquote&gt;&lt;p&gt;
7738 ark
7739 google-gadgets-common
7740 google-gadgets-qt
7741 htdig
7742 kate
7743 kdebase-bin
7744 kdebase-data
7745 kdepasswd
7746 kfind
7747 klipper
7748 konq-plugins
7749 konqueror
7750 ksysguard
7751 ksysguardd
7752 libarchive1
7753 libcln6
7754 libeet1
7755 libeina-svn-06
7756 libggadget-1.0-0b
7757 libggadget-qt-1.0-0b
7758 libgps19
7759 libkdecorations4
7760 libkephal4
7761 libkonq4
7762 libkonqsidebarplugin4a
7763 libkscreensaver5
7764 libksgrd4
7765 libksignalplotter4
7766 libkunitconversion4
7767 libkwineffects1a
7768 libmarblewidget4
7769 libntrack-qt4-1
7770 libntrack0
7771 libplasma-geolocation-interface4
7772 libplasmaclock4a
7773 libplasmagenericshell4
7774 libprocesscore4a
7775 libprocessui4a
7776 libqalculate5
7777 libqedje0a
7778 libqtruby4shared2
7779 libqzion0a
7780 libruby1.8
7781 libscim8c2a
7782 libsmokekdecore4-3
7783 libsmokekdeui4-3
7784 libsmokekfile3
7785 libsmokekhtml3
7786 libsmokekio3
7787 libsmokeknewstuff2-3
7788 libsmokeknewstuff3-3
7789 libsmokekparts3
7790 libsmokektexteditor3
7791 libsmokekutils3
7792 libsmokenepomuk3
7793 libsmokephonon3
7794 libsmokeplasma3
7795 libsmokeqtcore4-3
7796 libsmokeqtdbus4-3
7797 libsmokeqtgui4-3
7798 libsmokeqtnetwork4-3
7799 libsmokeqtopengl4-3
7800 libsmokeqtscript4-3
7801 libsmokeqtsql4-3
7802 libsmokeqtsvg4-3
7803 libsmokeqttest4-3
7804 libsmokeqtuitools4-3
7805 libsmokeqtwebkit4-3
7806 libsmokeqtxml4-3
7807 libsmokesolid3
7808 libsmokesoprano3
7809 libtaskmanager4a
7810 libtidy-0.99-0
7811 libweather-ion4a
7812 libxklavier16
7813 libxxf86misc1
7814 okteta
7815 oxygencursors
7816 plasma-dataengines-addons
7817 plasma-scriptengine-superkaramba
7818 plasma-widget-lancelot
7819 plasma-widgets-addons
7820 plasma-widgets-workspace
7821 polkit-kde-1
7822 ruby1.8
7823 systemsettings
7824 update-notifier-common
7825 &lt;/p&gt;&lt;/blockquote&gt;
7826
7827 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
7828 aptitude a bit more similar, but there are still quite a lott of
7829 differences. I have no idea what packages should be installed after
7830 the upgrade, but hope those that do can have a look.&lt;/p&gt;
7831 </description>
7832 </item>
7833
7834 <item>
7835 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
7836 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
7837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
7838 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
7839 <description>&lt;p&gt;Most of the computers in use by the
7840 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
7841 are virtual machines. And they have been Xen machines running on a
7842 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
7843 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
7844 bit harder that it could have been, because we set up the Xen virtual
7845 machines to get the virtual partitions from LVM, which as far as I
7846 know is not supported by KVM. So to migrate, we had to convert
7847 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
7848
7849 &lt;p&gt;I found
7850 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
7851 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
7852 migration. It uses qemu-img from the qemu package to make the disk
7853 image, parted to partition it, losetup and kpartx to present the disk
7854 image partions as devices, and dd to copy the data. I NFS mounted the
7855 new servers storage area on the old server to do the migration.&lt;/p&gt;
7856
7857 &lt;pre&gt;
7858 #!/bin/sh
7859
7860 # Based on
7861 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7862
7863 set -e
7864 set -x
7865
7866 if [ -z &quot;$1&quot; ] ; then
7867 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
7868 exit 1
7869 else
7870 host=&quot;$1&quot;
7871 fi
7872
7873 if [ ! -e /dev/vg_data/$host-disk ] ; then
7874 echo &quot;error: unable to find LVM volume for $host&quot;
7875 exit 1
7876 fi
7877
7878 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7879 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7880 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
7881 totalsize=$(( ( $disksize + $swapsize ) ))
7882
7883 img=$host.img
7884 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
7885 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7886
7887 parted $img mklabel msdos
7888 parted $img mkpart primary linux-swap 0 $disksize
7889 parted $img mkpart primary ext2 $disksize $totalsize
7890 parted $img set 1 boot on
7891
7892 modprobe dm-mod
7893 losetup /dev/loop0 $img
7894 kpartx -a /dev/loop0
7895
7896 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
7897 fsck.ext3 -f /dev/mapper/loop0p1 || true
7898 mkswap /dev/mapper/loop0p2
7899
7900 kpartx -d /dev/loop0
7901 losetup -d /dev/loop0
7902 &lt;/pre&gt;
7903
7904 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
7905 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
7906
7907 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
7908 the new disk image attached, installed grub-pc and linux-image-686 and
7909 set up grub to boot from the disk image. After this, the KVM machines
7910 seem to work just fine.&lt;/p&gt;
7911 </description>
7912 </item>
7913
7914 <item>
7915 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
7916 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
7917 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
7918 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
7919 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
7920 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7921 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
7922 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
7923
7924 &lt;p&gt;I still do not know what a correct migration should look like, so I
7925 report any differences between apt and aptitude and hope someone else
7926 can see if anything should be changed.&lt;/p&gt;
7927
7928 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7929
7930 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7931
7932 &lt;blockquote&gt;&lt;p&gt;
7933 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7934 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
7935 dmz-cursor-theme empathy empathy-common finger
7936 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7937 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7938 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7939 gnome-cards-data gnome-codec-install gnome-core
7940 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7941 gnome-search-tool gnome-session-canberra gnome-spell
7942 gnome-system-log gnome-themes-extras gnome-themes-more
7943 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7944 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7945 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7946 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7947 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
7948 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
7949 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
7950 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
7951 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
7952 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7953 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
7954 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7955 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7956 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7957 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7958 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7959 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7960 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7961 libmono-security2.0-cil libmono-sharpzip2.84-cil
7962 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
7963 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
7964 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
7965 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
7966 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
7967 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
7968 libxalan2-java libxerces2-java media-player-info mesa-utils
7969 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
7970 nautilus-sendto-empathy openoffice.org-writer2latex
7971 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
7972 python-aptdaemon python-aptdaemon-gtk python-axiom
7973 python-beautifulsoup python-bugbuddy python-clientform
7974 python-coherence python-configobj python-crypto python-cupshelpers
7975 python-cupsutils python-eggtrayicon python-elementtree
7976 python-epsilon python-evolution python-feedparser python-gdata
7977 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7978 python-gtksourceview2 python-httplib2 python-louie python-mako
7979 python-markupsafe python-mechanize python-nevow python-notify
7980 python-opengl python-openssl python-pam python-pkg-resources
7981 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7982 python-tagpy python-twisted-bin python-twisted-conch
7983 python-twisted-core python-twisted-web python-utidylib python-webkit
7984 python-xdg python-zope.interface remmina remmina-plugin-data
7985 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7986 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7987 software-center svgalibg1 system-config-printer-udev
7988 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
7989 totem totem-coherence totem-mozilla totem-plugins
7990 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7991 zip
7992 &lt;/p&gt;&lt;/blockquote&gt;
7993
7994 Installed using apt-get, removed with aptitude
7995
7996 &lt;blockquote&gt;&lt;p&gt;
7997 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7998 epiphany-extensions epiphany-gecko evolution-exchange
7999 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8000 gedit-common gnome-app-install gnome-games gnome-games-data
8001 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8002 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8003 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8004 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
8005 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
8006 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
8007 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
8008 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8009 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8010 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8011 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
8012 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
8013 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8014 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8015 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8016 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8017 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
8018 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
8019 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
8020 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
8021 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
8022 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8023 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8024 sound-juicer swfdec-gnome system-config-printer totem-common
8025 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8026 &lt;/p&gt;&lt;/blockquote&gt;
8027
8028 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8029
8030 &lt;blockquote&gt;&lt;p&gt;
8031 gstreamer0.10-gnomevfs
8032 &lt;/p&gt;&lt;/blockquote&gt;
8033
8034 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8035
8036 &lt;blockquote&gt;&lt;p&gt;
8037 [nothing]
8038 &lt;/p&gt;&lt;/blockquote&gt;
8039
8040 &lt;p&gt;This is for KDE:&lt;/p&gt;
8041
8042 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8043
8044 &lt;blockquote&gt;&lt;p&gt;
8045 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
8046 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8047 ghostscript-x git gnome-audio gnugo granatier gs-common
8048 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8049 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8050 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8051 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8052 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8053 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8054 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8055 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8056 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8057 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8058 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8059 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
8060 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8061 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8062 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8063 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8064 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8065 libkrossui4 libmailtools-perl libmime-tools-perl
8066 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8067 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8068 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8069 lirc luatex marble networkstatus noatun-plugins
8070 openoffice.org-writer2latex palapeli palapeli-data parley
8071 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8072 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8073 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8074 ttf-sazanami-gothic
8075 &lt;/p&gt;&lt;/blockquote&gt;
8076
8077 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8078
8079 &lt;blockquote&gt;&lt;p&gt;
8080 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8081 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8082 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8083 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8084 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8085 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8086 kitchensync kiten kjumpingcube klatin klettres klickety klines
8087 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8088 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8089 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8090 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8091 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8092 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8093 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8094 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8095 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8096 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8097 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8098 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8099 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8100 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8101 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8102 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8103 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8104 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8105 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8106 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8107 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8108 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8109 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8110 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8111 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8112 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8113 &lt;/p&gt;&lt;/blockquote&gt;
8114
8115 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8116
8117 &lt;blockquote&gt;&lt;p&gt;
8118 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8119 kdeartwork kdebase kdebase-apps kdebase-workspace
8120 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8121 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8122 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8123 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8124 xscreensaver-screensaver-bsod
8125 &lt;/p&gt;&lt;/blockquote&gt;
8126
8127 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8128
8129 &lt;blockquote&gt;&lt;p&gt;
8130 kdebase-bin konq-plugins konqueror
8131 &lt;/p&gt;&lt;/blockquote&gt;
8132 </description>
8133 </item>
8134
8135 <item>
8136 <title>Gnash buildbot slave and Debian kfreebsd</title>
8137 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8139 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8140 <description>&lt;p&gt;Answering
8141 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8142 call from the Gnash project&lt;/a&gt; for
8143 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8144 current source, I have set up a virtual KVM machine on the Debian
8145 Edu/Skolelinux virtualization host to test the git source on
8146 Debian/Squeeze. I hope this can help the developers in getting new
8147 releases out more often.&lt;/p&gt;
8148
8149 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8150 I have considered setting up a &lt;a
8151 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8152 machine as well. I have also considered using the kfreebsd
8153 architecture in Debian as a file server in NUUG to get access to the 5
8154 TB zfs volume we currently use to store DV video. Because of this, I
8155 finally got around to do a test installation of Debian/Squeeze with
8156 kfreebsd. Installation went fairly smooth, thought I noticed some
8157 visual glitches in the cdebconf dialogs (black cursor left on the
8158 screen at random locations). Have not gotten very far with the
8159 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8160 fatal problem. Have to spend some more time on it to see if it is
8161 useful as a file server for NUUG. Will try to find time to set up a
8162 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8163 </description>
8164 </item>
8165
8166 <item>
8167 <title>Debian in 3D</title>
8168 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8170 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8171 <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;
8172
8173 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8174 3D linked in from
8175 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8176 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8177 </description>
8178 </item>
8179
8180 <item>
8181 <title>Software updates 2010-10-24</title>
8182 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8183 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8184 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8185 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8186
8187 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8188 raise money for the project is going well. The lower limit of 10
8189 signers was reached in 24 hours, and so far 13 people have signed it.
8190 More signers and more funding is most welcome, and I am really curious
8191 how far we can get before the time limit of December 24 is reached.
8192 :)&lt;/p&gt;
8193
8194 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
8195 about what appear to be a great code coverage tool capable of
8196 generating code coverage stats without any changes to the source code.
8197 It is called
8198 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
8199 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
8200 It is missing in Debian, but the git source built just fine in Squeeze
8201 after I installed libelf-dev, libdwarf-dev, pkg-config and
8202 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8203 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
8204
8205 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
8206 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
8207 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
8208 alpha test release of the Squeeze based Debian Edu /
8209 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
8210 release. Give it a try if you need a complete linux solution for your
8211 school, including central infrastructure server, workstations, thin
8212 client servers and diskless workstations. A nice touch added
8213 yesterday is RDP support on the thin client servers, for windows
8214 clients to get a Linux desktop on request.&lt;/p&gt;
8215 </description>
8216 </item>
8217
8218 <item>
8219 <title>Some notes on Flash in Debian and Debian Edu</title>
8220 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
8221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
8222 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
8223 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
8224 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
8225 second most popular used package that is missing in Debian. The sixth
8226 most popular is flashplayer-mozilla. This is a clear indication that
8227 working flash is important for Debian users. Around 10 percent of the
8228 users submitting data to popcon.debian.org have this package
8229 installed.&lt;/p&gt;
8230
8231 &lt;p&gt;In the report written by Lars Risan in August 2008
8232&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
8233 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8234 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
8235 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8236 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
8237 web sites require Flash to work, and lacking working Flash support in
8238 the web browser and the problems with installing it was perceived as a
8239 good reason to stay with Windows.&lt;/p&gt;
8240
8241 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
8242 said to be the retarded cousin that did not really understand
8243 everything you told him but could work fairly well. This was a
8244 comment regarding the problems Linux have with proprietary formats and
8245 non-standard web pages, and is sad because it exposes a fairly common
8246 understanding of whose fault it is if web pages that only work in for
8247 example Internet Explorer 6 fail to work on Firefox, and funny because
8248 it explain very well how annoying it is for users when Linux
8249 distributions do not work with the documents they receive or the web
8250 pages they want to visit.&lt;/p&gt;
8251
8252 &lt;p&gt;This is part of the reason why I believe it is important for Debian
8253 and Debian Edu to have a well working Flash implementation in the
8254 distribution, to get at least popular sites as Youtube and Google
8255 Video to working out of the box. For Squeeze, Debian have the chance
8256 to include the latest version of Gnash that will make this happen, as
8257 the new release 0.8.8 was published a few weeks ago and is resting in
8258 unstable. The new version work with more sites that version 0.8.7.
8259 The Gnash maintainers have asked for a freeze exception, but the
8260 release team have not had time to reply to it yet. I hope they agree
8261 with me that Flash is important for the Debian desktop users, and thus
8262 accept the new package into Squeeze.&lt;/p&gt;
8263 </description>
8264 </item>
8265
8266 <item>
8267 <title>Circular package dependencies harms apt recovery</title>
8268 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
8269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
8270 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
8271 <description>&lt;p&gt;I discovered this while doing
8272 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
8273 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
8274 in Debian still got circular dependencies, and it is often claimed
8275 that apt and aptitude should be able to handle this just fine, but
8276 some times these dependency loops causes apt to fail.&lt;/p&gt;
8277
8278 &lt;p&gt;An example is from todays
8279 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
8280 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
8281 causes perl-modules to fail to upgrade. The cause is simple. If a
8282 package fail to unpack, then only part of packages with the circular
8283 dependency might end up being unpacked when unpacking aborts, and the
8284 ones already unpacked will fail to configure in the recovery phase
8285 because its dependencies are unavailable.&lt;/p&gt;
8286
8287 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
8288
8289 &lt;blockquote&gt;&lt;pre&gt;
8290 dpkg: dependency problems prevent configuration of perl-modules:
8291 perl-modules depends on perl (&gt;= 5.10.1-1); however:
8292 Version of perl on system is 5.10.0-19lenny2.
8293 dpkg: error processing perl-modules (--configure):
8294 dependency problems - leaving unconfigured
8295 &lt;/pre&gt;&lt;/blockquote&gt;
8296
8297 &lt;p&gt;The perl/perl-modules circular dependency is already
8298 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
8299 hopefully be solved as soon as possible, but it is not the only one,
8300 and each one of these loops in the dependency tree can cause similar
8301 failures. Of course, they only occur when there are bugs in other
8302 packages causing the unpacking to fail, but it is rather nasty when
8303 the failure of one package causes the problem to become worse because
8304 of dependency loops.&lt;/p&gt;
8305
8306 &lt;p&gt;Thanks to
8307 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
8308 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
8309 dependencies
8310 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
8311 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
8312
8313 &lt;p&gt;Todays testing also exposed a bug in
8314 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
8315 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
8316 apt-get and aptitude, the latter possibly caused by some circular
8317 dependency. Reported both to BTS to try to get someone to look at
8318 it.&lt;/p&gt;
8319 </description>
8320 </item>
8321
8322 <item>
8323 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
8324 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
8325 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
8326 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
8327 <description>&lt;p&gt;This is a
8328 &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;
8329 on my
8330 &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
8331 work&lt;/a&gt; on
8332 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
8333 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
8334
8335 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
8336 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8337 and dhcp3-server-ldap in Debian use the LDAP server. The two
8338 implementations are quite different in how they use LDAP.&lt;/p&gt;
8339
8340 To get this information, I started slapd with debugging enabled and
8341 dumped the debug output to a file to get the LDAP searches performed
8342 on a Debian Edu main-server. Here is a summary.
8343
8344 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
8345
8346 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
8347 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
8348 the web.
8349
8350 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
8351 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
8352 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
8353 reverse entries are in two different subtrees in LDAP with a structure
8354 based on the DNS names, as in tjener.intern and
8355 2.2.0.10.in-addr.arpa.&lt;/p&gt;
8356
8357 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
8358 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
8359 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
8360 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
8361 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
8362 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
8363 forward entries, it is looking for attributes named dnsttl, arecord,
8364 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8365 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8366 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8367 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8368 spfrecord and modifytimestamp. For reverse entries it is looking for
8369 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8370 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8371 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8372 ldapsearch commands could look like this:&lt;/p&gt;
8373
8374 &lt;blockquote&gt;&lt;pre&gt;
8375 ldapsearch -h ldap \
8376 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8377 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8378 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8379 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8380 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8381 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8382
8383 ldapsearch -h ldap \
8384 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8385 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
8386 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8387 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8388 srvrecord naptrrecord modifytimestamp
8389 &lt;/pre&gt;&lt;/blockquote&gt;
8390
8391 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
8392 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8393 example LDAP objects used there. In addition to these objects, the
8394 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8395 also exist.&lt;/p&gt;
8396
8397 &lt;blockquote&gt;&lt;pre&gt;
8398 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8399 objectclass: top
8400 objectclass: dnsdomain
8401 objectclass: domainrelatedobject
8402 dc: tjener
8403 arecord: 10.0.2.2
8404 associateddomain: tjener.intern
8405
8406 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8407 objectclass: top
8408 objectclass: dnsdomain2
8409 objectclass: domainrelatedobject
8410 dc: 2
8411 ptrrecord: tjener.intern
8412 associateddomain: 2.2.0.10.in-addr.arpa
8413 &lt;/pre&gt;&lt;/blockquote&gt;
8414
8415 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8416 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8417 same base as in the tree mode for a object with filter
8418 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8419 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8420 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8421 naptrrecord and modifytimestamp. For reverse entires it also do a
8422 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8423 and the requested attributes are associateddomain, dnsttl and
8424 modifytimestamp. In short, in strict mode the objects with ptrrecord
8425 go away, and the arecord attribute in the forward object is used
8426 instead.&lt;/p&gt;
8427
8428 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8429 like this:&lt;/p&gt;
8430
8431 &lt;blockquote&gt;&lt;pre&gt;
8432 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8433 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8434 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8435 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8436 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8437 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8438
8439 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8440 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8441 &lt;/pre&gt;&lt;/blockquote&gt;
8442
8443 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8444 search for SOA records, which behave similar to the forward and
8445 reverse lookups.&lt;/p&gt;
8446
8447 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8448 specify any objectclass names, and instead look for the attributes it
8449 need to generate a DNS reply. This make it able to work with any
8450 objectclass that provide the needed attributes.&lt;/p&gt;
8451
8452 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8453 dnsdomain2 schemas. The latter is used for reverse entries like
8454 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8455
8456 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8457 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8458 attributes) and domainrelatedobject (for associatedDomain). The use
8459 of structural object classes make it impossible to combine these
8460 classes with the object classes used by DHCP.&lt;/p&gt;
8461
8462 &lt;p&gt;There are other schemas that could be used too, for example the
8463 dnszone structural object class used by Gosa and bind-sdb for the DNS
8464 attributes combined with the domainrelatedobject object class, but in
8465 this case some unused attributes would have to be included as well
8466 (zonename and relativedomainname).&lt;/p&gt;
8467
8468 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8469 mode and not use any of the existing objectclasses (dnsdomain,
8470 dnsdomain2 and dnszone) when one want to combine the DNS information
8471 with DHCP information, and instead create a auxiliary object class
8472 defined something like this (using the attributes defined for
8473 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8474
8475 &lt;blockquote&gt;&lt;pre&gt;
8476 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8477 SUP top
8478 AUXILIARY
8479 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8480 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8481 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8482 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8483 A6Record $ DNAMERecord
8484 ))
8485 &lt;/pre&gt;&lt;/blockquote&gt;
8486
8487 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8488 the domainrelatedobject object class, and allow any entity to include
8489 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8490 developers asking for their view on this schema and if they are
8491 interested in providing such schema with PowerDNS, and I hope my
8492 message will be accepted into their mailing list soon.&lt;/p&gt;
8493
8494 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8495
8496 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8497 the object attributes, and then uses the attributes it want. This
8498 make it harder to figure out exactly what attributes are used, but
8499 thanks to the working example in Debian Edu I can at least get an idea
8500 what is needed without having to read the source code.&lt;/p&gt;
8501
8502 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8503 search filter to use to locate the correct dhcpServer entity is
8504 stored. These are the relevant entries from
8505 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8506
8507 &lt;blockquote&gt;&lt;pre&gt;
8508 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8509 ldap-dhcp-server-cn &quot;dhcp&quot;;
8510 &lt;/pre&gt;&lt;/blockquote&gt;
8511
8512 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8513 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8514 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8515 search result is this entry:&lt;/p&gt;
8516
8517 &lt;blockquote&gt;&lt;pre&gt;
8518 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8519 cn: dhcp
8520 objectClass: top
8521 objectClass: dhcpServer
8522 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8523 &lt;/pre&gt;&lt;/blockquote&gt;
8524
8525 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8526 subtree with DHCP configuration. The DHCP configuration subtree base
8527 is located using a base scope search with base &quot;cn=DHCP
8528 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8529 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8530 The search result is this entry:&lt;/p&gt;
8531
8532 &lt;blockquote&gt;&lt;pre&gt;
8533 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8534 cn: DHCP Config
8535 objectClass: top
8536 objectClass: dhcpService
8537 objectClass: dhcpOptions
8538 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8539 dhcpStatements: ddns-update-style none
8540 dhcpStatements: authoritative
8541 dhcpOption: smtp-server code 69 = array of ip-address
8542 dhcpOption: www-server code 72 = array of ip-address
8543 dhcpOption: wpad-url code 252 = text
8544 &lt;/pre&gt;&lt;/blockquote&gt;
8545
8546 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8547 all the DHCP configuration is loaded, it is ready to receive requests.
8548 The subtree in Debian Edu contain objects with object classes
8549 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8550 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8551 and information about netmasks, dynamic range etc. Leaving out the
8552 details here because it is not relevant for the focus of my
8553 investigation, which is to see if it is possible to merge dns and dhcp
8554 related computer objects.&lt;/p&gt;
8555
8556 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8557 of the client (00:00:00:00:00:00 in this example), using a subtree
8558 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8559 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8560 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8561 like:&lt;/p&gt;
8562
8563 &lt;blockquote&gt;&lt;pre&gt;
8564 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8565 cn: hostname
8566 objectClass: top
8567 objectClass: dhcpHost
8568 dhcpHWAddress: ethernet 00:00:00:00:00:00
8569 dhcpStatements: fixed-address hostname
8570 &lt;/pre&gt;&lt;/blockquote&gt;
8571
8572 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8573 The object classes need to have fixed names, and the configuration
8574 need to be stored in a fairly specific LDAP structure. On the
8575 positive side, the invidiual dhcpHost entires can be anywhere without
8576 the DN pointed to by the dhcpServer entries. The latter should make
8577 it possible to group all host entries in a subtree next to the
8578 configuration entries, and this subtree can also be shared with the
8579 DNS server if the schema proposed above is combined with the dhcpHost
8580 structural object class.
8581
8582 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8583
8584 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8585 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8586 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8587 allowing DNS objects to be stored anywhere under the base cn specified
8588 in the configuration.&lt;/p&gt;
8589
8590 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8591 regarding which LDAP schemas to use and which LDAP structure to use.
8592 I guess one could implement ones own schema, as long as the
8593 objectclasses and attributes have the names used, but this do not
8594 really help when the DHCP subtree need to have a fairly fixed
8595 structure.&lt;/p&gt;
8596
8597 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8598 this might work for Debian Edu:&lt;/p&gt;
8599
8600 &lt;blockquote&gt;&lt;pre&gt;
8601 ou=services
8602 cn=machine-info (dhcpService) - dhcpServiceDN points here
8603 cn=dhcp (dhcpServer)
8604 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8605 cn=10.0.2.0 (dhcpSubnet)
8606 cn=group1 (dhcpGroup/dhcpOptions)
8607 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8608 cn=192.168.0.0 (dhcpSubnet)
8609 cn=group1 (dhcpGroup/dhcpOptions)
8610 ou=machines - PowerDNS base points here
8611 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8612 &lt;/pre&gt;&lt;/blockquote&gt;
8613
8614 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8615 entries to be in the dhcpGroup subtrees, the entries can be stored
8616 there instead of a common machines subtree, and the PowerDNS base
8617 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8618
8619 &lt;p&gt;The combined object under the machines subtree would look something
8620 like this:&lt;/p&gt;
8621
8622 &lt;blockquote&gt;&lt;pre&gt;
8623 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8624 dc: hostname
8625 objectClass: top
8626 objectClass: dhcpHost
8627 objectclass: domainrelatedobject
8628 objectclass: dnsDomainAux
8629 associateddomain: hostname.intern
8630 arecord: 10.11.12.13
8631 dhcpHWAddress: ethernet 00:00:00:00:00:00
8632 dhcpStatements: fixed-address hostname.intern
8633 &lt;/pre&gt;&lt;/blockquote&gt;
8634
8635 &lt;/p&gt;One could even add the LTSP configuration associated with a given
8636 machine, as long as the required attributes are available in a
8637 auxiliary object class.&lt;/p&gt;
8638 </description>
8639 </item>
8640
8641 <item>
8642 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
8643 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
8644 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
8645 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
8646 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
8647 DHCP services in Debian Edu to use the same LDAP objects for a given
8648 computer, to avoid the possibility of having a inconsistent state for
8649 a computer in LDAP (as in DHCP but no DNS entry or the other way
8650 around) and make it easier to add computers to LDAP.&lt;/p&gt;
8651
8652 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
8653 information finally found a solution that seem to work.&lt;/p&gt;
8654
8655 &lt;p&gt;The old setup required three LDAP objects for a given computer.
8656 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8657 we switch powerdns to use its strict LDAP method (ldap-method=strict
8658 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8659 merged into one while making it impossible to transfer the reverse map
8660 to a slave DNS server.&lt;/p&gt;
8661
8662 &lt;p&gt;If we also replace the object class used to get the DNS related
8663 attributes to one allowing these attributes to be combined with the
8664 dhcphost object class, we can merge the DNS and DHCP entries into one.
8665 I&#39;ve written such object class in the dnsdomainaux.schema file (need
8666 proper OIDs, but that is a minor issue), and tested the setup. It
8667 seem to work.&lt;/p&gt;
8668
8669 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
8670 for both DNS and DHCP, and even the LTSP configuration I suggested in
8671 an earlier email. The combined LDAP object will look something like
8672 this:&lt;/p&gt;
8673
8674 &lt;blockquote&gt;&lt;pre&gt;
8675 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8676 cn: hostname
8677 objectClass: dhcphost
8678 objectclass: domainrelatedobject
8679 objectclass: dnsdomainaux
8680 associateddomain: hostname.intern
8681 arecord: 10.11.12.13
8682 dhcphwaddress: ethernet 00:00:00:00:00:00
8683 dhcpstatements: fixed-address hostname
8684 ldapconfigsound: Y
8685 &lt;/pre&gt;&lt;/blockquote&gt;
8686
8687 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
8688 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8689 before asking DNS to resolve the fixed-adddress. LTSP will use
8690 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
8691
8692 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
8693 dhcphost in a different location, to allow us to put the objects
8694 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
8695 that. If I can&#39;t figure out a way to do that, we can still get rid of
8696 the hosts subtree and move all its content into the DHCP Config tree
8697 (which probably should be renamed to be more related to the new
8698 content. I suspect cn=dnsdhcp,ou=services or something like that
8699 might be a good place to put it.&lt;/p&gt;
8700
8701 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8702 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8703 </description>
8704 </item>
8705
8706 <item>
8707 <title>Idea for storing LTSP configuration in LDAP</title>
8708 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
8709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
8710 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
8711 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
8712 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8713 clients, and that this can be used to fetch configuration from LDAP if
8714 Debian Edu choose to store configuration there.&lt;/p&gt;
8715
8716 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
8717 to get configuration from LDAP. The idea is to look up the MAC
8718 address of the client in LDAP, and look for attributes on the form
8719 ltspconfigsetting=value, and use this to export SETTING=value to the
8720 LTSP clients.&lt;/p&gt;
8721
8722 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
8723 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
8724 allowing us to store all information about a computer in one place.&lt;/p&gt;
8725
8726 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
8727 this approach. A real LDAP schema for the ltspClientAux objectclass
8728 need to be written. Comments, suggestions, etc?&lt;/p&gt;
8729
8730 &lt;blockquote&gt;&lt;pre&gt;
8731 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8732 #
8733 # Fetch LTSP client settings from LDAP based on MAC address
8734 #
8735 # Uses ethernet address as stored in the dhcpHost objectclass using
8736 # the dhcpHWAddress attribute or ethernet address stored in the
8737 # ieee802Device objectclass with the macAddress attribute.
8738 #
8739 # This module is written to be schema agnostic, and only depend on the
8740 # existence of attribute names.
8741 #
8742 # The LTSP configuration variables are saved directly using a
8743 # ltspConfig prefix and uppercasing the rest of the attribute name.
8744 # To set the SERVER variable, set the ltspConfigServer attribute.
8745 #
8746 # Some LDAP schema should be created with all the relevant
8747 # configuration settings. Something like this should work:
8748 #
8749 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
8750 # SUP top
8751 # AUXILIARY
8752 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8753
8754 LDAPSERVER=$(debian-edu-ldapserver)
8755 if [ &quot;$LDAPSERVER&quot; ] ; then
8756 LDAPBASE=$(debian-edu-ldapserver -b)
8757 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
8758 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
8759 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
8760 grep &#39;^ltspConfig&#39; | while read attr value ; do
8761 # Remove prefix and convert to upper case
8762 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
8763 # bass value on to clients
8764 eval &quot;$attr=$value; export $attr&quot;
8765 done
8766 done
8767 fi
8768 &lt;/pre&gt;&lt;/blockquote&gt;
8769
8770 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
8771 the while block might end up in a subshell causing the variables set
8772 there to not show up in ltsp-config, but if that is the case I am sure
8773 the code can be restructured to make sure the variables are passed on.
8774 I expect that can be solved with some testing. :)&lt;/p&gt;
8775
8776 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8777 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8778
8779 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
8780 configuration in LDAP that was created around year 2000 by
8781 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
8782 Xperience, Inc., 2000&lt;/a&gt;. I found its
8783 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
8784 personal home page over at redhat.com.&lt;/p&gt;
8785 </description>
8786 </item>
8787
8788 <item>
8789 <title>jXplorer, a very nice LDAP GUI</title>
8790 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
8791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
8792 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
8793 <description>&lt;p&gt;Since
8794 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
8795 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
8796 LDAP GUI that is even better than luma. The java application
8797 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
8798 moving LDAP objects and subtrees using drag-and-drop, and can
8799 authenticate using Kerberos. I have only tested the Kerberos
8800 authentication, but do not have a LDAP setup allowing me to rewrite
8801 LDAP with my test user yet. It is
8802 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
8803 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
8804 have with it is how it handle errors. If something go wrong, its
8805 non-intuitive behaviour require me to go through some query work list
8806 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
8807 </description>
8808 </item>
8809
8810 <item>
8811 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
8812 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
8813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
8814 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
8815 <description>&lt;p&gt;Here is a short update on my &lt;a
8816 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
8817 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
8818 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
8819 not reporting the status for KDE, because the upgrade crashes when
8820 aptitude try because of missing conflicts
8821 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
8822 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
8823
8824 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
8825 complete list of the installed packages. Based on this I see these
8826 differences when I did a test run today. As usual, I do not really
8827 know what the correct set of packages would be, but thought it best to
8828 publish the difference.&lt;/p&gt;
8829
8830 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8831
8832 &lt;blockquote&gt;&lt;p&gt;
8833 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
8834 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
8835 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8836 libgtksourceview-common libpt-1.10.10-plugins-alsa
8837 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8838 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8839 python-4suite-xml python-eggtrayicon python-gtkhtml2
8840 python-gtkmozembed svgalibg1 xserver-xephyr zip
8841 &lt;/p&gt;&lt;/blockquote&gt;
8842
8843 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8844
8845 &lt;blockquote&gt;&lt;p&gt;
8846 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8847 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8848 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
8849 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
8850 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
8851 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
8852 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8853 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8854 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8855 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
8856 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
8857 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
8858 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8859 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
8860 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8861 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
8862 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
8863 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8864 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8865 mysql-common swfdec-gnome totem-gstreamer wodim
8866 &lt;/p&gt;&lt;/blockquote&gt;
8867
8868 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8869
8870 &lt;blockquote&gt;&lt;p&gt;
8871 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8872 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8873 xserver-xorg-input-all xserver-xorg-input-evdev
8874 xserver-xorg-input-kbd xserver-xorg-input-mouse
8875 xserver-xorg-input-synaptics xserver-xorg-video-all
8876 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8877 xserver-xorg-video-chips xserver-xorg-video-cirrus
8878 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8879 xserver-xorg-video-glint xserver-xorg-video-i128
8880 xserver-xorg-video-i740 xserver-xorg-video-mach64
8881 xserver-xorg-video-mga xserver-xorg-video-neomagic
8882 xserver-xorg-video-nouveau xserver-xorg-video-nv
8883 xserver-xorg-video-r128 xserver-xorg-video-radeon
8884 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8885 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8886 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8887 xserver-xorg-video-sis xserver-xorg-video-sisusb
8888 xserver-xorg-video-tdfx xserver-xorg-video-tga
8889 xserver-xorg-video-trident xserver-xorg-video-tseng
8890 xserver-xorg-video-vesa xserver-xorg-video-vmware
8891 xserver-xorg-video-voodoo
8892 &lt;/p&gt;&lt;/blockquote&gt;
8893
8894 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8895
8896 &lt;blockquote&gt;&lt;p&gt;
8897 deskbar-applet xserver-xorg xserver-xorg-core
8898 xserver-xorg-input-wacom xserver-xorg-video-intel
8899 xserver-xorg-video-openchrome
8900 &lt;/p&gt;&lt;/blockquote&gt;
8901
8902 &lt;p&gt;I was told on IRC that the xorg-xserver package was
8903 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
8904 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
8905 No idea when it hits Squeeze, but when it does I hope it will reduce
8906 the difference somewhat.
8907 </description>
8908 </item>
8909
8910 <item>
8911 <title>LUMA, a very nice LDAP GUI</title>
8912 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
8913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
8914 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
8915 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
8916 directory in Debian Edu, and in the process I started to miss a GUI
8917 tool to browse the LDAP tree. The only one I was able to find in
8918 Debian/Squeeze and Lenny is
8919 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
8920 be a great tool to get a overview of the current LDAP directory
8921 populated by default in Skolelinux. Thanks to it, I have been able to
8922 find empty and obsolete subtrees, misplaced objects and duplicate
8923 objects. It will be installed by default in Debian/Squeeze. If you
8924 are working with LDAP, give it a go. :)&lt;/p&gt;
8925
8926 &lt;p&gt;I did notice one problem with it I have not had time to report to
8927 the BTS yet. There is no .desktop file in the package, so the tool do
8928 not show up in the Gnome and KDE menus, but only deep down in in the
8929 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8930 released.&lt;/p&gt;
8931
8932 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
8933 like to move objects and remove subtrees directly in the GUI, but have
8934 not found a way to do that with LUMA yet. So in the mean time, I use
8935 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
8936
8937 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
8938 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8939
8940 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
8941 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
8942 useful GUI alternative. It seem like a good tool, but is unmaintained
8943 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8944 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
8945 </description>
8946 </item>
8947
8948 <item>
8949 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
8950 <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>
8951 <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>
8952 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
8953 <description>&lt;p&gt;A while back, I
8954 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
8955 about the fact&lt;/a&gt; that it is not possible with the provided schemas
8956 for storing DNS and DHCP information in LDAP to combine the two sets
8957 of information into one LDAP object representing a computer.&lt;/p&gt;
8958
8959 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
8960 the dhcpHost object class auxiliary, to allow it to be combined with
8961 the dNSDomain object class, and thus forming one object for one
8962 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
8963
8964 &lt;p&gt;If I understand this correctly, it is not safe to do this change
8965 without also changing the assigned number for the object class, and I
8966 do not know enough about LDAP schema design to do that properly for
8967 Debian Edu.&lt;/p&gt;
8968
8969 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
8970 the
8971 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
8972 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
8973 available today from IETF.&lt;/p&gt;
8974
8975 &lt;pre&gt;
8976 --- dhcp.schema (revision 65192)
8977 +++ dhcp.schema (working copy)
8978 @@ -376,7 +376,7 @@
8979 objectclass ( 2.16.840.1.113719.1.203.6.6
8980 NAME &#39;dhcpHost&#39;
8981 DESC &#39;This represents information about a particular client&#39;
8982 - SUP top
8983 + SUP top AUXILIARY
8984 MUST cn
8985 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8986 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
8987 &lt;/pre&gt;
8988
8989 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
8990 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8991 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
8992
8993 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8994 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8995 </description>
8996 </item>
8997
8998 <item>
8999 <title>Calling tasksel like the installer, while still getting useful output</title>
9000 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
9001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
9002 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
9003 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
9004 installs packages during the normal debian-installer run. Until now,
9005 I have ended up letting tasksel do the work, with the annoying problem
9006 of not getting any feedback at all when something fails (like a
9007 conffile question from dpkg or a download that fails), using code like
9008 this:
9009
9010 &lt;blockquote&gt;&lt;pre&gt;
9011 export DEBIAN_FRONTEND=noninteractive
9012 tasksel --new-install
9013 &lt;/pre&gt;&lt;/blockquote&gt;
9014
9015 This would invoke tasksel, let its automatic task selection pick the
9016 tasks to install, and continue to install the requested tasks without
9017 any output what so ever.
9018
9019 Recently I revisited this problem while working on the automatic
9020 package upgrade testing, because tasksel would some times hang without
9021 any useful feedback, and I want to see what is going on when it
9022 happen. Then it occured to me, I can parse the output from tasksel
9023 when asked to run in test mode, and use that aptitude command line
9024 printed by tasksel then to simulate the tasksel run. I ended up using
9025 code like this:
9026
9027 &lt;blockquote&gt;&lt;pre&gt;
9028 export DEBIAN_FRONTEND=noninteractive
9029 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
9030 $cmd
9031 &lt;/pre&gt;&lt;/blockquote&gt;
9032
9033 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
9034 --without-recommends -o APT::Install-Recommends=no -y install
9035 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9036 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
9037 laptop task and all packages with priority standard , required and
9038 important, just like tasksel would have done it during
9039 installation.&lt;/p&gt;
9040
9041 &lt;p&gt;A better approach is probably to extend tasksel to be able to
9042 install packages without using debconf-apt-progress, for use cases
9043 like this.&lt;/p&gt;
9044 </description>
9045 </item>
9046
9047 <item>
9048 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
9049 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
9050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
9051 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
9052 <description>&lt;p&gt;My
9053 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
9054 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
9055 finally made the upgrade logs available from
9056 &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;.
9057 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9058 apt and aptitude, and found their differences interesting. This time
9059 I will only focus on their removal plans.&lt;/p&gt;
9060
9061 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
9062 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
9063 surprising part is that it want to remove xorg and all
9064 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9065 sure why. When asking aptitude to do the same, it want to remove 129
9066 packages, but most of them are library packages I suspect are no
9067 longer needed. Both of them want to remove bluetooth packages, which
9068 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
9069
9070 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
9071 which seem like a bad idea and xorg the same way as with Gnome. Asking
9072 aptitude for the same, it wants to remove 192 packages, none which are
9073 too surprising.&lt;/p&gt;
9074
9075 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
9076 and avoided, and perhaps others as well. Here are the complete list
9077 of planned removals. The complete logs is available from the URL
9078 above. Note if you want to repeat these tests, that the upgrade test
9079 for kde+apt-get hung in the tasksel setup because of dpkg asking
9080 conffile questions. No idea why. I worked around it by using
9081 &#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
9082 continue.&lt;/p&gt;
9083
9084 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
9085 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
9086 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9087 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9088 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9089 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9090 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9091 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9092 xserver-xorg-input-kbd xserver-xorg-input-mouse
9093 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9094 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9095 xserver-xorg-video-ati xserver-xorg-video-chips
9096 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9097 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9098 xserver-xorg-video-glint xserver-xorg-video-i128
9099 xserver-xorg-video-i740 xserver-xorg-video-imstt
9100 xserver-xorg-video-intel xserver-xorg-video-mach64
9101 xserver-xorg-video-mga xserver-xorg-video-neomagic
9102 xserver-xorg-video-nsc xserver-xorg-video-nv
9103 xserver-xorg-video-openchrome xserver-xorg-video-r128
9104 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9105 xserver-xorg-video-rendition xserver-xorg-video-s3
9106 xserver-xorg-video-s3virge xserver-xorg-video-savage
9107 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9108 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9109 xserver-xorg-video-tga xserver-xorg-video-trident
9110 xserver-xorg-video-tseng xserver-xorg-video-v4l
9111 xserver-xorg-video-vesa xserver-xorg-video-vga
9112 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9113 xulrunner-1.9-gnome-support&lt;/p&gt;
9114
9115 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9116
9117 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9118 djvulibre-desktop finger gnome-app-install gnome-mount
9119 gnome-network-admin gnome-spell gnome-vfs-obexftp
9120 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9121 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9122 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9123 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9124 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9125 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9126 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9127 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9128 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9129 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9130 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9131 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9132 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9133 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9134 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9135 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9136 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9137 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9138 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9139 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9140 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9141 openoffice.org-writer2latex openssl-blacklist p7zip
9142 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9143 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9144 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9145 swfdec-mozilla totem-gstreamer update-manager wodim
9146 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9147 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9148 zip&lt;/p&gt;
9149
9150 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9151
9152 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9153 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9154 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9155 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9156 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9157 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9158 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9159 xserver-xorg-input-kbd xserver-xorg-input-mouse
9160 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9161 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9162 xserver-xorg-video-ati xserver-xorg-video-chips
9163 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9164 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9165 xserver-xorg-video-glint xserver-xorg-video-i128
9166 xserver-xorg-video-i740 xserver-xorg-video-imstt
9167 xserver-xorg-video-intel xserver-xorg-video-mach64
9168 xserver-xorg-video-mga xserver-xorg-video-neomagic
9169 xserver-xorg-video-nsc xserver-xorg-video-nv
9170 xserver-xorg-video-openchrome xserver-xorg-video-r128
9171 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9172 xserver-xorg-video-rendition xserver-xorg-video-s3
9173 xserver-xorg-video-s3virge xserver-xorg-video-savage
9174 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9175 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9176 xserver-xorg-video-tga xserver-xorg-video-trident
9177 xserver-xorg-video-tseng xserver-xorg-video-v4l
9178 xserver-xorg-video-vesa xserver-xorg-video-vga
9179 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9180
9181 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9182 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9183 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9184 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9185 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9186 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9187 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9188 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9189 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9190 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9191 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9192 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9193 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9194 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9195 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9196 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9197 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9198 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9199 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9200 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
9201 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9202 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9203 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
9204 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9205 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9206 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9207 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9208 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9209 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
9210 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
9211 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9212 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9213 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9214 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9215 texlive-common texlive-doc-base texlive-fonts-recommended
9216 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9217 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9218 xulrunner-1.9&lt;/p&gt;
9219
9220 </description>
9221 </item>
9222
9223 <item>
9224 <title>Automatic upgrade testing from Lenny to Squeeze</title>
9225 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
9226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
9227 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
9228 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
9229 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9230 have been discovered and reported in the process
9231 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
9232 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
9233 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
9234 kdebase-workspace-data), and to get a more regular testing going on, I
9235 am working on a script to automate the test.&lt;/p&gt;
9236
9237 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
9238 Gnome or KDE desktop installation inside the chroot before upgrading
9239 it. To ensure no services are started in the chroot, a policy-rc.d
9240 script is inserted. To make sure tasksel believe it is to install a
9241 desktop on a laptop, the tasksel tests are replaced in the chroot
9242 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
9243
9244 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9245 currently always fail because udev refuses to upgrade with the kernel
9246 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9247 is created. The bug report
9248 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
9249 this problem do not trigger in a chroot, but I touch the file anyway
9250 to make sure the upgrade go well. Testing on virtual and real
9251 hardware have failed me because of udev so far, and creating this file
9252 do the trick in such settings anyway. This is a
9253 &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
9254 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
9255 maintainer because he lack the resources to rewrite udev to keep
9256 working with old kernels or something like that. I really wish the
9257 udev upstream would keep udev backwards compatible, to avoid such
9258 upgrade problem, but given that they fail to do so, I guess
9259 documenting the way out of this mess is the best option we got for
9260 Debian Squeeze.&lt;/p&gt;
9261
9262 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
9263 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
9264 trick:&lt;/p&gt;
9265
9266 &lt;blockquote&gt;&lt;pre&gt;
9267 #!/bin/sh
9268 set -ex
9269
9270 if [ &quot;$1&quot; ] ; then
9271 desktop=$1
9272 else
9273 desktop=gnome
9274 fi
9275
9276 from=lenny
9277 to=squeeze
9278
9279 exec &amp;lt; /dev/null
9280 unset LANG
9281 mirror=http://ftp.skolelinux.org/debian
9282 tmpdir=chroot-$from-upgrade-$to-$desktop
9283 fuser -mv .
9284 debootstrap $from $tmpdir $mirror
9285 chroot $tmpdir aptitude update
9286 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
9287 #!/bin/sh
9288 exit 101
9289 EOF
9290 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9291 exit_cleanup() {
9292 umount $tmpdir/proc
9293 }
9294 mount -t proc proc $tmpdir/proc
9295 # Make sure proc is unmounted also on failure
9296 trap exit_cleanup EXIT INT
9297
9298 chroot $tmpdir aptitude -y install debconf-utils
9299
9300 # Make sure tasksel autoselection trigger. It need the test scripts
9301 # to return the correct answers.
9302 echo tasksel tasksel/desktop multiselect $desktop | \
9303 chroot $tmpdir debconf-set-selections
9304
9305 # Include the desktop and laptop task
9306 for test in desktop laptop ; do
9307 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
9308 #!/bin/sh
9309 exit 2
9310 EOF
9311 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9312 done
9313
9314 DEBIAN_FRONTEND=noninteractive
9315 DEBIAN_PRIORITY=critical
9316 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9317 chroot $tmpdir tasksel --new-install
9318
9319 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
9320 chroot $tmpdir aptitude update
9321 touch $tmpdir/etc/udev/kernel-upgrade
9322 chroot $tmpdir aptitude -y dist-upgrade
9323 fuser -mv
9324 &lt;/pre&gt;&lt;/blockquote&gt;
9325
9326 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
9327 with aptitude, but I have not had time to look at how they behave
9328 differently so far. I hope to get a cron job running to do the test
9329 regularly and post the result on the web. The Gnome upgrade currently
9330 work, while the KDE upgrade fail because of the bug in
9331 kdebase-workspace-data&lt;/p&gt;
9332
9333 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
9334 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
9335 post, so I will refrain from trying. I can report that for Gnome,
9336 aptitude report 760 packages upgraded, 448 newly installed, 129 to
9337 remove and 1 not upgraded and 1024MB need to be downloaded while for
9338 KDE the same numbers are 702 packages upgraded, 507 newly installed,
9339 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
9340
9341 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
9342 is able to migrate to dependency based boot sequencing and parallel
9343 booting without a hitch. Was unsure if there were still bugs with
9344 packages failing to clean up their obsolete init.d script during
9345 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9346 packages.&lt;/p&gt;
9347 </description>
9348 </item>
9349
9350 <item>
9351 <title>Upstart or sysvinit - as init.d scripts see it</title>
9352 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
9353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
9354 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
9355 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
9356 scripts to migrate (some of) their operations to upstart job while
9357 keeping the init.d for hurd and kfreebsd. The packages with such
9358 needs will need a way to get their init.d scripts to behave
9359 differently when used with sysvinit and with upstart. Because of
9360 this, I had a look at the environment variables set when a init.d
9361 script is running under upstart, and when it is not.&lt;/p&gt;
9362
9363 &lt;p&gt;With upstart, I notice these environment variables are set when a
9364 script is started from rcS.d/ (ignoring some irrelevant ones like
9365 COLUMNS):&lt;/p&gt;
9366
9367 &lt;blockquote&gt;&lt;pre&gt;
9368 DEFAULT_RUNLEVEL=2
9369 previous=N
9370 PREVLEVEL=
9371 RUNLEVEL=
9372 runlevel=S
9373 UPSTART_EVENTS=startup
9374 UPSTART_INSTANCE=
9375 UPSTART_JOB=rc-sysinit
9376 &lt;/pre&gt;&lt;/blockquote&gt;
9377
9378 &lt;p&gt;With sysvinit, these environment variables are set for the same
9379 script.&lt;/p&gt;
9380
9381 &lt;blockquote&gt;&lt;pre&gt;
9382 INIT_VERSION=sysvinit-2.88
9383 previous=N
9384 PREVLEVEL=N
9385 RUNLEVEL=S
9386 runlevel=S
9387 &lt;/pre&gt;&lt;/blockquote&gt;
9388
9389 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
9390 sysvinit are not set by upstart. Not sure if it is intentional or not
9391 to not be compatible with sysvinit in this regard.&lt;/p&gt;
9392
9393 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9394 looking for the UPSTART_JOB environment variable seem to be a good
9395 choice.&lt;/p&gt;
9396 </description>
9397 </item>
9398
9399 <item>
9400 <title>A manual for standards wars...</title>
9401 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9403 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9404 <description>&lt;p&gt;Via the
9405 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9406 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9407 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9408 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9409 following the standards wars of today.&lt;/p&gt;
9410 </description>
9411 </item>
9412
9413 <item>
9414 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9415 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9416 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9417 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9418 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9419 to get a list of the machine types in use thanks to the DMI
9420 information extracted from each machine. The script to do so is
9421 included in the sitesummary package, and here is example output from
9422 the Skolelinux build servers:&lt;/p&gt;
9423
9424 &lt;blockquote&gt;&lt;pre&gt;
9425 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9426 vendor count
9427 Dell Computer Corporation 1
9428 PowerEdge 1750 1
9429 IBM 1
9430 eserver xSeries 345 -[8670M1X]- 1
9431 Intel 2
9432 [no-dmi-info] 3
9433 maintainer:~#
9434 &lt;/pre&gt;&lt;/blockquote&gt;
9435
9436 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9437 provided in each machine. Here there are Intel machines without model
9438 information listed with Intel as vendor and no model, and virtual Xen
9439 machines listed as [no-dmi-info]. One can add -l as a command line
9440 option to list the individual machines.&lt;/p&gt;
9441
9442 &lt;p&gt;A larger list is
9443 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9444 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9445 provide the basic sitesummary report publicly. In their report there
9446 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9447 their machines, and as sitesummary is available in both distributions,
9448 it is trivial to get all of them to report to the same central
9449 collector.&lt;/p&gt;
9450 </description>
9451 </item>
9452
9453 <item>
9454 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9455 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9456 <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>
9457 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9458 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9459 start at boot when an NVidia video card is used is handled. The
9460 problem seem to be that the nvidia X.org driver uses a long time to
9461 initialize, and this duration is longer than kdm is configured to
9462 wait.&lt;/p&gt;
9463
9464 &lt;p&gt;I came across two bugs related to this issue,
9465 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9466 against initscripts and passed on to nvidia-glx when it became obvious
9467 that the nvidia drivers were involved, and
9468 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9469 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9470
9471 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9472 problem nvidia video card owners experience and make sure the Debian
9473 distribution work out of the box for these users. The nvidia driver
9474 maintainers expect kdm to be set up to wait longer, while kdm expect
9475 the nvidia driver maintainers to fix the driver to start faster, and
9476 while they wait for each other I guess the users end up switching to a
9477 distribution that work for them. I have no idea what the solution is,
9478 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9479
9480 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9481 </description>
9482 </item>
9483
9484 <item>
9485 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9486 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9487 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9488 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9489 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9490 The feature seem to hold up pretty well, but three fairly serious
9491 issues are known and should be solved:
9492
9493 &lt;p&gt;&lt;ul&gt;
9494
9495 &lt;li&gt;The wicd package seen to
9496 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9497 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9498 parallel booting is enabled. No idea why, but the wicd maintainer
9499 seem to be on the case.&lt;/li&gt;
9500
9501 &lt;li&gt;The nvidia X driver seem to
9502 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9503 triggered more easily when parallel booting is in effect. The
9504 maintainer is on the case.&lt;/li&gt;
9505
9506 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9507 sequencing (the shutdown is broken) when old file-rc users
9508 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9509 sysv-rc. One way to solve it would be for file-rc to create
9510 /etc/init.d/.legacy-bootordering, and another is to try to make
9511 sysv-rc more robust. Will investigate some more and probably upload a
9512 workaround in sysv-rc to help those trying to move from file-rc to
9513 sysv-rc get a working shutdown.&lt;/li&gt;
9514
9515 &lt;/ul&gt;&lt;/p&gt;
9516
9517 &lt;p&gt;All in all not many surprising issues, and all of them seem
9518 solvable before Squeeze is released. In addition to these there are
9519 some packages with bugs in their dependencies and run level settings,
9520 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9521
9522 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9523 the BTS, please usertag the report to get it to show up at
9524 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9525 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9526
9527 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9528 </description>
9529 </item>
9530
9531 <item>
9532 <title>More flexible firmware handling in debian-installer</title>
9533 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9535 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9536 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9537 found time today to return to the project. Having to spend less time
9538 working dependency based boot in debian, as it is almost complete now,
9539 definitely helped freeing some time.&lt;/p&gt;
9540
9541 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9542 include some firmware packages on the Debian Edu CDs, those needed to
9543 get disk and network controllers working. Without having these
9544 firmware packages available during installation, it is impossible to
9545 install Debian Edu on the given machine, and because our target group
9546 are non-technical people, asking them to provide firmware packages on
9547 an external medium is a support pain. Initially, I expected it to be
9548 enough to include the firmware packages on the CD to get
9549 debian-installer to find and use them. This proved to be wrong.
9550 Next, I hoped it was enough to symlink the relevant firmware packages
9551 to some useful location on the CD (tried /cdrom/ and
9552 /cdrom/firmware/). This also proved to not work, and at this point I
9553 found time to look at the debian-installer code to figure out what was
9554 going to work.&lt;/p&gt;
9555
9556 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9557 look revealed that it would only look for firmware packages outside
9558 the installation media, so the CD was never checked for firmware
9559 packages. It would only check USB sticks, floppies and other
9560 &quot;external&quot; media devices. Today I changed it to also look in the
9561 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9562 solve the problem I ran into with Debian edu. I also changed it to
9563 look in /firmware/, to make sure the installer also find firmware
9564 provided in the initrd when booting the installer via PXE, to allow us
9565 to provide the same feature in the PXE setup included in Debian
9566 Edu.&lt;/p&gt;
9567
9568 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9569 activated without asking if the license is accepted, I extended
9570 hw-detect to look for preinst scripts in the firmware packages, and
9571 run these before activating the firmware during installation. The
9572 license question is asked using debconf in the preinst, so this should
9573 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9574
9575 &lt;p&gt;If you want to discuss the details of these features, please
9576 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9577 </description>
9578 </item>
9579
9580 <item>
9581 <title>Parallellized boot is now the default in Debian/unstable</title>
9582 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9584 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9585 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9586 Debian/unstable for machines using dependency based boot sequencing.
9587 Apparently the testing of concurrent booting has been wider than
9588 expected, if I am to believe the
9589 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9590 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9591 with the feature this weekend, to give us some time to detect any
9592 remaining problems before Squeeze is frozen. If serious problems are
9593 detected, it is simple to change the default back to sequential boot.
9594 The upload of the new sysvinit package also activate a new upstream
9595 version.&lt;/p&gt;
9596
9597 More information about
9598 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9599 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9600 currently possible to disable parallel booting when one run into
9601 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9602
9603 &lt;blockquote&gt;&lt;pre&gt;
9604 CONCURRENCY=none
9605 &lt;/pre&gt;&lt;/blockquote&gt;
9606
9607 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9608 the BTS, please usertag the report to get it to show up at
9609 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9610 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9611 </description>
9612 </item>
9613
9614 <item>
9615 <title>Sitesummary tip: Listing MAC address of all clients</title>
9616 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9617 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9618 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9619 <description>&lt;p&gt;In the recent Debian Edu versions, the
9620 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9621 system&lt;/a&gt; is used to keep track of the machines in the school
9622 network. Each machine will automatically report its status to the
9623 central server after boot and once per night. The network setup is
9624 also reported, and using this information it is possible to get the
9625 MAC address of all network interfaces in the machines. This is useful
9626 to update the DHCP configuration.&lt;/p&gt;
9627
9628 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
9629 ist all MAC addresses of all machines reporting to sitesummary. Run
9630 this on the collector host:&lt;/p&gt;
9631
9632 &lt;blockquote&gt;&lt;pre&gt;
9633 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
9634 &lt;/pre&gt;&lt;/blockquote&gt;
9635
9636 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
9637 line per machine and with space between the MAC addresses.&lt;/p&gt;
9638
9639 &lt;p&gt;To allow system administrators easier job at adding static DHCP
9640 addresses for hosts, it would be possible to extend this to fetch
9641 machine information from sitesummary and update the DHCP and DNS
9642 tables in LDAP using this information. Such tool is unfortunately not
9643 written yet.&lt;/p&gt;
9644 </description>
9645 </item>
9646
9647 <item>
9648 <title>systemd, an interesting alternative to upstart</title>
9649 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
9650 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
9651 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
9652 <description>&lt;p&gt;The last few days a new boot system called
9653 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
9654 has been
9655 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
9656
9657 to the free software world. I have not yet had time to play around
9658 with it, but it seem to be a very interesting alternative to
9659 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
9660 a good alternative for Debian when we are able to switch to an event
9661 based boot system. Tollef is
9662 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
9663 systemd into Debian, and I look forward to seeing how well it work. I
9664 like the fact that systemd handles init.d scripts with dependency
9665 information natively, allowing them to run in parallel where upstart
9666 at the moment do not.&lt;/p&gt;
9667
9668 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
9669 platform support. It only work on recent Linux kernels, and also need
9670 some new kernel features enabled to function properly. This means
9671 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9672 system. Not sure how that will be handled if systemd proves to be the
9673 way forward.&lt;/p&gt;
9674
9675 &lt;p&gt;In the mean time, based on the
9676 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9677 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
9678 decided to enable full parallel booting as the default in Debian as
9679 soon as possible (probably this weekend or early next week), to see if
9680 there are any remaining serious bugs in the init.d dependencies. A
9681 new version of the sysvinit package implementing this change is
9682 already in experimental. If all go well, Squeeze will be released
9683 with parallel booting enabled by default.&lt;/p&gt;
9684 </description>
9685 </item>
9686
9687 <item>
9688 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
9689 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
9690 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
9691 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
9692 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
9693 complete, so complete that it is actually possible to run all the
9694 init.d scripts in parallell based on these dependencies. If you want
9695 to test your Squeeze system, make sure
9696 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9697 based boot sequencing&lt;/a&gt; is enabled, and add this line to
9698 /etc/default/rcS:&lt;/p&gt;
9699
9700 &lt;blockquote&gt;&lt;pre&gt;
9701 CONCURRENCY=makefile
9702 &lt;/pre&gt;&lt;/blockquote&gt;
9703
9704 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
9705 scripts in parallel using the dependency information stored in
9706 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9707 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9708 to try to start the kdm and gdm scripts as early as possible, and will
9709 start the facilities required by kdm or gdm as early as possible to
9710 make this happen.&lt;/p&gt;
9711
9712 &lt;p&gt;Give it a try, and see if you like the result. If some services
9713 fail to start properly, it is most likely because they have incomplete
9714 init.d script dependencies in their startup script (or some of their
9715 dependent scripts have incomplete dependencies). Report bugs and get
9716 the package maintainers to fix it. :)&lt;/p&gt;
9717
9718 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
9719 manage to get the init.d script dependencies complete and correct. I
9720 expect we will get there in Squeeze+1, if we get manage to test and
9721 fix the remaining issues.&lt;/p&gt;
9722
9723 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9724 the BTS, please usertag the report to get it to show up at
9725 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9726 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9727 </description>
9728 </item>
9729
9730 <item>
9731 <title>Debian has switched to dependency based boot sequencing</title>
9732 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
9733 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
9734 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
9735 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
9736 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
9737 have been migrated to using dependency based boot sequencing. This
9738 conclude work me and others have been doing for the last three days.
9739 It feels great to see this finally part of the default Debian
9740 installation. Now we just need to weed out the last few problems that
9741 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
9742
9743 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
9744 fixing the more fundamental problem of handing the event based
9745 non-predictable kernel in the early boot.&lt;/p&gt;
9746 </description>
9747 </item>
9748
9749 <item>
9750 <title>Taking over sysvinit development</title>
9751 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
9752 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
9753 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
9754 <description>&lt;p&gt;After several years of frustration with the lack of activity from
9755 the existing sysvinit upstream developer, I decided a few weeks ago to
9756 take over the package and become the new upstream. The number of
9757 patches to track for the Debian package was becoming a burden, and the
9758 lack of synchronization between the distribution made it hard to keep
9759 the package up to date.&lt;/p&gt;
9760
9761 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9762 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
9763 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
9764 and Fedora), based on the patches currently in use in these
9765 distributions. We Debian maintainers plan to move to this tarball as
9766 the new upstream as soon as we find time to do the merge. Since the
9767 new tarball was created, we agreed with Werner at SuSe to make a new
9768 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
9769 development there. The project is registered and currently waiting
9770 for approval by the Savannah administrators, and as soon as it is
9771 approved, we will import the old versions from svn and continue
9772 working on the future release.&lt;/p&gt;
9773
9774 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
9775 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
9776 </description>
9777 </item>
9778
9779 <item>
9780 <title>Debian boots quicker and quicker</title>
9781 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
9782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
9783 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
9784 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
9785 people involved in the boot system on Debian and Ubuntu, to see if we
9786 could find more ways to speed up the boot system. This was an Ubuntu
9787 funded
9788 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
9789 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
9790 of boot systems, and ways to handle the increasing number of boot
9791 issues introduced by the Linux kernel becoming more and more
9792 asynchronous and event base. The Ubuntu approach using udev and
9793 upstart might be a good way forward. Time will show.&lt;/p&gt;
9794
9795 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
9796 process in Debian. All of these should be applied to get a quick
9797 boot:&lt;/p&gt;
9798
9799 &lt;ul&gt;
9800
9801 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
9802
9803 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
9804 clock is in UTC.&lt;/li&gt;
9805
9806 &lt;li&gt;Install and activate the insserv package to enable
9807 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9808 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
9809
9810 &lt;/ul&gt;
9811
9812 These points are based on the Google summer of code work done by
9813 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
9814 Villegas&lt;/a&gt;.
9815
9816 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
9817 unstable yesterday. When we tested it, we were able to cut 6 seconds
9818 from the boot sequence. It depend on very correct dependency
9819 declaration in all init.d scripts, so I expect us to find edge cases
9820 where the dependences in some scripts are slightly wrong when we start
9821 using this.&lt;/p&gt;
9822
9823 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9824 introduced by Raphael Geissert today, one that could affect the
9825 startup speed as well. Instead of starting some scripts concurrently
9826 from rcS.d/ and another set of scripts from rc2.d/, it would be
9827 possible to run a of them in the same process. A quick way to test
9828 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
9829 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
9830 </description>
9831 </item>
9832
9833 <item>
9834 <title>BSAs påstander om piratkopiering møter motstand</title>
9835 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
9836 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
9837 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
9838 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
9839 programvareselskapene som Microsoft og Apple, publisert en rapport der
9840 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9841 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9842 dager siden kom
9843 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
9844 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
9845 dagene. Et spesielt interessant kommentar fra Sverige,
9846 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
9847 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
9848
9849 &lt;blockquote&gt;
9850 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
9851 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9852 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
9853 exakta&quot;, säger BSAs Sverigechef John Hugosson.
9854 &lt;/blockquote&gt;
9855
9856 &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
9857 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
9858 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
9859 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
9860 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
9861
9862 &lt;p&gt;Fant lenkene via &lt;a
9863 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
9864 på Slashdot&lt;/a&gt;.&lt;/p&gt;
9865 </description>
9866 </item>
9867
9868 <item>
9869 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
9870 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
9871 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
9872 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
9873 <description>&lt;p&gt;Kom over
9874 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
9875 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9876 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9877 jobber til daglig. En rask opptelling forteller meg at vi har 490
9878 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
9879 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
9880 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
9881 </description>
9882 </item>
9883
9884 <item>
9885 <title>Kryptert harddisk - naturligvis</title>
9886 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
9887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
9888 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
9889 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
9890 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
9891 når en tar tap av arbeidstid, fortrolige dokumenter,
9892 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9893 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9894 til at jeg har kryptert harddisken på både kontormaskinen og min
9895 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9896 komme på avveie, den første informasjon relatert til jobben min ved
9897 Universitetet i Oslo, og den andre relatert til blant annet
9898 foreningsarbeide. Kryptering av diskene gjør at det er lite
9899 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9900 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9901 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9902 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9903 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9904 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9905 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9906 det er gjort slik jeg gjør det er minimale, og gevinstene er
9907 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9908 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
9909
9910 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9911 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9912 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9913 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9914 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9915 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9916 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9917 betydelige.&lt;/p&gt;
9918 </description>
9919 </item>
9920
9921 <item>
9922 <title>Two projects that have improved the quality of free software a lot</title>
9923 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
9924 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
9925 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
9926 <description>&lt;p&gt;There are two software projects that have had huge influence on the
9927 quality of free software, and I wanted to mention both in case someone
9928 do not yet know them.&lt;/p&gt;
9929
9930 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
9931 tool to detect and expose errors in the memory handling of programs.
9932 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
9933 and it will report any problems on stdout. It is even better if the
9934 program include debug information. With debug information, it is able
9935 to report the source file name and line number where the problem
9936 occurs. It can report things like &#39;reading past memory block in file
9937 X line N, the memory block was allocated in file Y, line M&#39;, and
9938 &#39;using uninitialised value in control logic&#39;. This tool has made it
9939 trivial to investigate reproducible crash bugs in programs, and have
9940 reduced the number of this kind of bugs in free software a lot.
9941
9942 &lt;p&gt;The second one is
9943 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
9944 a source code checker. It is able to process the source of a program
9945 and find problems in the logic without running the program. It
9946 started out as the Stanford Checker and became well known when it was
9947 used to find bugs in the Linux kernel. It is now a commercial tool
9948 and the company behind it is running
9949 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
9950 free software community, where a lot of free software projects get
9951 their source checked for free. Several thousand defects have been
9952 found and fixed so far. It can find errors like &#39;lock L taken in file
9953 X line N is never released if exiting in line M&#39;, or &#39;the code in file
9954 Y lines O to P can never be executed&#39;. The projects included in the
9955 community service project have managed to get rid of a lot of
9956 reliability problems thanks to Coverity.&lt;/p&gt;
9957
9958 &lt;p&gt;I believe tools like this, that are able to automatically find
9959 errors in the source, are vital to improve the quality of software and
9960 make sure we can get rid of the crashing and failing software we are
9961 surrounded by today.&lt;/p&gt;
9962 </description>
9963 </item>
9964
9965 <item>
9966 <title>No patch is not better than a useless patch</title>
9967 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
9968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
9969 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
9970 <description>&lt;p&gt;Julien Blache
9971 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
9972 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
9973 patch allow one to discuss a concrete and proposed solution, and also
9974 prove that the issue at hand is important enough for someone to spent
9975 time on fixing it. No patch do not provide any of these positive
9976 properties.&lt;/p&gt;
9977 </description>
9978 </item>
9979
9980 <item>
9981 <title>Standardize on protocols and formats, not vendors and applications</title>
9982 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
9983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
9984 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
9985 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
9986 very good one to form a long lived computer infrastructure. It is the
9987 simple one, lost by many in todays computer industry: Standardize on
9988 open network protocols and open exchange/storage formats, not applications.
9989 Applications come and go, while protocols and files tend to stay, and
9990 thus one want to make it easy to change application and vendor, while
9991 avoiding conversion costs and locking users to a specific platform or
9992 application.&lt;/p&gt;
9993
9994 &lt;p&gt;This approach make it possible to replace the client applications
9995 independently of the server applications. One can even allow users to
9996 use several different applications as long as they handle the selected
9997 protocol and format. In the normal case, only one client application
9998 is recommended and users only get help if they choose to use this
9999 application, but those that want to deviate from the easy path are not
10000 blocked from doing so.&lt;/p&gt;
10001
10002 &lt;p&gt;It also allow us to replace the server side without forcing the
10003 users to replace their applications, and thus allow us to select the
10004 best server implementation at any moment, when scale and resouce
10005 requirements change.&lt;/p&gt;
10006
10007 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
10008 open formats, but I would never recommend standardizing on a single
10009 application that do not use open network protocol or open formats.&lt;/p&gt;
10010 </description>
10011 </item>
10012
10013 <item>
10014 <title>Returning from Skolelinux developer gathering</title>
10015 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
10016 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
10017 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
10018 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
10019 Edu/Skolelinux development gathering. I got a bit done tuning the
10020 desktop, and looked into the dynamic service location protocol
10021 implementation avahi. It look like it could be useful for us. Almost
10022 30 people participated, and I believe it was a great environment to
10023 get to know the Skolelinux system. Walter Bender, involved in the
10024 development of the Sugar educational platform, presented his stuff and
10025 also helped me improve my OLPC installation. He also showed me that
10026 his Turtle Art application can be used in standalone mode, and we
10027 agreed that I would help getting it packaged for Debian. As a
10028 standalone application it would be great for Debian Edu. We also
10029 tried to get the video conferencing working with two OLPCs, but that
10030 proved to be too hard for us. The application seem to need more work
10031 before it is ready for me. I look forward to getting home and relax
10032 now. :)&lt;/p&gt;
10033 </description>
10034 </item>
10035
10036 <item>
10037 <title>Time for new LDAP schemas replacing RFC 2307?</title>
10038 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
10039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
10040 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
10041 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
10042 optimal. There is RFC 2307 documenting one way to store NIS maps in
10043 LDAP, and a modified version of this normally called RFC 2307bis, with
10044 some modifications to be compatible with Active Directory. The RFC
10045 specification handle the content of a lot of system databases, but do
10046 not handle DNS zones and DHCP configuration.&lt;/p&gt;
10047
10048 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
10049 we would like to store information about users, SMB clients/hosts,
10050 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10051 and LTSP configuration in LDAP. These objects have a lot in common,
10052 but with the current LDAP schemas it is not possible to have one
10053 object per entity. For example, one need to have at least three LDAP
10054 objects for a given computer, one with the SMB related stuff, one with
10055 DNS information and another with DHCP information. The schemas
10056 provided for DNS and DHCP are impossible to combine into one LDAP
10057 object. In addition, it is impossible to implement quick queries for
10058 netgroup membership, because of the way NIS triples are implemented.
10059 It just do not scale. I believe it is time for a few RFC
10060 specifications to cleam up this mess.&lt;/p&gt;
10061
10062 &lt;p&gt;I would like to have one LDAP object representing each computer in
10063 the network, and this object can then keep the SMB (ie host key), DHCP
10064 (mac address/name) and DNS (name/IP address) settings in one place.
10065 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
10066
10067 &lt;p&gt;I would also like to have a quick way to map from a user or
10068 computer and to the net group this user or computer is a member.&lt;/p&gt;
10069
10070 &lt;p&gt;Active Directory have done a better job than unix heads like myself
10071 in this regard, and the unix side need to catch up. Time to start a
10072 new IETF work group?&lt;/p&gt;
10073 </description>
10074 </item>
10075
10076 <item>
10077 <title>Endelig er Debian Lenny gitt ut</title>
10078 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
10079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
10080 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
10081 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
10082 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
10083 Et langt steg videre for Debian-prosjektet, og en rekke nye
10084 programpakker blir nå tilgjengelig for de av oss som bruker den
10085 stabile utgaven av Debian. Neste steg er nå å få
10086 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
10087 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10088 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10089 slippes løs på skolene. Takk til alle debian-utviklerne som har
10090 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10091 bootsekvens tilgjengelig i stabil utgave, vha pakken
10092 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10093 </description>
10094 </item>
10095
10096 <item>
10097 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10098 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10100 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10101 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10102 Oslo. Most of Saturday was used for the general assemly for the
10103 member organization, but the rest of the weekend I used to tune the
10104 LTSP installation. LTSP now work out of the box on the 10-network.
10105 Acer Aspire One proved to be a very nice thin client, with both
10106 screen, mouse and keybard in a small box. Was working on getting the
10107 diskless workstation setup configured out of the box, but did not
10108 finish it before the weekend was up.&lt;/p&gt;
10109
10110 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10111 the Brazilian group, so that will have to wait for the next
10112 development gathering. Would love to have the Debian Edu installer
10113 automatically detect and configure a multiseat setup when it find one
10114 of these cards.&lt;/p&gt;
10115 </description>
10116 </item>
10117
10118 <item>
10119 <title>The sorry state of multimedia browser plugins in Debian</title>
10120 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10122 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10123 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10124 plugins available in Debian Lenny, to see which one we should use by
10125 default in Debian Edu. We need an embedded video playing plugin with
10126 control buttons to pause or stop the video, and capable of streaming
10127 all the multimedia content available on the web. The test results and
10128 notes are available on
10129 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10130 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10131 fill this need. My personal video player favorite, VLC, has a really
10132 bad plugin which fail on a lot of the test pages. A lot of the MIME
10133 types I would expect to work with any free software player (like
10134 video/ogg), just do not work. And simple formats like the
10135 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10136 totem and vlc plugins. I hope the situation will improve soon. No
10137 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10138
10139 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10140 be the only one fitting our needs. :/&lt;/p&gt;
10141 </description>
10142 </item>
10143
10144 </channel>
10145 </rss>