]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
50adf0e980309b85db59e00a2cc9a0266e979c66
[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>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
11 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
13 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
14 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
15 web servers, and who own the network equipment it is flowing through?
16 It is possible to get a glimpse of this from using traceroute, but it
17 is hard to find all the details. Many years ago, I wrote a system to
18 map the Norwegian Internet (trying to figure out if our plans for a
19 network game service would get low enough latency, and who we needed
20 to talk to about setting up game servers close to the users. Back
21 then I used traceroute output from many locations (I asked my friends
22 to run a script and send me their traceroute output) to create the
23 graph and the map. The output from traceroute typically look like
24 this:
25
26 &lt;p&gt;&lt;pre&gt;
27 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
28 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
29 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
30 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
31 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
32 5 he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.627 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48) 3.172 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.857 ms
33 6 ae1.ar8.oslosda310.as2116.net (195.0.242.39) 0.662 ms 0.637 ms ae0.ar8.oslosda310.as2116.net (195.0.242.23) 0.622 ms
34 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
35 8 * * *
36 9 * * *
37 [...]
38 &lt;/pre&gt;&lt;/p&gt;
39
40 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
41 network equipment involved in getting the data traffic from me to the
42 www.stortinget.no server, and how long it took in milliseconds for a
43 package to reach the equipment and return to me. Three packages are
44 sent, and some times the packages do not follow the same path. This
45 is shown for hop 5, where three different IP addresses replied to the
46 traceroute request.&lt;/p&gt;
47
48 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
49 implementations I use are traceroute (using ICMP packages) mtr (can do
50 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
51 traceroute and a lot of other capabilities). All of them are easily
52 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
53
54 &lt;p&gt;This time around, I wanted to know the geographic location of
55 different route points, to visualize how visiting a web page spread
56 information about the visit to a lot of servers around the globe. The
57 background is that a web site today often will ask the browser to get
58 from many servers the parts (for example HTML, JSON, fonts,
59 JavaScript, CSS, video) required to display the content. This will
60 leak information about the visit to those controlling these servers
61 and anyone able to peek at the data traffic passing by (like your ISP,
62 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
63
64 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
65 www.stortinget.no. It is read daily by all members of parliament and
66 their staff, as well as political journalists, activits and many other
67 citizens of Norway. A visit to the www.stortinget.no web site will
68 ask your browser to contact 8 other servers: ajax.googleapis.com,
69 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
70 stats.g.doubleclick.net, www.google-analytics.com,
71 www.googletagmanager.com and www.netigate.se. I extracted this by
72 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
73 Stortinget web page and tell me all the URLs PhantomJS downloaded to
74 render the page (in HAR format using
75 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
76 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
77 to do this). My goal is to visualize network traces to all IP
78 addresses behind these DNS names, do show where visitors personal
79 information is spread when visiting the page.&lt;/p&gt;
80
81 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
82 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geoip-small.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using GeoIP&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
83
84 &lt;p&gt;When I had a look around for options, I could not find any good
85 free software tools to do this, and decided I needed my own traceroute
86 wrapper outputting KML based on locations looked up using GeoIP. KML
87 is easy to work with and easy to generate, and understood by several
88 of the GIS tools I have available. I got good help from by NUUG
89 colleague Anders Einar with this, and the result can be seen in
90 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
91 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
92 free GeoIP databases I could find (and the for-pay databases my
93 friends had access to) is not up to the task. The IP addresses of
94 central Internet infrastructure would typically be placed near the
95 controlling companies main office, and not where the router is really
96 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
97 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
98
99 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;&lt;img
100 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy-small.png&quot; alt=&quot;scapy traceroute graph for URLs used by www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
101
102 &lt;p&gt;I also had a look at the visual traceroute graph created by
103 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
104 showing IP network ownership (aka AS owner) for the IP address in
105 question.
106 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
107 graph display a lot of useful information about the traceroute in SVG
108 format&lt;/a&gt;, and give a good indication on who control the network
109 equipment involved, but it do not include geolocation. This graph
110 make it possible to see the information is made available at least for
111 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
112 3 Communications and NetDNA.&lt;/p&gt;
113
114 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;https://geotraceroute.com/index.php?node=4&amp;host=www.stortinget.no&quot;&gt;&lt;img
115 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png&quot; alt=&quot;example geotraceroute view for www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
116
117 &lt;p&gt;In the process, I came across the
118 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceRoute&lt;/a&gt; by
119 Salim Gasmi. Its methology of combining guesses based on DNS names,
120 various location databases and finally use latecy times to rule out
121 candidate locations seemed to do a very good job of guessing correct
122 geolocation. But it could only do one trace at the time, did not have
123 a sensor in Norway and did not make the geolocations easily available
124 for postprocessing. So I contacted the developer and asked if he
125 would be willing to share the code (he refused until he had time to
126 clean it up), but he was interested in providing the geolocations in a
127 machine readable format, and willing to set up a sensor in Norway. So
128 since yesterday, it is possible to run traces from Norway in this
129 service thanks to a sensor node set up by
130 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
131 trace in KML format for further processing.&lt;/p&gt;
132
133 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.kml&quot;&gt;&lt;img
134 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using geotraceroute&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
135
136 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
137 Denmark, Germany, Holland and Ireland. Plenty of places where the
138 Snowden confirmations verified the traffic is read by various actors
139 without your best interest as their top priority.&lt;/p&gt;
140
141 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
142 over all the hosts behind the urls imported by www.stortinget.no and
143 ask for the KML file from geotraceroute, and create a combined KML
144 file with all the traces (unfortunately only one of the IP addresses
145 behind the DNS name is traced this time. To get them all, one would
146 have to request traces using IP number instead of DNS names from
147 geotraceroute). That might be the next step in this project.&lt;/p&gt;
148
149 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
150 the IP traffic moves and who control the boxes involved in moving it.
151 And every time the link crosses for example the Swedish border, we can
152 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
153 Britain and NSA in USA and cables around the globe. (Hm, what should
154 we tell them? :) Keep that in mind if you ever send anything
155 unencrypted over the Internet.&lt;/p&gt;
156
157 &lt;p&gt;PS: KML files are drawn using
158 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
159 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
160 Marble. There are heaps of other options too.&lt;/p&gt;
161 </description>
162 </item>
163
164 <item>
165 <title>Appstream just learned how to map hardware to packages too!</title>
166 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
167 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
168 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
169 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
170 readers probably know, I have been working on the
171 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
172 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
173 it easier for users to figure out what to install to get a given piece
174 of hardware to work in Debian, and a key part of this system is a way
175 to map hardware to packages. Isenkram have its own mapping database,
176 and also uses data provided by each package using the AppStream
177 metadata format. And today,
178 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
179 Debian learned to look up hardware the same way Isenkram is doing it,
180 ie using fnmatch():&lt;/p&gt;
181
182 &lt;p&gt;&lt;pre&gt;
183 % appstreamcli what-provides modalias \
184 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
185 Identifier: pymissile [generic]
186 Name: pymissile
187 Summary: Control original Striker USB Missile Launcher
188 Package: pymissile
189 % appstreamcli what-provides modalias usb:v0694p0002d0000
190 Identifier: libnxt [generic]
191 Name: libnxt
192 Summary: utility library for talking to the LEGO Mindstorms NXT brick
193 Package: libnxt
194 ---
195 Identifier: t2n [generic]
196 Name: t2n
197 Summary: Simple command-line tool for Lego NXT
198 Package: t2n
199 ---
200 Identifier: python-nxt [generic]
201 Name: python-nxt
202 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
203 Package: python-nxt
204 ---
205 Identifier: nbc [generic]
206 Name: nbc
207 Summary: C compiler for LEGO Mindstorms NXT bricks
208 Package: nbc
209 %
210 &lt;/pre&gt;&lt;/p&gt;
211
212 &lt;p&gt;A similar query can be done using the combined AppStream and
213 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
214
215 &lt;p&gt;&lt;pre&gt;
216 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
217 pymissile
218 % isenkram-lookup usb:v0694p0002d0000
219 libnxt
220 nbc
221 python-nxt
222 t2n
223 %
224 &lt;/pre&gt;&lt;/p&gt;
225
226 &lt;p&gt;You can find modalias values relevant for your machine using
227 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
228
229 &lt;p&gt;If you want to make this system a success and help Debian users
230 make the most of the hardware they have, please
231 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
232 AppStream metadata for your package following the guidelines&lt;/a&gt;
233 documented in the wiki. So far only 11 packages provide such
234 information, among the several hundred hardware specific packages in
235 Debian. The Isenkram database on the other hand contain 101 packages,
236 mostly related to USB dongles. Most of the packages with hardware
237 mapping in AppStream are LEGO Mindstorms related, because I have, as
238 part of my involvement in
239 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
240 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
241 complete set of packages in Debian for that particular hardware. The
242 team also got a nice Christmas present today. The
243 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
244 package&lt;/a&gt; made it into Debian. With this package in place, it is
245 now possible to use the LEGO Mindstorms NXT unit with only free
246 software, as the nxt-firmware package contain the source and firmware
247 binaries for the NXT brick.&lt;/p&gt;
248
249 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
250 activities, please send Bitcoin donations to my address
251 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
252 </description>
253 </item>
254
255 <item>
256 <title>Isenkram updated with a lot more hardware-package mappings</title>
257 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
258 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
259 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
260 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
261 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
262 and install packages to get your hardware dongles to work, is still
263 going strong. It is a system to look up the hardware present on or
264 connected to the current system, and map the hardware to Debian
265 packages. It can either be done using the tools in isenkram-cli or
266 using the user space daemon in the isenkram package. The latter will
267 notify you, when inserting new hardware, about what packages to
268 install to get the dongle working. It will even provide a button to
269 click on to ask packagekit to install the packages.&lt;/p&gt;
270
271 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
272
273 &lt;p&gt;&lt;pre&gt;
274 % isenkram-lookup
275 bluez
276 cheese
277 ethtool
278 fprintd
279 fprintd-demo
280 gkrellm-thinkbat
281 hdapsd
282 libpam-fprintd
283 pidgin-blinklight
284 thinkfan
285 tlp
286 tp-smapi-dkms
287 tp-smapi-source
288 tpb
289 %
290 &lt;/pre&gt;&lt;/p&gt;
291
292 &lt;p&gt;It can also list the firware package providing firmware requested
293 by the load kernel modules, which in my case is an empty list because
294 I have all the firmware my machine need:
295
296 &lt;p&gt;&lt;pre&gt;
297 % /usr/sbin/isenkram-autoinstall-firmware -l
298 info: did not find any firmware files requested by loaded kernel modules. exiting
299 %
300 &lt;/pre&gt;&lt;/p&gt;
301
302 &lt;p&gt;The last few days I had a look at several of the around 250
303 packages in Debian with udev rules. These seem like good candidates
304 to install when a given hardware dongle is inserted, and I found
305 several that should be proposed by isenkram. I have not had time to
306 check all of them, but am happy to report that now there are 97
307 packages packages mapped to hardware by Isenkram. 11 of these
308 packages provide hardware mapping using AppStream, while the rest are
309 listed in the modaliases file provided in isenkram.&lt;/p&gt;
310
311 &lt;p&gt;These are the packages with hardware mappings at the moment. The
312 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
313 support using AppStream, for everyone to use:&lt;/p&gt;
314
315 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
316 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
317 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
318 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
319 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
320 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
321 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
322 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
323 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
324 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
325 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
326 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
327 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
328 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
329 pcscd, pidgin-blinklight, printer-driver-splix,
330 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
331 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
332 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
333 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
334 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
335 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
336 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
337 xserver-xorg-video-vmware, yubikey-personalization and
338 zd1211-firmware&lt;/p&gt;
339
340 &lt;p&gt;If you know of other packages, please let me know with a wishlist
341 bug report against the isenkram-cli package, and ask the package
342 maintainer to
343 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
344 metadata according to the guidelines&lt;/a&gt; to provide the information
345 for everyone. In time, I hope to get rid of the isenkram specific
346 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
347
348 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
349 much hardware, and suggest that the package with with any ethernet
350 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
351 the details. I hope the maintainer find time to address it soon. In
352 the mean time I provide an override in isenkram.&lt;/p&gt;
353 </description>
354 </item>
355
356 <item>
357 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
358 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
359 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
360 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
361 <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;
362
363 &lt;p&gt;In my early years, I played
364 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
365 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
366 space, and reached the &#39;elite&#39; fighting status before I moved on. The
367 original Elite game was available on Commodore 64 and the IBM PC
368 edition I played had a 64 KB executable. I am still impressed today
369 that the authors managed to squeeze both a 3D engine and details about
370 more than 2000 planet systems across 7 galaxies into a binary so
371 small.&lt;/p&gt;
372
373 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
374 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
375 really have time to test it properly until a few days ago. It was
376 great to discover that my old knowledge about trading routes were
377 still valid. But my fighting and flying abilities were gone, so I had
378 to retrain to be able to dock on a space station. And I am still not
379 able to make much resistance when I am attacked by pirates, so I
380 bougth and mounted the most powerful laser in the rear to be able to
381 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
382
383 &lt;p&gt;When playing Elite in the late eighties, I had to discover
384 everything on my own, and I had long lists of prices seen on different
385 planets to be able to decide where to trade what. This time I had the
386 advantages of the
387 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
388 where information about each planet is easily available with common
389 price ranges and suggested trading routes. This improved my ability
390 to earn money and I have been able to earn enough to buy a lot of
391 useful equipent in a few days. I believe I originally played for
392 months before I could get a docking computer, while now I could get it
393 after less then a week.&lt;/p&gt;
394
395 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
396 space, you should try out Oolite. It is available for Linux, MacOSX
397 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
398
399 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
400 activities, please send Bitcoin donations to my address
401 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
402 </description>
403 </item>
404
405 <item>
406 <title>Quicker Debian installations using eatmydata</title>
407 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
409 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
410 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
411 installation system, observing how using
412 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
413 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
414 speedup around 20-40 percent for Debian Edu, where we install around
415 1000 packages from within the installer. The eatmydata package
416 provide a way to disable/delay file system flushing. This is a bit
417 risky in the general case, as files that should be stored on disk will
418 stay only in memory a bit longer than expected, causing problems if a
419 machine crashes at an inconvenient time. But for an installation, if
420 the machine crashes during installation the process is normally
421 restarted, and avoiding disk operations as much as possible to speed
422 up the process make perfect sense.
423
424 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
425 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
426 but did not have time to push it any further. But a few months ago I
427 picked it up again and worked with the libeatmydata package maintainer
428 Mattia Rizzolo to make it easier for everyone to get this installation
429 speedup in Debian. Thanks to our cooperation There is now an
430 eatmydata-udeb package in Debian testing and unstable, and simply
431 enabling/installing it in debian-installer (d-i) is enough to get the
432 quicker installations. It can be enabled using preseeding. The
433 following untested kernel argument should do the trick:&lt;/p&gt;
434
435 &lt;blockquote&gt;&lt;pre&gt;
436 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
437 &lt;/pre&gt;&lt;/blockquote&gt;
438
439 &lt;p&gt;This should ask d-i to install the package inside the d-i
440 environment early in the installation sequence. Having it installed
441 in d-i in turn will make sure the relevant scripts are called just
442 after debootstrap filled /target/ with the freshly installed Debian
443 system to configure apt to run dpkg with eatmydata. This is enough to
444 speed up the installation process. There is a proposal to
445 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
446 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
447 tested its impact.&lt;/p&gt;
448
449 </description>
450 </item>
451
452 <item>
453 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
454 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
456 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
457 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
458 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
459 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
460 elever over det ganske land skal levere inn hvert år. Det mange ikke
461 vet er at selv om de kommersielle alternativene
462 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
463 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
464 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
465 utmerket fri programvarealternativ som kan. Oversetterverktøyet
466 Apertium har støtte for en rekke språkkombinasjoner, og takket være
467 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
468 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
469 nynorsk, og få den automatoversatt til det andre skriftspråket.
470 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
471 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
472 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
473 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
474 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
475 teksten din i webskjemaet der.
476
477 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
478 teknologien kan du enten installere pakken
479 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
480 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
481 api.apertium.org. Se
482 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
483 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
484 denne teksten som ble skrevet på bokmål over maskinoversatt til
485 nynorsk.&lt;/p&gt;
486
487 &lt;hr/&gt;
488
489 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
490 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
491 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
492 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
493 veit er at sjølv om dei kommersielle alternativa
494 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
495 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
496 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
497 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
498 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
499 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
500 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
501 nynorsk, og få den *automatoversatt til det andre skriftspråket.
502 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
503 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
504 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
505 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
506 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
507 teksta di i *webskjemaet der.
508
509 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
510 teknologien kan du anten installera pakken
511 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
512 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
513 *api.*apertium.org. Sjå
514 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
515 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
516 for denne teksta som vart skreva på bokmål over *maskinoversatt til
517 nynorsk.&lt;/p&gt;
518 </description>
519 </item>
520
521 <item>
522 <title>Coz profiler for multi-threaded software is now in Debian</title>
523 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
525 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
526 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
527 profiler able to run benchmarking experiments on the instrumented
528 multi-threaded program, finally
529 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
530 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
531 months since
532 &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
533 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
534 it suitable for Debian. There are still issues with clang
535 compatibility, inline assembly only working x86 and minimized
536 JavaScript libraries.&lt;/p&gt;
537
538 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
539
540 &lt;p&gt;&lt;blockquote&gt;
541 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
542 &lt;/blockquote&gt;&lt;/p&gt;
543
544 &lt;p&gt;This will produce a profile.coz file in the current working
545 directory with the profiling information. This is then given to a
546 JavaScript application provided in the package and available from
547 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
548 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
549
550 &lt;p&gt;&lt;blockquote&gt;
551 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
552 &lt;/blockquote&gt;&lt;/p&gt;
553
554 &lt;p&gt;See the project home page and the
555 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
556 ;login: article on Coz&lt;/a&gt; for more information on how it is
557 working.&lt;/p&gt;
558 </description>
559 </item>
560
561 <item>
562 <title>My own self balancing Lego Segway</title>
563 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
565 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
566 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
567 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
568 present. It had been on my wishlist for a while, because I wanted to
569 build a Segway like balancing lego robot. I had already built
570 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
571 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
572 NXT kit as the balance sensor, but it was not working very well. It
573 could balance for a while, but was very sensitive to the light
574 condition in the room and the reflective properties of the surface and
575 would fall over after a short while. I wanted something more robust,
576 and had
577 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
578 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
579 wishlist for some years before it suddenly showed up as a gift from my
580 loved ones. :)&lt;/p&gt;
581
582 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
583 since then. But that changed some days ago, when I was searching for
584 lego segway information and came across a recipe from HiTechnic for
585 building
586 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
587 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
588 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
589 code&lt;/a&gt; was included, so it was just a question of putting it all
590 together. And thanks to the great work of many Debian developers, the
591 compiler needed to build the source for the NXT is already included in
592 Debian, so I was read to go in less than an hour. The resulting robot
593 do not look very impressive in its simplicity:&lt;/p&gt;
594
595 &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;
596
597 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
598 design from HiTechnic, I had to comment out the last task
599 (taskControl). I simply placed /* and */ around it get the program
600 working without that sensor present. Now it balances just fine until
601 the battery status run low:&lt;/p&gt;
602
603 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
604 &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;
605 &lt;/video&gt;&lt;/p&gt;
606
607 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
608 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
609
610 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
611 they need to work with LEGO in Debian and all our derivative
612 distributions like Ubuntu, check out
613 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
614 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
615 RCX and NXT controller (no EV3), and would like to make sure the
616 Debian tools needed to program the systems I own work as they
617 should.&lt;/p&gt;
618 </description>
619 </item>
620
621 <item>
622 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
623 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
624 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
625 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
626 <description>&lt;p&gt;In July
627 &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
628 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
629 the ability to receive SMS messages (aka without a cell phone). It is
630 time to share some experiences and provide an updated setup.&lt;/p&gt;
631
632 &lt;p&gt;The Signal app have worked fine for several months now, and I use
633 it regularly to chat with my loved ones. I had a major snag at the
634 end of my summer vacation, when the the app completely forgot my
635 setup, identity and keys. The reason behind this major mess was
636 running out of disk space. To avoid that ever happening again I have
637 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
638 roll back to an earlier version if the files are wiped by mistake. I
639 had to use it once after introducing the git backup. When rolling
640 back to an earlier version, one need to use the &#39;reset session&#39; option
641 in Signal to get going, and notify the people you talk with about the
642 problem. I assume there is some sequence number tracking in the
643 protocol to detect rollback attacks. The git repository is rather big
644 (674 MiB so far), but I have not tried to figure out if some of the
645 content can be added to a .gitignore file due to lack of spare
646 time.&lt;/p&gt;
647
648 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
649 make it impossible to send messages using Signal. I could still
650 receive them, but had to patch the code with a new timestamp to send.
651 I believe the timeout is added by the developers to force people to
652 upgrade to the latest version of the app, even when there is no
653 protocol changes, to reduce the version skew among the user base and
654 thus try to keep the number of support requests down.&lt;/p&gt;
655
656 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
657 making the old patch fail to apply cleanly. Below is an updated
658 patch, including the shell wrapper I use to start Signal. The
659 original version required a new user to locate the JavaScript console
660 and call a function from there. I got help from a friend with more
661 JavaScript knowledge than me to modify the code to provide a GUI
662 button instead. This mean that to get started you just need to run
663 the wrapper and click the &#39;Register without mobile phone&#39; to get going
664 now. I&#39;ve also modified the timeout code to always set it to 90 days
665 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
666
667 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
668
669 &lt;ol&gt;
670
671 &lt;li&gt;First, install required packages to get the source code and the
672 browser you need. Signal only work with Chrome/Chromium, as far as I
673 know, so you need to install it.
674
675 &lt;pre&gt;
676 apt install git tor chromium
677 git clone https://github.com/WhisperSystems/Signal-Desktop.git
678 &lt;/pre&gt;&lt;/li&gt;
679
680 &lt;li&gt;Modify the source code using command listed in the the patch
681 block below.&lt;/li&gt;
682
683 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
684 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
685
686 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
687 number you can receive calls to the next minute, receive the
688 verification code and enter it into the form field and press
689 &#39;Register&#39;. Note, the phone number you use will be user Signal
690 username, ie the way others can find you on Signal.&lt;/li&gt;
691
692 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
693 not show up in the contact list until you restart Signal, and there is
694 no way to assign names to Contacts. There is also no way to create or
695 update chat groups. I suspect this is because the web app do not have
696 a associated contact database.&lt;/li&gt;
697
698 &lt;/ol&gt;
699
700 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
701 main author moxie0 reject federation and accept dependencies to major
702 corporations like Google (part of the code is fetched from Google) and
703 Amazon (the central coordination point is owned by Amazon). See for
704 example
705 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
706 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
707 view on these issues. But the network effect is strong in this case,
708 and several of the people I want to communicate with already use
709 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
710 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
711 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
712 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
713 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
714 working on Debian Stable.&lt;/p&gt;
715
716 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
717 working. It switch to the production servers, disable to timeout,
718 make registration easier and add the shell wrapper:&lt;/p&gt;
719
720 &lt;pre&gt;
721 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
722 diff --git a/js/background.js b/js/background.js
723 index 24b4c1d..579345f 100644
724 --- a/js/background.js
725 +++ b/js/background.js
726 @@ -33,9 +33,9 @@
727 });
728 });
729
730 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
731 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
732 var SERVER_PORTS = [80, 4433, 8443];
733 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
734 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
735 var messageReceiver;
736 window.getSocketStatus = function() {
737 if (messageReceiver) {
738 diff --git a/js/expire.js b/js/expire.js
739 index 639aeae..beb91c3 100644
740 --- a/js/expire.js
741 +++ b/js/expire.js
742 @@ -1,6 +1,6 @@
743 ;(function() {
744 &#39;use strict&#39;;
745 - var BUILD_EXPIRATION = 0;
746 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
747
748 window.extension = window.extension || {};
749
750 diff --git a/js/views/install_view.js b/js/views/install_view.js
751 index 7816f4f..1d6233b 100644
752 --- a/js/views/install_view.js
753 +++ b/js/views/install_view.js
754 @@ -38,7 +38,8 @@
755 return {
756 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
757 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
758 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
759 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
760 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
761 };
762 },
763 clearQR: function() {
764 diff --git a/options.html b/options.html
765 index dc0f28e..8d709f6 100644
766 --- a/options.html
767 +++ b/options.html
768 @@ -14,7 +14,10 @@
769 &amp;lt;div class=&#39;nav&#39;&gt;
770 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
771 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
772 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
773 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
774 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
775 +
776 + &amp;lt;/div&gt;
777 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
778 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
779 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
780 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
781 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
782 @@ -0,0 +1,12 @@
783 +#!/bin/sh
784 +set -e
785 +cd $(dirname $0)
786 +mkdir -p userdata
787 +userdata=&quot;`pwd`/userdata&quot;
788 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
789 + (cd $userdata &amp;&amp; git init)
790 +fi
791 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
792 +exec chromium \
793 + --proxy-server=&quot;socks://localhost:9050&quot; \
794 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
795 EOF
796 chmod a+rx run-signal-app
797 &lt;/pre&gt;
798
799 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
800 activities, please send Bitcoin donations to my address
801 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
802 </description>
803 </item>
804
805 <item>
806 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
807 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
809 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
810 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
811 system&lt;/a&gt; provide a practical and easy way to figure out which
812 packages support the hardware in a given machine. The command line
813 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
814 convenient way to list and install packages relevant for the current
815 hardware during system installation, both user space packages and
816 firmware packages. The GUI background daemon on the other hand provide
817 a pop-up proposing to install packages when a new dongle is inserted
818 while using the computer. For example, if you plug in a smart card
819 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
820 that package isn&#39;t already installed, and if you plug in a USB video
821 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
822 cheese is currently missing. This already work just fine.&lt;/p&gt;
823
824 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
825 package names. When I started no such database existed in Debian, so
826 I made my own data set and included it with the isenkram package and
827 made isenkram fetch the latest version of this database from git using
828 http. This way the isenkram users would get updated package proposals
829 as soon as I learned more about hardware related packages.&lt;/p&gt;
830
831 &lt;p&gt;The hardware is identified using modalias strings. The modalias
832 design is from the Linux kernel where most hardware descriptors are
833 made available as a strings that can be matched using filename style
834 globbing. It handle USB, PCI, DMI and a lot of other hardware related
835 identifiers.&lt;/p&gt;
836
837 &lt;p&gt;The downside to the Isenkram specific database is that there is no
838 information about relevant distribution / Debian version, making
839 isenkram propose obsolete packages too. But along came AppStream, a
840 cross distribution mechanism to store and collect metadata about
841 software packages. When I heard about the proposal, I contacted the
842 people involved and suggested to add a hardware matching rule using
843 modalias strings in the specification, to be able to use AppStream for
844 mapping hardware to packages. This idea was accepted and AppStream is
845 now a great way for a package to announce the hardware it support in a
846 distribution neutral way. I wrote
847 &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
848 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
849 December. If you have a hardware related package in Debian, please
850 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
851
852 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
853 RCX or NXT unit, announce this support using AppStream. The effect is
854 that when you insert such LEGO robot controller into your Debian
855 machine, Isenkram will propose to install the packages needed to get
856 it working. The intention is that this should allow the local user to
857 start programming his robot controller right away without having to
858 guess what packages to use or which permissions to fix.&lt;/p&gt;
859
860 &lt;p&gt;But when I sat down with my son the other day to program our NXT
861 unit using his Debian Stretch computer, I discovered something
862 annoying. The local console user (ie my son) did not get access to
863 the USB device for programming the unit. This used to work, but no
864 longer in Jessie and Stretch. After some investigation and asking
865 around on #debian-devel, I discovered that this was because udev had
866 changed the mechanism used to grant access to local devices. The
867 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
868 no longer applied, because LDAP users no longer was added to the
869 plugdev group during login. Michael Biebl told me that this method
870 was obsolete and the new method used ACLs instead. This was good
871 news, as the plugdev mechanism is a mess when using a remote user
872 directory like LDAP. Using ACLs would make sure a user lost device
873 access when she logged out, even if the user left behind a background
874 process which would retain the plugdev membership with the ConsoleKit
875 setup. Armed with this knowledge I moved on to fix the access problem
876 for the LEGO Mindstorms related packages.&lt;/p&gt;
877
878 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
879 applied directly for a device, or is applied in
880 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
881 LEGO Mindstorms udev rules did not have a class, I decided to add the
882 tag directly in the udev rules files included in the packages. Here
883 is one example. For the nqc C compiler for the RCX, the
884 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
885
886 &lt;p&gt;&lt;pre&gt;
887 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
888 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
889 &lt;/pre&gt;&lt;/p&gt;
890
891 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
892 packages using plugdev in their /lib/udev/rules.d/ files should be
893 changed to use this tag (either directly or indirectly via
894 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
895 to detect this?&lt;/p&gt;
896
897 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
898 It is unclear to me if the uaccess tag is an internal implementation
899 detail like the udev-acl tag used by
900 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
901 indirect method is the preferred way. Michael
902 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
903 documentation from the systemd project&lt;/a&gt; and I hope it will make
904 this clearer. For now I use the generic classes when they exist and
905 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
906 directly if no such class exist.&lt;/p&gt;
907
908 &lt;p&gt;To learn more about the isenkram system, please check out
909 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
910 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
911
912 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
913 please join us on our IRC channel
914 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
915 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
916 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
917 list is not yet created, but we are working on it. :)&lt;/p&gt;
918
919 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
920 activities, please send Bitcoin donations to my address
921 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
922 </description>
923 </item>
924
925 <item>
926 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
927 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
928 <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>
929 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
930 <description>&lt;p&gt;In April we
931 &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
932 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
933 how to set up and administrate a Debian system. Today I am happy to
934 report that the first draft is now publicly available. You can find
935 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
936 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
937 eight chapters have a first draft translation, and we are working on
938 proofreading the content. If you want to help out, please start
939 contributing using
940 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
941 hosted weblate project page&lt;/a&gt;, and get in touch using
942 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
943 translators mailing list&lt;/a&gt;. Please also check out
944 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
945 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
946 and update weblate if you find errors.&lt;/p&gt;
947
948 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
949 electronic form.&lt;/p&gt;
950 </description>
951 </item>
952
953 <item>
954 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
955 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
957 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
958 <description>&lt;p&gt;This summer, I read a great article
959 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
960 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
961 how to profile multi-threaded programs. It presented a system for
962 profiling software by running experiences in the running program,
963 testing how run time performance is affected by &quot;speeding up&quot; parts of
964 the code to various degrees compared to a normal run. It does this by
965 slowing down parallel threads while the &quot;faster up&quot; code is running
966 and measure how this affect processing time. The processing time is
967 measured using probes inserted into the code, either using progress
968 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
969 can also measure unmodified code by measuring complete the program
970 runtime and running the program several times instead.&lt;/p&gt;
971
972 &lt;p&gt;The project and presentation was so inspiring that I would like to
973 get the system into Debian. I
974 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
975 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
976 system ready for Debian by sending patches. The build process need to
977 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
978 to include the JavaScript web page used to visualize the collected
979 profiling information included in the source package.
980 But I expect that should work out fairly soon.&lt;/p&gt;
981
982 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
983 on a binary with debug symbols available, start the program like this:
984
985 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
986 coz run --- program-to-run
987 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
988
989 &lt;p&gt;This will create a text file profile.coz with the instrumentation
990 information. To show what part of the code affect the performance
991 most, use a web browser and either point it to
992 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
993 or use the copy from git (in the gh-pages branch). Check out this web
994 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
995 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
996 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
997 code, rebuild and run the profiler. This allow coz to do more
998 targeted experiments.&lt;/p&gt;
999
1000 &lt;p&gt;A video published by ACM
1001 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
1002 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
1003 from the 25th Symposium on Operating Systems Principles available
1004 titled
1005 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
1006 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
1007
1008 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
1009 for Coz is available from github. It will only build with clang
1010 because it uses a
1011 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
1012 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
1013 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
1014 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
1015
1016 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
1017 of software in Debian. I would very much like some help with the
1018 packaging effort, as I lack the in depth knowledge on how to package
1019 C++ libraries.&lt;/p&gt;
1020 </description>
1021 </item>
1022
1023 <item>
1024 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
1025 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
1026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
1027 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
1028 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1029 to be a slight challenge. Here is the recipe if I ever need to do it
1030 again. It all started by me wanting to try the recipe to set up
1031 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
1032 hardened Android installation&lt;/a&gt; from the Tor project blog on a
1033 device I had access to. It is a old mobile phone with a broken
1034 microphone The initial idea had been to just
1035 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
1036 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
1037 until a few days ago.&lt;/p&gt;
1038
1039 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
1040 loader (press volume down and power at the same time), (2) select
1041 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
1042 machine, (4) request the device identifier token by running &#39;fastboot
1043 oem get_identifier_token&#39;, (5) request the device unlocking key using
1044 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
1045 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
1046
1047 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
1048 or newer, and the device I was working on had 2.00.0027. This
1049 apparently can be easily fixed by downloading a Windows program and
1050 running it on your Windows machine, if you accept the terms Microsoft
1051 require you to accept to use Windows - which I do not. So I had to
1052 come up with a different approach. I got a lot of help from AndyCap
1053 on #nuug, and would not have been able to get this working without
1054 him.&lt;/p&gt;
1055
1056 &lt;p&gt;First I needed to extract the hboot firmware from
1057 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
1058 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
1059 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
1060 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
1061 recognise the file format, but unruu worked and extracted rom.zip,
1062 containing the new hboot firmware and a text file describing which
1063 devices it would work for.&lt;/p&gt;
1064
1065 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
1066 followed some instructions
1067 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
1068 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
1069 machine with Debian testing:&lt;/p&gt;
1070
1071 &lt;p&gt;&lt;pre&gt;
1072 adb reboot-bootloader
1073 fastboot oem rebootRUU
1074 fastboot flash zip rom.zip
1075 fastboot flash zip rom.zip
1076 fastboot reboot
1077 &lt;/pre&gt;&lt;/p&gt;
1078
1079 &lt;p&gt;The flash command apparently need to be done twice to take effect,
1080 as the first is just preparations and the second one do the flashing.
1081 The adb command is just to get to the boot loader menu, so turning the
1082 device on while holding volume down and the power button should work
1083 too.&lt;/p&gt;
1084
1085 &lt;p&gt;With the new hboot version in place I could start following the
1086 instructions on the HTC developer web site. I got the device token
1087 like this:&lt;/p&gt;
1088
1089 &lt;p&gt;&lt;pre&gt;
1090 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
1091 &lt;/pre&gt;
1092
1093 &lt;p&gt;And once I got the unlock code via email, I could use it like
1094 this:&lt;/p&gt;
1095
1096 &lt;p&gt;&lt;pre&gt;
1097 fastboot flash unlocktoken Unlock_code.bin
1098 &lt;/pre&gt;&lt;/p&gt;
1099
1100 &lt;p&gt;And with that final step in place, the phone was unlocked and I
1101 could start stuffing the software of my own choosing into the device.
1102 So far I only inserted a replacement recovery image to wipe the phone
1103 before I start. We will see what happen next. Perhaps I should
1104 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
1105 </description>
1106 </item>
1107
1108 <item>
1109 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
1110 <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>
1111 <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>
1112 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
1113 <description>&lt;p&gt;For a while now, I have wanted to test
1114 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
1115 said to provide end to end encrypted communication and several of my
1116 friends and family are already using it. As I by choice do not own a
1117 mobile phone, this proved to be harder than expected. And I wanted to
1118 have the source of the client and know that it was the code used on my
1119 machine. But yesterday I managed to get it working. I used the
1120 Github source, compared it to the source in
1121 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
1122 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
1123 patches to use the production Signal servers, started the app and
1124 asked for the hidden &quot;register without a smart phone&quot; form. Here is
1125 the recipe how I did it.&lt;/p&gt;
1126
1127 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
1128
1129 &lt;pre&gt;
1130 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1131 &lt;/pre&gt;
1132
1133 &lt;p&gt;Next, I patched the source to use the production servers, to be
1134 able to talk to other Signal users:&lt;/p&gt;
1135
1136 &lt;pre&gt;
1137 cat &amp;lt;&amp;lt;EOF | patch -p0
1138 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
1139 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
1140 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
1141 @@ -47,8 +47,8 @@
1142 });
1143 });
1144
1145 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1146 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1147 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
1148 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1149 var messageReceiver;
1150 window.getSocketStatus = function() {
1151 if (messageReceiver) {
1152 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
1153 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
1154 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
1155 @@ -1,6 +1,6 @@
1156 ;(function() {
1157 &#39;use strict&#39;;
1158 - var BUILD_EXPIRATION = 0;
1159 + var BUILD_EXPIRATION = 1474492690000;
1160
1161 window.extension = window.extension || {};
1162
1163 EOF
1164 &lt;/pre&gt;
1165
1166 &lt;p&gt;The first part is changing the servers, and the second is updating
1167 an expiration timestamp. This timestamp need to be updated regularly.
1168 It is set 90 days in the future by the build process (Gruntfile.js).
1169 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
1170
1171 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
1172 script to launch Signal in Chromium.&lt;/p&gt;
1173
1174 &lt;pre&gt;
1175 #!/bin/sh
1176 cd $(dirname $0)
1177 mkdir -p userdata
1178 exec chromium \
1179 --proxy-server=&quot;socks://localhost:9050&quot; \
1180 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1181 &lt;/pre&gt;
1182
1183 &lt;p&gt; The script start the app and configure Chromium to use the Tor
1184 SOCKS5 proxy to make sure those controlling the Signal servers (today
1185 Amazon and Whisper Systems) as well as those listening on the lines
1186 will have a harder time location my laptop based on the Signal
1187 connections if they use source IP address.&lt;/p&gt;
1188
1189 &lt;p&gt;When the script starts, one need to follow the instructions under
1190 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
1191 repository. I right clicked on the Signal window to get up the
1192 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
1193 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
1194 registration form. Then I entered by land line phone number and
1195 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
1196 repeated the verification code three times. After entering the number
1197 into the verification code field in the form, I could start using
1198 Signal from my laptop.
1199
1200 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
1201 whom and thus who know who to those controlling the central server,
1202 but such leakage is hard to avoid with a centrally controlled server
1203 setup. It is something to keep in mind when using Signal - the
1204 content of your chats are harder to intercept, but the meta data
1205 exposing your contact network is available to people you do not know.
1206 So better than many options, but not great. And sadly the usage is
1207 connected to my land line, thus allowing those controlling the server
1208 to associate it to my home and person. I would prefer it if only
1209 those I knew could tell who I was on Signal. There are options
1210 avoiding such information leakage, but most of my friends are not
1211 using them, so I am stuck with Signal for now.&lt;/p&gt;
1212 </description>
1213 </item>
1214
1215 <item>
1216 <title>The new &quot;best&quot; multimedia player in Debian?</title>
1217 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
1218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
1219 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
1220 <description>&lt;p&gt;When I set out a few weeks ago to figure out
1221 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
1222 multimedia player in Debian claimed to support most file formats /
1223 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
1224 the various players claimed support for. The range was from 55 to 130
1225 MIME types. I suspect most media formats are supported by all
1226 players, but this is not really reflected in the MimeTypes values in
1227 their desktop files. There are probably also some bogus MIME types
1228 listed, but it is hard to identify which one this is.&lt;/p&gt;
1229
1230 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
1231 the players suggesting to add more MIME types to their desktop files,
1232 and decided to spend some time myself improving the situation for my
1233 favorite media player VLC. The fixes for VLC entered Debian unstable
1234 yesterday. The complete list of MIME types can be seen on the
1235 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
1236 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
1237
1238 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
1239 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1240 kmplayer. I am sure some of the other players desktop files support
1241 several of the formats currently listed as working only with vlc,
1242 toten and parole.&lt;/p&gt;
1243
1244 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
1245 supported by all the tested multimedia players in Debian in their
1246 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1247 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1248 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1249 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1250 it sad that video/ogg and video/webm is not supported by all the media
1251 players in Debian. As far as I can tell, all of them can handle both
1252 formats.&lt;/p&gt;
1253 </description>
1254 </item>
1255
1256 <item>
1257 <title>A program should be able to open its own files on Linux</title>
1258 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1260 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1261 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1262 decided to test its presentation tool when making the slides for a
1263 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1264 wrote the first draft of the slides, saved the result and went to bed
1265 the day before I would give the talk. The next day I took a plane to
1266 the location where the meeting should take place, and on the plane I
1267 started up koffice again to polish the talk a bit, only to discover
1268 that kpresenter refused to load its own data file. I cursed a bit and
1269 started making the slides again from memory, to have something to
1270 present when I arrived. I tested that the saved files could be
1271 loaded, and the day seemed to be rescued. I continued to polish the
1272 slides until I suddenly discovered that the saved file could no longer
1273 be loaded into kpresenter. In the end I had to rewrite the slides
1274 three times, condensing the content until the talk became shorter and
1275 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1276 kpresenter wrote inline images in a way itself could not understand.
1277 Eventually that bug was fixed and kpresenter ended up being a great
1278 program to make slides. The point I&#39;m trying to make is that we
1279 expect a program to be able to load its own data files, and it is
1280 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1281
1282 &lt;p&gt;Did you ever experience a program failing to load its own data
1283 files from the desktop file browser? It is not a uncommon problem. A
1284 while back I discovered that the screencast recorder
1285 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1286 browser would refuse to open. No video player claimed to understand
1287 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1288 returning the application/ogg MIME type, which no video player I had
1289 installed listed as a MIME type they would understand. I asked for
1290 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1291 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1292 several video players to add video/ogg to their desktop files, to give
1293 the file browser an idea what to do about Ogg Theora files. After a
1294 while, the desktop file browsers in Debian started to handle the
1295 output from gtk-recordmydesktop properly.&lt;/p&gt;
1296
1297 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1298 system Rosegarden again, and I discovered that the KDE and xfce file
1299 browsers did not know what to do with the Rosegarden project files
1300 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1301 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1302 included in the next upload. To increase the chance of me remembering
1303 how to fix the problem next time some program fail to load its files
1304 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1305
1306 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1307 There are two sources for the MIME type of a given file. The output from
1308 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1309 shared MIME type registry (under /usr/share/mime/). The file MIME
1310 type is mapped to programs supporting the MIME type, and this
1311 information is collected from
1312 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1313 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1314 one desktop file claiming support for the MIME type of the file, it is
1315 activated when asking to open a given file. If there are more, one
1316 can normally select which one to use by right-clicking on the file and
1317 selecting the wanted one using &#39;Open with&#39; or similar. In general
1318 this work well. But it depend on each program picking a good MIME
1319 type (preferably
1320 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1321 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1322 registry recognizing the file and the desktop file to list the MIME
1323 type in its list of supported MIME types.&lt;/p&gt;
1324
1325 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1326 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1327 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1328
1329 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1330 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1331 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1332 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1333 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1334 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1335 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1336 &amp;lt;/mime-type&amp;gt;
1337 &amp;lt;/mime-info&amp;gt;
1338 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1339
1340 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1341 (it is a gzipped XML file). Note, it is much better to use an
1342 official MIME type registered with IANA than it is to make up ones own
1343 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1344
1345 &lt;p&gt;The desktop file of the rosegarden program failed to list
1346 audio/x-rosegarden in its list of supported MIME types, causing the
1347 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1348
1349 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1350 % grep Mime /usr/share/applications/rosegarden.desktop
1351 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1352 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1353 %
1354 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1355
1356 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
1357 MimeType= line.&lt;/p&gt;
1358
1359 &lt;p&gt;If you run into a file which fail to open the correct program when
1360 selected from the file browser, please check out the output from
1361 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
1362 MIME type is registered somewhere under /usr/share/mime/ and check
1363 that some desktop file under /usr/share/applications/ is claiming
1364 support for this MIME type. If not, please report a bug to have it
1365 fixed. :)&lt;/p&gt;
1366 </description>
1367 </item>
1368
1369 <item>
1370 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
1371 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
1372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
1373 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
1374 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
1375 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
1376 related packages. The idea is to have a database of mappings between
1377 hardware and packages, and pop up a dialog suggesting for the user to
1378 install the packages to use a given hardware dongle. Some use cases
1379 are when you insert a Yubikey, it proposes to install the software
1380 needed to control it; when you insert a braille reader list it
1381 proposes to install the packages needed to send text to the reader;
1382 and when you insert a ColorHug screen calibrator it suggests to
1383 install the driver for it. The system work well, and even have a few
1384 command line tools to install firmware packages and packages for the
1385 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
1386
1387 &lt;p&gt;The system was initially written using aptdaemon, because I found
1388 good documentation and example code on how to use it. But aptdaemon
1389 is going away and is generally being replaced by
1390 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
1391 so Isenkram needed a rewrite. And today, thanks to the great patch
1392 from my college Sunil Mohan Adapa in the FreedomBox project, the
1393 rewrite finally took place. I&#39;ve just uploaded a new version of
1394 Isenkram into Debian Unstable with the patch included, and the default
1395 for the background daemon is now to use PackageKit. To check it out,
1396 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
1397 and see if it is recognised.&lt;/p&gt;
1398
1399 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
1400 the machine it is running on, you can check out the isenkram-lookup
1401 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
1402
1403 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1404 % isenkram-lookup
1405 bluez
1406 cheese
1407 fprintd
1408 fprintd-demo
1409 gkrellm-thinkbat
1410 hdapsd
1411 libpam-fprintd
1412 pidgin-blinklight
1413 thinkfan
1414 tleds
1415 tp-smapi-dkms
1416 tp-smapi-source
1417 tpb
1418 %p
1419 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1420
1421 &lt;p&gt;The hardware mappings come from several places. The preferred way
1422 is for packages to announce their hardware support using
1423 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1424 cross distribution appstream system&lt;/a&gt;.
1425 See
1426 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
1427 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
1428 </description>
1429 </item>
1430
1431 <item>
1432 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
1433 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
1434 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
1435 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
1436 <description>&lt;p&gt;Yesterday I updated the
1437 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
1438 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
1439 enterprising users. There were some nice user and visible changes.
1440 First of all, both desktop menu entries now work. A design flaw in
1441 one of the script made the history graph fail to show up (its PNG was
1442 dumped in ~/.xsession-errors) if no controlling TTY was available.
1443 The script worked when called from the command line, but not when
1444 called from the desktop menu. I changed this to look for a DISPLAY
1445 variable or a TTY before deciding where to draw the graph, and now the
1446 graph window pop up as expected.&lt;/p&gt;
1447
1448 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
1449 graphs (the one showing the last few hours). New is also the user of
1450 colours showing charging in blue and discharge in red. The percentages
1451 of this graph is relative to last full charge, not battery design
1452 capacity.&lt;/p&gt;
1453
1454 &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;
1455
1456 &lt;p&gt;The other graph show the entire history of the collected battery
1457 statistics, comparing it to the design capacity of the battery to
1458 visualise how the battery life time get shorter over time. The red
1459 line in this graph is what the previous graph considers 100 percent:
1460
1461 &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;
1462
1463 &lt;p&gt;In this graph you can see that I only charge the battery to 80
1464 percent of last full capacity, and how the capacity of the battery is
1465 shrinking. :(&lt;/p&gt;
1466
1467 &lt;p&gt;The last new feature is in the collector, which now will handle
1468 more hardware models. On some hardware, Linux power supply
1469 information is stored in /sys/class/power_supply/ACAD/, while the
1470 collector previously only looked in /sys/class/power_supply/AC/. Now
1471 both are checked to figure if there is power connected to the
1472 machine.&lt;/p&gt;
1473
1474 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1475 check out the
1476 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1477 in Debian unstable, or rebuild it on Jessie to get it working on
1478 Debian stable. :) The upstream source is available from &lt;a
1479 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1480 Patches are very welcome.&lt;/p&gt;
1481
1482 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1483 activities, please send Bitcoin donations to my address
1484 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1485 </description>
1486 </item>
1487
1488 <item>
1489 <title>Debian now with ZFS on Linux included</title>
1490 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
1491 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
1492 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
1493 <description>&lt;p&gt;Today, after many years of hard work from many people,
1494 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
1495 Debian. The package status can be seen on
1496 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
1497 for zfs-linux&lt;/a&gt;. and
1498 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1499 team status page&lt;/a&gt;. If you want to help out, please join us.
1500 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
1501 source code&lt;/a&gt; is available via git on Alioth. It would also be
1502 great if you could help out with
1503 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
1504 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
1505 </description>
1506 </item>
1507
1508 <item>
1509 <title>What is the best multimedia player in Debian?</title>
1510 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
1511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
1512 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
1513 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
1514 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
1515
1516 &lt;p&gt;A few years ago, I had a look at the media support for Browser
1517 plugins in Debian, to get an idea which plugins to include in Debian
1518 Edu. I created a script to extract the set of supported MIME types
1519 for each plugin, and used this to find out which multimedia browser
1520 plugin supported most file formats / media types.
1521 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
1522 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
1523 not been updated for a while. But browser plugins are less relevant
1524 these days, so I thought it was time to look at standalone
1525 players.&lt;/p&gt;
1526
1527 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
1528 player when I wanted to play videos from the Norwegian National
1529 Broadcasting Company, and decided to investigate why. The cause is a
1530 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
1531 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
1532 of MIME types announced in the desktop file and the browser plugin,
1533 only to discover that there is quite a large difference between the
1534 two for VLC. This discovery made me dig up the script I used to
1535 compare browser plugins, and adjust it to compare desktop files
1536 instead, to try to figure out which multimedia player in Debian
1537 support most file formats.&lt;/p&gt;
1538
1539 &lt;p&gt;The result can be seen on the Debian Wiki, as
1540 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
1541 table listing all MIME types supported by one of the packages included
1542 in the table&lt;/a&gt;, with the package supporting most MIME types being
1543 listed first in the table.&lt;/p&gt;
1544
1545 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
1546 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1547 kmplayer. Time for the other players to update their announced MIME
1548 support?&lt;/p&gt;
1549 </description>
1550 </item>
1551
1552 <item>
1553 <title>The Pyra - handheld computer with Debian preinstalled</title>
1554 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1556 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1557 <description>A friend of mine made me aware of
1558 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1559 handheld computer which will be delivered with Debian preinstalled. I
1560 would love to get one of those for my birthday. :)&lt;/p&gt;
1561
1562 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1563 plugs and many others connectors, and include a full keyboard and a 5&quot;
1564 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1565 day of battery life time, but I have not seen any independent tests
1566 confirming this. The vendor is still collecting preorders, and the
1567 last I heard last night was that 22 more orders were needed before
1568 production started.&lt;/p&gt;
1569
1570 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1571 Debian. Please let me know if you know of any others. Is it the
1572 first computer being sold with Debian preinstalled?&lt;/p&gt;
1573 </description>
1574 </item>
1575
1576 <item>
1577 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1578 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1579 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1580 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1581 <description>&lt;p&gt;During this weekends
1582 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1583 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1584 to make sure there are good books about Debian available in Norwegian
1585 Bokmål, and got in touch with the people behind the
1586 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1587 project&lt;/a&gt; to get started. If you want to help out, please start
1588 contributing using
1589 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1590 hosted weblate project page&lt;/a&gt;, and get in touch using
1591 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1592 translators mailing list&lt;/a&gt;. Please also check out
1593 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1594 contributors&lt;/a&gt;.&lt;/p&gt;
1595
1596 &lt;p&gt;The book is already available on paper in English, French and
1597 Japanese, and our goal is to get it available on paper in Norwegian
1598 Bokmål too. In addition to the paper edition, there are also EPUB and
1599 Mobi versions available. And there are incomplete translations
1600 available for many more languages.&lt;/p&gt;
1601 </description>
1602 </item>
1603
1604 <item>
1605 <title>One in two hundred Debian users using ZFS on Linux?</title>
1606 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1607 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1608 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1609 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1610 packages in Debian, and was quite surprised with what I found. I use
1611 ZFS myself at home, but did not really expect many others to do so.
1612 But I might be wrong.&lt;/p&gt;
1613
1614 &lt;p&gt;According to
1615 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1616 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1617 0.53% of the population, with the package installed. As far as I know
1618 the only use of the spl-linux package is as a support library for ZFS
1619 on Linux, so I use it here as proxy for measuring the number of ZFS
1620 installation on Linux in Debian. In the kFreeBSD variant of Debian
1621 the ZFS feature is already available, and there
1622 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1623 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1624 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1625
1626 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1627 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1628 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1629 cleared, the package is still not in Debian. The package is again in
1630 the NEW queue. Several uploads have been rejected so far because the
1631 debian/copyright file was incomplete or wrong, but there is no reason
1632 to give up. The current status can be seen on
1633 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1634 team status page&lt;/a&gt;, and
1635 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1636 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1637
1638 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1639 my home server can function in the future using only official Debian
1640 packages, and the current blocker is to get the debian/copyright file
1641 accepted by the FTP masters in Debian, I decided a while back to try
1642 to help out the team. This was the background for my blog post about
1643 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1644 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1645 used the techniques I explored there to try to find any errors in the
1646 copyright file. It is not very easy to check every one of the around
1647 2000 files in the source package, but I hope we this time got it
1648 right. If you want to help out, check out the git source and try to
1649 find missing entries in the debian/copyright file.&lt;/p&gt;
1650 </description>
1651 </item>
1652
1653 <item>
1654 <title>Full battery stats collector is now available in Debian</title>
1655 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1656 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1657 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1658 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1659 extended collector that will collect the complete battery history for
1660 later processing and graphing. The original collector store the
1661 battery level as percentage of last full level, while the new
1662 collector also record battery vendor, model, serial number, design
1663 full level, last full level and current battery level. This make it
1664 possible to predict the lifetime of the battery as well as visualise
1665 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1666
1667 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1668 in the version 0.5.1 package in unstable. Get the new battery level graph
1669 and lifetime prediction by running:
1670
1671 &lt;p&gt;&lt;pre&gt;
1672 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1673 &lt;/pre&gt;&lt;/p&gt;
1674
1675 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1676
1677 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1678 entry yet):&lt;/p&gt;
1679
1680 &lt;p&gt;&lt;pre&gt;
1681 /usr/share/battery-stats/battery-stats-graph-flow
1682 &lt;/pre&gt;&lt;/p&gt;
1683
1684 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1685 when there are few data points. The graphs look a bit better with a
1686 few years of data.&lt;/p&gt;
1687
1688 &lt;p&gt;A while back one important feature I use in the battery stats
1689 collector broke in Debian. The scripts in
1690 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1691 suspect it happened when Jessie started using systemd, but I do not
1692 know. The issue is reported as
1693 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1694 pm-utils. I managed to work around it by adding an udev rule to call
1695 the collector script every time the power connector is connected and
1696 disconnected. With this fix in place it was finally time to make a
1697 new release of the package, and get it into Debian.&lt;/p&gt;
1698
1699 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1700 check out the
1701 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1702 in Debian unstable, or rebuild it on Jessie to get it working on
1703 Debian stable. :) The upstream source is available from
1704 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1705 As always, patches are very welcome.&lt;/p&gt;
1706 </description>
1707 </item>
1708
1709 <item>
1710 <title>Making battery measurements a little easier in Debian</title>
1711 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1712 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1713 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1714 <description>&lt;p&gt;Back in September, I blogged about
1715 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1716 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1717 how it showed the decay and death of this battery (now replaced). I
1718 created a simple deb package to handle the collection and graphing,
1719 but did not want to upload it to Debian as there were already
1720 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1721 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1722 a point of uploading a competing package when battery-stats could be
1723 fixed instead. I reported a few bugs about its non-function, and
1724 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1725
1726 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1727 hands. The end result is that I am now the new upstream developer of
1728 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
1729 battery-stats in Debian, and the package in Debian unstable is finally
1730 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1731 information provided by the Linux kernel. If you install the
1732 battery-stats package from unstable now, you will be able to get a
1733 graph of the current battery fill level, to get some idea about the
1734 status of the battery. The source package build and work just fine in
1735 Debian testing and stable (and probably oldstable too, but I have not
1736 tested). The default graph you get for that system look like this:&lt;/p&gt;
1737
1738 &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;
1739
1740 &lt;p&gt;My plans for the future is to merge my old scripts into the
1741 battery-stats package, as my old scripts collected a lot more details
1742 about the battery. The scripts are merged into the upstream
1743 battery-stats git repository already, but I am not convinced they work
1744 yet, as I changed a lot of paths along the way. Will have to test a
1745 bit more before I make a new release.&lt;/p&gt;
1746
1747 &lt;p&gt;I will also consider changing the file format slightly, as I
1748 suspect the way I combine several values into one field might make it
1749 impossible to know the type of the value when using it for processing
1750 and graphing.&lt;/p&gt;
1751
1752 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1753 battery, check out the battery-stats package in
1754 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1755 on
1756 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1757 I would love some help to improve the system further.&lt;/p&gt;
1758 </description>
1759 </item>
1760
1761 <item>
1762 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1763 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1764 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1765 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1766 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1767 details. And one of the details is the content of the
1768 debian/copyright file, which should list all relevant licenses used by
1769 the code in the package in question, preferably in
1770 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1771 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1772
1773 &lt;p&gt;For large packages with lots of contributors it is hard to write
1774 and update this file manually, and if you get some detail wrong, the
1775 package is normally rejected by the ftpmasters. So getting it right
1776 the first time around get the package into Debian faster, and save
1777 both you and the ftpmasters some work.. Today, while trying to figure
1778 out what was wrong with
1779 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1780 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
1781 figuring out the options for doing this job automatically, or at least
1782 semi-automatically.&lt;/p&gt;
1783
1784 &lt;p&gt;Lucikly, there are at least two tools available for generating the
1785 file based on the code in the source package,
1786 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
1787 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
1788 not sure which one of them came first, but both seem to be able to
1789 create a sensible draft file. As far as I can tell, none of them can
1790 be trusted to get the result just right, so the content need to be
1791 polished a bit before the file is OK to upload. I found the debmake
1792 option in
1793 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
1794 blog posts from 2014&lt;/a&gt;.
1795
1796 &lt;p&gt;To generate using debmake, use the -cc option:
1797
1798 &lt;p&gt;&lt;pre&gt;
1799 debmake -cc &gt; debian/copyright
1800 &lt;/pre&gt;&lt;/p&gt;
1801
1802 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
1803 this might not be the best option.&lt;/p&gt;
1804
1805 &lt;p&gt;The cme option is based on a config parsing library, and I found
1806 this approach in
1807 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
1808 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
1809 dpkg-copyright&#39; option:
1810
1811 &lt;p&gt;&lt;pre&gt;
1812 cme update dpkg-copyright
1813 &lt;/pre&gt;&lt;/p&gt;
1814
1815 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
1816 handle UTF-8 names better than debmake.&lt;/p&gt;
1817
1818 &lt;p&gt;When the copyright file is created, I would also like some help to
1819 check if the file is correct. For this I found two good options,
1820 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
1821 to focus on license types and file matching, and is able to detect
1822 ineffective blocks in the copyright file. The latter reports missing
1823 copyright holders and years, but was confused by inconsistent license
1824 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
1825 fix all issues reported by them before uploading. But I do not know
1826 if the tools and the ftpmasters agree on what is important to fix in a
1827 copyright file, so the package might still be rejected.&lt;/p&gt;
1828
1829 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
1830 will read through the source and try to find all copyright statements.
1831 It is not comparing the result to the content of debian/copyright, but
1832 can be useful when verifying the content of the copyright file.&lt;/p&gt;
1833
1834 &lt;p&gt;Are you aware of better tools in Debian to create and update
1835 debian/copyright file. Please let me know, or blog about it on
1836 planet.debian.org.&lt;/p&gt;
1837
1838 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1839 activities, please send Bitcoin donations to my address
1840 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1841
1842 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
1843 on how to use licensecheck and cdbs to create a draft copyright file
1844
1845 &lt;p&gt;&lt;pre&gt;
1846 licensecheck --copyright -r `find * -type f` | \
1847 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
1848 &lt;/pre&gt;&lt;/p&gt;
1849
1850 &lt;p&gt;He mentioned that he normally check the generated file into the
1851 version control system to make it easier to discover license and
1852 copyright changes in the upstream source. I will try to do the same
1853 with my packages in the future.&lt;/p&gt;
1854
1855 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
1856 against using -quiet for new users, so I removed it from the proposed
1857 command line.&lt;/p&gt;
1858 </description>
1859 </item>
1860
1861 <item>
1862 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
1863 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
1864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
1865 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
1866 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
1867 is taking shape in Debian, and one provided feature is a very
1868 convenient way to tell you which package to install to make a given
1869 firmware file available when the kernel is looking for it. This can
1870 be done using apt-file too, but that is for someone else to blog
1871 about. :)&lt;/p&gt;
1872
1873 &lt;p&gt;Here is a small recipe to find the package with a given firmware
1874 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
1875 picked from the set of firmware announced using appstream in Debian
1876 unstable. In general you would be looking for the firmware requested
1877 by the kernel during kernel module loading. To find the package
1878 providing the example file, do like this:&lt;/p&gt;
1879
1880 &lt;blockquote&gt;&lt;pre&gt;
1881 % apt install appstream
1882 [...]
1883 % apt update
1884 [...]
1885 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
1886 awk &#39;/Package:/ {print $2}&#39;
1887 firmware-qlogic
1888 %
1889 &lt;/pre&gt;&lt;/blockquote&gt;
1890
1891 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
1892 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
1893 a way appstream can use.&lt;/p&gt;
1894
1895 &lt;p&gt;This same approach can be used to find any package supporting a
1896 given MIME type. This is very useful when you get a file you do not
1897 know how to handle. First find the mime type using &lt;tt&gt;file
1898 --mime-type&lt;/tt&gt;, and next look up the package providing support for
1899 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1900 and you can find all packages handling this type like this:&lt;/p&gt;
1901
1902 &lt;blockquote&gt;&lt;pre&gt;
1903 % apt install appstream
1904 [...]
1905 % apt update
1906 [...]
1907 % appstreamcli what-provides mimetype image/svg+xml | \
1908 awk &#39;/Package:/ {print $2}&#39;
1909 bkchem
1910 phototonic
1911 inkscape
1912 shutter
1913 tetzle
1914 geeqie
1915 xia
1916 pinta
1917 gthumb
1918 karbon
1919 comix
1920 mirage
1921 viewnior
1922 postr
1923 ristretto
1924 kolourpaint4
1925 eog
1926 eom
1927 gimagereader
1928 midori
1929 %
1930 &lt;/pre&gt;&lt;/blockquote&gt;
1931
1932 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
1933 packages providing appstream metadata.&lt;/p&gt;
1934 </description>
1935 </item>
1936
1937 <item>
1938 <title>Creepy, visualise geotagged social media information - nice free software</title>
1939 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
1940 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
1941 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
1942 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
1943 with the computerised radio beacon known as a mobile phone their
1944 position is tracked by the phone company and often stored for a long
1945 time (like every time a SMS is received or sent). And if their
1946 computerised radio beacon is capable of running programs (often called
1947 mobile apps) downloaded from the Internet, these programs are often
1948 also capable of tracking their location (if the app requested access
1949 during installation). And when these programs send out information to
1950 central collection points, the location is often included, unless
1951 extra care is taken to not send the location. The provided
1952 information is used by several entities, for good and bad (what is
1953 good and bad, depend on your point of view). What is certain, is that
1954 the private sphere and the right to free movement is challenged and
1955 perhaps even eradicated for those announcing their location this way,
1956 when they share their whereabouts with private and public
1957 entities.&lt;/p&gt;
1958
1959 &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;
1960
1961 &lt;p&gt;The phone company logs provide a register of locations to check out
1962 when one want to figure out what the tracked person was doing. It is
1963 unavailable for most of us, but provided to selected government
1964 officials, company staff, those illegally buying information from
1965 unfaithful servants and crackers stealing the information. But the
1966 public information can be collected and analysed, and a free software
1967 tool to do so is called
1968 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
1969 discovered it when I read
1970 &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
1971 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
1972 November 2014, and decided to check if it was available in Debian.
1973 The python program was in Debian, but
1974 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
1975 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
1976 uploaded a new version which did not work quite right, but did not
1977 have time to fix it then. This Christmas I decided to finally try to
1978 get Creepy operational in Debian. Now a fixed version is available in
1979 Debian unstable and testing, and almost all Debian specific patches
1980 are now included
1981 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
1982
1983 &lt;p&gt;The Creepy program visualises geolocation information fetched from
1984 Twitter, Instagram, Flickr and Google+, and allow one to get a
1985 complete picture of every social media message posted recently in a
1986 given area, or track the movement of a given individual across all
1987 these services. Earlier it was possible to use the search API of at
1988 least some of these services without identifying oneself, but these
1989 days it is impossible. This mean that to use Creepy, you need to
1990 configure it to log in as yourself on these services, and provide
1991 information to them about your search interests. This should be taken
1992 into account when using Creepy, as it will also share information
1993 about yourself with the services.&lt;/p&gt;
1994
1995 &lt;p&gt;The picture above show the twitter messages sent from (or at least
1996 geotagged with a position from) the city centre of Oslo, the capital
1997 of Norway. One useful way to use Creepy is to first look at
1998 information tagged with an area of interest, and next look at all the
1999 information provided by one or more individuals who was in the area.
2000 I tested it by checking out which celebrity provide their location in
2001 twitter messages by checkout out who sent twitter messages near a
2002 Norwegian TV station, and next could track their position over time,
2003 making it possible to locate their home and work place, among other
2004 things. A similar technique have been
2005 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
2006 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
2007 tool to discover lying governments, and a useful tool to help people
2008 understand the value of the private information they provide to the
2009 public.&lt;/p&gt;
2010
2011 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
2012 it depend on several python modules currently missing in Jessie (at
2013 least python-instagram, python-flickrapi and
2014 python-requests-toolbelt).&lt;/p&gt;
2015
2016 &lt;p&gt;(I have uploaded
2017 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
2018 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
2019 Creepy program in Debian.)&lt;/p&gt;
2020 </description>
2021 </item>
2022
2023 <item>
2024 <title>Always download Debian packages using Tor - the simple recipe</title>
2025 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
2026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
2027 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
2028 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
2029 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
2030 that those listening on the Internet lines would have good reason to
2031 believe a computer have a given security hole&lt;/a&gt; if it download a
2032 security fix from a Debian mirror. This is a good reason to always
2033 use encrypted connections to the Debian mirror, to make sure those
2034 listening do not know which IP address to attack. In August, Richard
2035 Hartmann observed that encryption was not enough, when it was possible
2036 to interfere download size to security patches or the fact that
2037 download took place shortly after a security fix was released, and
2038 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
2039 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
2040 was not the first to propose this, as the
2041 &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;
2042 package by Tim Retout already existed to make it easy to convince apt
2043 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
2044 aware of that package when I read the blog post from Richard.&lt;/p&gt;
2045
2046 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
2047 sysadmins, and he set up a Tor hidden service on one of the central
2048 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2049 it possible to download packages directly between two tor nodes,
2050 making sure the network traffic always were encrypted.&lt;/p&gt;
2051
2052 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
2053 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
2054 urls with tor+http and tor+https, and using the hidden service instead
2055 of the official Debian mirror site. I recommend installing
2056 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
2057 done in /etc/.&lt;/p&gt;
2058
2059 &lt;blockquote&gt;&lt;pre&gt;
2060 apt install apt-transport-tor
2061 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
2062 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
2063 &lt;/pre&gt;&lt;/blockquote&gt;
2064
2065 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
2066 the sed commands for these too. The sed command is assuming your are
2067 using the ftp.debian.org Debian mirror. Adjust the command (or just
2068 edit the file manually) to match your mirror.&lt;/p&gt;
2069
2070 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
2071 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
2072 system, and do not work with these tor+http URLs. For
2073 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
2074 which need a recent apt version currently only in unstable. So if you
2075 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
2076
2077 &lt;p&gt;Another advantage from this change is that your machine will start
2078 using Tor regularly and at fairly random intervals (every time you
2079 update the package lists or upgrade or install a new package), thus
2080 masking other Tor traffic done from the same machine. Using Tor will
2081 become normal for the machine in question.&lt;/p&gt;
2082
2083 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
2084 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
2085 enabled. It would be great if it was the default on any Debian
2086 system.&lt;/p&gt;
2087 </description>
2088 </item>
2089
2090 <item>
2091 <title>OpenALPR, find car license plates in video streams - nice free software</title>
2092 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
2093 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
2094 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
2095 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
2096 call the car license plate numbers in those days. I would write the
2097 numbers down in my little book and compare notes with the other kids
2098 to see how many region codes we had seen and if we had seen some
2099 exotic or special region codes and numbers. It was a fun game to pass
2100 time, as we kids have plenty of it.&lt;/p&gt;
2101
2102 &lt;p&gt;A few days I came across
2103 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
2104 project&lt;/a&gt;, a free software project to automatically discover and
2105 report license plates in images and video streams, and provide the
2106 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
2107 such system for a while now, because I believe it is a bad idea that the
2108 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
2109 number plate recognition&lt;/a&gt; tool only is available in the hands of
2110 the powerful, and want it to be available also for the powerless to
2111 even the score when it comes to surveillance and sousveillance. I
2112 discovered the developer
2113 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
2114 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
2115 help him get it into shape to get the package uploaded into the Debian
2116 archive.&lt;/p&gt;
2117
2118 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
2119 it into Debian, where it currently
2120 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
2121 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
2122
2123 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
2124 for the common folks, ie those not running a large government
2125 surveillance system? Well, I plan to put it in a computer on my bike
2126 and in my car, tracking the cars nearby and allowing me to be notified
2127 when number plates on my watch list are discovered. Another use case
2128 was suggested by a friend of mine, who wanted to set it up at his home
2129 to open the car port automatically when it discovered the plate on his
2130 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2131 capable of placing his license plate number of a piece of cardboard to
2132 open his car port, men replied that it was always unlocked anyway. I
2133 guess for such use case it make sense. I am sure there are other use
2134 cases too, for those with imagination and a vision.&lt;/p&gt;
2135
2136 &lt;p&gt;If you want to build your own version of the Debian package, check
2137 out the upstream git source and symlink ./distros/debian to ./debian/
2138 before running &quot;debuild&quot; to build the source. Or wait a bit until the
2139 package show up in unstable.&lt;/p&gt;
2140 </description>
2141 </item>
2142
2143 <item>
2144 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
2145 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
2146 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
2147 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
2148 <description>&lt;p&gt;Around three years ago, I created
2149 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
2150 system&lt;/a&gt; to get a more practical solution in Debian for handing
2151 hardware related packages. A GUI system in the isenkram package will
2152 present a pop-up dialog when some hardware dongle supported by
2153 relevant packages in Debian is inserted into the machine. The same
2154 lookup mechanism to detect packages is available as command line
2155 tools in the isenkram-cli package. In addition to mapping hardware,
2156 it will also map kernel firmware files to packages and make it easy to
2157 install needed firmware packages automatically. The key for this
2158 system to work is a good way to map hardware to packages, in other
2159 words, allow packages to announce what hardware they will work
2160 with.&lt;/p&gt;
2161
2162 &lt;p&gt;I started by providing data files in the isenkram source, and
2163 adding code to download the latest version of these data files at run
2164 time, to ensure every user had the most up to date mapping available.
2165 I also added support for storing the mapping in the Packages file in
2166 the apt repositories, but did not push this approach because while I
2167 was trying to figure out how to best store hardware/package mappings,
2168 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2169 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
2170 add the hardware mapping into that data set to be able to use
2171 appstream as a data source, and this was accepted at least for the
2172 Debian version of appstream.&lt;/p&gt;
2173
2174 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
2175 and today I uploaded a new version 0.20 of isenkram adding support for
2176 appstream as a data source for mapping hardware to packages. The only
2177 package so far using appstream to announce its hardware support is my
2178 pymissile package. I got help from Matthias Klumpp with figuring out
2179 how do add the required
2180 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
2181 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
2182 this content:&lt;/p&gt;
2183
2184 &lt;blockquote&gt;&lt;pre&gt;
2185 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2186 &amp;lt;component&amp;gt;
2187 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
2188 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
2189 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
2190 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
2191 &amp;lt;description&amp;gt;
2192 &amp;lt;p&amp;gt;
2193 Pymissile provides a curses interface to control an original
2194 Marks and Spencer / Striker USB Missile Launcher, as well as a
2195 motion control script to allow a webcamera to control the
2196 launcher.
2197 &amp;lt;/p&amp;gt;
2198 &amp;lt;/description&amp;gt;
2199 &amp;lt;provides&amp;gt;
2200 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
2201 &amp;lt;/provides&amp;gt;
2202 &amp;lt;/component&amp;gt;
2203 &lt;/pre&gt;&lt;/blockquote&gt;
2204
2205 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
2206 which is a glob style match rule for hardware specific strings
2207 (modalias strings) provided by the Linux kernel. In this case, it
2208 will map to all USB devices with vendor code 1130 and product code
2209 0202.&lt;/p&gt;
2210
2211 &lt;p&gt;Note, it is important that the license of all the metadata files
2212 are compatible to have permissions to aggregate them into archive wide
2213 appstream files. Matthias suggested to use MIT or BSD licenses for
2214 these files. A challenge is figuring out a good id for the data, as
2215 it is supposed to be globally unique and shared across distributions
2216 (in other words, best to coordinate with upstream what to use). But
2217 it can be changed later or, so we went with the package name as
2218 upstream for this project is dormant.&lt;/p&gt;
2219
2220 &lt;p&gt;To get the metadata file installed in the correct location for the
2221 mirror update scripts to pick it up and include its content the
2222 appstream data source, the file must be installed in the binary
2223 package under /usr/share/appdata/. I did this by adding the following
2224 line to debian/pymissile.install:&lt;/p&gt;
2225
2226 &lt;blockquote&gt;&lt;pre&gt;
2227 debian/pymissile.metainfo.xml usr/share/appdata
2228 &lt;/pre&gt;&lt;/blockquote&gt;
2229
2230 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
2231 all packages useful on the current computer automatically, and the GUI
2232 pop-up handler will propose to install the package not already
2233 installed if a hardware dongle is inserted into the machine in
2234 question.&lt;/p&gt;
2235
2236 &lt;p&gt;Details of the modalias field in appstream is available from the
2237 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
2238
2239 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
2240 try running this command on the command line:&lt;/p&gt;
2241
2242 &lt;blockquote&gt;&lt;pre&gt;
2243 cat $(find /sys/devices/|grep modalias)
2244 &lt;/pre&gt;&lt;/blockquote&gt;
2245
2246 &lt;p&gt;To learn more about the isenkram system, please check out
2247 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2248 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2249 </description>
2250 </item>
2251
2252 <item>
2253 <title>The GNU General Public License is not magic pixie dust</title>
2254 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2255 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2256 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2257 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2258 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2259 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2260 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2261 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2262
2263 &lt;blockquote&gt;
2264
2265 &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;
2266
2267 &lt;blockquote&gt;
2268 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2269
2270 The first step is to choose a
2271 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2272 code.&lt;br/&gt;
2273
2274 The next step is, when someone fails to follow that copyleft license,
2275 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2276
2277 and its a simple fact of our modern society that such type of
2278 work&lt;br/&gt;
2279
2280 is incredibly expensive to do and incredibly difficult to do.
2281 &lt;/blockquote&gt;
2282
2283 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2284 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2285 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2286 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2287
2288 &lt;p&gt;As the Debian Website
2289 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2290 &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;
2291 imply, public domain and permissively licensed software can lead to
2292 the production of more proprietary software as people discover useful
2293 software, extend it and or incorporate it into their hardware or
2294 software products. Copyleft licenses such as the GNU GPL were created
2295 to close off this avenue to the production of proprietary software but
2296 such licenses are not enough. With the ongoing adoption of Free
2297 Software by individuals and groups, inevitably the community&#39;s
2298 expectations of license compliance are violated, usually out of
2299 ignorance of the way Free Software works, but not always. As Karen
2300 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2301 Freedom&quot;&gt;FaiF&lt;/a&gt;
2302 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2303 copyleft is nothing if no-one is willing and able to stand up in court
2304 to protect it. The reality of today&#39;s world is that legal
2305 representation is expensive, difficult and time consuming. With
2306 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2307 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2308 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2309 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2310 of the Linux project, Debian and other groups against GPL violations.
2311 In March the SFC supported a
2312 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2313 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2314 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2315 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2316 kernel. Since then two of their sponsors pulled corporate funding and
2317 conferences
2318 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2319 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2320 less on corporate funding and more on the broad community of
2321 individuals who support Free Software and copyleft. So the SFC has
2322 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2323 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2324 a community of folks who stand up for copyleft and the GPL by
2325 supporting their work on promoting and supporting copyleft and Free
2326 Software.&lt;/p&gt;
2327
2328 &lt;p&gt;If you support Free Software,
2329 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2330 what the SFC do, agree with their
2331 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2332 principles&lt;/a&gt;, are happy about their
2333 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2334 work on a project that is an SFC
2335 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2336 just want to stand up for copyleft, please join
2337 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2338 Allan Webber&lt;/a&gt;,
2339 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2340 Smith&lt;/a&gt;,
2341 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2342 Bacon&lt;/a&gt;, myself and
2343 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2344 becoming a
2345 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2346 next week your donation will be
2347 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2348 by an anonymous donor. Please also consider asking your employer to
2349 match your donation or become a sponsor of SFC. Don&#39;t forget to
2350 spread the word about your support for SFC via email, your blog and or
2351 social media accounts.&lt;/p&gt;
2352
2353 &lt;/blockquote&gt;
2354
2355 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
2356 of Software Freedom Conservancy myself. Perhaps you should be a
2357 supporter too?&lt;/p&gt;
2358 </description>
2359 </item>
2360
2361 <item>
2362 <title>PGP key transition statement for key EE4E02F9</title>
2363 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
2364 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
2365 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
2366 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
2367 set it up properly. I wanted to generate it offline and have it
2368 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
2369 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
2370 time to sit down with an offline machine almost took forever. But
2371 finally I&#39;ve been able to complete the process, and have now moved
2372 from my old GPG key to a new GPG key. See
2373 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
2374 full transition statement, signed with both my old and new key&lt;/a&gt; for
2375 the details. This is my new key:&lt;/p&gt;
2376
2377 &lt;pre&gt;
2378 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]
2379 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
2380 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
2381 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
2382 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
2383 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
2384 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
2385 &lt;/pre&gt;
2386
2387 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
2388 my old key.&lt;/p&gt;
2389
2390 &lt;p&gt;If you signed my old key
2391 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
2392 I&#39;d very much appreciate a signature on my new key, details and
2393 instructions in the transition statement. I m happy to reciprocate if
2394 you have a similarly signed transition statement to present.&lt;/p&gt;
2395 </description>
2396 </item>
2397
2398 <item>
2399 <title>The life and death of a laptop battery</title>
2400 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
2401 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
2402 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
2403 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
2404 But this do not last. The last few laptops gave me a feeling that
2405 within a year, the life time is just a fraction of what it used to be,
2406 and it slowly become painful to use the laptop without power connected
2407 all the time. Because of this, when I got a new Thinkpad X230 laptop
2408 about two years ago, I decided to monitor its battery state to have
2409 more hard facts when the battery started to fail.&lt;/p&gt;
2410
2411 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
2412
2413 &lt;p&gt;First I tried to find a sensible Debian package to record the
2414 battery status, assuming that this must be a problem already handled
2415 by someone else. I found
2416 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
2417 which collects statistics from the battery, but it was completely
2418 broken. I sent a few suggestions to the maintainer, but decided to
2419 write my own collector as a shell script while I waited for feedback
2420 from him. Via
2421 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
2422 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
2423 discovered
2424 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
2425 available in Debian.&lt;/p&gt;
2426
2427 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
2428 battery stats ever since. Now my
2429 /var/log/hjemmenett-battery-status.log file contain around 115,000
2430 measurements, from the time the battery was working great until now,
2431 when it is unable to charge above 7% of original capacity. My
2432 collector shell script is quite simple and look like this:&lt;/p&gt;
2433
2434 &lt;pre&gt;
2435 #!/bin/sh
2436 # Inspired by
2437 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
2438 # See also
2439 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
2440 logfile=/var/log/hjemmenett-battery-status.log
2441
2442 files=&quot;manufacturer model_name technology serial_number \
2443 energy_full energy_full_design energy_now cycle_count status&quot;
2444
2445 if [ ! -e &quot;$logfile&quot; ] ; then
2446 (
2447 printf &quot;timestamp,&quot;
2448 for f in $files; do
2449 printf &quot;%s,&quot; $f
2450 done
2451 echo
2452 ) &gt; &quot;$logfile&quot;
2453 fi
2454
2455 log_battery() {
2456 # Print complete message in one echo call, to avoid race condition
2457 # when several log processes run in parallel.
2458 msg=$(printf &quot;%s,&quot; $(date +%s); \
2459 for f in $files; do \
2460 printf &quot;%s,&quot; $(cat $f); \
2461 done)
2462 echo &quot;$msg&quot;
2463 }
2464
2465 cd /sys/class/power_supply
2466
2467 for bat in BAT*; do
2468 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
2469 done
2470 &lt;/pre&gt;
2471
2472 &lt;p&gt;The script is called when the power management system detect a
2473 change in the power status (power plug in or out), and when going into
2474 and out of hibernation and suspend. In addition, it collect a value
2475 every 10 minutes. This make it possible for me know when the battery
2476 is discharging, charging and how the maximum charge change over time.
2477 The code for the Debian package
2478 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
2479 available on github&lt;/a&gt;.&lt;/p&gt;
2480
2481 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
2482
2483 &lt;pre&gt;
2484 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2485 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
2486 [...]
2487 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2488 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2489 &lt;/pre&gt;
2490
2491 &lt;p&gt;I wrote a small script to create a graph of the charge development
2492 over time. This graph depicted above show the slow death of my laptop
2493 battery.&lt;/p&gt;
2494
2495 &lt;p&gt;But why is this happening? Why are my laptop batteries always
2496 dying in a year or two, while the batteries of space probes and
2497 satellites keep working year after year. If we are to believe
2498 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
2499 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
2500 chance, and the fix is to not charge the Lithium-ion batteries to 100%
2501 all the time, but to stay below 90% of full charge most of the time.
2502 I&#39;ve been told that the Tesla electric cars
2503 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
2504 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
2505 100% when preparing for a longer trip (not that I would want a car
2506 like Tesla where rights to privacy is abandoned, but that is another
2507 story), which I guess is the option we should have for laptops on
2508 Linux too.&lt;/p&gt;
2509
2510 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
2511 stop charging at 80%, unless requested to charge to 100% once in
2512 preparation for a longer trip? I found
2513 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
2514 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2515 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
2516 load).&lt;/p&gt;
2517
2518 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
2519 at the start. I also wonder why the &quot;full capacity&quot; increases some
2520 times, and if it is possible to repeat the process to get the battery
2521 back to design capacity. And I wonder if the discharge and charge
2522 speed change over time, or if this stay the same. I did not yet try
2523 to write a tool to calculate the derivative values of the battery
2524 level, but suspect some interesting insights might be learned from
2525 those.&lt;/p&gt;
2526
2527 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
2528 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2529 packages instead of the tp-smapi-dkms package I had tried to use
2530 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
2531 and stop. I&#39;ve done so now, but expect my existing battery is toast
2532 and need to be replaced. The proposal is unfortunately Thinkpad
2533 specific.&lt;/p&gt;
2534 </description>
2535 </item>
2536
2537 <item>
2538 <title>New laptop - some more clues and ideas based on feedback</title>
2539 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
2540 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
2541 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
2542 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
2543 need for a new laptop, and provided very useful feedback. I wish to
2544 thank every one of these. Several pointed me to the possibility of
2545 fixing my X230, and I am already in the process of getting Lenovo to
2546 do so thanks to the on site, next day support contract covering the
2547 machine. But the battery is almost useless (I expect to replace it
2548 with a non-official battery) and I do not expect the machine to live
2549 for many more years, so it is time to plan its replacement. If I did
2550 not have a support contract, it was suggested to find replacement parts
2551 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2552 might present a language barrier as I do not understand French.&lt;/p&gt;
2553
2554 &lt;p&gt;One tip I got was to use the
2555 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2556 compare laptop models. It seem to have more models available than
2557 prisjakt.no. Another tip I got from someone I know have similar
2558 keyboard preferences was that the HP EliteBook 840 keyboard is not
2559 very good, and this matches my experience with earlier EliteBook
2560 keyboards I tested. Because of this, I will not consider it any further.
2561
2562 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2563 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2564 (which is missing from the X240), and is working fairly well with
2565 Debian Sid/Unstable according to
2566 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2567 got on the keyboard quality are not consistent. Some say the keyboard
2568 is good, others say it is ok, while others say it is not very good.
2569 Those with experience from X41 and and X60 agree that the X250
2570 keyboard is not as good as those trusty old laptops, and suggest I
2571 keep and fix my X230 instead of upgrading, or get a used X230 to
2572 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2573 activity and battery status, which is very convenient on my X230. I&#39;m
2574 also told that the CPU fan is running very often, making it a bit
2575 noisy. In any case, the X250 do not work out of the box with Debian
2576 Stable/Jessie, one of my requirements.&lt;/p&gt;
2577
2578 &lt;p&gt;I have also gotten a few vendor proposals, one was
2579 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2580 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2581 The latter look very attractive to me.&lt;/p&gt;
2582
2583 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2584 as I keep looking for a replacement.&lt;/p&gt;
2585
2586 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2587 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2588 different
2589 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2590 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2591 </description>
2592 </item>
2593
2594 <item>
2595 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2596 <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>
2597 <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>
2598 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2599 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2600 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2601 started flickering yesterday, and I suspect the cause is a broken
2602 cable, as changing the angle of the screen some times get rid of the
2603 flickering.&lt;/p&gt;
2604
2605 &lt;p&gt;My requirements have not really changed since I bought it, and is
2606 still as
2607 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2608 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2609 good help from
2610 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2611 where I could select at least a few of the requirements (mouse pin,
2612 wifi, weight) and go through the rest manually. Three button mouse
2613 and a good keyboard is not available as an option, and all the three
2614 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2615 G2) lack three mouse buttons). It is also unclear to me how good the
2616 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2617 the keyboard, even if the quality and robustness in the X series have
2618 deteriorated since X41.&lt;/p&gt;
2619
2620 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2621 seem sensible to me? Are there better services around to search the
2622 set of available laptops for features? Please send me an email if you
2623 have suggestions.&lt;/p&gt;
2624
2625 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2626 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2627 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2628 </description>
2629 </item>
2630
2631 <item>
2632 <title>How to stay with sysvinit in Debian Jessie</title>
2633 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2634 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2635 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2636 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2637 sysvinit as its boot system by default. But how can one keep using
2638 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2639 courtesy of
2640 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2641 Schubert&lt;/a&gt; and
2642 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2643 McVittie&lt;/a&gt;.
2644
2645 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2646 keep sysvinit as your boot system, create a file
2647 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2648 you upgrade:&lt;/p&gt;
2649
2650 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2651 Package: systemd-sysv
2652 Pin: release o=Debian
2653 Pin-Priority: -1
2654 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2655
2656 &lt;p&gt;This file content will tell apt and aptitude to not consider
2657 installing systemd-sysv as part of any installation and upgrade
2658 solution when resolving dependencies, and thus tell it to avoid
2659 systemd as a default boot system. The end result should be that the
2660 upgraded system keep using sysvinit.&lt;/p&gt;
2661
2662 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2663 get sysvinit installed by default (debootstrap used by
2664 debian-installer have no option for this), but one can tell the
2665 installer to switch to sysvinit before the first boot. Either by
2666 using a kernel argument to the installer, or by adding a line to the
2667 preseed file used. First, the kernel command line argument:
2668
2669 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2670 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2671 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2672
2673 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2674
2675 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2676 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2677 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2678
2679 &lt;p&gt;One can of course also do this after the first boot by installing
2680 the sysvinit-core package.&lt;/p&gt;
2681
2682 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2683 sysvinit boot sequence in Debian have several hardware specific bugs
2684 on Linux caused by the fact that it is unpredictable when hardware
2685 devices show up during boot. But on the other hand, the new default
2686 boot system still have a few rough edges I hope will be fixed before
2687 Jessie is released.&lt;/p&gt;
2688
2689 &lt;p&gt;Update 2014-11-26: Inspired by
2690 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2691 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2692 line.&lt;/p&gt;
2693 </description>
2694 </item>
2695
2696 <item>
2697 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2698 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2700 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2701 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2702 without anyone snooping, is a right every citicen have in a liberal
2703 democracy. But this right is under serious attack these days.&lt;/p&gt;
2704
2705 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2706 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2707 the whisleblower Snowden) more expensive for Internet email,
2708 is to deliver all email using SMTP via Tor. Such SMTP option would be
2709 a nice addition to the FreedomBox project if we could send email
2710 between FreedomBox machines without leaking metadata about the emails
2711 to the people peeking on the wire. I
2712 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2713 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2714 lot of useful feedback and suggestions. It also became obvious to me
2715 that this was not a novel idea, as the same idea was tested and
2716 documented by Johannes Berg as early as 2006, and both
2717 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2718 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2719 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2720
2721 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2722 providing the SMTP protocol on port 25, and use email addresses
2723 looking like username@hidden-service-name.onion. With such addresses
2724 the connections to port 25 on hidden-service-name.onion using Tor will
2725 go to the correct SMTP server. To do this, one need to configure the
2726 Tor daemon to provide the hidden service and the mail server to accept
2727 emails for this .onion domain. To learn more about Exim configuration
2728 in Debian and test the design provided by Johannes Berg in his FAQ, I
2729 set out yesterday to create a Debian package for making it trivial to
2730 set up such SMTP over Tor service based on Debian. Getting it to work
2731 were fairly easy, and
2732 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2733 source code for the Debian package&lt;/a&gt; is available from github. I
2734 plan to move it into Debian if further testing prove this to be a
2735 useful approach.&lt;/p&gt;
2736
2737 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2738 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2739 get rid of exim4). Install tor, clone the git repository mentioned
2740 above, build the deb and install it on the machine. Next, run
2741 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2742 the instructions to get the service up and running. Restart tor and
2743 exim when it is done, and test mail delivery using swaks like
2744 this:&lt;/p&gt;
2745
2746 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2747 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2748 --to fbx@dutlqrrmjhtfa3vp.onion
2749 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2750
2751 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2752 address with your own address to test your server. :)&lt;/p&gt;
2753
2754 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2755 easier and more automatic. Especially the tor setup need more work.
2756 Also, the package include a tor-smtp tool written in C, but its task
2757 should probably be rewritten in some script language to make the deb
2758 architecture independent. It would probably also make the code easier
2759 to review. The tor-smtp tool currently need to listen on a socket for
2760 exim to talk to it and is started using xinetd. It would be better if
2761 no daemon and no socket is needed. I suspect it is possible to get
2762 exim to run a command line tool for delivery instead of talking to a
2763 socket, and hope to figure out how in a future version of this
2764 system.&lt;/p&gt;
2765
2766 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2767 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2768 SMTorP. :)&lt;/p&gt;
2769 </description>
2770 </item>
2771
2772 <item>
2773 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2774 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2776 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2777 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2778 alioth.debian.org, you know the web interface is fairly slow to
2779 operate. First you visit one web page, enter the moderation password
2780 and get a new page shown with a list of all the messages to moderate
2781 and various options for each email address. This take a while for
2782 every list you moderate, and you need to do it regularly to do a good
2783 job as a list moderator. But there is a quick alternative,
2784 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
2785 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
2786 to moderate in a fraction of a second. Here is a test run on two
2787 lists I recently took over:&lt;/p&gt;
2788
2789 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2790 % time listadmin xiph
2791 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2792 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2793
2794 real 0m1.709s
2795 user 0m0.232s
2796 sys 0m0.012s
2797 %
2798 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2799
2800 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
2801 there are no message in the moderation queue. Every morning I
2802 currently moderate 68 mailman lists, and it normally take around two
2803 minutes. When I took over the two pkg-xiph lists above a few days
2804 ago, there were 400 emails waiting in the moderator queue. It took me
2805 less than 15 minutes to process them all using the listadmin
2806 program.&lt;/p&gt;
2807
2808 &lt;p&gt;If you install
2809 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
2810 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
2811 with content like this, the moderation task is a breeze:&lt;/p&gt;
2812
2813 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2814 username username@example.org
2815 spamlevel 23
2816 default discard
2817 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
2818
2819 password secret
2820 adminurl https://{domain}/mailman/admindb/{list}
2821 mailman-list@lists.example.com
2822
2823 password hidden
2824 other-list@otherserver.example.org
2825 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2826
2827 &lt;p&gt;There are other options to set as well. Check the manual page to
2828 learn the details.&lt;/p&gt;
2829
2830 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
2831 the SSL certificate is self signed or not properly signed by a
2832 generally accepted signing authority, you can set a environment
2833 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
2834
2835 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2836 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
2837 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2838
2839 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
2840 can provide an argument to the listadmin script like I do in the
2841 initial screen dump (the xiph argument). Using an argument, only
2842 lists matching the argument string will be processed. This make it
2843 quick to accept messages if you notice the moderation request in your
2844 email.&lt;/p&gt;
2845
2846 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
2847 mailing lists, as I simply do not have time to spend on that if the
2848 process was any slower. The listadmin program have saved me hours of
2849 time I could spend elsewhere over the years. It truly is nice free
2850 software.&lt;/p&gt;
2851
2852 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2853 activities, please send Bitcoin donations to my address
2854 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2855
2856 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
2857 configuration example. Also, I&#39;ve been told that the
2858 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
2859 sure why.&lt;/p&gt;
2860 </description>
2861 </item>
2862
2863 <item>
2864 <title>Debian Jessie, PXE and automatic firmware installation</title>
2865 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
2866 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
2867 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
2868 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
2869 problem that the WiFi card require some firmware to work properly.
2870 And it has been a pain to fix this using preseeding in Debian.
2871 Normally something more is needed. But thanks to
2872 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
2873 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
2874 to do this using simple preseeding.&lt;/p&gt;
2875
2876 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
2877 firmware for the hardware found in the machine (actually, requested by
2878 the kernel modules for the hardware). (It can also install user space
2879 programs supporting the hardware detected, but that is not the focus
2880 of this story.)&lt;/p&gt;
2881
2882 &lt;p&gt;To get this working in the default installation, two preeseding
2883 values are needed. First, the isenkram-cli package must be installed
2884 into the target chroot (aka the hard drive) before tasksel is executed
2885 in the pkgsel step of the debian-installer system. This is done by
2886 preseeding the base-installer/includes debconf value to include the
2887 isenkram-cli package. The package name is next passed to debootstrap
2888 for installation. With the isenkram-cli package in place, tasksel
2889 will automatically use the isenkram tasks to detect hardware specific
2890 packages for the machine being installed and install them, because
2891 isenkram-cli contain tasksel tasks.&lt;/p&gt;
2892
2893 &lt;p&gt;Second, one need to enable the non-free APT repository, because
2894 most firmware unfortunately is non-free. This is done by preseeding
2895 the apt-mirror-setup step. This is unfortunate, but for a lot of
2896 hardware it is the only option in Debian.&lt;/p&gt;
2897
2898 &lt;p&gt;The end result is two lines needed in your preseeding file to get
2899 firmware installed automatically by the installer:&lt;/p&gt;
2900
2901 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2902 base-installer base-installer/includes string isenkram-cli
2903 apt-mirror-setup apt-setup/non-free boolean true
2904 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2905
2906 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
2907 both firmware and user space packages when using this method. It also
2908 do not work well, so use version 0.15 or later. Installing both
2909 firmware and user space packages might give you a bit more than you
2910 want, so I decided to split the tasksel task in two, one for firmware
2911 and one for user space programs. The firmware task is enabled by
2912 default, while the one for user space programs is not. This split is
2913 implemented in the package currently in unstable.&lt;/p&gt;
2914
2915 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
2916 this recipe work for you. :)&lt;/p&gt;
2917
2918 &lt;p&gt;So, I bet you are wondering, how can this work. First and
2919 foremost, it work because tasksel is modular, and driven by whatever
2920 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2921 isenkram-cli package place two files for tasksel to find. First there
2922 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
2923
2924 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2925 Task: isenkram-packages
2926 Section: hardware
2927 Description: Hardware specific packages (autodetected by isenkram)
2928 Based on the detected hardware various hardware specific packages are
2929 proposed.
2930 Test-new-install: show show
2931 Relevance: 8
2932 Packages: for-current-hardware
2933
2934 Task: isenkram-firmware
2935 Section: hardware
2936 Description: Hardware specific firmware packages (autodetected by isenkram)
2937 Based on the detected hardware various hardware specific firmware
2938 packages are proposed.
2939 Test-new-install: mark show
2940 Relevance: 8
2941 Packages: for-current-hardware-firmware
2942 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2943
2944 &lt;p&gt;The key parts are Test-new-install which indicate how the task
2945 should be handled and the Packages line referencing to a script in
2946 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2947 list of packages to install. The for-current-hardware-firmware script
2948 look like this to list relevant firmware for the machine:
2949
2950 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2951 #!/bin/sh
2952 #
2953 PATH=/usr/sbin:$PATH
2954 export PATH
2955 isenkram-autoinstall-firmware -l
2956 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2957
2958 &lt;p&gt;With those two pieces in place, the firmware is installed by
2959 tasksel during the normal d-i run. :)&lt;/p&gt;
2960
2961 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
2962 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
2963 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
2964 install.&lt;/p&gt;
2965
2966 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
2967 pilots in testing this feature, as isenkram is used there now to
2968 install firmware, replacing the earlier scripts.&lt;/p&gt;
2969 </description>
2970 </item>
2971
2972 <item>
2973 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
2974 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
2975 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
2976 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
2977 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
2978 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2979 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
2980 on a screen normally showing the bread types and prizes:&lt;/p&gt;
2981
2982 &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;
2983
2984 &lt;p&gt;If it had booted as it was supposed to, I would never had known
2985 about this hidden Linux installation. It is interesting what
2986 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
2987 </description>
2988 </item>
2989
2990 <item>
2991 <title>New lsdvd release version 0.17 is ready</title>
2992 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
2993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
2994 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
2995 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
2996 got a new set of developers a few weeks ago, after the original
2997 developer decided to step down and pass the project to fresh blood.
2998 This project is now maintained by Petter Reinholdtsen and Steve
2999 Dibb.&lt;/p&gt;
3000
3001 &lt;p&gt;I just wrapped up
3002 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
3003 new lsdvd release&lt;/a&gt;, available in git or from
3004 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
3005 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
3006 0.17.&lt;/p&gt;
3007
3008 &lt;ul&gt;
3009
3010 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
3011 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
3012 non-existant, to work around additional copy protection&lt;/li&gt;
3013 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
3014 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
3015 &lt;li&gt;Fix include orders&lt;/li&gt;
3016 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
3017 &lt;li&gt;Fix the chapter count&lt;/li&gt;
3018 &lt;li&gt;Make sure the array size and the array limit used when initialising
3019 the palette size is the same.&lt;/li&gt;
3020 &lt;li&gt;Fix array printing.&lt;/li&gt;
3021 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
3022 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
3023 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
3024 with more GCC compiler warnings.&lt;/li&gt;
3025
3026 &lt;/ul&gt;
3027
3028 &lt;p&gt;This change bring together patches for lsdvd in use in various
3029 Linux and Unix distributions, as well as patches submitted to the
3030 project the last nine years. Please check it out. :)&lt;/p&gt;
3031 </description>
3032 </item>
3033
3034 <item>
3035 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
3036 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
3037 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
3038 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
3039 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3040 project&lt;/a&gt; provide a Linux solution for schools, including a
3041 powerful desktop with education software, a central server providing
3042 web pages, user database, user home directories, central login and PXE
3043 boot of both clients without disk and the installation to install Debian
3044 Edu on machines with disk (and a few other services perhaps to small
3045 to mention here). We in the Debian Edu team are currently working on
3046 the Jessie based version, trying to get everything in shape before the
3047 freeze, to avoid having to maintain our own package repository in the
3048 future. The
3049 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
3050 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
3051 work left. Some fatal problems block testing, breaking the installer,
3052 but it is possible to work around these to get anyway. Here is a
3053 recipe on how to get the installation limping along.&lt;/p&gt;
3054
3055 &lt;p&gt;First, download the test ISO via
3056 &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;,
3057 &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;
3058 or rsync (use
3059 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
3060 The ISO build was broken on Tuesday, so we do not get a new ISO every
3061 12 hours or so, but thankfully the ISO we already got we are able to
3062 install with some tweaking.&lt;/p&gt;
3063
3064 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
3065 (use Alt-Ctrl-F2), run&lt;/p&gt;
3066
3067 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3068 nano /usr/bin/edu-eatmydata-install
3069 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3070
3071 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
3072 optimization. Return to the installation, select the profile you want
3073 and continue. Without this change, exim4-config will fail to install
3074 due to a known bug in eatmydata.&lt;/p&gt;
3075
3076 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
3077 this do not work, figure out what your correct value would be. All my
3078 test machines need /dev/sda, so I have no advice if it do not fit
3079 your need.&lt;/p&gt;
3080
3081 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
3082 root after the initial boot from hard drive, and install the
3083 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3084 or mate. If you want several desktop options, install more than one
3085 metapackage. Once this is done, reboot and you should have a working
3086 graphical login screen. This workaround should no longer be needed
3087 once the education-tasks package version 1.801 enter testing in two
3088 days.&lt;/p&gt;
3089
3090 &lt;p&gt;I believe the ISO build will start working on two days when the new
3091 tasksel package enter testing and Steve McIntyre get a chance to
3092 update the debian-cd git repository. The eatmydata, grub and desktop
3093 issues are already fixed in unstable and testing, and should show up
3094 on the ISO as soon as the ISO build start working again. Well the
3095 eatmydata optimization is really just disabled. The proper fix
3096 require an upload by the eatmydata maintainer applying the patch
3097 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
3098 The rest have proper fixes in unstable.&lt;/p&gt;
3099
3100 &lt;p&gt;I hope this get you going with the installation testing, as we are
3101 quickly running out of time trying to get our Jessie based
3102 installation ready before the distribution freeze in a month.&lt;/p&gt;
3103 </description>
3104 </item>
3105
3106 <item>
3107 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
3108 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
3109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
3110 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
3111 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
3112 to handle my fairly large DVD collection. It is a nice command line
3113 tool to get details about a DVD, like title, tracks, track length,
3114 etc, in XML, Perl or human readable format. But lsdvd have not seen
3115 any new development since 2006 and had a few irritating bugs affecting
3116 its use with some DVDs. Upstream seemed to be dead, and in January I
3117 sent a small probe asking for a version control repository for the
3118 project, without any reply. But I use it regularly and would like to
3119 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
3120 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
3121 the project admin, and after getting a reply from him explaining that
3122 he was no longer interested in the project, I asked if I could take
3123 over. And yesterday, I became project admin.&lt;/p&gt;
3124
3125 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
3126 maintainer interested in joining forces to maintain the upstream
3127 project, and I hope we can get a new release out fairly quickly,
3128 collecting the patches spread around on the internet into on place.
3129 I&#39;ve added the relevant Debian patches to the freshly created git
3130 repository, and expect the Gentoo patches to make it too. If you got
3131 a DVD collection and care about command line tools, check out
3132 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
3133 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
3134 list&lt;/a&gt;. :)&lt;/p&gt;
3135 </description>
3136 </item>
3137
3138 <item>
3139 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
3140 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
3141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
3142 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
3143 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
3144 a lot quicker. When we install more than 2000 packages in
3145 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
3146 tasksel in the installer, unpacking the binary packages take forever.
3147 A part of the slow I/O issue was discussed in
3148 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
3149 much file system sync-ing done by dpkg, which is the package
3150 responsible for unpacking the binary packages. Other parts (like code
3151 executed by postinst scripts) might also sync to disk during
3152 installation. All this sync-ing to disk do not really make sense to
3153 me. If the machine crash half-way through, I start over, I do not try
3154 to salvage the half installed system. So the failure sync-ing is
3155 supposed to protect against, hardware or system crash, is not really
3156 relevant while the installer is running.&lt;/p&gt;
3157
3158 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
3159 system sync()-ing in a fairly non-intrusive way, without the need to
3160 change the code in several packages. The idea is not new, but I have
3161 not heard anyone propose the approach using dpkg-divert before. It
3162 depend on the small and clever package
3163 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
3164 uses LD_PRELOAD to replace the system functions for syncing data to
3165 disk with functions doing nothing, thus allowing programs to live
3166 dangerous while speeding up disk I/O significantly. Instead of
3167 modifying the implementation of dpkg, apt and tasksel (which are the
3168 packages responsible for selecting, fetching and installing packages),
3169 it occurred to me that we could just divert the programs away, replace
3170 them with a simple shell wrapper calling
3171 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
3172 Two days ago I decided to test the idea, and wrapped up a simple
3173 implementation for the Debian Edu udeb.&lt;/p&gt;
3174
3175 &lt;p&gt;The effect was stunning. In my first test it reduced the running
3176 time of the pkgsel step (installing tasks) from 64 to less than 44
3177 minutes (20 minutes shaved off the installation) on an old Dell
3178 Latitude D505 machine. I am not quite sure what the optimised time
3179 would have been, as I messed up the testing a bit, causing the debconf
3180 priority to get low enough for two questions to pop up during
3181 installation. As soon as I saw the questions I moved the installation
3182 along, but do not know how long the question were holding up the
3183 installation. I did some more measurements using Debian Edu Jessie,
3184 and got these results. The time measured is the time stamp in
3185 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
3186 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
3187 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3188 timing thus do not depend on how quickly the user handle the tasksel
3189 dialog.&lt;/p&gt;
3190
3191 &lt;p&gt;&lt;table&gt;
3192
3193 &lt;tr&gt;
3194 &lt;th&gt;Machine/setup&lt;/th&gt;
3195 &lt;th&gt;Original tasksel&lt;/th&gt;
3196 &lt;th&gt;Optimised tasksel&lt;/th&gt;
3197 &lt;th&gt;Reduction&lt;/th&gt;
3198 &lt;/tr&gt;
3199
3200 &lt;tr&gt;
3201 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
3202 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
3203 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
3204 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
3205 &lt;/tr&gt;
3206
3207 &lt;tr&gt;
3208 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
3209 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
3210 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
3211 &lt;td&gt;23 min 40%&lt;/td&gt;
3212 &lt;/tr&gt;
3213
3214 &lt;tr&gt;
3215 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
3216 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
3217 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
3218 &lt;td&gt;11 min 50%&lt;/td&gt;
3219 &lt;/tr&gt;
3220
3221 &lt;tr&gt;
3222 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
3223 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
3224 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
3225 &lt;td&gt;2 min 33%&lt;/td&gt;
3226 &lt;/tr&gt;
3227
3228 &lt;tr&gt;
3229 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
3230 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
3231 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
3232 &lt;td&gt;4 min 21%&lt;/td&gt;
3233 &lt;/tr&gt;
3234
3235 &lt;/table&gt;&lt;/p&gt;
3236
3237 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
3238 time is spent downloading packages. The connection to the Internet
3239 was 100Mbit/s during testing, so downloading should not be a
3240 significant factor in the measurement. Download typically took a few
3241 seconds to a few minutes, depending on the amount of packages being
3242 installed.&lt;/p&gt;
3243
3244 &lt;p&gt;The speedup is implemented by using two hooks in
3245 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3246 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3247 finish-install.d hook to remove the divert at the end of the
3248 installation. I picked the pre-pkgsel.d hook instead of the
3249 post-base-installer.d hook because I test using an ISO without the
3250 eatmydata package included, and the post-base-installer.d hook in
3251 Debian Edu can only operate on packages included in the ISO. The
3252 negative effect of this is that I am unable to activate this
3253 optimization for the kernel installation step in d-i. If the code is
3254 moved to the post-base-installer.d hook, the speedup would be larger
3255 for the entire installation.&lt;/p&gt;
3256
3257 &lt;p&gt;I&#39;ve implemented this in the
3258 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3259 git repository, and plan to provide the optimization as part of the
3260 Debian Edu installation. If you want to test this yourself, you can
3261 create two files in the installer (or in an udeb). One shell script
3262 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3263
3264 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3265 #!/bin/sh
3266 set -e
3267 . /usr/share/debconf/confmodule
3268 info() {
3269 logger -t my-pkgsel &quot;info: $*&quot;
3270 }
3271 error() {
3272 logger -t my-pkgsel &quot;error: $*&quot;
3273 }
3274 override_install() {
3275 apt-install eatmydata || true
3276 if [ -x /target/usr/bin/eatmydata ] ; then
3277 for bin in dpkg apt-get aptitude tasksel ; do
3278 file=/usr/bin/$bin
3279 # Test that the file exist and have not been diverted already.
3280 if [ -f /target$file ] ; then
3281 info &quot;diverting $file using eatmydata&quot;
3282 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3283 &gt; /target$file.edu
3284 chmod 755 /target$file.edu
3285 in-target dpkg-divert --package debian-edu-config \
3286 --rename --quiet --add $file
3287 ln -sf ./$bin.edu /target$file
3288 else
3289 error &quot;unable to divert $file, as it is missing.&quot;
3290 fi
3291 done
3292 else
3293 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3294 fi
3295 }
3296
3297 override_install
3298 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3299
3300 &lt;p&gt;To clean up, another shell script should go into
3301 /usr/lib/finish-install.d/ with code like this:
3302
3303 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3304 #! /bin/sh -e
3305 . /usr/share/debconf/confmodule
3306 error() {
3307 logger -t my-finish-install &quot;error: $@&quot;
3308 }
3309 remove_install_override() {
3310 for bin in dpkg apt-get aptitude tasksel ; do
3311 file=/usr/bin/$bin
3312 if [ -x /target$file.edu ] ; then
3313 rm /target$file
3314 in-target dpkg-divert --package debian-edu-config \
3315 --rename --quiet --remove $file
3316 rm /target$file.edu
3317 else
3318 error &quot;Missing divert for $file.&quot;
3319 fi
3320 done
3321 sync # Flush file buffers before continuing
3322 }
3323
3324 remove_install_override
3325 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3326
3327 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3328 edu-eatmydata-install and call it from the pre-pkgsel.d and
3329 finish-install.d scripts.&lt;/p&gt;
3330
3331 &lt;p&gt;By now you might ask if this change should get into the normal
3332 Debian installer too? I suspect it should, but am not sure the
3333 current debian-installer coordinators find it useful enough. It also
3334 depend on the side effects of the change. I&#39;m not aware of any, but I
3335 guess we will see if the change is safe after some more testing.
3336 Perhaps there is some package in Debian depending on sync() and
3337 fsync() having effect? Perhaps it should go into its own udeb, to
3338 allow those of us wanting to enable it to do so without affecting
3339 everyone.&lt;/p&gt;
3340
3341 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3342 will break installation of all programs using gnutls because of
3343 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3344 eatmydata package in Debian will solve it.&lt;/p&gt;
3345
3346 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3347 the optimization work again. And I have discovered that the
3348 dpkg-divert trick is not really needed and implemented a slightly
3349 simpler approach as part of the debian-edu-install package. See
3350 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3351
3352 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
3353 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
3354 triggering on i386 made it into testing, and broke this installation
3355 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
3356 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
3357 </description>
3358 </item>
3359
3360 <item>
3361 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
3362 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
3363 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
3364 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
3365 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
3366 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
3367 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
3368 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
3369 learn that there is a large set of publicly available key servers to
3370 use when looking for peoples public key. So far I have used
3371 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3372 were misbehaving, but those days are ended. The servers I have used
3373 up until yesterday have been slow and some times unavailable. I hope
3374 those problems are gone now.&lt;/p&gt;
3375
3376 &lt;p&gt;Behind the round robin DNS entry of the
3377 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
3378 there is a pool of more than 100 keyservers which are checked every
3379 day to ensure they are well connected and up to date. It must be
3380 better than what I have used so far. :)&lt;/p&gt;
3381
3382 &lt;p&gt;Yesterdays speaker told me that the service is the default
3383 keyserver provided by the default configuration in GnuPG, but this do
3384 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
3385
3386 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
3387 line:&lt;/p&gt;
3388
3389 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3390 keyserver pool.sks-keyservers.net
3391 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3392
3393 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
3394 entries in DNS. Just for fun, I did just that at work, so now every
3395 user of GnuPG at the University of Oslo should find a OpenGPG
3396 keyserver automatically should their need it:&lt;/p&gt;
3397
3398 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3399 % host -t srv _pgpkey-http._tcp.uio.no
3400 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
3401 %
3402 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3403
3404 &lt;p&gt;Now if only
3405 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
3406 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
3407 very happy. It can look up a given key or search for a user ID, but I
3408 normally do not want that, but to find a trust path from my key to
3409 another key. Given a user ID or key ID, I would like to find (and
3410 download) the keys representing a signature path from my key to the
3411 key in question, to be able to get a trust path between the two keys.
3412 This is as far as I can tell not possible today. Perhaps something
3413 for a future version of the protocol?&lt;/p&gt;
3414 </description>
3415 </item>
3416
3417 <item>
3418 <title>From English wiki to translated PDF and epub via Docbook</title>
3419 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
3420 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
3421 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
3422 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3423 project&lt;/a&gt; provide an instruction manual for teachers, system
3424 administrators and other users that contain useful tips for setting up
3425 and maintaining a Debian Edu installation. This text is about how the
3426 text processing of this manual is handled in the project.&lt;/p&gt;
3427
3428 &lt;p&gt;One goal of the project is to provide information in the native
3429 language of its users, and for this we need to handle translations.
3430 But we also want to make sure each language contain the same
3431 information, so for this we need a good way to keep the translations
3432 in sync. And we want it to be easy for our users to improve the
3433 documentation, avoiding the need to learn special formats or tools to
3434 contribute, and the obvious way to do this is to make it possible to
3435 edit the documentation using a web browser. We also want it to be
3436 easy for translators to keep the translation up to date, and give them
3437 help in figuring out what need to be translated. Here is the list of
3438 tools and the process we have found trying to reach all these
3439 goals.&lt;/p&gt;
3440
3441 &lt;p&gt;We maintain the authoritative source of our manual in the
3442 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
3443 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
3444 front page with references to the different chapters, several pages
3445 for each chapter, and finally one &quot;collection page&quot; gluing all the
3446 chapters together into one large web page (aka
3447 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
3448 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
3449 processing and translations. Thanks to the fact that the
3450 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
3451 wiki.debian.org support exporting pages in
3452 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
3453 the list of pages to export using the raw version of the AllInOne
3454 page, loop over each of them to generate a Docbook XML version of the
3455 manual. This process also download images and transform image
3456 references to use the locally downloaded images. The generated
3457 Docbook XML files are slightly broken, so some post-processing is done
3458 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
3459 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3460 a handfull of images. The XML file can now be used to generate PDF, HTML
3461 and epub versions of the English manual. This is the basic step of
3462 our process, making PDF (using dblatex), HTML (using xsltproc) and
3463 epub (using dbtoepub) version from Docbook XML, and the resulting files
3464 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
3465
3466 &lt;p&gt;But English documentation is not enough for us. We want translated
3467 documentation too, and we want to make it easy for translators to
3468 track the English original. For this we use the
3469 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
3470 which allow us to transform the English Docbook XML file into a
3471 translation file (a .pot file), usable with the normal gettext based
3472 translation tools used by those translating free software. The pot
3473 file is used to create and maintain translation files (several .po
3474 files), which the translations update with the native language
3475 translations of all titles, paragraphs and blocks of text in the
3476 original. The next step is combining the original English Docbook XML
3477 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3478 create a translated Docbook XML file (in this case
3479 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3480 translated, if the translation is not complete) Docbook XML file can
3481 then be used like the original to create a PDF, HTML and epub version
3482 of the documentation.&lt;/p&gt;
3483
3484 &lt;p&gt;The translators use different tools to edit the .po files. We
3485 recommend using
3486 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
3487 while some use emacs and vi, others can use web based editors like
3488 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
3489 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
3490 is where the .po file end up, in our git repository. Updated
3491 translations can either be committed directly to git, or submitted as
3492 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
3493 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
3494
3495 &lt;p&gt;One challenge is images, which both might need to be translated (if
3496 they show translated user applications), and are needed in different
3497 formats when creating PDF and HTML versions (epub is a HTML version in
3498 this regard). For this we transform the original PNG images to the
3499 needed density and format during build, and have a way to provide
3500 translated images by storing translated versions in
3501 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3502 package maintainers know more.&lt;/p&gt;
3503
3504 &lt;p&gt;If you wonder what the result look like, we provide
3505 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
3506 of the documentation packages on the web&lt;/a&gt;. See for example the
3507 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
3508 PDF version&lt;/a&gt; or the
3509 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
3510 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
3511 but perhaps it will be done in the future.&lt;/p&gt;
3512
3513 &lt;p&gt;To learn more, check out
3514 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
3515 debian-edu-doc package&lt;/a&gt;,
3516 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
3517 manual on the wiki&lt;/a&gt; and
3518 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
3519 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
3520 </description>
3521 </item>
3522
3523 <item>
3524 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
3525 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
3526 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
3527 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
3528 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
3529 related packages relevant for the computer installed automatically.
3530 So I implemented one, using
3531 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
3532 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
3533 run tasksel as user root. You should be presented with a new option,
3534 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
3535 select it, tasksel will install the packages isenkram claim is fit for
3536 the current hardware, hot pluggable or not.&lt;p&gt;
3537
3538 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
3539 description, and the other is the script used to extract the list of
3540 packages to install. The first part is in
3541 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
3542 this:&lt;/p&gt;
3543
3544 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3545 Task: isenkram
3546 Section: hardware
3547 Description: Hardware specific packages (autodetected by isenkram)
3548 Based on the detected hardware various hardware specific packages are
3549 proposed.
3550 Test-new-install: mark show
3551 Relevance: 8
3552 Packages: for-current-hardware
3553 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3554
3555 &lt;p&gt;The second part is in
3556 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3557 this:&lt;/p&gt;
3558
3559 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3560 #!/bin/sh
3561 #
3562 (
3563 isenkram-lookup
3564 isenkram-autoinstall-firmware -l
3565 ) | sort -u
3566 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3567
3568 &lt;p&gt;All in all, a very short and simple implementation making it
3569 trivial to install the hardware dependent package we all may want to
3570 have installed on our machines. I&#39;ve not been able to find a way to
3571 get tasksel to tell you exactly which packages it plan to install
3572 before doing the installation. So if you are curious or careful,
3573 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3574
3575 &lt;p&gt;The information about which packages are handling which hardware is
3576 fetched either from the isenkram package itself in
3577 /usr/share/isenkram/, from git.debian.org or from the APT package
3578 database (using the Modaliases header). The APT package database
3579 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3580 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3581 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3582 the python-apt code (bug
3583 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3584 workaround I was able to get rid of the file descriptor leak and
3585 reduce the memory leak from ~30 MiB per hardware detection down to
3586 around 2 MiB per hardware detection. It should make the desktop
3587 daemon a lot more useful. The fix is in version 0.7 uploaded to
3588 unstable today.&lt;/p&gt;
3589
3590 &lt;p&gt;I believe the current way of mapping hardware to packages in
3591 Isenkram is is a good draft, but in the future I expect isenkram to
3592 use the AppStream data source for this. A proposal for getting proper
3593 AppStream support into Debian is floating around as
3594 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3595 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3596 project&lt;/a&gt; will take place this summer to improve the situation. I
3597 look forward to seeing the result, and welcome patches for isenkram to
3598 start using the information when it is ready.&lt;/p&gt;
3599
3600 &lt;p&gt;If you want your package to map to some specific hardware, either
3601 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3602 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3603 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3604 package. See also
3605 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3606 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3607 the information will be migrated to AppStream eventually, but for the
3608 moment I got no better place to store it.&lt;/p&gt;
3609 </description>
3610 </item>
3611
3612 <item>
3613 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3614 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3615 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3616 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3617 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3618 project&lt;/a&gt; is working on providing the software and hardware to make
3619 it easy for non-technical people to host their data and communication
3620 at home, and being able to communicate with their friends and family
3621 encrypted and away from prying eyes. It is still going strong, and
3622 today a major mile stone was reached.&lt;/p&gt;
3623
3624 &lt;p&gt;Today, the last of the packages currently used by the project to
3625 created the system images were accepted into Debian Unstable. It was
3626 the freedombox-setup package, which is used to configure the images
3627 during build and on the first boot. Now all one need to get going is
3628 the build code from the freedom-maker git repository and packages from
3629 Debian. And once the freedombox-setup package enter testing, we can
3630 build everything directly from Debian. :)&lt;/p&gt;
3631
3632 &lt;p&gt;Some key packages used by Freedombox are
3633 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3634 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3635 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3636 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3637 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3638 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3639 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3640 are plans to integrate more packages into the setup. User
3641 documentation is maintained on the Debian wiki. Please
3642 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3643 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3644
3645 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3646 setup, run this on a Debian machine using a user with sudo rights to
3647 become root:&lt;/p&gt;
3648
3649 &lt;p&gt;&lt;pre&gt;
3650 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3651 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3652 u-boot-tools
3653 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3654 freedom-maker
3655 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3656 &lt;/pre&gt;&lt;/p&gt;
3657
3658 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3659 devices. See the README in the freedom-maker git repo for more
3660 details on the build. If you do not want all three images, trim the
3661 make line. Note that the virtualbox-image target is not really
3662 virtualbox specific. It create a x86 image usable in kvm, qemu,
3663 vmware and any other x86 virtual machine environment. You might need
3664 the version of vmdebootstrap in Jessie to get the build working, as it
3665 include fixes for a race condition with kpartx.&lt;/p&gt;
3666
3667 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3668 method, boot a Debian Wheezy ISO and use this boot argument to load
3669 the preseed values:&lt;/p&gt;
3670
3671 &lt;p&gt;&lt;pre&gt;
3672 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;
3673 &lt;/pre&gt;&lt;/p&gt;
3674
3675 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3676 it still work.&lt;/p&gt;
3677
3678 &lt;p&gt;If you wonder how to help, one task you could look at is using
3679 systemd as the boot system. It will become the default for Linux in
3680 Jessie, so we need to make sure it is usable on the Freedombox. I did
3681 a simple test a few weeks ago, and noticed dnsmasq failed to start
3682 during boot when using systemd. I suspect there are other problems
3683 too. :) To detect problems, there is a test suite included, which can
3684 be run from the plinth web interface.&lt;/p&gt;
3685
3686 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3687 us get the new release published. :) Please join us on
3688 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3689 irc.debian.org)&lt;/a&gt; and
3690 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3691 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3692 </description>
3693 </item>
3694
3695 <item>
3696 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3697 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3698 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3699 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3700 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3701 solution for use at home. My requirements are simple, it must be
3702 cheap and locally encrypted (in other words, I keep the encryption
3703 keys, the storage provider do not have access to my private files).
3704 One idea me and my friends had many years ago, before the cloud
3705 storage providers showed up, was to use Google mail as storage,
3706 writing a Linux block device storing blocks as emails in the mail
3707 service provided by Google, and thus get heaps of free space. On top
3708 of this one can add encryption, RAID and volume management to have
3709 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3710 I never found time to implement such system. But the last few weeks I
3711 have looked at a system called
3712 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3713 mounted network backed file system with the features I need.&lt;/p&gt;
3714
3715 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3716 handling several different storage providers, any with Amazon S3,
3717 Google Drive or OpenStack API. There are heaps of such storage
3718 providers. S3QL can also use a local directory as storage, which
3719 combined with sshfs allow for file storage on any ssh server. S3QL
3720 include support for encryption, compression, de-duplication, snapshots
3721 and immutable file systems, allowing me to mount the remote storage as
3722 a local mount point, look at and use the files as if they were local,
3723 while the content is stored in the cloud as well. This allow me to
3724 have a backup that should survive fire. The file system can not be
3725 shared between several machines at the same time, as only one can
3726 mount it at the time, but any machine with the encryption key and
3727 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3728
3729 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3730 package is included already. So to get started, run &lt;tt&gt;apt-get
3731 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3732 Greenqloud, after reading their nice recipe on
3733 &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
3734 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3735 in Iceland more than those in USA when it come to keeping my personal
3736 data safe and private, and thus would rather spend money on a company
3737 in Iceland. Another nice recipe is available from the article
3738 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3739 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3740 Admin magazine. When the provider is picked, figure out how to get
3741 the API key needed to connect to the storage API. With Greencloud,
3742 the key did not show up until I had added payment details to my
3743 account.&lt;/p&gt;
3744
3745 &lt;p&gt;Armed with the API access details, it is time to create the file
3746 system. First, create a new bucket in the cloud. This bucket is the
3747 file system storage area. I picked a bucket name reflecting the
3748 machine that was going to store data there, but any name will do.
3749 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3750 the API login and password, and a locally created password. Store it
3751 all in ~root/.s3ql/authinfo2 like this:
3752
3753 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3754 [s3c]
3755 storage-url: s3c://s.greenqloud.com:443/bucket-name
3756 backend-login: API-login
3757 backend-password: API-password
3758 fs-passphrase: local-password
3759 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3760
3761 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3762 but any sensible way to create a fairly random password should do it.
3763 Armed with these details, it is now time to run mkfs, entering the API
3764 details and password to create it:&lt;/p&gt;
3765
3766 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3767 # mkdir -m 700 /var/lib/s3ql-cache
3768 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3769 --ssl s3c://s.greenqloud.com:443/bucket-name
3770 Enter backend login:
3771 Enter backend password:
3772 Before using S3QL, make sure to read the user&#39;s guide, especially
3773 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3774 Enter encryption password:
3775 Confirm encryption password:
3776 Generating random encryption key...
3777 Creating metadata tables...
3778 Dumping metadata...
3779 ..objects..
3780 ..blocks..
3781 ..inodes..
3782 ..inode_blocks..
3783 ..symlink_targets..
3784 ..names..
3785 ..contents..
3786 ..ext_attributes..
3787 Compressing and uploading metadata...
3788 Wrote 0.00 MB of compressed metadata.
3789 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3790
3791 &lt;p&gt;The next step is mounting the file system to make the storage available.
3792
3793 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3794 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3795 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3796 Using 4 upload threads.
3797 Downloading and decompressing metadata...
3798 Reading metadata...
3799 ..objects..
3800 ..blocks..
3801 ..inodes..
3802 ..inode_blocks..
3803 ..symlink_targets..
3804 ..names..
3805 ..contents..
3806 ..ext_attributes..
3807 Mounting filesystem...
3808 # df -h /s3ql
3809 Filesystem Size Used Avail Use% Mounted on
3810 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
3811 #
3812 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3813
3814 &lt;p&gt;The file system is now ready for use. I use rsync to store my
3815 backups in it, and as the metadata used by rsync is downloaded at
3816 mount time, no network traffic (and storage cost) is triggered by
3817 running rsync. To unmount, one should not use the normal umount
3818 command, as this will not flush the cache to the cloud storage, but
3819 instead running the umount.s3ql command like this:
3820
3821 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3822 # umount.s3ql /s3ql
3823 #
3824 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3825
3826 &lt;p&gt;There is a fsck command available to check the file system and
3827 correct any problems detected. This can be used if the local server
3828 crashes while the file system is mounted, to reset the &quot;already
3829 mounted&quot; flag. This is what it look like when processing a working
3830 file system:&lt;/p&gt;
3831
3832 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3833 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
3834 Using cached metadata.
3835 File system seems clean, checking anyway.
3836 Checking DB integrity...
3837 Creating temporary extra indices...
3838 Checking lost+found...
3839 Checking cached objects...
3840 Checking names (refcounts)...
3841 Checking contents (names)...
3842 Checking contents (inodes)...
3843 Checking contents (parent inodes)...
3844 Checking objects (reference counts)...
3845 Checking objects (backend)...
3846 ..processed 5000 objects so far..
3847 ..processed 10000 objects so far..
3848 ..processed 15000 objects so far..
3849 Checking objects (sizes)...
3850 Checking blocks (referenced objects)...
3851 Checking blocks (refcounts)...
3852 Checking inode-block mapping (blocks)...
3853 Checking inode-block mapping (inodes)...
3854 Checking inodes (refcounts)...
3855 Checking inodes (sizes)...
3856 Checking extended attributes (names)...
3857 Checking extended attributes (inodes)...
3858 Checking symlinks (inodes)...
3859 Checking directory reachability...
3860 Checking unix conventions...
3861 Checking referential integrity...
3862 Dropping temporary indices...
3863 Backing up old metadata...
3864 Dumping metadata...
3865 ..objects..
3866 ..blocks..
3867 ..inodes..
3868 ..inode_blocks..
3869 ..symlink_targets..
3870 ..names..
3871 ..contents..
3872 ..ext_attributes..
3873 Compressing and uploading metadata...
3874 Wrote 0.89 MB of compressed metadata.
3875 #
3876 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3877
3878 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
3879 quick, about the same speed as local file access. Uploading large
3880 amount of data is to me limited by the bandwidth out of and into my
3881 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
3882 which is very close to my upload speed, and downloading the same
3883 Debian installation ISO gave me 610 kiB/s, close to my download speed.
3884 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
3885 network, not the file system code. I do not know what a good cache
3886 size would be, but suspect that the cache should e larger than your
3887 working set.&lt;/p&gt;
3888
3889 &lt;p&gt;I mentioned that only one machine can mount the file system at the
3890 time. If another machine try, it is told that the file system is
3891 busy:&lt;/p&gt;
3892
3893 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3894 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3895 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
3896 Using 8 upload threads.
3897 Backend reports that fs is still mounted elsewhere, aborting.
3898 #
3899 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3900
3901 &lt;p&gt;The file content is uploaded when the cache is full, while the
3902 metadata is uploaded once every 24 hour by default. To ensure the
3903 file system content is flushed to the cloud, one can either umount the
3904 file system, or ask S3QL to flush the cache and metadata using
3905 s3qlctrl:
3906
3907 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3908 # s3qlctrl upload-meta /s3ql
3909 # s3qlctrl flushcache /s3ql
3910 #
3911 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3912
3913 &lt;p&gt;If you are curious about how much space your data uses in the
3914 cloud, and how much compression and deduplication cut down on the
3915 storage usage, you can use s3qlstat on the mounted file system to get
3916 a report:&lt;/p&gt;
3917
3918 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3919 # s3qlstat /s3ql
3920 Directory entries: 9141
3921 Inodes: 9143
3922 Data blocks: 8851
3923 Total data size: 22049.38 MB
3924 After de-duplication: 21955.46 MB (99.57% of total)
3925 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
3926 Database size: 2.39 MB (uncompressed)
3927 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3928 #
3929 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3930
3931 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
3932 storage. I did not try to locate them all, but am aware of at least
3933 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
3934 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
3935 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
3936 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
3937 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
3938 accept payment in Bitcoin. Pick one that suit your need. Some of
3939 them provide several GiB of free storage, but the prize models are
3940 quite different and you will have to figure out what suits you
3941 best.&lt;/p&gt;
3942
3943 &lt;p&gt;While researching this blog post, I had a look at research papers
3944 and posters discussing the S3QL file system. There are several, which
3945 told me that the file system is getting a critical check by the
3946 science community and increased my confidence in using it. One nice
3947 poster is titled
3948 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
3949 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3950 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
3951 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3952 and Pamela Smith. Please have a look.&lt;/p&gt;
3953
3954 &lt;p&gt;Given my problems with different file systems earlier, I decided to
3955 check out the mounted S3QL file system to see if it would be usable as
3956 a home directory (in other word, that it provided POSIX semantics when
3957 it come to locking and umask handling etc). Running
3958 &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
3959 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
3960 no error was found. So the file system can be used for home
3961 directories, if one chooses to do so.&lt;/p&gt;
3962
3963 &lt;p&gt;If you do not want a locally file system, and want something that
3964 work without the Linux fuse file system, I would like to mention the
3965 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
3966 provide locally encrypted backup using a command line client. It have
3967 a nicer access control system, where one can split out read and write
3968 access, allowing some systems to write to the backup and others to
3969 only read from it.&lt;/p&gt;
3970
3971 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3972 activities, please send Bitcoin donations to my address
3973 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3974 </description>
3975 </item>
3976
3977 <item>
3978 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
3979 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
3980 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
3981 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
3982 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3983 project&lt;/a&gt; is working on providing the software and hardware for
3984 making it easy for non-technical people to host their data and
3985 communication at home, and being able to communicate with their
3986 friends and family encrypted and away from prying eyes. It has been
3987 going on for a while, and is slowly progressing towards a new test
3988 release (0.2).&lt;/p&gt;
3989
3990 &lt;p&gt;And what day could be better than the Pi day to announce that the
3991 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
3992 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3993 system), and can also be installed using a Debian installer preseed
3994 file. The Debian based Freedombox is now based on Debian Jessie,
3995 where most of the needed packages used are already present. Only one,
3996 the freedombox-setup package, is missing. To try to build your own
3997 boot image to test the current status, fetch the freedom-maker scripts
3998 and build using
3999 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
4000 with a user with sudo access to become root:
4001
4002 &lt;pre&gt;
4003 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4004 freedom-maker
4005 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4006 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4007 u-boot-tools
4008 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4009 &lt;/pre&gt;
4010
4011 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4012 devices. See the README for more details on the build. If you do not
4013 want all three images, trim the make line. But note that thanks to &lt;a
4014 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
4015 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
4016 kpartx call.&lt;/p&gt;
4017
4018 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4019 method, boot a Debian Wheezy ISO and use this boot argument to load
4020 the preseed values:&lt;/p&gt;
4021
4022 &lt;pre&gt;
4023 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;
4024 &lt;/pre&gt;
4025
4026 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
4027 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
4028 currently hang while setting up APT sources. Killing the
4029 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
4030 installation will get the installation going. This affect all
4031 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
4032
4033 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4034 us get the new release published. :) Please join us on
4035 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4036 irc.debian.org)&lt;/a&gt; and
4037 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4038 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4039 </description>
4040 </item>
4041
4042 <item>
4043 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
4044 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
4045 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
4046 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
4047 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
4048 innetgr tools, because I needed them in
4049 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
4050 ng-utils, and it has served me well. I placed the project under the
4051 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
4052 repository. But many years ago, the CVS repository was dropped (lost,
4053 not migrated to new hardware, not sure), and the project have lacked a
4054 proper home since then.&lt;/p&gt;
4055
4056 &lt;p&gt;Last summer, I had a look at the package and made a new release
4057 fixing a irritating crash bug, but was unable to store the changes in
4058 a proper source control system. I applied for a project on
4059 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
4060 to follow up on it. Until today. :)&lt;/p&gt;
4061
4062 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
4063 now have a new home, and a git repository with the highlight of the
4064 history of the project. I published all release tarballs and imported
4065 them into the git repository. As the project is really stable and not
4066 expected to gain new features any time soon, I decided to make a new
4067 release and call it 1.0. Visit the new project home on
4068 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
4069 if you want to check it out. The new version is also uploaded into
4070 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
4071 </description>
4072 </item>
4073
4074 <item>
4075 <title>Testing sysvinit from experimental in Debian Hurd</title>
4076 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
4077 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
4078 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
4079 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
4080 their changes into sysvinit, to allow them to use the normal sysvinit
4081 boot system instead of their old one. This follow up on the
4082 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
4083 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
4084 get Debian on Hurd working more like Debian on Linux. To get started,
4085 I downloaded a prebuilt hard disk image from
4086 &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;,
4087 and started it using virt-manager.&lt;/p&gt;
4088
4089 &lt;p&gt;The first think I had to do after logging in (root without any
4090 password) was to get the network operational. I followed
4091 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
4092 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
4093 commands as root to get the machine to accept a IP address from the
4094 kvm internal DHCP server:&lt;/p&gt;
4095
4096 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4097 settrans -fgap /dev/netdde /hurd/netdde
4098 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
4099 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
4100 dhclient /dev/eth0
4101 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4102
4103 &lt;p&gt;After this, the machine had internet connectivity, and I could
4104 upgrade it and install the sysvinit packages from experimental and
4105 enable it as the default boot system in Hurd.&lt;/p&gt;
4106
4107 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
4108 running on the machine it for ssh login to work a password need to be
4109 set. Also, note that a bug somewhere in openssh on Hurd block
4110 compression from working. Remember to turn that off on the client
4111 side.&lt;/p&gt;
4112
4113 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
4114 stuff:&lt;/p&gt;
4115
4116 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4117 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
4118 deb http://http.debian.net/debian/ experimental main
4119 EOF
4120 apt-get update
4121 apt-get dist-upgrade
4122 apt-get install -t experimental initscripts sysv-rc sysvinit \
4123 sysvinit-core sysvinit-utils
4124 update-alternatives --config runsystem
4125 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4126
4127 &lt;p&gt;To reboot after switching boot system, you have to use
4128 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
4129 yet a sysvinit process able to receive the signals from the normal
4130 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
4131 upgrading every package and rebooting, the network come up with DHCP
4132 after boot as it should, and the settrans/pkill hack mentioned at the
4133 start is no longer needed. But for some strange reason, there are no
4134 longer any login prompt in the virtual console, so I logged in using
4135 ssh instead.
4136
4137 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
4138 fail some times. No idea what the cause is, but hope the Hurd porters
4139 figure it out. At least Justus said on IRC (#debian-hurd on
4140 irc.debian.org) that they are aware of the problem. A way to reduce
4141 the impact is to upgrade to the Hurd packages built by Justus by
4142 adding this repository to the machine:&lt;/p&gt;
4143
4144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4145 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
4146 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4147 EOF
4148 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4149
4150 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
4151 http://ftp.debian-ports.org/debian, because some of the packages in
4152 unstable do not yet include the required patches that are lingering in
4153 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
4154
4155 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4156 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
4157 i emacs - GNU Emacs editor (metapackage)
4158 i gdb - GNU Debugger
4159 i hurd-recommended - Miscellaneous translators
4160 i isc-dhcp-client - ISC DHCP client
4161 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4162 i libc-bin - Embedded GNU C Library: Binaries
4163 i libc-dev-bin - Embedded GNU C Library: Development binaries
4164 i libc0.3 - Embedded GNU C Library: Shared libraries
4165 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4166 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4167 i multiarch-support - Transitional package to ensure multiarch compatibilit
4168 i A x11-common - X Window System (X.Org) infrastructure
4169 i xorg - X.Org X Window System
4170 i A xserver-xorg - X.Org X server
4171 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4172 #
4173 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4174
4175 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
4176 X.org did not work out of the box and I never took the time to follow
4177 the porters instructions to fix it. This time I was interested in the
4178 command line stuff.&lt;p&gt;
4179 </description>
4180 </item>
4181
4182 <item>
4183 <title>New chrpath release 0.16</title>
4184 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
4185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
4186 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
4187 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
4188 find problems in C, C++ and Java code using static source code
4189 analysis. It can detect a lot of different problems, and is very
4190 useful to find memory and locking bugs in the error handling part of
4191 the source. The company behind it provide
4192 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
4193 a community service&lt;/a&gt;, and many hundred free software projects are
4194 already checked. A few days ago I decided to have a closer look at
4195 the Coverity system, and discovered that the
4196 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
4197 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
4198 projects I am involved with was already registered. But these are
4199 fairly big, and I would also like to have a small and easy project to
4200 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
4201 checking of the chrpath project&lt;/a&gt;. It was
4202 added to the checker and discovered seven potential defects. Six of
4203 these were real, mostly resource &quot;leak&quot; when the program detected an
4204 error. Nothing serious, as the resources would be released a fraction
4205 of a second later when the program exited because of the error, but it
4206 is nice to do it right in case the source of the program some time in
4207 the future end up in a library. Having fixed all defects and added
4208 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
4209 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
4210 publish a new release. These are the release notes:&lt;/p&gt;
4211
4212 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
4213
4214 &lt;ul&gt;
4215
4216 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
4217 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
4218 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
4219
4220 &lt;/ul&gt;
4221
4222 &lt;p&gt;You can
4223 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4224 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
4225 project if something is wrong with the new release. The test suite
4226 did not discover any old errors, so if you find a new one, please also
4227 include a test suite check.&lt;/p&gt;
4228 </description>
4229 </item>
4230
4231 <item>
4232 <title>New chrpath release 0.15</title>
4233 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
4234 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
4235 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
4236 <description>&lt;p&gt;After many years break from the package and a vain hope that
4237 development would be continued by someone else, I finally pulled my
4238 acts together this morning and wrapped up a new release of chrpath,
4239 the command line tool to modify the rpath and runpath of already
4240 compiled ELF programs. The update was triggered by the persistence of
4241 Isha Vishnoi at IBM, which needed a new config.guess file to get
4242 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
4243 is working on. I checked the
4244 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
4245 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4246 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4247 packages for interesting patches (failed to find the source from
4248 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4249 These are the release notes:&lt;/p&gt;
4250
4251 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4252
4253 &lt;ul&gt;
4254
4255 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4256 with newer architectures. Thanks to isha vishnoi for the heads
4257 up.&lt;/li&gt;
4258
4259 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4260
4261 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4262 Matthias Klose.&lt;/li&gt;
4263
4264 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4265 Petr Machata found in Fedora.&lt;/li&gt;
4266
4267 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4268 .dynamic is a NULL terminated string. Based on patch found in
4269 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4270
4271 &lt;/ul&gt;
4272
4273 &lt;p&gt;You can
4274 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4275 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4276 project if something is wrong with the new release. The test suite
4277 did not discover any old errors, so if you find a new one, please also
4278 include a testsuite check.&lt;/p&gt;
4279 </description>
4280 </item>
4281
4282 <item>
4283 <title>Debian init.d boot script example for rsyslog</title>
4284 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4285 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4286 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4287 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4288 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4289 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4290 init.d scripts at all. Here is an example init.d script, ie a rewrite
4291 of /etc/init.d/rsyslog:&lt;/p&gt;
4292
4293 &lt;p&gt;&lt;pre&gt;
4294 #!/lib/init/init-d-script
4295 ### BEGIN INIT INFO
4296 # Provides: rsyslog
4297 # Required-Start: $remote_fs $time
4298 # Required-Stop: umountnfs $time
4299 # X-Stop-After: sendsigs
4300 # Default-Start: 2 3 4 5
4301 # Default-Stop: 0 1 6
4302 # Short-Description: enhanced syslogd
4303 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4304 # It is quite compatible to stock sysklogd and can be
4305 # used as a drop-in replacement.
4306 ### END INIT INFO
4307 DESC=&quot;enhanced syslogd&quot;
4308 DAEMON=/usr/sbin/rsyslogd
4309 &lt;/pre&gt;&lt;/p&gt;
4310
4311 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4312 script was 137 lines, and the above is just 15 lines, most of it meta
4313 info/comments.&lt;/p&gt;
4314
4315 &lt;p&gt;How to do this, you ask? Well, one create a new script
4316 /lib/init/init-d-script looking something like this:
4317
4318 &lt;p&gt;&lt;pre&gt;
4319 #!/bin/sh
4320
4321 # Define LSB log_* functions.
4322 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4323 # and status_of_proc is working.
4324 . /lib/lsb/init-functions
4325
4326 #
4327 # Function that starts the daemon/service
4328
4329 #
4330 do_start()
4331 {
4332 # Return
4333 # 0 if daemon has been started
4334 # 1 if daemon was already running
4335 # 2 if daemon could not be started
4336 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4337 || return 1
4338 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4339 $DAEMON_ARGS \
4340 || return 2
4341 # Add code here, if necessary, that waits for the process to be ready
4342 # to handle requests from services started subsequently which depend
4343 # on this one. As a last resort, sleep for some time.
4344 }
4345
4346 #
4347 # Function that stops the daemon/service
4348 #
4349 do_stop()
4350 {
4351 # Return
4352 # 0 if daemon has been stopped
4353 # 1 if daemon was already stopped
4354 # 2 if daemon could not be stopped
4355 # other if a failure occurred
4356 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
4357 RETVAL=&quot;$?&quot;
4358 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
4359 # Wait for children to finish too if this is a daemon that forks
4360 # and if the daemon is only ever run from this initscript.
4361 # If the above conditions are not satisfied then add some other code
4362 # that waits for the process to drop all resources that could be
4363 # needed by services started subsequently. A last resort is to
4364 # sleep for some time.
4365 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
4366 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
4367 # Many daemons don&#39;t delete their pidfiles when they exit.
4368 rm -f $PIDFILE
4369 return &quot;$RETVAL&quot;
4370 }
4371
4372 #
4373 # Function that sends a SIGHUP to the daemon/service
4374 #
4375 do_reload() {
4376 #
4377 # If the daemon can reload its configuration without
4378 # restarting (for example, when it is sent a SIGHUP),
4379 # then implement that here.
4380 #
4381 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
4382 return 0
4383 }
4384
4385 SCRIPTNAME=$1
4386 scriptbasename=&quot;$(basename $1)&quot;
4387 echo &quot;SN: $scriptbasename&quot;
4388 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
4389 script=&quot;$1&quot;
4390 shift
4391 . $script
4392 else
4393 exit 0
4394 fi
4395
4396 NAME=$(basename $DAEMON)
4397 PIDFILE=/var/run/$NAME.pid
4398
4399 # Exit if the package is not installed
4400 #[ -x &quot;$DAEMON&quot; ] || exit 0
4401
4402 # Read configuration variable file if it is present
4403 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
4404
4405 # Load the VERBOSE setting and other rcS variables
4406 . /lib/init/vars.sh
4407
4408 case &quot;$1&quot; in
4409 start)
4410 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
4411 do_start
4412 case &quot;$?&quot; in
4413 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4414 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4415 esac
4416 ;;
4417 stop)
4418 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
4419 do_stop
4420 case &quot;$?&quot; in
4421 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4422 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4423 esac
4424 ;;
4425 status)
4426 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
4427 ;;
4428 #reload|force-reload)
4429 #
4430 # If do_reload() is not implemented then leave this commented out
4431 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
4432 #
4433 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
4434 #do_reload
4435 #log_end_msg $?
4436 #;;
4437 restart|force-reload)
4438 #
4439 # If the &quot;reload&quot; option is implemented then remove the
4440 # &#39;force-reload&#39; alias
4441 #
4442 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
4443 do_stop
4444 case &quot;$?&quot; in
4445 0|1)
4446 do_start
4447 case &quot;$?&quot; in
4448 0) log_end_msg 0 ;;
4449 1) log_end_msg 1 ;; # Old process is still running
4450 *) log_end_msg 1 ;; # Failed to start
4451 esac
4452 ;;
4453 *)
4454 # Failed to stop
4455 log_end_msg 1
4456 ;;
4457 esac
4458 ;;
4459 *)
4460 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
4461 exit 3
4462 ;;
4463 esac
4464
4465 :
4466 &lt;/pre&gt;&lt;/p&gt;
4467
4468 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
4469 lot. I did not really polish the approach, so it might not always
4470 work out of the box, but you get the idea. I did not try very hard to
4471 optimize it nor make it more robust either.&lt;/p&gt;
4472
4473 &lt;p&gt;A better argument for switching init system in Debian than reducing
4474 the size of init scripts (which is a good thing to do anyway), is to
4475 get boot system that is able to handle the kernel events sensibly and
4476 robustly, and do not depend on the boot to run sequentially. The boot
4477 and the kernel have not behaved sequentially in years.&lt;/p&gt;
4478 </description>
4479 </item>
4480
4481 <item>
4482 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
4483 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
4484 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
4485 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
4486 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
4487 remote display access is the preferred solution with oVirt and RedHat
4488 Enterprise Virtualization, and I was sad to discover the other day
4489 that the browser plugin needed to use these systems seamlessly was
4490 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
4491 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
4492 2013-04-01, so I decided to wrap up a package based on the great work
4493 from Cajus Pollmeier and put it in a collab-maint maintained git
4494 repository to get a package I could use. I would very much like
4495 others to help me maintain the package (or just take over, I do not
4496 mind), but as no-one had volunteered so far, I just uploaded it to
4497 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
4498
4499 &lt;p&gt;The source is now available from
4500 &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;
4501 </description>
4502 </item>
4503
4504 <item>
4505 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
4506 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
4507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
4508 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
4509 <description>&lt;p&gt;The
4510 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
4511 program is a a very nice system to create virtual machine images. It
4512 create a image file, add a partition table, mount it and run
4513 debootstrap in the mounted directory to create a Debian system on a
4514 stick. Yesterday, I decided to try to teach it how to make images for
4515 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
4516 of a plan to simplify the build system for
4517 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
4518 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
4519 the virtualbox images, but its current build system made multistrap
4520 based system for Dreamplug images, and it is lacking support for
4521 Raspberry Pi.&lt;/p&gt;
4522
4523 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
4524 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4525 code and adjusted it to be able to build armel images on my amd64
4526 Debian laptop. I ended up giving vmdebootstrap five new options,
4527 allowing me to replicate the image creation process I use to make
4528 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
4529 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
4530 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
4531 call debootstrap with --foreign and to copy the handler into the
4532 generated chroot before running the second stage. This allow
4533 vmdebootstrap to create armel images on an amd64 host. Next I added
4534 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
4535 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
4536 given file system type, allowing me to create an image with a vfat
4537 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
4538 variant&lt;/tt&gt; option to allow me to create smaller images without the
4539 Debian base system packages installed. Finally, I added an option
4540 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
4541 as a boot loader. It is not needed on the Raspberry Pi and probably
4542 most other non-x86 architectures. The changes were accepted by the
4543 upstream author of vmdebootstrap yesterday and today, and is now
4544 available from
4545 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
4546 upstream project page&lt;/a&gt;.&lt;/p&gt;
4547
4548 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
4549 create a small script (the customize script) to add the non-free
4550 binary blob needed to boot the Raspberry Pi and the APT source
4551 list:&lt;/p&gt;
4552
4553 &lt;p&gt;&lt;pre&gt;
4554 #!/bin/sh
4555 set -e # Exit on first error
4556 rootdir=&quot;$1&quot;
4557 cd &quot;$rootdir&quot;
4558 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4559 deb http://http.debian.net/debian/ jessie main contrib non-free
4560 EOF
4561 # Install non-free binary blob needed to boot Raspberry Pi. This
4562 # install a kernel somewhere too.
4563 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4564 -O $rootdir/usr/bin/rpi-update
4565 chmod a+x $rootdir/usr/bin/rpi-update
4566 mkdir -p $rootdir/lib/modules
4567 touch $rootdir/boot/start.elf
4568 chroot $rootdir rpi-update
4569 &lt;/pre&gt;&lt;/p&gt;
4570
4571 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4572 to build the image:&lt;/p&gt;
4573
4574 &lt;pre&gt;
4575 sudo ./vmdebootstrap \
4576 --variant minbase \
4577 --arch armel \
4578 --distribution jessie \
4579 --mirror http://http.debian.net/debian \
4580 --image test.img \
4581 --size 600M \
4582 --bootsize 64M \
4583 --boottype vfat \
4584 --log-level debug \
4585 --verbose \
4586 --no-kernel \
4587 --no-extlinux \
4588 --root-password raspberry \
4589 --hostname raspberrypi \
4590 --foreign /usr/bin/qemu-arm-static \
4591 --customize `pwd`/customize \
4592 --package netbase \
4593 --package git-core \
4594 --package binutils \
4595 --package ca-certificates \
4596 --package wget \
4597 --package kmod
4598 &lt;/pre&gt;&lt;/p&gt;
4599
4600 &lt;p&gt;The list of packages being installed are the ones needed by
4601 rpi-update to make the image bootable on the Raspberry Pi, with the
4602 exception of netbase, which is needed by debootstrap to find
4603 /etc/hosts with the minbase variant. I really wish there was a way to
4604 set up an Raspberry Pi using only packages in the Debian archive, but
4605 that is not possible as far as I know, because it boots from the GPU
4606 using a non-free binary blob.&lt;/p&gt;
4607
4608 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4609 probably a few others installed. I have not checked the complete
4610 build dependency list.&lt;/p&gt;
4611
4612 &lt;p&gt;The resulting image will not use the hardware floating point unit
4613 on the Raspberry PI, because the armel architecture in Debian is not
4614 optimized for that use. So the images created will be a bit slower
4615 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4616 </description>
4617 </item>
4618
4619 <item>
4620 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4621 <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>
4622 <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>
4623 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4624 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4625 wider attention. I recommend signing and donating to each one of
4626 these. :)&lt;/p&gt;
4627
4628 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4629 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4630 Women program which is a Google Summer of Code like initiative to get
4631 more women involved in free software. One debian sponsor has offered
4632 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4633 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4634 hope you will to. :)&lt;/p&gt;
4635
4636 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4637 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4638 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4639 take place these days, and their need to fund the work. I&#39;ve already
4640 donated. Are you next?&lt;/p&gt;
4641
4642 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4643 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4644 statement under the heading
4645 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4646 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4647 Norwegian government. So far 499 signatures. I hope you will sign it
4648 too.&lt;/p&gt;
4649 </description>
4650 </item>
4651
4652 <item>
4653 <title>Videos about the Freedombox project - for inspiration and learning</title>
4654 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4656 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4657 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4658 project&lt;/a&gt; have been going on for a while, and have presented the
4659 vision, ideas and solution several places. Here is a little
4660 collection of videos of talks and presentation of the project.&lt;/p&gt;
4661
4662 &lt;ul&gt;
4663
4664 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4665 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4666
4667 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4668 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4669
4670 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4671 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4672 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4673 (Youtube)&lt;/li&gt;
4674
4675 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4676 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4677
4678 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4679 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4680
4681 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4682 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4683 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4684
4685 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4686 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4687 (Youtube)&lt;/li&gt;
4688
4689 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4690 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4691
4692 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4693 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4694
4695 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4696 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4697 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4698
4699 &lt;/ul&gt;
4700
4701 &lt;p&gt;A larger list is available from
4702 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4703 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4704
4705 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4706 Jessie is coming along quite well, and soon both Owncloud and using
4707 Tor should be available for testers of the Freedombox solution. :) In
4708 a few weeks I hope everything needed to test it is included in Debian.
4709 The withsqlite package is already in Debian, and the plinth package is
4710 pending in NEW. The third and vital part of that puzzle is the
4711 metapackage/setup framework, which is still pending an upload. Join
4712 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4713 (#freedombox on irc.debian.org)&lt;/a&gt; and
4714 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4715 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4716 </description>
4717 </item>
4718
4719 <item>
4720 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4721 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4723 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4724 <description>&lt;p&gt;I was introduced to the
4725 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4726 in 2010, when Eben Moglen presented his vision about serving the need
4727 of non-technical people to keep their personal information private and
4728 within the legal protection of their own homes. The idea is to give
4729 people back the power over their network and machines, and return
4730 Internet back to its intended peer-to-peer architecture. Instead of
4731 depending on a central service, the Freedombox will give everyone
4732 control over their own basic infrastructure.&lt;/p&gt;
4733
4734 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4735 taken priority. But this summers nasty news about the misuse of trust
4736 and privilege exercised by the &quot;western&quot; intelligence gathering
4737 communities increased my eagerness to contribute to a point where I
4738 actually started working on the project a while back.&lt;/p&gt;
4739
4740 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4741 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4742 create a simple and cheap Debian based appliance that anyone can hook
4743 up in their home and get access to secure and private services and
4744 communication. The initial deployment platform have been the
4745 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4746 which is a piece of hardware I do not own. So to be able to test what
4747 the current Freedombox setup look like, I had to come up with a way to install
4748 it on some hardware I do have access to. I have rewritten the
4749 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4750 image build framework to use .deb packages instead of only copying
4751 setup into the boot images, and thanks to this rewrite I am able to
4752 set up any machine supported by Debian Wheezy as a Freedombox, using
4753 the previously mentioned deb (and a few support debs for packages
4754 missing in Debian).&lt;/p&gt;
4755
4756 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4757 scripts
4758 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4759 and a administrative web interface
4760 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4761 withsqlite), as well as a privacy enhancing proxy based on
4762 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4763 (freedombox-privoxy). There is also a web/javascript based XMPP
4764 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4765 trying (unsuccessfully so far) to talk to the XMPP server
4766 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4767 web interface is pluggable, and the goal is to use it to enable OpenID
4768 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4769 this is really working yet, see
4770 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4771 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4772 on github at the moment. The HTTP proxy is operational out of the
4773 box, and the admin web interface can be used to add/remove plinth
4774 users. I&#39;ve not been able to do anything else with it so far, but
4775 know there are several branches spread around github and other places
4776 with lots of half baked features.&lt;/p&gt;
4777
4778 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4779 following recipes should work to give you a test machine to poke
4780 at.&lt;/p&gt;
4781
4782 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
4783
4784 &lt;ol&gt;
4785
4786 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
4787 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
4788 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
4789 to the Debian installer:&lt;p&gt;
4790 &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;
4791
4792 &lt;li&gt;Answer the few language/region/password questions and pick disk to
4793 install on.&lt;/li&gt;
4794
4795 &lt;li&gt;When the installation is finished and the machine have rebooted a
4796 few times, your Freedombox is ready for testing.&lt;/li&gt;
4797
4798 &lt;/ol&gt;
4799
4800 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
4801
4802 &lt;ol&gt;
4803
4804 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
4805 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
4806 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
4807 &lt;pre&gt;
4808 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
4809 &lt;/pre&gt;&lt;/li&gt;
4810 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
4811 &lt;pre&gt;
4812 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4813 apt-key add -
4814 apt-get update
4815 apt-get install freedombox-setup
4816 /usr/lib/freedombox/setup
4817 &lt;/pre&gt;&lt;/li&gt;
4818 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
4819
4820 &lt;/ol&gt;
4821
4822 &lt;p&gt;You can test it on other architectures too, but because the
4823 freedombox-privoxy package is binary, it will only work as intended on
4824 the architectures where I have had time to build the binary and put it
4825 in my APT repository. But do not let this stop you. It is only a
4826 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
4827
4828 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
4829 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
4830 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
4831 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
4832
4833 &lt;p&gt;Please let me know if this works for you, or if you have any
4834 problems. We gather on the IRC channel
4835 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
4836 irc.debian.org and the
4837 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
4838 mailing list&lt;/a&gt;.&lt;/p&gt;
4839
4840 &lt;p&gt;Once you get your freedombox operational, you can visit
4841 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
4842 welcome screen (dead end - do not be surprised if you are unable to
4843 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
4844 to look at the rest of plinth. The default user is &#39;admin&#39; and the
4845 default password is &#39;secret&#39;.&lt;/p&gt;
4846 </description>
4847 </item>
4848
4849 <item>
4850 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
4851 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
4852 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
4853 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
4854 <description>&lt;p&gt;Earlier, I reported about
4855 &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
4856 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
4857 told by IBM that the original disk should be thrown away. And as
4858 there no longer was a problem if I bricked the firmware, I decided
4859 today to try to install Intel firmware to replace the Lenovo firmware
4860 currently on the disk.&lt;/p&gt;
4861
4862 &lt;p&gt;I searched the Intel site for firmware, and found
4863 &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;
4864 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4865 according to the site should contain the latest firmware for SSD
4866 disks. I inserted the broken disk in one of my spare laptops and
4867 booted the ISO from a USB stick. The disk was recognized, but the
4868 program claimed the newest firmware already were installed and refused
4869 to insert any Intel firmware. So no change, and the disk is still
4870 unable to handle write load. :( I guess the only way to get them
4871 working would be if Lenovo releases new firmware. No idea how likely
4872 that is. Anyway, just blogging about this test for completeness. I
4873 got a working Samsung disk, and see no point in spending more time on
4874 the broken disks.&lt;/p&gt;
4875 </description>
4876 </item>
4877
4878 <item>
4879 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
4880 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
4881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
4882 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
4883 <description>&lt;p&gt;Today I switched to
4884 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
4885 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
4886 my new Thinkpad X230, which was delivered with an
4887 &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
4888 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
4889 sustained writes. My hardware supplier have been very forthcoming in
4890 trying to find a solution, and after first trying with another
4891 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
4892 disk instead to fix it once and for all. The Samsung disk survived
4893 the installation of Debian with encrypted disks (filling the disk with
4894 random data during installation killed the first two), and I thus
4895 decided to trust it with my data. I have installed it as a Debian Edu
4896 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4897 server at home using Kerberos and LDAP, and will use it as my work
4898 station from now on.&lt;/p&gt;
4899
4900 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
4901 Debian Wheezy default installation need to be tuned a bit to increase
4902 performance and increase life time of the disk. The Linux kernel and
4903 user space applications do not yet adjust automatically to such
4904 environment. To make it easier for my self, I created a draft Debian
4905 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
4906 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
4907 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
4908 is set up to adjust the setup of the machine by just installing the
4909 package. If there is any non-SSD disk in the machine, the package
4910 will refuse to install, as I did not try to write any logic to sort
4911 file systems in SSD and non-SSD file systems.&lt;/p&gt;
4912
4913 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
4914 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4915 where I set up the machine with one large encrypted partition (in
4916 addition to /boot), put LVM on top of this and set up partitions on
4917 top of this again. See the README file in the package source for the
4918 references I used to pick the settings. At the moment these
4919 parameters are tuned:&lt;/p&gt;
4920
4921 &lt;ul&gt;
4922
4923 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
4924 (adding discard to /etc/crypttab)&lt;/li&gt;
4925
4926 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
4927 this case a cryptsetup partition) by changing issue_discards from
4928 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
4929
4930 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
4931 systems.&lt;/li&gt;
4932
4933 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
4934 /etc/fstab.&lt;/li&gt;
4935
4936 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
4937
4938 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
4939 cron.daily).&lt;/li&gt;
4940
4941 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
4942 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
4943
4944 &lt;/ul&gt;
4945
4946 &lt;p&gt;During installation, I cancelled the part where the installer fill
4947 the disk with random data, as this would kill the SSD performance for
4948 little gain. My goal with the encrypted file system is to ensure
4949 those stealing my laptop end up with a brick and not a working
4950 computer. I have no hope in keeping the really resourceful people
4951 from getting the data on the disk (see
4952 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
4953 Thus I concluded that adding the discard option to crypttab is the
4954 right thing to do.&lt;/p&gt;
4955
4956 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
4957 it for SSD, but others recommended deadline and a benchmark I found
4958 indicated that deadline might be better for interactive use.&lt;/p&gt;
4959
4960 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
4961 and ext4, but read that it would give a performance hit ever time a
4962 file is removed, and thought it best to that that slowdown once a day
4963 instead of during my work.&lt;/p&gt;
4964
4965 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4966 this is already done by Debian Edu.&lt;/p&gt;
4967
4968 &lt;p&gt;I have not yet started on the user space tuning. I expect
4969 iceweasel need some tuning, and perhaps other applications too, but
4970 have not yet had time to investigate those parts.&lt;/p&gt;
4971
4972 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
4973 there.&lt;/p&gt;
4974
4975 &lt;p&gt;As for the answer to the question in the title of this blog post,
4976 as far as I know, the only solution I know about is to replace the
4977 disk. It might be possible to flash it with Intel firmware instead of
4978 the Lenovo firmware. But I have not tried and did not want to do so
4979 without approval from Lenovo as I wanted to keep the warranty on the
4980 disk until a solution was found and they wanted the broken disks
4981 back.&lt;/p&gt;
4982 </description>
4983 </item>
4984
4985 <item>
4986 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
4987 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
4988 <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>
4989 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
4990 <description>&lt;p&gt;A few days ago, I wrote about
4991 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
4992 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
4993 was dying during installation because it is unable to cope with
4994 sustained write. My supplier is in contact with
4995 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
4996 replacement disk to try to fix the problem. They decided to send an
4997 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
4998
4999 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
5000 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5001 same firmware version as the original. This time my hope raised
5002 slightly as the installation progressed, as the original disk used to
5003 die after 4-7% of the disk was written to, while this time it kept
5004 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
5005 died again and I was back on square one. I still do not have a new
5006 laptop with a disk I can trust. I can not live with a disk that might
5007 lock up when I download a new
5008 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
5009 other large files. I look forward to hearing from my supplier with
5010 the next proposal from Lenovo.&lt;/p&gt;
5011
5012 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
5013 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5014 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5015 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
5016 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5017 P/N 45N8295, P0C38732.&lt;/p&gt;
5018
5019 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
5020 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
5021 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5022 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
5023 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5024 P/N 45N8295, P0C38732.&lt;/p&gt;
5025
5026 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
5027 SA, date and WNPP values. Mentioning all the details here in case
5028 someone is able to use the information to find a way to identify the
5029 failing disk among working ones (if any such working disk actually
5030 exist).&lt;/p&gt;
5031 </description>
5032 </item>
5033
5034 <item>
5035 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
5036 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
5037 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
5038 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
5039 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
5040 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5041 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
5042 member assosiation NUUG&lt;/a&gt; and
5043 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
5044 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
5045 Bitraf&lt;/a&gt;.&lt;/p&gt;
5046
5047 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
5048 welcome, and there is no fee to participate. There is on the other
5049 hand limited space, and only room for 30 people. Please put your name
5050 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
5051 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
5052 </description>
5053 </item>
5054
5055 <item>
5056 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
5057 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
5058 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
5059 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
5060 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
5061 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
5062 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
5063 time to spend on it, and it took a while to find a model I believe
5064 will do the job, but two days ago the replacement finally arrived. I
5065 ended up picking a
5066 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
5067 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5068 a roaming workstation, and it seemed to work flawlessly. But my
5069 second installation with encrypted disk was not as successful. More
5070 on that below.&lt;/p&gt;
5071
5072 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5073 important requirements (robust and with a good keyboard) are never
5074 listed in the feature list. But I did get good help from the search
5075 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5076 allowed me to limit the list of interesting laptops based on my other
5077 requirements. A bit surprising that SSD disk are not disks according
5078 to that search interface, so I had to drop specifying the number of
5079 disks from my search parameters. I also asked around among friends to
5080 get their impression on keyboards and robustness.&lt;/p&gt;
5081
5082 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
5083 X41. I am not quite convinced about the keyboard, as it is
5084 significantly wider than my old keyboard, and I have to stretch my
5085 hand a lot more to reach the edges. But the key response is fairly
5086 good and the individual key shape is fairly easy to handle, so I hope
5087 I will get used to it. My old X40 was starting to fail, and I really
5088 needed a new laptop now. :)&lt;/p&gt;
5089
5090 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
5091 visit to the BIOS during boot it disable it.&lt;/p&gt;
5092
5093 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
5094 lock up during load. And this happen when installing Debian Wheezy
5095 with encrypted disk, while the disk is being filled with random data.
5096 I also tested to install Ubuntu Raring, and it happen there too if I
5097 reenable the code to fill the disk with random data (it is disabled by
5098 default in Ubuntu). And the bug with is already known. It was
5099 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
5100 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
5101 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5102 kernel developers as
5103 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
5104 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
5105 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5106 Lenovo forums, both for
5107 &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
5108 2012-11-10&lt;/a&gt; and for
5109 &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
5110 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
5111 reports state that the disk lock up during use if many writes are done
5112 on the disk, so it is much no use to work around the installation
5113 problem and end up with a computer that can lock up at any moment.
5114 There is even a
5115 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
5116 available&lt;/a&gt; that will lock up the hard drive after running a few
5117 minutes by writing to a file.&lt;/p&gt;
5118
5119 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
5120 contacting PCHELP Norway (request 01D1FDP) which handle support
5121 requests for Lenovo, his first suggestion was to upgrade the disk
5122 firmware. Unfortunately there is no newer firmware available from
5123 Lenovo, as my disk already have the most recent one (version LF1i). I
5124 hope to hear more from him today and hope the problem can be
5125 fixed. :)&lt;/p&gt;
5126 </description>
5127 </item>
5128
5129 <item>
5130 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
5131 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
5132 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
5133 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
5134 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
5135 trusty old Thinkpad X41. Unfortunately I did not have much time to
5136 spend on it, but today the replacement finally arrived. I ended up
5137 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
5138 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
5139 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5140 this, it is installing what I hope will be a more final installation,
5141 with a encrypted hard drive to ensure any dope head stealing it end up
5142 with an expencive door stop.&lt;/p&gt;
5143
5144 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5145 important requirements (robust and with a good keyboard) are never
5146 listed in the feature list. But I did get good help from the search
5147 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5148 allowed me to limit the list of interesting laptops based on my other
5149 requirements. A bit surprising that SSD disk are not disks, so I had
5150 to drop number of disks from my search parameters.&lt;/p&gt;
5151
5152 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
5153 wider than my old keyboard, and I have to stretch my hand a lot more
5154 to reach the edges. But the key response is fairly good and the
5155 individual key shape is fairly easy to handle, so I hope I will get
5156 used to it. My old X40 was starting to fail, and I really needed a
5157 new laptop now. :)&lt;/p&gt;
5158
5159 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
5160 </description>
5161 </item>
5162
5163 <item>
5164 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
5165 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
5166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
5167 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
5168 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
5169 perfectly capable of, and I have to do it manually to get things
5170 working. One such task is to find out what firmware packages are
5171 needed to get the hardware on my computer working. Most often this
5172 affect the wifi card, but some times it even affect the RAID
5173 controller or the ethernet card. Today I pushed version 0.4 of the
5174 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
5175 including a new script isenkram-autoinstall-firmware handling the
5176 process of asking all the loaded kernel modules what firmware files
5177 they want, find debian packages providing these files and install the
5178 debian packages. Here is a test run on my laptop:&lt;/p&gt;
5179
5180 &lt;p&gt;&lt;pre&gt;
5181 # isenkram-autoinstall-firmware
5182 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5183 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5184 info: locating packages with the requested firmware files
5185 info: Updating APT sources after adding non-free APT source
5186 info: trying to install firmware-ipw2x00
5187 firmware-ipw2x00
5188 firmware-ipw2x00
5189 Preconfiguring packages ...
5190 Selecting previously deselected package firmware-ipw2x00.
5191 (Reading database ... 259727 files and directories currently installed.)
5192 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5193 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
5194 #
5195 &lt;/pre&gt;&lt;/p&gt;
5196
5197 &lt;p&gt;When all the requested firmware is present, a simple message is
5198 printed instead:&lt;/p&gt;
5199
5200 &lt;p&gt;&lt;pre&gt;
5201 # isenkram-autoinstall-firmware
5202 info: did not find any firmware files requested by loaded kernel modules. exiting
5203 #
5204 &lt;/pre&gt;&lt;/p&gt;
5205
5206 &lt;p&gt;It could use some polish, but it is already working well and saving
5207 me some time when setting up new machines. :)&lt;/p&gt;
5208
5209 &lt;p&gt;So, how does it work? It look at the set of currently loaded
5210 kernel modules, and look up each one of them using modinfo, to find
5211 the firmware files listed in the module meta-information. Next, it
5212 download the Contents file from a nearby APT mirror, and search for
5213 the firmware files in this file to locate the package with the
5214 requested firmware file. If the package is in the non-free section, a
5215 non-free APT source is added and the package is installed using
5216 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
5217 machine.&lt;/p&gt;
5218
5219 &lt;p&gt;I hope someone find time to implement a more polished version of
5220 this script as part of the hw-detect debian-installer module, to
5221 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
5222 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
5223 firmware during a PXE install when the packages already are available
5224 from the nearby Debian mirror.&lt;/p&gt;
5225 </description>
5226 </item>
5227
5228 <item>
5229 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
5230 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
5231 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
5232 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
5233 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5234 the screen just turn black when Linux boot, either during installation
5235 or on first boot from the hard disk. I&#39;ve seen it once in a while the
5236 last few years, but only recently understood the cause. I&#39;ve seen it
5237 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5238 The reason seem to be in the wiring of some laptops. The system to
5239 control the screen background light is inverted, so when Linux try to
5240 turn the brightness fully on, it end up turning it off instead. I do
5241 not know which Linux drivers are affected, but this post is about the
5242 i915 driver used by the
5243 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5244 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
5245
5246 &lt;p&gt;The problem can be worked around two ways. Either by adding
5247 i915.invert_brightness=1 as a kernel option, or by adding a file in
5248 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5249 option when it load the i915 kernel module. On Debian and Ubuntu, it
5250 can be done by running these commands as root:&lt;/p&gt;
5251
5252 &lt;pre&gt;
5253 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5254 update-initramfs -u -k all
5255 &lt;/pre&gt;
5256
5257 &lt;p&gt;Since March 2012 there is
5258 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5259 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5260 hardware have this problem, and get the driver to invert the
5261 brightness setting automatically. To use it, one need to add a row in
5262 &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
5263 intel_quirks array&lt;/a&gt; in the driver source
5264 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5265 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5266 number (vendor number 8086 is assumed) and subdevice vendor and device
5267 number.&lt;/p&gt;
5268
5269 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5270 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5271
5272 &lt;p&gt;&lt;pre&gt;
5273 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5274 3rd Gen Core processor Graphics Controller [8086:0156] \
5275 (rev 09) (prog-if 00 [VGA controller])
5276 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5277 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5278 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5279 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5280 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5281 Latency: 0
5282 Interrupt: pin A routed to IRQ 42
5283 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5284 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5285 Region 4: I/O ports at 4000 [size=64]
5286 Expansion ROM at &lt;unassigned&gt; [disabled]
5287 Capabilities: &lt;access denied&gt;
5288 Kernel driver in use: i915
5289 &lt;/pre&gt;&lt;/p&gt;
5290
5291 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5292
5293 &lt;p&gt;&lt;pre&gt;
5294 struct intel_quirk intel_quirks[] = {
5295 ...
5296 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5297 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5298 ...
5299 }
5300 &lt;/pre&gt;&lt;/p&gt;
5301
5302 &lt;p&gt;According to the kernel module instructions (as seen using
5303 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5304 invert_brightness flag should be sent to the
5305 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5306 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5307 developers. But my email about the laptop sent 2013-06-03 have not
5308 yet shown up in
5309 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5310 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5311 emails from non-subscribers. Because of this, I sent my patch also to
5312 the Debian bug tracking system instead as
5313 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5314 sure the patch is not lost.&lt;/p&gt;
5315
5316 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5317 with this problem working properly with Linux. If you use Gnome, your
5318 worries should be over at this point. But if you use KDE, there is
5319 something in KDE ignoring the invert_brightness setting and turning on
5320 the screen during login. I&#39;ve reported it to Debian as
5321 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5322 have no idea yet how to figure out exactly what subsystem is doing
5323 this. Perhaps you can help? Perhaps you know what the Gnome
5324 developers did to handle this, and this can give a clue to the KDE
5325 developers? Or you know where in KDE the screen brightness is changed
5326 during login? If so, please update the BTS report (or get in touch if
5327 you do not know how to update BTS).&lt;/p&gt;
5328
5329 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5330 acpi_backlight=vendor, to disable ACPI backlight support completely,
5331 as the ACPI information on the machine is trash and it is better to
5332 leave it to the intel video driver to control the screen
5333 backlight.&lt;/p&gt;
5334 </description>
5335 </item>
5336
5337 <item>
5338 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5339 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5340 <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>
5341 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5342 <description>&lt;p&gt;Two days ago, I asked
5343 &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
5344 I could install Linux on a Packard Bell EasyNote LV computer
5345 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5346 with the obstacles put in the way of Linux users on a laptop with UEFI
5347 and Windows 8.&lt;/p&gt;
5348
5349 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5350 secure booting or fast boot. I suspect fast boot was the problem,
5351 causing the firmware to boot directly from HD without considering any
5352 key presses and alternative devices, but do not know UEFI settings
5353 enough to tell.&lt;/p&gt;
5354
5355 &lt;p&gt;There is no way to install Linux on the machine in question without
5356 opening the box and disconnecting the hard drive! This is as far as I
5357 can tell, the only way to get access to the firmware setup menu
5358 without accepting the Windows 8 license agreement. I am told (and
5359 found description on how to) that it is possible to configure the
5360 firmware setup once booted into Windows 8. But as I believe the terms
5361 of that agreement are completely unacceptable, accepting the license
5362 was never an alternative. I do not enter agreements I do not intend
5363 to follow.&lt;/p&gt;
5364
5365 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
5366 waste many hours on this, but luckily there was a way to get it to
5367 work. But I would not recommend it to anyone planning to run Linux on
5368 it, and I have become sceptical to Windows 8 certified laptops. Is
5369 this the way Linux will be forced out of the market place, by making
5370 it close to impossible for &quot;normal&quot; users to install Linux without
5371 accepting the Microsoft Windows license terms? Or at least not
5372 without risking to loose the warranty?&lt;/p&gt;
5373
5374 &lt;p&gt;I&#39;ve updated the
5375 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
5376 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
5377 do not have to struggle as much as I did to get Linux into the
5378 machine.&lt;/p&gt;
5379
5380 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5381 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
5382 </description>
5383 </item>
5384
5385 <item>
5386 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
5387 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
5388 <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>
5389 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
5390 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
5391 new laptops for my parents and a few others. I bought Packard Bell
5392 Easynote LV to run Kubuntu on and use as their home computer. But I
5393 am completely unable to figure out how to install Linux on it. The
5394 computer is preinstalled with Windows 8, and I suspect it uses UEFI
5395 instead of a BIOS to boot.&lt;/p&gt;
5396
5397 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
5398 to get it to boot the Linux installer from my USB stick. I have yet
5399 to try the DVD install, and still hope it will work. when I turn on
5400 the computer, there is no information on what buttons to press to get
5401 the normal boot menu. I expect to get some boot menu to select PXE or
5402 USB stick booting. When booting, it first ask for the language to
5403 use, then for some regional settings, and finally if I will accept the
5404 Windows 8 terms of use. As these terms are completely unacceptable to
5405 me, I have no other choice but to turn off the computer and try again
5406 to get it to boot the Linux installer.&lt;/p&gt;
5407
5408 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
5409 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5410 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
5411 installed on this machine, please get in touch or update that wiki
5412 page. If I can&#39;t find a way to install Linux, I will have to return
5413 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
5414
5415 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
5416 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
5417 on new Laptops?&lt;/p&gt;
5418 </description>
5419 </item>
5420
5421 <item>
5422 <title>How to transform a Debian based system to a Debian Edu installation</title>
5423 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
5424 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
5425 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
5426 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
5427 an operating system based on Debian intended for use in schools. It
5428 contain a turn-key solution for the computer network provided to
5429 pupils in the primary schools. It provide both the central server,
5430 network boot servers and desktop environments with heaps of
5431 educational software. The project was founded almost 12 years ago,
5432 2001-07-02. If you want to support the project, which is in need for
5433 cash to fund developer gatherings and other project related activity,
5434 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
5435 donate some money&lt;/a&gt;.
5436
5437 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
5438 lists and elsewhere, is the question on how to transform a Debian or
5439 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
5440 hard, and last week I wrote a script to replicate the steps done by
5441 the Debian Edu installer.&lt;/p&gt;
5442
5443 &lt;p&gt;The script,
5444 &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;
5445 in the debian-edu-config package, will go through these six steps and
5446 transform an existing Debian Wheezy or Ubuntu (untested) installation
5447 into a Debian Edu Workstation:&lt;/p&gt;
5448
5449 &lt;ol&gt;
5450
5451 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
5452 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
5453 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
5454 our configuration.&lt;/li&gt;
5455 &lt;li&gt;Preseed debconf database with profile setup in
5456 /etc/debian-edu/config, and run tasksel to install packages
5457 according to the profile specified in the config above,
5458 overriding some of the Debian automation machinery.&lt;/li&gt;
5459 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
5460 that could not be done using preseeding.&lt;/li&gt;
5461 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
5462
5463 &lt;/ol&gt;
5464
5465 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
5466 replicated like this. Disk partitioning and LVM setup, for example.
5467 So this script just assume there is enough disk space to install all
5468 the needed packages.&lt;/p&gt;
5469
5470 &lt;p&gt;The script was created to help a Debian Edu student working on
5471 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
5472 Debian Edu client, and using it he can take the existing
5473 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
5474 transform it into a fully functioning Debian Edu Workstation (or
5475 Roaming Workstation, or whatever :).&lt;/p&gt;
5476
5477 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
5478 If a LXDE based Roaming workstation is wanted instead, modify the
5479 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
5480
5481 &lt;p&gt;&lt;pre&gt;
5482 PROFILE=&quot;Roaming-Workstation&quot;
5483 DESKTOP=&quot;lxde&quot;
5484 &lt;/pre&gt;&lt;/p&gt;
5485
5486 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
5487 the cloud, by starting with a virtual Debian installation at some
5488 virtual hosting service and setting up all the services on first
5489 boot.&lt;/p&gt;
5490 </description>
5491 </item>
5492
5493 <item>
5494 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
5495 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
5496 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
5497 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
5498 <description>&lt;P&gt;In January,
5499 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
5500 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
5501 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
5502 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
5503 marvellous construction system from Denmark. We also created
5504 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
5505 a place to take notes and write down our plans and hopes. And several
5506 people showed up to help. I was very happy to see the effect of my
5507 call. Since the small start, we have a debtags tag
5508 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
5509 tag for LEGO related packages, and now count 10 packages related to
5510 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
5511
5512 &lt;p&gt;&lt;table&gt;
5513 &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;
5514 &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;
5515 &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;
5516 &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;
5517 &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;
5518 &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;
5519 &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;
5520 &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;
5521 &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;
5522 &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;
5523 &lt;/table&gt;&lt;/p&gt;
5524
5525 &lt;p&gt;Some of these are available in Wheezy, and all but one are
5526 currently available in Jessie/testing. leocad is so far only
5527 available in experimental.&lt;/p&gt;
5528
5529 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
5530 adding the rest of the great free software tools available on Linux
5531 for LEGO designers.&lt;/p&gt;
5532 </description>
5533 </item>
5534
5535 <item>
5536 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
5537 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
5538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
5539 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
5540 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
5541 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
5542 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
5543 Debian release, and I expect to move my machines at home over to it fairly
5544 soon.&lt;/p&gt;
5545
5546 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
5547 in particular make me very happy to see included. The
5548 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
5549 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
5550 included for the first time. Alongside similar programs like
5551 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5552 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5553 it allow for visual programming where syntax errors can not happen,
5554 and a friendly programming environment for learning to control the
5555 computer. Scratch will also be included in the next release of Debian
5556 Edu.&lt;/a&gt;
5557
5558 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5559 Edu/Skolelinux release too. The
5560 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5561 alpha release&lt;/a&gt; went out last week, and the next should soon
5562 follow.&lt;p&gt;
5563 </description>
5564 </item>
5565
5566 <item>
5567 <title>Isenkram 0.2 finally in the Debian archive</title>
5568 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5569 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5570 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5571 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5572 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5573 for many months. I uploaded it to the Debian experimental suite
5574 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5575
5576 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5577 install to work with a pluggable hardware device. The suggestion pop
5578 up when the device is plugged in. For example if a Lego Mindstorm NXT
5579 is inserted, it will suggest to install the program needed to program
5580 the NXT controller. Give it a go, and report bugs and suggestions to
5581 BTS. :)&lt;/p&gt;
5582 </description>
5583 </item>
5584
5585 <item>
5586 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5587 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5589 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5590 <description>&lt;p&gt;My
5591 &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
5592 bitcoin related blog post&lt;/a&gt; mentioned that the new
5593 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5594 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5595 2013-01-19, and have been available in unstable since then. It was
5596 automatically copied to Ubuntu, and is available in their Raring
5597 version too.&lt;/p&gt;
5598
5599 &lt;p&gt;But there is a strange problem with the build that block this new
5600 version from being available on the i386 and kfreebsd-i386
5601 architectures. For some strange reason, the autobuilders in Debian
5602 for these architectures fail to run the test suite on these
5603 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5604 We are so far unable to reproduce it when building it manually, and
5605 no-one have been able to propose a fix. If you got an idea what is
5606 failing, please let us know via the BTS.&lt;/p&gt;
5607
5608 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5609 I often run low on disk space, is the fact that the client will exit
5610 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5611 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5612 it. :)&lt;/p&gt;
5613
5614 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5615 activities, please send Bitcoin donations to my address
5616 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5617 </description>
5618 </item>
5619
5620 <item>
5621 <title>Welcome to the world, Isenkram!</title>
5622 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5624 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5625 <description>&lt;p&gt;Yesterday, I
5626 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5627 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5628 pluggable hardware devices, which I
5629 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5630 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5631 up, and caused me to really want to to open up the development to more
5632 people. But before I did this, I want to come up with a sensible name
5633 for this project. Today I finally decided on a new name, and I have
5634 renamed the project from hw-support-handler to this new name. In the
5635 process, I moved the source to git and made it available as a
5636 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5637 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5638 To fetch and build the latest version of the source, use&lt;/p&gt;
5639
5640 &lt;pre&gt;
5641 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5642 cd isenkram &amp;&amp; git-buildpackage -us -uc
5643 &lt;/pre&gt;
5644
5645 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5646 want to hack on the source or improve the package, please go ahead.
5647 But please talk to me first on IRC or via email before you do major
5648 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5649
5650 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5651 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5652 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5653 the German word eisenkram, for those that are familiar with that
5654 word.&lt;/p&gt;
5655
5656 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5657 instructions, to avoid confusing people with an error from the signing
5658 process.&lt;/p&gt;
5659
5660 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5661 clone argument to avoid the need for authentication.&lt;/p&gt;
5662 </description>
5663 </item>
5664
5665 <item>
5666 <title>First prototype ready making hardware easier to use in Debian</title>
5667 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5668 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5669 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5670 <description>&lt;p&gt;Early this month I set out to try to
5671 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5672 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5673 prototype is working, and it is ready for a larger audience. To test
5674 it, fetch the
5675 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5676 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5677 package. You might have to log out and in again activate the
5678 autostart script.&lt;/p&gt;
5679
5680 &lt;p&gt;The design is simple:&lt;/p&gt;
5681
5682 &lt;ul&gt;
5683
5684 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5685 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5686
5687 &lt;li&gt;This program listen for kernel events about new hardware (directly
5688 from the kernel like udev does), not using HAL dbus events as I
5689 initially did.&lt;/li&gt;
5690
5691 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5692 the APT database, a database
5693 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5694 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5695
5696 &lt;li&gt;If a package is mapped to the hardware in question, the package
5697 isn&#39;t installed yet and this is the first time the hardware was
5698 plugged in, show a desktop notification suggesting to install the
5699 package or packages.&lt;/li&gt;
5700
5701 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5702 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5703
5704 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5705 package while showing progress information in a window.&lt;/li&gt;
5706
5707 &lt;/ul&gt;
5708
5709 &lt;p&gt;I still need to come up with a better name for the system. Here
5710 are some screen shots showing the prototype in action. First the
5711 notification, then the password request, and finally the request to
5712 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5713
5714 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5715 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5716 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5717 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5718 &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;
5719
5720 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5721 is already useful. The database of hardware to package mappings also
5722 need more work. It is currently compatible with the Ubuntu way of
5723 storing such information in the package control file, but could be
5724 changed to use other formats instead or in addition to the current
5725 method. I&#39;ve dropped the use of discover for this mapping, as the
5726 modalias approach is more flexible and easier to use on Linux as long
5727 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5728
5729 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5730 here is the command required to check out and build the source: Use
5731 &#39;&lt;tt&gt;svn checkout
5732 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5733 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5734 devscripts package.&lt;/p&gt;
5735
5736 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5737 renamed to Isenkram and the source moved from the Debian Edu
5738 subversion repository to a Debian collab-maint git repository. See
5739 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5740 instructions&lt;/a&gt; for details.&lt;/p&gt;
5741 </description>
5742 </item>
5743
5744 <item>
5745 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5746 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5748 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5749 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5750 suddenly in bed. With a quiet whimper, it went completely quiet and
5751 black. The power button was no longer able to turn it on. It was a
5752 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5753 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5754 Compaq I had before that. Now I need to find a replacement. To keep
5755 going during Christmas, I moved the one year old SSD disk to my old
5756 X40 where it fitted (only one I had left that could use it), but it is
5757 not a durable solution.
5758
5759 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5760 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5761
5762 &lt;ul&gt;
5763
5764 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5765 than A4).&lt;/li&gt;
5766 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5767 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5768 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5769 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5770 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5771 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5772 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5773 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5774 size).&lt;/li&gt;
5775 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5776 X.org packages.&lt;/li&gt;
5777 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5778 the time).
5779
5780 &lt;/ul&gt;
5781
5782 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
5783 list. The reason is simply that the specifications on laptops the
5784 last 10-15 years have been sufficient for my needs, and I have to look
5785 at other features to choose my laptop. But are there still made as
5786 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5787 robust, and Thinkpads seem to be heading in the wrong direction since
5788 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
5789 still be useful.&lt;/p&gt;
5790
5791 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
5792 external keyboard? I&#39;ll have to check the
5793 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
5794 well-supported laptops, or perhaps just buy one preinstalled from one
5795 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
5796 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
5797 </description>
5798 </item>
5799
5800 <item>
5801 <title>How to find a browser plugin supporting a given MIME type</title>
5802 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
5803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
5804 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
5805 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
5806 install to get support for a given MIME type. Thanks to
5807 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
5808 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
5809 Unfortunately, not very many packages provide the needed meta
5810 information, Anyway, here is a small script to look up all browser
5811 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
5812
5813 &lt;pre&gt;
5814 #!/usr/bin/python
5815 import sys
5816 import apt
5817 def pkgs_handling_mimetype(mimetype):
5818 cache = apt.Cache()
5819 cache.open(None)
5820 thepkgs = []
5821 for pkg in cache:
5822 version = pkg.candidate
5823 if version is None:
5824 version = pkg.installed
5825 if version is None:
5826 continue
5827 record = version.record
5828 if not record.has_key(&#39;Npp-MimeType&#39;):
5829 continue
5830 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
5831 for t in mime_types:
5832 t = t.rstrip().strip()
5833 if t == mimetype:
5834 thepkgs.append(pkg.name)
5835 return thepkgs
5836 mimetype = &quot;audio/ogg&quot;
5837 if 1 &lt; len(sys.argv):
5838 mimetype = sys.argv[1]
5839 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
5840 for pkg in pkgs_handling_mimetype(mimetype):
5841 print &quot; %s&quot; %pkg
5842 &lt;/pre&gt;
5843
5844 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
5845
5846 &lt;pre&gt;
5847 % ./apt-find-browserplug-for-mimetype
5848 Browser plugin packages supporting audio/ogg:
5849 gecko-mediaplayer
5850 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5851 Browser plugin packages supporting application/x-shockwave-flash:
5852 browser-plugin-gnash
5853 %
5854 &lt;/pre&gt;
5855
5856 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
5857 itself to query for plugins and propose to install the needed
5858 packages. It would be great if Debian supported such feature too. Is
5859 anyone working on adding it?&lt;/p&gt;
5860
5861 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
5862 request for icweasel support for this feature is
5863 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
5864 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
5865 of manpower and wish for a different design is the reason thus feature
5866 is not yet in iceweasel from Debian.&lt;/p&gt;
5867 </description>
5868 </item>
5869
5870 <item>
5871 <title>What is the most supported MIME type in Debian?</title>
5872 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
5873 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
5874 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
5875 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
5876 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
5877 proposal to make it possible for a Desktop application to propose to
5878 the user some package to install to gain support for a given MIME
5879 type, font, library etc. that is currently missing. With such
5880 mechanism in place, it would be possible for the desktop to
5881 automatically propose and install leocad if some LDraw file is
5882 downloaded by the browser.&lt;/p&gt;
5883
5884 &lt;p&gt;To get some idea about the current content of the archive, I decided
5885 to write a simple program to extract all .desktop files from the
5886 Debian archive and look up the claimed MIME support there. The result
5887 can be found on the
5888 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
5889 site&lt;/a&gt;. Using the collected information, it become possible to
5890 answer the question in the title. Here are the 20 most supported MIME
5891 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5892 The complete list is available from the link above.&lt;/p&gt;
5893
5894 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
5895
5896 &lt;pre&gt;
5897 count MIME type
5898 ----- -----------------------
5899 32 text/plain
5900 30 audio/mpeg
5901 29 image/png
5902 28 image/jpeg
5903 27 application/ogg
5904 26 audio/x-mp3
5905 25 image/tiff
5906 25 image/gif
5907 22 image/bmp
5908 22 audio/x-wav
5909 20 audio/x-flac
5910 19 audio/x-mpegurl
5911 18 video/x-ms-asf
5912 18 audio/x-musepack
5913 18 audio/x-mpeg
5914 18 application/x-ogg
5915 17 video/mpeg
5916 17 audio/x-scpls
5917 17 audio/ogg
5918 16 video/x-ms-wmv
5919 &lt;/pre&gt;
5920
5921 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
5922
5923 &lt;pre&gt;
5924 count MIME type
5925 ----- -----------------------
5926 33 text/plain
5927 32 image/png
5928 32 image/jpeg
5929 29 audio/mpeg
5930 27 image/gif
5931 26 image/tiff
5932 26 application/ogg
5933 25 audio/x-mp3
5934 22 image/bmp
5935 21 audio/x-wav
5936 19 audio/x-mpegurl
5937 19 audio/x-mpeg
5938 18 video/mpeg
5939 18 audio/x-scpls
5940 18 audio/x-flac
5941 18 application/x-ogg
5942 17 video/x-ms-asf
5943 17 text/html
5944 17 audio/x-musepack
5945 16 image/x-xbitmap
5946 &lt;/pre&gt;
5947
5948 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
5949
5950 &lt;pre&gt;
5951 count MIME type
5952 ----- -----------------------
5953 31 text/plain
5954 31 image/png
5955 31 image/jpeg
5956 29 audio/mpeg
5957 28 application/ogg
5958 27 image/gif
5959 26 image/tiff
5960 26 audio/x-mp3
5961 23 audio/x-wav
5962 22 image/bmp
5963 21 audio/x-flac
5964 20 audio/x-mpegurl
5965 19 audio/x-mpeg
5966 18 video/x-ms-asf
5967 18 video/mpeg
5968 18 audio/x-scpls
5969 18 application/x-ogg
5970 17 audio/x-musepack
5971 16 video/x-ms-wmv
5972 16 video/x-msvideo
5973 &lt;/pre&gt;
5974
5975 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
5976 information mentioned in DEP-11. I have not yet had time to look at
5977 it, but hope the PackageKit people in Debian are on top of these
5978 issues.&lt;/p&gt;
5979
5980 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
5981 discovering a typo in my script.&lt;/p&gt;
5982 </description>
5983 </item>
5984
5985 <item>
5986 <title>Using modalias info to find packages handling my hardware</title>
5987 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
5988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
5989 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
5990 <description>&lt;p&gt;Yesterday, I wrote about the
5991 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
5992 values provided by the Linux kernel&lt;/a&gt; following my hope for
5993 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
5994 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
5995 modalias values attached to package names can be used to map packages
5996 to hardware. This allow the system to look up and suggest relevant
5997 packages when I plug in some new hardware into my machine, and replace
5998 discover and discover-data as the database used to map hardware to
5999 packages.&lt;/p&gt;
6000
6001 &lt;p&gt;I create a modaliases file with entries like the following,
6002 containing package name, kernel module name (if relevant, otherwise
6003 the package name) and globs matching the relevant hardware
6004 modalias.&lt;/p&gt;
6005
6006 &lt;p&gt;&lt;blockquote&gt;
6007 Package: package-name
6008 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
6009 &lt;/blockquote&gt;&lt;/p&gt;
6010
6011 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
6012 for a given modalias value using this file.&lt;/p&gt;
6013
6014 &lt;p&gt;An entry like this would suggest the video and picture application
6015 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
6016
6017 &lt;p&gt;&lt;blockquote&gt;
6018 Package: cheese
6019 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
6020 &lt;/blockquote&gt;&lt;/p&gt;
6021
6022 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
6023 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
6024
6025 &lt;p&gt;&lt;blockquote&gt;
6026 Package: pcmciautils
6027 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6028 &lt;/blockquote&gt;&lt;/p&gt;
6029
6030 &lt;p&gt;An entry like this would suggest the package colorhug-client when
6031 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
6032
6033 &lt;p&gt;&lt;blockquote&gt;
6034 Package: colorhug-client
6035 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
6036 &lt;/blockquote&gt;&lt;/p&gt;
6037
6038 &lt;p&gt;I believe the format is compatible with the format of the Packages
6039 file in the Debian archive. Ubuntu already uses their Packages file
6040 to store their mappings from packages to hardware.&lt;/p&gt;
6041
6042 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
6043 announce the hardware it support in a way my prototype understand.
6044 This allow those publishing packages in an APT source outside the
6045 Debian archive as well as those backporting packages to make sure the
6046 hardware mapping are included in the package meta information. I&#39;ve
6047 tested such header in the pymissile package, and its modalias mapping
6048 is working as it should with my prototype. It even made it to Ubuntu
6049 Raring.&lt;/p&gt;
6050
6051 &lt;p&gt;To test if it was possible to look up supported hardware using only
6052 the shell tools available in the Debian installer, I wrote a shell
6053 implementation of the lookup code. The idea is to create files for
6054 each modalias and let the shell do the matching. Please check out and
6055 try the
6056 &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;
6057 shell script. It run without any extra dependencies and fetch the
6058 hardware mappings from the Debian archive and the subversion
6059 repository where I currently work on my prototype.&lt;/p&gt;
6060
6061 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
6062 install yubikey-personalization:&lt;/p&gt;
6063
6064 &lt;p&gt;&lt;blockquote&gt;
6065 % ./hw-support-lookup
6066 &lt;br&gt;yubikey-personalization
6067 &lt;br&gt;%
6068 &lt;/blockquote&gt;&lt;/p&gt;
6069
6070 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6071 propose to install the pcmciautils package:&lt;/p&gt;
6072
6073 &lt;p&gt;&lt;blockquote&gt;
6074 % ./hw-support-lookup
6075 &lt;br&gt;pcmciautils
6076 &lt;br&gt;%
6077 &lt;/blockquote&gt;&lt;/p&gt;
6078
6079 &lt;p&gt;If you know of any hardware-package mapping that should be added to
6080 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
6081 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
6082
6083 &lt;p&gt;It could be possible to generate several of the mappings between
6084 packages and hardware. One source would be to look at packages with
6085 kernel modules, ie packages with *.ko files in /lib/modules/, and
6086 extract their modalias information. Another would be to look at
6087 packages with udev rules, ie packages with files in
6088 /lib/udev/rules.d/, and extract their vendor/model information to
6089 generate a modalias matching rule. I have not tested any of these to
6090 see if it work.&lt;/p&gt;
6091
6092 &lt;p&gt;If you want to help implementing a system to let us propose what
6093 packages to install when new hardware is plugged into a Debian
6094 machine, please send me an email or talk to me on
6095 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6096 </description>
6097 </item>
6098
6099 <item>
6100 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
6101 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
6102 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
6103 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
6104 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
6105 information, to find the packages that support a given piece of
6106 hardware, I refreshed my memory regarding modalias values, and decided
6107 to document the details. Here are my findings so far, also available
6108 in
6109 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6110 Debian Edu subversion repository&lt;/a&gt;:
6111
6112 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
6113
6114 &lt;p&gt;This document try to explain what the different types of modalias
6115 values stands for. It is in part based on information from
6116 &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;,
6117 &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;,
6118 &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
6119 &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;.
6120
6121 &lt;p&gt;The modalias entries for a given Linux machine can be found using
6122 this shell script:&lt;/p&gt;
6123
6124 &lt;pre&gt;
6125 find /sys -name modalias -print0 | xargs -0 cat | sort -u
6126 &lt;/pre&gt;
6127
6128 &lt;p&gt;The supported modalias globs for a given kernel module can be found
6129 using modinfo:&lt;/p&gt;
6130
6131 &lt;pre&gt;
6132 % /sbin/modinfo psmouse | grep alias:
6133 alias: serio:ty05pr*id*ex*
6134 alias: serio:ty01pr*id*ex*
6135 %
6136 &lt;/pre&gt;
6137
6138 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
6139
6140 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
6141 Bridge memory controller:&lt;/p&gt;
6142
6143 &lt;p&gt;&lt;blockquote&gt;
6144 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6145 &lt;/blockquote&gt;&lt;/p&gt;
6146
6147 &lt;p&gt;This represent these values:&lt;/p&gt;
6148
6149 &lt;pre&gt;
6150 v 00008086 (vendor)
6151 d 00002770 (device)
6152 sv 00001028 (subvendor)
6153 sd 000001AD (subdevice)
6154 bc 06 (bus class)
6155 sc 00 (bus subclass)
6156 i 00 (interface)
6157 &lt;/pre&gt;
6158
6159 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
6160 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
6161 0600. The 0600 class is a host bridge. Other useful bus values are
6162 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
6163
6164 &lt;p&gt;Not sure how to figure out the interface value, nor what it
6165 means.&lt;/p&gt;
6166
6167 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
6168
6169 &lt;p&gt;Some typical USB entries can look like this. This is an internal
6170 USB hub in a laptop:&lt;/p&gt;
6171
6172 &lt;p&gt;&lt;blockquote&gt;
6173 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6174 &lt;/blockquote&gt;&lt;/p&gt;
6175
6176 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
6177
6178 &lt;pre&gt;
6179 v 1D6B (device vendor)
6180 p 0001 (device product)
6181 d 0206 (bcddevice)
6182 dc 09 (device class)
6183 dsc 00 (device subclass)
6184 dp 00 (device protocol)
6185 ic 09 (interface class)
6186 isc 00 (interface subclass)
6187 ip 00 (interface protocol)
6188 &lt;/pre&gt;
6189
6190 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
6191 class is in the interface class section. For a simple USB web camera,
6192 these alias entries show up:&lt;/p&gt;
6193
6194 &lt;p&gt;&lt;blockquote&gt;
6195 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6196 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6197 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6198 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6199 &lt;/blockquote&gt;&lt;/p&gt;
6200
6201 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
6202 camera), 0101 is audio control device and 0102 is audio streaming (aka
6203 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
6204
6205 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
6206
6207 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
6208 receiver in a Thinkpad X40:&lt;/p&gt;
6209
6210 &lt;p&gt;&lt;blockquote&gt;
6211 acpi:IBM0071:PNP0511:
6212 &lt;/blockquote&gt;&lt;/p&gt;
6213
6214 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
6215
6216 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
6217
6218 &lt;p&gt;The DMI table contain lots of information about the computer case
6219 and model. This is an entry for a IBM Thinkpad X40, fetched from
6220 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
6221
6222 &lt;p&gt;&lt;blockquote&gt;
6223 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6224 &lt;/blockquote&gt;&lt;/p&gt;
6225
6226 &lt;p&gt;The values present are&lt;/p&gt;
6227
6228 &lt;pre&gt;
6229 bvn IBM (BIOS vendor)
6230 bvr 1UETB6WW(1.66) (BIOS version)
6231 bd 06/15/2005 (BIOS date)
6232 svn IBM (system vendor)
6233 pn 2371H4G (product name)
6234 pvr ThinkPadX40 (product version)
6235 rvn IBM (board vendor)
6236 rn 2371H4G (board name)
6237 rvr NotAvailable (board version)
6238 cvn IBM (chassis vendor)
6239 ct 10 (chassis type)
6240 cvr NotAvailable (chassis version)
6241 &lt;/pre&gt;
6242
6243 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
6244 found in the dmidecode source:&lt;/p&gt;
6245
6246 &lt;pre&gt;
6247 3 Desktop
6248 4 Low Profile Desktop
6249 5 Pizza Box
6250 6 Mini Tower
6251 7 Tower
6252 8 Portable
6253 9 Laptop
6254 10 Notebook
6255 11 Hand Held
6256 12 Docking Station
6257 13 All In One
6258 14 Sub Notebook
6259 15 Space-saving
6260 16 Lunch Box
6261 17 Main Server Chassis
6262 18 Expansion Chassis
6263 19 Sub Chassis
6264 20 Bus Expansion Chassis
6265 21 Peripheral Chassis
6266 22 RAID Chassis
6267 23 Rack Mount Chassis
6268 24 Sealed-case PC
6269 25 Multi-system
6270 26 CompactPCI
6271 27 AdvancedTCA
6272 28 Blade
6273 29 Blade Enclosing
6274 &lt;/pre&gt;
6275
6276 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6277 table. For example my home server is a tower, but the DMI modalias
6278 claim it is a desktop.&lt;/p&gt;
6279
6280 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6281
6282 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6283 test machine:&lt;/p&gt;
6284
6285 &lt;p&gt;&lt;blockquote&gt;
6286 serio:ty01pr00id00ex00
6287 &lt;/blockquote&gt;&lt;/p&gt;
6288
6289 &lt;p&gt;The values present are&lt;/p&gt;
6290
6291 &lt;pre&gt;
6292 ty 01 (type)
6293 pr 00 (prototype)
6294 id 00 (id)
6295 ex 00 (extra)
6296 &lt;/pre&gt;
6297
6298 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6299 the valid values are.&lt;/p&gt;
6300
6301 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6302
6303 &lt;p&gt;There are heaps of other modalias subtypes according to
6304 file2alias.c. There is the rest of the list from that source: amba,
6305 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6306 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6307 vmbus, x86cpu and zorro. I did not spend time documenting all of
6308 these, as they do not seem relevant for my intended use with mapping
6309 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6310
6311 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6312
6313 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6314 one can use the following shell script:&lt;/p&gt;
6315
6316 &lt;pre&gt;
6317 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6318 echo &quot;$id&quot; ; \
6319 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6320 done
6321 &lt;/pre&gt;
6322
6323 &lt;p&gt;The output can look like this (only the first few entries as the
6324 list is very long on my test machine):&lt;/p&gt;
6325
6326 &lt;pre&gt;
6327 acpi:ACPI0003:
6328 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6329 acpi:device:
6330 FATAL: Module acpi:device: not found.
6331 acpi:IBM0068:
6332 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6333 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6334 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6335 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6336 acpi:IBM0071:PNP0511:
6337 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6338 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6339 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6340 [...]
6341 &lt;/pre&gt;
6342
6343 &lt;p&gt;If you want to help implementing a system to let us propose what
6344 packages to install when new hardware is plugged into a Debian
6345 machine, please send me an email or talk to me on
6346 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6347
6348 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6349 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6350 in /sys/ with space in them.&lt;/p&gt;
6351 </description>
6352 </item>
6353
6354 <item>
6355 <title>Moved the pymissile Debian packaging to collab-maint</title>
6356 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
6357 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
6358 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
6359 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
6360 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6361 Launcher and updated the Debian package
6362 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
6363 sure udev will fix the device permissions when it is plugged in. I
6364 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
6365 hopefully make the package be proposed by jockey in Ubuntu when a user
6366 plug in his rocket launcher. In the process I moved the source to a
6367 git repository under collab-maint, to make it easier for any DD to
6368 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
6369 is not very active, but the software still work for me even after five
6370 years of relative silence. The new git repository is not listed in
6371 the uploaded package yet, because I want to test the other changes a
6372 bit more before I upload the new version. If you want to check out
6373 the new version with a .desktop file included, visit the
6374 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
6375 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
6376 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
6377 </description>
6378 </item>
6379
6380 <item>
6381 <title>Lets make hardware dongles easier to use in Debian</title>
6382 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
6383 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
6384 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
6385 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
6386 general, is that there is a great package management system with the
6387 ability to automatically install software packages by downloading them
6388 from the distribution mirrors, but no way to get it to automatically
6389 install the packages I need to use the hardware I plug into my
6390 machine. Even if the package to use it is easily available from the
6391 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6392 suggest to automatically install the python-nxt, nbc and t2n packages
6393 I need to talk to it. When I plug in a Yubikey, it could propose the
6394 yubikey-personalization package. The information required to do this
6395 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
6396
6397 &lt;p&gt;Some years ago, I proposed to
6398 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
6399 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
6400 simple:
6401
6402 &lt;ul&gt;
6403
6404 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
6405 starting when a user log in.&lt;/li&gt;
6406
6407 &lt;li&gt;Set this program up to listen for kernel events emitted when new
6408 hardware is inserted into the computer.&lt;/li&gt;
6409
6410 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
6411 database mapping to packages, and take note of any non-installed
6412 packages.&lt;/li&gt;
6413
6414 &lt;li&gt;Show a message to the user proposing to install the discovered
6415 package, and make it easy to install it.&lt;/li&gt;
6416
6417 &lt;/ul&gt;
6418
6419 &lt;p&gt;I am not sure what the best way to implement this is, but my
6420 initial idea was to use dbus events to discover new hardware, the
6421 discover database to find packages and
6422 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
6423 packages.&lt;/p&gt;
6424
6425 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
6426 draft package is now checked into
6427 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6428 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
6429 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
6430 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6431 the relevant packages in Debian, and uploaded a new version
6432 2.2013.01.09 to unstable. I also discovered that the current
6433 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
6434 package in Debian no longer discovered any USB devices, because
6435 /proc/bus/usb/devices is no longer present. I ported it to use
6436 libusb as a fall back option to get it working. The fixed package
6437 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
6438 because of the freeze).&lt;/p&gt;
6439
6440 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
6441 desktop notification to show up (only once, the first time it is
6442 inserted):&lt;/p&gt;
6443
6444 &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;
6445
6446 &lt;p&gt;For this prototype to be really useful, some way to automatically
6447 install the proposed packages by pressing the &quot;Please install
6448 program(s)&quot; button should to be implemented.&lt;/p&gt;
6449
6450 &lt;p&gt;If this idea seem useful to you, and you want to help make it
6451 happen, please help me update the discover-data database with mappings
6452 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
6453 list the package you would like to have installed when a given
6454 hardware device is inserted into your computer, and report bugs using
6455 reportbug if it isn&#39;t. Or, if you know of a better way to provide
6456 such mapping, please let me know.&lt;/p&gt;
6457
6458 &lt;p&gt;This prototype need more work, and there are several questions that
6459 should be considered before it is ready for production use. Is dbus
6460 the correct way to detect new hardware? At the moment I look for HAL
6461 dbus events on the system bus, because that is the events I could see
6462 on my Debian Squeeze KDE desktop. Are there better events to use?
6463 How should the user be notified? Is the desktop notification
6464 mechanism the best option, or should the background daemon raise a
6465 popup instead? How should packages be installed? When should they
6466 not be installed?&lt;/p&gt;
6467
6468 &lt;p&gt;If you want to help getting such feature implemented in Debian,
6469 please send me an email. :)&lt;/p&gt;
6470 </description>
6471 </item>
6472
6473 <item>
6474 <title>New IRC channel for LEGO designers using Debian</title>
6475 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
6476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
6477 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
6478 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
6479 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
6480 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
6481 discovered I had to build all the tools myself because none were
6482 already in Debian Squeeze. If Debian support for LEGO is something
6483 you care about, please join me on the IRC channel
6484 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
6485 irc.debian.org). There is a lot that could be done to improve the
6486 Debian support for LEGO designers. For example both CAD software
6487 and Mindstorm compilers are missing. :)&lt;/p&gt;
6488
6489 &lt;p&gt;Update 2012-01-03: A
6490 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
6491 including links to Lego related packages is now available.&lt;/p&gt;
6492 </description>
6493 </item>
6494
6495 <item>
6496 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
6497 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
6498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
6499 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
6500 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
6501 year! I hope next year will prove to be a good year.&lt;/p&gt;
6502
6503 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
6504 decentralised &quot;currency&quot; that allow people to transfer bitcoins
6505 between each other with minimal overhead, is a very interesting
6506 experiment. And as I wrote a few days ago, the bitcoin situation in
6507 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
6508 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
6509 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
6510 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
6511 for one of the ftpmasters to approve the new bitcoin-qt package
6512 name.&lt;/p&gt;
6513
6514 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
6515 team in Debian, you can easily test the package in Debian Squeeze
6516 using the following steps to get a set of working packages:&lt;/p&gt;
6517
6518 &lt;blockquote&gt;&lt;pre&gt;
6519 git clone git://git.debian.org/git/collab-maint/bitcoin
6520 cd bitcoin
6521 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6522 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6523 &lt;/pre&gt;&lt;/blockquote&gt;
6524
6525 &lt;p&gt;You might have to install some build dependencies as well. The
6526 list of commands should give you two packages, bitcoind and
6527 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6528 client will download the complete set of bitcoin &quot;blocks&quot;, which need
6529 around 5.6 GiB of data on my machine at the moment. Make sure your
6530 ~/.bitcoin/ directory have lots of spare room if you want to download
6531 all the blocks. The client will warn if the disk is getting full, so
6532 there is not really a problem if you got too little room, but you will
6533 not be able to get all the features out of the client.&lt;/p&gt;
6534
6535 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6536 activities, please send Bitcoin donations to my address
6537 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6538 </description>
6539 </item>
6540
6541 <item>
6542 <title>A word on bitcoin support in Debian</title>
6543 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
6544 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
6545 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
6546 <description>&lt;p&gt;It has been a while since I wrote about
6547 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
6548 peer-to-peer based crypto-currency, and the reason is simply that I
6549 have been busy elsewhere. But two days ago, I started looking at the
6550 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
6551 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6552 is now maintained by a
6553 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6554 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6555 owe a huge thank you to all these team members. :)
6556 But I was sad to discover that the bitcoin client is missing in
6557 Wheezy. It is only available in Sid (and an outdated client from
6558 backports). The client had several RC bugs registered in BTS blocking
6559 it from entering testing. To try to help the team and improve the
6560 situation, I spent some time providing patches and triaging the bug
6561 reports. I also had a look at the bitcoin package available from Matt
6562 Corallo in a
6563 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6564 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6565 Debian package.&lt;/p&gt;
6566
6567 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6568 IRC, I pushed several patches into the collab-maint git repository to
6569 improve the package. It now contains fixes for the RC issues (not from
6570 me, but fixed by Scott Howard), build rules for a Qt GUI client
6571 package, konqueror support for the bitcoin: URI and bash completion
6572 setup. As I work on Debian Squeeze, I also created
6573 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6574 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6575 it and try to integrate it into the git repository before uploading a
6576 new version to unstable.
6577
6578 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6579 centralized control currently exercised in the monetary system. I
6580 find it completely unacceptable that the USA government is collecting
6581 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6582 that the major credit card companies can block legal money
6583 transactions to Wikileaks. But for bitcoin to succeed, more people
6584 need to use bitcoins, and more people need to accept bitcoins when
6585 they sell products and services. Improving the bitcoin support in
6586 Debian is a small step in the right direction, but not enough.
6587 Unfortunately the user experience when browsing the web and wanting to
6588 pay with bitcoin is still not very good. The bitcoin: URI is a step
6589 in the right direction, but need to work in most or every browser in
6590 use. Also the bitcoin-qt client is too heavy to fire up to do a
6591 quick transaction. I believe there are other clients available, but
6592 have not tested them.&lt;/p&gt;
6593
6594 &lt;p&gt;My
6595 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6596 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6597 I received 20.15 BTC so far on the address I provided in my blog two
6598 years ago, as can be
6599 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6600 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6601 donation. The blockexplorer service demonstrates quite well that
6602 bitcoin is not quite anonymous and untracked. :) I wonder if the
6603 number of users have gone up since then. If you use bitcoin and want
6604 to show your support of my activity, please send Bitcoin donations to
6605 the same address as last time,
6606 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6607 </description>
6608 </item>
6609
6610 <item>
6611 <title>Git repository for song book for Computer Scientists</title>
6612 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6614 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6615 <description>&lt;p&gt;As I
6616 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6617 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6618 years ago, and today I finally found time to create a public
6619 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6620 repository for the project&lt;/a&gt;.&lt;/p&gt;
6621
6622 &lt;p&gt;If you want to help out, please clone the source and submit patches
6623 to the HTML version. To generate the PDF and PostScript version,
6624 please use prince XML, or let me know about a useful free software
6625 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6626
6627 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6628 PostScript formats at
6629 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6630 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6631 </description>
6632 </item>
6633
6634 <item>
6635 <title>Gratulerer med 19-årsdagen, Debian!</title>
6636 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6637 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6638 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6639 <description>&lt;p&gt;I dag fyller
6640 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6641 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6642 si gratulerer med dagen, Debian!&lt;/p&gt;
6643 </description>
6644 </item>
6645
6646 <item>
6647 <title>Song book for Computer Scientists</title>
6648 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6649 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6650 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6651 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6652 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6653 collecting computer related songs for use at parties. The original
6654 version was written in LaTeX, but a few years ago I got help from
6655 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6656 while keeping the ability to create a nice book in PDF format. I have
6657 not had time to maintain the book for a while now, and guess I should
6658 put it up on some public version control repository where others can
6659 help me extend and update the book. If anyone is volunteering to help
6660 me with this, send me an email. Also let me know if there are songs
6661 missing in my book.&lt;/p&gt;
6662
6663 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6664 me today that I really should let all my readers share the joys of
6665 singing out load about programming, computers and computer networks.
6666 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6667 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6668 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6669 Computer Science Songbook&lt;/a&gt;.
6670 </description>
6671 </item>
6672
6673 <item>
6674 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6675 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6677 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6678 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6679 around 1000 at the moment. To be able to get help from the vendors
6680 when something go wrong, we want to keep the firmware on the servers
6681 up to date. If the firmware isn&#39;t the latest and greatest, the
6682 vendors typically refuse to start debugging any problems until the
6683 firmware is upgraded. So before every reboot, we want to upgrade the
6684 firmware, and we would really like everyone handling servers at the
6685 university to do this themselves when they plan to reboot a machine.
6686 For that to happen we at the unix server admin group need to provide
6687 the tools to do so.&lt;/p&gt;
6688
6689 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6690 fetch and install the latest firmware for the servers we got. Most of
6691 our hardware are from Dell and HP, so I have focused on these servers
6692 so far. This blog post is about the Dell part.&lt;/P&gt;
6693
6694 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6695 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6696 with firmware information for all 11th generation servers, listing
6697 which firmware should be used on a given model and where on the FTP
6698 site I can find it. Using a simple perl XML parser I can then
6699 download the shell scripts Dell provides to do firmware upgrades from
6700 within Linux and reboot when all the firmware is primed and ready to
6701 be activated on the first reboot.&lt;/p&gt;
6702
6703 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6704 Are there anyone working on similar tools for firmware upgrading all
6705 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6706
6707 &lt;p&gt;&lt;pre&gt;
6708 #!/usr/bin/perl
6709 use strict;
6710 use warnings;
6711 use File::Temp qw(tempdir);
6712 BEGIN {
6713 # Install needed RHEL packages if missing
6714 my %rhelmodules = (
6715 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6716 );
6717 for my $module (keys %rhelmodules) {
6718 eval &quot;use $module;&quot;;
6719 if ($@) {
6720 my $pkg = $rhelmodules{$module};
6721 system(&quot;yum install -y $pkg&quot;);
6722 eval &quot;use $module;&quot;;
6723 }
6724 }
6725 }
6726 my $errorsto = &#39;pere@hungry.com&#39;;
6727
6728 upgrade_dell();
6729
6730 exit 0;
6731
6732 sub run_firmware_script {
6733 my ($opts, $script) = @_;
6734 unless ($script) {
6735 print STDERR &quot;fail: missing script name\n&quot;;
6736 exit 1
6737 }
6738 print STDERR &quot;Running $script\n\n&quot;;
6739
6740 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6741 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6742 } else {
6743 print STDERR &quot;fail: firmware script returned error\n&quot;;
6744 }
6745 }
6746
6747 sub run_firmware_scripts {
6748 my ($opts, @dirs) = @_;
6749 # Run firmware packages
6750 for my $dir (@dirs) {
6751 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6752 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6753 while (my $s = readdir $dh) {
6754 next if $s =~ m/^\.\.?/;
6755 run_firmware_script($opts, &quot;$dir/$s&quot;);
6756 }
6757 closedir $dh;
6758 }
6759 }
6760
6761 sub download {
6762 my $url = shift;
6763 print STDERR &quot;info: Downloading $url\n&quot;;
6764 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6765 }
6766
6767 sub upgrade_dell {
6768 my @dirs;
6769 my $product = `dmidecode -s system-product-name`;
6770 chomp $product;
6771
6772 if ($product =~ m/PowerEdge/) {
6773
6774 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6775 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6776
6777 my $tmpdir = tempdir(
6778 CLEANUP =&gt; 1
6779 );
6780 chdir($tmpdir);
6781 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
6782 system(&#39;gunzip Catalog.xml.gz&#39;);
6783 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
6784 # -q is quiet, disabling interactivity and reducing console output
6785 my $fwopts = &quot;-q&quot;;
6786 if (@paths) {
6787 for my $url (@paths) {
6788 fetch_dell_fw($url);
6789 }
6790 run_firmware_scripts($fwopts, $tmpdir);
6791 } else {
6792 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6793 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6794 }
6795 chdir(&#39;/&#39;);
6796 } else {
6797 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
6798 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
6799 }
6800 }
6801
6802 sub fetch_dell_fw {
6803 my $path = shift;
6804 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
6805 download($url);
6806 }
6807
6808 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6809 # firmware packages to download from Dell. Only work for Linux
6810 # machines and 11th generation Dell servers.
6811 sub fetch_dell_fw_list {
6812 my $filename = shift;
6813
6814 my $product = `dmidecode -s system-product-name`;
6815 chomp $product;
6816 my ($mybrand, $mymodel) = split(/\s+/, $product);
6817
6818 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
6819
6820 my $xml = XMLin($filename);
6821 my @paths;
6822 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
6823 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
6824 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
6825 my $oscode;
6826 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
6827 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
6828 } else {
6829 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
6830 }
6831 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
6832 {
6833 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
6834 }
6835 }
6836 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
6837 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
6838
6839 # Drop application packages, only firmware and BIOS
6840 next if &#39;APAC&#39; eq $componenttype;
6841
6842 my $cpath = $component-&gt;{path};
6843 for my $path (@paths) {
6844 if ($cpath =~ m%/$path$%) {
6845 push(@paths, $cpath);
6846 }
6847 }
6848 }
6849 return @paths;
6850 }
6851 &lt;/pre&gt;
6852
6853 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
6854 it could work on other platforms with some tweaking. Anyone know a
6855 index like Catalog.xml is available from HP for HP servers? At the
6856 moment I maintain a similar list manually and it is quickly getting
6857 outdated.&lt;/p&gt;
6858 </description>
6859 </item>
6860
6861 <item>
6862 <title>How is booting into runlevel 1 different from single user boots?</title>
6863 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
6864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
6865 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
6866 <description>&lt;p&gt;Wouter Verhelst have some
6867 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
6868 comments and opinions&lt;/a&gt; on my blog post on
6869 &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
6870 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
6871 &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
6872 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
6873 small piece of his comment now, and though it best to address the
6874 misunderstanding he bring forward:&lt;/p&gt;
6875
6876 &lt;p&gt;&lt;blockquote&gt;
6877 Currently, a system admin has four options: [...] boot to a
6878 single-user system (by adding &#39;single&#39; to the kernel command line;
6879 this runs rcS and rc1 scripts)
6880 &lt;/blockquote&gt;&lt;/p&gt;
6881
6882 &lt;p&gt;This make me believe Wouter believe booting into single user mode
6883 and booting into runlevel 1 is the same. I am not surprised he
6884 believe this, because it would make sense and is a quite sensible
6885 thing to believe. But because the boot in Debian is slightly broken,
6886 runlevel 1 do not work properly and it isn&#39;t the same as single user
6887 mode. I&#39;ll try to explain what is actually happing, but it is a bit
6888 hard to explain.&lt;/p&gt;
6889
6890 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
6891 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
6892 executed in single user mode is sulogin. Single user mode is a boot
6893 state &quot;between&quot; the runlevels, and when booting into single user mode,
6894 only the scripts in /etc/rcS.d/ are executed before the init process
6895 enters the single user state. When switching to runlevel 1, the state
6896 is in fact not ending in runlevel 1, but it passes through runlevel 1
6897 and end up in the single user mode (see /etc/rc1.d/S03single, which
6898 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
6899 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
6900 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6901 mode).&lt;/p&gt;
6902
6903 &lt;p&gt;This summary might make it clearer. When booting for the first
6904 time into single user mode, the following commands are executed:
6905 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
6906 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
6907 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
6908 trying to continue after visiting single user mode. Not all services
6909 are started again as they should, causing the machine to end up in an
6910 unpredicatble state. This is why Debian admins recommend rebooting
6911 after visiting single user mode.&lt;/p&gt;
6912
6913 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
6914 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
6915 to runlevel 1, the services started from /etc/rcS.d/ are not properly
6916 stopped when passing through the scripts in /etc/rc1.d/, and not
6917 started again when switching away from runlevel 1 to the runlevels
6918 2-5. I believe the problem is best fixed by moving all the scripts
6919 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
6920 functioning single user mode during boot.&lt;/p&gt;
6921
6922 &lt;p&gt;I have spent several years investigating the Debian boot system,
6923 and discovered this problem a few years ago. I suspect it originates
6924 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
6925 </description>
6926 </item>
6927
6928 <item>
6929 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
6930 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
6931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
6932 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
6933 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
6934 are started from /etc/rcS.d/. In fact, there is a bite more of them
6935 than make sense, and this causes a few problems. What kind of
6936 problems, you might ask. There are at least two problems. The first
6937 is that it is not possible to recover a machine after switching to
6938 runlevel 1. One need to actually reboot to get the machine back to
6939 the expected state. The other is that single user boot will sometimes
6940 run into problems because some of the subsystems are activated before
6941 the root login is presented, causing problems when trying to recover a
6942 machine from a problem in that subsystem. A minor additional point is
6943 that moving more scripts out of rcS.d/ and into the other rc#.d/
6944 directories will increase the amount of scripts that can run in
6945 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
6946
6947 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
6948 scripts that _have_ to execute before the root login prompt is
6949 presented during a single user boot should go there. Everything else
6950 should go into the numeric runlevels. This means things like
6951 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6952 the numeric runlevels. Today in Debian, there are around 115 init.d
6953 scripts that are started from rcS.d/, and most of them should be moved
6954 out. Do your package have one of them? Please help us make single
6955 user and runlevel 1 better by moving it.&lt;/p&gt;
6956
6957 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
6958 etc. should still be started from rcS.d/, but there is for example no
6959 need to have the network enabled before the single user login prompt
6960 is presented.&lt;/p&gt;
6961
6962 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
6963 Debian systems working while scripts migrate and during upgrades, the
6964 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6965 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6966 and the next ones can only be moved when their dependencies have been
6967 moved first. This migration must be done sequentially while we ensure
6968 that the package system upgrade packages in the right order to keep
6969 the system state correct. This will require some coordination when it
6970 comes to network related packages, but most of the packages with
6971 scripts that should migrate do not have anything in rcS.d/ depending
6972 on them. Some packages have already been updated, like the sudo
6973 package, while others are still left to do. I wish I had time to work
6974 on this myself, but real live constrains make it unlikely that I will
6975 find time to push this forward.&lt;/p&gt;
6976 </description>
6977 </item>
6978
6979 <item>
6980 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
6981 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
6982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
6983 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
6984 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
6985 mentioned the issues I believe should be improved in Debian for its
6986 desktop to be useful for more people. The use case for this is my
6987 parents, which are currently running Kubuntu which solve the
6988 issues.&lt;/p&gt;
6989
6990 &lt;p&gt;I suspect these four missing features are not very hard to
6991 implement. After all, they are present in Ubuntu, so if we wanted to
6992 do this in Debian we would have a source.&lt;/p&gt;
6993
6994 &lt;ol&gt;
6995
6996 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
6997 are new packages available for upgrades, a icon in the KDE status bar
6998 indicate this, and clicking on it will activate the simple upgrade
6999 tool to handle it. I have no problem guiding both of my parents
7000 through the process over the phone. If a kernel reboot is required,
7001 this too is indicated by the status bars and the upgrade tool. Last
7002 time I checked, nothing with the same features was working in KDE in
7003 Debian.&lt;/li&gt;
7004
7005 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
7006 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
7007 currently have a handler for, it will ask the user if the system
7008 should search for a package that would add support for this MIME type,
7009 and if the user say yes, the APT sources will be searched for packages
7010 advertising the MIME type in their control file (visible in the
7011 Packages file in the APT archive). If one or more packages are found,
7012 it is a simple click of the mouse to add support for the missing mime
7013 type. If the package require the user to accept some non-free
7014 license, this is explained to the user. The entire process make it
7015 more clear to the user why something do not work in the browser, and
7016 make the chances higher for the user to blame the web page authors and
7017 not the browser for any missing features.&lt;/li&gt;
7018
7019 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
7020 handlers.&lt;/strong&gt; When the media players encounter a format or codec
7021 it is not supporting, a dialog pop up asking the user if the system
7022 should search for a package that would add support for it. This
7023 happen with things like MP3, Windows Media or H.264. The selection
7024 and installation procedure is very similar to the Firefox browser
7025 plugin handling. This is as far as I know implemented using a
7026 gstreamer hook. The end result is that the user easily get access to
7027 the codecs that are present from the APT archives available, while
7028 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
7029
7030 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
7031 displaying a text/plain file in my Debian browser, it will propose to
7032 start emacs to show it. If I remember correctly, when doing the same
7033 in Kunbutu it show the file as a text file in the browser. At least I
7034 know Opera will show text files within the browser. I much prefer the
7035 latter behaviour.&lt;/li&gt;
7036
7037 &lt;/ol&gt;
7038
7039 &lt;p&gt;There are other nice features as well, like the simplified suite
7040 upgrader, but given that I am the one mostly doing the dist-upgrade,
7041 it do not matter much.&lt;/p&gt;
7042
7043 &lt;p&gt;I really hope we could get these features in place for the next
7044 Debian release. It would require the coordinated effort of several
7045 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
7046 </description>
7047 </item>
7048
7049 <item>
7050 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
7051 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
7052 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
7053 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
7054 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
7055 site is build on Debian/Squeeze, and this platform was chosen because
7056 I am most familiar with Debian (being a Debian Developer for around 10
7057 years) because it is the latest stable Debian release which should get
7058 security support for a few years.&lt;/p&gt;
7059
7060 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
7061 that are missing in Debian at the moment. It would be great if these
7062 modules were added to the Debian archive, allowing anyone to set up
7063 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
7064 in their own country using only Debian packages. The list of modules
7065 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
7066 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
7067 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7068 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7069 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7070 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7071 easier in the future.&lt;/p&gt;
7072
7073 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
7074 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
7075 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
7076 with the responsibility of tracking security problems, which I really
7077 do not have time for.&lt;/p&gt;
7078 </description>
7079 </item>
7080
7081 <item>
7082 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
7083 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
7084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
7085 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
7086 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
7087 posts have been in Norwegian the last few weeks, so here is a short
7088 update in English.&lt;/p&gt;
7089
7090 &lt;p&gt;The kids still keep me too busy to get much free software work
7091 done, but I did manage to organise a project to get a Norwegian port
7092 of the British service
7093 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
7094 and it has been running for a month now. The entire project has been
7095 organised by me and two others. Around Christmas we gathered sponsors
7096 to fund the development work. In January I drafted a contract with
7097 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
7098 and in February the development took place. Most of it involved
7099 converting the source to use GPS coordinates instead of British
7100 easting/northing, and the resulting code should be a lot easier to get
7101 running in any country by now. The Norwegian
7102 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
7103 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
7104 source and the source for administrative borders in Norway, and
7105 support for this had to be added/fixed.&lt;/p&gt;
7106
7107 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
7108 polishing the system before we announced it March 7th. The system is
7109 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
7110 problem reports in a few weeks. Soon we hope to announce the Android
7111 and iPhone versions making it even easier to report problems with the
7112 public infrastructure.&lt;/p&gt;
7113
7114 &lt;p&gt;Perhaps something to consider for those of you in countries without
7115 such service?&lt;/p&gt;
7116 </description>
7117 </item>
7118
7119 <item>
7120 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
7121 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
7122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
7123 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
7124 <description>&lt;p&gt;The last few days I have looked at ways to track open security
7125 issues here at my work with the University of Oslo. My idea is that
7126 it should be possible to use the information about security issues
7127 available on the Internet, and check our locally
7128 maintained/distributed software against this information. It should
7129 allow us to verify that no known security issues are forgotten. The
7130 CVE database listing vulnerabilities seem like a great central point,
7131 and by using the package lists from Debian mapped to CVEs provided by
7132 the testing security team, I believed it should be possible to figure
7133 out which security holes were present in our free software
7134 collection.&lt;/p&gt;
7135
7136 &lt;p&gt;After reading up on the topic, it became obvious that the first
7137 building block is to be able to name software packages in a unique and
7138 consistent way across data sources. I considered several ways to do
7139 this, for example coming up with my own naming scheme like using URLs
7140 to project home pages or URLs to the Freshmeat entries, or using some
7141 existing naming scheme. And it seem like I am not the first one to
7142 come across this problem, as MITRE already proposed and implemented a
7143 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
7144 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
7145 software, hardware and other platform components. The CPE ids are
7146 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
7147 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
7148 issues for any CPE name. With this in place, all I need to do is to
7149 locate the CPE id for the software packages we use at the university.
7150 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
7151 NVD entry if a CVE for the package exist).&lt;/p&gt;
7152
7153 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
7154 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
7155 check out, one could look up
7156 &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
7157 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
7158 The most recent one is
7159 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
7160 and at the bottom of the NVD page for this vulnerability the complete
7161 list of affected versions is provided.&lt;/p&gt;
7162
7163 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
7164 for offline processing of issues. Using this dump, I&#39;ve written a
7165 small script taking a list of CPEs as input and list all CVEs
7166 affecting the packages represented by these CPEs. One give it CPEs
7167 with version numbers as specified above and get a list of open
7168 security issues out.&lt;/p&gt;
7169
7170 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
7171 information need to be high. For that to happen, I believe as many as
7172 possible need to use and contribute to the NVD database. I notice
7173 RHEL is providing
7174 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
7175 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
7176 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
7177
7178 &lt;p&gt;To get an idea about the quality for free software, I spent some
7179 time making it possible to compare the CVE database from Debian with
7180 the CVE database in NVD. The result look fairly good, but there are
7181 some inconsistencies in NVD (same software package having several
7182 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7183 Debian believe are affected by a CVE). Hope to find time to improve
7184 the quality of NVD, but that require being able to get in touch with
7185 someone maintaining it. So far my three emails with questions and
7186 corrections have not seen any reply, but I hope contact can be
7187 established soon.&lt;/p&gt;
7188
7189 &lt;p&gt;An interesting application for CPEs is cross platform package
7190 mapping. It would be useful to know which packages in for example
7191 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7192 this would be trivial if all linux distributions provided CPE entries
7193 for their packages.&lt;/p&gt;
7194 </description>
7195 </item>
7196
7197 <item>
7198 <title>Which module is loaded for a given PCI and USB device?</title>
7199 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
7200 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
7201 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
7202 <description>&lt;p&gt;In the
7203 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
7204 package in Debian, there is a script to report useful information
7205 about the running hardware for use when people report missing
7206 information. One part of this script that I find very useful when
7207 debugging hardware problems, is the part mapping loaded kernel module
7208 to the PCI device it claims. It allow me to quickly see if the kernel
7209 module I expect is driving the hardware I am struggling with. To see
7210 the output, make sure discover-data is installed and run
7211 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
7212 one of my machines like this:&lt;/p&gt;
7213
7214 &lt;pre&gt;
7215 loaded modules:
7216 10de:03eb i2c_nforce2
7217 10de:03f1 ohci_hcd
7218 10de:03f2 ehci_hcd
7219 10de:03f0 snd_hda_intel
7220 10de:03ec pata_amd
7221 10de:03f6 sata_nv
7222 1022:1103 k8temp
7223 109e:036e bttv
7224 109e:0878 snd_bt87x
7225 11ab:4364 sky2
7226 &lt;/pre&gt;
7227
7228 &lt;p&gt;The code in question look like this, slightly modified for
7229 readability and to drop the output to file descriptor 3:&lt;/p&gt;
7230
7231 &lt;pre&gt;
7232 if [ -d /sys/bus/pci/devices/ ] ; then
7233 echo loaded pci modules:
7234 (
7235 cd /sys/bus/pci/devices/
7236 for address in * ; do
7237 if [ -d &quot;$address/driver/module&quot; ] ; then
7238 module=`cd $address/driver/module ; pwd -P | xargs basename`
7239 if grep -q &quot;^$module &quot; /proc/modules ; then
7240 address=$(echo $address |sed s/0000://)
7241 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
7242 echo &quot;$id $module&quot;
7243 fi
7244 fi
7245 done
7246 )
7247 echo
7248 fi
7249 &lt;/pre&gt;
7250
7251 &lt;p&gt;Similar code could be used to extract USB device module
7252 mappings:&lt;/p&gt;
7253
7254 &lt;pre&gt;
7255 if [ -d /sys/bus/usb/devices/ ] ; then
7256 echo loaded usb modules:
7257 (
7258 cd /sys/bus/usb/devices/
7259 for address in * ; do
7260 if [ -d &quot;$address/driver/module&quot; ] ; then
7261 module=`cd $address/driver/module ; pwd -P | xargs basename`
7262 if grep -q &quot;^$module &quot; /proc/modules ; then
7263 address=$(echo $address |sed s/0000://)
7264 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7265 if [ &quot;$id&quot; ] ; then
7266 echo &quot;$id $module&quot;
7267 fi
7268 fi
7269 fi
7270 done
7271 )
7272 echo
7273 fi
7274 &lt;/pre&gt;
7275
7276 &lt;p&gt;This might perhaps be something to include in other tools as
7277 well.&lt;/p&gt;
7278 </description>
7279 </item>
7280
7281 <item>
7282 <title>How to test if a laptop is working with Linux</title>
7283 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7284 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7285 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7286 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7287 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7288 batch of computers will work with Linux. Every year for the last few
7289 years the university have organised shared bid of a few thousand
7290 computers, and this year HP won the bid. Two different desktops and
7291 five different laptops are on the list this year. We in the UNIX
7292 group want to know which one of these computers work well with RHEL
7293 and Ubuntu, the two Linux distributions we currently handle at the
7294 university.&lt;/p&gt;
7295
7296 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7297 perhaps inspire others to test hardware as well. To test, I PXE
7298 install the OS version of choice, and log in as my normal user and run
7299 a few applications and plug in selected pieces of hardware. When
7300 something fail, I make a note about this in the test matrix and move
7301 on. If I have some spare time I try to report the bug to the OS
7302 vendor, but as I only have the machines for a short time, I rarely
7303 have the time to do this for all the problems I find.&lt;/p&gt;
7304
7305 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7306 I perform on a new model.&lt;/p&gt;
7307
7308 &lt;ul&gt;
7309
7310 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7311 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7312 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7313
7314 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7315 installation, X.org is working.&lt;/li&gt;
7316
7317 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7318 package mesa-utils on Ubuntu) and writing down the frames per second
7319 reported by the program.&lt;/li&gt;
7320
7321 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7322 logging in, and if I can hear this the test is successful. If there
7323 are several audio exits on the machine, I try them all and check if
7324 the Gnome/KDE audio mixer can control where to send the sound. I
7325 normally test this by playing
7326 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7327 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7328
7329 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7330 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7331
7332 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7333 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7334
7335 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7336 picture from the v4l device show up.&lt;/li&gt;
7337
7338 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7339 any bluetooth devices are discovered. In my office, I normally see a
7340 few.&lt;/li&gt;
7341
7342 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7343 memory modules lying around, and stick them in and see if Gnome/KDE
7344 notice this.&lt;/li&gt;
7345
7346 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7347 special button work, and if the laptop continue to work after
7348 resume.&lt;/li&gt;
7349
7350 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7351 adjusting background light, switching on/off external video output,
7352 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7353 laptop to laptop, so I just write down which are working and which are
7354 not.&lt;/li&gt;
7355
7356 &lt;li&gt;Some laptops have smart card readers, finger print readers,
7357 acceleration sensors etc. I rarely test these, as I do not know how
7358 to quickly test if they are working or not, so I only document their
7359 existence.&lt;/li&gt;
7360
7361 &lt;/ul&gt;
7362
7363 &lt;p&gt;By now I suspect you are really curious what the test results are
7364 for the HP machines I am testing. I&#39;m not done yet, so I will report
7365 the test results later. For now I can report that HP 8100 Elite work
7366 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
7367 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
7368 can see, I have most machines left to test. One interesting
7369 observation is that Ubuntu Lucid has almost twice the frame rate than
7370 RHEL6 with glxgears. No idea why.&lt;/p&gt;
7371 </description>
7372 </item>
7373
7374 <item>
7375 <title>Some thoughts on BitCoins</title>
7376 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
7377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
7378 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
7379 <description>&lt;p&gt;As I continue to explore
7380 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
7381 what properties the system have, and how it will be affected by laws
7382 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
7383
7384 &lt;p&gt;One interesting thing to note is that since the transactions are
7385 verified using a peer to peer network, all details about a transaction
7386 is known to everyone. This means that if a BitCoin address has been
7387 published like I did with mine in my initial post about BitCoin, it is
7388 possible for everyone to see how many BitCoins have been transfered to
7389 that address. There is even a web service to look at the details for
7390 all transactions. There I can see that my address
7391 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
7392 have received 16.06 Bitcoin, the
7393 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
7394 address of Simon Phipps have received 181.97 BitCoin and the address
7395 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
7396 of EFF have received 2447.38 BitCoins so far. Thank you to each and
7397 every one of you that donated bitcoins to support my activity. The
7398 fact that anyone can see how much money was transfered to a given
7399 address make it more obvious why the BitCoin community recommend to
7400 generate and hand out a new address for each transaction. I&#39;m told
7401 there is no way to track which addresses belong to a given person or
7402 organisation without the person or organisation revealing it
7403 themselves, as Simon, EFF and I have done.&lt;/p&gt;
7404
7405 &lt;p&gt;In Norway, and in most other countries, there are laws and
7406 regulations limiting how much money one can transfer across the border
7407 without declaring it. There are money laundering, tax and accounting
7408 laws and regulations I would expect to apply to the use of BitCoin.
7409 If the Skolelinux foundation
7410 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
7411 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
7412 normal bank transfers like EFF is doing, how should this be accounted?
7413 Given that it is impossible to know if money can cross the border or
7414 not, should everything or nothing be declared? What exchange rate
7415 should be used when calculating taxes? Would receivers have to pay
7416 income tax if the foundation were to pay Skolelinux contributors in
7417 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
7418
7419 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
7420 accepted by a lot of users. It must be possible to get easy access to
7421 the currency (as a wage or using currency exchanges), and it must be
7422 easy to spend it. At the moment BitCoin seem fairly easy to get
7423 access to, but there are very few places to spend it. I am not really
7424 a regular user of any of the vendor types currently accepting BitCoin,
7425 so I wonder when my kind of shop would start accepting BitCoins. I
7426 would like to buy electronics, travels and subway tickets, not herbs
7427 and books. :) The currency is young, and this will improve over time
7428 if it become popular, but I suspect regular banks will start to lobby
7429 to get BitCoin declared illegal if it become popular. I&#39;m sure they
7430 will claim it is helping fund terrorism and money laundering (which
7431 probably would be true, as is any currency in existence), but I
7432 believe the problems should be solved elsewhere and not by blaming
7433 currencies.&lt;/p&gt;
7434
7435 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
7436 CPU intensive process that depend on a bit of luck as well (as one is
7437 competing against all the other miners currently spending CPU cycles
7438 to see which one get the next lump of cash). The &quot;winner&quot; get 50
7439 BitCoin when this happen. Yesterday I came across the obvious way to
7440 join forces to increase ones changes of getting at least some coins,
7441 by coordinating the work on mining BitCoins across several machines
7442 and people, and sharing the result if one is lucky and get the 50
7443 BitCoins. Check out
7444 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
7445 if this sounds interesting. I have not had time to try to set up a
7446 machine to participate there yet, but have seen that running on ones
7447 own for a few days have not yield any BitCoins througth mining
7448 yet.&lt;/p&gt;
7449
7450 &lt;p&gt;Update 2010-12-15: Found an &lt;a
7451 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
7452 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
7453 it was interesting to read. The arguments presented seem to be
7454 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
7455 </description>
7456 </item>
7457
7458 <item>
7459 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
7460 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
7461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
7462 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
7463 <description>&lt;p&gt;With this weeks lawless
7464 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
7465 attacks&lt;/a&gt; on Wikileak and
7466 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
7467 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
7468 not be trusted to handle money transactions.
7469 A blog post from
7470 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
7471 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
7472 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
7473 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
7474 some help from my friend to get it all running, and he even handed me
7475 some bitcoins to get started. I even donated a few bitcoins to Simon
7476 for helping me remember BitCoin.&lt;/p&gt;
7477
7478 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
7479 crypto-currency, decentralised and handled using peer-to-peer
7480 networks. It allows anonymous transactions and prohibits central
7481 control over the transactions, making it impossible for governments
7482 and companies alike to block donations and other transactions. The
7483 source is free software, and while the key dependency wxWidgets 2.9
7484 for the graphical user interface is missing in Debian, the command
7485 line client builds just fine. Hopefully Jonas
7486 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
7487 Debian&lt;/a&gt; soon.&lt;/p&gt;
7488
7489 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
7490 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
7491 bitcoins&lt;/a&gt; when selling services and goods, and there are even
7492 currency &quot;stock&quot; markets where the exchange rate is decided. There
7493 are not many users so far, but the concept seems promising. If you
7494 want to get started and lack a friend with any bitcoins to spare,
7495 you can even get
7496 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
7497 bitcoin at the time of writing). Use
7498 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
7499 on the current exchange rates.&lt;/p&gt;
7500
7501 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
7502 machines. If you want to support my activity, please send Bitcoin
7503 donations to the address
7504 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
7505 </description>
7506 </item>
7507
7508 <item>
7509 <title>Why isn&#39;t Debian Edu using VLC?</title>
7510 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
7511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
7512 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
7513 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
7514 presented, and the winner among the multimedia player were VLC.
7515 Personally, I like VLC, and it is my player of choice when I first try
7516 to play a video file or stream. Only if VLC fail will I drag out
7517 gmplayer to see if it can do better. The reason is mostly the failure
7518 model and trust. When VLC fail, it normally pop up a error message
7519 reporting the problem. When mplayer fail, it normally segfault or
7520 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
7521
7522 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
7523 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7524 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
7525 plugin to play web videos seamlessly, and the VLC browser plugin is
7526 not very good. For example, it lack in-line control buttons, so there
7527 is no way for the user to pause the video. Also, when I
7528 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
7529 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
7530 failed on several video pages where mplayer based plugins worked. If
7531 the browser plugin for VLC was as good as the gecko-mediaplayer
7532 package (which uses mplayer), we would switch.&lt;/P&gt;
7533
7534 &lt;p&gt;While VLC is a good player, its user interface is slightly
7535 annoying. The most annoying feature is its inconsistent use of
7536 keyboard shortcuts. When the player is in full screen mode, its
7537 shortcuts are different from when it is playing the video in a window.
7538 For example, space only work as pause when in full screen mode. I
7539 wish it had consisten shortcuts and that space also would work when in
7540 window mode. Another nice shortcut in gmplayer is [enter] to restart
7541 the current video. It is very nice when playing short videos from the
7542 web and want to restart it when new people arrive to have a look at
7543 what is going on.&lt;/p&gt;
7544 </description>
7545 </item>
7546
7547 <item>
7548 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
7549 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
7550 <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>
7551 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7552 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7553 upgrade testing of the
7554 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7555 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7556 This seem like a very good idea, so I adjusted by test scripts and
7557 can now present the updated result from today:&lt;/p&gt;
7558
7559 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7560
7561 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7562
7563 &lt;blockquote&gt;&lt;p&gt;
7564 apache2.2-bin
7565 aptdaemon
7566 baobab
7567 binfmt-support
7568 browser-plugin-gnash
7569 cheese-common
7570 cli-common
7571 cups-pk-helper
7572 dmz-cursor-theme
7573 empathy
7574 empathy-common
7575 freedesktop-sound-theme
7576 freeglut3
7577 gconf-defaults-service
7578 gdm-themes
7579 gedit-plugins
7580 geoclue
7581 geoclue-hostip
7582 geoclue-localnet
7583 geoclue-manual
7584 geoclue-yahoo
7585 gnash
7586 gnash-common
7587 gnome
7588 gnome-backgrounds
7589 gnome-cards-data
7590 gnome-codec-install
7591 gnome-core
7592 gnome-desktop-environment
7593 gnome-disk-utility
7594 gnome-screenshot
7595 gnome-search-tool
7596 gnome-session-canberra
7597 gnome-system-log
7598 gnome-themes-extras
7599 gnome-themes-more
7600 gnome-user-share
7601 gstreamer0.10-fluendo-mp3
7602 gstreamer0.10-tools
7603 gtk2-engines
7604 gtk2-engines-pixbuf
7605 gtk2-engines-smooth
7606 hamster-applet
7607 libapache2-mod-dnssd
7608 libapr1
7609 libaprutil1
7610 libaprutil1-dbd-sqlite3
7611 libaprutil1-ldap
7612 libart2.0-cil
7613 libboost-date-time1.42.0
7614 libboost-python1.42.0
7615 libboost-thread1.42.0
7616 libchamplain-0.4-0
7617 libchamplain-gtk-0.4-0
7618 libcheese-gtk18
7619 libclutter-gtk-0.10-0
7620 libcryptui0
7621 libdiscid0
7622 libelf1
7623 libepc-1.0-2
7624 libepc-common
7625 libepc-ui-1.0-2
7626 libfreerdp-plugins-standard
7627 libfreerdp0
7628 libgconf2.0-cil
7629 libgdata-common
7630 libgdata7
7631 libgdu-gtk0
7632 libgee2
7633 libgeoclue0
7634 libgexiv2-0
7635 libgif4
7636 libglade2.0-cil
7637 libglib2.0-cil
7638 libgmime2.4-cil
7639 libgnome-vfs2.0-cil
7640 libgnome2.24-cil
7641 libgnomepanel2.24-cil
7642 libgpod-common
7643 libgpod4
7644 libgtk2.0-cil
7645 libgtkglext1
7646 libgtksourceview2.0-common
7647 libmono-addins-gui0.2-cil
7648 libmono-addins0.2-cil
7649 libmono-cairo2.0-cil
7650 libmono-corlib2.0-cil
7651 libmono-i18n-west2.0-cil
7652 libmono-posix2.0-cil
7653 libmono-security2.0-cil
7654 libmono-sharpzip2.84-cil
7655 libmono-system2.0-cil
7656 libmtp8
7657 libmusicbrainz3-6
7658 libndesk-dbus-glib1.0-cil
7659 libndesk-dbus1.0-cil
7660 libopal3.6.8
7661 libpolkit-gtk-1-0
7662 libpt2.6.7
7663 libpython2.6
7664 librpm1
7665 librpmio1
7666 libsdl1.2debian
7667 libsrtp0
7668 libssh-4
7669 libtelepathy-farsight0
7670 libtelepathy-glib0
7671 libtidy-0.99-0
7672 media-player-info
7673 mesa-utils
7674 mono-2.0-gac
7675 mono-gac
7676 mono-runtime
7677 nautilus-sendto
7678 nautilus-sendto-empathy
7679 p7zip-full
7680 pkg-config
7681 python-aptdaemon
7682 python-aptdaemon-gtk
7683 python-axiom
7684 python-beautifulsoup
7685 python-bugbuddy
7686 python-clientform
7687 python-coherence
7688 python-configobj
7689 python-crypto
7690 python-cupshelpers
7691 python-elementtree
7692 python-epsilon
7693 python-evolution
7694 python-feedparser
7695 python-gdata
7696 python-gdbm
7697 python-gst0.10
7698 python-gtkglext1
7699 python-gtksourceview2
7700 python-httplib2
7701 python-louie
7702 python-mako
7703 python-markupsafe
7704 python-mechanize
7705 python-nevow
7706 python-notify
7707 python-opengl
7708 python-openssl
7709 python-pam
7710 python-pkg-resources
7711 python-pyasn1
7712 python-pysqlite2
7713 python-rdflib
7714 python-serial
7715 python-tagpy
7716 python-twisted-bin
7717 python-twisted-conch
7718 python-twisted-core
7719 python-twisted-web
7720 python-utidylib
7721 python-webkit
7722 python-xdg
7723 python-zope.interface
7724 remmina
7725 remmina-plugin-data
7726 remmina-plugin-rdp
7727 remmina-plugin-vnc
7728 rhythmbox-plugin-cdrecorder
7729 rhythmbox-plugins
7730 rpm-common
7731 rpm2cpio
7732 seahorse-plugins
7733 shotwell
7734 software-center
7735 system-config-printer-udev
7736 telepathy-gabble
7737 telepathy-mission-control-5
7738 telepathy-salut
7739 tomboy
7740 totem
7741 totem-coherence
7742 totem-mozilla
7743 totem-plugins
7744 transmission-common
7745 xdg-user-dirs
7746 xdg-user-dirs-gtk
7747 xserver-xephyr
7748 &lt;/p&gt;&lt;/blockquote&gt;
7749
7750 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7751
7752 &lt;blockquote&gt;&lt;p&gt;
7753 cheese
7754 ekiga
7755 eog
7756 epiphany-extensions
7757 evolution-exchange
7758 fast-user-switch-applet
7759 file-roller
7760 gcalctool
7761 gconf-editor
7762 gdm
7763 gedit
7764 gedit-common
7765 gnome-games
7766 gnome-games-data
7767 gnome-nettool
7768 gnome-system-tools
7769 gnome-themes
7770 gnuchess
7771 gucharmap
7772 guile-1.8-libs
7773 libavahi-ui0
7774 libdmx1
7775 libgalago3
7776 libgtk-vnc-1.0-0
7777 libgtksourceview2.0-0
7778 liblircclient0
7779 libsdl1.2debian-alsa
7780 libspeexdsp1
7781 libsvga1
7782 rhythmbox
7783 seahorse
7784 sound-juicer
7785 system-config-printer
7786 totem-common
7787 transmission-gtk
7788 vinagre
7789 vino
7790 &lt;/p&gt;&lt;/blockquote&gt;
7791
7792 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7793
7794 &lt;blockquote&gt;&lt;p&gt;
7795 gstreamer0.10-gnomevfs
7796 &lt;/p&gt;&lt;/blockquote&gt;
7797
7798 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7799
7800 &lt;blockquote&gt;&lt;p&gt;
7801 [nothing]
7802 &lt;/p&gt;&lt;/blockquote&gt;
7803
7804 &lt;p&gt;This is for KDE:&lt;/p&gt;
7805
7806 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7807
7808 &lt;blockquote&gt;&lt;p&gt;
7809 ksmserver
7810 &lt;/p&gt;&lt;/blockquote&gt;
7811
7812 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7813
7814 &lt;blockquote&gt;&lt;p&gt;
7815 kwin
7816 network-manager-kde
7817 &lt;/p&gt;&lt;/blockquote&gt;
7818
7819 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7820
7821 &lt;blockquote&gt;&lt;p&gt;
7822 arts
7823 dolphin
7824 freespacenotifier
7825 google-gadgets-gst
7826 google-gadgets-xul
7827 kappfinder
7828 kcalc
7829 kcharselect
7830 kde-core
7831 kde-plasma-desktop
7832 kde-standard
7833 kde-window-manager
7834 kdeartwork
7835 kdeartwork-emoticons
7836 kdeartwork-style
7837 kdeartwork-theme-icon
7838 kdebase
7839 kdebase-apps
7840 kdebase-workspace
7841 kdebase-workspace-bin
7842 kdebase-workspace-data
7843 kdeeject
7844 kdelibs
7845 kdeplasma-addons
7846 kdeutils
7847 kdewallpapers
7848 kdf
7849 kfloppy
7850 kgpg
7851 khelpcenter4
7852 kinfocenter
7853 konq-plugins-l10n
7854 konqueror-nsplugins
7855 kscreensaver
7856 kscreensaver-xsavers
7857 ktimer
7858 kwrite
7859 libgle3
7860 libkde4-ruby1.8
7861 libkonq5
7862 libkonq5-templates
7863 libnetpbm10
7864 libplasma-ruby
7865 libplasma-ruby1.8
7866 libqt4-ruby1.8
7867 marble-data
7868 marble-plugins
7869 netpbm
7870 nuvola-icon-theme
7871 plasma-dataengines-workspace
7872 plasma-desktop
7873 plasma-desktopthemes-artwork
7874 plasma-runners-addons
7875 plasma-scriptengine-googlegadgets
7876 plasma-scriptengine-python
7877 plasma-scriptengine-qedje
7878 plasma-scriptengine-ruby
7879 plasma-scriptengine-webkit
7880 plasma-scriptengines
7881 plasma-wallpapers-addons
7882 plasma-widget-folderview
7883 plasma-widget-networkmanagement
7884 ruby
7885 sweeper
7886 update-notifier-kde
7887 xscreensaver-data-extra
7888 xscreensaver-gl
7889 xscreensaver-gl-extra
7890 xscreensaver-screensaver-bsod
7891 &lt;/p&gt;&lt;/blockquote&gt;
7892
7893 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7894
7895 &lt;blockquote&gt;&lt;p&gt;
7896 ark
7897 google-gadgets-common
7898 google-gadgets-qt
7899 htdig
7900 kate
7901 kdebase-bin
7902 kdebase-data
7903 kdepasswd
7904 kfind
7905 klipper
7906 konq-plugins
7907 konqueror
7908 ksysguard
7909 ksysguardd
7910 libarchive1
7911 libcln6
7912 libeet1
7913 libeina-svn-06
7914 libggadget-1.0-0b
7915 libggadget-qt-1.0-0b
7916 libgps19
7917 libkdecorations4
7918 libkephal4
7919 libkonq4
7920 libkonqsidebarplugin4a
7921 libkscreensaver5
7922 libksgrd4
7923 libksignalplotter4
7924 libkunitconversion4
7925 libkwineffects1a
7926 libmarblewidget4
7927 libntrack-qt4-1
7928 libntrack0
7929 libplasma-geolocation-interface4
7930 libplasmaclock4a
7931 libplasmagenericshell4
7932 libprocesscore4a
7933 libprocessui4a
7934 libqalculate5
7935 libqedje0a
7936 libqtruby4shared2
7937 libqzion0a
7938 libruby1.8
7939 libscim8c2a
7940 libsmokekdecore4-3
7941 libsmokekdeui4-3
7942 libsmokekfile3
7943 libsmokekhtml3
7944 libsmokekio3
7945 libsmokeknewstuff2-3
7946 libsmokeknewstuff3-3
7947 libsmokekparts3
7948 libsmokektexteditor3
7949 libsmokekutils3
7950 libsmokenepomuk3
7951 libsmokephonon3
7952 libsmokeplasma3
7953 libsmokeqtcore4-3
7954 libsmokeqtdbus4-3
7955 libsmokeqtgui4-3
7956 libsmokeqtnetwork4-3
7957 libsmokeqtopengl4-3
7958 libsmokeqtscript4-3
7959 libsmokeqtsql4-3
7960 libsmokeqtsvg4-3
7961 libsmokeqttest4-3
7962 libsmokeqtuitools4-3
7963 libsmokeqtwebkit4-3
7964 libsmokeqtxml4-3
7965 libsmokesolid3
7966 libsmokesoprano3
7967 libtaskmanager4a
7968 libtidy-0.99-0
7969 libweather-ion4a
7970 libxklavier16
7971 libxxf86misc1
7972 okteta
7973 oxygencursors
7974 plasma-dataengines-addons
7975 plasma-scriptengine-superkaramba
7976 plasma-widget-lancelot
7977 plasma-widgets-addons
7978 plasma-widgets-workspace
7979 polkit-kde-1
7980 ruby1.8
7981 systemsettings
7982 update-notifier-common
7983 &lt;/p&gt;&lt;/blockquote&gt;
7984
7985 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
7986 aptitude a bit more similar, but there are still quite a lott of
7987 differences. I have no idea what packages should be installed after
7988 the upgrade, but hope those that do can have a look.&lt;/p&gt;
7989 </description>
7990 </item>
7991
7992 <item>
7993 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
7994 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
7995 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
7996 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
7997 <description>&lt;p&gt;Most of the computers in use by the
7998 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
7999 are virtual machines. And they have been Xen machines running on a
8000 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
8001 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
8002 bit harder that it could have been, because we set up the Xen virtual
8003 machines to get the virtual partitions from LVM, which as far as I
8004 know is not supported by KVM. So to migrate, we had to convert
8005 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
8006
8007 &lt;p&gt;I found
8008 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
8009 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
8010 migration. It uses qemu-img from the qemu package to make the disk
8011 image, parted to partition it, losetup and kpartx to present the disk
8012 image partions as devices, and dd to copy the data. I NFS mounted the
8013 new servers storage area on the old server to do the migration.&lt;/p&gt;
8014
8015 &lt;pre&gt;
8016 #!/bin/sh
8017
8018 # Based on
8019 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8020
8021 set -e
8022 set -x
8023
8024 if [ -z &quot;$1&quot; ] ; then
8025 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
8026 exit 1
8027 else
8028 host=&quot;$1&quot;
8029 fi
8030
8031 if [ ! -e /dev/vg_data/$host-disk ] ; then
8032 echo &quot;error: unable to find LVM volume for $host&quot;
8033 exit 1
8034 fi
8035
8036 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8037 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8038 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8039 totalsize=$(( ( $disksize + $swapsize ) ))
8040
8041 img=$host.img
8042 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
8043 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8044
8045 parted $img mklabel msdos
8046 parted $img mkpart primary linux-swap 0 $disksize
8047 parted $img mkpart primary ext2 $disksize $totalsize
8048 parted $img set 1 boot on
8049
8050 modprobe dm-mod
8051 losetup /dev/loop0 $img
8052 kpartx -a /dev/loop0
8053
8054 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
8055 fsck.ext3 -f /dev/mapper/loop0p1 || true
8056 mkswap /dev/mapper/loop0p2
8057
8058 kpartx -d /dev/loop0
8059 losetup -d /dev/loop0
8060 &lt;/pre&gt;
8061
8062 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
8063 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
8064
8065 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
8066 the new disk image attached, installed grub-pc and linux-image-686 and
8067 set up grub to boot from the disk image. After this, the KVM machines
8068 seem to work just fine.&lt;/p&gt;
8069 </description>
8070 </item>
8071
8072 <item>
8073 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
8074 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
8075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
8076 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
8077 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
8078 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8079 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
8080 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
8081
8082 &lt;p&gt;I still do not know what a correct migration should look like, so I
8083 report any differences between apt and aptitude and hope someone else
8084 can see if anything should be changed.&lt;/p&gt;
8085
8086 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8087
8088 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8089
8090 &lt;blockquote&gt;&lt;p&gt;
8091 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8092 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
8093 dmz-cursor-theme empathy empathy-common finger
8094 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8095 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8096 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8097 gnome-cards-data gnome-codec-install gnome-core
8098 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8099 gnome-search-tool gnome-session-canberra gnome-spell
8100 gnome-system-log gnome-themes-extras gnome-themes-more
8101 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8102 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8103 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8104 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8105 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
8106 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
8107 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
8108 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
8109 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
8110 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8111 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
8112 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8113 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8114 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8115 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8116 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8117 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8118 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8119 libmono-security2.0-cil libmono-sharpzip2.84-cil
8120 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
8121 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
8122 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
8123 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
8124 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
8125 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
8126 libxalan2-java libxerces2-java media-player-info mesa-utils
8127 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
8128 nautilus-sendto-empathy openoffice.org-writer2latex
8129 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
8130 python-aptdaemon python-aptdaemon-gtk python-axiom
8131 python-beautifulsoup python-bugbuddy python-clientform
8132 python-coherence python-configobj python-crypto python-cupshelpers
8133 python-cupsutils python-eggtrayicon python-elementtree
8134 python-epsilon python-evolution python-feedparser python-gdata
8135 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8136 python-gtksourceview2 python-httplib2 python-louie python-mako
8137 python-markupsafe python-mechanize python-nevow python-notify
8138 python-opengl python-openssl python-pam python-pkg-resources
8139 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8140 python-tagpy python-twisted-bin python-twisted-conch
8141 python-twisted-core python-twisted-web python-utidylib python-webkit
8142 python-xdg python-zope.interface remmina remmina-plugin-data
8143 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8144 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8145 software-center svgalibg1 system-config-printer-udev
8146 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
8147 totem totem-coherence totem-mozilla totem-plugins
8148 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8149 zip
8150 &lt;/p&gt;&lt;/blockquote&gt;
8151
8152 Installed using apt-get, removed with aptitude
8153
8154 &lt;blockquote&gt;&lt;p&gt;
8155 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8156 epiphany-extensions epiphany-gecko evolution-exchange
8157 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8158 gedit-common gnome-app-install gnome-games gnome-games-data
8159 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8160 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8161 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8162 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
8163 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
8164 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
8165 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
8166 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8167 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8168 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8169 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
8170 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
8171 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8172 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8173 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8174 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8175 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
8176 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
8177 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
8178 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
8179 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
8180 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8181 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8182 sound-juicer swfdec-gnome system-config-printer totem-common
8183 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8184 &lt;/p&gt;&lt;/blockquote&gt;
8185
8186 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8187
8188 &lt;blockquote&gt;&lt;p&gt;
8189 gstreamer0.10-gnomevfs
8190 &lt;/p&gt;&lt;/blockquote&gt;
8191
8192 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8193
8194 &lt;blockquote&gt;&lt;p&gt;
8195 [nothing]
8196 &lt;/p&gt;&lt;/blockquote&gt;
8197
8198 &lt;p&gt;This is for KDE:&lt;/p&gt;
8199
8200 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8201
8202 &lt;blockquote&gt;&lt;p&gt;
8203 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
8204 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8205 ghostscript-x git gnome-audio gnugo granatier gs-common
8206 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8207 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8208 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8209 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8210 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8211 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8212 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8213 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8214 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8215 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8216 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8217 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
8218 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8219 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8220 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8221 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8222 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8223 libkrossui4 libmailtools-perl libmime-tools-perl
8224 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8225 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8226 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8227 lirc luatex marble networkstatus noatun-plugins
8228 openoffice.org-writer2latex palapeli palapeli-data parley
8229 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8230 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8231 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8232 ttf-sazanami-gothic
8233 &lt;/p&gt;&lt;/blockquote&gt;
8234
8235 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8236
8237 &lt;blockquote&gt;&lt;p&gt;
8238 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8239 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8240 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8241 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8242 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8243 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8244 kitchensync kiten kjumpingcube klatin klettres klickety klines
8245 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8246 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8247 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8248 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8249 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8250 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8251 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8252 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8253 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8254 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8255 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8256 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8257 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8258 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8259 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8260 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8261 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8262 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8263 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8264 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8265 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8266 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8267 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8268 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8269 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8270 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8271 &lt;/p&gt;&lt;/blockquote&gt;
8272
8273 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8274
8275 &lt;blockquote&gt;&lt;p&gt;
8276 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8277 kdeartwork kdebase kdebase-apps kdebase-workspace
8278 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8279 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8280 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8281 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8282 xscreensaver-screensaver-bsod
8283 &lt;/p&gt;&lt;/blockquote&gt;
8284
8285 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8286
8287 &lt;blockquote&gt;&lt;p&gt;
8288 kdebase-bin konq-plugins konqueror
8289 &lt;/p&gt;&lt;/blockquote&gt;
8290 </description>
8291 </item>
8292
8293 <item>
8294 <title>Gnash buildbot slave and Debian kfreebsd</title>
8295 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8297 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8298 <description>&lt;p&gt;Answering
8299 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8300 call from the Gnash project&lt;/a&gt; for
8301 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8302 current source, I have set up a virtual KVM machine on the Debian
8303 Edu/Skolelinux virtualization host to test the git source on
8304 Debian/Squeeze. I hope this can help the developers in getting new
8305 releases out more often.&lt;/p&gt;
8306
8307 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8308 I have considered setting up a &lt;a
8309 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8310 machine as well. I have also considered using the kfreebsd
8311 architecture in Debian as a file server in NUUG to get access to the 5
8312 TB zfs volume we currently use to store DV video. Because of this, I
8313 finally got around to do a test installation of Debian/Squeeze with
8314 kfreebsd. Installation went fairly smooth, thought I noticed some
8315 visual glitches in the cdebconf dialogs (black cursor left on the
8316 screen at random locations). Have not gotten very far with the
8317 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8318 fatal problem. Have to spend some more time on it to see if it is
8319 useful as a file server for NUUG. Will try to find time to set up a
8320 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8321 </description>
8322 </item>
8323
8324 <item>
8325 <title>Debian in 3D</title>
8326 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8327 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8328 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8329 <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;
8330
8331 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8332 3D linked in from
8333 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8334 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8335 </description>
8336 </item>
8337
8338 <item>
8339 <title>Software updates 2010-10-24</title>
8340 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8341 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8342 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8343 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8344
8345 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8346 raise money for the project is going well. The lower limit of 10
8347 signers was reached in 24 hours, and so far 13 people have signed it.
8348 More signers and more funding is most welcome, and I am really curious
8349 how far we can get before the time limit of December 24 is reached.
8350 :)&lt;/p&gt;
8351
8352 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
8353 about what appear to be a great code coverage tool capable of
8354 generating code coverage stats without any changes to the source code.
8355 It is called
8356 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
8357 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
8358 It is missing in Debian, but the git source built just fine in Squeeze
8359 after I installed libelf-dev, libdwarf-dev, pkg-config and
8360 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8361 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
8362
8363 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
8364 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
8365 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
8366 alpha test release of the Squeeze based Debian Edu /
8367 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
8368 release. Give it a try if you need a complete linux solution for your
8369 school, including central infrastructure server, workstations, thin
8370 client servers and diskless workstations. A nice touch added
8371 yesterday is RDP support on the thin client servers, for windows
8372 clients to get a Linux desktop on request.&lt;/p&gt;
8373 </description>
8374 </item>
8375
8376 <item>
8377 <title>Some notes on Flash in Debian and Debian Edu</title>
8378 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
8379 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
8380 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
8381 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
8382 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
8383 second most popular used package that is missing in Debian. The sixth
8384 most popular is flashplayer-mozilla. This is a clear indication that
8385 working flash is important for Debian users. Around 10 percent of the
8386 users submitting data to popcon.debian.org have this package
8387 installed.&lt;/p&gt;
8388
8389 &lt;p&gt;In the report written by Lars Risan in August 2008
8390&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
8391 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8392 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
8393 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8394 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
8395 web sites require Flash to work, and lacking working Flash support in
8396 the web browser and the problems with installing it was perceived as a
8397 good reason to stay with Windows.&lt;/p&gt;
8398
8399 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
8400 said to be the retarded cousin that did not really understand
8401 everything you told him but could work fairly well. This was a
8402 comment regarding the problems Linux have with proprietary formats and
8403 non-standard web pages, and is sad because it exposes a fairly common
8404 understanding of whose fault it is if web pages that only work in for
8405 example Internet Explorer 6 fail to work on Firefox, and funny because
8406 it explain very well how annoying it is for users when Linux
8407 distributions do not work with the documents they receive or the web
8408 pages they want to visit.&lt;/p&gt;
8409
8410 &lt;p&gt;This is part of the reason why I believe it is important for Debian
8411 and Debian Edu to have a well working Flash implementation in the
8412 distribution, to get at least popular sites as Youtube and Google
8413 Video to working out of the box. For Squeeze, Debian have the chance
8414 to include the latest version of Gnash that will make this happen, as
8415 the new release 0.8.8 was published a few weeks ago and is resting in
8416 unstable. The new version work with more sites that version 0.8.7.
8417 The Gnash maintainers have asked for a freeze exception, but the
8418 release team have not had time to reply to it yet. I hope they agree
8419 with me that Flash is important for the Debian desktop users, and thus
8420 accept the new package into Squeeze.&lt;/p&gt;
8421 </description>
8422 </item>
8423
8424 <item>
8425 <title>Circular package dependencies harms apt recovery</title>
8426 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
8427 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
8428 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
8429 <description>&lt;p&gt;I discovered this while doing
8430 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
8431 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
8432 in Debian still got circular dependencies, and it is often claimed
8433 that apt and aptitude should be able to handle this just fine, but
8434 some times these dependency loops causes apt to fail.&lt;/p&gt;
8435
8436 &lt;p&gt;An example is from todays
8437 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
8438 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
8439 causes perl-modules to fail to upgrade. The cause is simple. If a
8440 package fail to unpack, then only part of packages with the circular
8441 dependency might end up being unpacked when unpacking aborts, and the
8442 ones already unpacked will fail to configure in the recovery phase
8443 because its dependencies are unavailable.&lt;/p&gt;
8444
8445 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
8446
8447 &lt;blockquote&gt;&lt;pre&gt;
8448 dpkg: dependency problems prevent configuration of perl-modules:
8449 perl-modules depends on perl (&gt;= 5.10.1-1); however:
8450 Version of perl on system is 5.10.0-19lenny2.
8451 dpkg: error processing perl-modules (--configure):
8452 dependency problems - leaving unconfigured
8453 &lt;/pre&gt;&lt;/blockquote&gt;
8454
8455 &lt;p&gt;The perl/perl-modules circular dependency is already
8456 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
8457 hopefully be solved as soon as possible, but it is not the only one,
8458 and each one of these loops in the dependency tree can cause similar
8459 failures. Of course, they only occur when there are bugs in other
8460 packages causing the unpacking to fail, but it is rather nasty when
8461 the failure of one package causes the problem to become worse because
8462 of dependency loops.&lt;/p&gt;
8463
8464 &lt;p&gt;Thanks to
8465 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
8466 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
8467 dependencies
8468 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
8469 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
8470
8471 &lt;p&gt;Todays testing also exposed a bug in
8472 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
8473 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
8474 apt-get and aptitude, the latter possibly caused by some circular
8475 dependency. Reported both to BTS to try to get someone to look at
8476 it.&lt;/p&gt;
8477 </description>
8478 </item>
8479
8480 <item>
8481 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
8482 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
8483 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
8484 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
8485 <description>&lt;p&gt;This is a
8486 &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;
8487 on my
8488 &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
8489 work&lt;/a&gt; on
8490 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
8491 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
8492
8493 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
8494 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8495 and dhcp3-server-ldap in Debian use the LDAP server. The two
8496 implementations are quite different in how they use LDAP.&lt;/p&gt;
8497
8498 To get this information, I started slapd with debugging enabled and
8499 dumped the debug output to a file to get the LDAP searches performed
8500 on a Debian Edu main-server. Here is a summary.
8501
8502 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
8503
8504 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
8505 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
8506 the web.
8507
8508 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
8509 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
8510 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
8511 reverse entries are in two different subtrees in LDAP with a structure
8512 based on the DNS names, as in tjener.intern and
8513 2.2.0.10.in-addr.arpa.&lt;/p&gt;
8514
8515 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
8516 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
8517 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
8518 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
8519 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
8520 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
8521 forward entries, it is looking for attributes named dnsttl, arecord,
8522 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8523 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8524 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8525 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8526 spfrecord and modifytimestamp. For reverse entries it is looking for
8527 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8528 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8529 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8530 ldapsearch commands could look like this:&lt;/p&gt;
8531
8532 &lt;blockquote&gt;&lt;pre&gt;
8533 ldapsearch -h ldap \
8534 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8535 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8536 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8537 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8538 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8539 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8540
8541 ldapsearch -h ldap \
8542 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8543 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
8544 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8545 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8546 srvrecord naptrrecord modifytimestamp
8547 &lt;/pre&gt;&lt;/blockquote&gt;
8548
8549 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
8550 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8551 example LDAP objects used there. In addition to these objects, the
8552 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8553 also exist.&lt;/p&gt;
8554
8555 &lt;blockquote&gt;&lt;pre&gt;
8556 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8557 objectclass: top
8558 objectclass: dnsdomain
8559 objectclass: domainrelatedobject
8560 dc: tjener
8561 arecord: 10.0.2.2
8562 associateddomain: tjener.intern
8563
8564 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8565 objectclass: top
8566 objectclass: dnsdomain2
8567 objectclass: domainrelatedobject
8568 dc: 2
8569 ptrrecord: tjener.intern
8570 associateddomain: 2.2.0.10.in-addr.arpa
8571 &lt;/pre&gt;&lt;/blockquote&gt;
8572
8573 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8574 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8575 same base as in the tree mode for a object with filter
8576 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8577 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8578 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8579 naptrrecord and modifytimestamp. For reverse entires it also do a
8580 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8581 and the requested attributes are associateddomain, dnsttl and
8582 modifytimestamp. In short, in strict mode the objects with ptrrecord
8583 go away, and the arecord attribute in the forward object is used
8584 instead.&lt;/p&gt;
8585
8586 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8587 like this:&lt;/p&gt;
8588
8589 &lt;blockquote&gt;&lt;pre&gt;
8590 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8591 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8592 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8593 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8594 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8595 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8596
8597 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8598 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8599 &lt;/pre&gt;&lt;/blockquote&gt;
8600
8601 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8602 search for SOA records, which behave similar to the forward and
8603 reverse lookups.&lt;/p&gt;
8604
8605 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8606 specify any objectclass names, and instead look for the attributes it
8607 need to generate a DNS reply. This make it able to work with any
8608 objectclass that provide the needed attributes.&lt;/p&gt;
8609
8610 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8611 dnsdomain2 schemas. The latter is used for reverse entries like
8612 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8613
8614 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8615 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8616 attributes) and domainrelatedobject (for associatedDomain). The use
8617 of structural object classes make it impossible to combine these
8618 classes with the object classes used by DHCP.&lt;/p&gt;
8619
8620 &lt;p&gt;There are other schemas that could be used too, for example the
8621 dnszone structural object class used by Gosa and bind-sdb for the DNS
8622 attributes combined with the domainrelatedobject object class, but in
8623 this case some unused attributes would have to be included as well
8624 (zonename and relativedomainname).&lt;/p&gt;
8625
8626 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8627 mode and not use any of the existing objectclasses (dnsdomain,
8628 dnsdomain2 and dnszone) when one want to combine the DNS information
8629 with DHCP information, and instead create a auxiliary object class
8630 defined something like this (using the attributes defined for
8631 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8632
8633 &lt;blockquote&gt;&lt;pre&gt;
8634 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8635 SUP top
8636 AUXILIARY
8637 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8638 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8639 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8640 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8641 A6Record $ DNAMERecord
8642 ))
8643 &lt;/pre&gt;&lt;/blockquote&gt;
8644
8645 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8646 the domainrelatedobject object class, and allow any entity to include
8647 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8648 developers asking for their view on this schema and if they are
8649 interested in providing such schema with PowerDNS, and I hope my
8650 message will be accepted into their mailing list soon.&lt;/p&gt;
8651
8652 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8653
8654 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8655 the object attributes, and then uses the attributes it want. This
8656 make it harder to figure out exactly what attributes are used, but
8657 thanks to the working example in Debian Edu I can at least get an idea
8658 what is needed without having to read the source code.&lt;/p&gt;
8659
8660 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8661 search filter to use to locate the correct dhcpServer entity is
8662 stored. These are the relevant entries from
8663 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8664
8665 &lt;blockquote&gt;&lt;pre&gt;
8666 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8667 ldap-dhcp-server-cn &quot;dhcp&quot;;
8668 &lt;/pre&gt;&lt;/blockquote&gt;
8669
8670 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8671 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8672 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8673 search result is this entry:&lt;/p&gt;
8674
8675 &lt;blockquote&gt;&lt;pre&gt;
8676 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8677 cn: dhcp
8678 objectClass: top
8679 objectClass: dhcpServer
8680 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8681 &lt;/pre&gt;&lt;/blockquote&gt;
8682
8683 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8684 subtree with DHCP configuration. The DHCP configuration subtree base
8685 is located using a base scope search with base &quot;cn=DHCP
8686 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8687 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8688 The search result is this entry:&lt;/p&gt;
8689
8690 &lt;blockquote&gt;&lt;pre&gt;
8691 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8692 cn: DHCP Config
8693 objectClass: top
8694 objectClass: dhcpService
8695 objectClass: dhcpOptions
8696 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8697 dhcpStatements: ddns-update-style none
8698 dhcpStatements: authoritative
8699 dhcpOption: smtp-server code 69 = array of ip-address
8700 dhcpOption: www-server code 72 = array of ip-address
8701 dhcpOption: wpad-url code 252 = text
8702 &lt;/pre&gt;&lt;/blockquote&gt;
8703
8704 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8705 all the DHCP configuration is loaded, it is ready to receive requests.
8706 The subtree in Debian Edu contain objects with object classes
8707 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8708 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8709 and information about netmasks, dynamic range etc. Leaving out the
8710 details here because it is not relevant for the focus of my
8711 investigation, which is to see if it is possible to merge dns and dhcp
8712 related computer objects.&lt;/p&gt;
8713
8714 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8715 of the client (00:00:00:00:00:00 in this example), using a subtree
8716 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8717 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8718 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8719 like:&lt;/p&gt;
8720
8721 &lt;blockquote&gt;&lt;pre&gt;
8722 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8723 cn: hostname
8724 objectClass: top
8725 objectClass: dhcpHost
8726 dhcpHWAddress: ethernet 00:00:00:00:00:00
8727 dhcpStatements: fixed-address hostname
8728 &lt;/pre&gt;&lt;/blockquote&gt;
8729
8730 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8731 The object classes need to have fixed names, and the configuration
8732 need to be stored in a fairly specific LDAP structure. On the
8733 positive side, the invidiual dhcpHost entires can be anywhere without
8734 the DN pointed to by the dhcpServer entries. The latter should make
8735 it possible to group all host entries in a subtree next to the
8736 configuration entries, and this subtree can also be shared with the
8737 DNS server if the schema proposed above is combined with the dhcpHost
8738 structural object class.
8739
8740 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8741
8742 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8743 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8744 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8745 allowing DNS objects to be stored anywhere under the base cn specified
8746 in the configuration.&lt;/p&gt;
8747
8748 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8749 regarding which LDAP schemas to use and which LDAP structure to use.
8750 I guess one could implement ones own schema, as long as the
8751 objectclasses and attributes have the names used, but this do not
8752 really help when the DHCP subtree need to have a fairly fixed
8753 structure.&lt;/p&gt;
8754
8755 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8756 this might work for Debian Edu:&lt;/p&gt;
8757
8758 &lt;blockquote&gt;&lt;pre&gt;
8759 ou=services
8760 cn=machine-info (dhcpService) - dhcpServiceDN points here
8761 cn=dhcp (dhcpServer)
8762 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8763 cn=10.0.2.0 (dhcpSubnet)
8764 cn=group1 (dhcpGroup/dhcpOptions)
8765 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8766 cn=192.168.0.0 (dhcpSubnet)
8767 cn=group1 (dhcpGroup/dhcpOptions)
8768 ou=machines - PowerDNS base points here
8769 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8770 &lt;/pre&gt;&lt;/blockquote&gt;
8771
8772 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8773 entries to be in the dhcpGroup subtrees, the entries can be stored
8774 there instead of a common machines subtree, and the PowerDNS base
8775 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8776
8777 &lt;p&gt;The combined object under the machines subtree would look something
8778 like this:&lt;/p&gt;
8779
8780 &lt;blockquote&gt;&lt;pre&gt;
8781 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8782 dc: hostname
8783 objectClass: top
8784 objectClass: dhcpHost
8785 objectclass: domainrelatedobject
8786 objectclass: dnsDomainAux
8787 associateddomain: hostname.intern
8788 arecord: 10.11.12.13
8789 dhcpHWAddress: ethernet 00:00:00:00:00:00
8790 dhcpStatements: fixed-address hostname.intern
8791 &lt;/pre&gt;&lt;/blockquote&gt;
8792
8793 &lt;/p&gt;One could even add the LTSP configuration associated with a given
8794 machine, as long as the required attributes are available in a
8795 auxiliary object class.&lt;/p&gt;
8796 </description>
8797 </item>
8798
8799 <item>
8800 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
8801 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
8802 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
8803 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
8804 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
8805 DHCP services in Debian Edu to use the same LDAP objects for a given
8806 computer, to avoid the possibility of having a inconsistent state for
8807 a computer in LDAP (as in DHCP but no DNS entry or the other way
8808 around) and make it easier to add computers to LDAP.&lt;/p&gt;
8809
8810 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
8811 information finally found a solution that seem to work.&lt;/p&gt;
8812
8813 &lt;p&gt;The old setup required three LDAP objects for a given computer.
8814 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8815 we switch powerdns to use its strict LDAP method (ldap-method=strict
8816 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8817 merged into one while making it impossible to transfer the reverse map
8818 to a slave DNS server.&lt;/p&gt;
8819
8820 &lt;p&gt;If we also replace the object class used to get the DNS related
8821 attributes to one allowing these attributes to be combined with the
8822 dhcphost object class, we can merge the DNS and DHCP entries into one.
8823 I&#39;ve written such object class in the dnsdomainaux.schema file (need
8824 proper OIDs, but that is a minor issue), and tested the setup. It
8825 seem to work.&lt;/p&gt;
8826
8827 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
8828 for both DNS and DHCP, and even the LTSP configuration I suggested in
8829 an earlier email. The combined LDAP object will look something like
8830 this:&lt;/p&gt;
8831
8832 &lt;blockquote&gt;&lt;pre&gt;
8833 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8834 cn: hostname
8835 objectClass: dhcphost
8836 objectclass: domainrelatedobject
8837 objectclass: dnsdomainaux
8838 associateddomain: hostname.intern
8839 arecord: 10.11.12.13
8840 dhcphwaddress: ethernet 00:00:00:00:00:00
8841 dhcpstatements: fixed-address hostname
8842 ldapconfigsound: Y
8843 &lt;/pre&gt;&lt;/blockquote&gt;
8844
8845 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
8846 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8847 before asking DNS to resolve the fixed-adddress. LTSP will use
8848 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
8849
8850 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
8851 dhcphost in a different location, to allow us to put the objects
8852 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
8853 that. If I can&#39;t figure out a way to do that, we can still get rid of
8854 the hosts subtree and move all its content into the DHCP Config tree
8855 (which probably should be renamed to be more related to the new
8856 content. I suspect cn=dnsdhcp,ou=services or something like that
8857 might be a good place to put it.&lt;/p&gt;
8858
8859 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8860 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8861 </description>
8862 </item>
8863
8864 <item>
8865 <title>Idea for storing LTSP configuration in LDAP</title>
8866 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
8867 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
8868 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
8869 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
8870 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8871 clients, and that this can be used to fetch configuration from LDAP if
8872 Debian Edu choose to store configuration there.&lt;/p&gt;
8873
8874 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
8875 to get configuration from LDAP. The idea is to look up the MAC
8876 address of the client in LDAP, and look for attributes on the form
8877 ltspconfigsetting=value, and use this to export SETTING=value to the
8878 LTSP clients.&lt;/p&gt;
8879
8880 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
8881 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
8882 allowing us to store all information about a computer in one place.&lt;/p&gt;
8883
8884 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
8885 this approach. A real LDAP schema for the ltspClientAux objectclass
8886 need to be written. Comments, suggestions, etc?&lt;/p&gt;
8887
8888 &lt;blockquote&gt;&lt;pre&gt;
8889 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8890 #
8891 # Fetch LTSP client settings from LDAP based on MAC address
8892 #
8893 # Uses ethernet address as stored in the dhcpHost objectclass using
8894 # the dhcpHWAddress attribute or ethernet address stored in the
8895 # ieee802Device objectclass with the macAddress attribute.
8896 #
8897 # This module is written to be schema agnostic, and only depend on the
8898 # existence of attribute names.
8899 #
8900 # The LTSP configuration variables are saved directly using a
8901 # ltspConfig prefix and uppercasing the rest of the attribute name.
8902 # To set the SERVER variable, set the ltspConfigServer attribute.
8903 #
8904 # Some LDAP schema should be created with all the relevant
8905 # configuration settings. Something like this should work:
8906 #
8907 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
8908 # SUP top
8909 # AUXILIARY
8910 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8911
8912 LDAPSERVER=$(debian-edu-ldapserver)
8913 if [ &quot;$LDAPSERVER&quot; ] ; then
8914 LDAPBASE=$(debian-edu-ldapserver -b)
8915 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
8916 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
8917 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
8918 grep &#39;^ltspConfig&#39; | while read attr value ; do
8919 # Remove prefix and convert to upper case
8920 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
8921 # bass value on to clients
8922 eval &quot;$attr=$value; export $attr&quot;
8923 done
8924 done
8925 fi
8926 &lt;/pre&gt;&lt;/blockquote&gt;
8927
8928 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
8929 the while block might end up in a subshell causing the variables set
8930 there to not show up in ltsp-config, but if that is the case I am sure
8931 the code can be restructured to make sure the variables are passed on.
8932 I expect that can be solved with some testing. :)&lt;/p&gt;
8933
8934 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8935 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8936
8937 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
8938 configuration in LDAP that was created around year 2000 by
8939 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
8940 Xperience, Inc., 2000&lt;/a&gt;. I found its
8941 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
8942 personal home page over at redhat.com.&lt;/p&gt;
8943 </description>
8944 </item>
8945
8946 <item>
8947 <title>jXplorer, a very nice LDAP GUI</title>
8948 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
8949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
8950 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
8951 <description>&lt;p&gt;Since
8952 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
8953 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
8954 LDAP GUI that is even better than luma. The java application
8955 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
8956 moving LDAP objects and subtrees using drag-and-drop, and can
8957 authenticate using Kerberos. I have only tested the Kerberos
8958 authentication, but do not have a LDAP setup allowing me to rewrite
8959 LDAP with my test user yet. It is
8960 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
8961 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
8962 have with it is how it handle errors. If something go wrong, its
8963 non-intuitive behaviour require me to go through some query work list
8964 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
8965 </description>
8966 </item>
8967
8968 <item>
8969 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
8970 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
8971 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
8972 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
8973 <description>&lt;p&gt;Here is a short update on my &lt;a
8974 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
8975 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
8976 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
8977 not reporting the status for KDE, because the upgrade crashes when
8978 aptitude try because of missing conflicts
8979 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
8980 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
8981
8982 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
8983 complete list of the installed packages. Based on this I see these
8984 differences when I did a test run today. As usual, I do not really
8985 know what the correct set of packages would be, but thought it best to
8986 publish the difference.&lt;/p&gt;
8987
8988 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8989
8990 &lt;blockquote&gt;&lt;p&gt;
8991 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
8992 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
8993 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8994 libgtksourceview-common libpt-1.10.10-plugins-alsa
8995 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8996 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8997 python-4suite-xml python-eggtrayicon python-gtkhtml2
8998 python-gtkmozembed svgalibg1 xserver-xephyr zip
8999 &lt;/p&gt;&lt;/blockquote&gt;
9000
9001 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9002
9003 &lt;blockquote&gt;&lt;p&gt;
9004 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9005 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9006 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
9007 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
9008 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
9009 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
9010 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9011 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9012 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9013 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
9014 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
9015 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
9016 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9017 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
9018 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9019 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
9020 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
9021 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9022 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9023 mysql-common swfdec-gnome totem-gstreamer wodim
9024 &lt;/p&gt;&lt;/blockquote&gt;
9025
9026 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9027
9028 &lt;blockquote&gt;&lt;p&gt;
9029 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9030 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9031 xserver-xorg-input-all xserver-xorg-input-evdev
9032 xserver-xorg-input-kbd xserver-xorg-input-mouse
9033 xserver-xorg-input-synaptics xserver-xorg-video-all
9034 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9035 xserver-xorg-video-chips xserver-xorg-video-cirrus
9036 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9037 xserver-xorg-video-glint xserver-xorg-video-i128
9038 xserver-xorg-video-i740 xserver-xorg-video-mach64
9039 xserver-xorg-video-mga xserver-xorg-video-neomagic
9040 xserver-xorg-video-nouveau xserver-xorg-video-nv
9041 xserver-xorg-video-r128 xserver-xorg-video-radeon
9042 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9043 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9044 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9045 xserver-xorg-video-sis xserver-xorg-video-sisusb
9046 xserver-xorg-video-tdfx xserver-xorg-video-tga
9047 xserver-xorg-video-trident xserver-xorg-video-tseng
9048 xserver-xorg-video-vesa xserver-xorg-video-vmware
9049 xserver-xorg-video-voodoo
9050 &lt;/p&gt;&lt;/blockquote&gt;
9051
9052 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9053
9054 &lt;blockquote&gt;&lt;p&gt;
9055 deskbar-applet xserver-xorg xserver-xorg-core
9056 xserver-xorg-input-wacom xserver-xorg-video-intel
9057 xserver-xorg-video-openchrome
9058 &lt;/p&gt;&lt;/blockquote&gt;
9059
9060 &lt;p&gt;I was told on IRC that the xorg-xserver package was
9061 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
9062 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
9063 No idea when it hits Squeeze, but when it does I hope it will reduce
9064 the difference somewhat.
9065 </description>
9066 </item>
9067
9068 <item>
9069 <title>LUMA, a very nice LDAP GUI</title>
9070 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
9071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
9072 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
9073 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
9074 directory in Debian Edu, and in the process I started to miss a GUI
9075 tool to browse the LDAP tree. The only one I was able to find in
9076 Debian/Squeeze and Lenny is
9077 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
9078 be a great tool to get a overview of the current LDAP directory
9079 populated by default in Skolelinux. Thanks to it, I have been able to
9080 find empty and obsolete subtrees, misplaced objects and duplicate
9081 objects. It will be installed by default in Debian/Squeeze. If you
9082 are working with LDAP, give it a go. :)&lt;/p&gt;
9083
9084 &lt;p&gt;I did notice one problem with it I have not had time to report to
9085 the BTS yet. There is no .desktop file in the package, so the tool do
9086 not show up in the Gnome and KDE menus, but only deep down in in the
9087 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9088 released.&lt;/p&gt;
9089
9090 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
9091 like to move objects and remove subtrees directly in the GUI, but have
9092 not found a way to do that with LUMA yet. So in the mean time, I use
9093 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
9094
9095 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
9096 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9097
9098 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
9099 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
9100 useful GUI alternative. It seem like a good tool, but is unmaintained
9101 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9102 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
9103 </description>
9104 </item>
9105
9106 <item>
9107 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
9108 <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>
9109 <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>
9110 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
9111 <description>&lt;p&gt;A while back, I
9112 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
9113 about the fact&lt;/a&gt; that it is not possible with the provided schemas
9114 for storing DNS and DHCP information in LDAP to combine the two sets
9115 of information into one LDAP object representing a computer.&lt;/p&gt;
9116
9117 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
9118 the dhcpHost object class auxiliary, to allow it to be combined with
9119 the dNSDomain object class, and thus forming one object for one
9120 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
9121
9122 &lt;p&gt;If I understand this correctly, it is not safe to do this change
9123 without also changing the assigned number for the object class, and I
9124 do not know enough about LDAP schema design to do that properly for
9125 Debian Edu.&lt;/p&gt;
9126
9127 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
9128 the
9129 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
9130 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
9131 available today from IETF.&lt;/p&gt;
9132
9133 &lt;pre&gt;
9134 --- dhcp.schema (revision 65192)
9135 +++ dhcp.schema (working copy)
9136 @@ -376,7 +376,7 @@
9137 objectclass ( 2.16.840.1.113719.1.203.6.6
9138 NAME &#39;dhcpHost&#39;
9139 DESC &#39;This represents information about a particular client&#39;
9140 - SUP top
9141 + SUP top AUXILIARY
9142 MUST cn
9143 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9144 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
9145 &lt;/pre&gt;
9146
9147 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
9148 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9149 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
9150
9151 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9152 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9153 </description>
9154 </item>
9155
9156 <item>
9157 <title>Calling tasksel like the installer, while still getting useful output</title>
9158 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
9159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
9160 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
9161 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
9162 installs packages during the normal debian-installer run. Until now,
9163 I have ended up letting tasksel do the work, with the annoying problem
9164 of not getting any feedback at all when something fails (like a
9165 conffile question from dpkg or a download that fails), using code like
9166 this:
9167
9168 &lt;blockquote&gt;&lt;pre&gt;
9169 export DEBIAN_FRONTEND=noninteractive
9170 tasksel --new-install
9171 &lt;/pre&gt;&lt;/blockquote&gt;
9172
9173 This would invoke tasksel, let its automatic task selection pick the
9174 tasks to install, and continue to install the requested tasks without
9175 any output what so ever.
9176
9177 Recently I revisited this problem while working on the automatic
9178 package upgrade testing, because tasksel would some times hang without
9179 any useful feedback, and I want to see what is going on when it
9180 happen. Then it occured to me, I can parse the output from tasksel
9181 when asked to run in test mode, and use that aptitude command line
9182 printed by tasksel then to simulate the tasksel run. I ended up using
9183 code like this:
9184
9185 &lt;blockquote&gt;&lt;pre&gt;
9186 export DEBIAN_FRONTEND=noninteractive
9187 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
9188 $cmd
9189 &lt;/pre&gt;&lt;/blockquote&gt;
9190
9191 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
9192 --without-recommends -o APT::Install-Recommends=no -y install
9193 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9194 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
9195 laptop task and all packages with priority standard , required and
9196 important, just like tasksel would have done it during
9197 installation.&lt;/p&gt;
9198
9199 &lt;p&gt;A better approach is probably to extend tasksel to be able to
9200 install packages without using debconf-apt-progress, for use cases
9201 like this.&lt;/p&gt;
9202 </description>
9203 </item>
9204
9205 <item>
9206 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
9207 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
9208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
9209 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
9210 <description>&lt;p&gt;My
9211 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
9212 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
9213 finally made the upgrade logs available from
9214 &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;.
9215 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9216 apt and aptitude, and found their differences interesting. This time
9217 I will only focus on their removal plans.&lt;/p&gt;
9218
9219 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
9220 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
9221 surprising part is that it want to remove xorg and all
9222 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9223 sure why. When asking aptitude to do the same, it want to remove 129
9224 packages, but most of them are library packages I suspect are no
9225 longer needed. Both of them want to remove bluetooth packages, which
9226 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
9227
9228 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
9229 which seem like a bad idea and xorg the same way as with Gnome. Asking
9230 aptitude for the same, it wants to remove 192 packages, none which are
9231 too surprising.&lt;/p&gt;
9232
9233 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
9234 and avoided, and perhaps others as well. Here are the complete list
9235 of planned removals. The complete logs is available from the URL
9236 above. Note if you want to repeat these tests, that the upgrade test
9237 for kde+apt-get hung in the tasksel setup because of dpkg asking
9238 conffile questions. No idea why. I worked around it by using
9239 &#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
9240 continue.&lt;/p&gt;
9241
9242 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
9243 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
9244 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9245 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9246 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9247 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9248 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9249 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9250 xserver-xorg-input-kbd xserver-xorg-input-mouse
9251 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9252 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9253 xserver-xorg-video-ati xserver-xorg-video-chips
9254 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9255 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9256 xserver-xorg-video-glint xserver-xorg-video-i128
9257 xserver-xorg-video-i740 xserver-xorg-video-imstt
9258 xserver-xorg-video-intel xserver-xorg-video-mach64
9259 xserver-xorg-video-mga xserver-xorg-video-neomagic
9260 xserver-xorg-video-nsc xserver-xorg-video-nv
9261 xserver-xorg-video-openchrome xserver-xorg-video-r128
9262 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9263 xserver-xorg-video-rendition xserver-xorg-video-s3
9264 xserver-xorg-video-s3virge xserver-xorg-video-savage
9265 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9266 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9267 xserver-xorg-video-tga xserver-xorg-video-trident
9268 xserver-xorg-video-tseng xserver-xorg-video-v4l
9269 xserver-xorg-video-vesa xserver-xorg-video-vga
9270 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9271 xulrunner-1.9-gnome-support&lt;/p&gt;
9272
9273 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9274
9275 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9276 djvulibre-desktop finger gnome-app-install gnome-mount
9277 gnome-network-admin gnome-spell gnome-vfs-obexftp
9278 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9279 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9280 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9281 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9282 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9283 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9284 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9285 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9286 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9287 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9288 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9289 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9290 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9291 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9292 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9293 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9294 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9295 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9296 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9297 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9298 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9299 openoffice.org-writer2latex openssl-blacklist p7zip
9300 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9301 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9302 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9303 swfdec-mozilla totem-gstreamer update-manager wodim
9304 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9305 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9306 zip&lt;/p&gt;
9307
9308 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9309
9310 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9311 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9312 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9313 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9314 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9315 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9316 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9317 xserver-xorg-input-kbd xserver-xorg-input-mouse
9318 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9319 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9320 xserver-xorg-video-ati xserver-xorg-video-chips
9321 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9322 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9323 xserver-xorg-video-glint xserver-xorg-video-i128
9324 xserver-xorg-video-i740 xserver-xorg-video-imstt
9325 xserver-xorg-video-intel xserver-xorg-video-mach64
9326 xserver-xorg-video-mga xserver-xorg-video-neomagic
9327 xserver-xorg-video-nsc xserver-xorg-video-nv
9328 xserver-xorg-video-openchrome xserver-xorg-video-r128
9329 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9330 xserver-xorg-video-rendition xserver-xorg-video-s3
9331 xserver-xorg-video-s3virge xserver-xorg-video-savage
9332 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9333 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9334 xserver-xorg-video-tga xserver-xorg-video-trident
9335 xserver-xorg-video-tseng xserver-xorg-video-v4l
9336 xserver-xorg-video-vesa xserver-xorg-video-vga
9337 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9338
9339 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9340 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9341 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9342 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9343 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9344 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9345 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9346 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9347 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9348 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9349 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9350 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9351 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9352 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9353 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9354 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9355 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9356 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9357 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9358 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
9359 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9360 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9361 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
9362 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9363 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9364 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9365 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9366 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9367 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
9368 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
9369 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9370 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9371 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9372 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9373 texlive-common texlive-doc-base texlive-fonts-recommended
9374 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9375 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9376 xulrunner-1.9&lt;/p&gt;
9377
9378 </description>
9379 </item>
9380
9381 <item>
9382 <title>Automatic upgrade testing from Lenny to Squeeze</title>
9383 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
9384 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
9385 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
9386 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
9387 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9388 have been discovered and reported in the process
9389 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
9390 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
9391 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
9392 kdebase-workspace-data), and to get a more regular testing going on, I
9393 am working on a script to automate the test.&lt;/p&gt;
9394
9395 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
9396 Gnome or KDE desktop installation inside the chroot before upgrading
9397 it. To ensure no services are started in the chroot, a policy-rc.d
9398 script is inserted. To make sure tasksel believe it is to install a
9399 desktop on a laptop, the tasksel tests are replaced in the chroot
9400 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
9401
9402 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9403 currently always fail because udev refuses to upgrade with the kernel
9404 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9405 is created. The bug report
9406 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
9407 this problem do not trigger in a chroot, but I touch the file anyway
9408 to make sure the upgrade go well. Testing on virtual and real
9409 hardware have failed me because of udev so far, and creating this file
9410 do the trick in such settings anyway. This is a
9411 &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
9412 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
9413 maintainer because he lack the resources to rewrite udev to keep
9414 working with old kernels or something like that. I really wish the
9415 udev upstream would keep udev backwards compatible, to avoid such
9416 upgrade problem, but given that they fail to do so, I guess
9417 documenting the way out of this mess is the best option we got for
9418 Debian Squeeze.&lt;/p&gt;
9419
9420 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
9421 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
9422 trick:&lt;/p&gt;
9423
9424 &lt;blockquote&gt;&lt;pre&gt;
9425 #!/bin/sh
9426 set -ex
9427
9428 if [ &quot;$1&quot; ] ; then
9429 desktop=$1
9430 else
9431 desktop=gnome
9432 fi
9433
9434 from=lenny
9435 to=squeeze
9436
9437 exec &amp;lt; /dev/null
9438 unset LANG
9439 mirror=http://ftp.skolelinux.org/debian
9440 tmpdir=chroot-$from-upgrade-$to-$desktop
9441 fuser -mv .
9442 debootstrap $from $tmpdir $mirror
9443 chroot $tmpdir aptitude update
9444 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
9445 #!/bin/sh
9446 exit 101
9447 EOF
9448 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9449 exit_cleanup() {
9450 umount $tmpdir/proc
9451 }
9452 mount -t proc proc $tmpdir/proc
9453 # Make sure proc is unmounted also on failure
9454 trap exit_cleanup EXIT INT
9455
9456 chroot $tmpdir aptitude -y install debconf-utils
9457
9458 # Make sure tasksel autoselection trigger. It need the test scripts
9459 # to return the correct answers.
9460 echo tasksel tasksel/desktop multiselect $desktop | \
9461 chroot $tmpdir debconf-set-selections
9462
9463 # Include the desktop and laptop task
9464 for test in desktop laptop ; do
9465 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
9466 #!/bin/sh
9467 exit 2
9468 EOF
9469 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9470 done
9471
9472 DEBIAN_FRONTEND=noninteractive
9473 DEBIAN_PRIORITY=critical
9474 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9475 chroot $tmpdir tasksel --new-install
9476
9477 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
9478 chroot $tmpdir aptitude update
9479 touch $tmpdir/etc/udev/kernel-upgrade
9480 chroot $tmpdir aptitude -y dist-upgrade
9481 fuser -mv
9482 &lt;/pre&gt;&lt;/blockquote&gt;
9483
9484 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
9485 with aptitude, but I have not had time to look at how they behave
9486 differently so far. I hope to get a cron job running to do the test
9487 regularly and post the result on the web. The Gnome upgrade currently
9488 work, while the KDE upgrade fail because of the bug in
9489 kdebase-workspace-data&lt;/p&gt;
9490
9491 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
9492 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
9493 post, so I will refrain from trying. I can report that for Gnome,
9494 aptitude report 760 packages upgraded, 448 newly installed, 129 to
9495 remove and 1 not upgraded and 1024MB need to be downloaded while for
9496 KDE the same numbers are 702 packages upgraded, 507 newly installed,
9497 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
9498
9499 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
9500 is able to migrate to dependency based boot sequencing and parallel
9501 booting without a hitch. Was unsure if there were still bugs with
9502 packages failing to clean up their obsolete init.d script during
9503 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9504 packages.&lt;/p&gt;
9505 </description>
9506 </item>
9507
9508 <item>
9509 <title>Upstart or sysvinit - as init.d scripts see it</title>
9510 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
9511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
9512 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
9513 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
9514 scripts to migrate (some of) their operations to upstart job while
9515 keeping the init.d for hurd and kfreebsd. The packages with such
9516 needs will need a way to get their init.d scripts to behave
9517 differently when used with sysvinit and with upstart. Because of
9518 this, I had a look at the environment variables set when a init.d
9519 script is running under upstart, and when it is not.&lt;/p&gt;
9520
9521 &lt;p&gt;With upstart, I notice these environment variables are set when a
9522 script is started from rcS.d/ (ignoring some irrelevant ones like
9523 COLUMNS):&lt;/p&gt;
9524
9525 &lt;blockquote&gt;&lt;pre&gt;
9526 DEFAULT_RUNLEVEL=2
9527 previous=N
9528 PREVLEVEL=
9529 RUNLEVEL=
9530 runlevel=S
9531 UPSTART_EVENTS=startup
9532 UPSTART_INSTANCE=
9533 UPSTART_JOB=rc-sysinit
9534 &lt;/pre&gt;&lt;/blockquote&gt;
9535
9536 &lt;p&gt;With sysvinit, these environment variables are set for the same
9537 script.&lt;/p&gt;
9538
9539 &lt;blockquote&gt;&lt;pre&gt;
9540 INIT_VERSION=sysvinit-2.88
9541 previous=N
9542 PREVLEVEL=N
9543 RUNLEVEL=S
9544 runlevel=S
9545 &lt;/pre&gt;&lt;/blockquote&gt;
9546
9547 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
9548 sysvinit are not set by upstart. Not sure if it is intentional or not
9549 to not be compatible with sysvinit in this regard.&lt;/p&gt;
9550
9551 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9552 looking for the UPSTART_JOB environment variable seem to be a good
9553 choice.&lt;/p&gt;
9554 </description>
9555 </item>
9556
9557 <item>
9558 <title>A manual for standards wars...</title>
9559 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9561 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9562 <description>&lt;p&gt;Via the
9563 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9564 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9565 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9566 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9567 following the standards wars of today.&lt;/p&gt;
9568 </description>
9569 </item>
9570
9571 <item>
9572 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9573 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9575 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9576 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9577 to get a list of the machine types in use thanks to the DMI
9578 information extracted from each machine. The script to do so is
9579 included in the sitesummary package, and here is example output from
9580 the Skolelinux build servers:&lt;/p&gt;
9581
9582 &lt;blockquote&gt;&lt;pre&gt;
9583 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9584 vendor count
9585 Dell Computer Corporation 1
9586 PowerEdge 1750 1
9587 IBM 1
9588 eserver xSeries 345 -[8670M1X]- 1
9589 Intel 2
9590 [no-dmi-info] 3
9591 maintainer:~#
9592 &lt;/pre&gt;&lt;/blockquote&gt;
9593
9594 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9595 provided in each machine. Here there are Intel machines without model
9596 information listed with Intel as vendor and no model, and virtual Xen
9597 machines listed as [no-dmi-info]. One can add -l as a command line
9598 option to list the individual machines.&lt;/p&gt;
9599
9600 &lt;p&gt;A larger list is
9601 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9602 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9603 provide the basic sitesummary report publicly. In their report there
9604 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9605 their machines, and as sitesummary is available in both distributions,
9606 it is trivial to get all of them to report to the same central
9607 collector.&lt;/p&gt;
9608 </description>
9609 </item>
9610
9611 <item>
9612 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9613 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9614 <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>
9615 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9616 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9617 start at boot when an NVidia video card is used is handled. The
9618 problem seem to be that the nvidia X.org driver uses a long time to
9619 initialize, and this duration is longer than kdm is configured to
9620 wait.&lt;/p&gt;
9621
9622 &lt;p&gt;I came across two bugs related to this issue,
9623 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9624 against initscripts and passed on to nvidia-glx when it became obvious
9625 that the nvidia drivers were involved, and
9626 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9627 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9628
9629 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9630 problem nvidia video card owners experience and make sure the Debian
9631 distribution work out of the box for these users. The nvidia driver
9632 maintainers expect kdm to be set up to wait longer, while kdm expect
9633 the nvidia driver maintainers to fix the driver to start faster, and
9634 while they wait for each other I guess the users end up switching to a
9635 distribution that work for them. I have no idea what the solution is,
9636 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9637
9638 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9639 </description>
9640 </item>
9641
9642 <item>
9643 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9644 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9646 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9647 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9648 The feature seem to hold up pretty well, but three fairly serious
9649 issues are known and should be solved:
9650
9651 &lt;p&gt;&lt;ul&gt;
9652
9653 &lt;li&gt;The wicd package seen to
9654 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9655 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9656 parallel booting is enabled. No idea why, but the wicd maintainer
9657 seem to be on the case.&lt;/li&gt;
9658
9659 &lt;li&gt;The nvidia X driver seem to
9660 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9661 triggered more easily when parallel booting is in effect. The
9662 maintainer is on the case.&lt;/li&gt;
9663
9664 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9665 sequencing (the shutdown is broken) when old file-rc users
9666 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9667 sysv-rc. One way to solve it would be for file-rc to create
9668 /etc/init.d/.legacy-bootordering, and another is to try to make
9669 sysv-rc more robust. Will investigate some more and probably upload a
9670 workaround in sysv-rc to help those trying to move from file-rc to
9671 sysv-rc get a working shutdown.&lt;/li&gt;
9672
9673 &lt;/ul&gt;&lt;/p&gt;
9674
9675 &lt;p&gt;All in all not many surprising issues, and all of them seem
9676 solvable before Squeeze is released. In addition to these there are
9677 some packages with bugs in their dependencies and run level settings,
9678 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9679
9680 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9681 the BTS, please usertag the report to get it to show up at
9682 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9683 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9684
9685 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9686 </description>
9687 </item>
9688
9689 <item>
9690 <title>More flexible firmware handling in debian-installer</title>
9691 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9693 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9694 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9695 found time today to return to the project. Having to spend less time
9696 working dependency based boot in debian, as it is almost complete now,
9697 definitely helped freeing some time.&lt;/p&gt;
9698
9699 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9700 include some firmware packages on the Debian Edu CDs, those needed to
9701 get disk and network controllers working. Without having these
9702 firmware packages available during installation, it is impossible to
9703 install Debian Edu on the given machine, and because our target group
9704 are non-technical people, asking them to provide firmware packages on
9705 an external medium is a support pain. Initially, I expected it to be
9706 enough to include the firmware packages on the CD to get
9707 debian-installer to find and use them. This proved to be wrong.
9708 Next, I hoped it was enough to symlink the relevant firmware packages
9709 to some useful location on the CD (tried /cdrom/ and
9710 /cdrom/firmware/). This also proved to not work, and at this point I
9711 found time to look at the debian-installer code to figure out what was
9712 going to work.&lt;/p&gt;
9713
9714 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9715 look revealed that it would only look for firmware packages outside
9716 the installation media, so the CD was never checked for firmware
9717 packages. It would only check USB sticks, floppies and other
9718 &quot;external&quot; media devices. Today I changed it to also look in the
9719 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9720 solve the problem I ran into with Debian edu. I also changed it to
9721 look in /firmware/, to make sure the installer also find firmware
9722 provided in the initrd when booting the installer via PXE, to allow us
9723 to provide the same feature in the PXE setup included in Debian
9724 Edu.&lt;/p&gt;
9725
9726 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9727 activated without asking if the license is accepted, I extended
9728 hw-detect to look for preinst scripts in the firmware packages, and
9729 run these before activating the firmware during installation. The
9730 license question is asked using debconf in the preinst, so this should
9731 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9732
9733 &lt;p&gt;If you want to discuss the details of these features, please
9734 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9735 </description>
9736 </item>
9737
9738 <item>
9739 <title>Parallellized boot is now the default in Debian/unstable</title>
9740 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9742 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9743 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9744 Debian/unstable for machines using dependency based boot sequencing.
9745 Apparently the testing of concurrent booting has been wider than
9746 expected, if I am to believe the
9747 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9748 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9749 with the feature this weekend, to give us some time to detect any
9750 remaining problems before Squeeze is frozen. If serious problems are
9751 detected, it is simple to change the default back to sequential boot.
9752 The upload of the new sysvinit package also activate a new upstream
9753 version.&lt;/p&gt;
9754
9755 More information about
9756 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9757 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9758 currently possible to disable parallel booting when one run into
9759 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9760
9761 &lt;blockquote&gt;&lt;pre&gt;
9762 CONCURRENCY=none
9763 &lt;/pre&gt;&lt;/blockquote&gt;
9764
9765 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9766 the BTS, please usertag the report to get it to show up at
9767 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9768 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9769 </description>
9770 </item>
9771
9772 <item>
9773 <title>Sitesummary tip: Listing MAC address of all clients</title>
9774 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9775 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9776 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9777 <description>&lt;p&gt;In the recent Debian Edu versions, the
9778 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9779 system&lt;/a&gt; is used to keep track of the machines in the school
9780 network. Each machine will automatically report its status to the
9781 central server after boot and once per night. The network setup is
9782 also reported, and using this information it is possible to get the
9783 MAC address of all network interfaces in the machines. This is useful
9784 to update the DHCP configuration.&lt;/p&gt;
9785
9786 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
9787 ist all MAC addresses of all machines reporting to sitesummary. Run
9788 this on the collector host:&lt;/p&gt;
9789
9790 &lt;blockquote&gt;&lt;pre&gt;
9791 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
9792 &lt;/pre&gt;&lt;/blockquote&gt;
9793
9794 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
9795 line per machine and with space between the MAC addresses.&lt;/p&gt;
9796
9797 &lt;p&gt;To allow system administrators easier job at adding static DHCP
9798 addresses for hosts, it would be possible to extend this to fetch
9799 machine information from sitesummary and update the DHCP and DNS
9800 tables in LDAP using this information. Such tool is unfortunately not
9801 written yet.&lt;/p&gt;
9802 </description>
9803 </item>
9804
9805 <item>
9806 <title>systemd, an interesting alternative to upstart</title>
9807 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
9808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
9809 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
9810 <description>&lt;p&gt;The last few days a new boot system called
9811 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
9812 has been
9813 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
9814
9815 to the free software world. I have not yet had time to play around
9816 with it, but it seem to be a very interesting alternative to
9817 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
9818 a good alternative for Debian when we are able to switch to an event
9819 based boot system. Tollef is
9820 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
9821 systemd into Debian, and I look forward to seeing how well it work. I
9822 like the fact that systemd handles init.d scripts with dependency
9823 information natively, allowing them to run in parallel where upstart
9824 at the moment do not.&lt;/p&gt;
9825
9826 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
9827 platform support. It only work on recent Linux kernels, and also need
9828 some new kernel features enabled to function properly. This means
9829 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9830 system. Not sure how that will be handled if systemd proves to be the
9831 way forward.&lt;/p&gt;
9832
9833 &lt;p&gt;In the mean time, based on the
9834 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9835 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
9836 decided to enable full parallel booting as the default in Debian as
9837 soon as possible (probably this weekend or early next week), to see if
9838 there are any remaining serious bugs in the init.d dependencies. A
9839 new version of the sysvinit package implementing this change is
9840 already in experimental. If all go well, Squeeze will be released
9841 with parallel booting enabled by default.&lt;/p&gt;
9842 </description>
9843 </item>
9844
9845 <item>
9846 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
9847 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
9848 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
9849 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
9850 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
9851 complete, so complete that it is actually possible to run all the
9852 init.d scripts in parallell based on these dependencies. If you want
9853 to test your Squeeze system, make sure
9854 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9855 based boot sequencing&lt;/a&gt; is enabled, and add this line to
9856 /etc/default/rcS:&lt;/p&gt;
9857
9858 &lt;blockquote&gt;&lt;pre&gt;
9859 CONCURRENCY=makefile
9860 &lt;/pre&gt;&lt;/blockquote&gt;
9861
9862 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
9863 scripts in parallel using the dependency information stored in
9864 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9865 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9866 to try to start the kdm and gdm scripts as early as possible, and will
9867 start the facilities required by kdm or gdm as early as possible to
9868 make this happen.&lt;/p&gt;
9869
9870 &lt;p&gt;Give it a try, and see if you like the result. If some services
9871 fail to start properly, it is most likely because they have incomplete
9872 init.d script dependencies in their startup script (or some of their
9873 dependent scripts have incomplete dependencies). Report bugs and get
9874 the package maintainers to fix it. :)&lt;/p&gt;
9875
9876 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
9877 manage to get the init.d script dependencies complete and correct. I
9878 expect we will get there in Squeeze+1, if we get manage to test and
9879 fix the remaining issues.&lt;/p&gt;
9880
9881 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9882 the BTS, please usertag the report to get it to show up at
9883 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9884 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9885 </description>
9886 </item>
9887
9888 <item>
9889 <title>Debian has switched to dependency based boot sequencing</title>
9890 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
9891 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
9892 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
9893 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
9894 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
9895 have been migrated to using dependency based boot sequencing. This
9896 conclude work me and others have been doing for the last three days.
9897 It feels great to see this finally part of the default Debian
9898 installation. Now we just need to weed out the last few problems that
9899 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
9900
9901 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
9902 fixing the more fundamental problem of handing the event based
9903 non-predictable kernel in the early boot.&lt;/p&gt;
9904 </description>
9905 </item>
9906
9907 <item>
9908 <title>Taking over sysvinit development</title>
9909 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
9910 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
9911 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
9912 <description>&lt;p&gt;After several years of frustration with the lack of activity from
9913 the existing sysvinit upstream developer, I decided a few weeks ago to
9914 take over the package and become the new upstream. The number of
9915 patches to track for the Debian package was becoming a burden, and the
9916 lack of synchronization between the distribution made it hard to keep
9917 the package up to date.&lt;/p&gt;
9918
9919 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9920 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
9921 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
9922 and Fedora), based on the patches currently in use in these
9923 distributions. We Debian maintainers plan to move to this tarball as
9924 the new upstream as soon as we find time to do the merge. Since the
9925 new tarball was created, we agreed with Werner at SuSe to make a new
9926 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
9927 development there. The project is registered and currently waiting
9928 for approval by the Savannah administrators, and as soon as it is
9929 approved, we will import the old versions from svn and continue
9930 working on the future release.&lt;/p&gt;
9931
9932 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
9933 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
9934 </description>
9935 </item>
9936
9937 <item>
9938 <title>Debian boots quicker and quicker</title>
9939 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
9940 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
9941 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
9942 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
9943 people involved in the boot system on Debian and Ubuntu, to see if we
9944 could find more ways to speed up the boot system. This was an Ubuntu
9945 funded
9946 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
9947 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
9948 of boot systems, and ways to handle the increasing number of boot
9949 issues introduced by the Linux kernel becoming more and more
9950 asynchronous and event base. The Ubuntu approach using udev and
9951 upstart might be a good way forward. Time will show.&lt;/p&gt;
9952
9953 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
9954 process in Debian. All of these should be applied to get a quick
9955 boot:&lt;/p&gt;
9956
9957 &lt;ul&gt;
9958
9959 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
9960
9961 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
9962 clock is in UTC.&lt;/li&gt;
9963
9964 &lt;li&gt;Install and activate the insserv package to enable
9965 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9966 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
9967
9968 &lt;/ul&gt;
9969
9970 These points are based on the Google summer of code work done by
9971 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
9972 Villegas&lt;/a&gt;.
9973
9974 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
9975 unstable yesterday. When we tested it, we were able to cut 6 seconds
9976 from the boot sequence. It depend on very correct dependency
9977 declaration in all init.d scripts, so I expect us to find edge cases
9978 where the dependences in some scripts are slightly wrong when we start
9979 using this.&lt;/p&gt;
9980
9981 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9982 introduced by Raphael Geissert today, one that could affect the
9983 startup speed as well. Instead of starting some scripts concurrently
9984 from rcS.d/ and another set of scripts from rc2.d/, it would be
9985 possible to run a of them in the same process. A quick way to test
9986 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
9987 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
9988 </description>
9989 </item>
9990
9991 <item>
9992 <title>BSAs påstander om piratkopiering møter motstand</title>
9993 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
9994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
9995 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
9996 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
9997 programvareselskapene som Microsoft og Apple, publisert en rapport der
9998 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9999 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10000 dager siden kom
10001 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
10002 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
10003 dagene. Et spesielt interessant kommentar fra Sverige,
10004 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
10005 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
10006
10007 &lt;blockquote&gt;
10008 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
10009 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10010 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
10011 exakta&quot;, säger BSAs Sverigechef John Hugosson.
10012 &lt;/blockquote&gt;
10013
10014 &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
10015 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
10016 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
10017 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
10018 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
10019
10020 &lt;p&gt;Fant lenkene via &lt;a
10021 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
10022 på Slashdot&lt;/a&gt;.&lt;/p&gt;
10023 </description>
10024 </item>
10025
10026 <item>
10027 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
10028 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
10029 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
10030 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
10031 <description>&lt;p&gt;Kom over
10032 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
10033 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10034 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10035 jobber til daglig. En rask opptelling forteller meg at vi har 490
10036 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
10037 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
10038 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
10039 </description>
10040 </item>
10041
10042 <item>
10043 <title>Kryptert harddisk - naturligvis</title>
10044 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
10045 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
10046 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
10047 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
10048 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
10049 når en tar tap av arbeidstid, fortrolige dokumenter,
10050 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10051 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10052 til at jeg har kryptert harddisken på både kontormaskinen og min
10053 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10054 komme på avveie, den første informasjon relatert til jobben min ved
10055 Universitetet i Oslo, og den andre relatert til blant annet
10056 foreningsarbeide. Kryptering av diskene gjør at det er lite
10057 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10058 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10059 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10060 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10061 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10062 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10063 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10064 det er gjort slik jeg gjør det er minimale, og gevinstene er
10065 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10066 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
10067
10068 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10069 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10070 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10071 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10072 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10073 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10074 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10075 betydelige.&lt;/p&gt;
10076 </description>
10077 </item>
10078
10079 <item>
10080 <title>Two projects that have improved the quality of free software a lot</title>
10081 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
10082 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
10083 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
10084 <description>&lt;p&gt;There are two software projects that have had huge influence on the
10085 quality of free software, and I wanted to mention both in case someone
10086 do not yet know them.&lt;/p&gt;
10087
10088 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
10089 tool to detect and expose errors in the memory handling of programs.
10090 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
10091 and it will report any problems on stdout. It is even better if the
10092 program include debug information. With debug information, it is able
10093 to report the source file name and line number where the problem
10094 occurs. It can report things like &#39;reading past memory block in file
10095 X line N, the memory block was allocated in file Y, line M&#39;, and
10096 &#39;using uninitialised value in control logic&#39;. This tool has made it
10097 trivial to investigate reproducible crash bugs in programs, and have
10098 reduced the number of this kind of bugs in free software a lot.
10099
10100 &lt;p&gt;The second one is
10101 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
10102 a source code checker. It is able to process the source of a program
10103 and find problems in the logic without running the program. It
10104 started out as the Stanford Checker and became well known when it was
10105 used to find bugs in the Linux kernel. It is now a commercial tool
10106 and the company behind it is running
10107 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
10108 free software community, where a lot of free software projects get
10109 their source checked for free. Several thousand defects have been
10110 found and fixed so far. It can find errors like &#39;lock L taken in file
10111 X line N is never released if exiting in line M&#39;, or &#39;the code in file
10112 Y lines O to P can never be executed&#39;. The projects included in the
10113 community service project have managed to get rid of a lot of
10114 reliability problems thanks to Coverity.&lt;/p&gt;
10115
10116 &lt;p&gt;I believe tools like this, that are able to automatically find
10117 errors in the source, are vital to improve the quality of software and
10118 make sure we can get rid of the crashing and failing software we are
10119 surrounded by today.&lt;/p&gt;
10120 </description>
10121 </item>
10122
10123 <item>
10124 <title>No patch is not better than a useless patch</title>
10125 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
10126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
10127 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
10128 <description>&lt;p&gt;Julien Blache
10129 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
10130 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
10131 patch allow one to discuss a concrete and proposed solution, and also
10132 prove that the issue at hand is important enough for someone to spent
10133 time on fixing it. No patch do not provide any of these positive
10134 properties.&lt;/p&gt;
10135 </description>
10136 </item>
10137
10138 <item>
10139 <title>Standardize on protocols and formats, not vendors and applications</title>
10140 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
10141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
10142 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
10143 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
10144 very good one to form a long lived computer infrastructure. It is the
10145 simple one, lost by many in todays computer industry: Standardize on
10146 open network protocols and open exchange/storage formats, not applications.
10147 Applications come and go, while protocols and files tend to stay, and
10148 thus one want to make it easy to change application and vendor, while
10149 avoiding conversion costs and locking users to a specific platform or
10150 application.&lt;/p&gt;
10151
10152 &lt;p&gt;This approach make it possible to replace the client applications
10153 independently of the server applications. One can even allow users to
10154 use several different applications as long as they handle the selected
10155 protocol and format. In the normal case, only one client application
10156 is recommended and users only get help if they choose to use this
10157 application, but those that want to deviate from the easy path are not
10158 blocked from doing so.&lt;/p&gt;
10159
10160 &lt;p&gt;It also allow us to replace the server side without forcing the
10161 users to replace their applications, and thus allow us to select the
10162 best server implementation at any moment, when scale and resouce
10163 requirements change.&lt;/p&gt;
10164
10165 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
10166 open formats, but I would never recommend standardizing on a single
10167 application that do not use open network protocol or open formats.&lt;/p&gt;
10168 </description>
10169 </item>
10170
10171 <item>
10172 <title>Returning from Skolelinux developer gathering</title>
10173 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
10174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
10175 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
10176 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
10177 Edu/Skolelinux development gathering. I got a bit done tuning the
10178 desktop, and looked into the dynamic service location protocol
10179 implementation avahi. It look like it could be useful for us. Almost
10180 30 people participated, and I believe it was a great environment to
10181 get to know the Skolelinux system. Walter Bender, involved in the
10182 development of the Sugar educational platform, presented his stuff and
10183 also helped me improve my OLPC installation. He also showed me that
10184 his Turtle Art application can be used in standalone mode, and we
10185 agreed that I would help getting it packaged for Debian. As a
10186 standalone application it would be great for Debian Edu. We also
10187 tried to get the video conferencing working with two OLPCs, but that
10188 proved to be too hard for us. The application seem to need more work
10189 before it is ready for me. I look forward to getting home and relax
10190 now. :)&lt;/p&gt;
10191 </description>
10192 </item>
10193
10194 <item>
10195 <title>Time for new LDAP schemas replacing RFC 2307?</title>
10196 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
10197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
10198 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
10199 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
10200 optimal. There is RFC 2307 documenting one way to store NIS maps in
10201 LDAP, and a modified version of this normally called RFC 2307bis, with
10202 some modifications to be compatible with Active Directory. The RFC
10203 specification handle the content of a lot of system databases, but do
10204 not handle DNS zones and DHCP configuration.&lt;/p&gt;
10205
10206 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
10207 we would like to store information about users, SMB clients/hosts,
10208 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10209 and LTSP configuration in LDAP. These objects have a lot in common,
10210 but with the current LDAP schemas it is not possible to have one
10211 object per entity. For example, one need to have at least three LDAP
10212 objects for a given computer, one with the SMB related stuff, one with
10213 DNS information and another with DHCP information. The schemas
10214 provided for DNS and DHCP are impossible to combine into one LDAP
10215 object. In addition, it is impossible to implement quick queries for
10216 netgroup membership, because of the way NIS triples are implemented.
10217 It just do not scale. I believe it is time for a few RFC
10218 specifications to cleam up this mess.&lt;/p&gt;
10219
10220 &lt;p&gt;I would like to have one LDAP object representing each computer in
10221 the network, and this object can then keep the SMB (ie host key), DHCP
10222 (mac address/name) and DNS (name/IP address) settings in one place.
10223 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
10224
10225 &lt;p&gt;I would also like to have a quick way to map from a user or
10226 computer and to the net group this user or computer is a member.&lt;/p&gt;
10227
10228 &lt;p&gt;Active Directory have done a better job than unix heads like myself
10229 in this regard, and the unix side need to catch up. Time to start a
10230 new IETF work group?&lt;/p&gt;
10231 </description>
10232 </item>
10233
10234 <item>
10235 <title>Endelig er Debian Lenny gitt ut</title>
10236 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
10237 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
10238 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
10239 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
10240 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
10241 Et langt steg videre for Debian-prosjektet, og en rekke nye
10242 programpakker blir nå tilgjengelig for de av oss som bruker den
10243 stabile utgaven av Debian. Neste steg er nå å få
10244 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
10245 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10246 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10247 slippes løs på skolene. Takk til alle debian-utviklerne som har
10248 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10249 bootsekvens tilgjengelig i stabil utgave, vha pakken
10250 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10251 </description>
10252 </item>
10253
10254 <item>
10255 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10256 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10258 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10259 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10260 Oslo. Most of Saturday was used for the general assemly for the
10261 member organization, but the rest of the weekend I used to tune the
10262 LTSP installation. LTSP now work out of the box on the 10-network.
10263 Acer Aspire One proved to be a very nice thin client, with both
10264 screen, mouse and keybard in a small box. Was working on getting the
10265 diskless workstation setup configured out of the box, but did not
10266 finish it before the weekend was up.&lt;/p&gt;
10267
10268 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10269 the Brazilian group, so that will have to wait for the next
10270 development gathering. Would love to have the Debian Edu installer
10271 automatically detect and configure a multiseat setup when it find one
10272 of these cards.&lt;/p&gt;
10273 </description>
10274 </item>
10275
10276 <item>
10277 <title>The sorry state of multimedia browser plugins in Debian</title>
10278 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10279 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10280 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10281 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10282 plugins available in Debian Lenny, to see which one we should use by
10283 default in Debian Edu. We need an embedded video playing plugin with
10284 control buttons to pause or stop the video, and capable of streaming
10285 all the multimedia content available on the web. The test results and
10286 notes are available on
10287 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10288 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10289 fill this need. My personal video player favorite, VLC, has a really
10290 bad plugin which fail on a lot of the test pages. A lot of the MIME
10291 types I would expect to work with any free software player (like
10292 video/ogg), just do not work. And simple formats like the
10293 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10294 totem and vlc plugins. I hope the situation will improve soon. No
10295 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10296
10297 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10298 be the only one fitting our needs. :/&lt;/p&gt;
10299 </description>
10300 </item>
10301
10302 </channel>
10303 </rss>