]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
b10463fcdb02ea01d9420da4411e888e0b79c430
[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>OpenALPR, find car license plates in video streams - nice free software</title>
11 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
13 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
14 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
15 call the car license plate numbers in those days. I would write the
16 numbers down in my little book and compare notes with the other kids
17 to see how many region codes we had seen and if we had seen some
18 exotic or special region codes and numbers. It was a fun game to pass
19 time, as we kids have plenty of it.&lt;/p&gt;
20
21 &lt;p&gt;A few days I came across
22 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
23 project&lt;/a&gt;, a free software project to automatically discover and
24 report license plates in images and video streams, and provide the
25 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
26 such system for a while now, because I believe it is a bad idea that the
27 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
28 number plate recognition&lt;/a&gt; tool only is available in the hands of
29 the powerful, and want it to be available also for the powerless to
30 even the score when it comes to surveillance and sousveillance. I
31 discovered the developer
32 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
33 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
34 help him get into into shape to get it uploaded into the Debian
35 archive.&lt;/p&gt;
36
37 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
38 it into Debian, where it currently
39 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
40 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
41
42 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
43 for the common folks, ie those not running a large government
44 surveillance system? Well, I plan to put it in a computer on my bike
45 and in my car, tracking the cars nearby and allowing me to be notified
46 when number plates on my watch list are discovered. Another use case
47 was suggested by a friend of mine, who wanted to set it up at his home
48 to open the car port automatically when it discovered the plate on his
49 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
50 capable of placing his license plate number of a piece of cardboard to
51 open his car port, men replied that it was always unlocked anyway. I
52 guess for such use case it make sense. I am sure there are other use
53 cases too, for those with imagination and a vision.&lt;/p&gt;
54
55 &lt;p&gt;If you want to build your own version of the Debian package, check
56 out the upstream git source and symlink ./distros/debian to ./debian/
57 before running &quot;debuild&quot; to build the source. Or wait a bit until the
58 package show up in unstable.&lt;/p&gt;
59 </description>
60 </item>
61
62 <item>
63 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
64 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
65 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
66 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
67 <description>&lt;p&gt;Around three years ago, I created
68 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
69 system&lt;/a&gt; to get a more practical solution in Debian for handing
70 hardware related packages. A GUI system in the isenkram package will
71 present a pop-up dialog when some hardware dongle supported by
72 relevant packages in Debian is inserted into the machine. The same
73 lookup mechanism to detect packages is available as command line
74 tools in the isenkram-cli package. In addition to mapping hardware,
75 it will also map kernel firmware files to packages and make it easy to
76 install needed firmware packages automatically. The key for this
77 system to work is a good way to map hardware to packages, in other
78 words, allow packages to announce what hardware they will work
79 with.&lt;/p&gt;
80
81 &lt;p&gt;I started by providing data files in the isenkram source, and
82 adding code to download the latest version of these data files at run
83 time, to ensure every user had the most up to date mapping available.
84 I also added support for storing the mapping in the Packages file in
85 the apt repositories, but did not push this approach because while I
86 was trying to figure out how to best store hardware/package mappings,
87 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
88 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
89 add the hardware mapping into that data set to be able to use
90 appstream as a data source, and this was accepted at least for the
91 Debian version of appstream.&lt;/p&gt;
92
93 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
94 and today I uploaded a new version 0.20 of isenkram adding support for
95 appstream as a data source for mapping hardware to packages. The only
96 package so far using appstream to announce its hardware support is my
97 pymissile package. I got help from Matthias Klumpp with figuring out
98 how do add the required
99 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
100 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
101 this content:&lt;/p&gt;
102
103 &lt;blockquote&gt;&lt;pre&gt;
104 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
105 &amp;lt;component&amp;gt;
106 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
107 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
108 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
109 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
110 &amp;lt;description&amp;gt;
111 &amp;lt;p&amp;gt;
112 Pymissile provides a curses interface to control an original
113 Marks and Spencer / Striker USB Missile Launcher, as well as a
114 motion control script to allow a webcamera to control the
115 launcher.
116 &amp;lt;/p&amp;gt;
117 &amp;lt;/description&amp;gt;
118 &amp;lt;provides&amp;gt;
119 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
120 &amp;lt;/provides&amp;gt;
121 &amp;lt;/component&amp;gt;
122 &lt;/pre&gt;&lt;/blockquote&gt;
123
124 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
125 which is a glob style match rule for hardware specific strings
126 (modalias strings) provided by the Linux kernel. In this case, it
127 will map to all USB devices with vendor code 1130 and product code
128 0202.&lt;/p&gt;
129
130 &lt;p&gt;Note, it is important that the license of all the metadata files
131 are compatible to have permissions to aggregate them into archive wide
132 appstream files. Matthias suggested to use MIT or BSD licenses for
133 these files. A challenge is figuring out a good id for the data, as
134 it is supposed to be globally unique and shared across distributions
135 (in other words, best to coordinate with upstream what to use). But
136 it can be changed later or, so we went with the package name as
137 upstream for this project is dormant.&lt;/p&gt;
138
139 &lt;p&gt;To get the metadata file installed in the correct location for the
140 mirror update scripts to pick it up and include its content the
141 appstream data source, the file must be installed in the binary
142 package under /usr/share/appdata/. I did this by adding the following
143 line to debian/pymissile.install:&lt;/p&gt;
144
145 &lt;blockquote&gt;&lt;pre&gt;
146 debian/pymissile.metainfo.xml usr/share/appdata
147 &lt;/pre&gt;&lt;/blockquote&gt;
148
149 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
150 all packages useful on the current computer automatically, and the GUI
151 pop-up handler will propose to install the package not already
152 installed if a hardware dongle is inserted into the machine in
153 question.&lt;/p&gt;
154
155 &lt;p&gt;Details of the modalias field in appstream is available from the
156 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
157
158 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
159 try running this command on the command line:&lt;/p&gt;
160
161 &lt;blockquote&gt;&lt;pre&gt;
162 cat $(find /sys/devices/|grep modalias)
163 &lt;/pre&gt;&lt;/blockquote&gt;
164
165 &lt;p&gt;To learn more about the isenkram system, please check out
166 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
167 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
168 </description>
169 </item>
170
171 <item>
172 <title>The GNU General Public License is not magic pixie dust</title>
173 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
175 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
176 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
177 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
178 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
179 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
180 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
181
182 &lt;blockquote&gt;
183
184 &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;
185
186 &lt;blockquote&gt;
187 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
188
189 The first step is to choose a
190 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
191 code.&lt;br/&gt;
192
193 The next step is, when someone fails to follow that copyleft license,
194 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
195
196 and its a simple fact of our modern society that such type of
197 work&lt;br/&gt;
198
199 is incredibly expensive to do and incredibly difficult to do.
200 &lt;/blockquote&gt;
201
202 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
203 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
204 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
205 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
206
207 &lt;p&gt;As the Debian Website
208 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
209 &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;
210 imply, public domain and permissively licensed software can lead to
211 the production of more proprietary software as people discover useful
212 software, extend it and or incorporate it into their hardware or
213 software products. Copyleft licenses such as the GNU GPL were created
214 to close off this avenue to the production of proprietary software but
215 such licenses are not enough. With the ongoing adoption of Free
216 Software by individuals and groups, inevitably the community&#39;s
217 expectations of license compliance are violated, usually out of
218 ignorance of the way Free Software works, but not always. As Karen
219 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
220 Freedom&quot;&gt;FaiF&lt;/a&gt;
221 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
222 copyleft is nothing if no-one is willing and able to stand up in court
223 to protect it. The reality of today&#39;s world is that legal
224 representation is expensive, difficult and time consuming. With
225 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
226 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
227 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
228 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
229 of the Linux project, Debian and other groups against GPL violations.
230 In March the SFC supported a
231 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
232 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
233 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
234 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
235 kernel. Since then two of their sponsors pulled corporate funding and
236 conferences
237 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
238 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
239 less on corporate funding and more on the broad community of
240 individuals who support Free Software and copyleft. So the SFC has
241 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
242 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
243 a community of folks who stand up for copyleft and the GPL by
244 supporting their work on promoting and supporting copyleft and Free
245 Software.&lt;/p&gt;
246
247 &lt;p&gt;If you support Free Software,
248 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
249 what the SFC do, agree with their
250 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
251 principles&lt;/a&gt;, are happy about their
252 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
253 work on a project that is an SFC
254 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
255 just want to stand up for copyleft, please join
256 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
257 Allan Webber&lt;/a&gt;,
258 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
259 Smith&lt;/a&gt;,
260 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
261 Bacon&lt;/a&gt;, myself and
262 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
263 becoming a
264 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
265 next week your donation will be
266 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
267 by an anonymous donor. Please also consider asking your employer to
268 match your donation or become a sponsor of SFC. Don&#39;t forget to
269 spread the word about your support for SFC via email, your blog and or
270 social media accounts.&lt;/p&gt;
271
272 &lt;/blockquote&gt;
273
274 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
275 of Software Freedom Conservancy myself. Perhaps you should be a
276 supporter too?&lt;/p&gt;
277 </description>
278 </item>
279
280 <item>
281 <title>PGP key transition statement for key EE4E02F9</title>
282 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
283 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
284 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
285 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
286 set it up properly. I wanted to generate it offline and have it
287 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
288 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
289 time to sit down with an offline machine almost took forever. But
290 finally I&#39;ve been able to complete the process, and have now moved
291 from my old GPG key to a new GPG key. See
292 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
293 full transition statement, signed with both my old and new key&lt;/a&gt; for
294 the details. This is my new key:&lt;/p&gt;
295
296 &lt;pre&gt;
297 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]
298 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
299 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
300 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
301 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
302 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
303 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
304 &lt;/pre&gt;
305
306 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
307 my old key.&lt;/p&gt;
308
309 &lt;p&gt;If you signed my old key
310 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
311 I&#39;d very much appreciate a signature on my new key, details and
312 instructions in the transition statement. I m happy to reciprocate if
313 you have a similarly signed transition statement to present.&lt;/p&gt;
314 </description>
315 </item>
316
317 <item>
318 <title>The life and death of a laptop battery</title>
319 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
320 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
321 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
322 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
323 But this do not last. The last few laptops gave me a feeling that
324 within a year, the life time is just a fraction of what it used to be,
325 and it slowly become painful to use the laptop without power connected
326 all the time. Because of this, when I got a new Thinkpad X230 laptop
327 about two years ago, I decided to monitor its battery state to have
328 more hard facts when the battery started to fail.&lt;/p&gt;
329
330 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
331
332 &lt;p&gt;First I tried to find a sensible Debian package to record the
333 battery status, assuming that this must be a problem already handled
334 by someone else. I found
335 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
336 which collects statistics from the battery, but it was completely
337 broken. I sent a few suggestions to the maintainer, but decided to
338 write my own collector as a shell script while I waited for feedback
339 from him. Via
340 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
341 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
342 discovered
343 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
344 available in Debian.&lt;/p&gt;
345
346 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
347 battery stats ever since. Now my
348 /var/log/hjemmenett-battery-status.log file contain around 115,000
349 measurements, from the time the battery was working great until now,
350 when it is unable to charge above 7% of original capacity. My
351 collector shell script is quite simple and look like this:&lt;/p&gt;
352
353 &lt;pre&gt;
354 #!/bin/sh
355 # Inspired by
356 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
357 # See also
358 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
359 logfile=/var/log/hjemmenett-battery-status.log
360
361 files=&quot;manufacturer model_name technology serial_number \
362 energy_full energy_full_design energy_now cycle_count status&quot;
363
364 if [ ! -e &quot;$logfile&quot; ] ; then
365 (
366 printf &quot;timestamp,&quot;
367 for f in $files; do
368 printf &quot;%s,&quot; $f
369 done
370 echo
371 ) &gt; &quot;$logfile&quot;
372 fi
373
374 log_battery() {
375 # Print complete message in one echo call, to avoid race condition
376 # when several log processes run in parallel.
377 msg=$(printf &quot;%s,&quot; $(date +%s); \
378 for f in $files; do \
379 printf &quot;%s,&quot; $(cat $f); \
380 done)
381 echo &quot;$msg&quot;
382 }
383
384 cd /sys/class/power_supply
385
386 for bat in BAT*; do
387 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
388 done
389 &lt;/pre&gt;
390
391 &lt;p&gt;The script is called when the power management system detect a
392 change in the power status (power plug in or out), and when going into
393 and out of hibernation and suspend. In addition, it collect a value
394 every 10 minutes. This make it possible for me know when the battery
395 is discharging, charging and how the maximum charge change over time.
396 The code for the Debian package
397 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
398 available on github&lt;/a&gt;.&lt;/p&gt;
399
400 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
401
402 &lt;pre&gt;
403 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
404 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
405 [...]
406 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
407 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
408 &lt;/pre&gt;
409
410 &lt;p&gt;I wrote a small script to create a graph of the charge development
411 over time. This graph depicted above show the slow death of my laptop
412 battery.&lt;/p&gt;
413
414 &lt;p&gt;But why is this happening? Why are my laptop batteries always
415 dying in a year or two, while the batteries of space probes and
416 satellites keep working year after year. If we are to believe
417 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
418 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
419 chance, and the fix is to not charge the Lithium-ion batteries to 100%
420 all the time, but to stay below 90% of full charge most of the time.
421 I&#39;ve been told that the Tesla electric cars
422 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
423 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
424 100% when preparing for a longer trip (not that I would want a car
425 like Tesla where rights to privacy is abandoned, but that is another
426 story), which I guess is the option we should have for laptops on
427 Linux too.&lt;/p&gt;
428
429 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
430 stop charging at 80%, unless requested to charge to 100% once in
431 preparation for a longer trip? I found
432 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
433 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
434 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
435 load).&lt;/p&gt;
436
437 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
438 at the start. I also wonder why the &quot;full capacity&quot; increases some
439 times, and if it is possible to repeat the process to get the battery
440 back to design capacity. And I wonder if the discharge and charge
441 speed change over time, or if this stay the same. I did not yet try
442 to write a tool to calculate the derivative values of the battery
443 level, but suspect some interesting insights might be learned from
444 those.&lt;/p&gt;
445
446 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
447 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
448 packages instead of the tp-smapi-dkms package I had tried to use
449 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
450 and stop. I&#39;ve done so now, but expect my existing battery is toast
451 and need to be replaced. The proposal is unfortunately Thinkpad
452 specific.&lt;/p&gt;
453 </description>
454 </item>
455
456 <item>
457 <title>New laptop - some more clues and ideas based on feedback</title>
458 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
460 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
461 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
462 need for a new laptop, and provided very useful feedback. I wish to
463 thank every one of these. Several pointed me to the possibility of
464 fixing my X230, and I am already in the process of getting Lenovo to
465 do so thanks to the on site, next day support contract covering the
466 machine. But the battery is almost useless (I expect to replace it
467 with a non-official battery) and I do not expect the machine to live
468 for many more years, so it is time to plan its replacement. If I did
469 not have a support contract, it was suggested to find replacement parts
470 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
471 might present a language barrier as I do not understand French.&lt;/p&gt;
472
473 &lt;p&gt;One tip I got was to use the
474 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
475 compare laptop models. It seem to have more models available than
476 prisjakt.no. Another tip I got from someone I know have similar
477 keyboard preferences was that the HP EliteBook 840 keyboard is not
478 very good, and this matches my experience with earlier EliteBook
479 keyboards I tested. Because of this, I will not consider it any further.
480
481 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
482 newest Thinkpad X model. The keyboard reintroduces mouse buttons
483 (which is missing from the X240), and is working fairly well with
484 Debian Sid/Unstable according to
485 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
486 got on the keyboard quality are not consistent. Some say the keyboard
487 is good, others say it is ok, while others say it is not very good.
488 Those with experience from X41 and and X60 agree that the X250
489 keyboard is not as good as those trusty old laptops, and suggest I
490 keep and fix my X230 instead of upgrading, or get a used X230 to
491 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
492 activity and battery status, which is very convenient on my X230. I&#39;m
493 also told that the CPU fan is running very often, making it a bit
494 noisy. In any case, the X250 do not work out of the box with Debian
495 Stable/Jessie, one of my requirements.&lt;/p&gt;
496
497 &lt;p&gt;I have also gotten a few vendor proposals, one was
498 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
499 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
500 The latter look very attractive to me.&lt;/p&gt;
501
502 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
503 as I keep looking for a replacement.&lt;/p&gt;
504
505 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
506 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
507 different
508 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
509 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
510 </description>
511 </item>
512
513 <item>
514 <title>Time to find a new laptop, as the old one is broken after only two years</title>
515 <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>
516 <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>
517 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
518 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
519 replacement soon. The left 5 cm of the screen on my Thinkpad X230
520 started flickering yesterday, and I suspect the cause is a broken
521 cable, as changing the angle of the screen some times get rid of the
522 flickering.&lt;/p&gt;
523
524 &lt;p&gt;My requirements have not really changed since I bought it, and is
525 still as
526 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
527 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
528 good help from
529 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
530 where I could select at least a few of the requirements (mouse pin,
531 wifi, weight) and go through the rest manually. Three button mouse
532 and a good keyboard is not available as an option, and all the three
533 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
534 G2) lack three mouse buttons). It is also unclear to me how good the
535 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
536 the keyboard, even if the quality and robustness in the X series have
537 deteriorated since X41.&lt;/p&gt;
538
539 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
540 seem sensible to me? Are there better services around to search the
541 set of available laptops for features? Please send me an email if you
542 have suggestions.&lt;/p&gt;
543
544 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
545 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
546 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
547 </description>
548 </item>
549
550 <item>
551 <title>How to stay with sysvinit in Debian Jessie</title>
552 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
553 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
554 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
555 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
556 sysvinit as its boot system by default. But how can one keep using
557 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
558 courtesy of
559 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
560 Schubert&lt;/a&gt; and
561 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
562 McVittie&lt;/a&gt;.
563
564 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
565 keep sysvinit as your boot system, create a file
566 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
567 you upgrade:&lt;/p&gt;
568
569 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
570 Package: systemd-sysv
571 Pin: release o=Debian
572 Pin-Priority: -1
573 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
574
575 &lt;p&gt;This file content will tell apt and aptitude to not consider
576 installing systemd-sysv as part of any installation and upgrade
577 solution when resolving dependencies, and thus tell it to avoid
578 systemd as a default boot system. The end result should be that the
579 upgraded system keep using sysvinit.&lt;/p&gt;
580
581 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
582 get sysvinit installed by default (debootstrap used by
583 debian-installer have no option for this), but one can tell the
584 installer to switch to sysvinit before the first boot. Either by
585 using a kernel argument to the installer, or by adding a line to the
586 preseed file used. First, the kernel command line argument:
587
588 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
589 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
590 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
591
592 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
593
594 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
595 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
596 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
597
598 &lt;p&gt;One can of course also do this after the first boot by installing
599 the sysvinit-core package.&lt;/p&gt;
600
601 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
602 sysvinit boot sequence in Debian have several hardware specific bugs
603 on Linux caused by the fact that it is unpredictable when hardware
604 devices show up during boot. But on the other hand, the new default
605 boot system still have a few rough edges I hope will be fixed before
606 Jessie is released.&lt;/p&gt;
607
608 &lt;p&gt;Update 2014-11-26: Inspired by
609 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
610 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
611 line.&lt;/p&gt;
612 </description>
613 </item>
614
615 <item>
616 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
617 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
619 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
620 <description>&lt;p&gt;The right to communicate with your friends and family in private,
621 without anyone snooping, is a right every citicen have in a liberal
622 democracy. But this right is under serious attack these days.&lt;/p&gt;
623
624 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
625 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
626 the whisleblower Snowden) more expensive for Internet email,
627 is to deliver all email using SMTP via Tor. Such SMTP option would be
628 a nice addition to the FreedomBox project if we could send email
629 between FreedomBox machines without leaking metadata about the emails
630 to the people peeking on the wire. I
631 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
632 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
633 lot of useful feedback and suggestions. It also became obvious to me
634 that this was not a novel idea, as the same idea was tested and
635 documented by Johannes Berg as early as 2006, and both
636 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
637 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
638 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
639
640 &lt;p&gt;To implement such system one need to set up a Tor hidden service
641 providing the SMTP protocol on port 25, and use email addresses
642 looking like username@hidden-service-name.onion. With such addresses
643 the connections to port 25 on hidden-service-name.onion using Tor will
644 go to the correct SMTP server. To do this, one need to configure the
645 Tor daemon to provide the hidden service and the mail server to accept
646 emails for this .onion domain. To learn more about Exim configuration
647 in Debian and test the design provided by Johannes Berg in his FAQ, I
648 set out yesterday to create a Debian package for making it trivial to
649 set up such SMTP over Tor service based on Debian. Getting it to work
650 were fairly easy, and
651 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
652 source code for the Debian package&lt;/a&gt; is available from github. I
653 plan to move it into Debian if further testing prove this to be a
654 useful approach.&lt;/p&gt;
655
656 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
657 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
658 get rid of exim4). Install tor, clone the git repository mentioned
659 above, build the deb and install it on the machine. Next, run
660 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
661 the instructions to get the service up and running. Restart tor and
662 exim when it is done, and test mail delivery using swaks like
663 this:&lt;/p&gt;
664
665 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
666 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
667 --to fbx@dutlqrrmjhtfa3vp.onion
668 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
669
670 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
671 address with your own address to test your server. :)&lt;/p&gt;
672
673 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
674 easier and more automatic. Especially the tor setup need more work.
675 Also, the package include a tor-smtp tool written in C, but its task
676 should probably be rewritten in some script language to make the deb
677 architecture independent. It would probably also make the code easier
678 to review. The tor-smtp tool currently need to listen on a socket for
679 exim to talk to it and is started using xinetd. It would be better if
680 no daemon and no socket is needed. I suspect it is possible to get
681 exim to run a command line tool for delivery instead of talking to a
682 socket, and hope to figure out how in a future version of this
683 system.&lt;/p&gt;
684
685 &lt;p&gt;Until I wipe my test machine, I can be reached using the
686 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
687 SMTorP. :)&lt;/p&gt;
688 </description>
689 </item>
690
691 <item>
692 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
693 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
695 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
696 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
697 alioth.debian.org, you know the web interface is fairly slow to
698 operate. First you visit one web page, enter the moderation password
699 and get a new page shown with a list of all the messages to moderate
700 and various options for each email address. This take a while for
701 every list you moderate, and you need to do it regularly to do a good
702 job as a list moderator. But there is a quick alternative,
703 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
704 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
705 to moderate in a fraction of a second. Here is a test run on two
706 lists I recently took over:&lt;/p&gt;
707
708 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
709 % time listadmin xiph
710 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
711 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
712
713 real 0m1.709s
714 user 0m0.232s
715 sys 0m0.012s
716 %
717 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
718
719 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
720 there are no message in the moderation queue. Every morning I
721 currently moderate 68 mailman lists, and it normally take around two
722 minutes. When I took over the two pkg-xiph lists above a few days
723 ago, there were 400 emails waiting in the moderator queue. It took me
724 less than 15 minutes to process them all using the listadmin
725 program.&lt;/p&gt;
726
727 &lt;p&gt;If you install
728 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
729 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
730 with content like this, the moderation task is a breeze:&lt;/p&gt;
731
732 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
733 username username@example.org
734 spamlevel 23
735 default discard
736 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
737
738 password secret
739 adminurl https://{domain}/mailman/admindb/{list}
740 mailman-list@lists.example.com
741
742 password hidden
743 other-list@otherserver.example.org
744 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
745
746 &lt;p&gt;There are other options to set as well. Check the manual page to
747 learn the details.&lt;/p&gt;
748
749 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
750 the SSL certificate is self signed or not properly signed by a
751 generally accepted signing authority, you can set a environment
752 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
753
754 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
755 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
756 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
757
758 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
759 can provide an argument to the listadmin script like I do in the
760 initial screen dump (the xiph argument). Using an argument, only
761 lists matching the argument string will be processed. This make it
762 quick to accept messages if you notice the moderation request in your
763 email.&lt;/p&gt;
764
765 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
766 mailing lists, as I simply do not have time to spend on that if the
767 process was any slower. The listadmin program have saved me hours of
768 time I could spend elsewhere over the years. It truly is nice free
769 software.&lt;/p&gt;
770
771 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
772 activities, please send Bitcoin donations to my address
773 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
774
775 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
776 configuration example. Also, I&#39;ve been told that the
777 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
778 sure why.&lt;/p&gt;
779 </description>
780 </item>
781
782 <item>
783 <title>Debian Jessie, PXE and automatic firmware installation</title>
784 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
785 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
786 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
787 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
788 problem that the WiFi card require some firmware to work properly.
789 And it has been a pain to fix this using preseeding in Debian.
790 Normally something more is needed. But thanks to
791 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
792 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
793 to do this using simple preseeding.&lt;/p&gt;
794
795 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
796 firmware for the hardware found in the machine (actually, requested by
797 the kernel modules for the hardware). (It can also install user space
798 programs supporting the hardware detected, but that is not the focus
799 of this story.)&lt;/p&gt;
800
801 &lt;p&gt;To get this working in the default installation, two preeseding
802 values are needed. First, the isenkram-cli package must be installed
803 into the target chroot (aka the hard drive) before tasksel is executed
804 in the pkgsel step of the debian-installer system. This is done by
805 preseeding the base-installer/includes debconf value to include the
806 isenkram-cli package. The package name is next passed to debootstrap
807 for installation. With the isenkram-cli package in place, tasksel
808 will automatically use the isenkram tasks to detect hardware specific
809 packages for the machine being installed and install them, because
810 isenkram-cli contain tasksel tasks.&lt;/p&gt;
811
812 &lt;p&gt;Second, one need to enable the non-free APT repository, because
813 most firmware unfortunately is non-free. This is done by preseeding
814 the apt-mirror-setup step. This is unfortunate, but for a lot of
815 hardware it is the only option in Debian.&lt;/p&gt;
816
817 &lt;p&gt;The end result is two lines needed in your preseeding file to get
818 firmware installed automatically by the installer:&lt;/p&gt;
819
820 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
821 base-installer base-installer/includes string isenkram-cli
822 apt-mirror-setup apt-setup/non-free boolean true
823 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
824
825 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
826 both firmware and user space packages when using this method. It also
827 do not work well, so use version 0.15 or later. Installing both
828 firmware and user space packages might give you a bit more than you
829 want, so I decided to split the tasksel task in two, one for firmware
830 and one for user space programs. The firmware task is enabled by
831 default, while the one for user space programs is not. This split is
832 implemented in the package currently in unstable.&lt;/p&gt;
833
834 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
835 this recipe work for you. :)&lt;/p&gt;
836
837 &lt;p&gt;So, I bet you are wondering, how can this work. First and
838 foremost, it work because tasksel is modular, and driven by whatever
839 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
840 isenkram-cli package place two files for tasksel to find. First there
841 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
842
843 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
844 Task: isenkram-packages
845 Section: hardware
846 Description: Hardware specific packages (autodetected by isenkram)
847 Based on the detected hardware various hardware specific packages are
848 proposed.
849 Test-new-install: show show
850 Relevance: 8
851 Packages: for-current-hardware
852
853 Task: isenkram-firmware
854 Section: hardware
855 Description: Hardware specific firmware packages (autodetected by isenkram)
856 Based on the detected hardware various hardware specific firmware
857 packages are proposed.
858 Test-new-install: mark show
859 Relevance: 8
860 Packages: for-current-hardware-firmware
861 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
862
863 &lt;p&gt;The key parts are Test-new-install which indicate how the task
864 should be handled and the Packages line referencing to a script in
865 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
866 list of packages to install. The for-current-hardware-firmware script
867 look like this to list relevant firmware for the machine:
868
869 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
870 #!/bin/sh
871 #
872 PATH=/usr/sbin:$PATH
873 export PATH
874 isenkram-autoinstall-firmware -l
875 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
876
877 &lt;p&gt;With those two pieces in place, the firmware is installed by
878 tasksel during the normal d-i run. :)&lt;/p&gt;
879
880 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
881 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
882 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
883 install.&lt;/p&gt;
884
885 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
886 pilots in testing this feature, as isenkram is used there now to
887 install firmware, replacing the earlier scripts.&lt;/p&gt;
888 </description>
889 </item>
890
891 <item>
892 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
893 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
895 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
896 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
897 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
898 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
899 on a screen normally showing the bread types and prizes:&lt;/p&gt;
900
901 &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;
902
903 &lt;p&gt;If it had booted as it was supposed to, I would never had known
904 about this hidden Linux installation. It is interesting what
905 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
906 </description>
907 </item>
908
909 <item>
910 <title>New lsdvd release version 0.17 is ready</title>
911 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
913 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
914 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
915 got a new set of developers a few weeks ago, after the original
916 developer decided to step down and pass the project to fresh blood.
917 This project is now maintained by Petter Reinholdtsen and Steve
918 Dibb.&lt;/p&gt;
919
920 &lt;p&gt;I just wrapped up
921 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
922 new lsdvd release&lt;/a&gt;, available in git or from
923 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
924 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
925 0.17.&lt;/p&gt;
926
927 &lt;ul&gt;
928
929 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
930 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
931 non-existant, to work around additional copy protection&lt;/li&gt;
932 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
933 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
934 &lt;li&gt;Fix include orders&lt;/li&gt;
935 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
936 &lt;li&gt;Fix the chapter count&lt;/li&gt;
937 &lt;li&gt;Make sure the array size and the array limit used when initialising
938 the palette size is the same.&lt;/li&gt;
939 &lt;li&gt;Fix array printing.&lt;/li&gt;
940 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
941 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
942 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
943 with more GCC compiler warnings.&lt;/li&gt;
944
945 &lt;/ul&gt;
946
947 &lt;p&gt;This change bring together patches for lsdvd in use in various
948 Linux and Unix distributions, as well as patches submitted to the
949 project the last nine years. Please check it out. :)&lt;/p&gt;
950 </description>
951 </item>
952
953 <item>
954 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
955 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
957 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
958 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
959 project&lt;/a&gt; provide a Linux solution for schools, including a
960 powerful desktop with education software, a central server providing
961 web pages, user database, user home directories, central login and PXE
962 boot of both clients without disk and the installation to install Debian
963 Edu on machines with disk (and a few other services perhaps to small
964 to mention here). We in the Debian Edu team are currently working on
965 the Jessie based version, trying to get everything in shape before the
966 freeze, to avoid having to maintain our own package repository in the
967 future. The
968 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
969 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
970 work left. Some fatal problems block testing, breaking the installer,
971 but it is possible to work around these to get anyway. Here is a
972 recipe on how to get the installation limping along.&lt;/p&gt;
973
974 &lt;p&gt;First, download the test ISO via
975 &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;,
976 &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;
977 or rsync (use
978 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
979 The ISO build was broken on Tuesday, so we do not get a new ISO every
980 12 hours or so, but thankfully the ISO we already got we are able to
981 install with some tweaking.&lt;/p&gt;
982
983 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
984 (use Alt-Ctrl-F2), run&lt;/p&gt;
985
986 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
987 nano /usr/bin/edu-eatmydata-install
988 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
989
990 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
991 optimization. Return to the installation, select the profile you want
992 and continue. Without this change, exim4-config will fail to install
993 due to a known bug in eatmydata.&lt;/p&gt;
994
995 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
996 this do not work, figure out what your correct value would be. All my
997 test machines need /dev/sda, so I have no advice if it do not fit
998 your need.&lt;/p&gt;
999
1000 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1001 root after the initial boot from hard drive, and install the
1002 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1003 or mate. If you want several desktop options, install more than one
1004 metapackage. Once this is done, reboot and you should have a working
1005 graphical login screen. This workaround should no longer be needed
1006 once the education-tasks package version 1.801 enter testing in two
1007 days.&lt;/p&gt;
1008
1009 &lt;p&gt;I believe the ISO build will start working on two days when the new
1010 tasksel package enter testing and Steve McIntyre get a chance to
1011 update the debian-cd git repository. The eatmydata, grub and desktop
1012 issues are already fixed in unstable and testing, and should show up
1013 on the ISO as soon as the ISO build start working again. Well the
1014 eatmydata optimization is really just disabled. The proper fix
1015 require an upload by the eatmydata maintainer applying the patch
1016 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1017 The rest have proper fixes in unstable.&lt;/p&gt;
1018
1019 &lt;p&gt;I hope this get you going with the installation testing, as we are
1020 quickly running out of time trying to get our Jessie based
1021 installation ready before the distribution freeze in a month.&lt;/p&gt;
1022 </description>
1023 </item>
1024
1025 <item>
1026 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1027 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1028 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1029 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1030 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1031 to handle my fairly large DVD collection. It is a nice command line
1032 tool to get details about a DVD, like title, tracks, track length,
1033 etc, in XML, Perl or human readable format. But lsdvd have not seen
1034 any new development since 2006 and had a few irritating bugs affecting
1035 its use with some DVDs. Upstream seemed to be dead, and in January I
1036 sent a small probe asking for a version control repository for the
1037 project, without any reply. But I use it regularly and would like to
1038 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1039 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1040 the project admin, and after getting a reply from him explaining that
1041 he was no longer interested in the project, I asked if I could take
1042 over. And yesterday, I became project admin.&lt;/p&gt;
1043
1044 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1045 maintainer interested in joining forces to maintain the upstream
1046 project, and I hope we can get a new release out fairly quickly,
1047 collecting the patches spread around on the internet into on place.
1048 I&#39;ve added the relevant Debian patches to the freshly created git
1049 repository, and expect the Gentoo patches to make it too. If you got
1050 a DVD collection and care about command line tools, check out
1051 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1052 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1053 list&lt;/a&gt;. :)&lt;/p&gt;
1054 </description>
1055 </item>
1056
1057 <item>
1058 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1059 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1061 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1062 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1063 a lot quicker. When we install more than 2000 packages in
1064 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1065 tasksel in the installer, unpacking the binary packages take forever.
1066 A part of the slow I/O issue was discussed in
1067 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1068 much file system sync-ing done by dpkg, which is the package
1069 responsible for unpacking the binary packages. Other parts (like code
1070 executed by postinst scripts) might also sync to disk during
1071 installation. All this sync-ing to disk do not really make sense to
1072 me. If the machine crash half-way through, I start over, I do not try
1073 to salvage the half installed system. So the failure sync-ing is
1074 supposed to protect against, hardware or system crash, is not really
1075 relevant while the installer is running.&lt;/p&gt;
1076
1077 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1078 system sync()-ing in a fairly non-intrusive way, without the need to
1079 change the code in several packages. The idea is not new, but I have
1080 not heard anyone propose the approach using dpkg-divert before. It
1081 depend on the small and clever package
1082 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1083 uses LD_PRELOAD to replace the system functions for syncing data to
1084 disk with functions doing nothing, thus allowing programs to live
1085 dangerous while speeding up disk I/O significantly. Instead of
1086 modifying the implementation of dpkg, apt and tasksel (which are the
1087 packages responsible for selecting, fetching and installing packages),
1088 it occurred to me that we could just divert the programs away, replace
1089 them with a simple shell wrapper calling
1090 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1091 Two days ago I decided to test the idea, and wrapped up a simple
1092 implementation for the Debian Edu udeb.&lt;/p&gt;
1093
1094 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1095 time of the pkgsel step (installing tasks) from 64 to less than 44
1096 minutes (20 minutes shaved off the installation) on an old Dell
1097 Latitude D505 machine. I am not quite sure what the optimised time
1098 would have been, as I messed up the testing a bit, causing the debconf
1099 priority to get low enough for two questions to pop up during
1100 installation. As soon as I saw the questions I moved the installation
1101 along, but do not know how long the question were holding up the
1102 installation. I did some more measurements using Debian Edu Jessie,
1103 and got these results. The time measured is the time stamp in
1104 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1105 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1106 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1107 timing thus do not depend on how quickly the user handle the tasksel
1108 dialog.&lt;/p&gt;
1109
1110 &lt;p&gt;&lt;table&gt;
1111
1112 &lt;tr&gt;
1113 &lt;th&gt;Machine/setup&lt;/th&gt;
1114 &lt;th&gt;Original tasksel&lt;/th&gt;
1115 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1116 &lt;th&gt;Reduction&lt;/th&gt;
1117 &lt;/tr&gt;
1118
1119 &lt;tr&gt;
1120 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1121 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1122 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1123 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1124 &lt;/tr&gt;
1125
1126 &lt;tr&gt;
1127 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1128 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1129 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1130 &lt;td&gt;23 min 40%&lt;/td&gt;
1131 &lt;/tr&gt;
1132
1133 &lt;tr&gt;
1134 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1135 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1136 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1137 &lt;td&gt;11 min 50%&lt;/td&gt;
1138 &lt;/tr&gt;
1139
1140 &lt;tr&gt;
1141 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1142 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1143 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1144 &lt;td&gt;2 min 33%&lt;/td&gt;
1145 &lt;/tr&gt;
1146
1147 &lt;tr&gt;
1148 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1149 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1150 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1151 &lt;td&gt;4 min 21%&lt;/td&gt;
1152 &lt;/tr&gt;
1153
1154 &lt;/table&gt;&lt;/p&gt;
1155
1156 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1157 time is spent downloading packages. The connection to the Internet
1158 was 100Mbit/s during testing, so downloading should not be a
1159 significant factor in the measurement. Download typically took a few
1160 seconds to a few minutes, depending on the amount of packages being
1161 installed.&lt;/p&gt;
1162
1163 &lt;p&gt;The speedup is implemented by using two hooks in
1164 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1165 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1166 finish-install.d hook to remove the divert at the end of the
1167 installation. I picked the pre-pkgsel.d hook instead of the
1168 post-base-installer.d hook because I test using an ISO without the
1169 eatmydata package included, and the post-base-installer.d hook in
1170 Debian Edu can only operate on packages included in the ISO. The
1171 negative effect of this is that I am unable to activate this
1172 optimization for the kernel installation step in d-i. If the code is
1173 moved to the post-base-installer.d hook, the speedup would be larger
1174 for the entire installation.&lt;/p&gt;
1175
1176 &lt;p&gt;I&#39;ve implemented this in the
1177 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1178 git repository, and plan to provide the optimization as part of the
1179 Debian Edu installation. If you want to test this yourself, you can
1180 create two files in the installer (or in an udeb). One shell script
1181 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1182
1183 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1184 #!/bin/sh
1185 set -e
1186 . /usr/share/debconf/confmodule
1187 info() {
1188 logger -t my-pkgsel &quot;info: $*&quot;
1189 }
1190 error() {
1191 logger -t my-pkgsel &quot;error: $*&quot;
1192 }
1193 override_install() {
1194 apt-install eatmydata || true
1195 if [ -x /target/usr/bin/eatmydata ] ; then
1196 for bin in dpkg apt-get aptitude tasksel ; do
1197 file=/usr/bin/$bin
1198 # Test that the file exist and have not been diverted already.
1199 if [ -f /target$file ] ; then
1200 info &quot;diverting $file using eatmydata&quot;
1201 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1202 &gt; /target$file.edu
1203 chmod 755 /target$file.edu
1204 in-target dpkg-divert --package debian-edu-config \
1205 --rename --quiet --add $file
1206 ln -sf ./$bin.edu /target$file
1207 else
1208 error &quot;unable to divert $file, as it is missing.&quot;
1209 fi
1210 done
1211 else
1212 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1213 fi
1214 }
1215
1216 override_install
1217 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1218
1219 &lt;p&gt;To clean up, another shell script should go into
1220 /usr/lib/finish-install.d/ with code like this:
1221
1222 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1223 #! /bin/sh -e
1224 . /usr/share/debconf/confmodule
1225 error() {
1226 logger -t my-finish-install &quot;error: $@&quot;
1227 }
1228 remove_install_override() {
1229 for bin in dpkg apt-get aptitude tasksel ; do
1230 file=/usr/bin/$bin
1231 if [ -x /target$file.edu ] ; then
1232 rm /target$file
1233 in-target dpkg-divert --package debian-edu-config \
1234 --rename --quiet --remove $file
1235 rm /target$file.edu
1236 else
1237 error &quot;Missing divert for $file.&quot;
1238 fi
1239 done
1240 sync # Flush file buffers before continuing
1241 }
1242
1243 remove_install_override
1244 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1245
1246 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1247 edu-eatmydata-install and call it from the pre-pkgsel.d and
1248 finish-install.d scripts.&lt;/p&gt;
1249
1250 &lt;p&gt;By now you might ask if this change should get into the normal
1251 Debian installer too? I suspect it should, but am not sure the
1252 current debian-installer coordinators find it useful enough. It also
1253 depend on the side effects of the change. I&#39;m not aware of any, but I
1254 guess we will see if the change is safe after some more testing.
1255 Perhaps there is some package in Debian depending on sync() and
1256 fsync() having effect? Perhaps it should go into its own udeb, to
1257 allow those of us wanting to enable it to do so without affecting
1258 everyone.&lt;/p&gt;
1259
1260 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1261 will break installation of all programs using gnutls because of
1262 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1263 eatmydata package in Debian will solve it.&lt;/p&gt;
1264
1265 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1266 the optimization work again. And I have discovered that the
1267 dpkg-divert trick is not really needed and implemented a slightly
1268 simpler approach as part of the debian-edu-install package. See
1269 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1270
1271 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1272 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1273 triggering on i386 made it into testing, and broke this installation
1274 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1275 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1276 </description>
1277 </item>
1278
1279 <item>
1280 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1281 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1283 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1284 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1285 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1286 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1287 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1288 learn that there is a large set of publicly available key servers to
1289 use when looking for peoples public key. So far I have used
1290 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1291 were misbehaving, but those days are ended. The servers I have used
1292 up until yesterday have been slow and some times unavailable. I hope
1293 those problems are gone now.&lt;/p&gt;
1294
1295 &lt;p&gt;Behind the round robin DNS entry of the
1296 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1297 there is a pool of more than 100 keyservers which are checked every
1298 day to ensure they are well connected and up to date. It must be
1299 better than what I have used so far. :)&lt;/p&gt;
1300
1301 &lt;p&gt;Yesterdays speaker told me that the service is the default
1302 keyserver provided by the default configuration in GnuPG, but this do
1303 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1304
1305 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1306 line:&lt;/p&gt;
1307
1308 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1309 keyserver pool.sks-keyservers.net
1310 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1311
1312 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1313 entries in DNS. Just for fun, I did just that at work, so now every
1314 user of GnuPG at the University of Oslo should find a OpenGPG
1315 keyserver automatically should their need it:&lt;/p&gt;
1316
1317 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1318 % host -t srv _pgpkey-http._tcp.uio.no
1319 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1320 %
1321 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1322
1323 &lt;p&gt;Now if only
1324 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1325 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1326 very happy. It can look up a given key or search for a user ID, but I
1327 normally do not want that, but to find a trust path from my key to
1328 another key. Given a user ID or key ID, I would like to find (and
1329 download) the keys representing a signature path from my key to the
1330 key in question, to be able to get a trust path between the two keys.
1331 This is as far as I can tell not possible today. Perhaps something
1332 for a future version of the protocol?&lt;/p&gt;
1333 </description>
1334 </item>
1335
1336 <item>
1337 <title>From English wiki to translated PDF and epub via Docbook</title>
1338 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1340 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1341 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1342 project&lt;/a&gt; provide an instruction manual for teachers, system
1343 administrators and other users that contain useful tips for setting up
1344 and maintaining a Debian Edu installation. This text is about how the
1345 text processing of this manual is handled in the project.&lt;/p&gt;
1346
1347 &lt;p&gt;One goal of the project is to provide information in the native
1348 language of its users, and for this we need to handle translations.
1349 But we also want to make sure each language contain the same
1350 information, so for this we need a good way to keep the translations
1351 in sync. And we want it to be easy for our users to improve the
1352 documentation, avoiding the need to learn special formats or tools to
1353 contribute, and the obvious way to do this is to make it possible to
1354 edit the documentation using a web browser. We also want it to be
1355 easy for translators to keep the translation up to date, and give them
1356 help in figuring out what need to be translated. Here is the list of
1357 tools and the process we have found trying to reach all these
1358 goals.&lt;/p&gt;
1359
1360 &lt;p&gt;We maintain the authoritative source of our manual in the
1361 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1362 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1363 front page with references to the different chapters, several pages
1364 for each chapter, and finally one &quot;collection page&quot; gluing all the
1365 chapters together into one large web page (aka
1366 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1367 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1368 processing and translations. Thanks to the fact that the
1369 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1370 wiki.debian.org support exporting pages in
1371 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1372 the list of pages to export using the raw version of the AllInOne
1373 page, loop over each of them to generate a Docbook XML version of the
1374 manual. This process also download images and transform image
1375 references to use the locally downloaded images. The generated
1376 Docbook XML files are slightly broken, so some post-processing is done
1377 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1378 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1379 a handfull of images. The XML file can now be used to generate PDF, HTML
1380 and epub versions of the English manual. This is the basic step of
1381 our process, making PDF (using dblatex), HTML (using xsltproc) and
1382 epub (using dbtoepub) version from Docbook XML, and the resulting files
1383 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1384
1385 &lt;p&gt;But English documentation is not enough for us. We want translated
1386 documentation too, and we want to make it easy for translators to
1387 track the English original. For this we use the
1388 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1389 which allow us to transform the English Docbook XML file into a
1390 translation file (a .pot file), usable with the normal gettext based
1391 translation tools used by those translating free software. The pot
1392 file is used to create and maintain translation files (several .po
1393 files), which the translations update with the native language
1394 translations of all titles, paragraphs and blocks of text in the
1395 original. The next step is combining the original English Docbook XML
1396 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1397 create a translated Docbook XML file (in this case
1398 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1399 translated, if the translation is not complete) Docbook XML file can
1400 then be used like the original to create a PDF, HTML and epub version
1401 of the documentation.&lt;/p&gt;
1402
1403 &lt;p&gt;The translators use different tools to edit the .po files. We
1404 recommend using
1405 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1406 while some use emacs and vi, others can use web based editors like
1407 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1408 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1409 is where the .po file end up, in our git repository. Updated
1410 translations can either be committed directly to git, or submitted as
1411 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1412 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1413
1414 &lt;p&gt;One challenge is images, which both might need to be translated (if
1415 they show translated user applications), and are needed in different
1416 formats when creating PDF and HTML versions (epub is a HTML version in
1417 this regard). For this we transform the original PNG images to the
1418 needed density and format during build, and have a way to provide
1419 translated images by storing translated versions in
1420 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1421 package maintainers know more.&lt;/p&gt;
1422
1423 &lt;p&gt;If you wonder what the result look like, we provide
1424 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1425 of the documentation packages on the web&lt;/a&gt;. See for example the
1426 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1427 PDF version&lt;/a&gt; or the
1428 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1429 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1430 but perhaps it will be done in the future.&lt;/p&gt;
1431
1432 &lt;p&gt;To learn more, check out
1433 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1434 debian-edu-doc package&lt;/a&gt;,
1435 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1436 manual on the wiki&lt;/a&gt; and
1437 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1438 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1439 </description>
1440 </item>
1441
1442 <item>
1443 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1444 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1446 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1447 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1448 related packages relevant for the computer installed automatically.
1449 So I implemented one, using
1450 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1451 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1452 run tasksel as user root. You should be presented with a new option,
1453 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1454 select it, tasksel will install the packages isenkram claim is fit for
1455 the current hardware, hot pluggable or not.&lt;p&gt;
1456
1457 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1458 description, and the other is the script used to extract the list of
1459 packages to install. The first part is in
1460 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1461 this:&lt;/p&gt;
1462
1463 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1464 Task: isenkram
1465 Section: hardware
1466 Description: Hardware specific packages (autodetected by isenkram)
1467 Based on the detected hardware various hardware specific packages are
1468 proposed.
1469 Test-new-install: mark show
1470 Relevance: 8
1471 Packages: for-current-hardware
1472 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1473
1474 &lt;p&gt;The second part is in
1475 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1476 this:&lt;/p&gt;
1477
1478 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1479 #!/bin/sh
1480 #
1481 (
1482 isenkram-lookup
1483 isenkram-autoinstall-firmware -l
1484 ) | sort -u
1485 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1486
1487 &lt;p&gt;All in all, a very short and simple implementation making it
1488 trivial to install the hardware dependent package we all may want to
1489 have installed on our machines. I&#39;ve not been able to find a way to
1490 get tasksel to tell you exactly which packages it plan to install
1491 before doing the installation. So if you are curious or careful,
1492 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1493
1494 &lt;p&gt;The information about which packages are handling which hardware is
1495 fetched either from the isenkram package itself in
1496 /usr/share/isenkram/, from git.debian.org or from the APT package
1497 database (using the Modaliases header). The APT package database
1498 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1499 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1500 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1501 the python-apt code (bug
1502 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1503 workaround I was able to get rid of the file descriptor leak and
1504 reduce the memory leak from ~30 MiB per hardware detection down to
1505 around 2 MiB per hardware detection. It should make the desktop
1506 daemon a lot more useful. The fix is in version 0.7 uploaded to
1507 unstable today.&lt;/p&gt;
1508
1509 &lt;p&gt;I believe the current way of mapping hardware to packages in
1510 Isenkram is is a good draft, but in the future I expect isenkram to
1511 use the AppStream data source for this. A proposal for getting proper
1512 AppStream support into Debian is floating around as
1513 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1514 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1515 project&lt;/a&gt; will take place this summer to improve the situation. I
1516 look forward to seeing the result, and welcome patches for isenkram to
1517 start using the information when it is ready.&lt;/p&gt;
1518
1519 &lt;p&gt;If you want your package to map to some specific hardware, either
1520 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1521 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1522 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1523 package. See also
1524 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1525 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1526 the information will be migrated to AppStream eventually, but for the
1527 moment I got no better place to store it.&lt;/p&gt;
1528 </description>
1529 </item>
1530
1531 <item>
1532 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1533 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1534 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1535 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1536 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1537 project&lt;/a&gt; is working on providing the software and hardware to make
1538 it easy for non-technical people to host their data and communication
1539 at home, and being able to communicate with their friends and family
1540 encrypted and away from prying eyes. It is still going strong, and
1541 today a major mile stone was reached.&lt;/p&gt;
1542
1543 &lt;p&gt;Today, the last of the packages currently used by the project to
1544 created the system images were accepted into Debian Unstable. It was
1545 the freedombox-setup package, which is used to configure the images
1546 during build and on the first boot. Now all one need to get going is
1547 the build code from the freedom-maker git repository and packages from
1548 Debian. And once the freedombox-setup package enter testing, we can
1549 build everything directly from Debian. :)&lt;/p&gt;
1550
1551 &lt;p&gt;Some key packages used by Freedombox are
1552 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1553 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1554 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1555 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1556 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1557 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1558 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1559 are plans to integrate more packages into the setup. User
1560 documentation is maintained on the Debian wiki. Please
1561 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1562 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1563
1564 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1565 setup, run this on a Debian machine using a user with sudo rights to
1566 become root:&lt;/p&gt;
1567
1568 &lt;p&gt;&lt;pre&gt;
1569 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1570 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1571 u-boot-tools
1572 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1573 freedom-maker
1574 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1575 &lt;/pre&gt;&lt;/p&gt;
1576
1577 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1578 devices. See the README in the freedom-maker git repo for more
1579 details on the build. If you do not want all three images, trim the
1580 make line. Note that the virtualbox-image target is not really
1581 virtualbox specific. It create a x86 image usable in kvm, qemu,
1582 vmware and any other x86 virtual machine environment. You might need
1583 the version of vmdebootstrap in Jessie to get the build working, as it
1584 include fixes for a race condition with kpartx.&lt;/p&gt;
1585
1586 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1587 method, boot a Debian Wheezy ISO and use this boot argument to load
1588 the preseed values:&lt;/p&gt;
1589
1590 &lt;p&gt;&lt;pre&gt;
1591 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;
1592 &lt;/pre&gt;&lt;/p&gt;
1593
1594 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1595 it still work.&lt;/p&gt;
1596
1597 &lt;p&gt;If you wonder how to help, one task you could look at is using
1598 systemd as the boot system. It will become the default for Linux in
1599 Jessie, so we need to make sure it is usable on the Freedombox. I did
1600 a simple test a few weeks ago, and noticed dnsmasq failed to start
1601 during boot when using systemd. I suspect there are other problems
1602 too. :) To detect problems, there is a test suite included, which can
1603 be run from the plinth web interface.&lt;/p&gt;
1604
1605 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1606 us get the new release published. :) Please join us on
1607 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1608 irc.debian.org)&lt;/a&gt; and
1609 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1610 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1611 </description>
1612 </item>
1613
1614 <item>
1615 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1616 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1617 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1618 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1619 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1620 solution for use at home. My requirements are simple, it must be
1621 cheap and locally encrypted (in other words, I keep the encryption
1622 keys, the storage provider do not have access to my private files).
1623 One idea me and my friends had many years ago, before the cloud
1624 storage providers showed up, was to use Google mail as storage,
1625 writing a Linux block device storing blocks as emails in the mail
1626 service provided by Google, and thus get heaps of free space. On top
1627 of this one can add encryption, RAID and volume management to have
1628 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1629 I never found time to implement such system. But the last few weeks I
1630 have looked at a system called
1631 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1632 mounted network backed file system with the features I need.&lt;/p&gt;
1633
1634 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1635 handling several different storage providers, any with Amazon S3,
1636 Google Drive or OpenStack API. There are heaps of such storage
1637 providers. S3QL can also use a local directory as storage, which
1638 combined with sshfs allow for file storage on any ssh server. S3QL
1639 include support for encryption, compression, de-duplication, snapshots
1640 and immutable file systems, allowing me to mount the remote storage as
1641 a local mount point, look at and use the files as if they were local,
1642 while the content is stored in the cloud as well. This allow me to
1643 have a backup that should survive fire. The file system can not be
1644 shared between several machines at the same time, as only one can
1645 mount it at the time, but any machine with the encryption key and
1646 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1647
1648 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1649 package is included already. So to get started, run &lt;tt&gt;apt-get
1650 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1651 Greenqloud, after reading their nice recipe on
1652 &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
1653 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1654 in Iceland more than those in USA when it come to keeping my personal
1655 data safe and private, and thus would rather spend money on a company
1656 in Iceland. Another nice recipe is available from the article
1657 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1658 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1659 Admin magazine. When the provider is picked, figure out how to get
1660 the API key needed to connect to the storage API. With Greencloud,
1661 the key did not show up until I had added payment details to my
1662 account.&lt;/p&gt;
1663
1664 &lt;p&gt;Armed with the API access details, it is time to create the file
1665 system. First, create a new bucket in the cloud. This bucket is the
1666 file system storage area. I picked a bucket name reflecting the
1667 machine that was going to store data there, but any name will do.
1668 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1669 the API login and password, and a locally created password. Store it
1670 all in ~root/.s3ql/authinfo2 like this:
1671
1672 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1673 [s3c]
1674 storage-url: s3c://s.greenqloud.com:443/bucket-name
1675 backend-login: API-login
1676 backend-password: API-password
1677 fs-passphrase: local-password
1678 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1679
1680 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1681 but any sensible way to create a fairly random password should do it.
1682 Armed with these details, it is now time to run mkfs, entering the API
1683 details and password to create it:&lt;/p&gt;
1684
1685 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1686 # mkdir -m 700 /var/lib/s3ql-cache
1687 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1688 --ssl s3c://s.greenqloud.com:443/bucket-name
1689 Enter backend login:
1690 Enter backend password:
1691 Before using S3QL, make sure to read the user&#39;s guide, especially
1692 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1693 Enter encryption password:
1694 Confirm encryption password:
1695 Generating random encryption key...
1696 Creating metadata tables...
1697 Dumping metadata...
1698 ..objects..
1699 ..blocks..
1700 ..inodes..
1701 ..inode_blocks..
1702 ..symlink_targets..
1703 ..names..
1704 ..contents..
1705 ..ext_attributes..
1706 Compressing and uploading metadata...
1707 Wrote 0.00 MB of compressed metadata.
1708 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1709
1710 &lt;p&gt;The next step is mounting the file system to make the storage available.
1711
1712 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1713 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1714 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1715 Using 4 upload threads.
1716 Downloading and decompressing metadata...
1717 Reading metadata...
1718 ..objects..
1719 ..blocks..
1720 ..inodes..
1721 ..inode_blocks..
1722 ..symlink_targets..
1723 ..names..
1724 ..contents..
1725 ..ext_attributes..
1726 Mounting filesystem...
1727 # df -h /s3ql
1728 Filesystem Size Used Avail Use% Mounted on
1729 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1730 #
1731 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1732
1733 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1734 backups in it, and as the metadata used by rsync is downloaded at
1735 mount time, no network traffic (and storage cost) is triggered by
1736 running rsync. To unmount, one should not use the normal umount
1737 command, as this will not flush the cache to the cloud storage, but
1738 instead running the umount.s3ql command like this:
1739
1740 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1741 # umount.s3ql /s3ql
1742 #
1743 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1744
1745 &lt;p&gt;There is a fsck command available to check the file system and
1746 correct any problems detected. This can be used if the local server
1747 crashes while the file system is mounted, to reset the &quot;already
1748 mounted&quot; flag. This is what it look like when processing a working
1749 file system:&lt;/p&gt;
1750
1751 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1752 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1753 Using cached metadata.
1754 File system seems clean, checking anyway.
1755 Checking DB integrity...
1756 Creating temporary extra indices...
1757 Checking lost+found...
1758 Checking cached objects...
1759 Checking names (refcounts)...
1760 Checking contents (names)...
1761 Checking contents (inodes)...
1762 Checking contents (parent inodes)...
1763 Checking objects (reference counts)...
1764 Checking objects (backend)...
1765 ..processed 5000 objects so far..
1766 ..processed 10000 objects so far..
1767 ..processed 15000 objects so far..
1768 Checking objects (sizes)...
1769 Checking blocks (referenced objects)...
1770 Checking blocks (refcounts)...
1771 Checking inode-block mapping (blocks)...
1772 Checking inode-block mapping (inodes)...
1773 Checking inodes (refcounts)...
1774 Checking inodes (sizes)...
1775 Checking extended attributes (names)...
1776 Checking extended attributes (inodes)...
1777 Checking symlinks (inodes)...
1778 Checking directory reachability...
1779 Checking unix conventions...
1780 Checking referential integrity...
1781 Dropping temporary indices...
1782 Backing up old metadata...
1783 Dumping metadata...
1784 ..objects..
1785 ..blocks..
1786 ..inodes..
1787 ..inode_blocks..
1788 ..symlink_targets..
1789 ..names..
1790 ..contents..
1791 ..ext_attributes..
1792 Compressing and uploading metadata...
1793 Wrote 0.89 MB of compressed metadata.
1794 #
1795 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1796
1797 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1798 quick, about the same speed as local file access. Uploading large
1799 amount of data is to me limited by the bandwidth out of and into my
1800 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1801 which is very close to my upload speed, and downloading the same
1802 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1803 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1804 network, not the file system code. I do not know what a good cache
1805 size would be, but suspect that the cache should e larger than your
1806 working set.&lt;/p&gt;
1807
1808 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1809 time. If another machine try, it is told that the file system is
1810 busy:&lt;/p&gt;
1811
1812 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1813 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1814 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1815 Using 8 upload threads.
1816 Backend reports that fs is still mounted elsewhere, aborting.
1817 #
1818 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1819
1820 &lt;p&gt;The file content is uploaded when the cache is full, while the
1821 metadata is uploaded once every 24 hour by default. To ensure the
1822 file system content is flushed to the cloud, one can either umount the
1823 file system, or ask S3QL to flush the cache and metadata using
1824 s3qlctrl:
1825
1826 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1827 # s3qlctrl upload-meta /s3ql
1828 # s3qlctrl flushcache /s3ql
1829 #
1830 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1831
1832 &lt;p&gt;If you are curious about how much space your data uses in the
1833 cloud, and how much compression and deduplication cut down on the
1834 storage usage, you can use s3qlstat on the mounted file system to get
1835 a report:&lt;/p&gt;
1836
1837 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1838 # s3qlstat /s3ql
1839 Directory entries: 9141
1840 Inodes: 9143
1841 Data blocks: 8851
1842 Total data size: 22049.38 MB
1843 After de-duplication: 21955.46 MB (99.57% of total)
1844 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1845 Database size: 2.39 MB (uncompressed)
1846 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1847 #
1848 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1849
1850 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1851 storage. I did not try to locate them all, but am aware of at least
1852 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1853 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1854 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1855 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1856 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1857 accept payment in Bitcoin. Pick one that suit your need. Some of
1858 them provide several GiB of free storage, but the prize models are
1859 quite different and you will have to figure out what suits you
1860 best.&lt;/p&gt;
1861
1862 &lt;p&gt;While researching this blog post, I had a look at research papers
1863 and posters discussing the S3QL file system. There are several, which
1864 told me that the file system is getting a critical check by the
1865 science community and increased my confidence in using it. One nice
1866 poster is titled
1867 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1868 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1869 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1870 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1871 and Pamela Smith. Please have a look.&lt;/p&gt;
1872
1873 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1874 check out the mounted S3QL file system to see if it would be usable as
1875 a home directory (in other word, that it provided POSIX semantics when
1876 it come to locking and umask handling etc). Running
1877 &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
1878 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1879 no error was found. So the file system can be used for home
1880 directories, if one chooses to do so.&lt;/p&gt;
1881
1882 &lt;p&gt;If you do not want a locally file system, and want something that
1883 work without the Linux fuse file system, I would like to mention the
1884 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1885 provide locally encrypted backup using a command line client. It have
1886 a nicer access control system, where one can split out read and write
1887 access, allowing some systems to write to the backup and others to
1888 only read from it.&lt;/p&gt;
1889
1890 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1891 activities, please send Bitcoin donations to my address
1892 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1893 </description>
1894 </item>
1895
1896 <item>
1897 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1898 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1900 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1901 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1902 project&lt;/a&gt; is working on providing the software and hardware for
1903 making it easy for non-technical people to host their data and
1904 communication at home, and being able to communicate with their
1905 friends and family encrypted and away from prying eyes. It has been
1906 going on for a while, and is slowly progressing towards a new test
1907 release (0.2).&lt;/p&gt;
1908
1909 &lt;p&gt;And what day could be better than the Pi day to announce that the
1910 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1911 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1912 system), and can also be installed using a Debian installer preseed
1913 file. The Debian based Freedombox is now based on Debian Jessie,
1914 where most of the needed packages used are already present. Only one,
1915 the freedombox-setup package, is missing. To try to build your own
1916 boot image to test the current status, fetch the freedom-maker scripts
1917 and build using
1918 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1919 with a user with sudo access to become root:
1920
1921 &lt;pre&gt;
1922 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1923 freedom-maker
1924 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1925 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1926 u-boot-tools
1927 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1928 &lt;/pre&gt;
1929
1930 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1931 devices. See the README for more details on the build. If you do not
1932 want all three images, trim the make line. But note that thanks to &lt;a
1933 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1934 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1935 kpartx call.&lt;/p&gt;
1936
1937 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1938 method, boot a Debian Wheezy ISO and use this boot argument to load
1939 the preseed values:&lt;/p&gt;
1940
1941 &lt;pre&gt;
1942 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;
1943 &lt;/pre&gt;
1944
1945 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1946 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1947 currently hang while setting up APT sources. Killing the
1948 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1949 installation will get the installation going. This affect all
1950 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1951
1952 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1953 us get the new release published. :) Please join us on
1954 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1955 irc.debian.org)&lt;/a&gt; and
1956 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1957 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1958 </description>
1959 </item>
1960
1961 <item>
1962 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1963 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1964 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1965 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1966 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1967 innetgr tools, because I needed them in
1968 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1969 ng-utils, and it has served me well. I placed the project under the
1970 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1971 repository. But many years ago, the CVS repository was dropped (lost,
1972 not migrated to new hardware, not sure), and the project have lacked a
1973 proper home since then.&lt;/p&gt;
1974
1975 &lt;p&gt;Last summer, I had a look at the package and made a new release
1976 fixing a irritating crash bug, but was unable to store the changes in
1977 a proper source control system. I applied for a project on
1978 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1979 to follow up on it. Until today. :)&lt;/p&gt;
1980
1981 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1982 now have a new home, and a git repository with the highlight of the
1983 history of the project. I published all release tarballs and imported
1984 them into the git repository. As the project is really stable and not
1985 expected to gain new features any time soon, I decided to make a new
1986 release and call it 1.0. Visit the new project home on
1987 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1988 if you want to check it out. The new version is also uploaded into
1989 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1990 </description>
1991 </item>
1992
1993 <item>
1994 <title>Testing sysvinit from experimental in Debian Hurd</title>
1995 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1996 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1997 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1998 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1999 their changes into sysvinit, to allow them to use the normal sysvinit
2000 boot system instead of their old one. This follow up on the
2001 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2002 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2003 get Debian on Hurd working more like Debian on Linux. To get started,
2004 I downloaded a prebuilt hard disk image from
2005 &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;,
2006 and started it using virt-manager.&lt;/p&gt;
2007
2008 &lt;p&gt;The first think I had to do after logging in (root without any
2009 password) was to get the network operational. I followed
2010 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2011 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2012 commands as root to get the machine to accept a IP address from the
2013 kvm internal DHCP server:&lt;/p&gt;
2014
2015 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2016 settrans -fgap /dev/netdde /hurd/netdde
2017 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2018 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2019 dhclient /dev/eth0
2020 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2021
2022 &lt;p&gt;After this, the machine had internet connectivity, and I could
2023 upgrade it and install the sysvinit packages from experimental and
2024 enable it as the default boot system in Hurd.&lt;/p&gt;
2025
2026 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2027 running on the machine it for ssh login to work a password need to be
2028 set. Also, note that a bug somewhere in openssh on Hurd block
2029 compression from working. Remember to turn that off on the client
2030 side.&lt;/p&gt;
2031
2032 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2033 stuff:&lt;/p&gt;
2034
2035 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2036 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2037 deb http://http.debian.net/debian/ experimental main
2038 EOF
2039 apt-get update
2040 apt-get dist-upgrade
2041 apt-get install -t experimental initscripts sysv-rc sysvinit \
2042 sysvinit-core sysvinit-utils
2043 update-alternatives --config runsystem
2044 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2045
2046 &lt;p&gt;To reboot after switching boot system, you have to use
2047 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2048 yet a sysvinit process able to receive the signals from the normal
2049 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2050 upgrading every package and rebooting, the network come up with DHCP
2051 after boot as it should, and the settrans/pkill hack mentioned at the
2052 start is no longer needed. But for some strange reason, there are no
2053 longer any login prompt in the virtual console, so I logged in using
2054 ssh instead.
2055
2056 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2057 fail some times. No idea what the cause is, but hope the Hurd porters
2058 figure it out. At least Justus said on IRC (#debian-hurd on
2059 irc.debian.org) that they are aware of the problem. A way to reduce
2060 the impact is to upgrade to the Hurd packages built by Justus by
2061 adding this repository to the machine:&lt;/p&gt;
2062
2063 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2064 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2065 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2066 EOF
2067 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2068
2069 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2070 http://ftp.debian-ports.org/debian, because some of the packages in
2071 unstable do not yet include the required patches that are lingering in
2072 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2073
2074 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2075 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2076 i emacs - GNU Emacs editor (metapackage)
2077 i gdb - GNU Debugger
2078 i hurd-recommended - Miscellaneous translators
2079 i isc-dhcp-client - ISC DHCP client
2080 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2081 i libc-bin - Embedded GNU C Library: Binaries
2082 i libc-dev-bin - Embedded GNU C Library: Development binaries
2083 i libc0.3 - Embedded GNU C Library: Shared libraries
2084 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2085 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2086 i multiarch-support - Transitional package to ensure multiarch compatibilit
2087 i A x11-common - X Window System (X.Org) infrastructure
2088 i xorg - X.Org X Window System
2089 i A xserver-xorg - X.Org X server
2090 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2091 #
2092 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2093
2094 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2095 X.org did not work out of the box and I never took the time to follow
2096 the porters instructions to fix it. This time I was interested in the
2097 command line stuff.&lt;p&gt;
2098 </description>
2099 </item>
2100
2101 <item>
2102 <title>New chrpath release 0.16</title>
2103 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2105 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2106 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2107 find problems in C, C++ and Java code using static source code
2108 analysis. It can detect a lot of different problems, and is very
2109 useful to find memory and locking bugs in the error handling part of
2110 the source. The company behind it provide
2111 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2112 a community service&lt;/a&gt;, and many hundred free software projects are
2113 already checked. A few days ago I decided to have a closer look at
2114 the Coverity system, and discovered that the
2115 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2116 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2117 projects I am involved with was already registered. But these are
2118 fairly big, and I would also like to have a small and easy project to
2119 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2120 checking of the chrpath project&lt;/a&gt;. It was
2121 added to the checker and discovered seven potential defects. Six of
2122 these were real, mostly resource &quot;leak&quot; when the program detected an
2123 error. Nothing serious, as the resources would be released a fraction
2124 of a second later when the program exited because of the error, but it
2125 is nice to do it right in case the source of the program some time in
2126 the future end up in a library. Having fixed all defects and added
2127 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2128 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2129 publish a new release. These are the release notes:&lt;/p&gt;
2130
2131 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2132
2133 &lt;ul&gt;
2134
2135 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2136 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2137 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2138
2139 &lt;/ul&gt;
2140
2141 &lt;p&gt;You can
2142 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2143 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2144 project if something is wrong with the new release. The test suite
2145 did not discover any old errors, so if you find a new one, please also
2146 include a test suite check.&lt;/p&gt;
2147 </description>
2148 </item>
2149
2150 <item>
2151 <title>New chrpath release 0.15</title>
2152 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2153 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2154 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2155 <description>&lt;p&gt;After many years break from the package and a vain hope that
2156 development would be continued by someone else, I finally pulled my
2157 acts together this morning and wrapped up a new release of chrpath,
2158 the command line tool to modify the rpath and runpath of already
2159 compiled ELF programs. The update was triggered by the persistence of
2160 Isha Vishnoi at IBM, which needed a new config.guess file to get
2161 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2162 is working on. I checked the
2163 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2164 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2165 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2166 packages for interesting patches (failed to find the source from
2167 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2168 These are the release notes:&lt;/p&gt;
2169
2170 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2171
2172 &lt;ul&gt;
2173
2174 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2175 with newer architectures. Thanks to isha vishnoi for the heads
2176 up.&lt;/li&gt;
2177
2178 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2179
2180 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2181 Matthias Klose.&lt;/li&gt;
2182
2183 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2184 Petr Machata found in Fedora.&lt;/li&gt;
2185
2186 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2187 .dynamic is a NULL terminated string. Based on patch found in
2188 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2189
2190 &lt;/ul&gt;
2191
2192 &lt;p&gt;You can
2193 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2194 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2195 project if something is wrong with the new release. The test suite
2196 did not discover any old errors, so if you find a new one, please also
2197 include a testsuite check.&lt;/p&gt;
2198 </description>
2199 </item>
2200
2201 <item>
2202 <title>Debian init.d boot script example for rsyslog</title>
2203 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2204 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2205 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2206 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2207 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2208 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2209 init.d scripts at all. Here is an example init.d script, ie a rewrite
2210 of /etc/init.d/rsyslog:&lt;/p&gt;
2211
2212 &lt;p&gt;&lt;pre&gt;
2213 #!/lib/init/init-d-script
2214 ### BEGIN INIT INFO
2215 # Provides: rsyslog
2216 # Required-Start: $remote_fs $time
2217 # Required-Stop: umountnfs $time
2218 # X-Stop-After: sendsigs
2219 # Default-Start: 2 3 4 5
2220 # Default-Stop: 0 1 6
2221 # Short-Description: enhanced syslogd
2222 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2223 # It is quite compatible to stock sysklogd and can be
2224 # used as a drop-in replacement.
2225 ### END INIT INFO
2226 DESC=&quot;enhanced syslogd&quot;
2227 DAEMON=/usr/sbin/rsyslogd
2228 &lt;/pre&gt;&lt;/p&gt;
2229
2230 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2231 script was 137 lines, and the above is just 15 lines, most of it meta
2232 info/comments.&lt;/p&gt;
2233
2234 &lt;p&gt;How to do this, you ask? Well, one create a new script
2235 /lib/init/init-d-script looking something like this:
2236
2237 &lt;p&gt;&lt;pre&gt;
2238 #!/bin/sh
2239
2240 # Define LSB log_* functions.
2241 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2242 # and status_of_proc is working.
2243 . /lib/lsb/init-functions
2244
2245 #
2246 # Function that starts the daemon/service
2247
2248 #
2249 do_start()
2250 {
2251 # Return
2252 # 0 if daemon has been started
2253 # 1 if daemon was already running
2254 # 2 if daemon could not be started
2255 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2256 || return 1
2257 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2258 $DAEMON_ARGS \
2259 || return 2
2260 # Add code here, if necessary, that waits for the process to be ready
2261 # to handle requests from services started subsequently which depend
2262 # on this one. As a last resort, sleep for some time.
2263 }
2264
2265 #
2266 # Function that stops the daemon/service
2267 #
2268 do_stop()
2269 {
2270 # Return
2271 # 0 if daemon has been stopped
2272 # 1 if daemon was already stopped
2273 # 2 if daemon could not be stopped
2274 # other if a failure occurred
2275 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2276 RETVAL=&quot;$?&quot;
2277 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2278 # Wait for children to finish too if this is a daemon that forks
2279 # and if the daemon is only ever run from this initscript.
2280 # If the above conditions are not satisfied then add some other code
2281 # that waits for the process to drop all resources that could be
2282 # needed by services started subsequently. A last resort is to
2283 # sleep for some time.
2284 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2285 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2286 # Many daemons don&#39;t delete their pidfiles when they exit.
2287 rm -f $PIDFILE
2288 return &quot;$RETVAL&quot;
2289 }
2290
2291 #
2292 # Function that sends a SIGHUP to the daemon/service
2293 #
2294 do_reload() {
2295 #
2296 # If the daemon can reload its configuration without
2297 # restarting (for example, when it is sent a SIGHUP),
2298 # then implement that here.
2299 #
2300 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2301 return 0
2302 }
2303
2304 SCRIPTNAME=$1
2305 scriptbasename=&quot;$(basename $1)&quot;
2306 echo &quot;SN: $scriptbasename&quot;
2307 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2308 script=&quot;$1&quot;
2309 shift
2310 . $script
2311 else
2312 exit 0
2313 fi
2314
2315 NAME=$(basename $DAEMON)
2316 PIDFILE=/var/run/$NAME.pid
2317
2318 # Exit if the package is not installed
2319 #[ -x &quot;$DAEMON&quot; ] || exit 0
2320
2321 # Read configuration variable file if it is present
2322 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2323
2324 # Load the VERBOSE setting and other rcS variables
2325 . /lib/init/vars.sh
2326
2327 case &quot;$1&quot; in
2328 start)
2329 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2330 do_start
2331 case &quot;$?&quot; in
2332 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2333 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2334 esac
2335 ;;
2336 stop)
2337 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2338 do_stop
2339 case &quot;$?&quot; in
2340 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2341 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2342 esac
2343 ;;
2344 status)
2345 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2346 ;;
2347 #reload|force-reload)
2348 #
2349 # If do_reload() is not implemented then leave this commented out
2350 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2351 #
2352 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2353 #do_reload
2354 #log_end_msg $?
2355 #;;
2356 restart|force-reload)
2357 #
2358 # If the &quot;reload&quot; option is implemented then remove the
2359 # &#39;force-reload&#39; alias
2360 #
2361 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2362 do_stop
2363 case &quot;$?&quot; in
2364 0|1)
2365 do_start
2366 case &quot;$?&quot; in
2367 0) log_end_msg 0 ;;
2368 1) log_end_msg 1 ;; # Old process is still running
2369 *) log_end_msg 1 ;; # Failed to start
2370 esac
2371 ;;
2372 *)
2373 # Failed to stop
2374 log_end_msg 1
2375 ;;
2376 esac
2377 ;;
2378 *)
2379 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2380 exit 3
2381 ;;
2382 esac
2383
2384 :
2385 &lt;/pre&gt;&lt;/p&gt;
2386
2387 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2388 lot. I did not really polish the approach, so it might not always
2389 work out of the box, but you get the idea. I did not try very hard to
2390 optimize it nor make it more robust either.&lt;/p&gt;
2391
2392 &lt;p&gt;A better argument for switching init system in Debian than reducing
2393 the size of init scripts (which is a good thing to do anyway), is to
2394 get boot system that is able to handle the kernel events sensibly and
2395 robustly, and do not depend on the boot to run sequentially. The boot
2396 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2397 </description>
2398 </item>
2399
2400 <item>
2401 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2402 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2404 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2405 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2406 remote display access is the preferred solution with oVirt and RedHat
2407 Enterprise Virtualization, and I was sad to discover the other day
2408 that the browser plugin needed to use these systems seamlessly was
2409 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2410 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2411 2013-04-01, so I decided to wrap up a package based on the great work
2412 from Cajus Pollmeier and put it in a collab-maint maintained git
2413 repository to get a package I could use. I would very much like
2414 others to help me maintain the package (or just take over, I do not
2415 mind), but as no-one had volunteered so far, I just uploaded it to
2416 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2417
2418 &lt;p&gt;The source is now available from
2419 &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;
2420 </description>
2421 </item>
2422
2423 <item>
2424 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2425 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2427 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2428 <description>&lt;p&gt;The
2429 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2430 program is a a very nice system to create virtual machine images. It
2431 create a image file, add a partition table, mount it and run
2432 debootstrap in the mounted directory to create a Debian system on a
2433 stick. Yesterday, I decided to try to teach it how to make images for
2434 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2435 of a plan to simplify the build system for
2436 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2437 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2438 the virtualbox images, but its current build system made multistrap
2439 based system for Dreamplug images, and it is lacking support for
2440 Raspberry Pi.&lt;/p&gt;
2441
2442 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2443 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2444 code and adjusted it to be able to build armel images on my amd64
2445 Debian laptop. I ended up giving vmdebootstrap five new options,
2446 allowing me to replicate the image creation process I use to make
2447 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2448 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2449 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2450 call debootstrap with --foreign and to copy the handler into the
2451 generated chroot before running the second stage. This allow
2452 vmdebootstrap to create armel images on an amd64 host. Next I added
2453 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2454 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2455 given file system type, allowing me to create an image with a vfat
2456 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2457 variant&lt;/tt&gt; option to allow me to create smaller images without the
2458 Debian base system packages installed. Finally, I added an option
2459 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2460 as a boot loader. It is not needed on the Raspberry Pi and probably
2461 most other non-x86 architectures. The changes were accepted by the
2462 upstream author of vmdebootstrap yesterday and today, and is now
2463 available from
2464 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2465 upstream project page&lt;/a&gt;.&lt;/p&gt;
2466
2467 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2468 create a small script (the customize script) to add the non-free
2469 binary blob needed to boot the Raspberry Pi and the APT source
2470 list:&lt;/p&gt;
2471
2472 &lt;p&gt;&lt;pre&gt;
2473 #!/bin/sh
2474 set -e # Exit on first error
2475 rootdir=&quot;$1&quot;
2476 cd &quot;$rootdir&quot;
2477 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2478 deb http://http.debian.net/debian/ jessie main contrib non-free
2479 EOF
2480 # Install non-free binary blob needed to boot Raspberry Pi. This
2481 # install a kernel somewhere too.
2482 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2483 -O $rootdir/usr/bin/rpi-update
2484 chmod a+x $rootdir/usr/bin/rpi-update
2485 mkdir -p $rootdir/lib/modules
2486 touch $rootdir/boot/start.elf
2487 chroot $rootdir rpi-update
2488 &lt;/pre&gt;&lt;/p&gt;
2489
2490 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2491 to build the image:&lt;/p&gt;
2492
2493 &lt;pre&gt;
2494 sudo ./vmdebootstrap \
2495 --variant minbase \
2496 --arch armel \
2497 --distribution jessie \
2498 --mirror http://http.debian.net/debian \
2499 --image test.img \
2500 --size 600M \
2501 --bootsize 64M \
2502 --boottype vfat \
2503 --log-level debug \
2504 --verbose \
2505 --no-kernel \
2506 --no-extlinux \
2507 --root-password raspberry \
2508 --hostname raspberrypi \
2509 --foreign /usr/bin/qemu-arm-static \
2510 --customize `pwd`/customize \
2511 --package netbase \
2512 --package git-core \
2513 --package binutils \
2514 --package ca-certificates \
2515 --package wget \
2516 --package kmod
2517 &lt;/pre&gt;&lt;/p&gt;
2518
2519 &lt;p&gt;The list of packages being installed are the ones needed by
2520 rpi-update to make the image bootable on the Raspberry Pi, with the
2521 exception of netbase, which is needed by debootstrap to find
2522 /etc/hosts with the minbase variant. I really wish there was a way to
2523 set up an Raspberry Pi using only packages in the Debian archive, but
2524 that is not possible as far as I know, because it boots from the GPU
2525 using a non-free binary blob.&lt;/p&gt;
2526
2527 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2528 probably a few others installed. I have not checked the complete
2529 build dependency list.&lt;/p&gt;
2530
2531 &lt;p&gt;The resulting image will not use the hardware floating point unit
2532 on the Raspberry PI, because the armel architecture in Debian is not
2533 optimized for that use. So the images created will be a bit slower
2534 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2535 </description>
2536 </item>
2537
2538 <item>
2539 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2540 <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>
2541 <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>
2542 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2543 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2544 wider attention. I recommend signing and donating to each one of
2545 these. :)&lt;/p&gt;
2546
2547 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2548 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2549 Women program which is a Google Summer of Code like initiative to get
2550 more women involved in free software. One debian sponsor has offered
2551 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2552 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2553 hope you will to. :)&lt;/p&gt;
2554
2555 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2556 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2557 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2558 take place these days, and their need to fund the work. I&#39;ve already
2559 donated. Are you next?&lt;/p&gt;
2560
2561 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2562 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2563 statement under the heading
2564 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2565 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2566 Norwegian government. So far 499 signatures. I hope you will sign it
2567 too.&lt;/p&gt;
2568 </description>
2569 </item>
2570
2571 <item>
2572 <title>Videos about the Freedombox project - for inspiration and learning</title>
2573 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2575 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2576 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2577 project&lt;/a&gt; have been going on for a while, and have presented the
2578 vision, ideas and solution several places. Here is a little
2579 collection of videos of talks and presentation of the project.&lt;/p&gt;
2580
2581 &lt;ul&gt;
2582
2583 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2584 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2585
2586 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2587 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2588
2589 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2590 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2591 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2592 (Youtube)&lt;/li&gt;
2593
2594 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2595 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2596
2597 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2598 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2599
2600 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2601 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2602 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2603
2604 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2605 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2606 (Youtube)&lt;/li&gt;
2607
2608 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2609 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2610
2611 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2612 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2613
2614 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2615 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2616 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2617
2618 &lt;/ul&gt;
2619
2620 &lt;p&gt;A larger list is available from
2621 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2622 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2623
2624 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2625 Jessie is coming along quite well, and soon both Owncloud and using
2626 Tor should be available for testers of the Freedombox solution. :) In
2627 a few weeks I hope everything needed to test it is included in Debian.
2628 The withsqlite package is already in Debian, and the plinth package is
2629 pending in NEW. The third and vital part of that puzzle is the
2630 metapackage/setup framework, which is still pending an upload. Join
2631 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2632 (#freedombox on irc.debian.org)&lt;/a&gt; and
2633 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2634 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2635 </description>
2636 </item>
2637
2638 <item>
2639 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2640 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2642 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2643 <description>&lt;p&gt;I was introduced to the
2644 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2645 in 2010, when Eben Moglen presented his vision about serving the need
2646 of non-technical people to keep their personal information private and
2647 within the legal protection of their own homes. The idea is to give
2648 people back the power over their network and machines, and return
2649 Internet back to its intended peer-to-peer architecture. Instead of
2650 depending on a central service, the Freedombox will give everyone
2651 control over their own basic infrastructure.&lt;/p&gt;
2652
2653 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2654 taken priority. But this summers nasty news about the misuse of trust
2655 and privilege exercised by the &quot;western&quot; intelligence gathering
2656 communities increased my eagerness to contribute to a point where I
2657 actually started working on the project a while back.&lt;/p&gt;
2658
2659 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2660 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2661 create a simple and cheap Debian based appliance that anyone can hook
2662 up in their home and get access to secure and private services and
2663 communication. The initial deployment platform have been the
2664 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2665 which is a piece of hardware I do not own. So to be able to test what
2666 the current Freedombox setup look like, I had to come up with a way to install
2667 it on some hardware I do have access to. I have rewritten the
2668 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2669 image build framework to use .deb packages instead of only copying
2670 setup into the boot images, and thanks to this rewrite I am able to
2671 set up any machine supported by Debian Wheezy as a Freedombox, using
2672 the previously mentioned deb (and a few support debs for packages
2673 missing in Debian).&lt;/p&gt;
2674
2675 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2676 scripts
2677 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2678 and a administrative web interface
2679 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2680 withsqlite), as well as a privacy enhancing proxy based on
2681 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2682 (freedombox-privoxy). There is also a web/javascript based XMPP
2683 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2684 trying (unsuccessfully so far) to talk to the XMPP server
2685 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2686 web interface is pluggable, and the goal is to use it to enable OpenID
2687 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2688 this is really working yet, see
2689 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2690 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2691 on github at the moment. The HTTP proxy is operational out of the
2692 box, and the admin web interface can be used to add/remove plinth
2693 users. I&#39;ve not been able to do anything else with it so far, but
2694 know there are several branches spread around github and other places
2695 with lots of half baked features.&lt;/p&gt;
2696
2697 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2698 following recipes should work to give you a test machine to poke
2699 at.&lt;/p&gt;
2700
2701 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2702
2703 &lt;ol&gt;
2704
2705 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2706 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2707 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2708 to the Debian installer:&lt;p&gt;
2709 &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;
2710
2711 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2712 install on.&lt;/li&gt;
2713
2714 &lt;li&gt;When the installation is finished and the machine have rebooted a
2715 few times, your Freedombox is ready for testing.&lt;/li&gt;
2716
2717 &lt;/ol&gt;
2718
2719 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2720
2721 &lt;ol&gt;
2722
2723 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2724 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2725 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2726 &lt;pre&gt;
2727 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2728 &lt;/pre&gt;&lt;/li&gt;
2729 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2730 &lt;pre&gt;
2731 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2732 apt-key add -
2733 apt-get update
2734 apt-get install freedombox-setup
2735 /usr/lib/freedombox/setup
2736 &lt;/pre&gt;&lt;/li&gt;
2737 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2738
2739 &lt;/ol&gt;
2740
2741 &lt;p&gt;You can test it on other architectures too, but because the
2742 freedombox-privoxy package is binary, it will only work as intended on
2743 the architectures where I have had time to build the binary and put it
2744 in my APT repository. But do not let this stop you. It is only a
2745 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2746
2747 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2748 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2749 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2750 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2751
2752 &lt;p&gt;Please let me know if this works for you, or if you have any
2753 problems. We gather on the IRC channel
2754 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2755 irc.debian.org and the
2756 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2757 mailing list&lt;/a&gt;.&lt;/p&gt;
2758
2759 &lt;p&gt;Once you get your freedombox operational, you can visit
2760 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2761 welcome screen (dead end - do not be surprised if you are unable to
2762 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2763 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2764 default password is &#39;secret&#39;.&lt;/p&gt;
2765 </description>
2766 </item>
2767
2768 <item>
2769 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2770 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2772 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2773 <description>&lt;p&gt;Earlier, I reported about
2774 &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
2775 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2776 told by IBM that the original disk should be thrown away. And as
2777 there no longer was a problem if I bricked the firmware, I decided
2778 today to try to install Intel firmware to replace the Lenovo firmware
2779 currently on the disk.&lt;/p&gt;
2780
2781 &lt;p&gt;I searched the Intel site for firmware, and found
2782 &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;
2783 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2784 according to the site should contain the latest firmware for SSD
2785 disks. I inserted the broken disk in one of my spare laptops and
2786 booted the ISO from a USB stick. The disk was recognized, but the
2787 program claimed the newest firmware already were installed and refused
2788 to insert any Intel firmware. So no change, and the disk is still
2789 unable to handle write load. :( I guess the only way to get them
2790 working would be if Lenovo releases new firmware. No idea how likely
2791 that is. Anyway, just blogging about this test for completeness. I
2792 got a working Samsung disk, and see no point in spending more time on
2793 the broken disks.&lt;/p&gt;
2794 </description>
2795 </item>
2796
2797 <item>
2798 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2799 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2801 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2802 <description>&lt;p&gt;Today I switched to
2803 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2804 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2805 my new Thinkpad X230, which was delivered with an
2806 &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
2807 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2808 sustained writes. My hardware supplier have been very forthcoming in
2809 trying to find a solution, and after first trying with another
2810 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2811 disk instead to fix it once and for all. The Samsung disk survived
2812 the installation of Debian with encrypted disks (filling the disk with
2813 random data during installation killed the first two), and I thus
2814 decided to trust it with my data. I have installed it as a Debian Edu
2815 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2816 server at home using Kerberos and LDAP, and will use it as my work
2817 station from now on.&lt;/p&gt;
2818
2819 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2820 Debian Wheezy default installation need to be tuned a bit to increase
2821 performance and increase life time of the disk. The Linux kernel and
2822 user space applications do not yet adjust automatically to such
2823 environment. To make it easier for my self, I created a draft Debian
2824 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2825 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2826 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2827 is set up to adjust the setup of the machine by just installing the
2828 package. If there is any non-SSD disk in the machine, the package
2829 will refuse to install, as I did not try to write any logic to sort
2830 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2831
2832 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2833 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2834 where I set up the machine with one large encrypted partition (in
2835 addition to /boot), put LVM on top of this and set up partitions on
2836 top of this again. See the README file in the package source for the
2837 references I used to pick the settings. At the moment these
2838 parameters are tuned:&lt;/p&gt;
2839
2840 &lt;ul&gt;
2841
2842 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2843 (adding discard to /etc/crypttab)&lt;/li&gt;
2844
2845 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2846 this case a cryptsetup partition) by changing issue_discards from
2847 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2848
2849 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2850 systems.&lt;/li&gt;
2851
2852 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2853 /etc/fstab.&lt;/li&gt;
2854
2855 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2856
2857 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2858 cron.daily).&lt;/li&gt;
2859
2860 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2861 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2862
2863 &lt;/ul&gt;
2864
2865 &lt;p&gt;During installation, I cancelled the part where the installer fill
2866 the disk with random data, as this would kill the SSD performance for
2867 little gain. My goal with the encrypted file system is to ensure
2868 those stealing my laptop end up with a brick and not a working
2869 computer. I have no hope in keeping the really resourceful people
2870 from getting the data on the disk (see
2871 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2872 Thus I concluded that adding the discard option to crypttab is the
2873 right thing to do.&lt;/p&gt;
2874
2875 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2876 it for SSD, but others recommended deadline and a benchmark I found
2877 indicated that deadline might be better for interactive use.&lt;/p&gt;
2878
2879 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2880 and ext4, but read that it would give a performance hit ever time a
2881 file is removed, and thought it best to that that slowdown once a day
2882 instead of during my work.&lt;/p&gt;
2883
2884 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2885 this is already done by Debian Edu.&lt;/p&gt;
2886
2887 &lt;p&gt;I have not yet started on the user space tuning. I expect
2888 iceweasel need some tuning, and perhaps other applications too, but
2889 have not yet had time to investigate those parts.&lt;/p&gt;
2890
2891 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2892 there.&lt;/p&gt;
2893
2894 &lt;p&gt;As for the answer to the question in the title of this blog post,
2895 as far as I know, the only solution I know about is to replace the
2896 disk. It might be possible to flash it with Intel firmware instead of
2897 the Lenovo firmware. But I have not tried and did not want to do so
2898 without approval from Lenovo as I wanted to keep the warranty on the
2899 disk until a solution was found and they wanted the broken disks
2900 back.&lt;/p&gt;
2901 </description>
2902 </item>
2903
2904 <item>
2905 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2906 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2907 <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>
2908 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2909 <description>&lt;p&gt;A few days ago, I wrote about
2910 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2911 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2912 was dying during installation because it is unable to cope with
2913 sustained write. My supplier is in contact with
2914 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2915 replacement disk to try to fix the problem. They decided to send an
2916 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2917
2918 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2919 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2920 same firmware version as the original. This time my hope raised
2921 slightly as the installation progressed, as the original disk used to
2922 die after 4-7% of the disk was written to, while this time it kept
2923 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2924 died again and I was back on square one. I still do not have a new
2925 laptop with a disk I can trust. I can not live with a disk that might
2926 lock up when I download a new
2927 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2928 other large files. I look forward to hearing from my supplier with
2929 the next proposal from Lenovo.&lt;/p&gt;
2930
2931 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2932 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2933 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2934 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2935 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2936 P/N 45N8295, P0C38732.&lt;/p&gt;
2937
2938 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2939 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2940 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2941 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2942 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2943 P/N 45N8295, P0C38732.&lt;/p&gt;
2944
2945 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2946 SA, date and WNPP values. Mentioning all the details here in case
2947 someone is able to use the information to find a way to identify the
2948 failing disk among working ones (if any such working disk actually
2949 exist).&lt;/p&gt;
2950 </description>
2951 </item>
2952
2953 <item>
2954 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2955 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2957 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2958 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2959 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2960 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2961 member assosiation NUUG&lt;/a&gt; and
2962 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2963 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2964 Bitraf&lt;/a&gt;.&lt;/p&gt;
2965
2966 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2967 welcome, and there is no fee to participate. There is on the other
2968 hand limited space, and only room for 30 people. Please put your name
2969 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2970 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2971 </description>
2972 </item>
2973
2974 <item>
2975 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2976 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2977 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2978 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2979 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2980 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2981 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2982 time to spend on it, and it took a while to find a model I believe
2983 will do the job, but two days ago the replacement finally arrived. I
2984 ended up picking a
2985 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2986 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2987 a roaming workstation, and it seemed to work flawlessly. But my
2988 second installation with encrypted disk was not as successful. More
2989 on that below.&lt;/p&gt;
2990
2991 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2992 important requirements (robust and with a good keyboard) are never
2993 listed in the feature list. But I did get good help from the search
2994 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2995 allowed me to limit the list of interesting laptops based on my other
2996 requirements. A bit surprising that SSD disk are not disks according
2997 to that search interface, so I had to drop specifying the number of
2998 disks from my search parameters. I also asked around among friends to
2999 get their impression on keyboards and robustness.&lt;/p&gt;
3000
3001 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3002 X41. I am not quite convinced about the keyboard, as it is
3003 significantly wider than my old keyboard, and I have to stretch my
3004 hand a lot more to reach the edges. But the key response is fairly
3005 good and the individual key shape is fairly easy to handle, so I hope
3006 I will get used to it. My old X40 was starting to fail, and I really
3007 needed a new laptop now. :)&lt;/p&gt;
3008
3009 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3010 visit to the BIOS during boot it disable it.&lt;/p&gt;
3011
3012 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3013 lock up during load. And this happen when installing Debian Wheezy
3014 with encrypted disk, while the disk is being filled with random data.
3015 I also tested to install Ubuntu Raring, and it happen there too if I
3016 reenable the code to fill the disk with random data (it is disabled by
3017 default in Ubuntu). And the bug with is already known. It was
3018 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3019 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3020 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3021 kernel developers as
3022 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3023 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3024 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3025 Lenovo forums, both for
3026 &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
3027 2012-11-10&lt;/a&gt; and for
3028 &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
3029 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3030 reports state that the disk lock up during use if many writes are done
3031 on the disk, so it is much no use to work around the installation
3032 problem and end up with a computer that can lock up at any moment.
3033 There is even a
3034 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3035 available&lt;/a&gt; that will lock up the hard drive after running a few
3036 minutes by writing to a file.&lt;/p&gt;
3037
3038 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3039 contacting PCHELP Norway (request 01D1FDP) which handle support
3040 requests for Lenovo, his first suggestion was to upgrade the disk
3041 firmware. Unfortunately there is no newer firmware available from
3042 Lenovo, as my disk already have the most recent one (version LF1i). I
3043 hope to hear more from him today and hope the problem can be
3044 fixed. :)&lt;/p&gt;
3045 </description>
3046 </item>
3047
3048 <item>
3049 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3050 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3051 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3052 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3053 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3054 trusty old Thinkpad X41. Unfortunately I did not have much time to
3055 spend on it, but today the replacement finally arrived. I ended up
3056 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3057 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3058 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3059 this, it is installing what I hope will be a more final installation,
3060 with a encrypted hard drive to ensure any dope head stealing it end up
3061 with an expencive door stop.&lt;/p&gt;
3062
3063 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3064 important requirements (robust and with a good keyboard) are never
3065 listed in the feature list. But I did get good help from the search
3066 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3067 allowed me to limit the list of interesting laptops based on my other
3068 requirements. A bit surprising that SSD disk are not disks, so I had
3069 to drop number of disks from my search parameters.&lt;/p&gt;
3070
3071 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3072 wider than my old keyboard, and I have to stretch my hand a lot more
3073 to reach the edges. But the key response is fairly good and the
3074 individual key shape is fairly easy to handle, so I hope I will get
3075 used to it. My old X40 was starting to fail, and I really needed a
3076 new laptop now. :)&lt;/p&gt;
3077
3078 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3079 </description>
3080 </item>
3081
3082 <item>
3083 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3084 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3086 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3087 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3088 perfectly capable of, and I have to do it manually to get things
3089 working. One such task is to find out what firmware packages are
3090 needed to get the hardware on my computer working. Most often this
3091 affect the wifi card, but some times it even affect the RAID
3092 controller or the ethernet card. Today I pushed version 0.4 of the
3093 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3094 including a new script isenkram-autoinstall-firmware handling the
3095 process of asking all the loaded kernel modules what firmware files
3096 they want, find debian packages providing these files and install the
3097 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3098
3099 &lt;p&gt;&lt;pre&gt;
3100 # isenkram-autoinstall-firmware
3101 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3102 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3103 info: locating packages with the requested firmware files
3104 info: Updating APT sources after adding non-free APT source
3105 info: trying to install firmware-ipw2x00
3106 firmware-ipw2x00
3107 firmware-ipw2x00
3108 Preconfiguring packages ...
3109 Selecting previously deselected package firmware-ipw2x00.
3110 (Reading database ... 259727 files and directories currently installed.)
3111 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3112 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3113 #
3114 &lt;/pre&gt;&lt;/p&gt;
3115
3116 &lt;p&gt;When all the requested firmware is present, a simple message is
3117 printed instead:&lt;/p&gt;
3118
3119 &lt;p&gt;&lt;pre&gt;
3120 # isenkram-autoinstall-firmware
3121 info: did not find any firmware files requested by loaded kernel modules. exiting
3122 #
3123 &lt;/pre&gt;&lt;/p&gt;
3124
3125 &lt;p&gt;It could use some polish, but it is already working well and saving
3126 me some time when setting up new machines. :)&lt;/p&gt;
3127
3128 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3129 kernel modules, and look up each one of them using modinfo, to find
3130 the firmware files listed in the module meta-information. Next, it
3131 download the Contents file from a nearby APT mirror, and search for
3132 the firmware files in this file to locate the package with the
3133 requested firmware file. If the package is in the non-free section, a
3134 non-free APT source is added and the package is installed using
3135 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3136 machine.&lt;/p&gt;
3137
3138 &lt;p&gt;I hope someone find time to implement a more polished version of
3139 this script as part of the hw-detect debian-installer module, to
3140 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3141 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3142 firmware during a PXE install when the packages already are available
3143 from the nearby Debian mirror.&lt;/p&gt;
3144 </description>
3145 </item>
3146
3147 <item>
3148 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3149 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3150 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3151 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3152 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3153 the screen just turn black when Linux boot, either during installation
3154 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3155 last few years, but only recently understood the cause. I&#39;ve seen it
3156 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3157 The reason seem to be in the wiring of some laptops. The system to
3158 control the screen background light is inverted, so when Linux try to
3159 turn the brightness fully on, it end up turning it off instead. I do
3160 not know which Linux drivers are affected, but this post is about the
3161 i915 driver used by the
3162 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3163 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3164
3165 &lt;p&gt;The problem can be worked around two ways. Either by adding
3166 i915.invert_brightness=1 as a kernel option, or by adding a file in
3167 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3168 option when it load the i915 kernel module. On Debian and Ubuntu, it
3169 can be done by running these commands as root:&lt;/p&gt;
3170
3171 &lt;pre&gt;
3172 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3173 update-initramfs -u -k all
3174 &lt;/pre&gt;
3175
3176 &lt;p&gt;Since March 2012 there is
3177 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3178 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3179 hardware have this problem, and get the driver to invert the
3180 brightness setting automatically. To use it, one need to add a row in
3181 &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
3182 intel_quirks array&lt;/a&gt; in the driver source
3183 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3184 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3185 number (vendor number 8086 is assumed) and subdevice vendor and device
3186 number.&lt;/p&gt;
3187
3188 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3189 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3190
3191 &lt;p&gt;&lt;pre&gt;
3192 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3193 3rd Gen Core processor Graphics Controller [8086:0156] \
3194 (rev 09) (prog-if 00 [VGA controller])
3195 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3196 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3197 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3198 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3199 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3200 Latency: 0
3201 Interrupt: pin A routed to IRQ 42
3202 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3203 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3204 Region 4: I/O ports at 4000 [size=64]
3205 Expansion ROM at &lt;unassigned&gt; [disabled]
3206 Capabilities: &lt;access denied&gt;
3207 Kernel driver in use: i915
3208 &lt;/pre&gt;&lt;/p&gt;
3209
3210 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3211
3212 &lt;p&gt;&lt;pre&gt;
3213 struct intel_quirk intel_quirks[] = {
3214 ...
3215 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3216 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3217 ...
3218 }
3219 &lt;/pre&gt;&lt;/p&gt;
3220
3221 &lt;p&gt;According to the kernel module instructions (as seen using
3222 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3223 invert_brightness flag should be sent to the
3224 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3225 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3226 developers. But my email about the laptop sent 2013-06-03 have not
3227 yet shown up in
3228 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3229 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3230 emails from non-subscribers. Because of this, I sent my patch also to
3231 the Debian bug tracking system instead as
3232 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3233 sure the patch is not lost.&lt;/p&gt;
3234
3235 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3236 with this problem working properly with Linux. If you use Gnome, your
3237 worries should be over at this point. But if you use KDE, there is
3238 something in KDE ignoring the invert_brightness setting and turning on
3239 the screen during login. I&#39;ve reported it to Debian as
3240 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3241 have no idea yet how to figure out exactly what subsystem is doing
3242 this. Perhaps you can help? Perhaps you know what the Gnome
3243 developers did to handle this, and this can give a clue to the KDE
3244 developers? Or you know where in KDE the screen brightness is changed
3245 during login? If so, please update the BTS report (or get in touch if
3246 you do not know how to update BTS).&lt;/p&gt;
3247
3248 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3249 acpi_backlight=vendor, to disable ACPI backlight support completely,
3250 as the ACPI information on the machine is trash and it is better to
3251 leave it to the intel video driver to control the screen
3252 backlight.&lt;/p&gt;
3253 </description>
3254 </item>
3255
3256 <item>
3257 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3258 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3259 <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>
3260 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3261 <description>&lt;p&gt;Two days ago, I asked
3262 &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
3263 I could install Linux on a Packard Bell EasyNote LV computer
3264 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3265 with the obstacles put in the way of Linux users on a laptop with UEFI
3266 and Windows 8.&lt;/p&gt;
3267
3268 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3269 secure booting or fast boot. I suspect fast boot was the problem,
3270 causing the firmware to boot directly from HD without considering any
3271 key presses and alternative devices, but do not know UEFI settings
3272 enough to tell.&lt;/p&gt;
3273
3274 &lt;p&gt;There is no way to install Linux on the machine in question without
3275 opening the box and disconnecting the hard drive! This is as far as I
3276 can tell, the only way to get access to the firmware setup menu
3277 without accepting the Windows 8 license agreement. I am told (and
3278 found description on how to) that it is possible to configure the
3279 firmware setup once booted into Windows 8. But as I believe the terms
3280 of that agreement are completely unacceptable, accepting the license
3281 was never an alternative. I do not enter agreements I do not intend
3282 to follow.&lt;/p&gt;
3283
3284 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3285 waste many hours on this, but luckily there was a way to get it to
3286 work. But I would not recommend it to anyone planning to run Linux on
3287 it, and I have become sceptical to Windows 8 certified laptops. Is
3288 this the way Linux will be forced out of the market place, by making
3289 it close to impossible for &quot;normal&quot; users to install Linux without
3290 accepting the Microsoft Windows license terms? Or at least not
3291 without risking to loose the warranty?&lt;/p&gt;
3292
3293 &lt;p&gt;I&#39;ve updated the
3294 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3295 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3296 do not have to struggle as much as I did to get Linux into the
3297 machine.&lt;/p&gt;
3298
3299 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3300 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3301 </description>
3302 </item>
3303
3304 <item>
3305 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3306 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3307 <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>
3308 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3309 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3310 new laptops for my parents and a few others. I bought Packard Bell
3311 Easynote LV to run Kubuntu on and use as their home computer. But I
3312 am completely unable to figure out how to install Linux on it. The
3313 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3314 instead of a BIOS to boot.&lt;/p&gt;
3315
3316 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3317 to get it to boot the Linux installer from my USB stick. I have yet
3318 to try the DVD install, and still hope it will work. when I turn on
3319 the computer, there is no information on what buttons to press to get
3320 the normal boot menu. I expect to get some boot menu to select PXE or
3321 USB stick booting. When booting, it first ask for the language to
3322 use, then for some regional settings, and finally if I will accept the
3323 Windows 8 terms of use. As these terms are completely unacceptable to
3324 me, I have no other choice but to turn off the computer and try again
3325 to get it to boot the Linux installer.&lt;/p&gt;
3326
3327 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3328 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3329 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3330 installed on this machine, please get in touch or update that wiki
3331 page. If I can&#39;t find a way to install Linux, I will have to return
3332 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3333
3334 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3335 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3336 on new Laptops?&lt;/p&gt;
3337 </description>
3338 </item>
3339
3340 <item>
3341 <title>How to transform a Debian based system to a Debian Edu installation</title>
3342 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3343 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3344 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3345 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3346 an operating system based on Debian intended for use in schools. It
3347 contain a turn-key solution for the computer network provided to
3348 pupils in the primary schools. It provide both the central server,
3349 network boot servers and desktop environments with heaps of
3350 educational software. The project was founded almost 12 years ago,
3351 2001-07-02. If you want to support the project, which is in need for
3352 cash to fund developer gatherings and other project related activity,
3353 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3354 donate some money&lt;/a&gt;.
3355
3356 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3357 lists and elsewhere, is the question on how to transform a Debian or
3358 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3359 hard, and last week I wrote a script to replicate the steps done by
3360 the Debian Edu installer.&lt;/p&gt;
3361
3362 &lt;p&gt;The script,
3363 &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;
3364 in the debian-edu-config package, will go through these six steps and
3365 transform an existing Debian Wheezy or Ubuntu (untested) installation
3366 into a Debian Edu Workstation:&lt;/p&gt;
3367
3368 &lt;ol&gt;
3369
3370 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3371 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3372 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3373 our configuration.&lt;/li&gt;
3374 &lt;li&gt;Preseed debconf database with profile setup in
3375 /etc/debian-edu/config, and run tasksel to install packages
3376 according to the profile specified in the config above,
3377 overriding some of the Debian automation machinery.&lt;/li&gt;
3378 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3379 that could not be done using preseeding.&lt;/li&gt;
3380 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3381
3382 &lt;/ol&gt;
3383
3384 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3385 replicated like this. Disk partitioning and LVM setup, for example.
3386 So this script just assume there is enough disk space to install all
3387 the needed packages.&lt;/p&gt;
3388
3389 &lt;p&gt;The script was created to help a Debian Edu student working on
3390 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3391 Debian Edu client, and using it he can take the existing
3392 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3393 transform it into a fully functioning Debian Edu Workstation (or
3394 Roaming Workstation, or whatever :).&lt;/p&gt;
3395
3396 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3397 If a LXDE based Roaming workstation is wanted instead, modify the
3398 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3399
3400 &lt;p&gt;&lt;pre&gt;
3401 PROFILE=&quot;Roaming-Workstation&quot;
3402 DESKTOP=&quot;lxde&quot;
3403 &lt;/pre&gt;&lt;/p&gt;
3404
3405 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3406 the cloud, by starting with a virtual Debian installation at some
3407 virtual hosting service and setting up all the services on first
3408 boot.&lt;/p&gt;
3409 </description>
3410 </item>
3411
3412 <item>
3413 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3414 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3416 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3417 <description>&lt;P&gt;In January,
3418 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3419 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3420 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3421 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3422 marvellous construction system from Denmark. We also created
3423 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3424 a place to take notes and write down our plans and hopes. And several
3425 people showed up to help. I was very happy to see the effect of my
3426 call. Since the small start, we have a debtags tag
3427 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3428 tag for LEGO related packages, and now count 10 packages related to
3429 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3430
3431 &lt;p&gt;&lt;table&gt;
3432 &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;
3433 &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;
3434 &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;
3435 &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;
3436 &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;
3437 &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;
3438 &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;
3439 &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;
3440 &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;
3441 &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;
3442 &lt;/table&gt;&lt;/p&gt;
3443
3444 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3445 currently available in Jessie/testing. leocad is so far only
3446 available in experimental.&lt;/p&gt;
3447
3448 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3449 adding the rest of the great free software tools available on Linux
3450 for LEGO designers.&lt;/p&gt;
3451 </description>
3452 </item>
3453
3454 <item>
3455 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3456 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3458 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3459 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3460 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3461 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3462 Debian release, and I expect to move my machines at home over to it fairly
3463 soon.&lt;/p&gt;
3464
3465 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3466 in particular make me very happy to see included. The
3467 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3468 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3469 included for the first time. Alongside similar programs like
3470 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3471 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3472 it allow for visual programming where syntax errors can not happen,
3473 and a friendly programming environment for learning to control the
3474 computer. Scratch will also be included in the next release of Debian
3475 Edu.&lt;/a&gt;
3476
3477 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3478 Edu/Skolelinux release too. The
3479 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3480 alpha release&lt;/a&gt; went out last week, and the next should soon
3481 follow.&lt;p&gt;
3482 </description>
3483 </item>
3484
3485 <item>
3486 <title>Isenkram 0.2 finally in the Debian archive</title>
3487 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3488 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3489 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3490 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3491 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3492 for many months. I uploaded it to the Debian experimental suite
3493 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3494
3495 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3496 install to work with a pluggable hardware device. The suggestion pop
3497 up when the device is plugged in. For example if a Lego Mindstorm NXT
3498 is inserted, it will suggest to install the program needed to program
3499 the NXT controller. Give it a go, and report bugs and suggestions to
3500 BTS. :)&lt;/p&gt;
3501 </description>
3502 </item>
3503
3504 <item>
3505 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3506 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3508 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3509 <description>&lt;p&gt;My
3510 &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
3511 bitcoin related blog post&lt;/a&gt; mentioned that the new
3512 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3513 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3514 2013-01-19, and have been available in unstable since then. It was
3515 automatically copied to Ubuntu, and is available in their Raring
3516 version too.&lt;/p&gt;
3517
3518 &lt;p&gt;But there is a strange problem with the build that block this new
3519 version from being available on the i386 and kfreebsd-i386
3520 architectures. For some strange reason, the autobuilders in Debian
3521 for these architectures fail to run the test suite on these
3522 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3523 We are so far unable to reproduce it when building it manually, and
3524 no-one have been able to propose a fix. If you got an idea what is
3525 failing, please let us know via the BTS.&lt;/p&gt;
3526
3527 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3528 I often run low on disk space, is the fact that the client will exit
3529 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3530 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3531 it. :)&lt;/p&gt;
3532
3533 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3534 activities, please send Bitcoin donations to my address
3535 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3536 </description>
3537 </item>
3538
3539 <item>
3540 <title>Welcome to the world, Isenkram!</title>
3541 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3542 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3543 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3544 <description>&lt;p&gt;Yesterday, I
3545 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3546 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3547 pluggable hardware devices, which I
3548 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3549 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3550 up, and caused me to really want to to open up the development to more
3551 people. But before I did this, I want to come up with a sensible name
3552 for this project. Today I finally decided on a new name, and I have
3553 renamed the project from hw-support-handler to this new name. In the
3554 process, I moved the source to git and made it available as a
3555 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3556 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3557 To fetch and build the latest version of the source, use&lt;/p&gt;
3558
3559 &lt;pre&gt;
3560 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3561 cd isenkram &amp;&amp; git-buildpackage -us -uc
3562 &lt;/pre&gt;
3563
3564 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3565 want to hack on the source or improve the package, please go ahead.
3566 But please talk to me first on IRC or via email before you do major
3567 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3568
3569 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3570 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3571 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3572 the German word eisenkram, for those that are familiar with that
3573 word.&lt;/p&gt;
3574
3575 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3576 instructions, to avoid confusing people with an error from the signing
3577 process.&lt;/p&gt;
3578
3579 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3580 clone argument to avoid the need for authentication.&lt;/p&gt;
3581 </description>
3582 </item>
3583
3584 <item>
3585 <title>First prototype ready making hardware easier to use in Debian</title>
3586 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3588 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3589 <description>&lt;p&gt;Early this month I set out to try to
3590 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3591 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3592 prototype is working, and it is ready for a larger audience. To test
3593 it, fetch the
3594 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3595 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3596 package. You might have to log out and in again activate the
3597 autostart script.&lt;/p&gt;
3598
3599 &lt;p&gt;The design is simple:&lt;/p&gt;
3600
3601 &lt;ul&gt;
3602
3603 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3604 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3605
3606 &lt;li&gt;This program listen for kernel events about new hardware (directly
3607 from the kernel like udev does), not using HAL dbus events as I
3608 initially did.&lt;/li&gt;
3609
3610 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3611 the APT database, a database
3612 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3613 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3614
3615 &lt;li&gt;If a package is mapped to the hardware in question, the package
3616 isn&#39;t installed yet and this is the first time the hardware was
3617 plugged in, show a desktop notification suggesting to install the
3618 package or packages.&lt;/li&gt;
3619
3620 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3621 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3622
3623 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3624 package while showing progress information in a window.&lt;/li&gt;
3625
3626 &lt;/ul&gt;
3627
3628 &lt;p&gt;I still need to come up with a better name for the system. Here
3629 are some screen shots showing the prototype in action. First the
3630 notification, then the password request, and finally the request to
3631 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3632
3633 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3634 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3635 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3636 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3637 &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;
3638
3639 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3640 is already useful. The database of hardware to package mappings also
3641 need more work. It is currently compatible with the Ubuntu way of
3642 storing such information in the package control file, but could be
3643 changed to use other formats instead or in addition to the current
3644 method. I&#39;ve dropped the use of discover for this mapping, as the
3645 modalias approach is more flexible and easier to use on Linux as long
3646 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3647
3648 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3649 here is the command required to check out and build the source: Use
3650 &#39;&lt;tt&gt;svn checkout
3651 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3652 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3653 devscripts package.&lt;/p&gt;
3654
3655 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3656 renamed to Isenkram and the source moved from the Debian Edu
3657 subversion repository to a Debian collab-maint git repository. See
3658 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3659 instructions&lt;/a&gt; for details.&lt;/p&gt;
3660 </description>
3661 </item>
3662
3663 <item>
3664 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3665 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3666 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3667 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3668 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3669 suddenly in bed. With a quiet whimper, it went completely quiet and
3670 black. The power button was no longer able to turn it on. It was a
3671 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3672 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3673 Compaq I had before that. Now I need to find a replacement. To keep
3674 going during Christmas, I moved the one year old SSD disk to my old
3675 X40 where it fitted (only one I had left that could use it), but it is
3676 not a durable solution.
3677
3678 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3679 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3680
3681 &lt;ul&gt;
3682
3683 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3684 than A4).&lt;/li&gt;
3685 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3686 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3687 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3688 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3689 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3690 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3691 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3692 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3693 size).&lt;/li&gt;
3694 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3695 X.org packages.&lt;/li&gt;
3696 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3697 the time).
3698
3699 &lt;/ul&gt;
3700
3701 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3702 list. The reason is simply that the specifications on laptops the
3703 last 10-15 years have been sufficient for my needs, and I have to look
3704 at other features to choose my laptop. But are there still made as
3705 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3706 robust, and Thinkpads seem to be heading in the wrong direction since
3707 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3708 still be useful.&lt;/p&gt;
3709
3710 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3711 external keyboard? I&#39;ll have to check the
3712 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3713 well-supported laptops, or perhaps just buy one preinstalled from one
3714 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3715 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3716 </description>
3717 </item>
3718
3719 <item>
3720 <title>How to find a browser plugin supporting a given MIME type</title>
3721 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3723 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3724 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3725 install to get support for a given MIME type. Thanks to
3726 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3727 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3728 Unfortunately, not very many packages provide the needed meta
3729 information, Anyway, here is a small script to look up all browser
3730 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3731
3732 &lt;pre&gt;
3733 #!/usr/bin/python
3734 import sys
3735 import apt
3736 def pkgs_handling_mimetype(mimetype):
3737 cache = apt.Cache()
3738 cache.open(None)
3739 thepkgs = []
3740 for pkg in cache:
3741 version = pkg.candidate
3742 if version is None:
3743 version = pkg.installed
3744 if version is None:
3745 continue
3746 record = version.record
3747 if not record.has_key(&#39;Npp-MimeType&#39;):
3748 continue
3749 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3750 for t in mime_types:
3751 t = t.rstrip().strip()
3752 if t == mimetype:
3753 thepkgs.append(pkg.name)
3754 return thepkgs
3755 mimetype = &quot;audio/ogg&quot;
3756 if 1 &lt; len(sys.argv):
3757 mimetype = sys.argv[1]
3758 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3759 for pkg in pkgs_handling_mimetype(mimetype):
3760 print &quot; %s&quot; %pkg
3761 &lt;/pre&gt;
3762
3763 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3764
3765 &lt;pre&gt;
3766 % ./apt-find-browserplug-for-mimetype
3767 Browser plugin packages supporting audio/ogg:
3768 gecko-mediaplayer
3769 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3770 Browser plugin packages supporting application/x-shockwave-flash:
3771 browser-plugin-gnash
3772 %
3773 &lt;/pre&gt;
3774
3775 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3776 itself to query for plugins and propose to install the needed
3777 packages. It would be great if Debian supported such feature too. Is
3778 anyone working on adding it?&lt;/p&gt;
3779
3780 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3781 request for icweasel support for this feature is
3782 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3783 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3784 of manpower and wish for a different design is the reason thus feature
3785 is not yet in iceweasel from Debian.&lt;/p&gt;
3786 </description>
3787 </item>
3788
3789 <item>
3790 <title>What is the most supported MIME type in Debian?</title>
3791 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3792 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3793 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3794 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3795 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3796 proposal to make it possible for a Desktop application to propose to
3797 the user some package to install to gain support for a given MIME
3798 type, font, library etc. that is currently missing. With such
3799 mechanism in place, it would be possible for the desktop to
3800 automatically propose and install leocad if some LDraw file is
3801 downloaded by the browser.&lt;/p&gt;
3802
3803 &lt;p&gt;To get some idea about the current content of the archive, I decided
3804 to write a simple program to extract all .desktop files from the
3805 Debian archive and look up the claimed MIME support there. The result
3806 can be found on the
3807 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3808 site&lt;/a&gt;. Using the collected information, it become possible to
3809 answer the question in the title. Here are the 20 most supported MIME
3810 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3811 The complete list is available from the link above.&lt;/p&gt;
3812
3813 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3814
3815 &lt;pre&gt;
3816 count MIME type
3817 ----- -----------------------
3818 32 text/plain
3819 30 audio/mpeg
3820 29 image/png
3821 28 image/jpeg
3822 27 application/ogg
3823 26 audio/x-mp3
3824 25 image/tiff
3825 25 image/gif
3826 22 image/bmp
3827 22 audio/x-wav
3828 20 audio/x-flac
3829 19 audio/x-mpegurl
3830 18 video/x-ms-asf
3831 18 audio/x-musepack
3832 18 audio/x-mpeg
3833 18 application/x-ogg
3834 17 video/mpeg
3835 17 audio/x-scpls
3836 17 audio/ogg
3837 16 video/x-ms-wmv
3838 &lt;/pre&gt;
3839
3840 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3841
3842 &lt;pre&gt;
3843 count MIME type
3844 ----- -----------------------
3845 33 text/plain
3846 32 image/png
3847 32 image/jpeg
3848 29 audio/mpeg
3849 27 image/gif
3850 26 image/tiff
3851 26 application/ogg
3852 25 audio/x-mp3
3853 22 image/bmp
3854 21 audio/x-wav
3855 19 audio/x-mpegurl
3856 19 audio/x-mpeg
3857 18 video/mpeg
3858 18 audio/x-scpls
3859 18 audio/x-flac
3860 18 application/x-ogg
3861 17 video/x-ms-asf
3862 17 text/html
3863 17 audio/x-musepack
3864 16 image/x-xbitmap
3865 &lt;/pre&gt;
3866
3867 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3868
3869 &lt;pre&gt;
3870 count MIME type
3871 ----- -----------------------
3872 31 text/plain
3873 31 image/png
3874 31 image/jpeg
3875 29 audio/mpeg
3876 28 application/ogg
3877 27 image/gif
3878 26 image/tiff
3879 26 audio/x-mp3
3880 23 audio/x-wav
3881 22 image/bmp
3882 21 audio/x-flac
3883 20 audio/x-mpegurl
3884 19 audio/x-mpeg
3885 18 video/x-ms-asf
3886 18 video/mpeg
3887 18 audio/x-scpls
3888 18 application/x-ogg
3889 17 audio/x-musepack
3890 16 video/x-ms-wmv
3891 16 video/x-msvideo
3892 &lt;/pre&gt;
3893
3894 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3895 information mentioned in DEP-11. I have not yet had time to look at
3896 it, but hope the PackageKit people in Debian are on top of these
3897 issues.&lt;/p&gt;
3898
3899 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3900 discovering a typo in my script.&lt;/p&gt;
3901 </description>
3902 </item>
3903
3904 <item>
3905 <title>Using modalias info to find packages handling my hardware</title>
3906 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3908 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3909 <description>&lt;p&gt;Yesterday, I wrote about the
3910 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3911 values provided by the Linux kernel&lt;/a&gt; following my hope for
3912 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3913 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3914 modalias values attached to package names can be used to map packages
3915 to hardware. This allow the system to look up and suggest relevant
3916 packages when I plug in some new hardware into my machine, and replace
3917 discover and discover-data as the database used to map hardware to
3918 packages.&lt;/p&gt;
3919
3920 &lt;p&gt;I create a modaliases file with entries like the following,
3921 containing package name, kernel module name (if relevant, otherwise
3922 the package name) and globs matching the relevant hardware
3923 modalias.&lt;/p&gt;
3924
3925 &lt;p&gt;&lt;blockquote&gt;
3926 Package: package-name
3927 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3928 &lt;/blockquote&gt;&lt;/p&gt;
3929
3930 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3931 for a given modalias value using this file.&lt;/p&gt;
3932
3933 &lt;p&gt;An entry like this would suggest the video and picture application
3934 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3935
3936 &lt;p&gt;&lt;blockquote&gt;
3937 Package: cheese
3938 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3939 &lt;/blockquote&gt;&lt;/p&gt;
3940
3941 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3942 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3943
3944 &lt;p&gt;&lt;blockquote&gt;
3945 Package: pcmciautils
3946 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3947 &lt;/blockquote&gt;&lt;/p&gt;
3948
3949 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3950 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3951
3952 &lt;p&gt;&lt;blockquote&gt;
3953 Package: colorhug-client
3954 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3955 &lt;/blockquote&gt;&lt;/p&gt;
3956
3957 &lt;p&gt;I believe the format is compatible with the format of the Packages
3958 file in the Debian archive. Ubuntu already uses their Packages file
3959 to store their mappings from packages to hardware.&lt;/p&gt;
3960
3961 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3962 announce the hardware it support in a way my prototype understand.
3963 This allow those publishing packages in an APT source outside the
3964 Debian archive as well as those backporting packages to make sure the
3965 hardware mapping are included in the package meta information. I&#39;ve
3966 tested such header in the pymissile package, and its modalias mapping
3967 is working as it should with my prototype. It even made it to Ubuntu
3968 Raring.&lt;/p&gt;
3969
3970 &lt;p&gt;To test if it was possible to look up supported hardware using only
3971 the shell tools available in the Debian installer, I wrote a shell
3972 implementation of the lookup code. The idea is to create files for
3973 each modalias and let the shell do the matching. Please check out and
3974 try the
3975 &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;
3976 shell script. It run without any extra dependencies and fetch the
3977 hardware mappings from the Debian archive and the subversion
3978 repository where I currently work on my prototype.&lt;/p&gt;
3979
3980 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3981 install yubikey-personalization:&lt;/p&gt;
3982
3983 &lt;p&gt;&lt;blockquote&gt;
3984 % ./hw-support-lookup
3985 &lt;br&gt;yubikey-personalization
3986 &lt;br&gt;%
3987 &lt;/blockquote&gt;&lt;/p&gt;
3988
3989 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3990 propose to install the pcmciautils package:&lt;/p&gt;
3991
3992 &lt;p&gt;&lt;blockquote&gt;
3993 % ./hw-support-lookup
3994 &lt;br&gt;pcmciautils
3995 &lt;br&gt;%
3996 &lt;/blockquote&gt;&lt;/p&gt;
3997
3998 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3999 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4000 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4001
4002 &lt;p&gt;It could be possible to generate several of the mappings between
4003 packages and hardware. One source would be to look at packages with
4004 kernel modules, ie packages with *.ko files in /lib/modules/, and
4005 extract their modalias information. Another would be to look at
4006 packages with udev rules, ie packages with files in
4007 /lib/udev/rules.d/, and extract their vendor/model information to
4008 generate a modalias matching rule. I have not tested any of these to
4009 see if it work.&lt;/p&gt;
4010
4011 &lt;p&gt;If you want to help implementing a system to let us propose what
4012 packages to install when new hardware is plugged into a Debian
4013 machine, please send me an email or talk to me on
4014 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4015 </description>
4016 </item>
4017
4018 <item>
4019 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4020 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4022 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4023 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4024 information, to find the packages that support a given piece of
4025 hardware, I refreshed my memory regarding modalias values, and decided
4026 to document the details. Here are my findings so far, also available
4027 in
4028 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4029 Debian Edu subversion repository&lt;/a&gt;:
4030
4031 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4032
4033 &lt;p&gt;This document try to explain what the different types of modalias
4034 values stands for. It is in part based on information from
4035 &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;,
4036 &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;,
4037 &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
4038 &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;.
4039
4040 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4041 this shell script:&lt;/p&gt;
4042
4043 &lt;pre&gt;
4044 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4045 &lt;/pre&gt;
4046
4047 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4048 using modinfo:&lt;/p&gt;
4049
4050 &lt;pre&gt;
4051 % /sbin/modinfo psmouse | grep alias:
4052 alias: serio:ty05pr*id*ex*
4053 alias: serio:ty01pr*id*ex*
4054 %
4055 &lt;/pre&gt;
4056
4057 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4058
4059 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4060 Bridge memory controller:&lt;/p&gt;
4061
4062 &lt;p&gt;&lt;blockquote&gt;
4063 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4064 &lt;/blockquote&gt;&lt;/p&gt;
4065
4066 &lt;p&gt;This represent these values:&lt;/p&gt;
4067
4068 &lt;pre&gt;
4069 v 00008086 (vendor)
4070 d 00002770 (device)
4071 sv 00001028 (subvendor)
4072 sd 000001AD (subdevice)
4073 bc 06 (bus class)
4074 sc 00 (bus subclass)
4075 i 00 (interface)
4076 &lt;/pre&gt;
4077
4078 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4079 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4080 0600. The 0600 class is a host bridge. Other useful bus values are
4081 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4082
4083 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4084 means.&lt;/p&gt;
4085
4086 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4087
4088 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4089 USB hub in a laptop:&lt;/p&gt;
4090
4091 &lt;p&gt;&lt;blockquote&gt;
4092 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4093 &lt;/blockquote&gt;&lt;/p&gt;
4094
4095 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4096
4097 &lt;pre&gt;
4098 v 1D6B (device vendor)
4099 p 0001 (device product)
4100 d 0206 (bcddevice)
4101 dc 09 (device class)
4102 dsc 00 (device subclass)
4103 dp 00 (device protocol)
4104 ic 09 (interface class)
4105 isc 00 (interface subclass)
4106 ip 00 (interface protocol)
4107 &lt;/pre&gt;
4108
4109 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4110 class is in the interface class section. For a simple USB web camera,
4111 these alias entries show up:&lt;/p&gt;
4112
4113 &lt;p&gt;&lt;blockquote&gt;
4114 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4115 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4116 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4117 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4118 &lt;/blockquote&gt;&lt;/p&gt;
4119
4120 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4121 camera), 0101 is audio control device and 0102 is audio streaming (aka
4122 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4123
4124 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4125
4126 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4127 receiver in a Thinkpad X40:&lt;/p&gt;
4128
4129 &lt;p&gt;&lt;blockquote&gt;
4130 acpi:IBM0071:PNP0511:
4131 &lt;/blockquote&gt;&lt;/p&gt;
4132
4133 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4134
4135 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4136
4137 &lt;p&gt;The DMI table contain lots of information about the computer case
4138 and model. This is an entry for a IBM Thinkpad X40, fetched from
4139 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4140
4141 &lt;p&gt;&lt;blockquote&gt;
4142 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4143 &lt;/blockquote&gt;&lt;/p&gt;
4144
4145 &lt;p&gt;The values present are&lt;/p&gt;
4146
4147 &lt;pre&gt;
4148 bvn IBM (BIOS vendor)
4149 bvr 1UETB6WW(1.66) (BIOS version)
4150 bd 06/15/2005 (BIOS date)
4151 svn IBM (system vendor)
4152 pn 2371H4G (product name)
4153 pvr ThinkPadX40 (product version)
4154 rvn IBM (board vendor)
4155 rn 2371H4G (board name)
4156 rvr NotAvailable (board version)
4157 cvn IBM (chassis vendor)
4158 ct 10 (chassis type)
4159 cvr NotAvailable (chassis version)
4160 &lt;/pre&gt;
4161
4162 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4163 found in the dmidecode source:&lt;/p&gt;
4164
4165 &lt;pre&gt;
4166 3 Desktop
4167 4 Low Profile Desktop
4168 5 Pizza Box
4169 6 Mini Tower
4170 7 Tower
4171 8 Portable
4172 9 Laptop
4173 10 Notebook
4174 11 Hand Held
4175 12 Docking Station
4176 13 All In One
4177 14 Sub Notebook
4178 15 Space-saving
4179 16 Lunch Box
4180 17 Main Server Chassis
4181 18 Expansion Chassis
4182 19 Sub Chassis
4183 20 Bus Expansion Chassis
4184 21 Peripheral Chassis
4185 22 RAID Chassis
4186 23 Rack Mount Chassis
4187 24 Sealed-case PC
4188 25 Multi-system
4189 26 CompactPCI
4190 27 AdvancedTCA
4191 28 Blade
4192 29 Blade Enclosing
4193 &lt;/pre&gt;
4194
4195 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4196 table. For example my home server is a tower, but the DMI modalias
4197 claim it is a desktop.&lt;/p&gt;
4198
4199 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4200
4201 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4202 test machine:&lt;/p&gt;
4203
4204 &lt;p&gt;&lt;blockquote&gt;
4205 serio:ty01pr00id00ex00
4206 &lt;/blockquote&gt;&lt;/p&gt;
4207
4208 &lt;p&gt;The values present are&lt;/p&gt;
4209
4210 &lt;pre&gt;
4211 ty 01 (type)
4212 pr 00 (prototype)
4213 id 00 (id)
4214 ex 00 (extra)
4215 &lt;/pre&gt;
4216
4217 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4218 the valid values are.&lt;/p&gt;
4219
4220 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4221
4222 &lt;p&gt;There are heaps of other modalias subtypes according to
4223 file2alias.c. There is the rest of the list from that source: amba,
4224 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4225 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4226 vmbus, x86cpu and zorro. I did not spend time documenting all of
4227 these, as they do not seem relevant for my intended use with mapping
4228 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4229
4230 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4231
4232 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4233 one can use the following shell script:&lt;/p&gt;
4234
4235 &lt;pre&gt;
4236 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4237 echo &quot;$id&quot; ; \
4238 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4239 done
4240 &lt;/pre&gt;
4241
4242 &lt;p&gt;The output can look like this (only the first few entries as the
4243 list is very long on my test machine):&lt;/p&gt;
4244
4245 &lt;pre&gt;
4246 acpi:ACPI0003:
4247 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4248 acpi:device:
4249 FATAL: Module acpi:device: not found.
4250 acpi:IBM0068:
4251 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4252 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4253 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4254 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4255 acpi:IBM0071:PNP0511:
4256 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4257 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4258 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4259 [...]
4260 &lt;/pre&gt;
4261
4262 &lt;p&gt;If you want to help implementing a system to let us propose what
4263 packages to install when new hardware is plugged into a Debian
4264 machine, please send me an email or talk to me on
4265 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4266
4267 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4268 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4269 in /sys/ with space in them.&lt;/p&gt;
4270 </description>
4271 </item>
4272
4273 <item>
4274 <title>Moved the pymissile Debian packaging to collab-maint</title>
4275 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4277 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4278 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4279 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4280 Launcher and updated the Debian package
4281 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4282 sure udev will fix the device permissions when it is plugged in. I
4283 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4284 hopefully make the package be proposed by jockey in Ubuntu when a user
4285 plug in his rocket launcher. In the process I moved the source to a
4286 git repository under collab-maint, to make it easier for any DD to
4287 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4288 is not very active, but the software still work for me even after five
4289 years of relative silence. The new git repository is not listed in
4290 the uploaded package yet, because I want to test the other changes a
4291 bit more before I upload the new version. If you want to check out
4292 the new version with a .desktop file included, visit the
4293 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4294 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4295 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4296 </description>
4297 </item>
4298
4299 <item>
4300 <title>Lets make hardware dongles easier to use in Debian</title>
4301 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4303 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4304 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4305 general, is that there is a great package management system with the
4306 ability to automatically install software packages by downloading them
4307 from the distribution mirrors, but no way to get it to automatically
4308 install the packages I need to use the hardware I plug into my
4309 machine. Even if the package to use it is easily available from the
4310 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4311 suggest to automatically install the python-nxt, nbc and t2n packages
4312 I need to talk to it. When I plug in a Yubikey, it could propose the
4313 yubikey-personalization package. The information required to do this
4314 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4315
4316 &lt;p&gt;Some years ago, I proposed to
4317 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4318 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4319 simple:
4320
4321 &lt;ul&gt;
4322
4323 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4324 starting when a user log in.&lt;/li&gt;
4325
4326 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4327 hardware is inserted into the computer.&lt;/li&gt;
4328
4329 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4330 database mapping to packages, and take note of any non-installed
4331 packages.&lt;/li&gt;
4332
4333 &lt;li&gt;Show a message to the user proposing to install the discovered
4334 package, and make it easy to install it.&lt;/li&gt;
4335
4336 &lt;/ul&gt;
4337
4338 &lt;p&gt;I am not sure what the best way to implement this is, but my
4339 initial idea was to use dbus events to discover new hardware, the
4340 discover database to find packages and
4341 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4342 packages.&lt;/p&gt;
4343
4344 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4345 draft package is now checked into
4346 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4347 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4348 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4349 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4350 the relevant packages in Debian, and uploaded a new version
4351 2.2013.01.09 to unstable. I also discovered that the current
4352 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4353 package in Debian no longer discovered any USB devices, because
4354 /proc/bus/usb/devices is no longer present. I ported it to use
4355 libusb as a fall back option to get it working. The fixed package
4356 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4357 because of the freeze).&lt;/p&gt;
4358
4359 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4360 desktop notification to show up (only once, the first time it is
4361 inserted):&lt;/p&gt;
4362
4363 &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;
4364
4365 &lt;p&gt;For this prototype to be really useful, some way to automatically
4366 install the proposed packages by pressing the &quot;Please install
4367 program(s)&quot; button should to be implemented.&lt;/p&gt;
4368
4369 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4370 happen, please help me update the discover-data database with mappings
4371 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4372 list the package you would like to have installed when a given
4373 hardware device is inserted into your computer, and report bugs using
4374 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4375 such mapping, please let me know.&lt;/p&gt;
4376
4377 &lt;p&gt;This prototype need more work, and there are several questions that
4378 should be considered before it is ready for production use. Is dbus
4379 the correct way to detect new hardware? At the moment I look for HAL
4380 dbus events on the system bus, because that is the events I could see
4381 on my Debian Squeeze KDE desktop. Are there better events to use?
4382 How should the user be notified? Is the desktop notification
4383 mechanism the best option, or should the background daemon raise a
4384 popup instead? How should packages be installed? When should they
4385 not be installed?&lt;/p&gt;
4386
4387 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4388 please send me an email. :)&lt;/p&gt;
4389 </description>
4390 </item>
4391
4392 <item>
4393 <title>New IRC channel for LEGO designers using Debian</title>
4394 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4395 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4396 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4397 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4398 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4399 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4400 discovered I had to build all the tools myself because none were
4401 already in Debian Squeeze. If Debian support for LEGO is something
4402 you care about, please join me on the IRC channel
4403 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4404 irc.debian.org). There is a lot that could be done to improve the
4405 Debian support for LEGO designers. For example both CAD software
4406 and Mindstorm compilers are missing. :)&lt;/p&gt;
4407
4408 &lt;p&gt;Update 2012-01-03: A
4409 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4410 including links to Lego related packages is now available.&lt;/p&gt;
4411 </description>
4412 </item>
4413
4414 <item>
4415 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4416 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4417 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4418 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4419 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4420 year! I hope next year will prove to be a good year.&lt;/p&gt;
4421
4422 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4423 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4424 between each other with minimal overhead, is a very interesting
4425 experiment. And as I wrote a few days ago, the bitcoin situation in
4426 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4427 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4428 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4429 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4430 for one of the ftpmasters to approve the new bitcoin-qt package
4431 name.&lt;/p&gt;
4432
4433 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4434 team in Debian, you can easily test the package in Debian Squeeze
4435 using the following steps to get a set of working packages:&lt;/p&gt;
4436
4437 &lt;blockquote&gt;&lt;pre&gt;
4438 git clone git://git.debian.org/git/collab-maint/bitcoin
4439 cd bitcoin
4440 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4441 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4442 &lt;/pre&gt;&lt;/blockquote&gt;
4443
4444 &lt;p&gt;You might have to install some build dependencies as well. The
4445 list of commands should give you two packages, bitcoind and
4446 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4447 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4448 around 5.6 GiB of data on my machine at the moment. Make sure your
4449 ~/.bitcoin/ directory have lots of spare room if you want to download
4450 all the blocks. The client will warn if the disk is getting full, so
4451 there is not really a problem if you got too little room, but you will
4452 not be able to get all the features out of the client.&lt;/p&gt;
4453
4454 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4455 activities, please send Bitcoin donations to my address
4456 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4457 </description>
4458 </item>
4459
4460 <item>
4461 <title>A word on bitcoin support in Debian</title>
4462 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4463 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4464 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4465 <description>&lt;p&gt;It has been a while since I wrote about
4466 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4467 peer-to-peer based crypto-currency, and the reason is simply that I
4468 have been busy elsewhere. But two days ago, I started looking at the
4469 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4470 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4471 is now maintained by a
4472 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4473 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4474 owe a huge thank you to all these team members. :)
4475 But I was sad to discover that the bitcoin client is missing in
4476 Wheezy. It is only available in Sid (and an outdated client from
4477 backports). The client had several RC bugs registered in BTS blocking
4478 it from entering testing. To try to help the team and improve the
4479 situation, I spent some time providing patches and triaging the bug
4480 reports. I also had a look at the bitcoin package available from Matt
4481 Corallo in a
4482 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4483 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4484 Debian package.&lt;/p&gt;
4485
4486 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4487 IRC, I pushed several patches into the collab-maint git repository to
4488 improve the package. It now contains fixes for the RC issues (not from
4489 me, but fixed by Scott Howard), build rules for a Qt GUI client
4490 package, konqueror support for the bitcoin: URI and bash completion
4491 setup. As I work on Debian Squeeze, I also created
4492 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4493 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4494 it and try to integrate it into the git repository before uploading a
4495 new version to unstable.
4496
4497 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4498 centralized control currently exercised in the monetary system. I
4499 find it completely unacceptable that the USA government is collecting
4500 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4501 that the major credit card companies can block legal money
4502 transactions to Wikileaks. But for bitcoin to succeed, more people
4503 need to use bitcoins, and more people need to accept bitcoins when
4504 they sell products and services. Improving the bitcoin support in
4505 Debian is a small step in the right direction, but not enough.
4506 Unfortunately the user experience when browsing the web and wanting to
4507 pay with bitcoin is still not very good. The bitcoin: URI is a step
4508 in the right direction, but need to work in most or every browser in
4509 use. Also the bitcoin-qt client is too heavy to fire up to do a
4510 quick transaction. I believe there are other clients available, but
4511 have not tested them.&lt;/p&gt;
4512
4513 &lt;p&gt;My
4514 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4515 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4516 I received 20.15 BTC so far on the address I provided in my blog two
4517 years ago, as can be
4518 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4519 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4520 donation. The blockexplorer service demonstrates quite well that
4521 bitcoin is not quite anonymous and untracked. :) I wonder if the
4522 number of users have gone up since then. If you use bitcoin and want
4523 to show your support of my activity, please send Bitcoin donations to
4524 the same address as last time,
4525 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4526 </description>
4527 </item>
4528
4529 <item>
4530 <title>Git repository for song book for Computer Scientists</title>
4531 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4533 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4534 <description>&lt;p&gt;As I
4535 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4536 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4537 years ago, and today I finally found time to create a public
4538 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4539 repository for the project&lt;/a&gt;.&lt;/p&gt;
4540
4541 &lt;p&gt;If you want to help out, please clone the source and submit patches
4542 to the HTML version. To generate the PDF and PostScript version,
4543 please use prince XML, or let me know about a useful free software
4544 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4545
4546 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4547 PostScript formats at
4548 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4549 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4550 </description>
4551 </item>
4552
4553 <item>
4554 <title>Gratulerer med 19-årsdagen, Debian!</title>
4555 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4557 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4558 <description>&lt;p&gt;I dag fyller
4559 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4560 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4561 si gratulerer med dagen, Debian!&lt;/p&gt;
4562 </description>
4563 </item>
4564
4565 <item>
4566 <title>Song book for Computer Scientists</title>
4567 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4568 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4569 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4570 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4571 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4572 collecting computer related songs for use at parties. The original
4573 version was written in LaTeX, but a few years ago I got help from
4574 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4575 while keeping the ability to create a nice book in PDF format. I have
4576 not had time to maintain the book for a while now, and guess I should
4577 put it up on some public version control repository where others can
4578 help me extend and update the book. If anyone is volunteering to help
4579 me with this, send me an email. Also let me know if there are songs
4580 missing in my book.&lt;/p&gt;
4581
4582 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4583 me today that I really should let all my readers share the joys of
4584 singing out load about programming, computers and computer networks.
4585 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4586 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4587 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4588 Computer Science Songbook&lt;/a&gt;.
4589 </description>
4590 </item>
4591
4592 <item>
4593 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4594 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4595 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4596 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4597 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4598 around 1000 at the moment. To be able to get help from the vendors
4599 when something go wrong, we want to keep the firmware on the servers
4600 up to date. If the firmware isn&#39;t the latest and greatest, the
4601 vendors typically refuse to start debugging any problems until the
4602 firmware is upgraded. So before every reboot, we want to upgrade the
4603 firmware, and we would really like everyone handling servers at the
4604 university to do this themselves when they plan to reboot a machine.
4605 For that to happen we at the unix server admin group need to provide
4606 the tools to do so.&lt;/p&gt;
4607
4608 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4609 fetch and install the latest firmware for the servers we got. Most of
4610 our hardware are from Dell and HP, so I have focused on these servers
4611 so far. This blog post is about the Dell part.&lt;/P&gt;
4612
4613 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4614 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4615 with firmware information for all 11th generation servers, listing
4616 which firmware should be used on a given model and where on the FTP
4617 site I can find it. Using a simple perl XML parser I can then
4618 download the shell scripts Dell provides to do firmware upgrades from
4619 within Linux and reboot when all the firmware is primed and ready to
4620 be activated on the first reboot.&lt;/p&gt;
4621
4622 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4623 Are there anyone working on similar tools for firmware upgrading all
4624 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4625
4626 &lt;p&gt;&lt;pre&gt;
4627 #!/usr/bin/perl
4628 use strict;
4629 use warnings;
4630 use File::Temp qw(tempdir);
4631 BEGIN {
4632 # Install needed RHEL packages if missing
4633 my %rhelmodules = (
4634 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4635 );
4636 for my $module (keys %rhelmodules) {
4637 eval &quot;use $module;&quot;;
4638 if ($@) {
4639 my $pkg = $rhelmodules{$module};
4640 system(&quot;yum install -y $pkg&quot;);
4641 eval &quot;use $module;&quot;;
4642 }
4643 }
4644 }
4645 my $errorsto = &#39;pere@hungry.com&#39;;
4646
4647 upgrade_dell();
4648
4649 exit 0;
4650
4651 sub run_firmware_script {
4652 my ($opts, $script) = @_;
4653 unless ($script) {
4654 print STDERR &quot;fail: missing script name\n&quot;;
4655 exit 1
4656 }
4657 print STDERR &quot;Running $script\n\n&quot;;
4658
4659 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4660 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4661 } else {
4662 print STDERR &quot;fail: firmware script returned error\n&quot;;
4663 }
4664 }
4665
4666 sub run_firmware_scripts {
4667 my ($opts, @dirs) = @_;
4668 # Run firmware packages
4669 for my $dir (@dirs) {
4670 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4671 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4672 while (my $s = readdir $dh) {
4673 next if $s =~ m/^\.\.?/;
4674 run_firmware_script($opts, &quot;$dir/$s&quot;);
4675 }
4676 closedir $dh;
4677 }
4678 }
4679
4680 sub download {
4681 my $url = shift;
4682 print STDERR &quot;info: Downloading $url\n&quot;;
4683 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4684 }
4685
4686 sub upgrade_dell {
4687 my @dirs;
4688 my $product = `dmidecode -s system-product-name`;
4689 chomp $product;
4690
4691 if ($product =~ m/PowerEdge/) {
4692
4693 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4694 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4695
4696 my $tmpdir = tempdir(
4697 CLEANUP =&gt; 1
4698 );
4699 chdir($tmpdir);
4700 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4701 system(&#39;gunzip Catalog.xml.gz&#39;);
4702 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4703 # -q is quiet, disabling interactivity and reducing console output
4704 my $fwopts = &quot;-q&quot;;
4705 if (@paths) {
4706 for my $url (@paths) {
4707 fetch_dell_fw($url);
4708 }
4709 run_firmware_scripts($fwopts, $tmpdir);
4710 } else {
4711 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4712 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4713 }
4714 chdir(&#39;/&#39;);
4715 } else {
4716 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4717 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4718 }
4719 }
4720
4721 sub fetch_dell_fw {
4722 my $path = shift;
4723 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4724 download($url);
4725 }
4726
4727 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4728 # firmware packages to download from Dell. Only work for Linux
4729 # machines and 11th generation Dell servers.
4730 sub fetch_dell_fw_list {
4731 my $filename = shift;
4732
4733 my $product = `dmidecode -s system-product-name`;
4734 chomp $product;
4735 my ($mybrand, $mymodel) = split(/\s+/, $product);
4736
4737 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4738
4739 my $xml = XMLin($filename);
4740 my @paths;
4741 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4742 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4743 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4744 my $oscode;
4745 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4746 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4747 } else {
4748 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4749 }
4750 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4751 {
4752 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4753 }
4754 }
4755 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4756 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4757
4758 # Drop application packages, only firmware and BIOS
4759 next if &#39;APAC&#39; eq $componenttype;
4760
4761 my $cpath = $component-&gt;{path};
4762 for my $path (@paths) {
4763 if ($cpath =~ m%/$path$%) {
4764 push(@paths, $cpath);
4765 }
4766 }
4767 }
4768 return @paths;
4769 }
4770 &lt;/pre&gt;
4771
4772 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4773 it could work on other platforms with some tweaking. Anyone know a
4774 index like Catalog.xml is available from HP for HP servers? At the
4775 moment I maintain a similar list manually and it is quickly getting
4776 outdated.&lt;/p&gt;
4777 </description>
4778 </item>
4779
4780 <item>
4781 <title>How is booting into runlevel 1 different from single user boots?</title>
4782 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4783 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4784 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4785 <description>&lt;p&gt;Wouter Verhelst have some
4786 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4787 comments and opinions&lt;/a&gt; on my blog post on
4788 &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
4789 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4790 &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
4791 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4792 small piece of his comment now, and though it best to address the
4793 misunderstanding he bring forward:&lt;/p&gt;
4794
4795 &lt;p&gt;&lt;blockquote&gt;
4796 Currently, a system admin has four options: [...] boot to a
4797 single-user system (by adding &#39;single&#39; to the kernel command line;
4798 this runs rcS and rc1 scripts)
4799 &lt;/blockquote&gt;&lt;/p&gt;
4800
4801 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4802 and booting into runlevel 1 is the same. I am not surprised he
4803 believe this, because it would make sense and is a quite sensible
4804 thing to believe. But because the boot in Debian is slightly broken,
4805 runlevel 1 do not work properly and it isn&#39;t the same as single user
4806 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4807 hard to explain.&lt;/p&gt;
4808
4809 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4810 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4811 executed in single user mode is sulogin. Single user mode is a boot
4812 state &quot;between&quot; the runlevels, and when booting into single user mode,
4813 only the scripts in /etc/rcS.d/ are executed before the init process
4814 enters the single user state. When switching to runlevel 1, the state
4815 is in fact not ending in runlevel 1, but it passes through runlevel 1
4816 and end up in the single user mode (see /etc/rc1.d/S03single, which
4817 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4818 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4819 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4820 mode).&lt;/p&gt;
4821
4822 &lt;p&gt;This summary might make it clearer. When booting for the first
4823 time into single user mode, the following commands are executed:
4824 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4825 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4826 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4827 trying to continue after visiting single user mode. Not all services
4828 are started again as they should, causing the machine to end up in an
4829 unpredicatble state. This is why Debian admins recommend rebooting
4830 after visiting single user mode.&lt;/p&gt;
4831
4832 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4833 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4834 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4835 stopped when passing through the scripts in /etc/rc1.d/, and not
4836 started again when switching away from runlevel 1 to the runlevels
4837 2-5. I believe the problem is best fixed by moving all the scripts
4838 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4839 functioning single user mode during boot.&lt;/p&gt;
4840
4841 &lt;p&gt;I have spent several years investigating the Debian boot system,
4842 and discovered this problem a few years ago. I suspect it originates
4843 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4844 </description>
4845 </item>
4846
4847 <item>
4848 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4849 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4850 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4851 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4852 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4853 are started from /etc/rcS.d/. In fact, there is a bite more of them
4854 than make sense, and this causes a few problems. What kind of
4855 problems, you might ask. There are at least two problems. The first
4856 is that it is not possible to recover a machine after switching to
4857 runlevel 1. One need to actually reboot to get the machine back to
4858 the expected state. The other is that single user boot will sometimes
4859 run into problems because some of the subsystems are activated before
4860 the root login is presented, causing problems when trying to recover a
4861 machine from a problem in that subsystem. A minor additional point is
4862 that moving more scripts out of rcS.d/ and into the other rc#.d/
4863 directories will increase the amount of scripts that can run in
4864 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4865
4866 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4867 scripts that _have_ to execute before the root login prompt is
4868 presented during a single user boot should go there. Everything else
4869 should go into the numeric runlevels. This means things like
4870 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4871 the numeric runlevels. Today in Debian, there are around 115 init.d
4872 scripts that are started from rcS.d/, and most of them should be moved
4873 out. Do your package have one of them? Please help us make single
4874 user and runlevel 1 better by moving it.&lt;/p&gt;
4875
4876 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4877 etc. should still be started from rcS.d/, but there is for example no
4878 need to have the network enabled before the single user login prompt
4879 is presented.&lt;/p&gt;
4880
4881 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4882 Debian systems working while scripts migrate and during upgrades, the
4883 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4884 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4885 and the next ones can only be moved when their dependencies have been
4886 moved first. This migration must be done sequentially while we ensure
4887 that the package system upgrade packages in the right order to keep
4888 the system state correct. This will require some coordination when it
4889 comes to network related packages, but most of the packages with
4890 scripts that should migrate do not have anything in rcS.d/ depending
4891 on them. Some packages have already been updated, like the sudo
4892 package, while others are still left to do. I wish I had time to work
4893 on this myself, but real live constrains make it unlikely that I will
4894 find time to push this forward.&lt;/p&gt;
4895 </description>
4896 </item>
4897
4898 <item>
4899 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4900 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4901 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4902 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4903 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4904 mentioned the issues I believe should be improved in Debian for its
4905 desktop to be useful for more people. The use case for this is my
4906 parents, which are currently running Kubuntu which solve the
4907 issues.&lt;/p&gt;
4908
4909 &lt;p&gt;I suspect these four missing features are not very hard to
4910 implement. After all, they are present in Ubuntu, so if we wanted to
4911 do this in Debian we would have a source.&lt;/p&gt;
4912
4913 &lt;ol&gt;
4914
4915 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4916 are new packages available for upgrades, a icon in the KDE status bar
4917 indicate this, and clicking on it will activate the simple upgrade
4918 tool to handle it. I have no problem guiding both of my parents
4919 through the process over the phone. If a kernel reboot is required,
4920 this too is indicated by the status bars and the upgrade tool. Last
4921 time I checked, nothing with the same features was working in KDE in
4922 Debian.&lt;/li&gt;
4923
4924 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4925 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4926 currently have a handler for, it will ask the user if the system
4927 should search for a package that would add support for this MIME type,
4928 and if the user say yes, the APT sources will be searched for packages
4929 advertising the MIME type in their control file (visible in the
4930 Packages file in the APT archive). If one or more packages are found,
4931 it is a simple click of the mouse to add support for the missing mime
4932 type. If the package require the user to accept some non-free
4933 license, this is explained to the user. The entire process make it
4934 more clear to the user why something do not work in the browser, and
4935 make the chances higher for the user to blame the web page authors and
4936 not the browser for any missing features.&lt;/li&gt;
4937
4938 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4939 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4940 it is not supporting, a dialog pop up asking the user if the system
4941 should search for a package that would add support for it. This
4942 happen with things like MP3, Windows Media or H.264. The selection
4943 and installation procedure is very similar to the Firefox browser
4944 plugin handling. This is as far as I know implemented using a
4945 gstreamer hook. The end result is that the user easily get access to
4946 the codecs that are present from the APT archives available, while
4947 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4948
4949 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4950 displaying a text/plain file in my Debian browser, it will propose to
4951 start emacs to show it. If I remember correctly, when doing the same
4952 in Kunbutu it show the file as a text file in the browser. At least I
4953 know Opera will show text files within the browser. I much prefer the
4954 latter behaviour.&lt;/li&gt;
4955
4956 &lt;/ol&gt;
4957
4958 &lt;p&gt;There are other nice features as well, like the simplified suite
4959 upgrader, but given that I am the one mostly doing the dist-upgrade,
4960 it do not matter much.&lt;/p&gt;
4961
4962 &lt;p&gt;I really hope we could get these features in place for the next
4963 Debian release. It would require the coordinated effort of several
4964 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4965 </description>
4966 </item>
4967
4968 <item>
4969 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4970 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4971 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4972 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4973 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4974 site is build on Debian/Squeeze, and this platform was chosen because
4975 I am most familiar with Debian (being a Debian Developer for around 10
4976 years) because it is the latest stable Debian release which should get
4977 security support for a few years.&lt;/p&gt;
4978
4979 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4980 that are missing in Debian at the moment. It would be great if these
4981 modules were added to the Debian archive, allowing anyone to set up
4982 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4983 in their own country using only Debian packages. The list of modules
4984 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4985 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4986 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4987 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4988 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4989 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4990 easier in the future.&lt;/p&gt;
4991
4992 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4993 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4994 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4995 with the responsibility of tracking security problems, which I really
4996 do not have time for.&lt;/p&gt;
4997 </description>
4998 </item>
4999
5000 <item>
5001 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5002 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5003 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5004 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5005 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5006 posts have been in Norwegian the last few weeks, so here is a short
5007 update in English.&lt;/p&gt;
5008
5009 &lt;p&gt;The kids still keep me too busy to get much free software work
5010 done, but I did manage to organise a project to get a Norwegian port
5011 of the British service
5012 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5013 and it has been running for a month now. The entire project has been
5014 organised by me and two others. Around Christmas we gathered sponsors
5015 to fund the development work. In January I drafted a contract with
5016 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5017 and in February the development took place. Most of it involved
5018 converting the source to use GPS coordinates instead of British
5019 easting/northing, and the resulting code should be a lot easier to get
5020 running in any country by now. The Norwegian
5021 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5022 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5023 source and the source for administrative borders in Norway, and
5024 support for this had to be added/fixed.&lt;/p&gt;
5025
5026 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5027 polishing the system before we announced it March 7th. The system is
5028 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5029 problem reports in a few weeks. Soon we hope to announce the Android
5030 and iPhone versions making it even easier to report problems with the
5031 public infrastructure.&lt;/p&gt;
5032
5033 &lt;p&gt;Perhaps something to consider for those of you in countries without
5034 such service?&lt;/p&gt;
5035 </description>
5036 </item>
5037
5038 <item>
5039 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5040 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5041 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5042 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5043 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5044 issues here at my work with the University of Oslo. My idea is that
5045 it should be possible to use the information about security issues
5046 available on the Internet, and check our locally
5047 maintained/distributed software against this information. It should
5048 allow us to verify that no known security issues are forgotten. The
5049 CVE database listing vulnerabilities seem like a great central point,
5050 and by using the package lists from Debian mapped to CVEs provided by
5051 the testing security team, I believed it should be possible to figure
5052 out which security holes were present in our free software
5053 collection.&lt;/p&gt;
5054
5055 &lt;p&gt;After reading up on the topic, it became obvious that the first
5056 building block is to be able to name software packages in a unique and
5057 consistent way across data sources. I considered several ways to do
5058 this, for example coming up with my own naming scheme like using URLs
5059 to project home pages or URLs to the Freshmeat entries, or using some
5060 existing naming scheme. And it seem like I am not the first one to
5061 come across this problem, as MITRE already proposed and implemented a
5062 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5063 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5064 software, hardware and other platform components. The CPE ids are
5065 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5066 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5067 issues for any CPE name. With this in place, all I need to do is to
5068 locate the CPE id for the software packages we use at the university.
5069 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5070 NVD entry if a CVE for the package exist).&lt;/p&gt;
5071
5072 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5073 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5074 check out, one could look up
5075 &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
5076 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5077 The most recent one is
5078 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5079 and at the bottom of the NVD page for this vulnerability the complete
5080 list of affected versions is provided.&lt;/p&gt;
5081
5082 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5083 for offline processing of issues. Using this dump, I&#39;ve written a
5084 small script taking a list of CPEs as input and list all CVEs
5085 affecting the packages represented by these CPEs. One give it CPEs
5086 with version numbers as specified above and get a list of open
5087 security issues out.&lt;/p&gt;
5088
5089 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5090 information need to be high. For that to happen, I believe as many as
5091 possible need to use and contribute to the NVD database. I notice
5092 RHEL is providing
5093 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5094 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5095 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5096
5097 &lt;p&gt;To get an idea about the quality for free software, I spent some
5098 time making it possible to compare the CVE database from Debian with
5099 the CVE database in NVD. The result look fairly good, but there are
5100 some inconsistencies in NVD (same software package having several
5101 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5102 Debian believe are affected by a CVE). Hope to find time to improve
5103 the quality of NVD, but that require being able to get in touch with
5104 someone maintaining it. So far my three emails with questions and
5105 corrections have not seen any reply, but I hope contact can be
5106 established soon.&lt;/p&gt;
5107
5108 &lt;p&gt;An interesting application for CPEs is cross platform package
5109 mapping. It would be useful to know which packages in for example
5110 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5111 this would be trivial if all linux distributions provided CPE entries
5112 for their packages.&lt;/p&gt;
5113 </description>
5114 </item>
5115
5116 <item>
5117 <title>Which module is loaded for a given PCI and USB device?</title>
5118 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5120 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5121 <description>&lt;p&gt;In the
5122 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5123 package in Debian, there is a script to report useful information
5124 about the running hardware for use when people report missing
5125 information. One part of this script that I find very useful when
5126 debugging hardware problems, is the part mapping loaded kernel module
5127 to the PCI device it claims. It allow me to quickly see if the kernel
5128 module I expect is driving the hardware I am struggling with. To see
5129 the output, make sure discover-data is installed and run
5130 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5131 one of my machines like this:&lt;/p&gt;
5132
5133 &lt;pre&gt;
5134 loaded modules:
5135 10de:03eb i2c_nforce2
5136 10de:03f1 ohci_hcd
5137 10de:03f2 ehci_hcd
5138 10de:03f0 snd_hda_intel
5139 10de:03ec pata_amd
5140 10de:03f6 sata_nv
5141 1022:1103 k8temp
5142 109e:036e bttv
5143 109e:0878 snd_bt87x
5144 11ab:4364 sky2
5145 &lt;/pre&gt;
5146
5147 &lt;p&gt;The code in question look like this, slightly modified for
5148 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5149
5150 &lt;pre&gt;
5151 if [ -d /sys/bus/pci/devices/ ] ; then
5152 echo loaded pci modules:
5153 (
5154 cd /sys/bus/pci/devices/
5155 for address in * ; do
5156 if [ -d &quot;$address/driver/module&quot; ] ; then
5157 module=`cd $address/driver/module ; pwd -P | xargs basename`
5158 if grep -q &quot;^$module &quot; /proc/modules ; then
5159 address=$(echo $address |sed s/0000://)
5160 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5161 echo &quot;$id $module&quot;
5162 fi
5163 fi
5164 done
5165 )
5166 echo
5167 fi
5168 &lt;/pre&gt;
5169
5170 &lt;p&gt;Similar code could be used to extract USB device module
5171 mappings:&lt;/p&gt;
5172
5173 &lt;pre&gt;
5174 if [ -d /sys/bus/usb/devices/ ] ; then
5175 echo loaded usb modules:
5176 (
5177 cd /sys/bus/usb/devices/
5178 for address in * ; do
5179 if [ -d &quot;$address/driver/module&quot; ] ; then
5180 module=`cd $address/driver/module ; pwd -P | xargs basename`
5181 if grep -q &quot;^$module &quot; /proc/modules ; then
5182 address=$(echo $address |sed s/0000://)
5183 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5184 if [ &quot;$id&quot; ] ; then
5185 echo &quot;$id $module&quot;
5186 fi
5187 fi
5188 fi
5189 done
5190 )
5191 echo
5192 fi
5193 &lt;/pre&gt;
5194
5195 &lt;p&gt;This might perhaps be something to include in other tools as
5196 well.&lt;/p&gt;
5197 </description>
5198 </item>
5199
5200 <item>
5201 <title>How to test if a laptop is working with Linux</title>
5202 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5203 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5204 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5205 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5206 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5207 batch of computers will work with Linux. Every year for the last few
5208 years the university have organised shared bid of a few thousand
5209 computers, and this year HP won the bid. Two different desktops and
5210 five different laptops are on the list this year. We in the UNIX
5211 group want to know which one of these computers work well with RHEL
5212 and Ubuntu, the two Linux distributions we currently handle at the
5213 university.&lt;/p&gt;
5214
5215 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5216 perhaps inspire others to test hardware as well. To test, I PXE
5217 install the OS version of choice, and log in as my normal user and run
5218 a few applications and plug in selected pieces of hardware. When
5219 something fail, I make a note about this in the test matrix and move
5220 on. If I have some spare time I try to report the bug to the OS
5221 vendor, but as I only have the machines for a short time, I rarely
5222 have the time to do this for all the problems I find.&lt;/p&gt;
5223
5224 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5225 I perform on a new model.&lt;/p&gt;
5226
5227 &lt;ul&gt;
5228
5229 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5230 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5231 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5232
5233 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5234 installation, X.org is working.&lt;/li&gt;
5235
5236 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5237 package mesa-utils on Ubuntu) and writing down the frames per second
5238 reported by the program.&lt;/li&gt;
5239
5240 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5241 logging in, and if I can hear this the test is successful. If there
5242 are several audio exits on the machine, I try them all and check if
5243 the Gnome/KDE audio mixer can control where to send the sound. I
5244 normally test this by playing
5245 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5246 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5247
5248 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5249 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5250
5251 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5252 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5253
5254 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5255 picture from the v4l device show up.&lt;/li&gt;
5256
5257 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5258 any bluetooth devices are discovered. In my office, I normally see a
5259 few.&lt;/li&gt;
5260
5261 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5262 memory modules lying around, and stick them in and see if Gnome/KDE
5263 notice this.&lt;/li&gt;
5264
5265 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5266 special button work, and if the laptop continue to work after
5267 resume.&lt;/li&gt;
5268
5269 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5270 adjusting background light, switching on/off external video output,
5271 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5272 laptop to laptop, so I just write down which are working and which are
5273 not.&lt;/li&gt;
5274
5275 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5276 acceleration sensors etc. I rarely test these, as I do not know how
5277 to quickly test if they are working or not, so I only document their
5278 existence.&lt;/li&gt;
5279
5280 &lt;/ul&gt;
5281
5282 &lt;p&gt;By now I suspect you are really curious what the test results are
5283 for the HP machines I am testing. I&#39;m not done yet, so I will report
5284 the test results later. For now I can report that HP 8100 Elite work
5285 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5286 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5287 can see, I have most machines left to test. One interesting
5288 observation is that Ubuntu Lucid has almost twice the frame rate than
5289 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5290 </description>
5291 </item>
5292
5293 <item>
5294 <title>Some thoughts on BitCoins</title>
5295 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5297 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5298 <description>&lt;p&gt;As I continue to explore
5299 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5300 what properties the system have, and how it will be affected by laws
5301 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5302
5303 &lt;p&gt;One interesting thing to note is that since the transactions are
5304 verified using a peer to peer network, all details about a transaction
5305 is known to everyone. This means that if a BitCoin address has been
5306 published like I did with mine in my initial post about BitCoin, it is
5307 possible for everyone to see how many BitCoins have been transfered to
5308 that address. There is even a web service to look at the details for
5309 all transactions. There I can see that my address
5310 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5311 have received 16.06 Bitcoin, the
5312 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5313 address of Simon Phipps have received 181.97 BitCoin and the address
5314 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5315 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5316 every one of you that donated bitcoins to support my activity. The
5317 fact that anyone can see how much money was transfered to a given
5318 address make it more obvious why the BitCoin community recommend to
5319 generate and hand out a new address for each transaction. I&#39;m told
5320 there is no way to track which addresses belong to a given person or
5321 organisation without the person or organisation revealing it
5322 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5323
5324 &lt;p&gt;In Norway, and in most other countries, there are laws and
5325 regulations limiting how much money one can transfer across the border
5326 without declaring it. There are money laundering, tax and accounting
5327 laws and regulations I would expect to apply to the use of BitCoin.
5328 If the Skolelinux foundation
5329 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5330 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5331 normal bank transfers like EFF is doing, how should this be accounted?
5332 Given that it is impossible to know if money can cross the border or
5333 not, should everything or nothing be declared? What exchange rate
5334 should be used when calculating taxes? Would receivers have to pay
5335 income tax if the foundation were to pay Skolelinux contributors in
5336 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5337
5338 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5339 accepted by a lot of users. It must be possible to get easy access to
5340 the currency (as a wage or using currency exchanges), and it must be
5341 easy to spend it. At the moment BitCoin seem fairly easy to get
5342 access to, but there are very few places to spend it. I am not really
5343 a regular user of any of the vendor types currently accepting BitCoin,
5344 so I wonder when my kind of shop would start accepting BitCoins. I
5345 would like to buy electronics, travels and subway tickets, not herbs
5346 and books. :) The currency is young, and this will improve over time
5347 if it become popular, but I suspect regular banks will start to lobby
5348 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5349 will claim it is helping fund terrorism and money laundering (which
5350 probably would be true, as is any currency in existence), but I
5351 believe the problems should be solved elsewhere and not by blaming
5352 currencies.&lt;/p&gt;
5353
5354 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5355 CPU intensive process that depend on a bit of luck as well (as one is
5356 competing against all the other miners currently spending CPU cycles
5357 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5358 BitCoin when this happen. Yesterday I came across the obvious way to
5359 join forces to increase ones changes of getting at least some coins,
5360 by coordinating the work on mining BitCoins across several machines
5361 and people, and sharing the result if one is lucky and get the 50
5362 BitCoins. Check out
5363 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5364 if this sounds interesting. I have not had time to try to set up a
5365 machine to participate there yet, but have seen that running on ones
5366 own for a few days have not yield any BitCoins througth mining
5367 yet.&lt;/p&gt;
5368
5369 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5370 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5371 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5372 it was interesting to read. The arguments presented seem to be
5373 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5374 </description>
5375 </item>
5376
5377 <item>
5378 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5379 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5380 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5381 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5382 <description>&lt;p&gt;With this weeks lawless
5383 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5384 attacks&lt;/a&gt; on Wikileak and
5385 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5386 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5387 not be trusted to handle money transactions.
5388 A blog post from
5389 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5390 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5391 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5392 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5393 some help from my friend to get it all running, and he even handed me
5394 some bitcoins to get started. I even donated a few bitcoins to Simon
5395 for helping me remember BitCoin.&lt;/p&gt;
5396
5397 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5398 crypto-currency, decentralised and handled using peer-to-peer
5399 networks. It allows anonymous transactions and prohibits central
5400 control over the transactions, making it impossible for governments
5401 and companies alike to block donations and other transactions. The
5402 source is free software, and while the key dependency wxWidgets 2.9
5403 for the graphical user interface is missing in Debian, the command
5404 line client builds just fine. Hopefully Jonas
5405 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5406 Debian&lt;/a&gt; soon.&lt;/p&gt;
5407
5408 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5409 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5410 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5411 currency &quot;stock&quot; markets where the exchange rate is decided. There
5412 are not many users so far, but the concept seems promising. If you
5413 want to get started and lack a friend with any bitcoins to spare,
5414 you can even get
5415 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5416 bitcoin at the time of writing). Use
5417 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5418 on the current exchange rates.&lt;/p&gt;
5419
5420 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5421 machines. If you want to support my activity, please send Bitcoin
5422 donations to the address
5423 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5424 </description>
5425 </item>
5426
5427 <item>
5428 <title>Why isn&#39;t Debian Edu using VLC?</title>
5429 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5431 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5432 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5433 presented, and the winner among the multimedia player were VLC.
5434 Personally, I like VLC, and it is my player of choice when I first try
5435 to play a video file or stream. Only if VLC fail will I drag out
5436 gmplayer to see if it can do better. The reason is mostly the failure
5437 model and trust. When VLC fail, it normally pop up a error message
5438 reporting the problem. When mplayer fail, it normally segfault or
5439 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5440
5441 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5442 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5443 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5444 plugin to play web videos seamlessly, and the VLC browser plugin is
5445 not very good. For example, it lack in-line control buttons, so there
5446 is no way for the user to pause the video. Also, when I
5447 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5448 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5449 failed on several video pages where mplayer based plugins worked. If
5450 the browser plugin for VLC was as good as the gecko-mediaplayer
5451 package (which uses mplayer), we would switch.&lt;/P&gt;
5452
5453 &lt;p&gt;While VLC is a good player, its user interface is slightly
5454 annoying. The most annoying feature is its inconsistent use of
5455 keyboard shortcuts. When the player is in full screen mode, its
5456 shortcuts are different from when it is playing the video in a window.
5457 For example, space only work as pause when in full screen mode. I
5458 wish it had consisten shortcuts and that space also would work when in
5459 window mode. Another nice shortcut in gmplayer is [enter] to restart
5460 the current video. It is very nice when playing short videos from the
5461 web and want to restart it when new people arrive to have a look at
5462 what is going on.&lt;/p&gt;
5463 </description>
5464 </item>
5465
5466 <item>
5467 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5468 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5469 <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>
5470 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5471 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5472 upgrade testing of the
5473 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5474 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5475 This seem like a very good idea, so I adjusted by test scripts and
5476 can now present the updated result from today:&lt;/p&gt;
5477
5478 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5479
5480 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5481
5482 &lt;blockquote&gt;&lt;p&gt;
5483 apache2.2-bin
5484 aptdaemon
5485 baobab
5486 binfmt-support
5487 browser-plugin-gnash
5488 cheese-common
5489 cli-common
5490 cups-pk-helper
5491 dmz-cursor-theme
5492 empathy
5493 empathy-common
5494 freedesktop-sound-theme
5495 freeglut3
5496 gconf-defaults-service
5497 gdm-themes
5498 gedit-plugins
5499 geoclue
5500 geoclue-hostip
5501 geoclue-localnet
5502 geoclue-manual
5503 geoclue-yahoo
5504 gnash
5505 gnash-common
5506 gnome
5507 gnome-backgrounds
5508 gnome-cards-data
5509 gnome-codec-install
5510 gnome-core
5511 gnome-desktop-environment
5512 gnome-disk-utility
5513 gnome-screenshot
5514 gnome-search-tool
5515 gnome-session-canberra
5516 gnome-system-log
5517 gnome-themes-extras
5518 gnome-themes-more
5519 gnome-user-share
5520 gstreamer0.10-fluendo-mp3
5521 gstreamer0.10-tools
5522 gtk2-engines
5523 gtk2-engines-pixbuf
5524 gtk2-engines-smooth
5525 hamster-applet
5526 libapache2-mod-dnssd
5527 libapr1
5528 libaprutil1
5529 libaprutil1-dbd-sqlite3
5530 libaprutil1-ldap
5531 libart2.0-cil
5532 libboost-date-time1.42.0
5533 libboost-python1.42.0
5534 libboost-thread1.42.0
5535 libchamplain-0.4-0
5536 libchamplain-gtk-0.4-0
5537 libcheese-gtk18
5538 libclutter-gtk-0.10-0
5539 libcryptui0
5540 libdiscid0
5541 libelf1
5542 libepc-1.0-2
5543 libepc-common
5544 libepc-ui-1.0-2
5545 libfreerdp-plugins-standard
5546 libfreerdp0
5547 libgconf2.0-cil
5548 libgdata-common
5549 libgdata7
5550 libgdu-gtk0
5551 libgee2
5552 libgeoclue0
5553 libgexiv2-0
5554 libgif4
5555 libglade2.0-cil
5556 libglib2.0-cil
5557 libgmime2.4-cil
5558 libgnome-vfs2.0-cil
5559 libgnome2.24-cil
5560 libgnomepanel2.24-cil
5561 libgpod-common
5562 libgpod4
5563 libgtk2.0-cil
5564 libgtkglext1
5565 libgtksourceview2.0-common
5566 libmono-addins-gui0.2-cil
5567 libmono-addins0.2-cil
5568 libmono-cairo2.0-cil
5569 libmono-corlib2.0-cil
5570 libmono-i18n-west2.0-cil
5571 libmono-posix2.0-cil
5572 libmono-security2.0-cil
5573 libmono-sharpzip2.84-cil
5574 libmono-system2.0-cil
5575 libmtp8
5576 libmusicbrainz3-6
5577 libndesk-dbus-glib1.0-cil
5578 libndesk-dbus1.0-cil
5579 libopal3.6.8
5580 libpolkit-gtk-1-0
5581 libpt2.6.7
5582 libpython2.6
5583 librpm1
5584 librpmio1
5585 libsdl1.2debian
5586 libsrtp0
5587 libssh-4
5588 libtelepathy-farsight0
5589 libtelepathy-glib0
5590 libtidy-0.99-0
5591 media-player-info
5592 mesa-utils
5593 mono-2.0-gac
5594 mono-gac
5595 mono-runtime
5596 nautilus-sendto
5597 nautilus-sendto-empathy
5598 p7zip-full
5599 pkg-config
5600 python-aptdaemon
5601 python-aptdaemon-gtk
5602 python-axiom
5603 python-beautifulsoup
5604 python-bugbuddy
5605 python-clientform
5606 python-coherence
5607 python-configobj
5608 python-crypto
5609 python-cupshelpers
5610 python-elementtree
5611 python-epsilon
5612 python-evolution
5613 python-feedparser
5614 python-gdata
5615 python-gdbm
5616 python-gst0.10
5617 python-gtkglext1
5618 python-gtksourceview2
5619 python-httplib2
5620 python-louie
5621 python-mako
5622 python-markupsafe
5623 python-mechanize
5624 python-nevow
5625 python-notify
5626 python-opengl
5627 python-openssl
5628 python-pam
5629 python-pkg-resources
5630 python-pyasn1
5631 python-pysqlite2
5632 python-rdflib
5633 python-serial
5634 python-tagpy
5635 python-twisted-bin
5636 python-twisted-conch
5637 python-twisted-core
5638 python-twisted-web
5639 python-utidylib
5640 python-webkit
5641 python-xdg
5642 python-zope.interface
5643 remmina
5644 remmina-plugin-data
5645 remmina-plugin-rdp
5646 remmina-plugin-vnc
5647 rhythmbox-plugin-cdrecorder
5648 rhythmbox-plugins
5649 rpm-common
5650 rpm2cpio
5651 seahorse-plugins
5652 shotwell
5653 software-center
5654 system-config-printer-udev
5655 telepathy-gabble
5656 telepathy-mission-control-5
5657 telepathy-salut
5658 tomboy
5659 totem
5660 totem-coherence
5661 totem-mozilla
5662 totem-plugins
5663 transmission-common
5664 xdg-user-dirs
5665 xdg-user-dirs-gtk
5666 xserver-xephyr
5667 &lt;/p&gt;&lt;/blockquote&gt;
5668
5669 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5670
5671 &lt;blockquote&gt;&lt;p&gt;
5672 cheese
5673 ekiga
5674 eog
5675 epiphany-extensions
5676 evolution-exchange
5677 fast-user-switch-applet
5678 file-roller
5679 gcalctool
5680 gconf-editor
5681 gdm
5682 gedit
5683 gedit-common
5684 gnome-games
5685 gnome-games-data
5686 gnome-nettool
5687 gnome-system-tools
5688 gnome-themes
5689 gnuchess
5690 gucharmap
5691 guile-1.8-libs
5692 libavahi-ui0
5693 libdmx1
5694 libgalago3
5695 libgtk-vnc-1.0-0
5696 libgtksourceview2.0-0
5697 liblircclient0
5698 libsdl1.2debian-alsa
5699 libspeexdsp1
5700 libsvga1
5701 rhythmbox
5702 seahorse
5703 sound-juicer
5704 system-config-printer
5705 totem-common
5706 transmission-gtk
5707 vinagre
5708 vino
5709 &lt;/p&gt;&lt;/blockquote&gt;
5710
5711 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5712
5713 &lt;blockquote&gt;&lt;p&gt;
5714 gstreamer0.10-gnomevfs
5715 &lt;/p&gt;&lt;/blockquote&gt;
5716
5717 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5718
5719 &lt;blockquote&gt;&lt;p&gt;
5720 [nothing]
5721 &lt;/p&gt;&lt;/blockquote&gt;
5722
5723 &lt;p&gt;This is for KDE:&lt;/p&gt;
5724
5725 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5726
5727 &lt;blockquote&gt;&lt;p&gt;
5728 ksmserver
5729 &lt;/p&gt;&lt;/blockquote&gt;
5730
5731 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5732
5733 &lt;blockquote&gt;&lt;p&gt;
5734 kwin
5735 network-manager-kde
5736 &lt;/p&gt;&lt;/blockquote&gt;
5737
5738 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5739
5740 &lt;blockquote&gt;&lt;p&gt;
5741 arts
5742 dolphin
5743 freespacenotifier
5744 google-gadgets-gst
5745 google-gadgets-xul
5746 kappfinder
5747 kcalc
5748 kcharselect
5749 kde-core
5750 kde-plasma-desktop
5751 kde-standard
5752 kde-window-manager
5753 kdeartwork
5754 kdeartwork-emoticons
5755 kdeartwork-style
5756 kdeartwork-theme-icon
5757 kdebase
5758 kdebase-apps
5759 kdebase-workspace
5760 kdebase-workspace-bin
5761 kdebase-workspace-data
5762 kdeeject
5763 kdelibs
5764 kdeplasma-addons
5765 kdeutils
5766 kdewallpapers
5767 kdf
5768 kfloppy
5769 kgpg
5770 khelpcenter4
5771 kinfocenter
5772 konq-plugins-l10n
5773 konqueror-nsplugins
5774 kscreensaver
5775 kscreensaver-xsavers
5776 ktimer
5777 kwrite
5778 libgle3
5779 libkde4-ruby1.8
5780 libkonq5
5781 libkonq5-templates
5782 libnetpbm10
5783 libplasma-ruby
5784 libplasma-ruby1.8
5785 libqt4-ruby1.8
5786 marble-data
5787 marble-plugins
5788 netpbm
5789 nuvola-icon-theme
5790 plasma-dataengines-workspace
5791 plasma-desktop
5792 plasma-desktopthemes-artwork
5793 plasma-runners-addons
5794 plasma-scriptengine-googlegadgets
5795 plasma-scriptengine-python
5796 plasma-scriptengine-qedje
5797 plasma-scriptengine-ruby
5798 plasma-scriptengine-webkit
5799 plasma-scriptengines
5800 plasma-wallpapers-addons
5801 plasma-widget-folderview
5802 plasma-widget-networkmanagement
5803 ruby
5804 sweeper
5805 update-notifier-kde
5806 xscreensaver-data-extra
5807 xscreensaver-gl
5808 xscreensaver-gl-extra
5809 xscreensaver-screensaver-bsod
5810 &lt;/p&gt;&lt;/blockquote&gt;
5811
5812 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5813
5814 &lt;blockquote&gt;&lt;p&gt;
5815 ark
5816 google-gadgets-common
5817 google-gadgets-qt
5818 htdig
5819 kate
5820 kdebase-bin
5821 kdebase-data
5822 kdepasswd
5823 kfind
5824 klipper
5825 konq-plugins
5826 konqueror
5827 ksysguard
5828 ksysguardd
5829 libarchive1
5830 libcln6
5831 libeet1
5832 libeina-svn-06
5833 libggadget-1.0-0b
5834 libggadget-qt-1.0-0b
5835 libgps19
5836 libkdecorations4
5837 libkephal4
5838 libkonq4
5839 libkonqsidebarplugin4a
5840 libkscreensaver5
5841 libksgrd4
5842 libksignalplotter4
5843 libkunitconversion4
5844 libkwineffects1a
5845 libmarblewidget4
5846 libntrack-qt4-1
5847 libntrack0
5848 libplasma-geolocation-interface4
5849 libplasmaclock4a
5850 libplasmagenericshell4
5851 libprocesscore4a
5852 libprocessui4a
5853 libqalculate5
5854 libqedje0a
5855 libqtruby4shared2
5856 libqzion0a
5857 libruby1.8
5858 libscim8c2a
5859 libsmokekdecore4-3
5860 libsmokekdeui4-3
5861 libsmokekfile3
5862 libsmokekhtml3
5863 libsmokekio3
5864 libsmokeknewstuff2-3
5865 libsmokeknewstuff3-3
5866 libsmokekparts3
5867 libsmokektexteditor3
5868 libsmokekutils3
5869 libsmokenepomuk3
5870 libsmokephonon3
5871 libsmokeplasma3
5872 libsmokeqtcore4-3
5873 libsmokeqtdbus4-3
5874 libsmokeqtgui4-3
5875 libsmokeqtnetwork4-3
5876 libsmokeqtopengl4-3
5877 libsmokeqtscript4-3
5878 libsmokeqtsql4-3
5879 libsmokeqtsvg4-3
5880 libsmokeqttest4-3
5881 libsmokeqtuitools4-3
5882 libsmokeqtwebkit4-3
5883 libsmokeqtxml4-3
5884 libsmokesolid3
5885 libsmokesoprano3
5886 libtaskmanager4a
5887 libtidy-0.99-0
5888 libweather-ion4a
5889 libxklavier16
5890 libxxf86misc1
5891 okteta
5892 oxygencursors
5893 plasma-dataengines-addons
5894 plasma-scriptengine-superkaramba
5895 plasma-widget-lancelot
5896 plasma-widgets-addons
5897 plasma-widgets-workspace
5898 polkit-kde-1
5899 ruby1.8
5900 systemsettings
5901 update-notifier-common
5902 &lt;/p&gt;&lt;/blockquote&gt;
5903
5904 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5905 aptitude a bit more similar, but there are still quite a lott of
5906 differences. I have no idea what packages should be installed after
5907 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5908 </description>
5909 </item>
5910
5911 <item>
5912 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5913 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5914 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5915 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5916 <description>&lt;p&gt;Most of the computers in use by the
5917 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5918 are virtual machines. And they have been Xen machines running on a
5919 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5920 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5921 bit harder that it could have been, because we set up the Xen virtual
5922 machines to get the virtual partitions from LVM, which as far as I
5923 know is not supported by KVM. So to migrate, we had to convert
5924 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5925
5926 &lt;p&gt;I found
5927 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5928 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5929 migration. It uses qemu-img from the qemu package to make the disk
5930 image, parted to partition it, losetup and kpartx to present the disk
5931 image partions as devices, and dd to copy the data. I NFS mounted the
5932 new servers storage area on the old server to do the migration.&lt;/p&gt;
5933
5934 &lt;pre&gt;
5935 #!/bin/sh
5936
5937 # Based on
5938 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5939
5940 set -e
5941 set -x
5942
5943 if [ -z &quot;$1&quot; ] ; then
5944 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5945 exit 1
5946 else
5947 host=&quot;$1&quot;
5948 fi
5949
5950 if [ ! -e /dev/vg_data/$host-disk ] ; then
5951 echo &quot;error: unable to find LVM volume for $host&quot;
5952 exit 1
5953 fi
5954
5955 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5956 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5957 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5958 totalsize=$(( ( $disksize + $swapsize ) ))
5959
5960 img=$host.img
5961 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5962 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5963
5964 parted $img mklabel msdos
5965 parted $img mkpart primary linux-swap 0 $disksize
5966 parted $img mkpart primary ext2 $disksize $totalsize
5967 parted $img set 1 boot on
5968
5969 modprobe dm-mod
5970 losetup /dev/loop0 $img
5971 kpartx -a /dev/loop0
5972
5973 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5974 fsck.ext3 -f /dev/mapper/loop0p1 || true
5975 mkswap /dev/mapper/loop0p2
5976
5977 kpartx -d /dev/loop0
5978 losetup -d /dev/loop0
5979 &lt;/pre&gt;
5980
5981 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5982 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5983
5984 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5985 the new disk image attached, installed grub-pc and linux-image-686 and
5986 set up grub to boot from the disk image. After this, the KVM machines
5987 seem to work just fine.&lt;/p&gt;
5988 </description>
5989 </item>
5990
5991 <item>
5992 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5993 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5995 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5996 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5997 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5998 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5999 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6000
6001 &lt;p&gt;I still do not know what a correct migration should look like, so I
6002 report any differences between apt and aptitude and hope someone else
6003 can see if anything should be changed.&lt;/p&gt;
6004
6005 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6006
6007 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6008
6009 &lt;blockquote&gt;&lt;p&gt;
6010 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6011 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6012 dmz-cursor-theme empathy empathy-common finger
6013 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6014 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6015 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6016 gnome-cards-data gnome-codec-install gnome-core
6017 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6018 gnome-search-tool gnome-session-canberra gnome-spell
6019 gnome-system-log gnome-themes-extras gnome-themes-more
6020 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6021 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6022 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6023 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6024 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6025 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6026 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6027 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6028 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6029 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6030 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6031 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6032 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6033 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6034 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6035 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6036 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6037 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6038 libmono-security2.0-cil libmono-sharpzip2.84-cil
6039 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6040 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6041 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6042 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6043 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6044 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6045 libxalan2-java libxerces2-java media-player-info mesa-utils
6046 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6047 nautilus-sendto-empathy openoffice.org-writer2latex
6048 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6049 python-aptdaemon python-aptdaemon-gtk python-axiom
6050 python-beautifulsoup python-bugbuddy python-clientform
6051 python-coherence python-configobj python-crypto python-cupshelpers
6052 python-cupsutils python-eggtrayicon python-elementtree
6053 python-epsilon python-evolution python-feedparser python-gdata
6054 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6055 python-gtksourceview2 python-httplib2 python-louie python-mako
6056 python-markupsafe python-mechanize python-nevow python-notify
6057 python-opengl python-openssl python-pam python-pkg-resources
6058 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6059 python-tagpy python-twisted-bin python-twisted-conch
6060 python-twisted-core python-twisted-web python-utidylib python-webkit
6061 python-xdg python-zope.interface remmina remmina-plugin-data
6062 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6063 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6064 software-center svgalibg1 system-config-printer-udev
6065 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6066 totem totem-coherence totem-mozilla totem-plugins
6067 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6068 zip
6069 &lt;/p&gt;&lt;/blockquote&gt;
6070
6071 Installed using apt-get, removed with aptitude
6072
6073 &lt;blockquote&gt;&lt;p&gt;
6074 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6075 epiphany-extensions epiphany-gecko evolution-exchange
6076 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6077 gedit-common gnome-app-install gnome-games gnome-games-data
6078 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6079 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6080 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6081 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6082 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6083 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6084 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6085 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6086 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6087 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6088 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6089 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6090 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6091 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6092 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6093 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6094 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6095 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6096 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6097 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6098 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6099 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6100 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6101 sound-juicer swfdec-gnome system-config-printer totem-common
6102 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6103 &lt;/p&gt;&lt;/blockquote&gt;
6104
6105 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6106
6107 &lt;blockquote&gt;&lt;p&gt;
6108 gstreamer0.10-gnomevfs
6109 &lt;/p&gt;&lt;/blockquote&gt;
6110
6111 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6112
6113 &lt;blockquote&gt;&lt;p&gt;
6114 [nothing]
6115 &lt;/p&gt;&lt;/blockquote&gt;
6116
6117 &lt;p&gt;This is for KDE:&lt;/p&gt;
6118
6119 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6120
6121 &lt;blockquote&gt;&lt;p&gt;
6122 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6123 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6124 ghostscript-x git gnome-audio gnugo granatier gs-common
6125 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6126 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6127 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6128 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6129 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6130 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6131 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6132 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6133 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6134 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6135 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6136 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6137 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6138 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6139 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6140 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6141 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6142 libkrossui4 libmailtools-perl libmime-tools-perl
6143 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6144 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6145 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6146 lirc luatex marble networkstatus noatun-plugins
6147 openoffice.org-writer2latex palapeli palapeli-data parley
6148 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6149 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6150 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6151 ttf-sazanami-gothic
6152 &lt;/p&gt;&lt;/blockquote&gt;
6153
6154 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6155
6156 &lt;blockquote&gt;&lt;p&gt;
6157 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6158 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6159 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6160 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6161 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6162 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6163 kitchensync kiten kjumpingcube klatin klettres klickety klines
6164 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6165 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6166 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6167 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6168 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6169 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6170 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6171 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6172 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6173 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6174 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6175 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6176 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6177 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6178 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6179 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6180 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6181 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6182 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6183 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6184 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6185 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6186 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6187 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6188 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6189 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6190 &lt;/p&gt;&lt;/blockquote&gt;
6191
6192 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6193
6194 &lt;blockquote&gt;&lt;p&gt;
6195 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6196 kdeartwork kdebase kdebase-apps kdebase-workspace
6197 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6198 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6199 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6200 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6201 xscreensaver-screensaver-bsod
6202 &lt;/p&gt;&lt;/blockquote&gt;
6203
6204 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6205
6206 &lt;blockquote&gt;&lt;p&gt;
6207 kdebase-bin konq-plugins konqueror
6208 &lt;/p&gt;&lt;/blockquote&gt;
6209 </description>
6210 </item>
6211
6212 <item>
6213 <title>Gnash buildbot slave and Debian kfreebsd</title>
6214 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6215 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6216 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6217 <description>&lt;p&gt;Answering
6218 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6219 call from the Gnash project&lt;/a&gt; for
6220 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6221 current source, I have set up a virtual KVM machine on the Debian
6222 Edu/Skolelinux virtualization host to test the git source on
6223 Debian/Squeeze. I hope this can help the developers in getting new
6224 releases out more often.&lt;/p&gt;
6225
6226 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6227 I have considered setting up a &lt;a
6228 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6229 machine as well. I have also considered using the kfreebsd
6230 architecture in Debian as a file server in NUUG to get access to the 5
6231 TB zfs volume we currently use to store DV video. Because of this, I
6232 finally got around to do a test installation of Debian/Squeeze with
6233 kfreebsd. Installation went fairly smooth, thought I noticed some
6234 visual glitches in the cdebconf dialogs (black cursor left on the
6235 screen at random locations). Have not gotten very far with the
6236 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6237 fatal problem. Have to spend some more time on it to see if it is
6238 useful as a file server for NUUG. Will try to find time to set up a
6239 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6240 </description>
6241 </item>
6242
6243 <item>
6244 <title>Debian in 3D</title>
6245 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6246 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6247 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6248 <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;
6249
6250 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6251 3D linked in from
6252 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6253 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6254 </description>
6255 </item>
6256
6257 <item>
6258 <title>Software updates 2010-10-24</title>
6259 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6261 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6262 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6263
6264 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6265 raise money for the project is going well. The lower limit of 10
6266 signers was reached in 24 hours, and so far 13 people have signed it.
6267 More signers and more funding is most welcome, and I am really curious
6268 how far we can get before the time limit of December 24 is reached.
6269 :)&lt;/p&gt;
6270
6271 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6272 about what appear to be a great code coverage tool capable of
6273 generating code coverage stats without any changes to the source code.
6274 It is called
6275 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6276 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6277 It is missing in Debian, but the git source built just fine in Squeeze
6278 after I installed libelf-dev, libdwarf-dev, pkg-config and
6279 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6280 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6281
6282 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6283 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6284 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6285 alpha test release of the Squeeze based Debian Edu /
6286 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6287 release. Give it a try if you need a complete linux solution for your
6288 school, including central infrastructure server, workstations, thin
6289 client servers and diskless workstations. A nice touch added
6290 yesterday is RDP support on the thin client servers, for windows
6291 clients to get a Linux desktop on request.&lt;/p&gt;
6292 </description>
6293 </item>
6294
6295 <item>
6296 <title>Some notes on Flash in Debian and Debian Edu</title>
6297 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6298 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6299 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6300 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6301 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6302 second most popular used package that is missing in Debian. The sixth
6303 most popular is flashplayer-mozilla. This is a clear indication that
6304 working flash is important for Debian users. Around 10 percent of the
6305 users submitting data to popcon.debian.org have this package
6306 installed.&lt;/p&gt;
6307
6308 &lt;p&gt;In the report written by Lars Risan in August 2008
6309&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
6310 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6311 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6312 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6313 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6314 web sites require Flash to work, and lacking working Flash support in
6315 the web browser and the problems with installing it was perceived as a
6316 good reason to stay with Windows.&lt;/p&gt;
6317
6318 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6319 said to be the retarded cousin that did not really understand
6320 everything you told him but could work fairly well. This was a
6321 comment regarding the problems Linux have with proprietary formats and
6322 non-standard web pages, and is sad because it exposes a fairly common
6323 understanding of whose fault it is if web pages that only work in for
6324 example Internet Explorer 6 fail to work on Firefox, and funny because
6325 it explain very well how annoying it is for users when Linux
6326 distributions do not work with the documents they receive or the web
6327 pages they want to visit.&lt;/p&gt;
6328
6329 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6330 and Debian Edu to have a well working Flash implementation in the
6331 distribution, to get at least popular sites as Youtube and Google
6332 Video to working out of the box. For Squeeze, Debian have the chance
6333 to include the latest version of Gnash that will make this happen, as
6334 the new release 0.8.8 was published a few weeks ago and is resting in
6335 unstable. The new version work with more sites that version 0.8.7.
6336 The Gnash maintainers have asked for a freeze exception, but the
6337 release team have not had time to reply to it yet. I hope they agree
6338 with me that Flash is important for the Debian desktop users, and thus
6339 accept the new package into Squeeze.&lt;/p&gt;
6340 </description>
6341 </item>
6342
6343 <item>
6344 <title>Circular package dependencies harms apt recovery</title>
6345 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6347 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6348 <description>&lt;p&gt;I discovered this while doing
6349 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6350 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6351 in Debian still got circular dependencies, and it is often claimed
6352 that apt and aptitude should be able to handle this just fine, but
6353 some times these dependency loops causes apt to fail.&lt;/p&gt;
6354
6355 &lt;p&gt;An example is from todays
6356 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6357 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6358 causes perl-modules to fail to upgrade. The cause is simple. If a
6359 package fail to unpack, then only part of packages with the circular
6360 dependency might end up being unpacked when unpacking aborts, and the
6361 ones already unpacked will fail to configure in the recovery phase
6362 because its dependencies are unavailable.&lt;/p&gt;
6363
6364 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6365
6366 &lt;blockquote&gt;&lt;pre&gt;
6367 dpkg: dependency problems prevent configuration of perl-modules:
6368 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6369 Version of perl on system is 5.10.0-19lenny2.
6370 dpkg: error processing perl-modules (--configure):
6371 dependency problems - leaving unconfigured
6372 &lt;/pre&gt;&lt;/blockquote&gt;
6373
6374 &lt;p&gt;The perl/perl-modules circular dependency is already
6375 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6376 hopefully be solved as soon as possible, but it is not the only one,
6377 and each one of these loops in the dependency tree can cause similar
6378 failures. Of course, they only occur when there are bugs in other
6379 packages causing the unpacking to fail, but it is rather nasty when
6380 the failure of one package causes the problem to become worse because
6381 of dependency loops.&lt;/p&gt;
6382
6383 &lt;p&gt;Thanks to
6384 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6385 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6386 dependencies
6387 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6388 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6389
6390 &lt;p&gt;Todays testing also exposed a bug in
6391 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6392 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6393 apt-get and aptitude, the latter possibly caused by some circular
6394 dependency. Reported both to BTS to try to get someone to look at
6395 it.&lt;/p&gt;
6396 </description>
6397 </item>
6398
6399 <item>
6400 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6401 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6403 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6404 <description>&lt;p&gt;This is a
6405 &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;
6406 on my
6407 &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
6408 work&lt;/a&gt; on
6409 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6410 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6411
6412 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6413 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6414 and dhcp3-server-ldap in Debian use the LDAP server. The two
6415 implementations are quite different in how they use LDAP.&lt;/p&gt;
6416
6417 To get this information, I started slapd with debugging enabled and
6418 dumped the debug output to a file to get the LDAP searches performed
6419 on a Debian Edu main-server. Here is a summary.
6420
6421 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6422
6423 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6424 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6425 the web.
6426
6427 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6428 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6429 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6430 reverse entries are in two different subtrees in LDAP with a structure
6431 based on the DNS names, as in tjener.intern and
6432 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6433
6434 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6435 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6436 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6437 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6438 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6439 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6440 forward entries, it is looking for attributes named dnsttl, arecord,
6441 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6442 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6443 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6444 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6445 spfrecord and modifytimestamp. For reverse entries it is looking for
6446 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6447 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6448 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6449 ldapsearch commands could look like this:&lt;/p&gt;
6450
6451 &lt;blockquote&gt;&lt;pre&gt;
6452 ldapsearch -h ldap \
6453 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6454 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6455 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6456 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6457 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6458 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6459
6460 ldapsearch -h ldap \
6461 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6462 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6463 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6464 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6465 srvrecord naptrrecord modifytimestamp
6466 &lt;/pre&gt;&lt;/blockquote&gt;
6467
6468 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6469 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6470 example LDAP objects used there. In addition to these objects, the
6471 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6472 also exist.&lt;/p&gt;
6473
6474 &lt;blockquote&gt;&lt;pre&gt;
6475 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6476 objectclass: top
6477 objectclass: dnsdomain
6478 objectclass: domainrelatedobject
6479 dc: tjener
6480 arecord: 10.0.2.2
6481 associateddomain: tjener.intern
6482
6483 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6484 objectclass: top
6485 objectclass: dnsdomain2
6486 objectclass: domainrelatedobject
6487 dc: 2
6488 ptrrecord: tjener.intern
6489 associateddomain: 2.2.0.10.in-addr.arpa
6490 &lt;/pre&gt;&lt;/blockquote&gt;
6491
6492 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6493 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6494 same base as in the tree mode for a object with filter
6495 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6496 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6497 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6498 naptrrecord and modifytimestamp. For reverse entires it also do a
6499 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6500 and the requested attributes are associateddomain, dnsttl and
6501 modifytimestamp. In short, in strict mode the objects with ptrrecord
6502 go away, and the arecord attribute in the forward object is used
6503 instead.&lt;/p&gt;
6504
6505 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6506 like this:&lt;/p&gt;
6507
6508 &lt;blockquote&gt;&lt;pre&gt;
6509 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6510 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6511 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6512 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6513 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6514 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6515
6516 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6517 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6518 &lt;/pre&gt;&lt;/blockquote&gt;
6519
6520 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6521 search for SOA records, which behave similar to the forward and
6522 reverse lookups.&lt;/p&gt;
6523
6524 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6525 specify any objectclass names, and instead look for the attributes it
6526 need to generate a DNS reply. This make it able to work with any
6527 objectclass that provide the needed attributes.&lt;/p&gt;
6528
6529 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6530 dnsdomain2 schemas. The latter is used for reverse entries like
6531 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6532
6533 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6534 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6535 attributes) and domainrelatedobject (for associatedDomain). The use
6536 of structural object classes make it impossible to combine these
6537 classes with the object classes used by DHCP.&lt;/p&gt;
6538
6539 &lt;p&gt;There are other schemas that could be used too, for example the
6540 dnszone structural object class used by Gosa and bind-sdb for the DNS
6541 attributes combined with the domainrelatedobject object class, but in
6542 this case some unused attributes would have to be included as well
6543 (zonename and relativedomainname).&lt;/p&gt;
6544
6545 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6546 mode and not use any of the existing objectclasses (dnsdomain,
6547 dnsdomain2 and dnszone) when one want to combine the DNS information
6548 with DHCP information, and instead create a auxiliary object class
6549 defined something like this (using the attributes defined for
6550 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6551
6552 &lt;blockquote&gt;&lt;pre&gt;
6553 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6554 SUP top
6555 AUXILIARY
6556 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6557 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6558 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6559 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6560 A6Record $ DNAMERecord
6561 ))
6562 &lt;/pre&gt;&lt;/blockquote&gt;
6563
6564 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6565 the domainrelatedobject object class, and allow any entity to include
6566 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6567 developers asking for their view on this schema and if they are
6568 interested in providing such schema with PowerDNS, and I hope my
6569 message will be accepted into their mailing list soon.&lt;/p&gt;
6570
6571 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6572
6573 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6574 the object attributes, and then uses the attributes it want. This
6575 make it harder to figure out exactly what attributes are used, but
6576 thanks to the working example in Debian Edu I can at least get an idea
6577 what is needed without having to read the source code.&lt;/p&gt;
6578
6579 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6580 search filter to use to locate the correct dhcpServer entity is
6581 stored. These are the relevant entries from
6582 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6583
6584 &lt;blockquote&gt;&lt;pre&gt;
6585 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6586 ldap-dhcp-server-cn &quot;dhcp&quot;;
6587 &lt;/pre&gt;&lt;/blockquote&gt;
6588
6589 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6590 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6591 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6592 search result is this entry:&lt;/p&gt;
6593
6594 &lt;blockquote&gt;&lt;pre&gt;
6595 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6596 cn: dhcp
6597 objectClass: top
6598 objectClass: dhcpServer
6599 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6600 &lt;/pre&gt;&lt;/blockquote&gt;
6601
6602 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6603 subtree with DHCP configuration. The DHCP configuration subtree base
6604 is located using a base scope search with base &quot;cn=DHCP
6605 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6606 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6607 The search result is this entry:&lt;/p&gt;
6608
6609 &lt;blockquote&gt;&lt;pre&gt;
6610 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6611 cn: DHCP Config
6612 objectClass: top
6613 objectClass: dhcpService
6614 objectClass: dhcpOptions
6615 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6616 dhcpStatements: ddns-update-style none
6617 dhcpStatements: authoritative
6618 dhcpOption: smtp-server code 69 = array of ip-address
6619 dhcpOption: www-server code 72 = array of ip-address
6620 dhcpOption: wpad-url code 252 = text
6621 &lt;/pre&gt;&lt;/blockquote&gt;
6622
6623 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6624 all the DHCP configuration is loaded, it is ready to receive requests.
6625 The subtree in Debian Edu contain objects with object classes
6626 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6627 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6628 and information about netmasks, dynamic range etc. Leaving out the
6629 details here because it is not relevant for the focus of my
6630 investigation, which is to see if it is possible to merge dns and dhcp
6631 related computer objects.&lt;/p&gt;
6632
6633 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6634 of the client (00:00:00:00:00:00 in this example), using a subtree
6635 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6636 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6637 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6638 like:&lt;/p&gt;
6639
6640 &lt;blockquote&gt;&lt;pre&gt;
6641 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6642 cn: hostname
6643 objectClass: top
6644 objectClass: dhcpHost
6645 dhcpHWAddress: ethernet 00:00:00:00:00:00
6646 dhcpStatements: fixed-address hostname
6647 &lt;/pre&gt;&lt;/blockquote&gt;
6648
6649 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6650 The object classes need to have fixed names, and the configuration
6651 need to be stored in a fairly specific LDAP structure. On the
6652 positive side, the invidiual dhcpHost entires can be anywhere without
6653 the DN pointed to by the dhcpServer entries. The latter should make
6654 it possible to group all host entries in a subtree next to the
6655 configuration entries, and this subtree can also be shared with the
6656 DNS server if the schema proposed above is combined with the dhcpHost
6657 structural object class.
6658
6659 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6660
6661 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6662 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6663 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6664 allowing DNS objects to be stored anywhere under the base cn specified
6665 in the configuration.&lt;/p&gt;
6666
6667 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6668 regarding which LDAP schemas to use and which LDAP structure to use.
6669 I guess one could implement ones own schema, as long as the
6670 objectclasses and attributes have the names used, but this do not
6671 really help when the DHCP subtree need to have a fairly fixed
6672 structure.&lt;/p&gt;
6673
6674 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6675 this might work for Debian Edu:&lt;/p&gt;
6676
6677 &lt;blockquote&gt;&lt;pre&gt;
6678 ou=services
6679 cn=machine-info (dhcpService) - dhcpServiceDN points here
6680 cn=dhcp (dhcpServer)
6681 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6682 cn=10.0.2.0 (dhcpSubnet)
6683 cn=group1 (dhcpGroup/dhcpOptions)
6684 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6685 cn=192.168.0.0 (dhcpSubnet)
6686 cn=group1 (dhcpGroup/dhcpOptions)
6687 ou=machines - PowerDNS base points here
6688 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6689 &lt;/pre&gt;&lt;/blockquote&gt;
6690
6691 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6692 entries to be in the dhcpGroup subtrees, the entries can be stored
6693 there instead of a common machines subtree, and the PowerDNS base
6694 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6695
6696 &lt;p&gt;The combined object under the machines subtree would look something
6697 like this:&lt;/p&gt;
6698
6699 &lt;blockquote&gt;&lt;pre&gt;
6700 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6701 dc: hostname
6702 objectClass: top
6703 objectClass: dhcpHost
6704 objectclass: domainrelatedobject
6705 objectclass: dnsDomainAux
6706 associateddomain: hostname.intern
6707 arecord: 10.11.12.13
6708 dhcpHWAddress: ethernet 00:00:00:00:00:00
6709 dhcpStatements: fixed-address hostname.intern
6710 &lt;/pre&gt;&lt;/blockquote&gt;
6711
6712 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6713 machine, as long as the required attributes are available in a
6714 auxiliary object class.&lt;/p&gt;
6715 </description>
6716 </item>
6717
6718 <item>
6719 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6720 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6721 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6722 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6723 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6724 DHCP services in Debian Edu to use the same LDAP objects for a given
6725 computer, to avoid the possibility of having a inconsistent state for
6726 a computer in LDAP (as in DHCP but no DNS entry or the other way
6727 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6728
6729 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6730 information finally found a solution that seem to work.&lt;/p&gt;
6731
6732 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6733 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6734 we switch powerdns to use its strict LDAP method (ldap-method=strict
6735 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6736 merged into one while making it impossible to transfer the reverse map
6737 to a slave DNS server.&lt;/p&gt;
6738
6739 &lt;p&gt;If we also replace the object class used to get the DNS related
6740 attributes to one allowing these attributes to be combined with the
6741 dhcphost object class, we can merge the DNS and DHCP entries into one.
6742 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6743 proper OIDs, but that is a minor issue), and tested the setup. It
6744 seem to work.&lt;/p&gt;
6745
6746 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6747 for both DNS and DHCP, and even the LTSP configuration I suggested in
6748 an earlier email. The combined LDAP object will look something like
6749 this:&lt;/p&gt;
6750
6751 &lt;blockquote&gt;&lt;pre&gt;
6752 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6753 cn: hostname
6754 objectClass: dhcphost
6755 objectclass: domainrelatedobject
6756 objectclass: dnsdomainaux
6757 associateddomain: hostname.intern
6758 arecord: 10.11.12.13
6759 dhcphwaddress: ethernet 00:00:00:00:00:00
6760 dhcpstatements: fixed-address hostname
6761 ldapconfigsound: Y
6762 &lt;/pre&gt;&lt;/blockquote&gt;
6763
6764 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6765 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6766 before asking DNS to resolve the fixed-adddress. LTSP will use
6767 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6768
6769 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6770 dhcphost in a different location, to allow us to put the objects
6771 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6772 that. If I can&#39;t figure out a way to do that, we can still get rid of
6773 the hosts subtree and move all its content into the DHCP Config tree
6774 (which probably should be renamed to be more related to the new
6775 content. I suspect cn=dnsdhcp,ou=services or something like that
6776 might be a good place to put it.&lt;/p&gt;
6777
6778 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6779 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6780 </description>
6781 </item>
6782
6783 <item>
6784 <title>Idea for storing LTSP configuration in LDAP</title>
6785 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6786 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6787 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6788 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6789 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6790 clients, and that this can be used to fetch configuration from LDAP if
6791 Debian Edu choose to store configuration there.&lt;/p&gt;
6792
6793 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6794 to get configuration from LDAP. The idea is to look up the MAC
6795 address of the client in LDAP, and look for attributes on the form
6796 ltspconfigsetting=value, and use this to export SETTING=value to the
6797 LTSP clients.&lt;/p&gt;
6798
6799 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6800 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6801 allowing us to store all information about a computer in one place.&lt;/p&gt;
6802
6803 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6804 this approach. A real LDAP schema for the ltspClientAux objectclass
6805 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6806
6807 &lt;blockquote&gt;&lt;pre&gt;
6808 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6809 #
6810 # Fetch LTSP client settings from LDAP based on MAC address
6811 #
6812 # Uses ethernet address as stored in the dhcpHost objectclass using
6813 # the dhcpHWAddress attribute or ethernet address stored in the
6814 # ieee802Device objectclass with the macAddress attribute.
6815 #
6816 # This module is written to be schema agnostic, and only depend on the
6817 # existence of attribute names.
6818 #
6819 # The LTSP configuration variables are saved directly using a
6820 # ltspConfig prefix and uppercasing the rest of the attribute name.
6821 # To set the SERVER variable, set the ltspConfigServer attribute.
6822 #
6823 # Some LDAP schema should be created with all the relevant
6824 # configuration settings. Something like this should work:
6825 #
6826 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6827 # SUP top
6828 # AUXILIARY
6829 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6830
6831 LDAPSERVER=$(debian-edu-ldapserver)
6832 if [ &quot;$LDAPSERVER&quot; ] ; then
6833 LDAPBASE=$(debian-edu-ldapserver -b)
6834 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6835 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6836 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6837 grep &#39;^ltspConfig&#39; | while read attr value ; do
6838 # Remove prefix and convert to upper case
6839 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6840 # bass value on to clients
6841 eval &quot;$attr=$value; export $attr&quot;
6842 done
6843 done
6844 fi
6845 &lt;/pre&gt;&lt;/blockquote&gt;
6846
6847 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6848 the while block might end up in a subshell causing the variables set
6849 there to not show up in ltsp-config, but if that is the case I am sure
6850 the code can be restructured to make sure the variables are passed on.
6851 I expect that can be solved with some testing. :)&lt;/p&gt;
6852
6853 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6854 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6855
6856 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6857 configuration in LDAP that was created around year 2000 by
6858 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6859 Xperience, Inc., 2000&lt;/a&gt;. I found its
6860 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6861 personal home page over at redhat.com.&lt;/p&gt;
6862 </description>
6863 </item>
6864
6865 <item>
6866 <title>jXplorer, a very nice LDAP GUI</title>
6867 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6869 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6870 <description>&lt;p&gt;Since
6871 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6872 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6873 LDAP GUI that is even better than luma. The java application
6874 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6875 moving LDAP objects and subtrees using drag-and-drop, and can
6876 authenticate using Kerberos. I have only tested the Kerberos
6877 authentication, but do not have a LDAP setup allowing me to rewrite
6878 LDAP with my test user yet. It is
6879 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6880 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6881 have with it is how it handle errors. If something go wrong, its
6882 non-intuitive behaviour require me to go through some query work list
6883 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6884 </description>
6885 </item>
6886
6887 <item>
6888 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6889 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6890 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6891 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6892 <description>&lt;p&gt;Here is a short update on my &lt;a
6893 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6894 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6895 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6896 not reporting the status for KDE, because the upgrade crashes when
6897 aptitude try because of missing conflicts
6898 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6899 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6900
6901 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6902 complete list of the installed packages. Based on this I see these
6903 differences when I did a test run today. As usual, I do not really
6904 know what the correct set of packages would be, but thought it best to
6905 publish the difference.&lt;/p&gt;
6906
6907 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6908
6909 &lt;blockquote&gt;&lt;p&gt;
6910 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6911 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6912 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6913 libgtksourceview-common libpt-1.10.10-plugins-alsa
6914 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6915 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6916 python-4suite-xml python-eggtrayicon python-gtkhtml2
6917 python-gtkmozembed svgalibg1 xserver-xephyr zip
6918 &lt;/p&gt;&lt;/blockquote&gt;
6919
6920 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6921
6922 &lt;blockquote&gt;&lt;p&gt;
6923 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6924 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6925 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6926 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6927 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6928 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6929 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6930 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6931 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6932 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6933 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6934 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6935 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6936 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6937 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6938 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6939 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6940 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6941 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6942 mysql-common swfdec-gnome totem-gstreamer wodim
6943 &lt;/p&gt;&lt;/blockquote&gt;
6944
6945 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6946
6947 &lt;blockquote&gt;&lt;p&gt;
6948 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6949 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6950 xserver-xorg-input-all xserver-xorg-input-evdev
6951 xserver-xorg-input-kbd xserver-xorg-input-mouse
6952 xserver-xorg-input-synaptics xserver-xorg-video-all
6953 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6954 xserver-xorg-video-chips xserver-xorg-video-cirrus
6955 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6956 xserver-xorg-video-glint xserver-xorg-video-i128
6957 xserver-xorg-video-i740 xserver-xorg-video-mach64
6958 xserver-xorg-video-mga xserver-xorg-video-neomagic
6959 xserver-xorg-video-nouveau xserver-xorg-video-nv
6960 xserver-xorg-video-r128 xserver-xorg-video-radeon
6961 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6962 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6963 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6964 xserver-xorg-video-sis xserver-xorg-video-sisusb
6965 xserver-xorg-video-tdfx xserver-xorg-video-tga
6966 xserver-xorg-video-trident xserver-xorg-video-tseng
6967 xserver-xorg-video-vesa xserver-xorg-video-vmware
6968 xserver-xorg-video-voodoo
6969 &lt;/p&gt;&lt;/blockquote&gt;
6970
6971 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6972
6973 &lt;blockquote&gt;&lt;p&gt;
6974 deskbar-applet xserver-xorg xserver-xorg-core
6975 xserver-xorg-input-wacom xserver-xorg-video-intel
6976 xserver-xorg-video-openchrome
6977 &lt;/p&gt;&lt;/blockquote&gt;
6978
6979 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6980 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6981 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6982 No idea when it hits Squeeze, but when it does I hope it will reduce
6983 the difference somewhat.
6984 </description>
6985 </item>
6986
6987 <item>
6988 <title>LUMA, a very nice LDAP GUI</title>
6989 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6990 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6991 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6992 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6993 directory in Debian Edu, and in the process I started to miss a GUI
6994 tool to browse the LDAP tree. The only one I was able to find in
6995 Debian/Squeeze and Lenny is
6996 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6997 be a great tool to get a overview of the current LDAP directory
6998 populated by default in Skolelinux. Thanks to it, I have been able to
6999 find empty and obsolete subtrees, misplaced objects and duplicate
7000 objects. It will be installed by default in Debian/Squeeze. If you
7001 are working with LDAP, give it a go. :)&lt;/p&gt;
7002
7003 &lt;p&gt;I did notice one problem with it I have not had time to report to
7004 the BTS yet. There is no .desktop file in the package, so the tool do
7005 not show up in the Gnome and KDE menus, but only deep down in in the
7006 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7007 released.&lt;/p&gt;
7008
7009 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7010 like to move objects and remove subtrees directly in the GUI, but have
7011 not found a way to do that with LUMA yet. So in the mean time, I use
7012 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7013
7014 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7015 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7016
7017 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7018 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7019 useful GUI alternative. It seem like a good tool, but is unmaintained
7020 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7021 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7022 </description>
7023 </item>
7024
7025 <item>
7026 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7027 <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>
7028 <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>
7029 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7030 <description>&lt;p&gt;A while back, I
7031 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7032 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7033 for storing DNS and DHCP information in LDAP to combine the two sets
7034 of information into one LDAP object representing a computer.&lt;/p&gt;
7035
7036 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7037 the dhcpHost object class auxiliary, to allow it to be combined with
7038 the dNSDomain object class, and thus forming one object for one
7039 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7040
7041 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7042 without also changing the assigned number for the object class, and I
7043 do not know enough about LDAP schema design to do that properly for
7044 Debian Edu.&lt;/p&gt;
7045
7046 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7047 the
7048 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7049 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7050 available today from IETF.&lt;/p&gt;
7051
7052 &lt;pre&gt;
7053 --- dhcp.schema (revision 65192)
7054 +++ dhcp.schema (working copy)
7055 @@ -376,7 +376,7 @@
7056 objectclass ( 2.16.840.1.113719.1.203.6.6
7057 NAME &#39;dhcpHost&#39;
7058 DESC &#39;This represents information about a particular client&#39;
7059 - SUP top
7060 + SUP top AUXILIARY
7061 MUST cn
7062 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7063 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7064 &lt;/pre&gt;
7065
7066 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7067 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7068 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7069
7070 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7071 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7072 </description>
7073 </item>
7074
7075 <item>
7076 <title>Calling tasksel like the installer, while still getting useful output</title>
7077 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7078 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7079 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7080 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7081 installs packages during the normal debian-installer run. Until now,
7082 I have ended up letting tasksel do the work, with the annoying problem
7083 of not getting any feedback at all when something fails (like a
7084 conffile question from dpkg or a download that fails), using code like
7085 this:
7086
7087 &lt;blockquote&gt;&lt;pre&gt;
7088 export DEBIAN_FRONTEND=noninteractive
7089 tasksel --new-install
7090 &lt;/pre&gt;&lt;/blockquote&gt;
7091
7092 This would invoke tasksel, let its automatic task selection pick the
7093 tasks to install, and continue to install the requested tasks without
7094 any output what so ever.
7095
7096 Recently I revisited this problem while working on the automatic
7097 package upgrade testing, because tasksel would some times hang without
7098 any useful feedback, and I want to see what is going on when it
7099 happen. Then it occured to me, I can parse the output from tasksel
7100 when asked to run in test mode, and use that aptitude command line
7101 printed by tasksel then to simulate the tasksel run. I ended up using
7102 code like this:
7103
7104 &lt;blockquote&gt;&lt;pre&gt;
7105 export DEBIAN_FRONTEND=noninteractive
7106 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7107 $cmd
7108 &lt;/pre&gt;&lt;/blockquote&gt;
7109
7110 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7111 --without-recommends -o APT::Install-Recommends=no -y install
7112 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7113 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7114 laptop task and all packages with priority standard , required and
7115 important, just like tasksel would have done it during
7116 installation.&lt;/p&gt;
7117
7118 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7119 install packages without using debconf-apt-progress, for use cases
7120 like this.&lt;/p&gt;
7121 </description>
7122 </item>
7123
7124 <item>
7125 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7126 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7127 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7128 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7129 <description>&lt;p&gt;My
7130 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7131 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7132 finally made the upgrade logs available from
7133 &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;.
7134 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7135 apt and aptitude, and found their differences interesting. This time
7136 I will only focus on their removal plans.&lt;/p&gt;
7137
7138 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7139 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7140 surprising part is that it want to remove xorg and all
7141 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7142 sure why. When asking aptitude to do the same, it want to remove 129
7143 packages, but most of them are library packages I suspect are no
7144 longer needed. Both of them want to remove bluetooth packages, which
7145 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7146
7147 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7148 which seem like a bad idea and xorg the same way as with Gnome. Asking
7149 aptitude for the same, it wants to remove 192 packages, none which are
7150 too surprising.&lt;/p&gt;
7151
7152 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7153 and avoided, and perhaps others as well. Here are the complete list
7154 of planned removals. The complete logs is available from the URL
7155 above. Note if you want to repeat these tests, that the upgrade test
7156 for kde+apt-get hung in the tasksel setup because of dpkg asking
7157 conffile questions. No idea why. I worked around it by using
7158 &#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
7159 continue.&lt;/p&gt;
7160
7161 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7162 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7163 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7164 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7165 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7166 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7167 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7168 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7169 xserver-xorg-input-kbd xserver-xorg-input-mouse
7170 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7171 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7172 xserver-xorg-video-ati xserver-xorg-video-chips
7173 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7174 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7175 xserver-xorg-video-glint xserver-xorg-video-i128
7176 xserver-xorg-video-i740 xserver-xorg-video-imstt
7177 xserver-xorg-video-intel xserver-xorg-video-mach64
7178 xserver-xorg-video-mga xserver-xorg-video-neomagic
7179 xserver-xorg-video-nsc xserver-xorg-video-nv
7180 xserver-xorg-video-openchrome xserver-xorg-video-r128
7181 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7182 xserver-xorg-video-rendition xserver-xorg-video-s3
7183 xserver-xorg-video-s3virge xserver-xorg-video-savage
7184 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7185 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7186 xserver-xorg-video-tga xserver-xorg-video-trident
7187 xserver-xorg-video-tseng xserver-xorg-video-v4l
7188 xserver-xorg-video-vesa xserver-xorg-video-vga
7189 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7190 xulrunner-1.9-gnome-support&lt;/p&gt;
7191
7192 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7193
7194 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7195 djvulibre-desktop finger gnome-app-install gnome-mount
7196 gnome-network-admin gnome-spell gnome-vfs-obexftp
7197 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7198 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7199 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7200 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7201 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7202 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7203 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7204 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7205 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7206 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7207 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7208 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7209 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7210 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7211 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7212 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7213 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7214 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7215 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7216 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7217 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7218 openoffice.org-writer2latex openssl-blacklist p7zip
7219 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7220 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7221 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7222 swfdec-mozilla totem-gstreamer update-manager wodim
7223 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7224 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7225 zip&lt;/p&gt;
7226
7227 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7228
7229 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7230 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7231 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7232 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7233 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7234 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7235 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7236 xserver-xorg-input-kbd xserver-xorg-input-mouse
7237 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7238 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7239 xserver-xorg-video-ati xserver-xorg-video-chips
7240 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7241 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7242 xserver-xorg-video-glint xserver-xorg-video-i128
7243 xserver-xorg-video-i740 xserver-xorg-video-imstt
7244 xserver-xorg-video-intel xserver-xorg-video-mach64
7245 xserver-xorg-video-mga xserver-xorg-video-neomagic
7246 xserver-xorg-video-nsc xserver-xorg-video-nv
7247 xserver-xorg-video-openchrome xserver-xorg-video-r128
7248 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7249 xserver-xorg-video-rendition xserver-xorg-video-s3
7250 xserver-xorg-video-s3virge xserver-xorg-video-savage
7251 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7252 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7253 xserver-xorg-video-tga xserver-xorg-video-trident
7254 xserver-xorg-video-tseng xserver-xorg-video-v4l
7255 xserver-xorg-video-vesa xserver-xorg-video-vga
7256 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7257
7258 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7259 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7260 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7261 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7262 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7263 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7264 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7265 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7266 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7267 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7268 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7269 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7270 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7271 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7272 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7273 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7274 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7275 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7276 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7277 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7278 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7279 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7280 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7281 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7282 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7283 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7284 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7285 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7286 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7287 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7288 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7289 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7290 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7291 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7292 texlive-common texlive-doc-base texlive-fonts-recommended
7293 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7294 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7295 xulrunner-1.9&lt;/p&gt;
7296
7297 </description>
7298 </item>
7299
7300 <item>
7301 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7302 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7304 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7305 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7306 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7307 have been discovered and reported in the process
7308 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7309 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7310 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7311 kdebase-workspace-data), and to get a more regular testing going on, I
7312 am working on a script to automate the test.&lt;/p&gt;
7313
7314 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7315 Gnome or KDE desktop installation inside the chroot before upgrading
7316 it. To ensure no services are started in the chroot, a policy-rc.d
7317 script is inserted. To make sure tasksel believe it is to install a
7318 desktop on a laptop, the tasksel tests are replaced in the chroot
7319 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7320
7321 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7322 currently always fail because udev refuses to upgrade with the kernel
7323 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7324 is created. The bug report
7325 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7326 this problem do not trigger in a chroot, but I touch the file anyway
7327 to make sure the upgrade go well. Testing on virtual and real
7328 hardware have failed me because of udev so far, and creating this file
7329 do the trick in such settings anyway. This is a
7330 &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
7331 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7332 maintainer because he lack the resources to rewrite udev to keep
7333 working with old kernels or something like that. I really wish the
7334 udev upstream would keep udev backwards compatible, to avoid such
7335 upgrade problem, but given that they fail to do so, I guess
7336 documenting the way out of this mess is the best option we got for
7337 Debian Squeeze.&lt;/p&gt;
7338
7339 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7340 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7341 trick:&lt;/p&gt;
7342
7343 &lt;blockquote&gt;&lt;pre&gt;
7344 #!/bin/sh
7345 set -ex
7346
7347 if [ &quot;$1&quot; ] ; then
7348 desktop=$1
7349 else
7350 desktop=gnome
7351 fi
7352
7353 from=lenny
7354 to=squeeze
7355
7356 exec &amp;lt; /dev/null
7357 unset LANG
7358 mirror=http://ftp.skolelinux.org/debian
7359 tmpdir=chroot-$from-upgrade-$to-$desktop
7360 fuser -mv .
7361 debootstrap $from $tmpdir $mirror
7362 chroot $tmpdir aptitude update
7363 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7364 #!/bin/sh
7365 exit 101
7366 EOF
7367 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7368 exit_cleanup() {
7369 umount $tmpdir/proc
7370 }
7371 mount -t proc proc $tmpdir/proc
7372 # Make sure proc is unmounted also on failure
7373 trap exit_cleanup EXIT INT
7374
7375 chroot $tmpdir aptitude -y install debconf-utils
7376
7377 # Make sure tasksel autoselection trigger. It need the test scripts
7378 # to return the correct answers.
7379 echo tasksel tasksel/desktop multiselect $desktop | \
7380 chroot $tmpdir debconf-set-selections
7381
7382 # Include the desktop and laptop task
7383 for test in desktop laptop ; do
7384 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7385 #!/bin/sh
7386 exit 2
7387 EOF
7388 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7389 done
7390
7391 DEBIAN_FRONTEND=noninteractive
7392 DEBIAN_PRIORITY=critical
7393 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7394 chroot $tmpdir tasksel --new-install
7395
7396 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7397 chroot $tmpdir aptitude update
7398 touch $tmpdir/etc/udev/kernel-upgrade
7399 chroot $tmpdir aptitude -y dist-upgrade
7400 fuser -mv
7401 &lt;/pre&gt;&lt;/blockquote&gt;
7402
7403 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7404 with aptitude, but I have not had time to look at how they behave
7405 differently so far. I hope to get a cron job running to do the test
7406 regularly and post the result on the web. The Gnome upgrade currently
7407 work, while the KDE upgrade fail because of the bug in
7408 kdebase-workspace-data&lt;/p&gt;
7409
7410 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7411 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7412 post, so I will refrain from trying. I can report that for Gnome,
7413 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7414 remove and 1 not upgraded and 1024MB need to be downloaded while for
7415 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7416 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7417
7418 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7419 is able to migrate to dependency based boot sequencing and parallel
7420 booting without a hitch. Was unsure if there were still bugs with
7421 packages failing to clean up their obsolete init.d script during
7422 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7423 packages.&lt;/p&gt;
7424 </description>
7425 </item>
7426
7427 <item>
7428 <title>Upstart or sysvinit - as init.d scripts see it</title>
7429 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7430 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7431 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7432 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7433 scripts to migrate (some of) their operations to upstart job while
7434 keeping the init.d for hurd and kfreebsd. The packages with such
7435 needs will need a way to get their init.d scripts to behave
7436 differently when used with sysvinit and with upstart. Because of
7437 this, I had a look at the environment variables set when a init.d
7438 script is running under upstart, and when it is not.&lt;/p&gt;
7439
7440 &lt;p&gt;With upstart, I notice these environment variables are set when a
7441 script is started from rcS.d/ (ignoring some irrelevant ones like
7442 COLUMNS):&lt;/p&gt;
7443
7444 &lt;blockquote&gt;&lt;pre&gt;
7445 DEFAULT_RUNLEVEL=2
7446 previous=N
7447 PREVLEVEL=
7448 RUNLEVEL=
7449 runlevel=S
7450 UPSTART_EVENTS=startup
7451 UPSTART_INSTANCE=
7452 UPSTART_JOB=rc-sysinit
7453 &lt;/pre&gt;&lt;/blockquote&gt;
7454
7455 &lt;p&gt;With sysvinit, these environment variables are set for the same
7456 script.&lt;/p&gt;
7457
7458 &lt;blockquote&gt;&lt;pre&gt;
7459 INIT_VERSION=sysvinit-2.88
7460 previous=N
7461 PREVLEVEL=N
7462 RUNLEVEL=S
7463 runlevel=S
7464 &lt;/pre&gt;&lt;/blockquote&gt;
7465
7466 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7467 sysvinit are not set by upstart. Not sure if it is intentional or not
7468 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7469
7470 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7471 looking for the UPSTART_JOB environment variable seem to be a good
7472 choice.&lt;/p&gt;
7473 </description>
7474 </item>
7475
7476 <item>
7477 <title>A manual for standards wars...</title>
7478 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7480 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7481 <description>&lt;p&gt;Via the
7482 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7483 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7484 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7485 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7486 following the standards wars of today.&lt;/p&gt;
7487 </description>
7488 </item>
7489
7490 <item>
7491 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7492 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7493 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7494 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7495 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7496 to get a list of the machine types in use thanks to the DMI
7497 information extracted from each machine. The script to do so is
7498 included in the sitesummary package, and here is example output from
7499 the Skolelinux build servers:&lt;/p&gt;
7500
7501 &lt;blockquote&gt;&lt;pre&gt;
7502 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7503 vendor count
7504 Dell Computer Corporation 1
7505 PowerEdge 1750 1
7506 IBM 1
7507 eserver xSeries 345 -[8670M1X]- 1
7508 Intel 2
7509 [no-dmi-info] 3
7510 maintainer:~#
7511 &lt;/pre&gt;&lt;/blockquote&gt;
7512
7513 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7514 provided in each machine. Here there are Intel machines without model
7515 information listed with Intel as vendor and no model, and virtual Xen
7516 machines listed as [no-dmi-info]. One can add -l as a command line
7517 option to list the individual machines.&lt;/p&gt;
7518
7519 &lt;p&gt;A larger list is
7520 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7521 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7522 provide the basic sitesummary report publicly. In their report there
7523 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7524 their machines, and as sitesummary is available in both distributions,
7525 it is trivial to get all of them to report to the same central
7526 collector.&lt;/p&gt;
7527 </description>
7528 </item>
7529
7530 <item>
7531 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7532 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7533 <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>
7534 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7535 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7536 start at boot when an NVidia video card is used is handled. The
7537 problem seem to be that the nvidia X.org driver uses a long time to
7538 initialize, and this duration is longer than kdm is configured to
7539 wait.&lt;/p&gt;
7540
7541 &lt;p&gt;I came across two bugs related to this issue,
7542 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7543 against initscripts and passed on to nvidia-glx when it became obvious
7544 that the nvidia drivers were involved, and
7545 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7546 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7547
7548 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7549 problem nvidia video card owners experience and make sure the Debian
7550 distribution work out of the box for these users. The nvidia driver
7551 maintainers expect kdm to be set up to wait longer, while kdm expect
7552 the nvidia driver maintainers to fix the driver to start faster, and
7553 while they wait for each other I guess the users end up switching to a
7554 distribution that work for them. I have no idea what the solution is,
7555 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7556
7557 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7558 </description>
7559 </item>
7560
7561 <item>
7562 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7563 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7565 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7566 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7567 The feature seem to hold up pretty well, but three fairly serious
7568 issues are known and should be solved:
7569
7570 &lt;p&gt;&lt;ul&gt;
7571
7572 &lt;li&gt;The wicd package seen to
7573 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7574 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7575 parallel booting is enabled. No idea why, but the wicd maintainer
7576 seem to be on the case.&lt;/li&gt;
7577
7578 &lt;li&gt;The nvidia X driver seem to
7579 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7580 triggered more easily when parallel booting is in effect. The
7581 maintainer is on the case.&lt;/li&gt;
7582
7583 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7584 sequencing (the shutdown is broken) when old file-rc users
7585 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7586 sysv-rc. One way to solve it would be for file-rc to create
7587 /etc/init.d/.legacy-bootordering, and another is to try to make
7588 sysv-rc more robust. Will investigate some more and probably upload a
7589 workaround in sysv-rc to help those trying to move from file-rc to
7590 sysv-rc get a working shutdown.&lt;/li&gt;
7591
7592 &lt;/ul&gt;&lt;/p&gt;
7593
7594 &lt;p&gt;All in all not many surprising issues, and all of them seem
7595 solvable before Squeeze is released. In addition to these there are
7596 some packages with bugs in their dependencies and run level settings,
7597 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7598
7599 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7600 the BTS, please usertag the report to get it to show up at
7601 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7602 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7603
7604 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7605 </description>
7606 </item>
7607
7608 <item>
7609 <title>More flexible firmware handling in debian-installer</title>
7610 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7611 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7612 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7613 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7614 found time today to return to the project. Having to spend less time
7615 working dependency based boot in debian, as it is almost complete now,
7616 definitely helped freeing some time.&lt;/p&gt;
7617
7618 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7619 include some firmware packages on the Debian Edu CDs, those needed to
7620 get disk and network controllers working. Without having these
7621 firmware packages available during installation, it is impossible to
7622 install Debian Edu on the given machine, and because our target group
7623 are non-technical people, asking them to provide firmware packages on
7624 an external medium is a support pain. Initially, I expected it to be
7625 enough to include the firmware packages on the CD to get
7626 debian-installer to find and use them. This proved to be wrong.
7627 Next, I hoped it was enough to symlink the relevant firmware packages
7628 to some useful location on the CD (tried /cdrom/ and
7629 /cdrom/firmware/). This also proved to not work, and at this point I
7630 found time to look at the debian-installer code to figure out what was
7631 going to work.&lt;/p&gt;
7632
7633 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7634 look revealed that it would only look for firmware packages outside
7635 the installation media, so the CD was never checked for firmware
7636 packages. It would only check USB sticks, floppies and other
7637 &quot;external&quot; media devices. Today I changed it to also look in the
7638 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7639 solve the problem I ran into with Debian edu. I also changed it to
7640 look in /firmware/, to make sure the installer also find firmware
7641 provided in the initrd when booting the installer via PXE, to allow us
7642 to provide the same feature in the PXE setup included in Debian
7643 Edu.&lt;/p&gt;
7644
7645 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7646 activated without asking if the license is accepted, I extended
7647 hw-detect to look for preinst scripts in the firmware packages, and
7648 run these before activating the firmware during installation. The
7649 license question is asked using debconf in the preinst, so this should
7650 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7651
7652 &lt;p&gt;If you want to discuss the details of these features, please
7653 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7654 </description>
7655 </item>
7656
7657 <item>
7658 <title>Parallellized boot is now the default in Debian/unstable</title>
7659 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7660 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7661 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7662 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7663 Debian/unstable for machines using dependency based boot sequencing.
7664 Apparently the testing of concurrent booting has been wider than
7665 expected, if I am to believe the
7666 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7667 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7668 with the feature this weekend, to give us some time to detect any
7669 remaining problems before Squeeze is frozen. If serious problems are
7670 detected, it is simple to change the default back to sequential boot.
7671 The upload of the new sysvinit package also activate a new upstream
7672 version.&lt;/p&gt;
7673
7674 More information about
7675 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7676 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7677 currently possible to disable parallel booting when one run into
7678 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7679
7680 &lt;blockquote&gt;&lt;pre&gt;
7681 CONCURRENCY=none
7682 &lt;/pre&gt;&lt;/blockquote&gt;
7683
7684 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7685 the BTS, please usertag the report to get it to show up at
7686 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7687 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7688 </description>
7689 </item>
7690
7691 <item>
7692 <title>Sitesummary tip: Listing MAC address of all clients</title>
7693 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7695 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7696 <description>&lt;p&gt;In the recent Debian Edu versions, the
7697 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7698 system&lt;/a&gt; is used to keep track of the machines in the school
7699 network. Each machine will automatically report its status to the
7700 central server after boot and once per night. The network setup is
7701 also reported, and using this information it is possible to get the
7702 MAC address of all network interfaces in the machines. This is useful
7703 to update the DHCP configuration.&lt;/p&gt;
7704
7705 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7706 ist all MAC addresses of all machines reporting to sitesummary. Run
7707 this on the collector host:&lt;/p&gt;
7708
7709 &lt;blockquote&gt;&lt;pre&gt;
7710 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7711 &lt;/pre&gt;&lt;/blockquote&gt;
7712
7713 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7714 line per machine and with space between the MAC addresses.&lt;/p&gt;
7715
7716 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7717 addresses for hosts, it would be possible to extend this to fetch
7718 machine information from sitesummary and update the DHCP and DNS
7719 tables in LDAP using this information. Such tool is unfortunately not
7720 written yet.&lt;/p&gt;
7721 </description>
7722 </item>
7723
7724 <item>
7725 <title>systemd, an interesting alternative to upstart</title>
7726 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7727 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7728 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7729 <description>&lt;p&gt;The last few days a new boot system called
7730 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7731 has been
7732 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7733
7734 to the free software world. I have not yet had time to play around
7735 with it, but it seem to be a very interesting alternative to
7736 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7737 a good alternative for Debian when we are able to switch to an event
7738 based boot system. Tollef is
7739 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7740 systemd into Debian, and I look forward to seeing how well it work. I
7741 like the fact that systemd handles init.d scripts with dependency
7742 information natively, allowing them to run in parallel where upstart
7743 at the moment do not.&lt;/p&gt;
7744
7745 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7746 platform support. It only work on recent Linux kernels, and also need
7747 some new kernel features enabled to function properly. This means
7748 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7749 system. Not sure how that will be handled if systemd proves to be the
7750 way forward.&lt;/p&gt;
7751
7752 &lt;p&gt;In the mean time, based on the
7753 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7754 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7755 decided to enable full parallel booting as the default in Debian as
7756 soon as possible (probably this weekend or early next week), to see if
7757 there are any remaining serious bugs in the init.d dependencies. A
7758 new version of the sysvinit package implementing this change is
7759 already in experimental. If all go well, Squeeze will be released
7760 with parallel booting enabled by default.&lt;/p&gt;
7761 </description>
7762 </item>
7763
7764 <item>
7765 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7766 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7767 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7768 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7769 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7770 complete, so complete that it is actually possible to run all the
7771 init.d scripts in parallell based on these dependencies. If you want
7772 to test your Squeeze system, make sure
7773 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7774 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7775 /etc/default/rcS:&lt;/p&gt;
7776
7777 &lt;blockquote&gt;&lt;pre&gt;
7778 CONCURRENCY=makefile
7779 &lt;/pre&gt;&lt;/blockquote&gt;
7780
7781 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7782 scripts in parallel using the dependency information stored in
7783 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7784 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7785 to try to start the kdm and gdm scripts as early as possible, and will
7786 start the facilities required by kdm or gdm as early as possible to
7787 make this happen.&lt;/p&gt;
7788
7789 &lt;p&gt;Give it a try, and see if you like the result. If some services
7790 fail to start properly, it is most likely because they have incomplete
7791 init.d script dependencies in their startup script (or some of their
7792 dependent scripts have incomplete dependencies). Report bugs and get
7793 the package maintainers to fix it. :)&lt;/p&gt;
7794
7795 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7796 manage to get the init.d script dependencies complete and correct. I
7797 expect we will get there in Squeeze+1, if we get manage to test and
7798 fix the remaining issues.&lt;/p&gt;
7799
7800 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7801 the BTS, please usertag the report to get it to show up at
7802 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7803 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7804 </description>
7805 </item>
7806
7807 <item>
7808 <title>Debian has switched to dependency based boot sequencing</title>
7809 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7810 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7811 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7812 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7813 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7814 have been migrated to using dependency based boot sequencing. This
7815 conclude work me and others have been doing for the last three days.
7816 It feels great to see this finally part of the default Debian
7817 installation. Now we just need to weed out the last few problems that
7818 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7819
7820 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7821 fixing the more fundamental problem of handing the event based
7822 non-predictable kernel in the early boot.&lt;/p&gt;
7823 </description>
7824 </item>
7825
7826 <item>
7827 <title>Taking over sysvinit development</title>
7828 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7829 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7830 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7831 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7832 the existing sysvinit upstream developer, I decided a few weeks ago to
7833 take over the package and become the new upstream. The number of
7834 patches to track for the Debian package was becoming a burden, and the
7835 lack of synchronization between the distribution made it hard to keep
7836 the package up to date.&lt;/p&gt;
7837
7838 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7839 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7840 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7841 and Fedora), based on the patches currently in use in these
7842 distributions. We Debian maintainers plan to move to this tarball as
7843 the new upstream as soon as we find time to do the merge. Since the
7844 new tarball was created, we agreed with Werner at SuSe to make a new
7845 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7846 development there. The project is registered and currently waiting
7847 for approval by the Savannah administrators, and as soon as it is
7848 approved, we will import the old versions from svn and continue
7849 working on the future release.&lt;/p&gt;
7850
7851 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7852 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7853 </description>
7854 </item>
7855
7856 <item>
7857 <title>Debian boots quicker and quicker</title>
7858 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7859 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7860 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7861 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7862 people involved in the boot system on Debian and Ubuntu, to see if we
7863 could find more ways to speed up the boot system. This was an Ubuntu
7864 funded
7865 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7866 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7867 of boot systems, and ways to handle the increasing number of boot
7868 issues introduced by the Linux kernel becoming more and more
7869 asynchronous and event base. The Ubuntu approach using udev and
7870 upstart might be a good way forward. Time will show.&lt;/p&gt;
7871
7872 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7873 process in Debian. All of these should be applied to get a quick
7874 boot:&lt;/p&gt;
7875
7876 &lt;ul&gt;
7877
7878 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7879
7880 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7881 clock is in UTC.&lt;/li&gt;
7882
7883 &lt;li&gt;Install and activate the insserv package to enable
7884 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7885 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7886
7887 &lt;/ul&gt;
7888
7889 These points are based on the Google summer of code work done by
7890 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7891 Villegas&lt;/a&gt;.
7892
7893 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7894 unstable yesterday. When we tested it, we were able to cut 6 seconds
7895 from the boot sequence. It depend on very correct dependency
7896 declaration in all init.d scripts, so I expect us to find edge cases
7897 where the dependences in some scripts are slightly wrong when we start
7898 using this.&lt;/p&gt;
7899
7900 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7901 introduced by Raphael Geissert today, one that could affect the
7902 startup speed as well. Instead of starting some scripts concurrently
7903 from rcS.d/ and another set of scripts from rc2.d/, it would be
7904 possible to run a of them in the same process. A quick way to test
7905 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7906 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7907 </description>
7908 </item>
7909
7910 <item>
7911 <title>BSAs påstander om piratkopiering møter motstand</title>
7912 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7914 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7915 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7916 programvareselskapene som Microsoft og Apple, publisert en rapport der
7917 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7918 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7919 dager siden kom
7920 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7921 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7922 dagene. Et spesielt interessant kommentar fra Sverige,
7923 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7924 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7925
7926 &lt;blockquote&gt;
7927 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7928 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7929 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7930 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7931 &lt;/blockquote&gt;
7932
7933 &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
7934 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7935 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7936 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7937 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7938
7939 &lt;p&gt;Fant lenkene via &lt;a
7940 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7941 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7942 </description>
7943 </item>
7944
7945 <item>
7946 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7947 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7948 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7949 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7950 <description>&lt;p&gt;Kom over
7951 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7952 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7953 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7954 jobber til daglig. En rask opptelling forteller meg at vi har 490
7955 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7956 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7957 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7958 </description>
7959 </item>
7960
7961 <item>
7962 <title>Kryptert harddisk - naturligvis</title>
7963 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7964 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7965 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7966 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7967 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7968 når en tar tap av arbeidstid, fortrolige dokumenter,
7969 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7970 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7971 til at jeg har kryptert harddisken på både kontormaskinen og min
7972 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7973 komme på avveie, den første informasjon relatert til jobben min ved
7974 Universitetet i Oslo, og den andre relatert til blant annet
7975 foreningsarbeide. Kryptering av diskene gjør at det er lite
7976 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7977 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7978 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7979 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7980 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7981 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7982 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7983 det er gjort slik jeg gjør det er minimale, og gevinstene er
7984 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7985 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7986
7987 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7988 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7989 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7990 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7991 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7992 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7993 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7994 betydelige.&lt;/p&gt;
7995 </description>
7996 </item>
7997
7998 <item>
7999 <title>Two projects that have improved the quality of free software a lot</title>
8000 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8002 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8003 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8004 quality of free software, and I wanted to mention both in case someone
8005 do not yet know them.&lt;/p&gt;
8006
8007 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8008 tool to detect and expose errors in the memory handling of programs.
8009 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8010 and it will report any problems on stdout. It is even better if the
8011 program include debug information. With debug information, it is able
8012 to report the source file name and line number where the problem
8013 occurs. It can report things like &#39;reading past memory block in file
8014 X line N, the memory block was allocated in file Y, line M&#39;, and
8015 &#39;using uninitialised value in control logic&#39;. This tool has made it
8016 trivial to investigate reproducible crash bugs in programs, and have
8017 reduced the number of this kind of bugs in free software a lot.
8018
8019 &lt;p&gt;The second one is
8020 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8021 a source code checker. It is able to process the source of a program
8022 and find problems in the logic without running the program. It
8023 started out as the Stanford Checker and became well known when it was
8024 used to find bugs in the Linux kernel. It is now a commercial tool
8025 and the company behind it is running
8026 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8027 free software community, where a lot of free software projects get
8028 their source checked for free. Several thousand defects have been
8029 found and fixed so far. It can find errors like &#39;lock L taken in file
8030 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8031 Y lines O to P can never be executed&#39;. The projects included in the
8032 community service project have managed to get rid of a lot of
8033 reliability problems thanks to Coverity.&lt;/p&gt;
8034
8035 &lt;p&gt;I believe tools like this, that are able to automatically find
8036 errors in the source, are vital to improve the quality of software and
8037 make sure we can get rid of the crashing and failing software we are
8038 surrounded by today.&lt;/p&gt;
8039 </description>
8040 </item>
8041
8042 <item>
8043 <title>No patch is not better than a useless patch</title>
8044 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8045 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8046 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8047 <description>&lt;p&gt;Julien Blache
8048 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8049 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8050 patch allow one to discuss a concrete and proposed solution, and also
8051 prove that the issue at hand is important enough for someone to spent
8052 time on fixing it. No patch do not provide any of these positive
8053 properties.&lt;/p&gt;
8054 </description>
8055 </item>
8056
8057 <item>
8058 <title>Standardize on protocols and formats, not vendors and applications</title>
8059 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8061 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8062 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8063 very good one to form a long lived computer infrastructure. It is the
8064 simple one, lost by many in todays computer industry: Standardize on
8065 open network protocols and open exchange/storage formats, not applications.
8066 Applications come and go, while protocols and files tend to stay, and
8067 thus one want to make it easy to change application and vendor, while
8068 avoiding conversion costs and locking users to a specific platform or
8069 application.&lt;/p&gt;
8070
8071 &lt;p&gt;This approach make it possible to replace the client applications
8072 independently of the server applications. One can even allow users to
8073 use several different applications as long as they handle the selected
8074 protocol and format. In the normal case, only one client application
8075 is recommended and users only get help if they choose to use this
8076 application, but those that want to deviate from the easy path are not
8077 blocked from doing so.&lt;/p&gt;
8078
8079 &lt;p&gt;It also allow us to replace the server side without forcing the
8080 users to replace their applications, and thus allow us to select the
8081 best server implementation at any moment, when scale and resouce
8082 requirements change.&lt;/p&gt;
8083
8084 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8085 open formats, but I would never recommend standardizing on a single
8086 application that do not use open network protocol or open formats.&lt;/p&gt;
8087 </description>
8088 </item>
8089
8090 <item>
8091 <title>Returning from Skolelinux developer gathering</title>
8092 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8093 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8094 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8095 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8096 Edu/Skolelinux development gathering. I got a bit done tuning the
8097 desktop, and looked into the dynamic service location protocol
8098 implementation avahi. It look like it could be useful for us. Almost
8099 30 people participated, and I believe it was a great environment to
8100 get to know the Skolelinux system. Walter Bender, involved in the
8101 development of the Sugar educational platform, presented his stuff and
8102 also helped me improve my OLPC installation. He also showed me that
8103 his Turtle Art application can be used in standalone mode, and we
8104 agreed that I would help getting it packaged for Debian. As a
8105 standalone application it would be great for Debian Edu. We also
8106 tried to get the video conferencing working with two OLPCs, but that
8107 proved to be too hard for us. The application seem to need more work
8108 before it is ready for me. I look forward to getting home and relax
8109 now. :)&lt;/p&gt;
8110 </description>
8111 </item>
8112
8113 <item>
8114 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8115 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8116 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8117 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8118 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8119 optimal. There is RFC 2307 documenting one way to store NIS maps in
8120 LDAP, and a modified version of this normally called RFC 2307bis, with
8121 some modifications to be compatible with Active Directory. The RFC
8122 specification handle the content of a lot of system databases, but do
8123 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8124
8125 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8126 we would like to store information about users, SMB clients/hosts,
8127 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8128 and LTSP configuration in LDAP. These objects have a lot in common,
8129 but with the current LDAP schemas it is not possible to have one
8130 object per entity. For example, one need to have at least three LDAP
8131 objects for a given computer, one with the SMB related stuff, one with
8132 DNS information and another with DHCP information. The schemas
8133 provided for DNS and DHCP are impossible to combine into one LDAP
8134 object. In addition, it is impossible to implement quick queries for
8135 netgroup membership, because of the way NIS triples are implemented.
8136 It just do not scale. I believe it is time for a few RFC
8137 specifications to cleam up this mess.&lt;/p&gt;
8138
8139 &lt;p&gt;I would like to have one LDAP object representing each computer in
8140 the network, and this object can then keep the SMB (ie host key), DHCP
8141 (mac address/name) and DNS (name/IP address) settings in one place.
8142 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8143
8144 &lt;p&gt;I would also like to have a quick way to map from a user or
8145 computer and to the net group this user or computer is a member.&lt;/p&gt;
8146
8147 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8148 in this regard, and the unix side need to catch up. Time to start a
8149 new IETF work group?&lt;/p&gt;
8150 </description>
8151 </item>
8152
8153 <item>
8154 <title>Endelig er Debian Lenny gitt ut</title>
8155 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8156 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8157 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8158 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8159 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8160 Et langt steg videre for Debian-prosjektet, og en rekke nye
8161 programpakker blir nå tilgjengelig for de av oss som bruker den
8162 stabile utgaven av Debian. Neste steg er nå å få
8163 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8164 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8165 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8166 slippes løs på skolene. Takk til alle debian-utviklerne som har
8167 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8168 bootsekvens tilgjengelig i stabil utgave, vha pakken
8169 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8170 </description>
8171 </item>
8172
8173 <item>
8174 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8175 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8177 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8178 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8179 Oslo. Most of Saturday was used for the general assemly for the
8180 member organization, but the rest of the weekend I used to tune the
8181 LTSP installation. LTSP now work out of the box on the 10-network.
8182 Acer Aspire One proved to be a very nice thin client, with both
8183 screen, mouse and keybard in a small box. Was working on getting the
8184 diskless workstation setup configured out of the box, but did not
8185 finish it before the weekend was up.&lt;/p&gt;
8186
8187 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8188 the Brazilian group, so that will have to wait for the next
8189 development gathering. Would love to have the Debian Edu installer
8190 automatically detect and configure a multiseat setup when it find one
8191 of these cards.&lt;/p&gt;
8192 </description>
8193 </item>
8194
8195 <item>
8196 <title>The sorry state of multimedia browser plugins in Debian</title>
8197 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8198 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8199 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8200 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8201 plugins available in Debian Lenny, to see which one we should use by
8202 default in Debian Edu. We need an embedded video playing plugin with
8203 control buttons to pause or stop the video, and capable of streaming
8204 all the multimedia content available on the web. The test results and
8205 notes are available on
8206 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8207 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8208 fill this need. My personal video player favorite, VLC, has a really
8209 bad plugin which fail on a lot of the test pages. A lot of the MIME
8210 types I would expect to work with any free software player (like
8211 video/ogg), just do not work. And simple formats like the
8212 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8213 totem and vlc plugins. I hope the situation will improve soon. No
8214 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8215
8216 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8217 be the only one fitting our needs. :/&lt;/p&gt;
8218 </description>
8219 </item>
8220
8221 </channel>
8222 </rss>